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

Why SFBT Documentation Is Its Own Category of Hard

Solution-Focused Brief Therapy (SFBT) produces sessions that feel distinctly different from most other approaches. Lighter in tone, forward-moving, client-driven. The clinician is asking about strengths, about exceptions, about imagined futures rather than cataloging deficits and tracing symptom trajectories. Clients often leave with more energy than they arrived with.

Then you sit down to write the progress note. And everything that made the session feel good becomes a documentation problem.

Standard progress note formats were built around problem-focused models. The subjective section expects symptom reports. The assessment expects clinical formulation of impairment. The plan expects intervention targets. SFBT does not produce those raw materials in the expected shape. You spent 50 minutes asking your client to imagine waking up after a miracle and to rate herself on a scale from one to ten. That is clinical work. Translating it into a format built for DSM-symptom tracking requires a deliberate strategy, not just adapting on the fly.

This guide is specifically about that translation problem: how to document SFBT's core techniques accurately, completely, and in a format that satisfies insurance reviewers and audit standards without distorting what actually happened in the session. Fictional examples are used throughout. No real client information appears here.

What SFBT Sessions Actually Generate (And Why It Matters for Documentation)

Before you can document SFBT well, you need to be clear about what the model produces as clinical output. Each core technique generates specific data that belongs in the record. Missing these elements produces thin notes that create audit risk, not just notes that underrepresent the clinical work.

Well-Formed Goals and Client-Generated Goal Language

Every SFBT session involves some version of the well-formed goal conversation. The client articulates what they want their life to look like when therapy has succeeded, and that vision is refined through questioning until it is concrete, observable, and genuinely owned by the client, not assigned by the clinician.

This is a meaningful distinction for documentation. A SFBT goal is not a treatment plan goal that the therapist developed and the client signed. It is a statement of the client's preferred future, expressed in language that emerged from the client. Your notes should capture that language, even when you slightly adapt it for clinical legibility.

The client-generated nature of these goals has implications for how you write your treatment plan, your progress narrative, and your assessment. When you note that a client is moving toward their preferred future, you are documenting something different from a clinician-assigned goal. Make that clear in the record.

Scaling Questions and Numeric Progress Data

Scaling questions convert the client's subjective experience of progress into a number that can be tracked across sessions. The clinician asks something like: "On a scale of one to ten, where ten represents the life you just described and one is as bad as things have ever been, where would you place yourself today?" The client names a number, explains the rationale for it, and the clinician asks what would need to happen to move one point higher.

These numbers are clinical data. They are quantified, reproducible, and they build a natural progress narrative across sessions that does not require constructing a deficit-based account. A client who rated herself a 4 in session two and a 7 in session eight has documented progress that is specific, concrete, and legible to any reviewer.

Document the number every session. Document the client's rationale for the number. Document what the client said would represent one step of progress. That three-part entry takes two sentences and creates a longitudinal record of change that is far more clinically specific than most narrative progress summaries.

Exception-Finding

Exception-finding is the SFBT technique of identifying times when the presenting problem was absent or less severe, and exploring what was happening during those periods. The clinical premise is that exceptions contain the ingredients of solution: if you can identify what the client was doing when things were better, you can amplify those behaviors deliberately.

What exception-finding surfaces matters for your record because it documents the client's existing strengths and functional coping mechanisms. When a client identifies that her anxiety was lower on Tuesday morning because she had not checked email before breakfast, she has identified a behavioral strategy that already works. Your note should capture what the exception was, what the client attributed it to, and whether the client expressed confidence that she could replicate it.

That attribution matters specifically because it tracks self-efficacy: does the client understand herself as an agent who creates the exceptions, or does she experience them as random good fortune? A shift in attribution over the course of treatment is itself clinical progress worth documenting.

The Miracle Question

The miracle question is SFBT's signature technique and one of the most clinically rich interventions in the model. The standard form: "Suppose that tonight while you are asleep, a miracle happens, and the problem that brought you here is solved. You do not know it happened while you were sleeping. When you wake up tomorrow, what would be the first small signs that something had shifted?"

The miracle question is not a warm-up activity. It is a clinical intervention designed to generate a detailed, emotionally accessible picture of the client's preferred future. The content it produces tells you a great deal: what the client wants, how vividly they can imagine it, whether their vision is concrete or abstract, and whether hope is accessible to them.

All of that is documentable. If a client generates a rich, specific miracle picture involving concrete behavioral changes, document the substance of that picture. If a client struggles to generate any clear vision of a different future, document that difficulty, because it is clinically significant: it may signal depression-related anhedonia, rigidity, or a therapeutic relationship that is not yet safe enough for vulnerable hope.

The miracle question does not need to be used every session. When you do use it, something about the client's response should be in the note.

Compliments

Clinician compliments in SFBT are not casual praise at the end of the session. They are deliberate clinical observations about the client's strengths, competencies, and resources, delivered in a way that reinforces the client's sense of agency and capacity for change.

Most SFBT sessions end with a short compliment sequence: the clinician explicitly names two or three things they noticed about the client during the session that reflect the client's strengths. These observations are targeted, specific, and often directly connected to the client's preferred future goals.

Document the compliments, briefly. Not because the compliments themselves are legally significant, but because they are clinical interventions, and an intervention that does not appear in the record does not exist from an audit perspective.

Between-Session Tasks

SFBT sessions almost always end with a task assignment: something the client will observe, notice, or do between sessions. Common task types include the formula first session task (notice what you want to have continue in your life), observation tasks (notice when exceptions occur and what you were doing differently), and do-more-of-what-works tasks (deliberately repeat a behavior that was identified as an exception).

Task assignments are clinical interventions with a specific rationale. They must appear in your note. If you gave a task and did not document it, the next session's follow-up on that task is orphaned: the chart shows a discussion of something that was never assigned.

Documenting Client-Generated Goals vs. Clinician-Assigned Goals

This is one of SFBT's most specific documentation challenges, and it matters more than most clinicians recognize.

In problem-focused models, treatment plan goals are typically developed by the clinician based on clinical assessment, then presented to the client for discussion and signature. The goals are written in clinical language and anchored in the diagnostic formulation.

In SFBT, goals emerge from the client's own account of their preferred future. The clinician helps refine those goals until they are well-formed, but the substance comes from the client. This is not a subtle difference. It is a different theory of therapeutic change.

The documentation implication: when you write your treatment plan goals and when you note progress toward those goals, you should reflect whose language the goals are in. A treatment plan that says "Client will increase adaptive coping and reduce avoidance behaviors" is a clinician-generated formulation. A note that captures the client's own statement, "I want to be able to go to work on Monday mornings without the knot in my stomach taking over," is a different kind of record.

You do not have to choose one or the other. The treatment plan can use clinical language that satisfies payer requirements, while your progress notes can track the client's own articulation of their goals alongside the clinical framing. Both serve a purpose. But your documentation should make clear, session by session, whether the goals being addressed are ones the client owns or ones that were assigned to them.

SFBT vs. Problem-Focused Note Formats

Here is what the structural difference looks like in practice.

In a standard problem-focused note, the data or subjective section summarizes presenting symptoms, the assessment addresses diagnostic criteria and functional impairment, and the plan targets symptoms and skill deficits. Progress is measured by symptom reduction.

In an SFBT note, the equivalent sections need to capture different content without abandoning the elements that insurance reviewers expect.

The key insight is that you are not replacing the problem-focused elements, you are adding the SFBT elements alongside them. An SFBT note that entirely omits the diagnostic picture and impairment language will not survive an insurance audit. An SFBT note that captures the diagnosis, the scaling progress, the exception content, and the task assignment is both clinically accurate and audit-ready.

SOAP Format Adapted for SFBT

Fictional Example: Elena

Elena is a 34-year-old teacher presenting with Generalized Anxiety Disorder (GAD), diagnosis F41.1. She has been in SFBT for five sessions. Her stated preferred future is "getting through a full Sunday without the dread of Monday taking over." Today is session six.

Subjective

"Client arrived on time and engaged readily. Reported that the past week 'went better than the last couple.' When asked to rate progress toward her preferred future goal on the 1-10 scale, client rated herself a 6, up from a 5 at the prior session. Client attributed the increase to having 'managed to stay in the moment' during a Sunday afternoon family meal without the Monday dread taking over the entire day. Exception identified: client noticed she did not experience anticipatory anxiety on Saturday afternoon, and attributed this to having deliberately planned a Sunday activity she was looking forward to (visiting a botanical garden with her sister). Client expressed the view that 'having something to look forward to on Sunday actually changes what Saturday feels like.' Client demonstrated capacity to identify the behavioral mechanism behind the exception without prompting. Miracle question revisited briefly; client elaborated a more specific version of her preferred future than in session one, now describing specific morning sensations ('not waking up with the grip in my chest') rather than general emotional states."

Objective

"Client was alert, cooperative, and engaged throughout the 53-minute individual session. Affect was euthymic to mildly brightened. Speech was organized and goal-directed. No evidence of suicidal ideation or intent. Mental status unremarkable."

Assessment

"Client continues to meet criteria for GAD F41.1 with functional impairment in occupational anticipation and weekend quality of life. Session focused on scaling progress review, exception-finding, and elaboration of preferred future via miracle question revisitation. Client demonstrated measurable progress: scaling increase from 5 to 6 reflects behavioral change consistent with treatment plan goal targeting reduction of anticipatory anxiety and improved occupational functioning. Client's self-identification of the behavioral mechanism underlying the exception (planning a forward-looking event) indicates growing self-efficacy in applying solution-focused strategies. Preferred future elaboration becoming more concrete and behaviorally specific across sessions, consistent with increasing hope accessibility. Clinical impression: steady progress; SFBT approach well-matched to client's profile."

Plan

"Task assigned: client will plan one 'forward anchor' for each Sunday over the next two weeks (an activity she looks forward to) and notice whether this changes her Saturday experience. Rationale: amplification of the behavioral exception identified today. Next session: review task outcome, continue scaling progress review, introduce 'coping question' if scaling number plateaus. Session scheduled in two weeks."

Key Differences from a Standard SOAP Note

Notice what this SOAP note does: it holds the diagnostic frame (GAD with impairment) in the assessment section while structuring the subjective around SFBT data (scaling number, exception content, miracle question response). It names the client's attribution explicitly. It gives the task assignment its own sentence in the plan with a stated rationale. An insurance reviewer reading this note sees medical necessity, treatment activity, and progress. An SFBT supervisor reading it sees a clinically coherent SFBT process.

DAP Format Adapted for SFBT

Some practitioners prefer DAP (Data, Assessment, Plan) for SFBT because the format is slightly less structured and allows more narrative flexibility in the data section. Here is the same clinical material in DAP format.

Fictional Example: Elena (Session Six, DAP)

Data

"Session six, 53 minutes, individual outpatient. Client reported the past week as 'better than the last couple' and rated progress toward preferred future goal at 6/10, up from 5 last session. Rationale: managed to remain present during a Sunday family meal without anticipatory Monday anxiety dominating. Exception identified: Saturday afternoon passed without anticipatory anxiety because client had planned a Sunday outing she was anticipating (botanical garden with sister). Client articulated the mechanism: 'having something to look forward to on Sunday actually changes what Saturday feels like.' Client demonstrated independent identification of the behavioral driver of the exception, without prompting. Miracle question revisited; client generated a more behaviorally specific preferred future description than in session one (somatic detail: 'not waking up with the grip in my chest'). Compliments offered: clinician noted client's growing precision in identifying her own behavioral strategies and her capacity to link behavioral action to emotional experience. Task assigned: plan one 'forward anchor' activity per Sunday over the next two weeks and track effect on Saturday experience."

Assessment

"Client meets criteria for GAD F41.1 with functional impairment in anticipatory anxiety affecting occupational preparation and leisure quality. Scaling progress from 5 to 6 reflects concrete behavioral change (reduced avoidance of Sunday experience) consistent with treatment plan goals targeting anticipatory anxiety reduction. Increasingly specific preferred future language suggests growing hope accessibility. Self-attribution of exception mechanism indicates emerging self-efficacy. Clinical impression: engaged client making measurable progress with SFBT approach well-matched to presentation. Continue current frequency and approach."

Plan

"Client to implement 'forward anchor' task over two weeks. Review task outcome next session. If scaling number reaches 7, introduce discussion of what maintaining that level would require. Monitor for treatment plan goal progress. Next session in two weeks."

Tracking Scaling Progress Across Sessions

Scaling questions only become a longitudinal progress record if you use them consistently and document the number every session. A table is useful here, though you can just as easily carry this in a brief notation.

Here is what consistent scaling documentation looks like across Elena's six sessions:

This table belongs in the chart or as a recurring section of your session notes, not hidden in narrative prose that becomes impossible to extract later. The scaling trajectory tells the treatment story in a format that a supervisor, a reviewer, or a subsequent therapist can read in thirty seconds.

When a client's scale number drops between sessions, that is also clinical data worth documenting. A drop from 5 to 3 does not mean SFBT failed. It may mean there was an external stressor, that the client is being honest rather than socially compliant, or that the treatment needs recalibration. Document the drop, document the client's explanation, and document how you responded clinically. "Client rated self a 3 this session, down from 5 last session, attributing the drop to a significant conflict with her partner that occurred on Thursday. Exception-finding was not productive today given acute distress. Clinical decision: shifted to coping question ('How have you managed to get through each day given what happened?') to establish competency before returning to preferred-future work. Task: observe any moment of relief over the coming week and note what helped it arrive."

Documenting Between-Session Change and Exception-Tracking

Between-session change is a specific phenomenon that SFBT attends to: the changes that happen in the client's life after the previous session and before the current one. Some of those changes were the result of the task assignment. Others were spontaneous. SFBT treats both as significant.

Begin each session note by capturing what the client reports from the interval between sessions. Did the client implement the task? What happened? Did anything change that the client did not expect? Were there additional exceptions the client noticed on their own?

This is important documentation for two reasons. First, it tracks the relationship between interventions and outcomes, which is what progress monitoring is supposed to do. Second, it establishes that you are practicing in a sequential, coherent way: each session connects to the last, the assignments were genuine, and the treatment is not a series of isolated conversations.

A consistent format for this section might look like: "Client reported on prior session task: [what the task was] / [whether client implemented it] / [what happened]. Additional changes or exceptions since last session: [anything the client offered unprompted]."

Do not skip this even when the client did not implement the task. "Client reported that she did not complete the observation task assigned at the prior session; stated she 'forgot about it until the day before today.' Explored what that week was like without the task. Client noted that things felt 'flat' mid-week, which she had not experienced the previous week. Clinician noted possible connection between the observation practice and the improved mid-week quality she had reported in session five; client agreed this warranted attention." That entry documents task non-completion as clinical data, not as a failure requiring no comment.

SFBT Notes When Insurance Requires Problem-Focused Formats

Insurance documentation standards were built around a deficit model. Payers want to see a diagnosable condition, functional impairment from that condition, and treatment that addresses the impairment. SFBT's strengths-based framing does not eliminate the obligation to document this. It changes how you frame it, not whether you include it.

Think of every SFBT note as running two parallel tracks.

Track one is the clinical SFBT track: what the client said about their preferred future, where they are on the scaling continuum, what exceptions they identified, what task was assigned. This is the substance of what happened in the session.

Track two is the insurance track: diagnosis code, brief acknowledgment of functional impairment, connection between the session's clinical activity and the treatment plan goals, clinical rationale for continuing treatment.

Neither track is dishonest. Both describe something real about the client and the treatment. Track one reflects the session process; track two reflects the clinical and administrative context.

The assessment section is where the two tracks most explicitly converge. Here is the formula: name the diagnosis, acknowledge the impairment, then connect the SFBT techniques to the treatment plan goals and to the client's progress on those goals. "Client continues to meet criteria for GAD F41.1 with functional impairment in occupational functioning and leisure quality. Exception-finding and scaling progress in today's session are directly consistent with treatment plan goal 2 (client will demonstrate use of at least two behavioral strategies to manage anticipatory anxiety) and goal 3 (client will report reduced interference of anxiety with weekend and Monday morning functioning). Progress is measurable and consistent with the current treatment approach."

That assessment section names the diagnosis, states impairment, and connects the SFBT session to specific treatment plan goals. A reviewer can justify continued authorization from it.

Connecting SFBT Techniques to Treatment Plan Goals

Your treatment plan does not need to be written in SFBT language to be compatible with SFBT sessions. If your treatment plan was written in deficit-focused language for insurance purposes, you can still practice SFBT and document accurately. The connection happens in the assessment section: "Exception-finding today identified that client successfully used behavioral scheduling (anticipated Sunday activity) to reduce anticipatory anxiety, consistent with treatment plan goal targeting increased use of adaptive coping strategies."

Make the connection explicit. One sentence per session, connecting what happened in the SFBT session to which treatment plan goal it addresses, is enough. Reviewers do not object to SFBT. They object to notes that make the treatment look arbitrary or disconnected from the treatment plan.

Billing Code Alignment

SFBT sessions are sometimes shorter than sessions in other modalities. One of the model's explicit premises is that change does not require extended treatment. That is legitimate clinical reasoning. It becomes a problem when the note's documented clinical content does not match the billing code being used.

If you are billing a CPT code 90837 (60-minute psychotherapy), your note needs to reflect clinical activity that would reasonably fill that time. If your SFBT sessions routinely run 30 to 35 minutes because the work is efficient, bill a 90834 (45-minute session) or reassess your session length. A note that describes five minutes of scaling review, a brief exception-finding conversation, and a task assignment assigned in three sentences does not support a 60-minute billing code. Mismatches between documented clinical content and billed time are a routine audit trigger.

Common Documentation Mistakes in SFBT Practice

Scaling Numbers Without Clinical Substance

A note that says "Client rated herself a 6 this session" and nothing more is not clinical documentation. The number is a doorway into the clinical content. Document what is on the other side: why the client rated herself a 6, what she said that number meant, and what she identified as the path to a 7. Without that, the number is administratively present but clinically empty.

Notes So Strengths-Focused That Medical Necessity Disappears

This is the most common SFBT documentation error. A note that is entirely forward-focused and strengths-affirming, with no acknowledgment of the diagnosis, the impairment, or the clinical rationale for continued treatment, will not survive an insurance review. The note can be strengths-focused in orientation and still include two sentences of diagnostic context. Both belong.

Omitting Task Assignments

If you gave a task and did not document it, the next session's follow-up appears to be a conversation about something that was never planned. Task assignments are interventions. They belong in the note with enough specificity that you could follow up on them accurately two weeks later.

Not Following Up on Previous Tasks

SFBT is a sequential model. The between-session assignment connects one session to the next. If you do not begin each session with a brief note on how the prior task went, the chart reads as a series of independent conversations rather than a treatment with continuity. Follow-up is not optional.

Treating the Miracle Question as Optional to Document

If you used the miracle question, something about the client's response belongs in the note. Even a brief notation: "Miracle question revisited; client's preferred future description becoming more behaviorally specific" tells a reader that the technique was used and what it produced. A session note that mentions the miracle question was used but documents nothing the client said is not useful documentation.

Using a Generic Template That Omits SFBT-Specific Fields

Standard clinical note templates include fields for presenting problem, symptom report, and intervention techniques, but almost none include dedicated fields for scaling question responses, exception content, or task assignments. When your template does not match your practice, you either skip the SFBT elements or squeeze them into fields where they do not belong.

A SFBT-specific note structure with dedicated fields for scaling number and rationale, exceptions identified, miracle question response (when used), compliments offered, and task assigned makes documentation faster and more complete. Tools like NotuDocs let you build a custom template that reflects your actual SFBT practice, so the structure you fill in each session matches the clinical events you are actually documenting rather than a generic note format designed for a different approach.

SFBT Documentation Checklist

Use this at the end of each session before you close the chart.

Session Basics

• Client name, session date, duration, modality (in-person or telehealth), and billing code recorded
• Diagnosis code(s) included
• Functional impairment acknowledged in assessment section
• Session duration matches billing code used

SFBT-Specific Data Elements

• Scaling number documented with client's rationale for the number
• What the client identified as the next step of progress (what a one-point increase would look like) documented
• Scaling number compared to prior session with any change noted
• Follow-up on prior session's task assignment documented (whether implemented, outcome)
• Between-session change or spontaneous exceptions noted
• Exceptions identified this session documented, including client's attribution
• Miracle question response documented if the technique was used (or absence of clear response noted if clinically significant)
• Compliments offered documented, with the specific client strengths they targeted
• Task assignment documented with specificity sufficient to follow up next session
• Rationale for the task assignment stated briefly

Assessment and Plan Quality

• Assessment section connects SFBT session activity to specific treatment plan goals
• Assessment demonstrates medical necessity without abandoning strengths framing
• Plan includes task assignment, rationale, and plan for the next session
• Clinical impression reflects current progress trajectory
• Would a reviewer who did not attend the session understand what happened and why continued treatment is warranted?

Longitudinal Coherence

• Scaling progress can be tracked from the previous session note
• Any significant change (increase, decrease, or plateau) is explained, not just reported
• Task follow-up connects this session to the last
• Progress narrative builds logically across the course of treatment

SFBT documentation does not require more words than any other modality's notes. It requires different structure and deliberate attention to the clinical events that are specific to this model. When your template matches your approach and your assessment section holds both the SFBT and the insurance frame simultaneously, the clinical content fills itself in rather than fighting against a format that was designed for something else.

For related guidance, the concurrent documentation guide covers strategies for capturing session data efficiently when SFBT's quick pace makes after-session documentation a race against fading detail. The motivational interviewing documentation guide addresses a similar challenge of documenting a non-directive, client-led model in formats built for directive intervention.