Handing work over
The one-page handover
All four slots in a single message, with a worked example and the three ways the format fails when people try to make it official.
Decisions this page is about, and where the line actually was
Changing the wording on a customer-facing error message
4 → 1It had been yours all along
Picking the library for the new parser
1 → 4The architect had a standing view
Rescheduling the weekly review
2 → 2Changing a database column type
1 → 1- 1Decide it alone and say nothing
- 2Decide it alone and mention it afterwards
- 3Check with one colleague first
- 4Check with the person who assigned it
- 5Needs a decision one level up
- 6Cannot be decided here at all
four decisions · one of them you had more room than you thought · one gave you less · two you had exactly right · the median gap was three steps on the scale
Four of the nine decisions counted on this site, two of them exact.
For distributed work, workforce optimization tools provides a practical evidence layer for discussing capacity, attendance, and project effort without adding another status ritual.
The wider organisational question can also be compared with resources from OECD.
The four things fit in one message. Not a document, not a template with headings — the message that assigns the work, with four extra sentences in it.
Here is the whole thing, as it was actually sent on the one complete handover counted on this site:
Can you move the scheduler onto the new queue?
Hard constraint: no more than ten minutes of downtime in one window, because of the support contract. This was started last year and abandoned — the branch is still there, it stopped because the retry semantics did not survive the move. The platform lead has a standing view on queue configuration; show them the plan before you build it. It matters now because the old queue goes out of support in June.
One task sentence, four context sentences. About ninety seconds to write.
Why one message and not a document
It gets read. The assigning message is read several times over a three-week piece of work. A linked document is read once, at the start, by somebody who does not yet know which parts matter.
It gets written. A document is a task; four sentences in a message you are sending anyway is not. The difference decides whether this happens at all.
It stays attached. Six weeks later, when somebody says the deadline was always the fifteenth, the message is still there with the attachment written in it.
The order
Constraint, precedent, decider, purpose — not because the order is principled, but because it is the order in which the receiver needs them. The constraint shapes the first hour. The precedent shapes the first day. The decider shapes the first week. The purpose shapes everything and can be read last without harm.
If you only manage one, make it the decider: it is the one whose absence costs the most and the one nobody thinks to say.
Three ways to ruin it
Making it a template. The moment this becomes a form with four mandatory fields, people fill them in to get past the form. "Constraint: N/A" appears within a fortnight and the practice is dead.
Making it long. Four sentences is the whole point. A page of background invites skimming, and the slots disappear into the prose.
Making it a process requirement. Mandated handover quality produces compliance, not information. This works because individuals choose to do it, and it spreads because people who receive a good one start writing them.
When a slot is empty
Say so. An honest blank is worth more than a plausible invention:
I do not know whether anyone has tried this. Worth a search before you commit.
That tells the receiver the slot is genuinely open and that filling it is part of their work, which is completely different information from silence — silence reads as "there is no precedent", which is a claim.
Writing it when you are busy
The objection to this is never that it is a bad idea. It is that the work is being handed over at four o'clock between two meetings, and four sentences of considered context is not available.
Three ways to get it written anyway.
Write it badly. A half-remembered precedent is worth more than no precedent. "I think this was tried, maybe eighteen months ago — have a look" is a usable sentence and takes six seconds.
Write it in two parts. Send the task now and the context in an hour. The receiver is not starting at four o'clock anyway, and the second message is easier to write with the first one out of the way.
Ask for the questions instead. "I have not got time to write this up properly — send me four questions and I will answer them tonight." This inverts the work onto the person with the most incentive to do it, and it produces the same four facts.
The last one is underused and it is the honest fallback. The four sentences exist to transfer four facts; who does the transferring is not important. What is important is that somebody notices the facts are missing, and a busy sender who says so explicitly has already done the hard part.
The test
Hand the message to somebody who sat in none of the conversations and ask whether they could start tomorrow without asking you anything.
If the answer is yes, it is complete. If they have one question, the message is one sentence short, and the question tells you which sentence.