From First Session to Defensible Documentation: A Supervisee Playbook

Different EHRs divide the encounter into different boxes, but the clinical reasoning underneath the record should remain coherent. A strong chart lets another qualified clinician understand why care began, what condition or problem is being treated, how the condition affects functioning, what skilled intervention occurred, how the person responded, what changed, what remains, and what happens next.

Use this longitudinal golden thread across the episode: WHY NOW → Symptoms and FIDO → Functional Impairment → Diagnostic Formulation → Functional Treatment Goals → Measurable Objectives → Skilled Interventions → Response → Behavioral Implementation → Measured Progress or Lack of Progress → Remaining Impairment → Medical Necessity → Next Clinical Direction → Review, Titration, Transition, or Discharge.

• Truth outranks template completion. Never manufacture a finding merely because the EHR contains a box for it.
• The source is the factual ceiling. Separate what the person reported, what the clinician observed, what the clinician did, what was clinically assessed, and what is planned.
• The treatment plan is the roadmap, but each progress note documents the clinical route actually taken during that encounter.
• A session topic is not automatically a treatment target. Connect the topic to symptoms, functioning, an active objective, treatment response, or another clinically meaningful reason before treating it as progress-note content.
• Insight is not the same as behavioral implementation, and behavioral implementation is not automatically the same as functional improvement.

A new clinician should not enter an intake trying to remember every possible question. Enter knowing the purpose of the encounter, the required form, the safety pathway, and the minimum clinical decisions that need to be made. The sequence below is an operational teaching example, not a substitute for the practice's intake policy.

• Confirm the encounter type, referral reason, scheduled format, and the exact intake form or documentation style that must be completed.
• Verify required consent, privacy, telehealth, financial, and practice documents according to the organization's workflow; do not assume a signed portal form replaces a required verbal discussion.
• Know how to reach the supervisor or designated backup and know the emergency, safeguarding, and after-hours pathways before the session begins.
• For telehealth, know the organization's requirements for current location, callback information, emergency contacts, and disconnection procedures before they are needed.
• Review only the information necessary for this individual. Do not preload another person's diagnosis, risk history, goals, language, or prior template content.
• Know whether a standardized measure is expected before the encounter and how the result is supposed to inform clinical discussion rather than merely satisfy a checkbox.

The time blocks below show one way to organize a typical extended intake. Actual length, billing, workflow, and sequencing vary. The clinician can move between domains naturally; the goal is to leave the encounter with enough supported information to formulate the presentation safely and accurately.

• Opening minutes — welcome the person, identify your role, complete any required associate/supervision disclosure, orient to confidentiality and its limits, confirm telehealth/emergency logistics when applicable, and invite questions.
• Early agenda — ask what made now the right time to seek support and what would make the conversation useful. This establishes WHY NOW and the person's priorities before the clinician begins filling diagnostic categories.
• Presenting problem — clarify the main symptoms, stressors, changes, and functional consequences. Follow the person's story while quietly organizing frequency, intensity, duration, and onset.
• Focused history — gather only the psychiatric, treatment, medical/medication, substance, trauma, developmental, family, social, cultural, occupational, educational, legal, and support information needed by the active intake and current clinical question.
• Safety — ask direct, developmentally and culturally appropriate questions about suicide, self-harm, violence/homicide, acute vulnerability, and other relevant safety concerns. Expand the assessment when a positive or ambiguous response requires it.
• Synthesis — review the mental status findings actually observed or assessed, reconcile symptoms with course and impairment, consider differential explanations, and determine whether the available evidence supports a diagnosis, a provisional formulation, or further assessment.
• Collaborative close — summarize what you heard, check accuracy, identify initial functional goals, explain the recommended next step, confirm follow-up, and review safety or referral instructions when indicated.

Scripts should sound human and should be adapted to the clinician's jurisdiction, license status, employer policy, consent documents, client age, and service setting. The examples below demonstrate content and cadence; they are not universal legal wording.

• Role and supervision example: “Before we get into what brought you in, I want to make sure my role is clear. I am practicing in an associate role under clinical supervision. My supervisor and I may review aspects of my clinical work as part of that supervision. I can answer questions about how that works before we continue.”
• Confidentiality example: “What you share is generally private within the rules that apply to this service. There are specific situations where I may need to disclose information for safety or as required by law. I want you to know those limits before we begin, and you can ask questions at any point.”
• Agenda example: “We have a few things I need to understand today, but I do not want the form to run the conversation. I would like to start with what made now the time to reach out and what you most want help with.”
• Risk segue example: “I ask direct safety questions because they help me understand what support is needed, not because I am assuming anything about you.”
• Diagnosis discussion example: “I am organizing what you have described into a clinical formulation. I want the diagnosis to reflect the pattern accurately, so I may continue clarifying the timeline and how this affects your functioning rather than forcing a label too early.”

FIDO is a practical way to clarify symptom course without writing four artificial paragraphs. Integrate it naturally into the interview and record only what was actually assessed. It helps a supervisee move from vague descriptions such as “anxious a lot” to information that can support diagnosis, treatment planning, and later measurement.

• F — Frequency: How often does the symptom, behavior, or pattern occur? What proportion of days, situations, or triggers are affected?
• I — Intensity: How severe is it, how difficult is it to control, and how much does it interfere with functioning?
• D — Duration: How long do episodes last, how persistent is the pattern, and how long has the current level of difficulty been present?
• O — Onset: When did it begin, recur, worsen, or most recently change? What was happening around that time?
• Always pair symptom description with functional impact: what the person cannot do, avoids, delays, performs inconsistently, performs only with disproportionate effort, or experiences differently in relationships because of the condition.

Fictional training example only. No real person is represented.

• Weak: “Client has anxiety and trouble sleeping.”
• Stronger: “Fictional adult reports worry on most days for approximately three months following a major role change, with episodes escalating several evenings per week and commonly lasting one to two hours. Worry is described as difficult to disengage from and is associated with delayed sleep onset, reduced concentration the following morning, repeated reassurance seeking, and avoidance of nonessential work tasks.”
• Why stronger: the second version gives course, FIDO, context, and impairment without inventing a diagnosis. The same variables can be reassessed later to show improvement, stability, or deterioration.

A diagnosis should not appear because the form requires a code. It should be the best-supported clinical formulation available at that point in the episode. When the evidence is incomplete, document the supported formulation and use supervision or further assessment rather than manufacturing criteria.

• Step 1 — WHY NOW: identify the current problem, precipitating event or change, and why intervention is clinically relevant now.
• Step 2 — Symptom pattern: organize symptoms by cluster and FIDO rather than by whichever diagnosis first comes to mind.
• Step 3 — Functional impairment: identify the individualized impact on work, school, relationships, parenting, sleep/routines, decision-making, self-care, social engagement, communication, emotional regulation, or other meaningful domains.
• Step 4 — Course and differential: examine duration, onset, stressor relationship, prior episodes, substances/medications/medical context, trauma, developmental factors, and competing diagnostic explanations. Rule-outs should reflect a real clinical question, not a list of every remotely possible diagnosis.
• Step 5 — Diagnostic rationale: connect symptoms → onset/course or stressor context → functional impairment → why the selected diagnosis fits better than the alternatives currently under consideration.

Fictional training example only. An adult reports three months of escalating worry, irritability, sleep-onset difficulty, and concentration problems after a substantial job-role change. Symptoms occur most days, interfere with task completion and relationships at home, and were not described at this intensity before the role change.

• Do not jump directly from “worry” to a chronic anxiety diagnosis. Clarify whether the pattern meets the required duration/course and whether symptoms remain primarily linked to the identifiable stressor.
• Ask whether similar episodes existed before the current role change, whether worry is generalized across domains, and whether mood, trauma, substance, medical, or medication factors better explain the presentation.
• If the evidence supports a stressor-linked diagnosis, the rationale should say why. If evidence for a more enduring disorder is emerging but incomplete, preserve the uncertainty and continue diagnostic assessment.
• The supervisor should be able to trace the selected diagnosis back to the actual interview rather than to generic diagnostic language pasted into the chart.

Risk documentation is assessed-only. Silence is not a denial, historical risk is not automatically current risk, and another person's suicidal behavior is not the client's own suicidal ideation. A risk score or screener can support assessment but does not replace clinical formulation.

• Screen directly for current suicidal ideation/death wish, self-harm thoughts or behavior, and homicidal/violent ideation when clinically required by the encounter and workflow.
• When positive, ambiguous, or clinically concerning, clarify frequency/recency, intent, plan, timing, access to means, preparatory behavior, controllability, prior attempts or self-injury, acute drivers, intoxication/psychosis/agitation when relevant, and the person's current ability to participate in a safe disposition.
• Identify protective factors only when they were actually assessed and are genuinely available now; do not copy them forward automatically.
• Formulate the concern using the actual findings and change from baseline rather than relying on an unexplained “low/moderate/high” label.
• Document the intervention actually completed: safety planning, means-safety work, support involvement, consultation, crisis referral, urgent evaluation, emergency activation, or another action.
• Make disposition and ownership explicit: why the selected level of response was appropriate, who owns the next step, when follow-up is expected, and what should trigger earlier escalation.
• Immediate safety action runs before documentation. Do not keep a person in danger waiting while trying to make the note complete.

The MSE is not a normal-findings template. Record what can reasonably be observed or assessed in the actual modality. An audio-only encounter cannot support visual appearance or eye-contact findings. A brief outpatient follow-up does not automatically justify a comprehensive cognitive examination.

• Common domains include appearance/grooming when visually observable, behavior/engagement, speech, reported mood, observed affect, thought process, relevant thought content, perception when assessed, orientation/cognition/attention/memory when supported, insight, judgment, and impulse control when reasonably assessed.
• Keep member report and clinician observation distinct: “reports feeling depressed” is not the same statement as “affect appeared constricted.”
• Risk findings belong in the risk section when the EHR separates them; do not duplicate the same safety narrative into every MSE field.
• Do not turn absence of discussion into a negative finding such as “no hallucinations” unless the domain was actually assessed or clearly observable in a way that supports the statement.

A useful treatment plan operationalizes the intake. Diagnosis, impairment, goals, objectives, interventions, measurement, medical necessity, and discharge criteria should read as one clinical story. The plan should not become a session-by-session history.

• Goal: describe a meaningful functional outcome. Example: “Improve ability to regulate anxiety sufficiently to complete routine work responsibilities without repeated avoidance.”
• Objective: define observable change. Example: “Use an agreed regulation strategy in at least four of five identified high-anxiety work situations for four consecutive weeks.”
• Intervention: describe skilled clinician work matched to the objective. Example: CBT-based identification of anticipatory thoughts, behavioral experiments, graded exposure to avoided tasks, and review of implementation barriers.
• Measurement: state how progress will be known—frequency, intensity, duration, percentage, count, sustained period, functional change, or a validated measure when clinically appropriate or program-required.
• Discharge/transition criteria: mirror the goals. Describe what independent functioning, sustained symptom management, reduced need for skilled intervention, or another clinically appropriate endpoint would look like.

Measurement-based care is useful when a measure becomes part of clinical reasoning. A score is not progress by itself and should not override the person's report, functioning, risk picture, or observable behavioral change.

• Establish a baseline using FIDO, individualized functional impairment, and validated measures when clinically indicated or required by the program/payer.
• At follow-up, compare like with like: the same symptom dimension, functional target, behavior, or standardized measure whenever possible.
• Reconcile score trajectory ↔ person report ↔ functioning ↔ treatment-goal progress ↔ clinical presentation.
• If the score improves but functioning does not, document the discrepancy and explore it. If functioning improves despite residual symptoms, document the functional gain rather than calling treatment unsuccessful.
• Use payer-specific instruments and completion thresholds only when they actually apply. Do not present one program's measurement rule as a universal clinical standard.

Once the intake and treatment plan establish the clinical foundation, each follow-up note should answer what continued, what changed, what the clinician did, how the person responded, what behavioral evidence demonstrates progress or continued difficulty, what impairment remains, why skilled treatment is still indicated, and what comes next.

• Do not repeat the entire intake in every note.
• Do not insert every treatment-plan goal into every session. Advance only the goals/objectives actually addressed or meaningfully affected by the encounter.
• Do not call discussion or insight “progress” unless there is evidence of learning, implementation, symptom change, functional change, stabilization, or another supported clinical outcome.
• Document interventions actually performed—not a standing list of modalities the clinician knows how to use.
• Document response to the intervention. “CBT provided” is incomplete if the note never shows what was targeted or how the person engaged/responded.
• Medical necessity should be individualized to the current condition, remaining impairment, incomplete implementation, clinical complexity, risk of deterioration/recurrence when supported, and need for skilled psychotherapy.

Use this style when the destination EHR presents a medical-record shell with brief encounter-orientation fields, a SOAP-like clinical note, and a separate patient-facing care-plan field. Preserve this exact order when this is the active architecture.

• 1. Chief Complaint — one concise statement explaining the encounter orientation or primary reason for treatment today.
• 2. Health Concerns — a brief summary/list of active behavioral-health domains; do not duplicate the Subjective narrative.
• 3. Subjective — current report, symptoms, relevant stressors, FIDO when useful, functional impact, coping, goal-related behavior, barriers, and safety information when assessed.
• 4. Objective — supported observations/MSE, clinician interventions actually performed, and response; include only what the encounter supports.
• 5. Assessment — diagnosis-anchored synthesis of clinical course, current impairment, treatment-plan progress, response/barriers, and individualized medical necessity. Do not repeat Subjective.
• 6. Plan — forward-looking treatment only: next focus, homework/behavioral work, monitoring, coordination/referrals, frequency when relevant, and safety follow-up when indicated.
• 7. Care Plan — brief, patient-facing, actionable language reflecting what the person can do between sessions; keep it distinct from the clinician-facing Assessment.

Fictional follow-up example only. Chief Complaint: “Psychotherapy follow-up for anxiety affecting work and sleep.” Health Concerns: “Anxiety, sleep disruption, work avoidance.” Subjective: “Fictional adult reports completing two previously avoided work tasks using the agreed task-start routine, while evening worry continues to delay sleep several nights per week.” Objective: “Clinician used cognitive restructuring and behavioral rehearsal to examine anticipatory predictions and practice a shorter task-initiation sequence; individual identified one prediction as inaccurate and rehearsed the revised sequence.” Assessment: “Anxiety remains functionally relevant through sleep disruption and avoidance, with early behavioral implementation demonstrated by completion of two previously delayed tasks. Continued skilled psychotherapy is indicated to consolidate independent use and address persistent anticipatory worry.” Plan: “Continue the task-initiation experiment, track evening worry duration, and review implementation barriers next session.” Care Plan: “Practice the shorter task-start routine during identified work tasks and track how long evening worry lasts on three nights before the next visit.”

Use this style when the EHR separates intake, formal treatment planning, progress notes, and termination, and the treatment plan is the primary longitudinal anchor. Do not force a medical-style shell into this architecture.

• Treatment plan field order: Diagnosis → Diagnostic Justification → Presenting Problem → Treatment Goal → Goal Description when the form includes it → Objective → Estimated Completion → Treatment Strategy / Intervention → repeat for each clinically meaningful goal → Discharge Criteria / Planning → Prescribed Frequency of Treatment.
• Diagnosis and Diagnostic Justification should remain aligned with the intake. The justification connects symptoms, course/stressor context, impairment, and diagnostic fit rather than copying textbook criteria.
• Presenting Problem should reinforce the active clinical pattern without becoming a duplicate intake.
• Each Treatment Goal should represent a distinct functional domain rather than restating the same concern three ways.
• Objectives should be measurable and fit within the authorized review period. Do not automatically impose another workflow's 90-day, 180-day, or annual interval.
• Treatment Strategy / Intervention should describe skilled work that can plausibly produce the objective—not a generic modality list.
• Progress notes should reference the active diagnosis and applicable treatment objectives, document actual intervention/response, and show whether progress, persistence, stabilization, regression, or barriers are occurring.
• Termination/discharge should summarize the supported treatment course and disposition. Administrative closure must not be rewritten as clinical recovery when no reassessment occurred.

Fictional training example only. Diagnosis: “Supported anxiety-related diagnosis selected after assessment.” Diagnostic Justification: “Fictional adult presents with a documented pattern of persistent worry, physiologic activation, sleep disruption, and avoidance that has impaired occupational task completion and relationship functioning; the course and differential assessment support the selected diagnosis.” Presenting Problem: “Worry and avoidance are interfering with timely work completion and evening recovery.” Treatment Goal 1: “Improve independent regulation of anxiety during work demands.” Goal Description: “Increase ability to initiate and complete routine responsibilities without repeated avoidance or reassurance seeking.” Objective 1.1: “Use the agreed task-initiation and regulation sequence in at least four of five identified situations for four consecutive weeks.” Estimated Completion: “Within the active plan period.” Treatment Strategy / Intervention: “CBT-based cognitive restructuring, behavioral experiments, graded practice, and review of implementation barriers.” Discharge Criteria / Planning: “Consider transition when gains are sustained across routine demands without the current level of skilled support and other active goals are sufficiently met.” Prescribed Frequency: “Per the clinically established plan and authorized workflow.”

Use this style when the EHR intake is a long questionnaire with many separate fields. The field separation is part of the architecture. Do not merge the questionnaire into SOAP, do not group multiple boxes into a narrative section, and do not append an Assessment/Plan unless the actual form includes one or a separate document is requested.

• Personal Information: Identifies As → Ethnicity/Cultural Identity field → Occupation → Education → Current/Prior Military Service → Individuals Present → Other Sources of Information.
• Intake Evaluation Summary: Presenting Problem → Symptoms/Behaviors and Onset → Frequency/Duration/Timing or Onset fields when present → CPT/service field when the form includes it.
• Risk / Critical Alerts: Current Safety Plan status → History of SI/SA → Current Self-Harming Behaviors → History of Self-Harming Behaviors → Current Homicidal Ideation/Plan/Intent → History of HI/HA → any additional active risk fields.
• History: Current or History of Traumatic Events → Behavioral Health History.
• Family Behavioral Health History: Paternal/Father side → Maternal/Mother side → Other.
• Social History / Support System: Family of Origin → Relationship Status → Social Support → Living Arrangements → Legal Issues → Other when present.
• Medical History: Last Annual Physical → Current Providers → Primary Care Provider → Psychiatrist → Other Specialists → Current Medications → Medical Problems → Chronic Conditions → Allergies when those fields are present.
• Family Psychosocial History: History → Cultural → Religious/Spiritual → Transportation when included.
• Substance Use — current fields stay separate: Current Use → Type → Amount → Frequency → Last Used → impact/history/treatment fields when present. Past-use fields remain separately documented in their own order.
• Personal Treatment Goals: Overall Goals → First Goal → Second Goal → Third Goal → Other when present.

Use this style when the platform may contain the same detailed intake questionnaire but also provides separate Risk Assessment, Biopsychosocial, and Mental Status modules. The modules remain distinct. Do not manufacture a SOAP note from the intake merely because the platform can generate narrative text.

• Intake questionnaire — preserve the exact questionnaire-style architecture described in Style C.
• Risk Assessment module — suicidal ideation/death wish → self-harm ideation/urge/behavior → homicidal/violent ideation → plan/intent/means or access/preparation/timing/imminence when relevant → history → protective factors actually identified → safety interventions actually completed → disposition/follow-up.
• Biopsychosocial module — biological/medical and medication context → psychological symptoms/course/history/trauma/coping/strengths/risk → social/family/cultural/spiritual/relational/work-school/legal/housing/transport/support domains → individualized functional impairment → formulation/recommendations only when requested and supported.
• Mental Status module — appearance/grooming only when observable → behavior/engagement → speech → reported mood and observed affect → thought process/content → perception when assessed → cognition/orientation/attention/memory when supported → insight/judgment/impulse control when reasonably assessed.
• The platform may make it easy to prefill normal findings; clinical governance still requires the clinician to confirm that the finding was actually assessed or observable.

Use this architecture when the clinical workflow requires a denser, explicitly longitudinal psychotherapy note with separate intervention, risk, treatment-progress, response, and medical-necessity fields. Preserve the exact order.

• 1. Subjective — current report, symptoms, FIDO when relevant, functioning, meaningful context, coping/implementation, progress/barriers, and safety content when assessed.
• 2. Objective: Mental Status Examination → Risk Assessment.
• 3. Clinical Interventions — specific skilled interventions actually completed, target/rationale, and supported response.
• 4. Assessment: Diagnosis → Clinical Course → Functional Impairment → Treatment Plan Progress → Response to Treatment → Medical Necessity.
• 5. Plan — next intervention direction, behavioral work, measurement follow-up, treatment frequency when relevant, coordination, and review/titration considerations when indicated.
• Clinical Review is a longitudinal synthesis rather than another progress note: compare initial versus current symptoms and impairment, measurement trajectory, risk trajectory, goal-by-goal progress, implementation/generalization, barriers, effectiveness, medical necessity, frequency/level-of-care fit, and readiness for revision or transition.
• Free-form/event notes document a real event or change; they should not duplicate the SOAP merely to create another entry.

The content can stay clinically consistent even when the destination boxes change. Fictional fact: a person used a previously practiced grounding strategy before a stressful meeting, completed the meeting without leaving early, and still experienced substantial anticipatory anxiety the night before.

• Medical-style EHR: Subjective carries the report; Objective carries the clinician intervention/review; Assessment identifies partial behavioral implementation with remaining impairment; Plan advances the next practice target; Care Plan gives the person's concrete between-session action.
• Treatment-plan-centered EHR: the progress note links the behavior to the applicable objective, states the intervention and response, and preserves the formal treatment-plan wording rather than rewriting the goal.
• Questionnaire-style intake: if this is an initial encounter, the fact belongs only in the specific current symptoms/functioning/goal fields that exist; do not create a follow-up SOAP inside the intake questionnaire.
• Modular platform: the same fact may inform biopsychosocial functioning or an intake field, while MSE and risk remain separate modules populated only by supported findings.
• Expanded governance SOAP: Treatment Plan Progress can explicitly distinguish successful implementation from persistent anticipatory anxiety and explain why continued skilled work remains indicated.

CMS and commercial payer requirements are not identical, and contracts change. The safest training approach is to teach a universal clinical core and then apply the specific payer/program overlay without allowing that overlay to rewrite the destination EHR or create unsupported facts.

• Record identity, date of service, responsible clinician/authorship, and signature/credentials in the manner required by the EHR and payer.
• Ensure the diagnosis/code is supported by the medical record and the billed service matches the service actually performed.
• When time affects coding or payment, document the required time element accurately; do not backfill a duration to fit a preferred code.
• Show the presenting problem/current symptoms and the person's current level of functioning or individualized impairment.
• Maintain a treatment plan with clinically meaningful, measurable goals and interventions matched to the active problems.
• For psychotherapy encounters, show the focus of treatment, skilled intervention, response/progress or continued difficulty, future direction, and follow-up as required by the applicable payer/workflow.
• Maintain chronological, legible, internally consistent records that support medical necessity and continuity of care.
• Treat payer manuals as contract-specific overlays. If a current contract, state Medicaid requirement, Medicare contractor policy, or program standard is more specific, follow the applicable requirement rather than a generic training example.

For Medicare psychotherapy coding, current CMS guidance identifies 90832 as 16–37 minutes, 90834 as 38–52 minutes, and 90837 as 53 minutes or more. When time is relevant for coding/payment, CMS permits documentation by start/stop times or total time. Other payers may apply their own policies, so the claim and record should be reconciled to the applicable contract and the service actually performed.

• Do not stretch a note to imply a longer service than occurred.
• Do not assume the diagnostic-evaluation workflow follows the psychotherapy time bands; diagnostic evaluation is a different service category.
• The narrative should support what was clinically done, while the time field supports the timed service when required.
• A longer note is not proof of medical necessity. Clinical specificity, functional relevance, skilled intervention, response, and appropriate treatment direction matter more than documentation volume.

Supervision is where uncertainty becomes explicit clinical reasoning. In California, supervision includes monitoring and evaluating assessment, diagnosis, and treatment decisions and reviewing treatment records as appropriate. The practical habit is to bring a focused decision question rather than only retelling the case.

• State the clinical question: “I am deciding between these formulations,” “I am unsure whether this risk finding changes disposition,” or “I cannot connect this proposed goal to an impairment.”
• Bring the relevant facts and what is missing—not every detail in the chart.
• State what you already considered or tried and how the person responded.
• Offer your proposed next step and identify exactly what makes you uncertain.
• Flag live deadlines: the person is still on the call, a report may be required, a referral is waiting, or the disposition cannot safely wait until scheduled supervision.
• Document consultation when it materially changes assessment, diagnosis, intervention, disposition, reporting, or follow-up according to practice policy.

• Correct person/episode; no cross-record contamination.
• Requested EHR style and exact field order preserved.
• Presenting problem and WHY NOW are clinically clear.
• Symptoms are individualized and sufficiently measurable; FIDO used when clinically useful.
• Functional impairment is explicit and not exaggerated.
• Diagnosis is supported by course, impairment, and differential reasoning; no diagnostic drift.
• Risk language reflects only what was actually assessed; current and historical risk are not conflated.
• MSE contains supported observations only and fits the encounter modality.
• Treatment goals arise from impairment and objectives are observable/measurable.
• Interventions are skilled, specific, actually performed, and matched to active objectives.
• Response/progress distinguishes insight, implementation, and functional outcome.
• Medical necessity is individualized and current rather than boilerplate.
• Plan follows the Assessment and identifies the next clinically supported direction.
• Billing/service/time documentation is consistent with the encounter and applicable payer rules.
• The final record contains no AI/process commentary, audit narration, unsupported certainty, or material that would be inappropriate in the permanent chart.

• Mistake: filling every blank with “denies.” Correction: a negative finding requires an actual assessment; unanswered is not the same as negative.
• Mistake: diagnosing from one symptom. Correction: formulate from pattern, course, impairment, context, exclusions, and differential fit.
• Mistake: “Client will learn three coping skills” as the goal. Correction: make the goal a functional outcome and place skill acquisition in measurable objectives/interventions.
• Mistake: listing CBT, MI, DBT, ACT, supportive therapy, and psychoeducation every session. Correction: document the interventions actually used and why they were used.
• Mistake: calling participation “progress.” Correction: identify behavioral implementation, symptom trajectory, functional change, stabilization, or the supported lack of progress.
• Mistake: rewriting the treatment goal to match today's conversation. Correction: preserve the approved goal and describe today's relationship to it.
• Mistake: copying the prior risk assessment forward. Correction: reassess what needs reassessment and document only current supported findings plus relevant history.
• Mistake: writing the same Assessment as Subjective. Correction: Assessment synthesizes diagnosis, course, impairment, treatment response, progress/barriers, and medical necessity.
• Mistake: putting supervisor/AI/audit commentary into the chart. Correction: permanent-record language only; governance and QA stay outside the clinical note unless the workflow specifically requires a consultation entry.

Fictional training case only. The person is an adult seeking care after a role transition, reporting persistent worry, sleep-onset difficulty, irritability, concentration problems, and avoidance that are affecting work completion and relationships. No diagnosis, risk finding, or history beyond what is explicitly stated here should be inferred.

• WHY NOW: symptoms intensified after the role transition and are now interfering with responsibilities and home functioning.
• FIDO: clarify how many days per week worry occurs, peak intensity/interference, episode duration, overall course, and exact onset/change point.
• Impairment: delayed work tasks, difficulty disengaging from work at night, sleep disruption, and increased conflict/reassurance seeking if actually reported.
• History: assess prior similar episodes, behavioral-health treatment, relevant medical/medication/substance factors, trauma and developmental context as required by the form, supports, and barriers.
• Risk: directly assess current and historical suicide/self-harm/violence domains and expand only as indicated; do not assume denial from this fictional prompt.
• MSE: document only what the actual encounter supports.
• Diagnosis: compare stressor-linked and enduring anxiety/mood formulations; select only the diagnosis currently supported and explain why.
• Plan: collaboratively identify a functional first target, establish measurement, select an intervention direction, and schedule/coordinate the next clinically appropriate step.
• Translation: place those same facts into Style A, B, C, D, or E without changing the clinical truth to satisfy the layout.

Before signing, ask one final question: could every sentence appropriately remain in the permanent medical record if reviewed by the person receiving care, another treating clinician, a supervisor, a payer auditor, a licensing board, or a court? If a sentence is unsupported, belongs to another person, describes the documentation process rather than the care, overstates what was assessed, or exists only to make the chart look complete, correct it before signing.