What this is
What is a shift handover record?
What is a shift handover record?
A shift handover record is the documented transfer of operational knowledge from an outgoing shift to an incoming one: running products, holds, open deviations, equipment faults, staffing and materials position. It exists so that the incoming supervisor starts from what the outgoing shift actually knew, not from a blank page.
Why does the record require a face-to-face handover method?
Because a written note cannot answer a question, and a question the outgoing shift could have answered in thirty seconds is exactly the detail that gets lost when the only handover is a note left on a desk. The template treats phone as a partial substitute and a written note alone as the weakest form.
What happens to an issue that is still open at handover?
It is recorded with enough detail for the incoming shift to act on it, and where it already has its own record, such as a hold or a work order, the record is referenced rather than re-described. The handover's job is continuity, not re-investigation.
Scope
When is a shift handover record required?
This record is one step in a larger programme. Using it to carry the actual investigation or hold decision, rather than reference them, produces a handover nobody can trust and a linked record nobody can find.
Use this template when
- A shift is ending and production, quality or safety status needs to pass to the next one
- A new handover record is needed; each one gets its own ID in the form HAND-2026-000
- You are running the HACCP and Food Safety programme and this is one of its communication steps
- A linked record needs this one to exist: links job, site
- Staffing, materials or resource position has changed and needs flagging before the next shift starts
Do not use it for
- Hold and Release Record, which manages the actual hold from placement to release; the handover references it by ID rather than re-describing the hold decision.
- Deviation or nonconformance investigation, which carries out the actual root-cause work; the handover flags that a deviation is open and links to it, it does not investigate it.
- Control Plan, which sets out what is measured on a process, how often, by what method, and what to do when it goes out of limits.
- Process Capability Study, which measures whether a process can reliably hold its specification, using data from a stable run.
- Anything outside KnowQuality, since an equipment fault or a staffing gap belongs in the workspace that owns that resource.
Compliance mapping
Which ISO 9001 cl.7.4 requirements does this satisfy?
Shift handover sits inside the general communication requirement most quality systems carry, but it is one of the few places a process-safety regulator names the practice directly and requires a procedure for it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.7.4 | Determining the internal and external communications relevant to the quality management system | Header |
| ISO 9001 cl.8.5.1 | Production carried out under controlled conditions, including availability of monitoring and measuring resources | Production status |
| ISO 9001 cl.8.7 | Identification and control of outputs that do not conform to requirements | Production status |
| ISO 9001 cl.10.2 | Reaction to nonconformity and evaluation of the need for action to eliminate the cause | Open issues |
| ISO 9001 cl.7.1.2 | Determining and providing the persons necessary for the effective operation of processes | Resources |
| ISO 9001 cl.7.1.3 | Determining, providing and maintaining the infrastructure and materials necessary for process operation | Resources |
| ISO 9001 cl.5.3 | Assigning and communicating organisational roles, responsibilities and authorities | Confirmation |
What it does not cover
- Hold and Release Record, which is the actual instrument governing a product placed on hold; the handover references its ID rather than recording the hold decision itself.
- Deviation or nonconformance investigation, which carries out the root-cause work behind an open deviation; the handover flags that it is open and unresolved.
- Work order, which manages an equipment fault or temporary repair to closure; the handover records that one exists and links its ID.
- Control Plan, which specifies what is measured on the process, at what frequency, and the reaction plan for an out-of-limits result.
- Statistical Process Control Log, which trends measurements over time; a single handover cannot show whether an issue is new or a known pattern.
Global
Shift Handover Record requirements by country
Shift handover is usually good practice rather than a named legal duty, with one significant exception in process-safety regulation where it is written into the standard directly.
OSHA Process Safety Management, 29 CFR 1910.119(f)(4)
Covered processes must have written procedures for shift changes, ensuring information is communicated between outgoing and incoming operators.
For sites within PSM scope this is a direct legal requirement, not a quality-system nicety, and an inspector can cite a handover process that exists only in name.
HSE guidance HSG48, human factors and shift handover
HSE identifies inadequate shift handover as a recurring contributor to major incidents and expects a structured handover process as evidence of managing that human factor.
An inspector reviewing an incident that crossed a shift boundary will ask what the handover recorded, not just whether one took place.
ISO 9001:2015 cl.7.4
Certification requires the organisation to determine the internal communications relevant to the management system's effectiveness.
Auditors look for evidence the communication changed what the incoming shift did, not for the existence of a signed form.
How to complete it
How to complete a shift handover record, step by step
The template will prompt for every category of open item. It will not tell you whether the handover actually happened as a conversation, and that is the judgement the record depends on.
Face-to-face, phone and written-note-only are not interchangeable ways of recording the same event; they are different levels of reliability. A record completed by written note only should be treated as a weaker handover regardless of what the rest of the form says.
None against open deviations, equipment faults and safety issues should reflect a deliberate check at the point of handover. A shift closing in a rush tends to default every field to None, and the record cannot then tell a clean shift from one never properly reviewed.
A hold, a deviation or a work order already has its own record with its own detail and ownership. The handover's job is to link to it and note what the incoming shift specifically needs to watch, not restate the investigation, which will drift from the source over time.
Incoming Supervisor Understood marked Yes with Questions Raised still populated in text is a contradiction the form allows but the process shouldn't. Resolve the question before the signature, or the record evidences attendance rather than transfer of knowledge.
What auditors find
Most common shift handover record findings
A shift handover record almost always exists and is almost always signed. The findings concern whether it evidences a conversation or a formality.
| Finding | Clause | What fixes it |
|---|---|---|
| Handover completed by phone or written note only, on a shift with open deviations or safety issues that warranted a face-to-face exchange. | ISO 9001 cl.7.4 | Require face-to-face handover whenever an open deviation, hold or safety issue is present, regardless of shift-end pressure. |
| Open deviation marked Yes with no Case ID recorded, leaving the incoming shift no way to trace what is actually outstanding. | ISO 9001 cl.10.2 | Make the Case ID mandatory whenever an open deviation is logged. |
| Equipment fault or temporary repair flagged with no linked Work Order ID. | ISO 9001 cl.8.5.1 | Require a Work Order ID whenever a fault or temporary repair is recorded, so the incoming shift can verify status directly. |
| Any Product On Hold marked Yes with no Hold ID, breaking the link to the record that actually governs the hold. | ISO 9001 cl.8.7 | Make the Hold ID mandatory whenever a hold is indicated, drawn from the live Hold and Release Record. |
| Incoming Supervisor Understood marked Yes while Questions Raised is populated with unresolved text. | ISO 9001 cl.5.3 | Block sign-off until questions raised are either answered on the record or explicitly deferred with an owner. |
| New or unsupervised staff logged on shift with no corresponding note on what mitigation, buddy pairing or reduced task scope was put in place. | ISO 9001 cl.7.1.2 | Require a mitigation note whenever unsupervised new staff are on shift, not just the flag itself. |
Case in point
Case in point: the handover that was signed and wrong
A bakery's afternoon shift ended with a sanitation issue outstanding on one proofer, noted verbally to the incoming night supervisor at the door, and marked Sanitation Issues Outstanding: None on the written record because the outgoing supervisor considered it already communicated. The night shift ran product through the proofer as normal, with no written trace of the issue anywhere the night crew would see it.
An allergen cross-contact incident three shifts later traced back to residue in that same proofer. The record was internally consistent, correctly signed by both supervisors, and said nothing was outstanding. The gap was not a missing signature; it was a verbal aside treated as equivalent to a documented handover, so the one detail that mattered was never in the record the next shift actually read.
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
- QUA-063
- Archetype
- Record
- Record ID
- HAND-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 9001 cl.7.4
- Links
- Links Job, Site
- Tags
- Process, Communication
- Sections
- 5
- Fields
- 39
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
16 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*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Line*
Shift*
Line Lead
Outgoing Shift*
Incoming Shift*
Handover Time*
Outgoing Supervisor*
Incoming Supervisor*
Handover Face To Face*
A written note left on a desk is not a handover.
- Yes3 pts
- By phone1 pt
- Written note only0 pts
Where Problems Cross Shifts
Most quality problems that survive a shift change started with a handover that did not happen. Cover what is running, what is held, what is broken and what is unusual.
Production status
5 fieldsProducts Running*
Batches In Progress
Planned Changeovers
Any Product On Hold*
- No3 pts
- Yes1 pt
Hold ID
Links to QUA-003 Hold ID
Open issues
9 fieldsOpen Deviations*
- None3 pts
- Yes0 pts
Deviation Detail
Equipment Faults Or Temporary Repairs*
- None3 pts
- Yes0 pts
Work Order ID
Links to MNT-002 Work Order ID
Detection Or CCP Concerns*
- None3 pts
- Yes0 pts
Sanitation Issues Outstanding*
- None3 pts
- Yes0 pts
Safety Issues Outstanding*
- None3 pts
- Yes0 pts
Case ID
Thread key
Anything Unusual This Shift
Odd noises, different smells, unfamiliar readings. Often the first sign of a developing problem.
Resources
3 fieldsStaffing Adequate Next Shift*
- Yes3 pts
- Tight1 pt
- No0 pts
New Or Untrained Staff On Shift*
- No3 pts
- Yes, supervised1 pt
- Yes, unsupervised0 pts
Materials Available*
- Yes3 pts
- Partly1 pt
- No0 pts
Confirmation
6 fieldsIncoming Supervisor Understood*
- Yes3 pts
- Questions outstanding1 pt
Questions Raised
Outgoing Supervisor*
Signature*
Incoming Supervisor*
Second Signature*
QUA-063 · record IDs look like HAND-2026-000 · Links Job, Site
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The record covers one shift change. What actually fails is the chain of them: an issue verbally passed once, never written down, and carried by memory until the memory runs out.
Holds the handover against its linked hold, deviation and work order records, and flags when an open item has no reference the incoming shift can actually check.
Watches for an item marked open on one handover and silently absent from the next, and raises it before it disappears from the record without ever being closed.
Takes safety issues outstanding out of the handover and into the safety workspace's own tracking, so a carried-over hazard gets ownership beyond the next shift's goodwill.
Connects equipment faults and temporary repairs logged at handover to the actual work order, so status is verifiable rather than restated from memory each shift.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Shift Handover Record definitions and key terms
- Handover
- The transfer of operational knowledge from an outgoing shift to an incoming one, covering what is running, held, broken or unusual.
- Face-to-face handover
- A verbal handover conducted in person between outgoing and incoming supervisors, the method the template rates most reliable because it allows questions.
- Open deviation
- A recorded departure from an expected process or specification that has not yet been resolved and closed at the point of handover.
- Hold
- A restriction preventing product from being released or used, governed by its own hold and release record; the handover only flags that one exists.
- Thread key
- A shared reference, such as a Case ID, that links records describing the same underlying event across different templates.
FAQ
Frequently asked questions about shift handover record
Is a written handover note enough on its own?+
No. A note transfers information only if it is found, read in full and raises no questions, and all three routinely fail. The template scores a written-note-only handover at zero, even when the note itself is accurate.
Should every field default to None if nothing unusual happened?+
Only if that reflects an actual check made at handover. A shift closing under time pressure will otherwise default every field to None regardless of whether anyone looked, making a clean shift indistinguishable from an unreviewed one.
Should the handover describe an open deviation in full?+
No. It should reference the deviation's own record by ID and note anything specific the incoming shift needs to watch. Re-describing the investigation creates a second version that will drift from the source over time.
What does it mean if the incoming supervisor has questions but still signs?+
It means the record has evidenced attendance, not transfer of understanding. Questions raised should be resolved, or explicitly assigned an owner and deferred, before the confirmation is signed.
Is shift handover legally required?+
For processes covered by OSHA's process safety management standard, yes, written shift-change procedures are a direct requirement. Outside that scope it is good practice and an expected control, though HSE guidance treats it as a significant human-factors control.
What should happen with new or unsupervised staff on a shift with open issues?+
The combination should be flagged and mitigated explicitly, whether by pairing with an experienced operator or narrowing task scope, and that mitigation should be recorded rather than left implicit in the staffing field alone.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in HACCP and Food Safety
Unannounced Audit Readiness Check
Checks whether the site would pass an audit arriving today, covering records, standards and area condition
Product Nonconformance Report
Records product that does not meet specification
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
HACCP Plan
The hazard analysis and critical control point plan for a product or process
HACCP Verification Record
Confirms the HACCP plan is being followed and still works
CCP Monitoring Log
Records readings at a critical control point, such as cook temperature, chill time or metal detection
More in Process Control
Control Plan
Sets out what is measured on a process, how often, by what method and what to do when it goes out of limits
Statistical Process Control Log
Records measurements over time so process variation can be seen and acted on before product fails
Process Capability Study
Measures whether a process can reliably hold its specification, using data from a stable run
Setup Approval Record
Confirms a new setup is correct and approved before the run continues past the first pieces
Batch Record
Records everything that happened during the production of one batch, including materials, settings, checks and people
Yield Analysis Record
Compares material in against product out and accounts for the difference
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 9001:2015 clauses 7.4, 8.5.1, 8.7, 7.1.2 and 5.3
- OSHA Process Safety Management, 29 CFR 1910.119(f)(4), shift-change procedures
- HSE guidance HSG48, Reducing Error and Influencing Behaviour (human factors and shift handover)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.