An ABA schedule conflict resolution queue turns each scheduling inconsistency into an owned case with a conflict type, affected visits, current source records, consequence, decision authority, next action, due time, communication plan, and closure evidence. It distinguishes double booking, authorization, staff, supervision, room, travel, access, client availability, and system-sync problems so teams fix the actual source rather than overwriting one calendar.
Create a conflict from evidence
Capture the conflicting values, systems or people, timestamps, affected visit IDs, and earliest consequence. Preserve both values until the responsible role resolves them. Examples include two clients assigned to one worker, mismatched locations, an expired authorization, unavailable interpreter, or travel that overlaps service time.
Use one record per conflict episode
A build-ready queue record can include:
| Field | Purpose |
|---|---|
| Conflict ID | Stable episode identity |
| Affected visits | Every schedule row exposed |
| Competing values | Value, source, version, timestamp |
| Consequence | Safety, service, access, pay, payer, facility |
| Authority | Role that may decide each disputed field |
| Workflow | Current state, owner, next action, due time |
| Closure | Final value, downstream updates, verification |
Link related conflicts when they share a cause, but do not merge them if their affected visits or decisions differ.
Classify consequence and urgency
Consider immediate safety, missed care, client burden, staff pay, supervision, authorization, claim risk, room access, and privacy. Define response targets by consequence. An urgent clinical or safety matter follows its immediate route while the queue record preserves the later reconciliation.
Set a source-specific decision order
There is no universal source hierarchy for every scheduling field. Identify which source governs the disputed fact for the exact product, contract, service, role, and date. A clinician owns clinical judgment, a payer owns its authorization action, a workforce owner applies employment rules, and operations controls approved resource facts.
When authority is unclear or sources genuinely conflict, hold the affected action, preserve both records, and escalate to the named qualified role. A portal, call note, calendar, or copied spreadsheet should not silently outrank a binding or case-specific source outside its scope.
Route each decision
A payer controls its authorization action; HealthCare.gov explains that preauthorization is not a payment promise. A qualified clinician decides clinical fit. Operations resolves resource and calendar facts. The BACB Ethics Code supports clear competence, client, risk, supervision, and documentation boundaries.
Prevent destructive resolution
Do not fix a double booking by deleting one visit, an authorization mismatch by altering the clinical service, or a travel overlap by shortening recorded service. Preserve the proposed and current states and use the authorized change workflow. Every affected person should receive an accurate update through the appropriate channel.
Restrict free-text descriptions to the minimum operational facts. Sensitive clinical, personnel, or family details belong in their controlled records. The queue can show that a qualified decision is pending without exposing the underlying narrative to every scheduler.
Close every connected record
A conflict closes after the approved state reaches scheduling, family and staff notices, timekeeping, clinical documentation, room or route, authorization tracking, charge hold, and claim workflow as applicable. Store the decision, effective time, owner, changed fields, and preserved history.
Define reopen conditions
Reopen the episode when the final value changes, a downstream system rejects the update, a recipient reports an inaccurate notice, the visit occurs under a different configuration, or the same conflict returns within the review window. Keep the earlier closure evidence and create a new state transition.
A queue item can be administratively closed while a claim, payroll correction, or family follow-up remains open only if those linked tasks have separate owners and due dates. Report full reconciliation separately from the first scheduling decision.
A fictional queue
Stonebridge ABA reviews 22 conflicts that reached their due time. Eighteen have a verified final state in every affected record. Closure completeness is 18 of 22, or 81.8%. The four open cases include two travel overlaps, one authorization mismatch, and one missing communication support.
Use the denominator to manage risk
The four open cases remain in the 22-conflict due cohort even if their visits are moved to a later date. Report their age, next consequence, owner, and latest family or staff update. The two travel conflicts count as two episodes only if they involve separate affected configurations.
Also report failed checks by type. One episode may contain several mismatches, so failure count can exceed conflict count. Conflict count measures affected decision episodes, while failed-check count measures repair work and recurring control weakness.
Measure recurrence
Track conflicts opened, age, consequence, source system, affected visits, on-time closure, reopens, service loss, staff-pay corrections, and repeat causes. Sample closed cases against raw records. A fast closed status has little value when another system still contains the conflict.
Run a daily queue review
Review immediate safety and access consequences first, then items approaching a visit or payroll deadline, oldest unresolved episodes, and repeat causes. Confirm that every open item has an owner, a next action that can actually move it, and a scheduled update to affected people.
Each month, identify the controls that would have prevented the most consequential conflicts. Assign a system, policy, training, or data-quality change and retest it. The goal is fewer conflicting source states, not merely faster queue closure.
Resolve the conflict chain, not only the visible overlap
One overlap may involve a client, staff member, supervisor, room, vehicle, interpreter, authorization, or system version. Build the connected cohort before moving anything. Identify which record is authoritative, which commitments were accepted first under policy, what decisions are reserved, and which downstream visits or people would be affected by each option.
Test complete alternatives. Moving one visit may fix a room conflict while creating impossible travel, lost supervision, inaccessible communication, or an overtime risk. The chosen resolution should show approvals, client and staff communication, effective time, version, and follow-up. If no option clears every gate, use the safe hold or cancellation route and keep the conflict open for structural repair.
Owner conflict-queue questions
- Is there one episode linking every conflicting resource, visit, version, and source event?
- Are urgency and consequence based on timing and impact rather than who escalated first?
- Does the decision order follow published policy and preserve qualified authority?
- Were all affected schedules, paid work, access supports, and communications recalculated?
- Can a resolved conflict reopen when a dependent fact changes?
- Do recurring conflict types produce resource, process, or system corrections with owners?
Closure requires every connected record to match the released resolution, not merely an empty queue row.
A connected-conflict example
One room is assigned to two visits, and moving the later visit would put its technician beyond a realistic travel window for the next client. The queue links both visits, the room, employee route, supervisor schedule, family contacts, and publication version. It evaluates a different room, different time, and qualified coverage as complete configurations.
Only the different-room option clears facility, access, clinical, payer, staff, and timing gates. Operations publishes the new version and sends corrections to affected people. The conflict stays open until calendars, site plan, travel, and downstream records reconcile. Root-cause review finds a stale room-capacity sync and tests the repair against another double-booking scenario.
Related resources
- ABA Same-Day Session Extension Approval Workflow
- ABA Supervision Capacity Allocation Calendar
- ABA Early-End Session Reconciliation Workflow
- ABA Staff Availability Change Intake Workflow
