A note written in a routine outpatient visit can end up read aloud in a courtroom years later, phrase by phrase, by an attorney asking exactly what a specific word was meant to convey. That’s playing out right now in an ongoing Massachusetts murder trial, where a treating psychiatrist has been cross-examined at length about her own chart notes — including one widely reported exchange over a note reading “not hyper, pressured speech,” and what exactly the word “not” was meant to modify. The trial is still underway and this piece isn’t about the facts of that case, which remain for the court to decide. But the documentation question underneath it is universal, and it’s worth residents learning the lesson now rather than discovering it years into practice: your notes will be read, eventually, by someone whose job is to find the gap between what you meant and what you actually wrote.

Why ambiguous negatives are a specific, avoidable trap

“Not hyper, pressured speech” is genuinely ambiguous on the page in a way it wouldn’t be in conversation — does it mean “not hyper; [yes,] pressured speech,” or “not [hyper, pressured] speech” (i.e., neither hyper nor pressured)? You know what you meant when you wrote it. A reader six months or six years later, without access to your intent, doesn’t. This is a broader category worth watching for in your own notes:

• Negatives modifying a list are the highest-risk construction. “No fever, chills, nausea” can be misread as only the first item being negated once it’s separated from context. When documenting the absence of multiple findings, consider explicit structure: “Denies fever. Denies chills. Denies nausea,” or a clearly formatted list, rather than a comma-strung negative that requires the reader to correctly infer scope.
• Qualifiers need their own words, not shared punctuation. If you mean two things are both absent, write both as clearly negated. If you mean one is present and one is absent, that contrast needs to be unambiguous, not implied by word order.
• Read your own ambiguous constructions the way an adversarial reader would, not the way you meant them. This is an uncomfortable habit to build, but it’s exactly the skill that prevents your intent from being relitigated by someone else years later.

The myth of the “bulletproof note” — and the real risk of over-documentation

A common reaction to any high-profile documentation controversy is a swing toward “write everything, protect yourself with volume.” This is understandable and largely wrong as a strategy. A few reasons:

• A note that’s mostly defensive boilerplate is harder to trust, not easier. Excessive templated language, especially language that looks copy-pasted or AI-generated without real clinical customization, can read to a reviewer — clinical or legal — as evidence you weren’t actually engaging with the specific patient in front of you.
• Volume doesn’t protect against ambiguity — it can multiply it. A ten-line note with one ambiguous negative is a smaller target than a fifty-line note with several, generated in part from a template you didn’t fully tailor.
• AI-generated note bloat is a growing, specific version of this risk. AI scribing and drafting tools can produce fluent, plausible-sounding documentation that doesn’t actually reflect your clinical reasoning accurately unless you review and edit it carefully. A note that reads confidently but doesn’t match what you actually assessed is a liability, not a protection — the appearance of thoroughness isn’t the same as accuracy, and a reviewer who catches the mismatch will trust the rest of the note less, not more.

There’s no such thing as a note that’s immune from scrutiny. The realistic goal is a note that accurately reflects your actual clinical reasoning in the moment, in language a future reader — clinical or legal — can’t easily misread.

What documenting clinical reasoning actually looks like

The most legally and clinically useful thing a note can capture isn’t just findings — it’s your reasoning: what you considered, why you ruled things in or out, and what you’d watch for. A few habits that build this in:

• State your differential and why you’re not pursuing the alternatives, briefly, rather than only recording your final impression. “Considered mania given elevated mood; speech not pressured, no flight of ideas, no decreased need for sleep reported — findings inconsistent with manic episode at this time” documents both the finding and the reasoning behind it, which is far more defensible and far more clinically useful than the finding alone.
• Document what the patient understood, not just what you told them, for anything involving informed consent or safety planning. “Patient verbalized understanding of warning signs and agreed to contact [specific resource] if symptoms worsen” is meaningfully different from “safety plan discussed” — the first shows engagement and comprehension; the second only shows that words were exchanged.
• Record follow-up and escalation plans explicitly, including who is responsible for what. Ambiguity about whether a follow-up call, referral, or safety check was the treating physician’s responsibility or another team member’s is a recurring theme in cases where care coordination is later scrutinized.

Dotphrases and templates: useful, but only if they carry your actual judgment

Structured templates and saved phrases are efficient and, used well, improve consistency and legibility — which are themselves protective. The risk isn’t the template; it’s using it as a substitute for actually documenting the specific patient’s specific presentation. A dotphrase for a standard mental status exam is fine as a starting structure. A dotphrase that gets used unedited across patients with meaningfully different presentations is a liability generator, because it creates a paper trail that doesn’t match reality — exactly the kind of gap that becomes the subject of a cross-examination years later.

A practical middle path

Between “document everything defensively” and “don’t let liability anxiety change how you practice,” the more useful standard is: write notes that accurately and specifically reflect your actual clinical reasoning, in unambiguous language, without either padding them defensively or leaning on templates you haven’t actually customized to the patient in front of you. That standard protects patients (because it reflects real clinical thinking, not boilerplate) and protects you (because accuracy, not volume, is what actually holds up under scrutiny).

You won’t get every note perfect, and no resident does. But two specific habits — checking your negatives for ambiguity, and making sure your documented reasoning actually matches your real clinical thinking rather than a template — address the two failure modes that come up again and again when documentation ends up under a microscope. Build them now, while the stakes of any individual note are lower, rather than under pressure later when they aren’t.