BeeThere Journal

Documentation workflow

How to Write Therapy Progress Notes Faster

A faster note is not a shorter memory dump. Use a repeatable workflow that captures the clinical thread, chooses a structure, drafts once, and performs a focused review.

BeeThere Editorial Team9 min read

Editorial note: This article is educational and does not provide legal, compliance, or clinical advice. Requirements differ by jurisdiction, license, payer, and practice. BeeThere does not currently claim clinical review of this article.

Therapy progress notes often take too long because the writer is making several decisions at once: remembering the session, deciding what is relevant, choosing a format, translating clinical thinking into concise language, and checking requirements.

A faster workflow separates those decisions. Capture a small set of anchors while the encounter is fresh, place each anchor into a consistent structure, draft once, and review against a short checklist. The aim is not the shortest possible note. The aim is a timely, accurate, useful note with no unnecessary narrative.

CMS’s Documentation Matters resources state that providers are responsible for documenting encounters completely, accurately, and on time, and that incomplete or inaccurate documentation can affect communication and outcomes. See the CMS Documentation Matters Toolkit. That makes speed valuable only when it preserves accuracy and clinical meaning.

Why a ten-minute note becomes a thirty-minute task

Documentation expands when the clinician starts with a blank page and an undefined target. Common time traps include:

  • replaying the entire session instead of identifying the clinical thread;
  • writing chronologically and then reorganizing;
  • switching between SOAP, DAP, and custom requirements from memory;
  • repeating the same facts across multiple sections;
  • searching for “clinical” wording after the content is already written;
  • documenting too much conversation detail out of fear of leaving something out; and
  • performing no review until the note is nearly complete.

The fix is a workflow with explicit stages. Each stage answers one kind of question.

The capture–structure–draft–review workflow

Step 1: Capture six clinical anchors

Immediately after the session—or during an approved workflow that does not interfere with care—capture six brief anchors:

  1. Focus: What treatment goal or clinically relevant problem did the session address?
  2. Evidence: What did the client report, and what did you observe?
  3. Intervention: What skilled action did you take?
  4. Response: How did the client participate or respond?
  5. Progress: What changed, did not change, or became clearer relative to the goal?
  6. Plan: What will the clinician and client do next?

These are fragments, not finished prose. For example:

Focus: avoidance in work meetings
Evidence: skipped one meeting; rapid speech when discussing presentation
Intervention: graded exposure hierarchy + rehearsal
Response: completed rehearsal; willingness 8/10
Progress: more insight; no real-world exposure yet
Plan: one low-stakes contribution; review next week

That small capture preserves the logic of the encounter. It also reduces the temptation to reconstruct every topic.

Step 2: Choose one structure

Match the captured anchors to the format required by your setting:

| Format | Where the six anchors go | | ------ | ------------------------------------------------------------------------------------- | | SOAP | Evidence in S/O; progress and formulation in A; next steps in P | | DAP | Evidence, intervention, and response in D; formulation/progress in A; next steps in P | | BIRP | Presentation in B; clinician action in I; response/progress in R; next steps in P | | GIRP | Focus in G; clinician action in I; response/progress in R; next steps in P | | Custom | Give each required element one defined home |

Do not let the acronym determine the clinical content. It is an organizing system. The same encounter should remain recognizable across formats even though information is grouped differently.

If you are still choosing a format, compare the free SOAP guide, DAP guide, BIRP guide, and GIRP guide.

Step 3: Draft each fact once

Repetition wastes time and weakens the note. Give each fact one primary job.

  • Client-reported experience establishes the subjective or data evidence.
  • Observable presentation establishes objective or behavioral evidence.
  • Intervention language establishes the skilled service.
  • Response language shows participation or immediate effect.
  • Assessment or progress language interprets what the evidence means.
  • Plan language states the next action.

An Assessment should not merely restate the client report. It should synthesize it: “Avoidance continues to maintain work-related anxiety; the client showed improved insight but has not yet tested the exposure plan outside session.”

Step 4: Run a focused review

Use a short sequence rather than rereading for everything at once:

  1. Facts: Is each statement true, supported, and correctly attributed?
  2. Clinical thread: Do focus, intervention, response, progress, and plan connect?
  3. Risk: Does the note accurately reflect what was assessed and what action was taken?
  4. Privacy: Can unnecessary sensitive detail be removed?
  5. Requirements: Are required fields, time, authentication, and other setting-specific elements complete?

This review is especially important for an AI-assisted draft. Fluency is not evidence.

Use section prompts that prevent rewriting

A section prompt should make the first draft closer to final by defining four things:

  1. Source: client report, observation, record review, or clinical synthesis;
  2. Scope: the clinically relevant content that belongs;
  3. Purpose: what decision or continuity need the section serves; and
  4. Guardrail: what the writer must not infer.

For example, a SOAP Objective prompt could read:

Document observable behavior, relevant mental-status findings, and therapeutic interventions provided during this encounter. Use factual language. Do not include client-reported experience unless clearly attributed, and do not add clinical interpretation.

A useful Assessment prompt could read:

Using only the documented report and observations, summarize symptom severity, functional impact, response to treatment, progress toward the named goal, and current barriers. Preserve uncertainty and do not add a diagnosis or risk finding that was not assessed.

These prompts reduce editing because they prevent information from landing in the wrong section. BeeThere’s therapy progress note template includes a format-neutral prompt set, while each format guide provides copyable prompts tailored to its sections.

Build a small library of precise clinical verbs

Clinicians often lose time searching for formal wording. A limited library of accurate verbs is more useful than decorative clinical language.

For interventions:

  • assessed, clarified, explored, reflected, summarized;
  • taught, modeled, rehearsed, practiced, reviewed;
  • challenged, reframed, identified, differentiated;
  • collaborated, planned, prioritized, coordinated; and
  • validated, normalized, reinforced.

For response:

  • reported, identified, demonstrated, practiced, completed;
  • engaged, participated, reflected, generated, applied;
  • had difficulty, required prompting, declined, questioned; and
  • showed increased, decreased, stable, partial, or no change.

Choose the verb that describes what happened. “Processed” and “supported” may be accurate, but they often need an object: what was processed, and how was support provided?

Avoid inflated phrasing. “The client demonstrated profound transformational insight” is rarely more useful than “The client identified the link between anticipatory thoughts and meeting avoidance.”

Write an honest progress statement

Progress is not always improvement. A clinically useful statement can document:

  • improvement;
  • partial progress;
  • stability;
  • no measurable change;
  • worsening symptoms;
  • a newly identified barrier;
  • improved engagement without symptom change; or
  • insufficient information to evaluate the goal.

Use a three-part pattern:

Status + evidence + implication

Examples:

  • “The client made partial progress toward the exposure goal, completing the in-session rehearsal but not yet attempting the task at work; continued graded practice is indicated.”
  • “Symptoms remained stable by client report, while improved recognition of escalation cues may support future skill use.”
  • “Progress could not be evaluated because the between-session measure was not completed; barriers to tracking will be reviewed next session.”

This is faster and more defensible than forcing every encounter into a success narrative.

Choose the right level of detail

CMS describes complete documentation as sufficient to identify the patient, support the condition, justify care, document the course and results, and promote continuity. Specific requirements depend on the service and setting. The CMS outpatient psychotherapy billing article includes examples of documentation elements such as time, interventions, progress toward goals, participation, and outcomes for covered services under that policy.

More detail is not automatically better. Use the “next clinician” test: if an appropriately authorized clinician read this note before the next encounter, would they understand the current problem, what treatment occurred, how the client responded, and what should happen next?

Include:

  • clinically relevant symptoms and functional impact;
  • observable facts that affect formulation;
  • specific interventions;
  • response and goal progress;
  • necessary risk findings and actions; and
  • an actionable plan.

Usually omit:

  • a transcript of the conversation;
  • vivid personal detail unrelated to care;
  • speculation about motives;
  • copied history that did not affect this encounter;
  • repeated text that has not been re-evaluated; and
  • negative findings that were not actually assessed.

Where templates and AI save time safely

Templates save time by preserving structure. AI may save time by turning clinician-supplied anchors into a draft. Both can also create error when they carry forward stale or invented information.

Use templates for:

  • required headings;
  • carefully written section prompts;
  • reminders about attribution and evidence;
  • a review checklist; and
  • stable administrative fields.

Do not auto-populate:

  • risk denials;
  • mental-status findings;
  • treatment response;
  • progress;
  • diagnosis;
  • medical necessity; or
  • a plan that has not been discussed or clinically determined.

When using AI, provide concise source facts, choose the format, and instruct the system not to add unsupported information. Then review the result sentence by sentence. For privacy and governance questions, read Can AI Write Therapy Notes?.

A practical ten-minute routine

The exact timing varies, but a bounded routine prevents documentation from expanding indefinitely:

Minutes 0–2: capture the six anchors.
Minutes 2–5: place them into the required structure and draft each fact once.
Minutes 5–7: write the formulation/progress statement and a connected plan.
Minutes 7–9: verify facts, risk, privacy, and requirements.
Minute 10: correct, authenticate, and complete the workflow.

If the note consistently exceeds the boundary, identify the stage causing delay. Missing capture suggests a workflow problem. Reorganizing suggests unclear section prompts. Rewriting suggests vague source facts or overly broad AI instructions. Long review suggests the draft is adding claims that require extensive verification.

The final quality checklist

Before completing a progress note, ask:

  • Is the session’s clinical focus clear?
  • Are client report and clinician observation distinguishable?
  • Is the skilled intervention specific?
  • Is the client’s response documented?
  • Is progress tied to a treatment goal?
  • Are risk statements limited to what was assessed?
  • Does the plan follow from the assessment and response?
  • Is every sentence necessary, neutral, and supportable?
  • Have required timing and authentication fields been completed?

Primary sources