What the Shift Handover Note Builder does
This builds a structured shift handover: plant status, what was done, open jobs with owners and due dates, isolations still in place, permits left open and any safety concerns. It produces a printable note and a copyable message, and it checks the things a handover goes wrong without.
The isolation section always appears, even when there is nothing in it, because an empty section and a missing section read completely differently at two in the morning. If nothing is isolated, the note says so in those words.
Nothing is generated or rewritten - the note contains what you typed - and nothing leaves your browser.
How to use it
- Set the date, the shift and the area, and name both people. A handover with only one name on it is a note, not a handover.
- Write the plant status: what is running, what is down, and what is running but not right. The third category is the one that gets left out and the one that causes the next breakdown.
- List the work done, one line each. Then list open items as item, owner, due date and priority - the owner is what turns an open item into something that will actually happen.
- Record every isolation still in place with its tag, the equipment, who applied it and why. If there are none, leave the box empty and the note will say so explicitly.
- Add open permits and safety concerns, then copy the note into your handover system, print it, or download it as Markdown.
Reading the results
Open items without an owner are flagged. Nobody comes on shift and adopts an orphan job; naming a person or a trade group is what makes the item survive the handover.
Isolations and open permits are counted separately from open items because they are a safety state, not a work list. Somebody on the incoming shift has to know about every one of them before touching anything.
The completeness check is an A2Z convention for a note the next shift can act on, not a compliance requirement. Your site's procedure decides what a handover must contain.
A quiet shift still deserves a note. 'Everything ran, nothing outstanding, no isolations' takes thirty seconds to write and is exactly the record that proves the state the plant was left in.
Worked example: a night shift in a packing hall
Plant status: lines 1 and 3 running normally; line 2 down awaiting a gearbox expected at 10:00; the baler running but with a high hydraulic temperature to watch. That third clause is the useful one - it is not a breakdown, and it is not nothing.
Work done: an idler roller replaced on CV-101, three jams cleared on the L3 infeed, hydraulic oil topped up on the baler.
Three open items. Fitting the new gearbox to the L2 drive is P1 and owned by day shift mechanical. Investigating the baler hydraulic temperature is P2 with the same owner. Ordering a replacement guard for L3 is P3 - and has no owner, so the note flags it: someone will have to be named or it will still be open next week.
One isolation remains: LO-214 on the L2 drive motor, applied by R. Ali for the gearbox removal. One permit is open, hot work HW-77 until 06:00.
One safety concern: water on the floor by the wash bay, cones placed and the cleaner informed. Writing it down is what makes it the next shift's problem too, rather than a hazard only one person knew about.
Why handovers fail
Investigations into major process-safety incidents keep finding the same contributor: a shift change where information about an abnormal state was not passed on, or was passed on verbally and not understood. The Piper Alpha inquiry is the best-known example, where a permit for work on a pump was not effectively handed over and the pump was later started.
The practical lessons are unglamorous. Write it down as well as saying it. Cover the state of the plant, not just the events of the shift. Be explicit about what is isolated and what permits are live. And make the handover a conversation with the written note in front of both people, rather than a note left on a desk.
The three states a machine can be in
Running, down, and running-but-wrong. Most handover forms have room for the first two and quietly lose the third, which is where the next breakdown usually comes from: the bearing that is warm, the line running at reduced speed, the sensor that needs a wipe every hour.
Writing those down has a second effect. A machine that has appeared in the running-but-wrong paragraph for five shifts in a row is a work order that should have been raised on the first one, and the handover note is the evidence that makes that case.
Limitations: what the result does not prove
- It produces a note from what you type. It is not a permit hand-back, an isolation certificate or a control-of-work record, and it does not replace any of them.
- The completeness check is a convention for a usable note, not your site's procedure. Where the two differ, the procedure wins.
- Nothing is stored. Closing the tab loses the note, so copy, print or download it before you finish.
- A written note is half of a handover. The other half is the face-to-face conversation with the note in front of both people, and no template can supply that.
Privacy: where your data goes
Everything you paste, type or drop is processed in this browser tab. It is not uploaded, logged, stored or sent to analytics. Session recording and tag-manager scripts are switched off on this page.
Standards and sources
- IEC 60300-3-11 - Dependability: reliability centred maintenance - checked 19 Sep 2026
- HSE - Safety critical communications: shift handover (Human Factors)
- ISO 22400-2 - Key performance indicators for manufacturing operations management
Frequently asked questions
What should a shift handover note include?
Date, shift, area and both names; the plant status, including anything running but not right; work done; open items with owners and due dates; isolations still in place; open permits; and safety concerns. The isolations and permits are the parts that matter most and are most often skipped.
How long should a handover take?
Long enough to cover the abnormal states, which on a quiet shift is a couple of minutes and after a bad one can be twenty. What matters more than the duration is that it is done with the written note in front of both people, rather than shouted across a changing room.
Why record isolations that the next shift can see for themselves?
Because they cannot. A lock on a motor starter in a substation is not visible from the line, and an isolation applied for a job that has since been paused is exactly the one that gets forgotten. Writing every one down, with who applied it and why, is the whole point of the section.
Should a quiet shift still write a handover?
Yes, and it takes half a minute. A note saying everything ran, nothing is outstanding and nothing is isolated is a record of the state the plant was left in - which is what you need if something is found wrong two shifts later.
What makes an open item actually get done?
A named owner and a due date. An item written as a description of a problem with no owner is a wish; the same item assigned to day shift mechanical for Friday is a job. This page flags unowned items for that reason.
Is a verbal handover enough?
No. Verbal handovers lose detail immediately and leave no record of what was said. The written note is both the memory aid during the conversation and the evidence afterwards - which, after an incident, is the only version anyone can examine.
Can I paste this into our handover system?
Yes. Copy it as plain text for a form field, or as Markdown for a wiki or ticketing system. You can also download the open items as CSV if they need to be loaded into a tracker separately.
Is anything I type sent anywhere?
No. The tool runs entirely in your browser, which is deliberate: a handover note names people, faults and safety concerns, and none of that should leave the site.
Last reviewed by the A2Z.Tools team against the sources listed above.
