Watch any process closely and you find the same pattern. Work gets done by one person, written up, and passed to someone else. At each pass, some of what the first person knew does not survive the write-up.
That loss is invisible, because what arrives looks complete. The receiving person has a document. It reads fine. They have no way to know what did not make it in.
Then the review happens three steps later, against the document rather than the work, and by that point the person who could have answered the question has moved on.
The compression nobody accounts for
A developer solves a problem and writes a commit message. An engineer diagnoses a fault and fills in a job sheet. A clinician examines a patient and types a note.
In each case, a rich understanding gets compressed into a few lines under time pressure, by someone who already knows the answer and is writing for themselves rather than for a stranger six months out.
The compression is not careless. It is what happens when the cost of writing more falls on the person who needs it least.
What the loss measures, when someone measures it
US healthcare has the most thoroughly audited version of this, because a federal agency publishes the results.
Clinical notes drive how insurers get paid for covering patients. Software reads those notes months later and works out which diagnoses should have been recorded. Classic post-handoff review.
The US Office of Inspector General found that across diagnosis codes it considers high risk, roughly 70 percent were not supported by the associated medical records, some categories above 90 percent. In one audit of 97 records carrying an acute stroke diagnosis, none were supported as acute strokes by the documentation. In 68 of those cases the patient had genuinely had a stroke, years earlier, and the record described it as current.
No fabrication anywhere. A temporal detail the clinician knew, which the note did not carry, reconstructed wrong by a system reading the note.
Why reviewing later cannot recover it
Here is the structural bit. A review that happens after the handoff can only assess the document. It cannot access what the document left out, because that information existed in one person’s head at one moment and was not written down.
So later review finds formatting problems, internal contradictions and missing fields. It cannot find the thing nobody recorded. More thorough review does not help. The information is not there to be found.
Which means the only place to fix a handoff loss is before the handoff.
What moving the review earlier looks like
In healthcare this is called concurrent hcc coding, reviewing documentation during the episode of care rather than after the claim has gone out. The clinician is still available, the patient is still there, and a missing detail costs ten seconds to add rather than a reconstruction to recover.
The same move works anywhere with the same shape.
- Review while the person who did the work is still available to ask. The whole value is the question you can only ask at the moment.
- Prompt at write-up time rather than inspecting afterwards. A field that asks for the thing people habitually omit beats a reviewer noticing it is absent weeks later.
- Measure how often your reviews result in a question going back to the originator. If that number is near zero, your review is checking documents rather than work.
Handoff loss is not a discipline problem and more training will not fix it. It is a timing problem, and timing is the one thing a process owner can actually change.
Write and Win: Participate in Creative writing Contest & International Essay Contest and win fabulous prizes.
About the Author
