An ABA authorization expiration calendar tracks each client, payer, product, service, provider, setting, approved quantity, period end, submission milestone, decision state, affected schedule cohort, hold rule, and continuity owner. It creates early warning without treating a renewal request as approval. The calendar links payer evidence to exact visits and preserves separate clinical recommendations, benefit information, claim outcomes, and payment.

Create one row per authorization configuration

Record member and plan, service, codes when applicable, provider or group, location, modality, quantity and unit, frequency, start and end, payer source, reference, received date, last verified date, and owner. Split rows when any controlling dimension differs.

Work backward from required dates

Add clinical review, updated assessment or plan, signatures or orders when applicable, record gathering, submission target, payer decision target, family update, schedule hold, and escalation dates. Use current payer and contract sources for the actual lead time.

Keep authorization meaning narrow

HealthCare.gov cautions that preauthorization does not promise a plan will cover cost. A pending or approved authorization does not establish clinical appropriateness, provider availability, claim acceptance, adjudication, or payment.

Protect continuity and clinical authority

The BACB Ethics Code addresses service continuity, client involvement, clinical accountability, documentation, and transitions for covered professionals. Qualified clinicians own clinical recommendations. Operations coordinates payer and schedule work.

A fictional expiration cohort

Lakeside ABA has 20 authorization rows ending within 45 days. Twelve are renewed, four are pending after complete submission, two need clinical material, one needs payer clarification, and one has a client-chosen service end. Renewal readiness is 16 of 20, or 80% when renewed and complete pending rows are reported together and labeled.

Reconcile every affected visit

Before the period ends, identify future visits and apply the approved hold or release rule. Track rows due, complete, pending, expired, stopped, late, and appealed; visits held; service loss; family updates; payer references; and downstream claim issues. Preserve the old and new periods.

Use a build-ready calendar record

Each row needs a stable authorization identifier, client and product, service and code when applicable, units, period, approved providers and settings, payer evidence, submission path, responsible owner, linked clinical-material task, affected future visits, hold rule, and next action. Restrict sensitive detail by role.

Record source issue date and verification date. A portal view, letter, call reference, and contract can answer different questions and should retain their own provenance.

Define workflow states

Useful states include review due, clinical material in progress, ready to submit, submitted, payer clarification, additional information due, approved, partially approved, denied, appeal or review underway, expired, client-chosen end, and closed. Define required evidence and owner for every state.

Do not label a row pending when the practice still owes material. Separate payer decision time from internal preparation time so the calendar points to the responsible next action.

Control units and quantities

Store the unit definition, approved quantity, scheduled quantity, delivered quantity, remaining quantity, and source period. Avoid mixing visits, hours, 15-minute units, days, or weekly limits. Reconcile any payer display with the controlling document and current workflow.

Forecast remaining quantity from released visits, while labeling it as a planning figure. Future cancellations, changes, payer rules, and supported claim units can produce a different final balance.

Handle amended and overlapping periods

When a payer changes dates, quantity, provider, setting, or service, preserve both records and link the superseding evidence. Define which row governs each date and visit. Do not overwrite the old period until open claims, corrections, appeals, and reconciliation are complete.

Test gaps, overlaps, retroactive changes, partial decisions, and multiple products. Route ambiguous precedence to the responsible payer or legal owner before automated release.

Connect the calendar to schedule holds

Predeclare the date and condition that moves affected future visits to review or hold. Identify the exact appointments, staff, families, rooms, and downstream work. Qualified clinicians own continuity and treatment recommendations, while operations applies the approved scheduling rule.

If current authority permits service while a decision is pending, store that route and scope. Do not infer it from a prior approval or common payer behavior.

Communicate the current state accurately

Tell the person or family what has been submitted, what the payer has decided, which services or dates are affected, what options are available, and when the next update will arrive. Use the requested accessible channel and distinguish sent, delivered, acknowledged, and reached.

Avoid saying coverage is approved when the evidence is only benefit information, submission receipt, or a pending review. Preserve questions and corrections.

Audit the calendar against evidence

Sample rows from each state and compare dates, quantities, providers, settings, payer sources, linked visits, and hold actions. Check expired rows that still release visits, approvals with unused old configurations, and pending rows without next actions.

Report rows due, completed on time, internally delayed, payer-pending, expired, held, interrupted, and later reconciled. Keep renewal process performance separate from service continuity and claim outcomes.

Handle uncertain or late decisions without implying coverage

When a request is submitted but no current decision exists, keep submitted, received, pending information, under review, approved, denied, appealed, expired, and unknown as separate states. Record the source, reference number, dates, configuration, and next follow-up. A verbal estimate, portal status, or prior period cannot become authorization for the new dates, units, provider, location, or service.

Connect the calendar to a controlled schedule hold. Before the current period ends, qualified clinical and payer owners determine the continuity options and communication. Tell the family what is verified, what remains pending, the practice's current scheduling state, and when the next update will come. Avoid promising coverage, payment, retroactivity, or a specific service change from an administrative submission.

Reconcile overlapping and amended periods

Link prior, amended, replacement, and overlapping records instead of overwriting one row. Compare effective dates, units, frequency, service, provider, location, modifiers, and any superseding language. Identify which visits were released under which evidence and preserve payer instructions. If the new document conflicts with the current schedule, hold affected future visits while the responsible roles resolve the exact configuration.

Owner authorization-calendar questions

  • Does every row describe one member, product, entity, provider, location, service, and period configuration?
  • Are preparation, submission, payer decision, scheduling, claim, and payment states distinct?
  • Do lead-time rules work backward from current requirements and internal clinical work?
  • Are remaining units and quantities calculated from reconciled source evidence?
  • Does each uncertain or expiring row have a hold, continuity owner, family update, and next date?
  • Can amendments and overlapping periods be traced without losing the earlier version?

An expiring-period example

An authorization ends September 30, and the next request was received by the payer on September 12. The portal shows pending, while the current schedule contains October visits. The calendar keeps the existing period, pending request, and future visits linked but separate. Operations applies the approved hold date, and the family receives an update that distinguishes submitted from approved without promising retroactive coverage.

On September 28, an amended document arrives with a different location and unit amount. The payer owner verifies the configuration, the clinical owner reviews any relevant continuity question, and affected October visits remain held until the released schedule matches the current evidence. The prior document and earlier communications stay available for reconciliation.

Related resources

Sources