Authorization period

The period is one part of the approval

An authorization can include several independent limits:

• approved start and end dates, plus whether each boundary date is included
• service code, modifier, setting, modality, provider, group, or location
• total units for the period
• daily, weekly, monthly, or visit frequency limits
• approved assessment, treatment, caregiver-training, or supervision service
• conditions, exclusions, documentation duties, and review triggers

A plan might approve 480 units for a 12-week period while also limiting use to 40 units per week. The total balance cannot override the weekly ceiling. An approval for one service code supplies no units for another code. An approved provider at one location may have no valid route at a second site.

Dates, units, and frequency answer different questions

The period answers when the approval can apply. Authorized units answer how much of a defined service the payer approved. Frequency limits how quickly or in what pattern those units may be used. Expiration identifies when the approval ends by date or another stated circumstance.

Elapsed time and remaining units should appear separately. A family can reach the midpoint of a period with most units remaining because of illness, staffing, school, or choice. A practice can also approach a unit limit well before the end date. Both situations need clinical and operational review rather than automatic schedule compression.

The CMS Prior Authorization API FAQ says an impacted payer's API response must indicate whether a request is approved, and for how long, denied with a specific reason, or needs more information. The API requirement applies to defined payer classes and medical items and services excluding drugs, generally beginning January 1, 2027. It creates no universal ABA period length or unit convention.

Build one versioned authorization record

For every approval, capture:

1. member, payer, product, group, request, and authorization identifiers
2. decision source, issue date, source version, and staff verification date
3. exact start date, end date, time zone when relevant, and inclusivity rule
4. service code, modifier, units, frequency, setting, modality, provider, and location
5. requested values beside approved values
6. units delivered, claims submitted, units adjudicated, adjustments, and remaining balances
7. renewal requirements, submission window, owner, due date, and receipt evidence
8. change, denial, appeal, continuity, and escalation history

Keep the original decision artifact. A portal summary, phone note, authorization letter, payer roster, and contract may answer different questions. Record conflicts and obtain written clarification before releasing work that depends on the disputed field.

A fictional 12-week period

Inez receives an approval for 480 units of one ABA service from September 7 through November 29. The approval also states a maximum of 40 units per week. The practice verifies that both boundary dates are included for this payer and configuration.

After four complete weeks, 144 units have been delivered and documented. The unit ledger shows 480 − 144 = 336 units remaining. Period use is 144 of 480, or 30%. Four of the 12 weeks have elapsed, or 33.3%.

The remaining 336 units do not permit more than 40 units in a later week. At that maximum, the final eight weeks could use no more than 8 × 40 = 320 units. The unused 16 units expire unless the payer's current process supplies another valid path. The practice reports the projected shortfall instead of moving units across weeks silently.

This example describes authorization tracking. A qualified clinician decides the appropriate schedule within the person's needs, preferences, assent, risks, and available supports. The family can decline, pause, or change services. Authorization provides a ceiling rather than a prescribed dose.

Reauthorization and continuity need lead time

A reauthorization submission date differs from the expiration date. Filing a request usually leaves the current authorization unchanged unless the payer issues a written extension or governing rule provides continuation. A pending status has its own effect under the applicable product.

The CASP ABA Practice Guidelines Version 3.0 public summary places assessment, treatment planning, implementation, and evaluation within ABA behavioral health treatment for people diagnosed with autism. Detailed access requires a license. This article uses only that public scope to keep clinical review connected to authorization operations.

Set internal milestones for clinical review, family input, current data, order or referral when required, payer forms, submission, confirmation, and follow-up. Make the lead time specific to the payer and case. Immediate safety and urgent clinical needs use their own escalation routes.

Measure the full due cohort

Suppose 20 active authorization records reach a monthly audit date. Eighteen have verified dates, codes, units, frequency, provider, and location fields, so configuration completeness is 18 of 20, or 90%. Sixteen of those 18 also have a reauthorization or closeout task assigned by the internal due date, giving task readiness of 16 of 18, or 88.9%.

Keep the two incomplete records visible as holds. Track authorizations expiring within the chosen horizon, remaining units, projected capacity, pending decisions, late submissions, and confirmed extensions. Separate operational readiness from clinical appropriateness and family choice.