How to Document Solution-Focused Brief Therapy (SFBT) Sessions

Why SFBT Notes Look Different From Everything Else

Solution-Focused Brief Therapy (SFBT) is organized around a simple inversion: instead of building a detailed picture of what is wrong and how it developed, SFBT focuses on what the client wants and what already works. The clinical logic moves forward, toward preferred futures, rather than backward through symptom history.

That orientation is its greatest strength and its most persistent documentation challenge.

Standard progress note formats, including SOAP (Subjective, Objective, Assessment, Plan) and DAP (Data, Assessment, Plan), were designed to track problem trajectories. The Subjective section expects symptom reports. The Assessment section expects clinical formulation of dysfunction. When you spend fifty minutes asking a client to describe a morning when things were better, to rate their confidence on a scale from one to ten, and to notice what they are already doing that is working, your session has not failed to produce clinical data. It has produced a different kind of clinical data, and you need to know where it goes and how to frame it.

This guide covers the mechanics of that translation: what each SFBT technique generates as a documentation element, how to write treatment goals in SFBT language, how to track session-to-session progress, and how to satisfy payer audit standards without flattening a strengths-based session into a deficit narrative. Fictional examples are used throughout. No real client information appears here.

The Core Documentation Difference: Capturing Client-Generated Content

Before getting into specific techniques, one principle needs to be stated clearly because it shapes everything else: in SFBT, the clinical content lives in what the client says, not in what the clinician interprets.

In problem-focused approaches, the therapist's clinical formulation is the primary data. In SFBT, the client's own language is the primary data. The miracle question works because the client articulates their preferred future in their own words. Scaling questions work because the client places themselves on a continuum and explains why they are where they are. Exception-finding works because the client identifies what they themselves are already doing that reduces the problem.

A progress note that paraphrases all of this into clinician language without preserving any client voice misrepresents the model and strips out the clinical substance. When a client says "I would wake up and not dread getting out of bed," that exact phrasing is clinical data worth preserving. It is not informal. It is the preferred future the treatment is organized around.

This does not mean your notes become verbatim transcripts. It means you quote or closely paraphrase key client statements, label them accurately, and maintain the distinction between what the client said and what you observed or assessed.

Documenting the Miracle Question

The miracle question is the signature technique of SFBT, developed by Steve de Shazer and Insoo Kim Berg. The standard form is something like: "Suppose tonight, while you are sleeping, a miracle happens and the problem that brought you here is solved. What would you notice first tomorrow morning that would tell you something is different?"

The question generates a client-constructed vision of life when the problem is resolved. That vision is the clinical content. Your job is to document it specifically enough that it is useful across sessions and legible to a reviewer who was not in the room.

What to Include in a Miracle Question Note

A well-documented miracle question response includes:

The client's concrete miracle indicators. What specific changes does the client describe? These should be behavioral, relational, and sensory. Not "I would feel better" but "I would make coffee instead of going straight to my phone" or "I would actually hear what my daughter is saying to me at breakfast." Document these specifics, not a summary of them.

The interactive dimension. SFBT practitioners often follow up by asking who else would notice the miracle and what they would observe. "My partner would notice I was not short with him before work" captures a relational marker that has treatment planning implications.

The client's affective response to the vision. How does the client respond when describing the miracle? Expanded affect, visible engagement, increased pace of speech, or visible discomfort all belong in the objective section of a SOAP note or the Data section of a DAP.

Example: Elena, a 34-year-old teacher presenting with persistent work-related anxiety, was asked the miracle question in session 3. She described the following miracle indicators: sleeping through the night without reviewing the next day's schedule at 3 a.m., arriving at school without her stomach tightening as she walked into the building, and being able to leave work at work rather than reviewing interactions with students during dinner. She noted her husband would notice because she would "actually sit down when we eat instead of standing at the counter." Client's affect was notably warmer and more engaged when describing this vision than at any prior point in the session.

That level of documentation does three things. It preserves the clinical content of the technique. It establishes the preferred future that subsequent sessions will track toward. And it provides behavioral indicators that can be converted into measurable treatment goals.

Documenting Scaling Questions

Scaling questions are the quantitative spine of SFBT. They allow a client to locate themselves on a continuum, compare across time, and describe what movement in either direction would look like. The most common form: "On a scale from zero to ten, where ten is the miracle we described and zero is the worst the problem has ever been, where would you say you are today?"

A single scaling question in a session is actually three documentation elements, and capturing all three is what makes the note useful across multiple sessions.

The Three-Part Scaling Note

1. The score and its basis. What number did the client give, and what reasoning did they offer? A 4 means something different when the client says "because things at work have been slightly better" than when they say "because at least I'm not crying every day." Document the number and the client's rationale for it.

2. The next-step question. SFBT practitioners follow every scaling question with something like "What would one point higher look like?" or "What would tell you that you had moved from a 4 to a 5?" The client's answer is the treatment planning content. Document it as specifically as the miracle question response.

3. The session-to-session tracking. Scaling scores are longitudinal data. A client who was at a 3 in session 2, moved to a 5 in session 4, and is now at a 4 in session 6 has a clinical story that belongs in your notes. You do not need a formal outcome measure table to track this, but the scores need to be recorded consistently and referenced in your assessment language.

Example: In session 5 with Tomás, a 42-year-old construction manager presenting with generalized anxiety, the following scaling exchange was documented:

Confidence scale (zero to ten) for managing work stress without physical symptoms: Client rated himself at a 5. Rationale: "I've been leaving the office by 6 most nights, which hasn't happened in two years. I'm still checking email before bed but less." When asked what a 6 would look like: "Probably cutting that last check before bed. Even if it's quick, it still puts my brain back in work mode."

In session 4, the same scale was rated at a 3. In session 3, no scale was administered.

One-point improvement from session 4 to session 5, consistent with client's identified behavioral changes. Scale tracking supports continued treatment.

That note structure gives a reviewer, a supervisor, a succeeding clinician, or a utilization reviewer everything they need to understand clinical progress without translating SFBT terminology into deficit language.

Documenting Exception-Finding

Exception-finding is the process of identifying times when the problem is less severe, less frequent, or absent entirely. The clinical premise is that exceptions to the problem contain information about what already works, and building on those existing successes is more efficient than building skills from scratch.

The documentation task is to make exceptions specific, attributable, and usable.

Exception Documentation Standards

Make exceptions behavioral and concrete. "Times when anxiety is lower" is not useful. "Mornings when client goes for a walk before checking email, describing anxiety as approximately a 2 compared to her typical 6-7 on non-walk mornings" is useful. The difference is not just clarity. It is the difference between a note that supports treatment planning and one that does not.

Attribute exceptions to the client. SFBT is intentional about attribution: when a client identifies that something they did contributed to a better moment, that attribution is the therapeutic leverage. Document not just what the exception was but whether the client identified it as something within their own agency. "Client attributed reduced anxiety on Tuesday morning to her decision to leave her phone in another room, identifying this as a choice she could make more consistently" captures both the exception and its clinical significance.

Note deliberate vs. spontaneous exceptions. A client who has been deliberately trying something different since the last session shows different clinical progress than a client who noticed a random good moment. Both are clinically useful, but they are different. Deliberate exceptions suggest developing agency; spontaneous exceptions are starting points for exploring what was happening differently.

Example: In session 4, client Maya, a 29-year-old graduate student presenting with depression and academic avoidance, identified three exceptions to her pattern of afternoon shutdowns: the Tuesday she met a peer for coffee before studying, the Thursday her advisor sent a brief encouraging email, and the Friday she worked in the library rather than her apartment. When asked what she had done to make those days happen: "The coffee one was me, I actually texted her. The library one was also me. The email was just luck." Exception documentation noted two client-agency exceptions and one circumstantial exception. Between-session task (see below) oriented toward coffee meeting and library approaches.

Documenting Coping Questions

Coping questions are used when a client is in significant distress and the scale question approach would feel dismissive. The form is something like: "Given everything you're facing, how have you managed to keep going?" or "What has helped you get through the hardest days?"

The clinical content of a coping question response is often different from exception-finding. It tends to surface strengths and resources rather than behavioral strategies, and it can reveal existing social support, values, and commitments that have stabilized the client even in acute periods.

Document coping question responses the same way you document exception-finding: specifically, in the client's language, with attribution of agency where the client expressed it.

Example: In session 2, Adriana, a 52-year-old nurse presenting following a difficult hospital restructuring and grief related to a colleague's death, declined to rate on a confidence scale, describing the week as "a 1 or a negative." Coping question was used: "Given how much you're carrying right now, what has helped you keep functioning?" Client response: "My patients. I show up for them because they don't have anyone else. And I call my sister every Sunday, that's non-negotiable." Documentation noted two resilience anchors: vocational purpose and relational consistency with one sibling. These were identified as natural strengths to scaffold future preferred-future work.

Documenting Best Hopes

Best hopes is the opening question in many SFBT sessions, particularly those developed in the Brief Therapy Practice model: "What are your best hopes for our work together?" Unlike a standard presenting problem question, best hopes is deliberately future-oriented. It asks the client to name what they want from therapy, not what has gone wrong.

Best hopes documentation serves two functions. It establishes the client's self-defined treatment goal in their own language, which is different from a clinician-assigned treatment objective. And it creates a reference point for session-to-session evaluation: are we moving toward what the client wanted?

Document best hopes early in treatment and return to them explicitly in progress language. "Client's best hopes at intake included being able to attend family events without leaving early due to anxiety. In today's session, client reported attending a cousin's graduation without early departure, describing this as a direct demonstration of hope fulfillment."

That language connects session-level progress to the treatment goal that came from the client, which is the SFBT equivalent of a SMART goal link in problem-focused approaches.

SFBT Treatment Goals: Writing for the Record and the Payer

Treatment goals in SFBT should be written in client language as closely as possible while still meeting the measurability requirements that third-party payers and licensing boards expect. This is a genuine tension, not a stylistic preference, and it requires a specific writing approach.

The SFBT Goal Format

A SFBT treatment goal has three components:

Client's preferred future statement (directly from the miracle or best hopes conversation): What does the client want their life to look like?

Behavioral indicators (how you will know when the goal is met): Observable changes the client or collaterals could verify.

Scaling benchmark (how progress will be measured across sessions): The point on the client's chosen scale that represents sufficient progress to support discharge or treatment completion.

Example treatment goal: "Client will be able to sustain work hours without physical anxiety symptoms (goal identified by client as attending meetings without visible shaking and remaining on-site through the workday). Progress will be tracked using a 0-10 confidence scale; client has identified 7 as sufficient improvement to meet this goal. Baseline rating: 3 (session 1)."

That goal is measurable, client-generated, and trackable. It satisfies SOAP-format treatment planning requirements without reducing the goal to a deficit framing.

Write Goals in Client Language First, Then Translate

A common mistake is writing SFBT treatment goals in clinical language and then summarizing the client's preferred future as a secondary note. Reverse that order. Write what the client said they wanted first. Then add the behavioral operationalization. This order makes the documentation faithful to the model and more honest about where the treatment direction came from.

How SFBT Progress Notes Differ From Problem-Focused Formats

SFBT does not map cleanly onto standard SOAP or DAP structures, but it can be adapted to both without distorting the model. The key is understanding what each section actually needs to contain, not what the generic template implies it needs.

Adapting SOAP for SFBT

Subjective: In a problem-focused SOAP note, this section contains the client's symptom report. In SFBT, you are documenting the client's report of exceptions, scaling self-assessments, and progress toward preferred future. The section is still the client's subjective experience. It is just not organized around symptom severity. You can write: "Client reported several days this week where she left work at her contracted time, rating this week's confidence at 6 compared to 4 at last session."

Objective: Document observable clinical observations in the session: affect, engagement with techniques, visible shifts when discussing exceptions or preferred future. "Client's affect became notably more animated when describing exception-finding findings from the week. Eye contact increased during miracle question follow-up."

Assessment: This is where SFBT and payer requirements most directly collide. Payers want evidence of clinical need and progress toward a clinical goal. You can write this accurately without abandoning SFBT language: "Client continues to meet criteria for Generalized Anxiety Disorder (F41.1). Session-to-session scaling scores show clinically significant improvement (from 3 at intake to 6 this session). Exceptions identified are consistent with client-identified behavioral markers in treatment plan. Treatment remains medically necessary to consolidate gains and reach client's defined goal of 7."

Plan: Document the between-session task, if any, the focus for the next session, and any treatment plan updates. If the client generated the task (which is the SFBT norm), note that: "Between-session task generated by client: continue library study sessions and track mood using personal journal rather than formal scale."

Adapting DAP for SFBT

Data: Combine all session content here, including the client's subjective reports and your objective observations. SFBT sessions generate rich content in this section: scaling scores, miracle question language, exception specifics, coping responses, and between-session feedback.

Assessment: Same function as SOAP Assessment above. Clinical diagnosis, functional status, and progress framing.

Plan: Between-session task, next session focus, and any clinical decision-making about treatment trajectory (e.g., approaching completion based on sustained scale improvement).

What to Avoid

Several documentation patterns consistently create problems in SFBT charts:

Documenting only technique names without content. "Miracle question administered. Scaling questions used." is not a note. It is a technique checklist. Document what the client said.

Ignoring the treatment plan. SFBT's strengths-based approach does not exempt you from treatment plan compliance. Every session note should connect to a treatment goal, even if briefly.

Writing the assessment in problem-escalation language. Notes that say "client continues to struggle significantly" when the scale has moved from 3 to 6 are internally inconsistent. Match your assessment language to the actual clinical picture.

Leaving the between-session task vague. "Client will try to notice positive things this week" is not a task. "Client will keep a three-item daily note of exceptions to the anxiety pattern, as she designed it, for review at next session" is a task.

Between-Session Tasks: Documentation That Supports Accountability

Between-session tasks in SFBT are client-generated, not clinician-prescribed. That distinction matters for documentation because it affects how you frame the task and how you document follow-through.

Document each between-session task with:

• The task in specific behavioral terms
• How the task was generated (client-initiated, collaboratively identified, or clinician suggested and client accepted)
• The rationale connecting the task to the client's exception-finding or preferred future
• At the following session: whether the task was completed, partially completed, or not attempted, and what the client made of that

If a client does not complete a task, SFBT documentation should reflect the model's response: curiosity about what was happening, not compliance-focused language. "Client reported she did not use the library this week due to a family obligation. Discussion of what the week did include that was helpful. Client identified that she maintained her morning walk on four of seven days despite the disruption."

A Sample SFBT DAP Note

Client: Tomás, session 6. Presenting concerns: work-related anxiety, conflict avoidance at home.

Data: Client arrived on time and appeared more relaxed in posture than at previous sessions. He reported a confidence scale rating of 6 for the week (session 5: 5; session 4: 3; session 3: 4). Rationale offered: "I didn't check email after dinner three nights this week. First time I can remember doing that since before my promotion." Between-session task review: Client completed the agreed-upon review of his exception log. He identified four evenings without work email review, compared to one during the previous week. Exception-finding in session focused on what made those evenings different. Client identified that on three of the four evenings, his wife had suggested a walk, which he agreed to. On the fourth, he made the decision independently. When asked what the independent evening told him about himself: "That I can actually do this on my own, not just when she reminds me."

Miracle question follow-up (brief check-in): Client rated current life at approximately 60% of his miracle picture, up from 35% at session 3.

Assessment: Client continues to meet criteria for Generalized Anxiety Disorder (F41.1) with functional impairment in work-life separation. Session-to-session scaling data indicates steady improvement. Client demonstrates developing autonomous agency in exception-finding, consistent with treatment goal (reaching scale rating of 7 in work-anxiety management). Treatment continues to be medically necessary.

Plan: Between-session task: Client will attempt one additional evening without email review that is self-initiated, with brief written note about what made it possible. Next session: continued scaling check-in, expand exception exploration to morning routines (identified by client as remaining difficult). No changes to treatment plan at this time.

End-of-Treatment Documentation in SFBT

SFBT is designed to be brief, and discharge documentation should reflect that intentional brevity. Do not write a discharge summary that frames the end of treatment as premature. If the client has reached their best hopes and their scaling benchmark, the note should say so clearly.

Discharge summary elements for SFBT:

• Initial best hopes or preferred future statement
• Scale score at intake vs. scale score at discharge
• Key exceptions and strengths identified during treatment
• Client's self-assessment of readiness to continue without therapy
• Any referrals or ongoing support identified

Discharge language: "Client entered treatment at a 3 on her confidence scale, with a best hope of being able to attend family events without anxiety-driven early departure. At discharge (session 8), client rated herself at a 7, consistent with her identified goal. Client reported attending three family events in the final month of treatment without early departure. Client identified her morning walk practice, library study habit, and weekly sister call as strengths she will continue. Client expressed confidence in managing future challenges without ongoing therapy. Discharge by mutual agreement."

Documentation Checklist for SFBT Practitioners

At intake and first sessions:

• Best hopes documented in client's language
• Preferred future or miracle question response recorded with specific behavioral indicators
• Baseline scaling score established with client's rationale
• Client-generated treatment goals written with behavioral markers and scale benchmark
• Treatment diagnosis documented with functional impairment rationale

Each session:

• Scaling score recorded with client's rationale and comparison to previous session
• Exception-finding specifics documented: behavioral details, attribution (client agency vs. circumstantial), deliberate vs. spontaneous
• Coping question response documented if crisis context applies
• Between-session task review: completed, partial, or not attempted, with clinical observation
• New between-session task documented with specifics and generation method
• Assessment connects session content to treatment goal and diagnosis
• No technique names without documented content

Longitudinal:

• Scale score trend visible across session notes
• Miracle/preferred-future language referenced when noting progress
• Treatment plan reviewed and updated at clinically appropriate intervals
• Discharge criteria (scale benchmark, best hopes achievement) documented in final session

NotuDocs supports template-first note generation where you control the exact fields in your SFBT note structure, including scaling score tables, exception logs, and preferred-future tracking sections. You write the session summary, the tool fills the structure you designed, and nothing is added that you did not put there.

---

Related guides: How to Document Motivational Interviewing (MI) Sessions | How to Document Therapy Sessions Using Standardized Outcome Measures | Concurrent Documentation in Therapy