A process-based documentation assistant for learning functional thinking
The Functional Process Note (FPN) Practice Tool is designed to help clinicians-in-training practice functional contextual thinking, not just tidy writing. It takes raw, messy, real-world session material and helps the learner transform it into language that tracks context, function, yearning, and trajectory, while remaining de-identified and clinically disciplined. The emphasis is not on perfection, but on seeing behavior in context and over time, and on learning how to write notes that reflect that stance.
At its core, the tool supports three learning moves:
- Condensing unstructured session material into workable behavioral descriptions
- De-identifying content so it can be used safely for training and supervision
- Shifting form without losing function, moving between raw notes, narrative reflection, and formal FPN structure
What follows illustrates how the tool works by contrasting an original raw entry with a refined narrative output, showing how meaning is preserved while clarity, safety, and functional precision increase.
From Raw Session Material to Functional Narrative
The original material entered into the tool looked much like real clinical notes often do: long, stream-of-consciousness, emotionally vivid, and clinically rich, but difficult to reuse for teaching. It included specific timing, emotionally charged language, interpersonal conflict, childhood history, and moment-by-moment dialogue. While clinically meaningful, it was too dense, too specific, and too unstructured to function as a training exemplar.
Using the FPN Practice Tool, that same content was transformed into a free-verse clinician narrative. The rewritten version retained the functional heart of the session: a moment of emotional reactivity, the protective function of distancing behaviors, the historical learning that shaped those strategies, and the client’s movement toward values of connection and openness. At the same time, identifiable details were softened or removed, chronology was clarified, and interpretation was grounded in observable patterns rather than diagnostic conclusions.
Importantly, the tool did not add insight that was not already present. Instead, it revealed what was already there, organizing it around functional principles such as short-term relief versus long-term cost, survival strategies versus current workability, and the distinction between “then” and “now.” This is a key teaching feature: learners can see how much functional data already exists in their sessions once they know how to look for it.
Demonstrating Range and Flexibility
By holding both the original raw material and the cleaned narrative version side by side, the FPN Practice Tool demonstrates its range. The same session can be represented in multiple ways depending on purpose:
- As raw material for learning to spot functional patterns
- As a reflective narrative that models contextual thinking
- As a bridge toward a formal Evoke–Model–Reinforce functional note
This flexibility matters. In real practice, clinicians move constantly between thinking, speaking, and documenting. The tool trains that movement explicitly, helping learners practice translating lived clinical moments into language that tracks function, yearning, and direction, without slipping into interpretation-heavy or content-focused habits.
Rather than teaching clinicians what to think, the FPN Practice Tool teaches them how to see. The transformation from the original entry to the refined narrative shows that good functional notes are not about sounding clinical. They are about staying close to behavior, context, and workability while remaining humane, precise, and teachable.
Areas of Shortcoming and Cautions for Use
While early results suggest the FPN Practice Tool performs with approximately 85 percent functional accuracy based on a small sample of 12 clinicians and roughly 100 submissions, several consistent limitations have emerged that users should understand clearly. These are not flaws so much as predictable tradeoffs of an early-stage, language-driven training system that prioritizes functional coherence over exhaustive completeness.
1. Tendency to Fill Gaps When Information Is Sparse
When the input lacks sufficient contextual or behavioral detail, the tool will sometimes infer or add elements based on internal ACT, FC, and RFT-consistent language patterns. This typically shows up as inferred yearnings, implied functions, or lightly filled intervention steps. While this can be helpful for learning structure, it may create the illusion of greater session clarity than actually occurred. This behavior is actively being addressed, with future iterations designed to more explicitly mark inferred content or leave sections intentionally incomplete when data is missing.
2. Compression When Information Is Dense
The most noticeable limitation appears when users provide a large volume of detail. In these cases, the tool reliably compresses content to keep the output under approximately two pages. This compression improves readability and instructional clarity, but it can result in important session elements being omitted or blended together. For this reason, the tool is intentionally not designed for direct cut-and-paste use into an EMR. It functions best as a thinking and supervision aid, not as a final clinical record.
3. Differential Output Based on Clinician Experience
Ongoing investigation is examining how the tool performs for clinicians who are well-trained in FC, RFT, and ACT compared to those who are newer to these models. Early patterns suggest that newer clinicians tend to receive more explicit structure, guidance, and modeling in the output, while more experienced clinicians receive less explanatory rationale and more concise functional framing. This difference appears to align with the underlying prompts and learning model, which prioritize scaffolding for developing clinicians.
Notably, this evolution reflects a shift in the tool’s purpose over time. While initially developed to help clinicians organize session material, it has increasingly been adapted to meet a growing need for immediate, functionally oriented supervisory feedback. This supervisory function is most visible in how the tool responds differently based on the apparent developmental level of the user, offering more teaching where needed and more economy where fluency is already present.
Training Example
Below is an example of how the FPN Practice Tool can transform dense, real-world session material into a concise, de-identified clinician narrative that preserves functional meaning while improving clarity and teachability.
She came in saying things had been mostly steady. Then she described a moment in the early morning hours, anger waking her up, a recent romantic connection already cut off, then briefly reopened just long enough to say what hadn’t been said. Sharp words were sent, and the door was closed again. She noticed it felt out of character. We slowed it down together. Not a flaw, just a moment. Something spilled and then passed. In her telling, that chapter already felt finished.
From there, her attention shifted outward. She spoke about wanting to practice listening to people, not deeply or dramatically, just enough to find something mildly interesting. An upcoming visit with friends felt like a live context to try being a little more open and a little kinder. She named a small experiment: intentionally engaging with at least one person a few times. When asked what that would look like, she described ordinary movements, light conversation, leaning in, smiling when it fits, softening a habitual guarded expression she often doesn’t realize she’s wearing. We linked this to presence, to connection, to her sense of isolation, and to her hope of becoming more at ease with dating over time.
When we turned toward the guardedness, she first said she doesn’t notice it. Asked again, she named its function clearly. It keeps people away. Unsolicited interaction brings immediate dread, followed by irritation, a sense of being interrupted or intruded upon. That distance works. No engagement required. No risk taken. When we explored the risk side, she connected it to earlier experiences of feeling overlooked and criticized, learning quickly that visibility carried a cost. A quiet rule formed: don’t need, don’t ask, don’t invite. What once helped her survive still shows up automatically. We spent time distinguishing who she had to be then from who she is now, not erasing the strategy, just noticing its age. We played with alternatives through brief role play in a neutral public setting, replaying the same scene with different responses, each time nudging closer to her stated values of kindness, openness, and connection. Nothing dramatic shifted, just more room, and a sense that the armor still exists and that she can choose, sometimes, to loosen it.
*This narration has been modified to keep any identifying information minimized.
At this point, the narrative has been intentionally cleaned but not yet functionally structured. It still reflects the clinician’s felt sense of the session, tracking moments, tone, and relational movement without formally naming patterns, functions, or processes. This is the natural middle space where many clinicians pause, unsure how much to interpret, what to name, or how to organize the material without overreaching.
The FPN Practice Assistant enters here as a translator rather than an author. Its task is to take this narrative and ask a different set of questions of it: What showed up, in context? What behaviors were selected, and what did they do in the moment? What short-term relief and longer-term costs are visible? Where do historical survival rules appear, and what yearning do they point toward? The assistant does not add new content, but it changes the frame, shifting from story to function, from sequence to pattern, and from description to workability.
The output that follows demonstrates this shift. You will see the same material reorganized into a Functional Process Note structure, with explicit attention to context, functional analysis, process-based intervention, and trajectory. This bridge is where experiential language is converted into a teachable, supervisable form while preserving the integrity of the original clinical moment.
Training Simulation Example
Presenting Context – What showed up in session?
Client described a 3 a.m. impulsive interaction with a past “situationship” partner — unblocking, sending angry messages, and then reblocking him. She identified this as “not like me,” and later reframed it as a brief lapse of expression, now seen as a closed chapter.
Current focus shifted to social re-engagement: practicing listening, initiating conversation, and showing kindness in anticipation of a trip with friends.
She identified a pattern of keeping emotional distance through her “resting bitch face,” which she linked to childhood experiences of maternal criticism and feeling like a nuisance.
Problem Severity Rating: 6/10 (moderate distress, increasing awareness and motivation for change).
Life domains touched: Love (relationship rupture), Play (social connection), Self-care/Health (emotional regulation).
Functional Analysis – What functional patterns are present?
Trigger (Time–Trigger–Trajectory):
Late-night ruminative anger triggered by betrayal cues → urge to regain control through verbal attack → immediate relief → subsequent regret and withdrawal.
Function:
Anger and blocking served an avoidance and protective function — to reduce vulnerability and preempt further rejection.
The “resting bitch face” operates as a rule-governed avoidance strategy (“Keep people away so they can’t hurt or dismiss me”).
Historical Rule Extraction:
From early shaping experiences: “If I don’t show need, I can’t be criticized.”
Rules likely derived from chronic maternal invalidation and performance-based worth.
Resultant survival strategy: emotional numbing, self-protection via aloofness, avoidance of unsolicited engagement.
Core Yearning:
Belonging — connection and acceptance without the cost of exposure to criticism.
Process-Based Intervention – What ACT process was targeted?
Evoke:
Invited client to revisit the blocking episode as a moment of pain and yearning for fairness rather than moral failure.
Elicited awareness of protective anger as a short-term move that closes off longer-term closeness.
Explored bodily experience of “instant dread when someone talks to me.”
Model:
Clinician differentiated her-then (child adapting to invalidation) from her-now (adult seeking closeness).
Used role-play (train-station vignette) to model alternative relational moves — leaning in, soft facial affect, curiosity — linking these to values of connection and kindness.
Introduced the idea of “creative hopelessness”: noticing the limits of control strategies (avoidance, withdrawal) in creating genuine safety.
Reinforce:
Reinforced awareness that the “I don’t give a f***” stance once protected but now restricts vitality.
Praised her plan to practice kind, open micro-engagements (three conversations during the trip).
Framed this as committed action toward the yearning for belonging — building social safety through presence rather than distance.
ACT Processes Engaged:
Defusion (from self-rules of rejection), Acceptance (allowing discomfort of contact), Present-moment awareness (noticing bodily cues), and Committed Action (intentional softening and approach).
Trajectory & Tracking – How does this connect to past sessions or future directions?
- Behavioral indicator: Client will track number of intentional, value-consistent social interactions (goal: ≥3 new conversations).
- Qualitative cue: Reports of emotional openness or reduced dread during engagement.
- Future direction: Continue examining old “keep-away” rules; introduce metaphor (e.g., armor vs. bridge) to deepen defusion; strengthen willingness to feel exposure while staying connected to values.
Teaching Reflection:
Notice how the “resting bitch face” was understood not as attitude but as a historically shaped protective act-in-context. The intervention closed the loop between yearning (belonging) and process (present, open, kind engagement). The therapist used functional precision — evoking safety strategies’ short-term relief and long-term cost — to model workable flexibility.
Do not use this output in clinical documentation or treatment. Reflect on what functional principles you notice here.
Closing statement
The FPN Practice Tool is best understood not as a documentation shortcut, but as a thinking partner designed to strengthen functional seeing. It helps clinicians slow down, notice patterns, and translate lived clinical moments into process-based language that supports learning, supervision, and coherence. Its value lies less in precision and more in direction, helping users orient toward context, function, yearning, and workability rather than content or correctness.
Used thoughtfully, with awareness of its limits, the tool can sharpen clinical reasoning, support developmental growth across experience levels, and reinforce the stance at the heart of FC, RFT, and ACT: behavior always makes sense in context, and our task is to learn how to see it clearly enough to move wisely.
Leave a comment