What this is
What is a shift handover, precisely?
What is a shift handover, precisely?
A shift handover is the structured transfer of the operating state of a site — production status, equipment condition, open safety items and anything the next crew must not do — from the outgoing lead to the incoming lead. It is not a status update read out in passing; ISO 45001 cl.7.4 treats it as a communication process that has to be established, implemented and maintained like any other control.
Why does a handover need a signature from both leads?
A single signature only proves the outgoing lead wrote something down. Two signatures prove the incoming lead heard it, understood it, and is now accountable for acting on it — that second signature turns a note into a transfer of responsibility.
What is the difference between a handover and a shift start-up check?
A handover closes out the shift that just ended; a start-up check opens the one about to begin. They sit either side of the same moment and belong to different people — the outgoing lead owns the handover, the incoming lead owns the check.
Scope
When is an operations shift handover required?
This record is the transfer point between two shifts, not a general operations log. Using it to plan the next shift, authorise overtime, or record a start-up walk produces a handover nobody can trust, because the fields that matter get buried under work that belongs somewhere else.
Use this template when
- A shift is ending and the operating state — production, equipment, people, safety — needs to cross to the next lead before anyone leaves the floor
- The outgoing and incoming leads are both present, or a documented alternative arrangement for their absence is in place
- Open items from a previous handover need to be checked off, or carried forward with a stated reason
- A linked record needs this one to exist first: the Downtime Log, the Escalation Log or the Production Report
- You are running the Shift Management programme and this is the step that closes one shift and opens the next
Do not use it for
- Shift Start Up Check (OPS-002), which confirms the area, the people and the equipment are ready before the shift starts producing — the incoming lead's record, not the outgoing lead's.
- Manning and Labour Plan (OPS-003), which sets who is working where for a shift against the competencies each position requires, ahead of the shift starting.
- Shift Performance Log (OPS-005), which tracks rate and output through the shift, rather than the state passed at its boundary.
- Escalation and Andon Log (OPS-006), which is the live record an open escalation should be logged against, not re-described inside the handover.
- Anything outside KnowOps, which belongs in the workspace that owns that process.
Compliance mapping
Which ISO 45001 cl.7.4 requirements does this satisfy?
ISO 45001 cl.7.4 covers communication in general terms; the sub-clauses below map onto the sections this template actually asks for, rather than the clause's full text.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 45001 cl.7.4.1 | Establish, implement and maintain a process for internal and external communication relevant to the OH&S management system, including what, when and with whom. | Header |
| ISO 45001 cl.7.4.2 | Internal communication among levels and functions must be initiated whenever there is a change affecting OH&S, including the routine change of shift. | Production |
| ISO 45001 cl.7.4.2 | Relevant OH&S information — faults, temporary fixes, work orders, manning gaps — must be communicated between those affected, not just recorded. | Equipment and people |
| ISO 45001 cl.8.2 | Arrangements for emergency preparedness, including the status of isolations and permits still in force, must be communicated to those affected. | Safety and open items |
| ISO 45001 cl.10.2 | Incidents and nonconformities identified during operation must be captured and carried into corrective action, not left to lapse at the changeover. | Safety and open items |
| ISO 45001 cl.5.4 | Consultation and participation of workers — the incoming crew's understanding must be confirmed, not assumed on the strength of a signature alone. | Outcome |
| ISO 45001 cl.9.1.1 | Monitor and measure OH&S performance; applied here as the tracked rate of completed, understood handovers rather than merely submitted ones. | Outcome |
What it does not cover
- A verbal-only handover with nothing logged, which leaves no record for the next shift, the next auditor, or the next incident investigation to check against.
- Every topic marked Yes without a face-to-face conversation, which turns the form into a formality completed after the fact from memory rather than a live transfer of state.
- A handover signed before the incoming lead has walked the line, which confirms understanding of a document, not of the plant it describes.
- Open items logged as N/A because nobody actually checked, which hides a gap behind the one option that isn't supposed to carry a score.
- A handover completed by someone other than the outgoing and incoming lead, which breaks the chain of accountability the record exists to create.
Global
Operations Shift Handover requirements by country
A shift handover reads differently depending on what it must be evidence for.
HSE HSG191 — Effective shift handover
Not law itself, but the guidance HSE inspectors reference when judging whether a documented handover process is adequate under the general duties of the Health and Safety at Work etc. Act 1974.
An inspector reviewing a UK site after an incident will ask for the handover record covering that shift and compare it against HSG191's recommendations, even though the guidance carries no direct legal force.
OSHA 29 CFR 1910.119(f)(4)
A hard requirement on sites covered by Process Safety Management — the rule text specifies that information shall be communicated between operating shift personnel before shift change.
On a covered PSM site, a missing or incomplete handover record isn't a quality gap, it's a citable gap against a named paragraph of a federal standard.
ISO 45001 cl.7.4
The clause this template is built against; certification bodies test the handover record as primary evidence the organisation's internal communication process is real, not a policy statement nobody follows.
An auditor sampling records across several shifts tests consistency of practice, not the wording of one record — a policy that only holds on the days someone remembers fails the sample.
How to complete it
How to complete an operations shift handover, step by step
The fields decide whether the form was filled in. These four decide whether the record would hold up under reliance.
Face To Face answered Yes is the only field on this form that speaks to method rather than content. A handover completed by phone, by text, or from a note left on a desk with Face To Face marked Yes anyway is a record that misrepresents its own reliability — the first thing to check before trusting anything else on it.
Every scored field in Production, Equipment and people, and Safety and open items is a completeness question, not a condition question. Reading Incidents Or Near Misses as Yes equals good news is the single most common misread of this template — one that would let a genuinely bad shift score well because everything on it happened to get discussed.
Open Items Carried Forward only means something if it connects to something else — a Downtime Log ID, an Escalation Log ID, or a CAPA reference raised off the back of it. A non-zero count with no linked reference is a number with nowhere to go, and it stays unexplained three handovers later.
Incoming Lead Confirmed Understanding is answered by the person receiving the shift, and it's the field most likely to be signed on trust rather than substance. A confirmation sitting next to several safety fields reading No is worth a second look before the record is treated as closed.
What auditors find
Most common operations shift handover findings
Patterns worth an automated check, not things a reviewer catches reading one form at a time.
| Finding | Clause | What fixes it |
|---|---|---|
| Face To Face recorded as No with no reason captured anywhere on the record | ISO 45001 cl.7.4.2 | Add a mandatory reason field whenever Face To Face is No, and route it to the site OH&S lead rather than letting the record close silently. |
| Open Items Carried Forward is above zero but neither log ID field is populated | ISO 45001 cl.10.2 | Make at least one log reference mandatory whenever the count is above zero, so an open item is always traceable to a record that owns it. |
| Incoming Lead Confirmed Understanding reads Yes on a record where three or more safety fields read No | ISO 45001 cl.5.4 | Flag any confirmation of understanding against a record carrying multiple open safety items for a second read by the site lead before it counts as closed. |
| Handover Time recorded later than the Incoming Shift's rostered start | ISO 45001 cl.7.4.1 | Compare Handover Time against the roster automatically and hold the record open until the gap is explained. |
| Anything The Next Shift Must Not Do answered No alongside an Action Required of Yes | ISO 45001 cl.9.1.1 | Cross-check these two fields at submission — a live action rarely coincides with a clean nothing-to-avoid answer, and the mismatch should hold the record for review. |
| Score Percent above 90 on a submission where Completeness Percent is below 70 | ISO 45001 cl.9.1.1 | Suppress the headline score whenever completeness falls below a set floor, so a high score can't be read off a form mostly left blank. |
Case in point
Case in point: the filler that stuck all shift
The Info field on this template exists because of one recurring shape of failure: the outgoing shift knows the third filler has been sticking intermittently all night, works around it, and never writes it down because it never became a full stoppage. At handover, Equipment Faults Handed Over gets marked Yes because a fault was mentioned — but Temporary Fixes Explained gets marked Yes too, on the strength of a sentence spoken in passing rather than a description anyone could act on.
Two hours into the next shift, the filler jams properly. The incoming crew treats it as a new breakdown and starts fault-finding from zero — because what actually crossed the handover was the fact that a conversation happened, not the information it was supposed to contain. The record shows a clean Yes. The plant shows otherwise.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- OPS-001
- Archetype
- Record
- Record ID
- HAND-2026-000
- Scoring
- Handovers completed
- Direction
- High is good
- Singleton
- Yes
- Basis
- ISO 45001 cl.7.4
- Links
- Links Downtime Log, Escalation Log, Production Report
- Tags
- Shift, Handover, Communication
- Sections
- 5
- Fields
- 52
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 4
Header
15 fieldsHandover ID*
Auto sequence. Format HAND-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Outgoing Shift*
Incoming Shift*
Handover Time*
Outgoing Lead*
Incoming Lead*
Face To Face*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Where A Known Problem Becomes Unknown
The outgoing shift knows the third filler has been sticking all night. If that does not cross the handover, the incoming shift spends two hours rediscovering it and calls it a breakdown.
Production
6 fieldsCurrent Order And Progress Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Rate Against Plan Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Materials Staged For The Next Order*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Changeover Due In The Next Shift*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Quality Issues In Progress*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Product On Hold Identified*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Equipment and people
6 fieldsEquipment Faults Handed Over*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Temporary Fixes Explained*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Work Orders Open On The Line*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Manning Gaps Stated*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Anybody On Restricted Duties*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Contractors Still On Site*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Safety and open items
6 fieldsIncidents Or Near Misses In The Shift*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Permits Still Open*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Isolations Still In Place*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Escalations Not Yet Resolved*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Spills Or Damage Outstanding*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Anything The Next Shift Must Not Do*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Outcome
19 fieldsHandover Complete*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Open Items Carried Forward*
Incoming Lead Confirmed Understanding*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Downtime Log ID
Links to OPS-010 Log ID
Escalation Log ID
Links to OPS-006 Log ID
Anything Missed From The Last Handover*
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Items Assessed*
Excludes anything marked N/A.
Items Failed*
Score Percent*
Calculated on submission. High is good. N/A items leave the denominator.
Result Band*
- Pass3 pts
- Caution1 pt
- Fail0 pts
Completeness Percent*
How much of the template was actually answered. A high score on a half completed form is not a high score.
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Outgoing Lead*
Signature*
Incoming Lead*
Second Signature*
OPS-001 · record IDs look like HAND-2026-000 · Links Downtime Log, Escalation Log, Production Report
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Catching the pattern across dozens of handovers is the work that actually slips.
Runs the Shift Management programme this handover belongs to, holds the linked Downtime, Escalation and Production records against it, and flags a handover that's clean on paper while Face To Face reads No.
Tracks isolations, permits and incidents across handovers rather than one record at a time, so a topic that keeps reading No — or keeps needing an N/A — surfaces as a pattern, not a one-off.
Picks up Equipment Faults Handed Over and Temporary Fixes Explained, and connects a vague fix mentioned at handover to the work order it should already have opened.
Coordinates the crew across the handover boundary, rolls open items and exceptions into one view for the site lead, and holds every write for approval before it touches a record.
This template lives in KnowOps — frontline execution. Shift handover, production control, daily management, worker lifecycle and improvement.
Meet KnowOps→Glossary
Operations Shift Handover definitions and key terms
- Handover
- The structured transfer of operating state — production, equipment, people, safety — from the outgoing shift lead to the incoming one, at a fixed point in time.
- Isolation
- A physical or procedural means of preventing a machine, circuit or system from being operated, applied before work starts and removed only once it's confirmed safe to do so.
- Permit to work
- A formal, time-limited authorisation for a specific piece of high-risk work, which stays open until the work is signed off as complete or safely suspended.
- CAPA
- Corrective and preventive action — the record raised when something needs fixing at root cause rather than patched, and tracked separately from the event that triggered it.
- Escalation
- A problem raised beyond the level that can resolve it alone, logged with a reference so it can be tracked to closure rather than mentioned once and left.
FAQ
Frequently asked questions about operations shift handover
Does a handover need to happen if nothing went wrong?+
Yes — every shift boundary gets one, regardless of how quiet the shift was. A quiet shift with no handover is indistinguishable, later, from a shift where something happened and wasn't passed on.
What if the outgoing or incoming lead isn't available at the boundary?+
The template still needs both signatures before it can close. A documented alternative — a delegated lead, or a phone handover followed by a face-to-face catch-up as soon as possible — should be the recorded exception, not the silent default.
Why does Open Items Carried Forward matter more than Score Percent?+
Score Percent measures whether topics got covered. Open Items Carried Forward measures whether the operation is actually accumulating unresolved problems across shift boundaries, which is the thing the handover exists to prevent.
Should the handover repeat what's already in the Downtime Log or Escalation Log?+
No — it should reference them. The Downtime Log ID and Escalation Log ID fields exist so the handover points at the record that owns the detail, rather than becoming a second, looser copy of it.
What does N/A mean on a scored field here?+
It means the topic doesn't apply to this shift or area, and it's excluded from the denominator rather than scored as a fail. It should never be used to avoid answering a question that does apply.
Who should be looking at these records after they're signed?+
Whoever owns the Shift Management programme, on a cadence that catches a pattern — the same field answering No repeatedly, or the same open item recurring across several handovers — rather than reviewing one record in isolation.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Shift Management
Shift Fatigue Screening
Screens work patterns for fatigue risk, covering shift length, rotation, breaks and consecutive days
Shift and Crew Register
Holds the shift pattern and crew structure for each area, so records can be grouped by the team that actually did the work
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
Shift Performance Log
Records what the shift actually achieved hour by hour against plan, and why it differed
More in Shift Management
Shift Start Up Check
Confirms the area, the people and the equipment are ready before the shift starts producing
Manning and Labour Plan
Sets who is working where for a shift, against the competencies each position requires
Overtime Authorisation
Authorises hours beyond the planned shift, with the reason and the cumulative position for that person
Shift Performance Log
Records what the shift actually achieved hour by hour against plan, and why it differed
Escalation and Andon Log
Records a call for help from the floor, who responded, how long it took and what was done
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 45001 — Occupational health and safety management systems, cl.7.4
- OSHA 29 CFR 1910.119(f)(4) — Process Safety Management, shift operations
- HSE HSG191 — Effective shift handover: a literature review
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.