ABA scheduling reconciliation exception aging measures how long unresolved schedule discrepancies remain open from a defined creation event to accepted disposition. The workflow records the source and destination records, consequence, owner, next action, due date, pause reason, escalation, communication, and evidence. It keeps old or high-impact exceptions visible after the visit date and avoids improving metrics by resetting clocks, changing queues, or excluding difficult cases.

Define the creation event

Choose the first detected source-to-destination mismatch, failed reconciliation deadline, user report, or system alert that creates the actionable exception. Record event time and processing time. Avoid resetting age when the row moves between queues, changes owners, or receives another note. Preserve links to earlier related findings.

Classify exception types

Separate missing event, stale version, duplicate, wrong field, unmatched identity, failed message, calendar discrepancy, permission gap, payer reference issue, payroll or claim linkage, archive gap, and unknown source. Each class needs a likely owner and evidence path. A broad sync issue category weakens triage and recurrence analysis.

Prioritize consequence

Assess imminent visit, wrong-client risk, safety or communication information, staffing or supervision, accessible notice, payer deadline, payroll, claim, privacy exposure, and downstream spread. Record severity and confidence separately. Age matters alongside consequence. A new wrong-client exception may outrank an older low-impact analytics mismatch.

Define clocks and service levels

State calendar or business time, working hours, holidays, start, pause, resume, due, breach, and close events. Use sourced service levels or explicit internal targets. Keep paused time and total elapsed time both visible. A vendor wait may explain delay without removing the client's unresolved record from leadership view.

Require a next action

Every open exception needs an owner, specific next step, due time, required evidence, dependency, and escalation. Replace vague researching notes with the actual source or person being checked. When no further action is possible, route a documented limitation or risk-acceptance decision to the qualified owner instead of leaving the row indefinitely active.

Preserve the original cohort

Lock exceptions due for the reporting period. Keep resolved, transferred, reopened, duplicate-linked, paused, and invalid findings with final disposition. Report new arrivals separately. A live backlog count cannot show whether work aged out, disappeared, or was resolved. Use stable finding IDs and preserve reopen history.

Escalate before harm

Set triggers for imminent visits, breached deadlines, repeated failed contact, unavailable owner, unknown identity, security concern, and growing downstream exposure. Name operational, clinical, privacy, vendor, payroll, billing, and leadership paths. Escalation should produce a decision or action, not merely add recipients to a message thread.

Close with accepted evidence

Define closure by exception class: source and destination match, duplicate removed, communication completed, access revoked, payer item routed, historical exception accepted, or limitation documented. Record reviewer and time. A closed ticket without a verified schedule state leaves the underlying reconciliation incomplete.

Document operating limits

Write the conditions under which scheduling reconciliation exception aging is reliable and the conditions that require a hold, alternate route, or specialist decision. Include unsupported systems, stale or missing evidence, unavailable owners, untested versions, capacity limits, timing assumptions, and user groups needing another communication path. Show these limits in procedures, dashboards, and release evidence where operators will see them. Assign each temporary limitation an owner, control, expiry, and next test. When a limitation affects an upcoming visit or active client and staff workflow, route current facts through the approved continuity process while correction proceeds.

Run an operator acceptance review

Before approving scheduling reconciliation exception aging, have reviewers independently explain the purpose, source, version, cohort, exclusions, ordinary result, failure state, stop rule, and final evidence. Trace one normal case and one high-consequence exception through the actual workflow. Ask which client, staff, clinical, communication, privacy, security, or financial decisions depend on the result and who owns uncertainty. Inspect what users see and what automated actions follow. Compare the register with raw evidence rather than relying on a dashboard or vendor summary. Record reviewer, date, questions, conditions, disagreements, and decision. Reopen acceptance when a later defect shows the tested workflow or consequence model was incomplete.

Assign decision rights

For scheduling reconciliation exception aging, record who detects the issue, who owns the source, who approves action, who performs it, and who accepts the result. The CASP public overview provides high-level operations and risk context. Under the BACB Ethics Code, covered professionals retain qualified clinical responsibility. The exception owner coordinates while accessibility, security, payroll, billing, and payer roles retain scoped decisions. Separate tool access from authority to change clinical, privacy, accessibility, or financial meaning. Give urgent holds and continuity decisions named owners so technical work does not outrun accountable review.

Protect data and access

Classify the entity, records, systems, identities, environments, and vendors involved in scheduling reconciliation exception aging. For HIPAA covered entities and business associates, the HHS Security Rule overview frames safeguards for ePHI. Restrict discrepancy details and bulk reports, protect attached evidence, and ensure escalation tools do not broaden schedule or client access. Restrict bulk tools and evidence, log privileged actions, review temporary access, and preserve an incident route.

A fictional aging review

Cypress Hollow ABA locks 60 exceptions due for review. Forty-eight close within target, five close late, four remain open within target, two are overdue, and one reopened after a stale calendar reappears. On-time closure is 48 of 60, or 80%. Twelve non-on-time rows remain visible by age and consequence.

Build the aging register

Use exception ID, class, source and destination IDs, creation event and time, consequence, severity, owner, next action, due time, pause and resume, contacts, dependency, escalation, correction, retest, close evidence, and reopen history. Link evidence to the exact source, version, cohort, and decision. Keep held, failed, incomplete, excluded, and unresolved rows visible. The register should support forward action and later reconstruction without copying sensitive details into a broadly available worklist.

Test aging arithmetic

Use an ordinary open row, weekend, holiday, approved pause, owner transfer, vendor wait, merged duplicate, reopened exception, and missing timestamp. Recalculate elapsed and target time independently. Confirm dashboards preserve original creation and show N/A when a required clock cannot be established.

Release and reconcile

Lock the locked exception cohort before action, record the approved rule and version, and use a representative pilot. Monitor source and destination behavior, user-facing views, side effects, and high-consequence exceptions. Verify every closed row against source and destination state and keep late, paused, overdue, reopened, and limited cases assigned. Pause at the defined stop condition. Close only when every row reaches an accepted disposition and affected people receive current, usable information.

Review after change

Review scheduling reconciliation exception aging after new exception classes, service-level changes, incidents, vendor delays, queue migrations, leadership review, or recurring overdue work. Compare new evidence with the prior approved version and label any break in comparability. Update procedures, training, monitoring, access, and regression cases together. Preserve retired definitions needed to interpret older records. Assign the next review date before closing the change.

Measure exception aging

Report exceptions due, closed on time, closed late, open within target, overdue, paused, reopened, ownerless, high consequence, and reconciled. Define every event, clock, numerator, denominator, inclusion rule, exclusion, and maturity window before reporting. Pair percentages with counts, oldest open item, maximum delay, and client or staff consequence. Segment by the source or version that can be acted on. Keep failed work visible until verified correction and retest.

Related resources

Sources