At the end of a shift you write to remember: shorthand, half sentences, the minimum. That works while the reader is the same person. Whoever walks in at seven reads the same words without the context that held them together, and the difference between a useful handover and a useless one sits entirely there — not in how hard the writer tried.
None of the bad versions comes from carelessness: every one was written by somebody in a hurry who already knew what they meant.
After: 214 not sellable: leak under the basin. Reported to maintenance 10:15. Front office decides before arrivals.
What changed: The first one is true and useless: it makes the incoming shift walk the floor to find out what. The second can be acted on without asking anyone.
After: 302: duct noise between 23:00 and 01:00. Room change promised tomorrow if it repeats. Front office AM checks at 08:00.
What changed: When a guest is involved a fifth item is needed on top of the four: what they were promised, in the words they were given.
After: Spa: chlorine probe out of range at 22:00, pool closed 22:30. Reopens only after maintenance verifies. If not verified by 09:00, tell management.
What changed: «Check» is a task with no exit condition. The good version also says when the thing stops being an operational matter and becomes a management one.
After: 118: allergy passed to the restaurant on the 3rd, confirmation received.
What changed: The name helps nobody who reads it and does not belong in a handover: it is already in the PMS. What the next shift needs is that the restaurant knows and answered.
After: Closed: corridor light replaced, 2nd floor. Verified by maintenance 07:40.
What changed: With no verified closing line the same thing gets reported again by the next shift, and the second report looks like a new problem.
Something solved and not written down as closed comes back: the next shift reports it, and the second report looks like a new problem. One line is enough — what was done, who verified it, at what time — and the double work disappears. It is also the only way to notice that something keeps happening: with no record of the closure, every time looks like the first.
You downloaded “How to write a shift handover”. The file remains free to adapt; the pack explains when a broader scope may be worth evaluating.
The download sends no data. To describe a workflow, use the separate contact page. Contact
The pack summarises the ten domains, required inputs, core boundaries and questions to verify. The download requires no email and sends no data.