Shift Handover Procedure
A shift handover procedure template for passing work, safety risks, and open actions from one shift to the next. Use it to keep operations continuous, reduce missed tasks, and create a clear record of responsibility.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Manufacturing · Logistics · Food Production · Maintenance · It Operations
Overview
This shift handover procedure template captures the transfer of responsibility between outgoing and incoming roles at the end of a shift. It is built to record current status, pending tasks, safety-critical items, unresolved deviations, and the final acceptance of the shift by the next role. The structure supports clear ownership, so the next team knows what is complete, what is still open, and what needs escalation.
Use this template whenever work continues across shifts, when a task has safety or quality implications, or when the next team must act on an active incident, permit, or maintenance job. It is also useful after abnormal events, because the handover record can preserve the context that might otherwise be lost in a rushed verbal briefing. The sign-off section helps show that both roles reviewed the same information.
Do not use this template as a substitute for a full incident report, permit-to-work record, or non-conformance form. If the issue requires immediate containment, emergency response, or formal investigation, those processes should run first and the handover should reference them. The template is not meant for casual chat between coworkers; it is meant for controlled transfer of operational responsibility.
Standards & compliance context
- The template supports ISO 9001 documented information practices by creating a consistent record of status, responsibility, and sign-off.
- It can be adapted to GMP, HACCP, or ServSafe environments by adding product hold, sanitation, allergen, or contamination-control notes where needed.
- In hazardous operations, it should align with OSHA 1910.119-style process safety expectations by documenting deviations, isolation status, and escalation for unsafe conditions.
- For hazardous communication, use site-approved wording and symbols consistent with ANSI Z535.6 so warnings are clear and recognizable.
- Where the handover includes active work control, it should reference permit-to-work, competent person review, or incident management records rather than replacing them.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns the handover into a controlled sequence with clear ownership at each point.
-
The outgoing role prepares the handover record
The outgoing role updates the handover record before the incoming shift arrives. Record the current operational status, completed work, open tasks, deviations, equipment issues, safety concerns, and any pending approvals or escalations. Use clear, factual language and include timestamps where relevant.
-
The outgoing role identifies safety-critical items
The outgoing role reviews the shift record and flags any safety-critical items, including active hazards, permit-to-work restrictions, isolation status, abnormal readings, near misses, and temporary controls. If any item requires immediate action, the outgoing role escalates it before handover is closed.
-
The outgoing role briefs the incoming role
The outgoing role briefs the incoming role using a structured format such as status, pending tasks, deviations, and safety concerns. Cover what was completed, what remains open, what changed during the shift, and any tolerance limits or abnormal conditions that require attention. Keep the briefing concise, factual, and complete.
-
The incoming role verifies understanding of open items
The incoming role reviews each open task, deviation, and safety concern with the outgoing role. Confirm ownership, due time, escalation path, and any required follow-up. If any item is unclear, the incoming role asks for clarification before accepting responsibility.
-
The incoming role accepts shift responsibility
The incoming role acknowledges the handover and accepts responsibility for the current shift. The outgoing role remains available for clarification only until the handover is complete, unless site policy requires overlap support.
-
The supervisor escalates unresolved issues
The supervisor reviews unresolved items and determines whether immediate escalation is required. Use the site escalation matrix for safety hazards, overdue tasks, equipment failures, permit-to-work conflicts, or process deviations outside tolerance.
-
The supervisor escalates the unresolved issue
The supervisor notifies the appropriate manager, competent person, maintenance contact, or safety representative according to the escalation path. Document the issue, the time of escalation, the person notified, and any interim controls applied.
-
The outgoing and incoming roles sign off the handover record
Both roles confirm the handover record is complete, accurate, and legible. Record signatures or digital acknowledgment, date, time, and any comments needed for traceability. Retain the record according to site document control requirements.
How to use this template
- 1. The outgoing role completes the handover record with current status, open tasks, safety notes, and any related reference numbers before the shift ends.
- 2. The outgoing role identifies each safety-critical item, records the deviation or hazard, and notes the required follow-up or escalation path.
- 3. The outgoing role briefs the incoming role face to face or through the approved communication channel and walks through each open item one by one.
- 4. The incoming role verifies understanding of every open item, asks clarifying questions, and confirms any tolerance, deadline, or escalation trigger that applies.
- 5. The incoming role accepts shift responsibility only after the handover is complete, and the supervisor resolves or escalates any unresolved issue that cannot be safely transferred.
- 6. The outgoing and incoming roles sign off the handover record, and the supervisor files or routes it according to the site’s documented information process.
Best practices
- Record the handover before the outgoing role leaves the area so the next shift receives current information, not memory-based notes.
- List each open item separately with one owner, one expected outcome, and one escalation trigger to avoid ambiguity.
- Mark safety-critical items clearly and include the hazard, required PPE, isolation status, or permit-to-work reference where relevant.
- Use exact equipment IDs, work order numbers, incident tickets, or line names so the incoming role can find the source record quickly.
- Require the incoming role to repeat back the key open items and confirm understanding before accepting responsibility.
- Escalate unresolved deviations immediately when they exceed tolerance, affect product quality, or create a hazard that the next shift cannot control.
- Keep the handover concise but complete; missing a critical detail is more harmful than a longer record.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this shift handover procedure template cover?
It covers the outgoing shift record, safety-critical items, open tasks, incoming shift verification, supervisor escalation, and final sign-off. The template is meant to capture what changed, what is still open, and who now owns each item. It works best when the handover needs a documented trail rather than a casual verbal update.
When should this template be used?
Use it at every planned shift change, and also after abnormal events such as equipment trips, quality deviations, or safety incidents. It is especially useful when work spans multiple shifts or when the next team must continue a permit-to-work, maintenance job, or production run. If the handover is purely informal and low-risk, a lighter record may be enough.
Who should complete the handover?
The outgoing role should prepare the record and brief the incoming role, while the incoming role verifies understanding and accepts responsibility. A supervisor should review unresolved issues and escalate anything that cannot be safely transferred. In regulated or high-risk environments, a competent person should confirm the handover content.
How often should a shift handover be performed?
It should be performed at every shift change, including weekend, night, and relief coverage handovers. If the operation has split shifts, the handover should happen each time responsibility changes. The cadence should match the actual transfer of control, not just the clock.
How does this relate to ISO 9001 or other quality systems?
It supports ISO 9001 documented information practices by creating a consistent record of status, actions, and responsibility transfer. It can also support GMP, HACCP, or ServSafe-style controls when the handover includes safety, sanitation, or product-risk items. The template does not replace your site procedures, but it helps show that critical information was communicated and acknowledged.
What are the most common mistakes when using a handover form?
The biggest mistakes are vague notes, missing open-item owners, and skipping verification by the incoming role. Another common failure is leaving out safety-critical deviations, which creates hidden risk for the next shift. A handover is only useful if it records what must be acted on, not just what happened.
Can this template be customized for maintenance, production, or IT?
Yes. For maintenance, add equipment status, permits, isolation points, and spare parts needed. For production, add line status, quality holds, and changeover details; for IT, add incident state, service impact, and rollback or escalation notes. The structure stays the same, but the fields should match the work being transferred.
How should this template integrate with other systems?
It can link to CMMS work orders, incident tickets, permit-to-work logs, quality non-conformance records, or ITIL runbooks. The handover should reference the source record number so the next shift can find the full context quickly. If your team uses digital forms, the sign-off and escalation fields should sync to the same workflow.
Is a verbal handover enough without a written record?
A verbal handover may work for low-risk, short-duration tasks, but it is weak when multiple people, hazards, or unresolved actions are involved. A written record reduces memory gaps and makes ownership clear if the issue reappears later. This template is designed to turn the conversation into a traceable operational record.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Geofencing defines a virtual geographic boundary — a "fence" — around a work location. When an employee's mobile device enters or exits the fence, the...
-
Disconnected cloud apps create friction and waste time. Learn why unified work platforms improve productivity and retention.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
HR compliance software that keeps records audit-ready every day with real-time reporting, tracking, and documentation.
-
Discover the 5 integrations your enterprise intranet needs — from HRIS and SSO to document management and CRM — to drive adoption and reduce tool sprawl.
Ready to use this template?
Get started with MangoApps and use Shift Handover Procedure with your team — pricing built for small business.
