Reread your draft and it looks clear. It will always look clear. You are reading it with the answer already installed, and there is no way to take that back out of your head for the length of a paragraph.
Care does not fix that. Procedure does — mechanical tests standing in for a perception you do not have.
You cannot proofread for what you already know
Once you know a thing, you cannot reconstruct not knowing it. Reading your own draft, your mind supplies every missing premise silently and instantly, every time.
Which breaks the standard revision move. Reading it back to see whether it is clear catches typos, tangled sentences and wrong tone, and cannot catch a missing premise — rereading is the exact activity in which the missing half gets supplied for free.
So substitute procedure for perception. The tests below ask you to notice nothing.
Expand the shorthand, especially "the"
Acronyms and internal names first. Every proper noun gets a few words of apposition on first use — "Atlas (the billing rewrite we started in spring)".
The harder one is the definite article. "The migration." "The client." "The outage." Each "the" claims the reader already knows which one you mean, and it is the most common way a draft quietly addresses somebody other than its recipient. Sweep for every "the" attached to a noun you have not introduced. Each hit is either a repair or proof you were writing to a colleague who is not on this message.
Shorthand resists detection because from the inside it feels like precision. To the reader it points into a memory they do not hold, which is why context does not transfer on its own.
Before: Blocked on the migration until Dana signs off, can you push?
After: We are moving customer billing off the old system this month, and it cannot start until Dana in finance approves the new refund policy. Could you ask her today?
Name people by role, not just by name
"Priya says it cannot ship" gives a cold reader nothing to work with. Is Priya the person who decides, the person doing the work, or the person who worries?
"Priya, who runs our release process, says it cannot ship" tells them whether to argue.
Names carry authority only inside the group that already knows them; outside it they are noise with a capital letter. The same goes for vendors and systems — "Northbridge, our payroll provider" converts a mystery into a fact for three words.
Say the obvious thing once
The most reliably omitted sentence in any handover is the one that felt too obvious to write. What the project is for. Which constraint is the real one. Why the obvious option is off the table.
It felt obvious because everyone in the room knew it, and the reader is not in the room. "Everyone involved already knows this" is the criterion for including it, not for cutting it. One sentence is the cost. Omitting it costs a round trip if you are lucky, and a confident answer to a question you did not ask if you are not.
Read it as someone with two minutes to answer
The last pass is a role-play, not a judgement. Read the draft as someone with no history and two minutes who has to produce an actual answer — not "does this make sense" but "could I answer this right now".
Then write down the questions that reader would have to ask. Three questions is three sentences you owe them. This works where rereading fails, because it produces a list instead of a feeling.
Better, if you can spend a favour, hand it to someone uninvolved and ask what you are asking them to do — never whether it is clear, which only gets you politeness.
Over-explaining is its own failure
Write every message as if to a stranger and you burn the one advantage a working relationship has. Shared context is what makes short messages possible between people who talk daily; explaining Atlas to the person who named it reads as condescension, and the padding buries the ask.
So the skill is calibration, not thoroughness. The question is not whether the reader was told something but whether they could reconstruct it now, without you. Told once in a meeting six weeks ago is not held.
Two rules of thumb survive contact. Warmth decays — someone who lived inside a project a quarter ago is warm on the shape and cold on the details — and a message with several readers is written for the coldest one. Neither error is free: wrong-warm costs a round trip, wrong-cold costs tone. With strangers, err cold. With people you speak to weekly, err short and let the first two lines carry the triage.
What a briefing does about it
A RelayLink briefing gives this problem two fields. The context brief is background for someone holding none of your history, and the assumptions list attacks the obvious-thing failure — each one marked as stated by the sender or inferred by the sender's AI, so a reader can correct a premise instead of answering around it.
Two honest limits. An assistant that sat through your session inherits your context and is not immune to any of this; what it lacks is your standing knowledge, which is why its inferred assumptions deserve the hardest read. And the stated-by-sender tag is set by the drafting model, not checked by the server — the only label the server derives for itself is the one on your note.
Take the last message you sent outside your team and run the definite-article sweep on it. If more than a couple of those "the"s point into your own head, you have found why the reply took three days. Connect your assistant if you want the cold version drafted from a session you already worked through — the calibration stays yours.