Here's a quick gut-check for any assessment summary you write: imagine a co-worker is covering your caseload while you're on vacation, and this summary is all they have to go on. Could they pick up where you left off? Would they understand who this client is, what's getting in the way of their functioning, and how to keep the work moving?
That single test does a lot of work. It pushes you toward clarity, and it quietly filters out the kind of language that doesn't belong in a clinical record in the first place.
An assessment summary isn't a place to record your impressions of someone as a person. It's a working document. Its job is to give anyone reading it — a supervisor, a covering clinician, a treatment team, sometimes the client — an accurate picture of functioning and a usable starting point for the next session.
When you keep the covering co-worker in mind, you naturally write toward function rather than character. You stop describing what the client is "like" and start describing what's happening and how it affects their life.
The biggest pitfall in summary writing is the descriptive label that feels efficient but carries a quiet judgment. Words like "manipulative," "difficult," "noncompliant," "attention-seeking," "resistant," or "unmotivated" all share a problem: they tell the reader how you feel about the client without telling them what the client actually did.
They also tend to stick. Once "manipulative" lands in a chart, the next clinician reads it before they ever meet the person, and it shapes the encounter before a word is exchanged. That's not a neutral act. A label can follow a client across providers and years, coloring care in ways you'll never see.
Compare these two entries:
"Client was manipulative and resistant throughout the session."
"Client declined to discuss the incident at work and redirected the conversation each time it came up. When asked directly, said, 'I don't see why we have to keep going over this.'"
The second one is longer, and it's better in every way that matters. A covering clinician knows exactly what they're walking into. There's no inherited grudge, no diagnosis-by-adjective — just behavior they can recognize and respond to.
Here's the filter that does most of the heavy lifting. Before including an observation, ask whether it bears on one of two things: the client's functioning, or the working relationship.
If a behavior affects how the client manages day-to-day life — sleep, work, relationships, safety, self-care — it belongs in the summary, described concretely. If a behavior shapes the therapeutic alliance — how the client engages, what they avoid, where rapport breaks down — it belongs too, because the next clinician needs to navigate it.
But your private reaction to the client usually fails the test. The fact that a session felt draining, or that you found someone irritating, says more about the interaction than about the client's functioning. If that reaction points to something clinically meaningful — say, the client's interpersonal style consistently pushes people away — then write about the pattern and its impact, not your feeling about it.
Describe behavior, then its effect. "Client has missed three of the last five appointments; engagement with the treatment plan has stalled as a result" gives the reader both the observation and why it matters.
Quote the client where it's illuminating. A short, direct quote often conveys mental status or affect more accurately than your summary of it, and it keeps your interpretation visible as interpretation.
Separate observation from inference. "Client appeared tearful when discussing her mother" is an observation. "Client is grieving" is an inference. Both can be useful, but the reader should be able to tell which is which.
Read it back as the covering co-worker. Would the language make you approach this person with curiosity or with caution you haven't earned? If it's the latter, revise.
This isn't only good practice — it's testable. ASWB questions frequently probe the line between objective documentation and biased or judgmental language, and between observation and inference. You'll see scenarios asking what a social worker should include in a record, or which note is most appropriate, and the right answer almost always favors specific, behavior-focused, functioning-anchored language over characterological labels.
In SWTP's practice tests, you'll see this distinction tested in assessment and documentation items, where the tempting wrong answers are the ones that sound clinical but actually encode a judgment.
Take a recent note — or write a quick one from memory — and circle any word that describes the client as a type of person rather than describing something they did. For each one, ask: what behavior made me write that, and how does it affect their functioning or our work together? Rewrite the line around the answer. That's the whole skill, and it's one you can practice in five minutes.
Documentation questions are some of the most reliably winnable points on the exam, because the underlying principle barely changes from item to item. Once the covering co-worker test is second nature, you'll spot the biased option before you finish reading it.
Right now, get SWTP's online practice exams at a reduced price. Just $39. Get additional savings when buying more than one exam at a time-- less than $30 per exam!
Keep going till you pass. Extensions are free.
To receive our free study guide and get started!