Behavioral Health Prior Authorization Checklist: From Intake to Decision
A practical behavioral health prior authorization checklist for collecting benefits, payer criteria, clinical evidence, submission proof, and follow-up dates.

On this page: Direct answer
Direct answer
Behavioral health prior authorization checklist: what operators need to know
A practical behavioral health prior authorization checklist for collecting benefits, payer criteria, clinical evidence, submission proof, and follow-up dates. Verify both active coverage and service-level behavioral health benefits before assembling the packet. Capture the exact service, units, dates, rendering provider, facility, and request type in a single case record.
A reliable prior authorization process starts before anyone opens a payer portal. The team needs to know what is being requested, which benefit and policy govern it, what evidence is required, who owns each task, and when the next action is due.
Use this checklist as an operational control, not as a substitute for the member's plan document, payer policy, clinical judgment, or state-specific rule. Requirements vary by payer, line of business, service, diagnosis, site of care, and provider contract.
Key takeaways
The short version
- Verify both active coverage and service-level behavioral health benefits before assembling the packet.
- Capture the exact service, units, dates, rendering provider, facility, and request type in a single case record.
- Translate payer criteria into a visible evidence map instead of attaching an undifferentiated chart export.
- Save submission confirmation, reference numbers, and the payer's stated decision deadline.
- Assign the next action and escalate before the deadline, not after a patient or clinician asks for status.
1. Lock the request before you collect documents
Write a one-sentence request definition: member, requested service, level of care, units or visits, date range, rendering provider, servicing location, and whether the request is standard, expedited, initial, or a continuation. If any element is uncertain, route it for clarification before the submission clock starts.
Match names, dates of birth, member IDs, NPIs, tax IDs, and facility identifiers across the referral, EHR, eligibility response, order, and form. Small identity mismatches create avoidable pends and make later follow-up harder to reconcile.
- Member demographics and current insurance card
- Subscriber relationship and coordination-of-benefits information
- Ordering, referring, rendering, and billing provider identifiers
- Requested CPT/HCPCS codes, modifiers, units, place of service, and date range
- Routine versus urgent/expedited rationale and the clinical owner who approved that classification
2. Verify the benefit and the authorization rule
An active eligibility response does not prove that the requested behavioral health service is covered or that prior authorization is unnecessary. Confirm the product, network, carve-out administrator, deductible and cost share when available, visit or unit limits, referral rules, authorization trigger, and the correct submission channel.
Record the source and timestamp for every requirement. If the portal, policy PDF, and representative disagree, preserve all three and escalate rather than silently choosing the most convenient answer.
| Control | What to capture | Why it matters |
|---|---|---|
| Coverage | Effective dates, product, network, carve-out | Routes the request to the right entity |
| Service rule | Code, units, threshold, level of care | Defines whether authorization is required |
| Submission | Portal, fax, API, phone, form version | Prevents wrong-channel rejection |
| Timing | Standard/expedited clock and follow-up date | Creates an actionable queue |
3. Build an evidence map, not a document pile
List each payer criterion in one column and point to the chart fact, assessment, plan, or other record that addresses it in the next. Mark missing items explicitly. This lets a clinician close the smallest real evidence gap without rewriting an entire note.
Typical evidence may include diagnosis and functional impairment, symptom severity and duration, risk and safety information, prior treatment and response, current treatment plan, measurable goals, frequency and duration, medication history when relevant, caregiver or school context when allowed, and discharge or step-down planning. Include only what the request and policy require.

4. Submit with a reproducible audit trail
- 01
Run a preflight check
Confirm identifiers, requested codes, dates, signatures, attachments, form version, and file readability.
- 02
Send through the required channel
Use the payer-designated portal, transaction, fax, or phone workflow and note any outage or fallback.
- 03
Capture proof
Save the confirmation page or transmission result, reference number, timestamp, channel, and submitting staff member.
- 04
Set the payer clock
Record the payer-stated due date and create an earlier internal follow-up date with an owner.
- 05
Communicate the status
Share a concise status with the clinical and scheduling teams without exposing unnecessary information.
5. Normalize every response into a next action
Do not leave the result trapped in a portal inbox or fax queue. Classify it as approved, partially approved, pending additional information, administratively closed, or denied. Capture approved units and dates exactly; for pends and denials, preserve the payer's language and map it to the missing requirement or appeal path.
A closed authorization still needs ownership. Calendar the end date, remaining-unit threshold, next clinical review, and reauthorization lead time. The final field in every case should be a dated next action, even when the current answer is approval.
Common questions
Answers before you build.
What information is usually needed for a behavioral health prior authorization?+
Most workflows require accurate member and provider identifiers, the requested service and units, relevant payer criteria, focused clinical evidence, and a complete submission record. The exact requirements depend on the payer, plan, service, and jurisdiction.
Does active eligibility mean prior authorization is not required?+
No. Eligibility indicates coverage status, while authorization rules are service specific. Verify the behavioral health benefit, network, carve-out, and authorization requirement separately.
Should a team send the full clinical chart?+
Not by default. Use the payer's request and policy to build a focused evidence packet, and apply applicable privacy and minimum-necessary controls.
What should be tracked after submission?+
Track the reference number, submission timestamp and channel, payer due date, internal follow-up date, owner, status, requests for additional information, and the final determination.
Practical closeout
Use this operator checklist.
- Verify both active coverage and service-level behavioral health benefits before assembling the packet.
- Capture the exact service, units, dates, rendering provider, facility, and request type in a single case record.
- Translate payer criteria into a visible evidence map instead of attaching an undifferentiated chart export.
- Save submission confirmation, reference numbers, and the payer's stated decision deadline.
- Assign the next action and escalate before the deadline, not after a patient or clinician asks for status.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on July 22, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesCurrent implementation dates, decision timeframes, denial-reason requirements, metrics, and API provisions for impacted payers.Accessed or rechecked July 22, 2026
- 02Health Plan Eligibility Benefit Inquiry and Response Centers for Medicare & Medicaid ServicesOfficial overview of the HIPAA-adopted X12 270/271 eligibility and benefit transaction.Accessed or rechecked July 22, 2026
- 03Minimum Necessary Requirement U.S. Department of Health and Human ServicesHIPAA guidance on limiting uses, disclosures, and requests for protected health information when the standard applies.Accessed or rechecked July 22, 2026
- 04Disclosures for Treatment, Payment, and Health Care Operations U.S. Department of Health and Human ServicesHIPAA guidance relevant to payment operations, role-based access, and the minimum-necessary standard.Accessed or rechecked July 22, 2026
- 05Electronic Prior Authorization Centers for Medicare & Medicaid ServicesCurrent CMS provider-readiness guidance for 2027 electronic prior authorization, EHR questions, FHIR testing, and workflow preparation.Accessed or rechecked July 22, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
July 22, 2026
Initial publication, source review, and operational editing.