How to Track an ABA Prior Authorization Request as a Family

Create a request identity

Record the member and product, provider entity, clinician when relevant, service, setting, requested units or frequency, requested dates, diagnosis or referral only as needed, and whether the request is assessment, initial treatment, continuation, or change. Use one row per distinct request. A reference number from the provider may differ from the payer's reference. Keep both. Confirm which payer or delegated organization actually makes the decision and where status questions belong.

Use clear request states

Define drafted, awaiting clinical approval, submitted, received, matched, incomplete, complete, under review, additional information requested, responded, approved, partly approved, denied, withdrawn, expired, and superseded. HealthCare.gov describes preauthorization as a plan decision that may be required before service and says it is not a coverage-cost promise. Ask which state the payer itself reports. A provider portal saying sent does not prove payer receipt or completeness.

Keep clinical authorship with the clinician

A qualified clinician should own the assessment, recommendation, risk discussion, and clinical response to a request for more information. Operations may assemble, transmit, and track the packet. For covered behavior analysts, the BACB Ethics Code addresses competence, assessment, client involvement, documentation, and accuracy. Families can supply priorities and history while avoiding pressure to write clinical rationale or alter facts to fit a payer rule.

Track every information request

Record what the payer asked for, source, received time, due date, responsible person, response, transmission evidence, payer acknowledgment, and whether the request became complete. Ask whether the review clock paused or changed under the actual plan rules. If the request seems unrelated or duplicative, ask for the governing source and route it through the provider's payer team. Send purpose-needed information through an authorized secure route. Keep a copy of what was actually submitted.

Read the decision notice line by line

Compare approved or denied service, units, frequency, dates, provider, site, conditions, rationale, and review or appeal instructions with the request. A partial approval needs its own clinical and family review. HealthCare.gov defines an appeal as a request to review a denied benefit or payment. The specific plan notice supplies the available route and deadline. Ask the provider how the decision affects scheduling and whether a corrected administrative request or clinical appeal is contemplated.

A fictional authorization register

Mina's provider requests an assessment authorization. Seven states are due before scheduling: clinician approval, submission, payer receipt, completeness, review, written decision, and provider implementation. Five are complete. Review is active and the decision is pending, so progress is 5 of 7 states. The family records the payer reference and next status date. It does not count the provider's tentative appointment as authorized or ask the clinician to begin before the applicable service gates clear.

Know when federal employer-plan guidance applies

The DOL benefit-claim guide explains claim and appeal procedures for ERISA-covered health plans, including denial-notice content and plan-specific timing. Its rules do not govern every Medicaid, Medicare, governmental, church, or individual plan. Ask the plan administrator or qualified benefits adviser what framework applies. Use the actual plan documents and decision notice rather than borrowing a deadline from another coverage type.

Connect the decision to start readiness

After approval, confirm provider and site network or enrollment state, assigned qualified staff, supervision, consent, access supports, safe setting, schedule, and the exact first service. Ask when the authorization appears in the provider's system. Track unused days when staffing is delayed. If dates or units no longer fit the clinical plan, route the issue before service. Authorization supports one gate; it does not prove service delivery, claim acceptance, adjudication, or payment.

Use a concise status request

Ask: What exact request is this? Who decides it? When and how was it submitted? What payer reference exists? Is it received and complete? Is more information due? Which clock applies? What is the next action, owner, and date? Has a written decision issued? What does it authorize? What remains before scheduling? A consistent request produces comparable updates and reduces repeated disclosure of clinical details.

Trace one authorization request from clinical approval through implementation

Create an authorization event register for one exact request. Record the member and product, request type, service, provider, site, units or frequency, requested dates, and qualified clinical author. Add the packet version, submission route, transmission time, sender, payer or delegate, receipt, reference number, completeness state, reviewer, information requests, responses, and written decision. Keep the provider's internal identifier beside the payer's identifier without assuming they are interchangeable.

Follow every handoff. Clinical approval is different from administrative assembly. Transmission is different from payer receipt. Receipt is different from completeness. Completeness is different from review. A decision is different from the provider loading the authorization into scheduling and billing systems. Record what evidence moves the request to the next state and who is responsible. If the payer asks for more information, preserve the original question, the qualified author's response, the transmission proof, and the payer's confirmation that the response was matched to the request.

When the notice arrives, compare it with the request line by line. Record approved, partly approved, or denied service, provider, site, dates, units, conditions, rationale, and review rights. Route clinical differences to the clinician and administrative discrepancies to the appropriate payer or provider team.

Use a release gate and a written fallback

Release scheduling only when the request identity is correct, the clinical content was approved by the qualified author, the packet reached the permitted route, receipt and completeness are known, the written decision covers the proposed service, and the provider has implemented it. Also recheck assigned staff, supervision, consent, communication access, safe setting, and the actual appointment. Authorization does not replace those gates.

If the request is incomplete, delayed, partly approved, or denied, preserve the deadline and choose the right path. The response may be an administrative correction, new request, clinical appeal, expedited review, adjusted start plan, or continuity discussion. The family should know which path is active, who owns it, what can occur meanwhile, and which costs or delays remain possible.

Verify one complete real-world cycle

Follow the first scheduled service and first claim under the authorization. Match date, service, provider, site, units, authorization identifier, claim, acknowledgment, EOB, and ledger. A decision that never reaches the provider's scheduling or claim configuration is not fully implemented. Record any mismatch as a new event tied to the same request so the family can see the complete chain rather than a series of isolated status calls.

Use a status script that forces each request state into the open

A useful status inquiry names the request before asking for progress: “I am checking the initial assessment request for this member, provider, site, requested dates, and service.” Ask whether the payer has received it, matched it to the member, and marked it complete. Request the payer reference, current state, last state-change date, reviewer or department, outstanding item, decision target, and next contact date. If the person says “pending,” ask which defined state that word represents. Pending receipt, pending records, and pending clinical review call for different action.

Compare the payer response with the provider register while both are fresh. If the provider has transmission proof and the payer has no request, verify the destination, identifiers, and whether a delegate receives the product's requests. If the payer reports missing information, compare the exact item with what was sent and preserve the qualified author's version. If the provider says approval was received, request the written notice and confirm service, provider, site, dates, and units. The responsible teams interpret clinical criteria and repair provider packets. The family can make discrepancies visible and ask those teams to reconcile them.

Set a contact rhythm tied to real events. Follow up after the stated receipt window, information-response deadline, or decision date rather than calling daily without a new question. Escalate sooner when an urgent clinical situation, expiring service, formal deadline, or unexplained lost request creates harm. Record unsuccessful contacts and accessible communication needs. Once a decision is issued, send the provider the notice through an authorized route and ask when its systems will reflect the result. The status log then becomes evidence of both payer decision and operational implementation.

Give the family a status view without exposing the whole packet

A family-facing tracker can show the request identity, current state, last update, next action, owner, target date, and decision result without displaying every clinical attachment. Use plain labels such as “payer confirmed receipt” or “clinician responding to one information request.” Explain whether a date is a payer target, contractual deadline, provider estimate, or family reminder. That distinction helps families plan without treating an estimate as a guarantee.

Provide a way to report an identity error, inaccessible notice, or changed appointment. Tell the family whom to contact for clinical questions and whom to contact for payer status. When information is missing, describe the category and owner rather than blaming the family. After the decision, give an accessible copy of the notice when permitted and explain what still must happen before service. The tracker should reduce repeated calls while preserving the family's ability to challenge an inaccurate or stagnant state.