ABA booking lead time is the elapsed time from a defined schedule-ready event to an accepted, released booking. A useful report fixes the cohort, start and end events, time zone, maturity cutoff, pauses, exclusions, sources, and segments before calculating results. People who remain unbooked stay visible with current age, and the metric never substitutes for clinical readiness, payer approval, access, or client choice.

Define the start event

Choose a reproducible event such as every required gate completed and the client entering schedule-ready state. Record its timestamp, source, owner, and configuration. Avoid starting from inquiry when the question is booking operations because upstream clinical and payer time would be mixed in. The CASP Organizational Guidelines public overview supplies high-level operations context; this metric is an editorial design.

Create one record for the reporting clock

A booking lead-time record should include the person or request ID, readiness event, readiness timestamp, timezone, service, setting, modality, geography, requested time bands, access needs, payer route, assigned owner, first accepted booking, release timestamp, pauses, exclusions, and current state. Store the exact source for every timestamp.

Use a stable request ID when an offer is rescheduled. Otherwise, the practice may accidentally reset the clock and make lead time look shorter. If the service, modality, or readiness basis changes materially, close the original request with a documented disposition and open a linked request under the new definition.

Define the booking event

End the clock when the person accepts a specific date, time, service, provider configuration, location, and modality and the visit is released. Keep offer sent, delivered, accepted, scheduled, and released as separate timestamps.

Write pause and exclusion rules before measuring

Pauses should represent a real interval in which the practice cannot reasonably advance the booking under the chosen metric. Examples may include a client-requested future start or a documented temporary unavailability. Internal backlog, missing staff, repeated failed outreach, or waiting for a routine approval usually remain part of the elapsed experience unless the report is deliberately designed to isolate another process.

Every pause needs a start event, end event, reason, source, and authority. Report gross elapsed time and paused time separately before calculating any net measure. Exclusions should be rare, source-based, and visible by count and reason. A record that stays open at the cutoff is an open observation, not an exclusion.

Preserve payer meaning

HealthCare.gov cautions that preauthorization does not promise cost coverage. The schedule-ready state should reference current payer evidence while preserving authorization, booking, claim, adjudication, and payment as separate outcomes.

Choose a maturity rule that fits the promise

A seven-day service standard cannot be fairly calculated for a request that became ready yesterday. Lock the cohort to requests whose readiness date gives them the full seven-day opportunity by the report cutoff. Then report three views:

  • mature standard attainment: mature requests booked within seven days divided by mature requests
  • current open aging: all open requests grouped by age, including immature requests
  • original-cohort disposition: booked, withdrawn, changed, referred, or still open for every request in the cohort

This keeps immature cases from depressing the standard rate while ensuring they remain visible to operations.

Report open records

Use medians, ranges, percentiles, and age buckets alongside averages. Show unbooked people at the cutoff and explain any valid pause. Segment by service, setting, time band, geography, access support, payer route, and workflow version only when cohorts remain interpretable.

Calculate durations consistently

Choose calendar hours, business hours, or business days and define holidays and cutoffs. Convert every timestamp to the reporting timezone before subtraction. For calendar time, lead time is the released-booking timestamp minus the schedule-ready timestamp. For business-time reporting, preserve the raw timestamps and use a reviewed business calendar rather than subtracting weekends by hand.

An average can hide a long tail. Report the median, 75th or 90th percentile when the cohort is large enough, minimum and maximum, and the number still open. Very small segments should be shown as counts and individual ages instead of unstable percentages.

A fictional cohort

Seventeen people enter schedule-ready state during June. Twelve accept a released visit within seven days, three accept later, and two remain unbooked at cutoff. Seven-day booking is 12 of 17, or 70.6%. The two open records remain in original-cohort reporting.

Read the fictional result accurately

The 70.6% figure answers one question: how many of the 17 ready requests reached a released booking within seven days. It does not say that 70.6% of inquiries received care or that booking caused service to begin. A second metric, booked by cutoff, is 15 of 17, or 88.2%. The two open requests have individual ages and next actions.

If either open record had entered readiness less than seven days before cutoff, the seven-day mature denominator would need a prewritten adjustment. The original 17-request cohort would still remain visible. The team should also report whether accepted bookings were later canceled, changed, or never delivered.

Use the report carefully

Investigate capacity, offer design, inaccessible channels, client preferences, travel, staff fit, and workflow delay. Lead time cannot establish quality or family satisfaction. Track accepted offers, reversals, service starts, and open age beside the duration.

Use a weekly operating view and a monthly learning view

The weekly view should list each open request, age, current dependency, next action, owner, and risk. The monthly view can compare mature cohorts, service types, time bands, workflow versions, and recurring failure reasons. Avoid public promises until the practice has enough stable history to support them.

When lead time worsens, inspect the stage where time accumulates before adding capacity. The problem may be sparse after-school availability, slow clinical assignment, inaccessible outreach, unstable staff configurations, or a release process that rechecks the same evidence. Record the chosen intervention and compare the next mature cohort using the same definition.

Limits of the lead-time report

Booking lead time measures elapsed process time for the defined cohort. It cannot establish clinical readiness, service quality, payer coverage, equitable access, client satisfaction or whether a booked visit was delivered. Open records, small segments, changed definitions and disputed timestamps can materially affect results. A target derived from one service or period should not become a public promise without stable evidence and qualified review. Keep client choice, access failures, cancellations, service starts and unresolved dependencies visible beside the duration.

Owner lead-time questions

Before comparing periods, ask whether the start event, booked event, pause rules, maturity cutoff, and open-record treatment stayed the same. Review the oldest open requests alongside the median and percentile results so completed cases do not hide current delay. Segment administrative waiting, family choice, clinical review, payer action, staffing, setting, and access work without assigning blame beyond the evidence.

When the number improves, confirm that visits were actually viable and delivered rather than booked early and corrected later. Pair lead time with change-after-booking, cancellation, family clarity, and service-start measures. Faster booking is useful only when the exact configuration remains workable.

Related resources

Sources