Prior authorization notes need more than a standard progress note
A prior authorization support note is written for a specific purpose: to help a payer decide whether a requested behavioral health service meets its requirements for coverage. It is not the same as a routine SOAP, DAP, BIRP, or GIRP progress note, although those notes often provide the clinical evidence behind the request.
For therapists, counselors, psychologists, psychiatrists, social workers, and other behavioral health professionals, prior authorization documentation often comes up around services such as psychological testing, intensive outpatient services, extended sessions, higher-frequency therapy, continued care, medication-related services, or treatment that requires payer review before it is delivered or continued.
The challenge is that payer requests usually require a different writing style than normal clinical notes. A strong support note connects diagnosis, symptoms, functional impairment, treatment history, risk factors, client response, and the requested service. It should be specific enough for review while still protecting the client’s privacy and staying clinically relevant.
This article gives you a copyable prior authorization support note template, a filled example, format comparisons, AI-assisted documentation guidance, privacy considerations, and a practical review checklist. Use it as a starting point, then adjust it to the client, payer requirements, service type, and your clinical judgment.
What a prior authorization support note should accomplish
A prior authorization support note should answer the payer’s main question: why is this service medically necessary for this client at this time? The note should not read like a general therapy summary. It should give the reviewer enough information to understand the clinical rationale for the request.
Most support notes need to cover five areas:
- The requested service: Name the service, level of care, session frequency, duration, CPT or HCPCS code when applicable, and requested date range.
- The clinical reason: Connect the request to symptoms, diagnosis, risk, impairment, or treatment needs.
- Treatment history: Summarize what has already been tried, what helped, what did not, and why the requested service is appropriate now.
- Functional impact: Describe how symptoms affect work, school, relationships, daily living, safety, or self-care.
Supporting documentation can include recent progress notes, assessments, treatment plans, screening scores, discharge summaries, medication history, or referral information. The exact requirements vary by payer and service, so the support note should match the request form or portal fields whenever possible.
Copyable prior authorization support note template
Use the template below as a structured starting point. Replace bracketed text with client-specific information. Keep the language clinically precise, factual, and tied to the service being requested.
Prior authorization support note template
Client: [Client initials or name, based on practice policy]
Date of birth: [DOB]
Date of request: [Date]
Provider: [Clinician name, credentials, NPI if required]
Payer/member information: [Insurance plan, member ID, authorization portal reference number if available]
Requested service: [Service name, CPT/HCPCS code if applicable, frequency, duration, requested start date, requested end date]
Diagnosis and presenting concerns: [List current diagnosis or diagnoses and summarize current symptoms. Include duration, severity, and relevant changes since the last review or start of treatment.]
Medical necessity rationale: [Explain why the requested service is clinically indicated. Connect symptoms and impairment to the requested service. Describe why a lower level of care, shorter duration, or less frequent service would not meet the client’s current needs, if applicable.]
Functional impairment: [Describe how symptoms affect daily functioning, relationships, work, school, parenting, sleep, self-care, emotional regulation, safety, or other relevant domains.]
Treatment history and response: [Summarize prior services, interventions used, attendance, client response, progress, barriers, and remaining treatment needs. Include recent progress toward treatment plan goals.]
Risk and protective factors: [Document current risk factors, safety concerns, protective factors, safety planning, or crisis resources as clinically relevant.]
Requested authorization period: [Number of sessions, date range, frequency, level of care, or units requested.]
Supporting documents attached: [Progress notes, treatment plan, assessment scores, psychological testing referral, discharge summary, medication list, prior authorization form, or other payer-requested documents.]
Clinician attestation: Based on my clinical assessment and the client’s current presentation, the requested service is clinically indicated to address the symptoms, impairment, and treatment goals described above.
Clinician signature and credentials: [Name, credentials, date]
Filled example for a behavioral health authorization request
The example below uses fictional details. It shows how a clinician might support a request for continued individual therapy. Payer requirements differ, so this example should be adapted before use.
Example: Continued individual therapy authorization
Client: J.R.
Date of birth: 04/15/1992
Date of request: 08/12/2026
Provider: Maya Thompson, LCSW
Requested service: Individual psychotherapy, CPT 90837, one 60-minute session weekly for 12 weeks
Diagnosis and presenting concerns: J.R. is receiving treatment for generalized anxiety disorder and recurrent major depressive disorder, moderate. Current symptoms include persistent worry, difficulty concentrating, sleep disruption, low motivation, social withdrawal, irritability, and periodic tearfulness. Symptoms have increased over the past six weeks following a job transition and family stressors.
Medical necessity rationale: Continued weekly therapy is requested to address ongoing anxiety and depressive symptoms that are impairing work performance, sleep, emotional regulation, and interpersonal functioning. The client has made partial progress with cognitive restructuring, grounding skills, behavioral activation, and problem-solving interventions, but symptoms remain clinically significant. Reducing session frequency at this time may limit treatment continuity while the client is working on stabilization, coping skill use, and relapse prevention.
Functional impairment: J.R. reports difficulty completing work tasks due to rumination and reduced concentration. The client has missed two workdays in the past month due to anxiety-related sleep disruption and fatigue. J.R. also reports decreased social contact and increased conflict with a partner related to irritability and avoidance.
Treatment history and response: The client has attended eight sessions over the past ten weeks. Interventions have included CBT-based thought monitoring, behavioral activation, mindfulness-based grounding, sleep hygiene planning, and communication skills practice. J.R. reports improved ability to identify anxious thoughts and use grounding skills, but continues to experience high symptom intensity during work-related stress. Continued treatment will focus on reducing avoidance, improving emotion regulation, strengthening coping skills, and tracking progress toward treatment plan goals.
Risk and protective factors: J.R. denies current suicidal ideation, intent, or plan. Protective factors include engagement in treatment, supportive partner, stable housing, and willingness to use coping strategies. A safety plan was reviewed due to history of passive suicidal ideation more than one year ago.
Requested authorization period: 12 weekly sessions from 08/19/2026 through 11/11/2026.
Supporting documents attached: Updated treatment plan, most recent progress note, intake assessment, and symptom screening scores.
How prior authorization support notes differ from SOAP, DAP, BIRP, and GIRP notes
Most clinicians already document the information needed for authorization somewhere in the chart. The problem is that standard progress note formats are designed for clinical recordkeeping, not payer review. A support note pulls the most relevant clinical details into a payer-facing structure.
| Format | Best used for | How it relates to authorization |
|---|---|---|
| SOAP note | Subjective report, objective observations, assessment, and plan | Useful for showing symptoms, clinical assessment, and next steps, but may need added medical necessity language. |
| DAP note | Data, assessment, and plan | Good for concise clinical updates. The authorization note may need more detail about impairment and requested service. |
| BIRP note | Behavior, intervention, response, and plan | Helpful for showing interventions and client response. Add diagnosis, treatment history, and payer-specific request details. |
| GIRP note | Goal, intervention, response, and plan | Useful for connecting services to treatment plan goals. Add medical necessity and authorization period. |
| Prior authorization support note | Payer review of requested or continued services | Best for linking symptoms, impairment, service request, treatment response, and supporting documents in one place. |
A progress note says what happened in a session. A prior authorization support note explains why the requested service is needed. That difference matters. For example, “client practiced grounding skills” may be appropriate in a session note, while an authorization note may need: “continued weekly therapy is requested because panic symptoms remain frequent, interfere with work attendance, and require ongoing skills training and monitoring.”
Clinical details that strengthen a support note
Prior authorization documentation should be specific without becoming excessive. Long notes are not always better. A reviewer needs a clear line from the client’s condition to the requested service.
Diagnosis and symptom severity
List the current diagnosis or diagnoses and describe symptoms in plain clinical terms. Include frequency, severity, duration, and recent changes. If the request is for continued care, explain what remains unresolved and what treatment is targeting next.
Functional impairment
Functional impairment is often the missing piece in weak authorization notes. Describe how symptoms affect daily life. Examples include missed work, school avoidance, panic episodes while driving, difficulty completing hygiene tasks, disrupted sleep, parenting strain, withdrawal from relationships, or impaired concentration.
Treatment history and response
Include enough history to show why the request fits the client’s needs. Mention prior therapy, medication management, group treatment, hospitalization, assessment results, crisis episodes, or lower levels of care if relevant. For ongoing therapy, describe interventions used and the client’s response.
Requested service and time period
State exactly what is being requested. “Therapy” is too vague for many payer reviews. A stronger request might read: “Individual psychotherapy, CPT 90834, weekly for eight sessions from 09/01/2026 through 10/27/2026.” If a code is uncertain, confirm it with your billing process before submission.
Common mistakes that can delay payer review
Many prior authorization problems come from missing details rather than poor clinical care. A note can be clinically sound but still fail to answer the payer’s specific question.
- Using only a progress note: A routine session note may not state the authorization period, requested units, or medical necessity rationale.
- Leaving out functional impairment: Symptoms should be connected to real effects on the client’s life.
- Submitting vague service requests: Include service type, code if required, frequency, duration, and date range.
- Copying the same rationale for every request: Repeated generic language can weaken the note and may not reflect current clinical need.
Another frequent issue is sending more documentation than needed. Include payer-requested attachments, but avoid unnecessary detail that does not support the request. If a form asks for recent treatment response, answer that directly instead of attaching several months of unrelated notes.
How AI-assisted notes can help with prior authorization documentation
AI-assisted documentation can give clinicians a faster starting point for support notes. It should not decide medical necessity, create unsupported claims, or replace the clinician’s review. The clinician remains responsible for checking accuracy, editing the draft, and finalizing the record.
For prior authorization work, AI can be useful when it is given structured clinical input. For example, a clinician might enter the requested service, diagnosis, symptom summary, functional impairment, recent interventions, client response, and payer requirements. The AI can then organize those details into a cleaner draft.
That draft still needs clinical review. The provider should check that:
- The diagnosis, symptoms, and treatment history match the chart.
- The requested service is stated correctly.
- The language does not overstate risk, impairment, or expected outcomes.
- The note includes only relevant client information.
Generic AI writing tools may produce polished text that is not clinically appropriate. Behavioral health documentation requires attention to interventions, client response, treatment plan goals, risk language, and payer requirements. A note that sounds fluent can still be incomplete or inaccurate.
How AutoNotes supports prior authorization note drafting
AutoNotes is built for behavioral health documentation, not general business writing. Clinicians can use it to create structured, editable drafts for services such as individual therapy, group therapy, intakes, assessments, treatment planning, and documentation related to authorization support.
For a prior authorization support note, AutoNotes can help organize the details clinicians already have:
- Service-specific structure: Drafts can follow a format that includes requested service, diagnosis, clinical rationale, impairment, treatment history, response, and next steps.
- Editable clinical language: The output is a draft, so the clinician can revise phrasing, add missing details, remove unnecessary information, and align the note with payer requirements.
- Consistency across requests: Templates help clinicians avoid skipping key fields such as authorization period, supporting documents, and treatment plan connection.
- Less after-hours writing: Starting from a structured draft can reduce the time spent rebuilding the same note format after a full clinical day.
AutoNotes does not remove the need for clinical judgment. It gives the clinician a more organized starting point. The provider reviews the draft, confirms that it matches the record, edits it for accuracy, and finalizes it according to practice policy.
Privacy and clinician review before submission
Prior authorization requests often require sensitive behavioral health information. The goal is to provide enough information to support the request while avoiding unnecessary disclosure. Before submitting a support note, review what the payer asked for and remove details that do not help explain medical necessity.
Clinicians should pay close attention to:
- Minimum necessary information: Include relevant symptoms, impairment, diagnosis, treatment response, and requested service details.
- Client identifiers: Use the identifiers required by the payer or practice policy. Avoid adding extra personal details when they are not needed.
- Risk language: Make sure risk statements are current, accurate, and consistent with the chart.
- Third-party details: Be careful with names or details about family members, partners, employers, or other people.
If your practice uses AI-assisted documentation, confirm that your workflow follows your privacy, security, consent, and recordkeeping policies. The safest approach is to treat every AI-generated note as an editable draft that must be reviewed before it enters the clinical record or is sent to a payer.
Prior authorization support note checklist
Use this checklist before submitting the request. It can also be built into a documentation template so the same review happens every time.
- Requested service is clearly named, with code, frequency, duration, units, and date range when required.
- Diagnosis and current symptoms are documented accurately.
- Medical necessity rationale connects the client’s presentation to the requested service.
- Functional impairment is described with specific examples.
After those core items are complete, review the supporting materials:
- Treatment history and client response are included.
- Progress toward treatment plan goals is addressed.
- Risk and protective factors are current and clinically appropriate.
- Required attachments are included and match the payer request.
Before final submission, confirm that the note is signed, dated, and consistent with the chart. If your practice has billing staff, an administrator, or a compliance lead, follow the internal review process for payer submissions.
Practical wording examples for common authorization situations
The language below can help you avoid vague phrases. Adapt each example to the client’s actual presentation and payer requirements.
Continued therapy
Less specific: Client needs more therapy to continue working on anxiety.
More specific: Continued weekly psychotherapy is requested due to ongoing panic symptoms, avoidance of work-related tasks, sleep disruption, and partial response to CBT-based interventions. Treatment will continue to target panic management, cognitive restructuring, exposure planning, and relapse prevention.
Psychological testing
Less specific: Testing is needed to clarify diagnosis.
More specific: Psychological testing is requested to clarify diagnostic questions related to attention, mood, and executive functioning. Current symptoms are interfering with academic performance and daily organization, and prior clinical interviews and screening tools have not provided enough information to guide treatment planning.
Higher level of care
Less specific: Client needs more support than outpatient therapy.
More specific: A higher level of care is requested due to increased symptom severity, reduced ability to complete daily responsibilities, limited response to weekly outpatient therapy, and need for more frequent monitoring and skills practice. The client remains engaged in treatment and is willing to participate in the recommended service.
Frequently asked questions about prior authorization support notes
What is a prior authorization support note?
A prior authorization support note is a clinical document that explains why a requested service is medically necessary. It usually includes the requested service, diagnosis, symptoms, impairment, treatment history, client response, and supporting documents.
Is a prior authorization support note the same as a progress note?
No. A progress note documents a specific clinical encounter. A prior authorization support note explains the rationale for a requested or continued service. Progress notes may support the request, but they often do not include every payer-required detail.
What should therapists include in a prior authorization note?
Include the service being requested, CPT or HCPCS code if required, diagnosis, symptoms, functional impairment, treatment history, response to interventions, treatment plan connection, requested date range, and relevant attachments.
Can AI write a prior authorization support note?
AI can help create an organized draft from clinician-provided details. The clinician should review, edit, and finalize the note. AI should not make the medical necessity decision or add facts that are not in the clinical record.
How can I make the note stronger without making it too long?
Focus on the direct link between the client’s symptoms, impairment, treatment history, and requested service. Use specific examples, such as missed work, sleep disruption, school avoidance, or difficulty completing daily tasks.
What if the payer denies the request?
Follow the payer’s appeal or reconsideration process. Review the denial reason, gather missing clinical information, and revise the rationale if appropriate. Some practices involve billing staff, supervisors, or compliance personnel in this step.
How often should prior authorization templates be updated?
Review templates whenever payer requirements change, new services are added, codes are updated, or your practice changes its documentation workflow. A template should support current practice rather than create extra editing work.
Build a faster prior authorization documentation workflow
A good prior authorization support note is clear, specific, and clinically grounded. It explains the requested service, why it is needed, how the client is affected, what has already been tried, and what documentation supports the request.
AutoNotes helps behavioral health professionals create structured, editable drafts for documentation tasks like progress notes, treatment planning, assessments, and authorization support. You stay in control of the final note while spending less time starting from a blank page.
Start your free trial to create your first AI-assisted clinical documentation draft and see how AutoNotes fits your practice workflow.
