An ABA peer to peer review prior authorization workflow starts by confirming the decision, review window, eligible participants, criteria, and whether a formal appeal deadline continues to run. The clinician should bring a criterion-linked evidence packet, present the current case concisely, ask what remains unresolved, and document the call immediately. Obtain the outcome in writing and preserve every appeal, expedited-review, and continuity option named in the member's notice.

For BCBAs, clinical directors, ABA authorization teams, and practice operators. Sources checked August 13, 2026. External review by a BCBA medical-necessity reviewer and prior-auth appeals specialist is pending.

This workflow supports preparation and documentation. It does not determine coverage, replace the member's plan or notice, provide legal advice, change a clinician's independent judgment, or promise that a payer will approve the request.

Route the case before accepting the appointment

Peer-to-peer review (P2P) is a payer-defined clinical discussion about a utilization-review issue. It can occur before an adverse determination in one jurisdiction and after a denial in another plan. Its deadline, participants, evidence rules, and effect on other rights require direct verification.

Start with the complete notice, portal status, authorization record, member plan, current medical policy, request form, and call instructions. Record the notice date, receipt date, service and span affected, decision status, stated reason, criteria title and version, P2P request deadline, scheduled time, formal appeal deadline, expedited route, and any continuation-of-benefits instruction. Ask the payer to confirm each deadline and whether one process pauses another. Retain the reference number and written response.

Keep these routes distinct:

RoutePurposeControl to verifyPeer-to-peer reviewClinical discussion with a payer reviewer about the decision issue and supporting evidenceWhether it occurs before or after a decision, who may speak, records accepted, window, and written dispositionReconsiderationA plan-labeled re-review that may address authorization, clinical, administrative, or claim issuesExact definition, eligibility, deadline, evidence rules, and relationship to appealAppealFormal review of an adverse benefit determination under the member's plan or programWho owns the right, consent, filing method, deadline, review level, expedited pathway, and continuity rulesGrievanceA complaint route whose scope depends on program rulesWhether the issue concerns service, conduct, timing, quality, or another matter outside the adverse-benefit appeal

For Medicaid managed care organizations (MCOs), prepaid inpatient health plans (PIHPs), and prepaid ambulatory health plans (PAHPs), 42 CFR 438.400 defines an appeal as plan review of an adverse benefit determination and a grievance as dissatisfaction about another matter. That federal definition has a specific program scope. It does not define every commercial, Medicare Advantage, self-funded employer, or state process.

The CMS Prior Authorization API FAQ separates approval, denial with a specific reason, and a request for more information for defined impacted payers. Use that distinction to identify the actual case state. The federal API rule supplies no universal ABA P2P right or deadline.

Do not let an informal discussion consume a formal deadline. When the governing source does not clearly say a P2P or reconsideration pauses an appeal clock, manage both clocks and file the appropriate protective action with required consent.

Scope every public payer example before using it

Public payer pages can orient a team, yet a member-specific notice, benefit plan, contract, state rule, and live portal control the case. Record product, state, effective date, and source-check date beside every borrowed instruction.

Public sourceProduct and state scopeDate scopeSafe useUnitedHealthcare provider appeal pageNames Medicare Advantage including D-SNP, Community Plan Medicaid, and commercial members; P2P availability is limited to UnitedHealthcare-managed prior authorizations; timing varies by plan and statePage shows 2026 copyright but no policy effective date; checked August 13, 2026Use as orientation, then follow the case notice and Participation Agreement. The page gives several timing descriptions, including “most” requests within 24 hours and separate inpatient and outpatient windows, so no single number should be copied into another case.Aetna dispute overviewGeneral Aetna educational page; product and state are unspecifiedPublished September 22, 2025; checked August 13, 2026Supports the general sequence of a clinical discussion before appeal and notes that an appeal on a patient's behalf can require consent. It cannot set a case deadline or establish ABA-specific criteria.Texas Department of Insurance FAQTexas utilization review under the cited Insurance Code and rules; exact health-plan jurisdiction still requires confirmationLast updated September 2, 2025; checked August 13, 2026Shows that Texas can require an opportunity to discuss the treatment plan with a Texas-licensed physician of the same or similar specialty before an adverse determination. Confirm that the member's product and review entity fall within the rule.

The current UnitedHealthcare page, Aetna overview, and Texas regulator FAQ support only the scoped statements above. A payer's general website cannot resolve missing product, jurisdiction, or effective-date facts.

Confirm participants, reviewer identity, and discussion scope

Before scheduling, ask who may request and attend. Some processes require the treating or ordering clinician; others permit a clinician with specific credentials or an authorized representative. Confirm whether a BCBA may participate, whether another licensed professional must lead, whether the member's authorization or consent is needed, and whether the payer accepts added documents during or after the call.

Request the reviewer information the process permits: name, professional discipline, licensure, specialty or relevant experience, role in the original decision, and authority during the call. Ask which policy, plan provision, utilization criteria, and version were applied. If the payer cannot disclose an item orally, request the applicable written record and log the request.

Define the call boundary in advance:

  • Is the decision pending, issued, partially approved, reduced, terminated, or returned for information?
  • What exact service, quantity, date range, provider, setting, or clinical criterion is disputed?
  • Can the reviewer consider new records, and by what deadline and channel?
  • Can the reviewer change the decision, recommend another review, or only explain the rationale?
  • How long is the appointment, who can join, and what identity verification is required?
  • Will the payer issue a written result, when, and where will it appear?

A P2P cannot safely resolve eligibility, benefit exclusions, provider contracting, claim payment, or an administrative return unless the plan expressly includes that issue. Route each separate problem to its proper owner while preserving the clinical-review clock.

Build one evidence packet around the disputed criterion

The packet should help the reviewer find the current clinical facts without searching through an undifferentiated record. Keep the original submission, later additions, and corrections separately labeled.

Packet componentWhat to prepareClinical ownerDecision recordFull notice, criteria, policy version, prior request, payer questions, and authorization historyPrior-auth specialist verifies completenessCurrent clinical pictureAssessment dates, functional needs, baseline, active goals, risks, preferences, assent or participation considerations when relevantBCBA verifies accuracy and scopeProgress and treatment exposureGoal-level data, measurement periods, sessions or units delivered, cancellations, graphs, response patterns, and limits of interpretationBCBA explains numerator, denominator, and missing dataBarriers and modificationsBarriers observed, dates, treatment-integrity information, protocol changes, coordination, and response after changesTreating clinician distinguishes evidence from inferenceRequested servicesExact service lines, units or hours, frequency, dates, setting, provider role, goal linkage, and calculation worksheetBCBA owns recommendation; authorization specialist checks transcriptionAlternatives consideredClinically appropriate options actually considered, why they were or were not selected, and the reassessment planBCBA documents individualized reasoningContinuity and follow-upCurrent authorization end, scheduled care, safety planning, family communication, next review, and appeal routeClinical and authorization owners divide responsibilities

The BACB ethics resources identify the current codes governing certificants. Apply the relevant requirements for accurate records, data-based decisions, confidentiality, delegated work, and truthful communication. The public CASP ABA Practice Guidelines page describes guidance for ABA assessment, treatment planning, implementation, and evaluation. The full guideline is licensed. Neither source supplies a payer's coverage criterion.

Reconcile codes, quantities, dates, goals, setting, provider identity, signatures, and document versions before the call. A strong oral presentation cannot cure an unresolved packet conflict.

Present the case in five minutes and keep a question log

Use this fillable script as a rehearsal aid. Replace every bracketed field with verified information. Preserve the clinician's own language and judgment.

Identity and request: “I am [name, credential, role] calling about authorization [reference]. We requested [service, quantity, dates, setting]. The current decision status is [status].” Decision issue: “The notice dated [date] identifies [reason] under [policy or criterion, version or effective date]. Is that the complete issue for today's review?” Current clinical facts: “The current assessment and treatment plan show [brief functional needs and active goals]. During [measurement period], the client received [actual treatment exposure], with [concise progress pattern] and these interpretation limits: [missing data or confounders].” Barriers and response: “Documented barriers were [barriers]. The team changed [clinician-approved modification] on [date], and the record since then shows [observed result without overstating causation].” Requested services and alternatives: “The BCBA recommends [exact request] because [criterion-linked rationale]. The team considered [actual alternatives], with [reason and reassessment condition].” Close: “Which criterion remains unresolved? What evidence can be considered in this route? Please confirm the current decision, added-information deadline, written-outcome date, reference number, and next review or appeal step.”

Assign a second team member to maintain the question log when permitted. If only the clinician may attend, prepare the log in advance.

QuestionAnswer to capture verbatim in substanceFollow-up evidenceWhat exact issue remains?Criterion, missing fact, conflict, or decision rationaleSource title, version, section, and reviewer explanationWhat evidence was reviewed?Named documents and datesCompare with the locked submission inventoryWhat was unavailable or unpersuasive?Specific missing item or interpretationOwner, response channel, and due dateCan added information be considered now?Yes, no, or another route requiredSubmission instructions and confirmation methodWhat is the current decision status?Pending, upheld, modified, withdrawn, or another payer termWritten notice and effective dateWhat comes next?Appeal, reconsideration, another clinical review, or no further P2PDeadline, consent, address or portal, and expedited option

Use the ABA peer to peer review prior authorization script to organize facts, never to coach a clinician toward unsupported statements. Say when an answer is unknown. Commit to follow-up after checking the source record.

Synthetic case: separate a clinical question from a packet gap

This fictional scenario uses an invented payer, plan, state, criteria, deadlines, and client. It teaches workflow and predicts no outcome.

Example Health Plan in Example State issues a partial adverse decision for Client A's concurrent request. The BCBA requested 15 hours per week for 12 weeks. The notice authorizes 8 and says the packet does not connect variable goal progress with the requested intensity. The fictional notice offers a P2P within three business days and a formal appeal within 30 calendar days, with no statement that the P2P pauses the appeal clock.

The team finds that the treatment plan contains goal graphs, yet the cover narrative omits actual treatment exposure. Over the review period, 68 percent of scheduled direct hours occurred because of illness, staffing interruptions, and family-scheduled absences. The BCBA also changed one protocol four weeks before submission. Those facts affect interpretation of a flat trend, though they do not establish that the requested intensity is covered or clinically correct.

For the call, the BCBA brings the notice, fictional criterion, delivered-versus-scheduled table, goal graphs, protocol-change date, current functional evidence, requested-service calculation, and alternatives actually considered. The opening request is specific: review the 15-hour recommendation using the corrected exposure denominator and dated protocol information.

The reviewer confirms the intensity rationale is the only clinical issue, asks for the calculation worksheet, and says the written outcome will follow after document review. No oral approval is given. The authorization specialist sends the requested file through the confirmed channel, saves the receipt, continues to track the 30-day fictional appeal deadline, and requests the written determination. If the plan does not resolve the issue, the team uses the notice to route the next formal step.

Document the call and require a written outcome

Create a contemporaneous note immediately after the discussion. Include date and time, participants, identity verification, reviewer name and disclosed credentials, case reference, decision status entering the call, criteria discussed, evidence cited, questions and substantive answers, documents requested, commitments, due dates, oral disposition, written-outcome channel, appeal deadline, and next owner. Mark which statements came from the payer and which are the practice's interpretation.

Ask for the complete written outcome even when the reviewer gives an oral indication. Verify service, quantity, dates, setting, provider, effective date, conditions, and appeal rights. If the portal, letter, and call conflict, preserve each record and seek written clarification. Avoid scheduling, billing, or communicating coverage as final based solely on an ambiguous call.

For Medicaid managed care within 42 CFR Part 438, section 438.404 requires a written adverse-benefit notice to explain the determination, reasons, access to relevant documents and criteria, appeal procedures, expedited circumstances, and continuation information. Section 438.402 gives an enrollee 60 calendar days from the notice date to request a plan appeal and allows provider action on the enrollee's behalf only under its stated state-law and written-consent conditions. Section 438.408 governs appeal resolution and notice. Apply these rules only to their covered entities and current state implementation.

Protect privacy throughout. Verify recipients, use approved communication channels, avoid discussing other clients, and send only the information needed for the authorized purpose and payer requirement. HHS explains the general minimum-necessary standard and its scope in its HIPAA Privacy Rule guidance. Follow the organization's privacy determination for the specific payment or healthcare-operations activity. Recording a call requires advance review of payer policy, participant consent, applicable law, storage, access, and retention.

Run the before, during, and after checklist

Before the call

  • [ ] Save the full notice, criteria, plan documents, portal status, and original packet.
  • [ ] Confirm decision status, P2P deadline, appeal deadline, expedited route, and continuity instructions.
  • [ ] Verify who may attend, required credentials, consent, reviewer role, call length, and added-document rules.
  • [ ] Reconcile services, units, dates, providers, setting, goals, signatures, and calculations.
  • [ ] Prepare the evidence packet, five-minute script, question log, and secure workspace.

During the call

  • [ ] Verify identities, case reference, decision issue, criteria, and scope.
  • [ ] Present current facts, progress, treatment exposure, barriers, modifications, request, and alternatives concisely.
  • [ ] Ask which issue remains, what evidence may be added, and what the reviewer can decide.
  • [ ] Capture document requests, due dates, oral status, reference number, written-outcome timing, and next route.

After the call

  • [ ] Finish the contemporaneous note and separate payer statements from practice interpretation.
  • [ ] Send permitted documents through the confirmed channel and retain a readable receipt.
  • [ ] Obtain and audit the written outcome against the service request and oral discussion.
  • [ ] Notify the authorized care team and family using accurate coverage language and privacy controls.
  • [ ] File or preserve appeal, expedited-review, grievance, and continuity actions before their controlling deadlines.

Escalate when the notice is missing, criteria cannot be obtained, the reviewer lacks the required scope, the call cannot address the stated issue, participation rules exclude the treating clinician, an oral statement conflicts with the written record, or timing could affect care. A qualified clinical, authorization, compliance, or legal professional should address the part within that person's authority.

Evaluate pre-submission gap review separately

Peer-to-peer preparation often exposes earlier packet controls worth reviewing: policy version, missing records, cross-document conflicts, unit calculations, and deadline fields. Evaluate any technology against your current payer sources, human-review workflow, privacy requirements, and validation evidence.

To explore the product for future requests, See how Finni AI Prior Auths organizes likely review gaps before submission. Confirm current capabilities and fit for your organization during the evaluation. The product CTA makes no claim about this P2P outcome.

Related resources

Sources