ABA Schedule Exception Approval Log

Name the base rule

Link the exact policy or configuration, version, effective date, and normal requirement. Describe the requested change and affected visits. If no approved base rule exists, route policy creation separately instead of labeling ordinary discretion as an exception.

Use a complete exception record

A practical log includes:

Link controlled evidence and keep sensitive detail out of the general log.

Assign authority by issue

Operations may decide routine scheduling within policy. Qualified clinicians own clinical changes. Payer, access, workforce, payroll, privacy, safety, and legal roles decide within their domains. One approval cannot confer every type of authority.

Use explicit states and deadlines

Track received, clarification due, domain reviews due, approved with conditions, declined, returned to standard rule, active, stop triggered, expired, extended, reconciliation, and closed. Each state needs an owner and next action. A pending review is not approval.

Set a decision deadline before the first affected visit. When the deadline cannot be met, follow the default hold or standard-rule path and communicate the current state accurately.

Capture payer and clinical boundaries

HealthCare.gov cautions that preauthorization does not promise cost coverage. The BACB Ethics Code addresses clinical competence, client involvement, risk, documentation, and accountability for covered professionals. Store each decision and source separately.

Avoid turning exceptions into shadow policy

Report repeated requests by base rule, reason, owner, service, site, and outcome. When similar exceptions recur, pause and decide whether the rule is wrong, capacity is inadequate, training is unclear, or a defined alternative policy is needed.

Do not extend an exception automatically because it worked once. Recheck current evidence, client choice, access, staff, supervision, payer state, and actual outcomes. A policy change needs its own review and effective version.

Set conditions and expiration

Record start, end, visit count, required supervision or communication support, monitoring, stop criteria, next review, client notice, and rollback. Recheck expired credentials, authorization, staff availability, setting, and access before extending an exception.

Monitor the approved cohort

List every visit operating under the exception and compare approved with actual staff, time, service, setting, modality, support, and outcome. Stop or escalate when a required condition fails. Preserve unaffected visits under the base rule.

Give clients, families, and staff the material schedule information and correction route through approved channels. Avoid exposing the internal rationale or another person's information beyond what they need.

Require an exception to describe its operational consequence

The request should show which visit, series, person, system, or policy is affected; the ordinary rule; why the rule cannot be followed; options considered; client and workforce impact; payer, clinical, access, privacy, and safety dependencies; duration; monitoring; and rollback. A preference for speed or convenience is not enough. The approving role needs the facts relevant to its authority and a clear statement of what approval does not decide.

Estimate the downstream burden before release. A one-time manual schedule change may create extra notice, payroll, authorization, documentation, supervision, reconciliation, or claim work. Assign those tasks and include them in the approval. Otherwise the exception appears low-cost only because its work shifts invisibly to another team or period.

A fictional exception cohort

River Stone ABA reviews nine requests. Five receive scoped approvals, two return to the standard rule after clarification, one awaits clinical review, and one lacks payer evidence. Disposition completeness is 7 of 9, or 77.8%. Each approved entry has an expiration and linked visit list.

Keep the two pending requests open

The five approvals and two returns to the standard rule produce seven dispositions. Clinical review and payer evidence remain separate pending routes. Their affected visits follow the defined hold or base-rule state until a decision arrives.

After the effective period, report visits covered by the five exceptions, failed conditions, extensions, service loss, client corrections, staff time, and downstream reconciliation. Approval count alone does not show whether the exceptions worked.

Account for operational cost and burden

Record the manual coordination, overtime or schedule disruption, added travel, unused capacity, family communication, supervision work, and reconciliation created by the exception. Keep employee time, payer treatment, and client financial effects under their own rules and owners.

Compare the exception with a feasible standard configuration when one exists. This helps leaders decide whether the exception should close, a recurring operating problem needs remediation, or the base policy should enter a formal change process.

Close and learn

Reconcile actual visits, service time, staff time, notes, authorization usage, charges, claims, client communication, incidents, and open conditions. Track exception count, reasons, owners, days active, expirations, extensions, failures, and repeated requests that may justify a policy change.

Audit closure evidence

Sample closed records against the base rule, approval, schedule versions, notices, actual visits, timekeeping, clinical records, authorization, charges, and claims. Reopen the exception when a downstream system still uses the temporary state.

Retain the decision and history under applicable access and retention rules. Remove temporary system permissions, flags, and assignments when the exception ends.

Owner exception questions

• Is the base rule current, explicit, and applicable to the exact request?
• Do the facts and alternatives support a time-limited exception rather than a rule change?
• Has each qualified role approved only the decision within its authority?
• Are affected people, systems, costs, conditions, monitoring, expiration, and rollback documented?
• Does expiration create a review or automatic safe state instead of silent continuation?
• Are repeated exceptions analyzed as evidence that the rule or operating design needs revision?

Closeout should verify the exception ended or was renewed through a fresh decision and every downstream record reconciled. Approval alone is not closure evidence.

An exception lifecycle example

A site asks to hold one room past its normal scheduling cutoff for a four-week transition. The request identifies the base rule, affected visits, facility access, staff closing work, supervisor coverage, client communication, payer and clinical states, added cost, and the date the temporary need ends. Facility, workforce, clinical, and operating owners each decide only the part within their authority.

Approval creates conditions, monitoring, and an automatic hold after the fourth week unless a fresh review occurs. Two weeks in, repeated late documentation shows the operating design is not working as assumed. The owner pauses new use, protects already affected visits through the approved route, and evaluates a different pattern. The log retains the original approval and evidence rather than converting the temporary exception into an unwritten permanent schedule.

Related resources

• ABA Scheduling Ownership and RACI Matrix
• ABA Waitlist Priority Review
• ABA Scheduling KPI Dictionary
• ABA Makeup Session Offer Workflow

Sources

• Council of Autism Service Providers, Organizational Guidelines public overview
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts
• HealthCare.gov, Preauthorization glossary