An ABA scheduling incident log records a material scheduling failure and its safety, access, privacy, service, workforce, payer, or financial consequences. It captures affected people and visits, direct facts, detection, immediate actions, escalation, evidence, correction, follow-up, and closure. The log distinguishes incidents from ordinary changes and routes each consequence to the qualified clinical, operational, privacy, safety, payroll, payer, or legal owner.

Define reportable scheduling incidents

Examples may include the wrong client or location, missing qualified coverage, absent communication support, unsafe route or room, large unauthorized bulk change, privacy exposure, repeated unnotified cancellation, or failed emergency handoff. Set thresholds and an ordinary-change alternative.

Publish the threshold and examples for schedulers, supervisors, clinicians, and on-call leaders. A routine, authorized time change with successful notice may stay in the ordinary change log. A change becomes an incident when it creates or could reasonably create material safety, privacy, access, continuity, workforce, payer, or financial harm, violates an approval boundary, or affects a defined number of records. Permit staff to report an uncertain event for triage without deciding its legal or clinical classification.

Use severity and urgency fields as routing aids. “Possible client mismatch with a visit beginning now” requires immediate containment even while facts are incomplete. “Bulk reminder failure discovered after the day closed” may require prompt family communication and access review but no active-site safety response. Define who can set and revise severity, and preserve each classification change with the evidence available at that time.

Record direct facts

Capture detection time, reporter, system and schedule versions, affected visit cohort, observed event, current safety state, people notified, immediate actions, service impact, and evidence preserved. Avoid unsupported conclusions about cause or intent.

Give each incident a stable ID. At intake, record what was observed, by whom, when, and through which source. Identify the potentially affected people, visits, dates, locations, service lines, staff roles, and systems. If the cohort is uncertain, say how it is being bounded and when the next reconciliation will occur. Preserve relevant schedule versions, messages, system events, and exports under the practice’s privacy, security, and retention rules.

Separate a reporter’s words from the organization’s later findings. A family report, staff statement, automated alert, and system log may disagree. Label each source and keep the discrepancy open. When a fact is corrected, append the prior value, new value, author, timestamp, reason, evidence source, and affected records. This maintains a reliable history and avoids asking staff to reconstruct the event from memory.

Use minimum necessary access

Incident records can contain sensitive schedule, health, family, employee, and payer information. Restrict each response track to the information it needs. A privacy reviewer may need recipient and disclosure details; a scheduler may need the approved correction and communication instruction; payroll may need affected work time. Keep broad narrative fields out of routine dashboards and use stable links to protected source records when possible.

The practice should define who may view, change, export, and close an incident and how access is reviewed. If the event itself involves possible unauthorized access or disclosure, route it immediately through the privacy or security procedure. The incident log supports that review but does not determine whether a legal breach occurred or which notice law applies.

Route clinical and access consequences

The BACB Ethics Code supports qualified clinical risk and documentation decisions for covered professionals. DOJ effective-communication guidance informs access and communication review for covered entities.

Schedulers can stop an unsafe or unauthorized release under the written escalation rule, contact the designated leader, and document direct facts. A qualified clinician decides clinical continuity, risk, treatment, and supervision questions. The safety owner manages immediate site or travel hazards. Accessibility staff review whether the communication method, interpreter, AAC support, or physical setting was usable. These owners should coordinate through the incident ID while keeping their decisions attributable.

Family communication should state what is known, what action affects today’s service, how the family can get accessible help, and when the next update will come. Avoid speculative causes or promises about clinical, payer, legal, or financial outcomes. Seek the person’s participation and assent where applicable, and include a legally authorized decision-maker when required.

Separate response tracks

Use named owners for immediate safety, clinical continuity, privacy or security, workforce, payer, payroll, family communication, schedule correction, and insurance or legal notice. Different clocks may apply. Response should continue while classification is refined.

An incident coordinator should maintain the shared timeline and check that no consequence disappears between teams. The scheduler may correct future visits while payroll reviews time already worked, the clinician reviews continuity, and the privacy lead determines whether an exposure occurred. A single “resolved” checkbox is too coarse for these parallel states.

A practical incident workflow is:

  1. Triage immediate safety and stop further affected releases when authorized.
  2. Open the incident ID, preserve direct evidence, and bound the initial visit cohort.
  3. Notify the required clinical, access, privacy, workforce, payer, and operational owners.
  4. Communicate an accessible, approved interim plan to affected people.
  5. Correct the schedule through versioned changes and reconcile downstream records.
  6. Document findings, corrective actions, validation, residual risk, and open specialized work.
  7. Close each response track only after its named owner records an outcome.

Reconciliation should cover every affected visit. Check the schedule, delivered-service record, staff time, authorization state, charge, claim, client communication, and recovery record as applicable. Keep these as separate states. Correcting a calendar entry does not prove that a time record, claim, or family notice is accurate.

A fictional incident cohort

Cedar Harbor ABA reviews six scheduling incidents. Four have immediate containment, affected-visit reconciliation, family communication, and corrective action complete. One awaits privacy review, and one awaits payroll correction. Closure completeness is 4 of 6, or 66.7%.

The denominator is the six incidents opened during the locked month, including the two still open at the cutoff. The practice also reports 17 affected visits: 13 fully reconciled, two awaiting privacy direction, and two awaiting payroll correction. Visit reconciliation is therefore 13 of 17, or 76.5%. Those percentages answer different questions and neither should be described as the overall safety rate.

One completed incident involved an incorrect clinic room that lacked the client’s required communication setup. The team moved the visit, confirmed access with the family, preserved the original and corrected room assignments, and linked a facilities action. The evidence supports an access-control improvement. It does not establish whether the treatment was clinically effective or whether any legal violation occurred.

Learn without erasing the event

Preserve original values, corrected values, timeline, cause status, actions, owner, due dates, validation, and residual open work. Track incidents by type, impact, detection source, recurrence, service loss, access failure, and workflow version.

Use a structured cause review only after urgent response is stable. Ask what condition allowed the event, what detection control worked or failed, and where authority or handoff was unclear. Distinguish supported contributing conditions from hypotheses. Avoid using an incident log as an employee blame list. Personnel, licensure, legal, and disciplinary decisions belong in their authorized processes with appropriate review.

Test corrective action prospectively. If the action adds a required room-access field, sample future visits that require access support and verify that the field is complete, reviewed, and usable. If the action changes bulk scheduling permissions, test approval, rollback, and affected-record export. Record the sample denominator, exceptions, and next owner.

Incident review checklist and limits

Before closure, confirm:

  • the reportable threshold and initial severity are recorded;
  • direct facts, source labels, schedule versions, and the affected cohort are preserved;
  • immediate safety and service-continuity actions have attributable owners;
  • the person and family received timely communication through a usable channel;
  • privacy, clinical, access, workforce, payer, payroll, and legal questions were routed within scope;
  • every affected visit and applicable downstream record was reconciled;
  • corrections append history and identify author, time, reason, source, and affected records;
  • corrective action was validated against a defined future sample; and
  • every remaining task has an owner, due date, and update path.

An incident log is an operational coordination record. It cannot replace emergency procedures, clinical documentation, required incident reporting, privacy or security assessment, payroll review, insurer notice, or legal advice. Reporting thresholds and retention obligations vary by entity, contract, jurisdiction, incident type, and facts. Owners should have qualified reviewers approve the design and escalation rules, keep uncertain classifications visible, and never delay urgent care or emergency help while completing the log.

Related resources

Sources