← Back to Insights
SOAP notesdocumentationtemplatesprivate practice

How to Write SOAP Notes: A Therapist Workflow and Example

Use a practical SOAP-note workflow, a fictional annotated example, and a review checklist. Learn where typed-input AI drafting fits and what clinicians must verify.

Founder, Therapy Companion
· 5 min read

To write a SOAP note, organize the client's report, your observations, your clinical interpretation, and the next steps under four headings. A repeatable structure can make drafting easier to organize; the final record still needs to reflect the encounter and your professional judgment.

This guide offers a workflow and a fictional structure example. It does not promise a five-minute note, a particular word count, or an insurance outcome.

Who wrote this: I'm Kamal Grewal, founder of Therapy Companion. This is a vendor-authored workflow guide, not a clinical review of an individual record. Use your practice's documentation standards, supervision where applicable, and the relevant payer requirements.

What belongs in each SOAP section?

SectionPurposeDrafting prompt
SubjectiveInformation reported by the client or another identified sourceWhat did the person report, and whose account is it?
ObjectiveRelevant observations and measured informationWhat did you observe or measure, and what is the source?
AssessmentYour interpretation of the available informationHow does this encounter relate to the clinical picture and care goals?
PlanThe next stepsWhat was agreed, ordered, referred, or planned, and who will follow up?

For general documentation background, OpenStax explains the SOAP structure. The St. Cloud VA social-work student handbook, pages 19–21, also emphasizes distinguishing observations from interpretation and checking information. These are educational references, not universal payer templates.

A practical drafting and review workflow

1. Start with the encounter and the relevant care plan

Confirm the correct person, encounter, service date, and applicable template. Review the relevant goals and prior plan. Carry forward only information you have verified remains accurate; a previous note is context, not a substitute for today's record.

2. Organize the source information

Separate the person's report from what you observed. Identify interventions actually provided and the person's response. Keep source attribution clear when information came from a family member, another clinician, or an assessment rather than direct observation.

3. Draft under the four headings

Use the prompts above to place information. Preserve clinically relevant detail and remove duplication that does not help the record. Document the clinical reasoning yourself; a template cannot decide a diagnosis, establish risk status, or select treatment.

4. Review the complete record before signing

Check the draft against your source information and required encounter fields. Correct contradictions and unsupported statements. Follow your practice's completion and amendment process rather than treating a target number of minutes as the governing rule.

A fictional SOAP structure example

This short excerpt illustrates organization only. It is not a complete clinical or billable note. It omits encounter identifiers, diagnosis, a full assessment, applicable risk documentation, and other required fields. Do not copy it into a real record as evidence of an encounter.

S — Subjective: The client reported completing an agreed between-session activity once rather than three times and described difficulty fitting it around a changing work schedule.

O — Objective: During a structured review of barriers, the client identified two possible times for the activity and wrote down a reminder cue. The clinician reviewed the previous plan with the client.

A — Assessment: Follow-through on the agreed activity goal was partial. The client's report and planning discussion suggest scheduling is a barrier to explore further; the effect of the revised plan is not yet known.

P — Plan: The client and clinician agreed to try the revised schedule and review completion and barriers at the next scheduled appointment.

The separation matters: S attributes the report; O describes the observed work; A identifies an interpretation and its uncertainty; P records the agreed follow-up. A real assessment may require substantially more information. Do not infer an unassessed finding from this example or use a standard risk sentence to fill a gap.

Review questions before you sign

  • Does the note describe this encounter, with accurate dates and other required fields?
  • Can a reader distinguish reported information, observations, and your interpretation?
  • Are the interventions and responses described accurately, without invented details?
  • Does the record explain the relevant care goals, clinical reasoning, and next steps?
  • Have you resolved stale copied text, contradictions, and statements unsupported by the source information?
  • Have you met the applicable completion, signature, supervision, and payer requirements?

The medical-necessity documentation checklist offers additional review prompts and explains its limits. It summarizes selections; it does not inspect or approve a record.

For Medicare context, article A56937 distinguishes encounter documentation from information maintained across the record. The Medicare Program Integrity Manual, Chapter 3, explains template limitations and identifiable corrections or delayed entries. Review each source's scope and the policy that applies to the service.

Where AI drafting fits

In Therapy Companion's typed-note workflow, clinicians can draft from typed input, review and edit, and sign. The walkthrough explains the steps, prerequisites, and checks before moving from a draft to a signed record. Treat the output as a draft: check both additions and omissions against the source material. A polished sentence does not establish that an observation, intervention, or assessment occurred.

When evaluating a workflow, time the complete process: entering source information, generating a draft, checking it, editing, and signing. Compare similar encounters and keep the review standard consistent. The workweek calculator can help organize time assumptions; it does not establish how much a product will save.

To compare products, use the documentation scenario in the software evaluation checklist: enter a fictional written summary, inspect and edit the draft, save and reopen it, then review signing and later corrections.

Book a workflow demo to walk through those steps in Therapy Companion with fictional details. Bring the input method, note format, and review or supervision steps your practice needs. For data-handling questions, start with the security information and ask for the relevant agreements and current technical details.

FAQ

Can every SOAP note be finished in five minutes?

This guide does not promise a completion time. The session, required documentation, and review needs determine the work. Measure drafting and review together when evaluating a change to your workflow.

How long should a therapy SOAP note be?

Use the detail needed to document the encounter and meet applicable requirements. A fixed word count does not establish completeness, medical necessity, or payment eligibility.

Do insurance payers require SOAP format?

Check the specific payer and practice requirements. Do not assume SOAP is mandatory or preferred everywhere. The Medicare sources linked here address documentation content and review; the four headings alone do not establish compliance.

Can I reuse a SOAP template?

Reuse headings and prompts, then verify the content against the current encounter. Remove stale text and do not carry forward an assessment, risk statement, or intervention as though it occurred today.

What should I check in an AI-generated SOAP draft?

Compare the draft with your source information. Check who reported each fact, observations, interventions, clinical interpretation, the plan, and encounter details. Resolve unsupported or missing statements before signing.

Published by the Therapy Companion team · Data sources cited within the article. Analysis updated .