An ABA schedule decision log records a consequential scheduling question, affected cohort, alternatives considered, source evidence, authorized decision-maker, rationale, conditions, effective period, communication, monitoring, and outcome. It captures why a choice was made without turning meeting notes into clinical, payer, legal, or workforce authority. The log supports handoffs, consistent exceptions, review, and later correction.
Define which decisions belong
Log schedule-rule changes, capacity releases, major reassignments, closures, persistent exceptions, waitlist rules, service-line pilots, and other choices with material client or workforce effects. Routine field edits belong in the audit trail rather than the decision log.
Separate a decision log from an activity log
An activity log records what happened to a schedule row. A decision log records why a consequential choice was made, by whom, under which evidence and limits. The decision may affect many schedule rows or a future operating rule. Link the two records without duplicating every edit.
Write entry criteria so staff know when to open a decision record. Examples include a change to booking priority, release of a new time band, a recurring exception, or a capacity reduction. Small routine changes remain in the schedule audit trail unless they reveal a pattern needing governance.
Record the decision packet
Include question, date, cohort, direct facts, alternatives, sources, assumptions, decision owner, consulted roles, rationale, conditions, effective period, monitoring, stop criteria, communication, and linked schedule version. Preserve dissent or unresolved evidence where relevant.
Use a build-ready schema
A useful decision record contains:
| Field | Required content |
|---|---|
| Decision ID and title | Stable reference and plain-language question |
| Scope and cohort | People, services, sites, dates, and exclusions affected |
| Current state | Why a decision is needed now |
| Alternatives | Options considered, including maintaining the current state |
| Evidence register | Source, date, owner, strength, and limitation |
| Decision rights | Accountable owner and consulted qualified roles |
| Choice and rationale | Selected action tied to evidence |
| Conditions and boundaries | What the decision does and does not authorize |
| Effective period and stop rules | Start, review, expiration, and rollback events |
| Communication and implementation | Owners, schedule versions, and audiences |
| Outcome review | Measures, date, and final disposition |
Keep authority attributable
The BACB Ethics Code supports qualified clinical accountability for covered professionals. HealthCare.gov cautions that preauthorization does not promise cost coverage. Log each distinct decision under its actual owner.
Split compound questions
“Should we open weekend ABA appointments?” contains several decisions. Operations can assess schedule demand and facility capacity. A qualified clinician decides case-specific clinical suitability and clinical safeguards. Workforce owners assess staffing and paid-time rules. Payer operations verifies product and authorization paths. Clients decide whether offered times fit their preferences.
Record each conclusion and scope separately, then let the accountable business owner decide whether the pilot can proceed within those constraints. One signature should not make every underlying statement appear to come from the same authority.
Use evidence at the right strength
Separate known facts, estimates, forecasts, professional judgments, payer statements, and unresolved questions. State the evidence date and scope. Avoid claiming a pilot caused an outcome when other schedule, staffing, clinical, or seasonal conditions changed.
Compare alternatives explicitly
For each viable option, record expected benefits, risks, resource needs, reversibility, client and staff effects, access implications, and unresolved evidence. A compact comparison table can expose when the preferred option depends on an assumption rather than a verified fact.
Use decision criteria declared before the choice, such as service continuity, safe staffing, accessible availability, financial exposure, implementation time, and reversibility. Weighting can support discussion, but the score does not replace qualified judgment or create legal, clinical, or payer authority.
A fictional decision
Cedar Point ABA considers opening eight weekend slots. The log records 14 mature requests, 10 ready configurations, eight slots, staffing and supervision limits, two access actions, a four-week pilot, and stop rules. The owner approves the pilot rather than permanent expansion.
Show the pilot math and limits
Demand readiness is 10 of 14 requests, or 71.4% at the locked review date. Eight slots can serve at most eight ready configurations in the first release, leaving at least two ready requests without a slot. The practice records its selection rule and keeps all 14 requests visible with dispositions.
The four-week pilot defines staffing, supervision, client communication, access actions, payer checks, maximum slots, service dates, review metrics, and stop conditions. It does not establish lasting demand or prove that weekend availability improves outcomes. A permanent decision requires a new review of actual delivery, client choice, staff burden, incidents, and financial results.
Review outcomes
At the review date, compare expected and actual demand, releases, delivery, service loss, staff burden, access, incidents, and client feedback. Record continue, modify, expire, or reverse, with new authority and schedule versions. Preserve the original decision.
Keep the log searchable and reviewable
Use controlled tags for service line, site, decision type, affected period, status, and review date. Link related decisions so a temporary exception does not silently become precedent. Restrict sensitive evidence while keeping the decision's scope and owner visible to people implementing it.
At least monthly, review decisions due for expiration, outcome review, or unresolved evidence. Sample implementations against the approved conditions. When actual practice diverges, correct the schedule or open a new decision rather than rewriting the original record.
A competing-alternatives example
An owner must decide whether to extend the scheduling freeze from 24 to 48 hours before service. The longer freeze may reduce late changes, but it can also increase override requests and make family or staff changes harder to accommodate. The decision packet should define the affected cohort, current error and override rates, family and workforce burden, access implications, alternatives, assumptions, and a reversible pilot period.
Record why the chosen option fits the evidence available on that date. The operations owner can decide the publication rule, while clinical, payer, workforce, access, privacy, or legal specialists decide issues within their domains. Avoid writing that everyone approved when reviewers actually supplied narrower advice or conditions.
Record uncertainty and a stopping rule
State what is known, what is inferred, and which evidence remains missing. Define the pilot's cohort, start and end, success and harm measures, review owner, and stop conditions before launch. If late cancellations or inaccessible notices worsen, the practice should know whether to pause, roll back, or adjust without inventing a new standard midstream.
At review, compare the original prediction with actual outcomes. Preserve surprising or unfavorable results and link the follow-up decision rather than editing the earlier rationale to look more certain.
Owner decision-log questions
Ask whether consequential choices can be found by topic, date, affected cohort, owner, evidence, and effective period. Check whether related schedule changes and notices link back to the decision. Sample older entries for expired assumptions and review dates. A useful log supports learning and accountability; it is not an activity transcript or a substitute for the source systems that prove implementation.
Related resources
- ABA Scheduler Workload Capacity Review
- ABA Scheduling Escalation Policy
- ABA Booking Lead-Time Report
- ABA Schedule Lock Override Workflow
