Requested units

Units translate a recommendation into a payer quantity

A unit is a reporting quantity defined by a code set and payer route. It may represent time, an encounter, a day, an assessment event, or another measure. Never assume every ABA code uses the same unit.

The requested amount should trace to a clinically supported service plan and an accurate calendar. Arithmetic cannot create medical necessity or clinical appropriateness.

Lock the code and unit convention

Use the licensed current code set and the payer’s current product-specific source. The CMS code-sets page explains the federal administrative-simplification role of adopted medical code sets. The page does not reproduce proprietary descriptors or decide one payer’s authorization rule.

Record the code, modifier, provider type, service setting, time increment, aggregation rule, rounding rule, and effective date. If the payer form calls a visit a unit while the claim code uses timed units, preserve both quantities and label them.

Build the calendar from actual dates

Identify the requested start and end dates, days per week, session length, and service-specific frequency. Count calendar occurrences rather than multiplying an average month. Review holidays, school breaks, planned closures, travel, caregiver availability, other services, and known staff constraints.

Do not subtract an absence that is merely possible. State assumptions and show how the total changes if they differ.

Use a transparent calculation

For a timed service, a general worksheet can show:

eligible sessions × minutes per session ÷ minutes per unit = requested units.

Apply the licensed code convention and payer’s aggregation or rounding method after calculating supported time. Different service dates or codes may need separate rows.

A fictional unit example

Noelle’s fictional clinician recommends a two-hour service three times per week for 12 weeks. The calendar contains 36 planned sessions. Two known closure dates remove two sessions, leaving 34 eligible sessions.

Assume the verified code and payer rule use 15-minute units. Each two-hour session contains eight units. The request is 34 sessions × 8 units = 272 units.

The packet also shows 68 service hours, the two excluded dates, provider type, setting, and the clinical rationale. If the payer authorizes 216 units, the team records 216 approved and 56 adverse. The original clinical recommendation remains 272 units unless the clinician separately changes it for clinical reasons.

Separate service categories

Assessment, direct treatment, caregiver guidance, protocol modification, group services, and supervision can have different codes, units, providers, and rules. Calculate each on its own row. Avoid using one service’s unused units for another.

If two services can occur on the same day, verify coding, authorization, and payer rules. A calendar overlap does not prove both are billable or clinically appropriate together.

Reconcile the numbers across the packet

The request form, treatment plan, schedule, calculation worksheet, clinical rationale, and portal should show consistent codes, dates, frequency, duration, and totals. Explain any difference, such as a form that requests visits while an attachment shows timed units.

Lock the final version and preserve the source inputs. A later correction should identify what changed, why, who approved it, and which submission it affects.

Use a release checklist

Before submission, verify the member and product, requested code and modifier, rendering role, service location, start and end dates, unit convention, session calendar, total, attachments, and submission channel. Compare the result with any portal field that rounds or caps the entered quantity. Save the value displayed after submission, because a portal may transform the input.

Give each held item a reason, owner, next action, and due date. Examples include a missing clinician decision, unresolved payer convention, provider-location mismatch, or calendar conflict. A deadline should trigger escalation, not silent guessing. When a payer representative clarifies a rule, record the date, channel, name or reference number, exact question, and answer. Written plan or portal evidence should replace a call note when available.

Include feasibility and burden

The clinician should consider the person’s priorities, other care, school or work, travel, rest, family time, communication access, health, and tolerance. Staff availability and supervision also affect feasibility.

Feasibility can prompt a clinical discussion. It should not cause administrative staff to cut a recommendation without clinician review. Authorized units are a coverage ceiling, not a mandate to deliver every unit.

Keep CMS policy in its lane

The CMS-0057-F final-rule page describes interoperability and prior-authorization requirements for impacted payers. Its scope stops short of defining one unit method or guaranteeing approval.

Useful measures include calculations with current source evidence, packets whose totals reconcile, corrections by reason, requested-to-approved units, and unused approved units by documented context. Never optimize approval percentages at the expense of clinical accuracy or person-centered care.