Maintenance Shift Handover Checklist: Transfer Work Without Losing Risk

A maintenance shift handover checklist protects continuity when the person who knows the current situation is about to leave. The incoming shift needs more than a task list: it needs the actual asset state, what changed, what remains uncertain, which temporary conditions exist and who can make the next decision.

This page focuses on transfer between shifts. It is different from the field service report template, which documents a customer-site visit, and from a preventive task list, which defines recurring work. Handover connects unfinished reality to the next accountable team.

Prepare the handover throughout the shift

Do not reconstruct eight hours of work from memory five minutes before departure. Update the shift record when an asset changes state, a defect is found, a permit changes, a part is removed, an external party commits to an action or a priority is revised.

Use timestamps where sequence matters, and distinguish the time an event occurred from the time it was entered. If the outgoing shift inherits an unresolved item from an earlier team, preserve its original source instead of retelling it as firsthand knowledge. This gives the incoming shift a more reliable trail and makes aging work visible.

Use one shared system of record. Private notebooks and chat messages may help temporarily, but material operational information must move into the authorized record. Mark uncertain information as uncertain instead of smoothing it into a confident narrative.

Shift and date:
Outgoing role:
Incoming role:
Area / asset scope:
Handover time:
Record location:
Supervisor or escalation contact:

State the operating picture first

Begin with the current picture, not a chronological story. Which assets are available, unavailable, degraded, under maintenance, awaiting verification or in another locally defined state? Use the organization’s controlled terminology.

A simple area overview can help the incoming team orient before details. Keep it synchronized with the authoritative asset or work-management system and state the time of the snapshot. If two systems disagree, do not choose the more convenient status. Flag the discrepancy, identify which source governs operational decisions and assign reconciliation.

Asset / area:
Current state:
State confirmed at:
Evidence or system reference:
Change since previous handover:
Operational impact:
Decision authority if state changes:

Avoid ambiguous phrases such as “basically running,” “should be fine” or “nearly done.” If verification is incomplete, state that directly. The incoming shift should not have to infer whether equipment can be used.

Separate completed, active and waiting work

Group work by status so finished jobs do not hide live exposure.

For every open item, use a single named owner. The action item form ownership guide explains why a department name is often too vague. Ownership does not mean one person performs all work; it means one role is accountable for making the next state visible.

Transfer faults, evidence and uncertainty

Describe what is known, what was reported and what remains inferred. A compact evidence structure prevents causal stories from hardening before diagnosis.

Fault / symptom:
First observed or reported:
Reported by:
Direct observations:
Measurements or evidence references:
Actions already attempted:
Result of each action:
Working hypothesis, clearly labeled:
Unknowns:
Next diagnostic step and owner:

Never imply that correlation proves cause. “Alarm cleared after reset” does not establish why the alarm occurred. Preserve the sequence and let qualified people assess causality.

Make temporary conditions impossible to miss

Temporary repairs, bypasses, unavailable safeguards, restricted operating modes, barriers and monitoring arrangements need prominent treatment under the site’s approved process. They should not sit inside a paragraph of routine updates.

TEMPORARY CONDITION
Asset / location:
Exact condition:
Authorized by:
Effective from:
Required monitoring or restriction:
Review / expiry point:
Removal or permanent-work owner:
Linked permit, assessment or work order:
Escalation trigger:

This generic structure does not authorize a temporary condition or determine its safety. Follow applicable permits, risk assessments, engineering controls and qualified authority.

Verify permit, isolation and access status

Handover should point to the current controlled records for permits, isolations, lockout or access controls where these apply. Do not reproduce fragments that could conflict with the authoritative source.

The incoming role should know which records are active, who controls them, where they are held and what formal transfer or closure process is required. If the process requires in-person verification, signatures or a walkdown, a checklist entry alone is insufficient.

[ ] Active controlled records identified
[ ] Responsible issuer / holder identified
[ ] Asset and boundary match confirmed under local process
[ ] Formal transfer, suspension or closure completed as required
[ ] Conflicts or discrepancies escalated

Account for parts, tools and external support

Unreceived parts and missing specialist support often determine whether the next shift can proceed. Record part identity, quantity, location, reservation status and expected arrival only from a verified source. Do not turn a supplier estimate into a guarantee.

Also note special tools, test equipment and removed components that need custody or return. For external technicians or customer representatives, record the organization, purpose, expected window, contact channel and access owner without exposing unnecessary personal information.

For site-visit logistics, the field service report template provides useful closeout fields, while the handover record should retain only what the incoming shift needs.

Rank the next shift’s priorities

Priority should reflect the organization’s approved operational and risk process, not who spoke most recently. Give the incoming team a small ordered list with rationale and a trigger for reassessment.

Priority 1:
Why it is first:
Owner:
Required dependency:
Decision / escalation trigger:

Priority 2:
Why it is next:
Owner:
Required dependency:
Decision / escalation trigger:

If two priorities conflict, make the conflict visible and name the authority who resolves it. A handover should not quietly ask the next shift to choose between production, quality, customer and safety expectations without mandate.

Conduct a focused verbal exchange

Use the written record as the agenda. The outgoing person summarizes exceptions; the incoming person asks questions and repeats back the highest-consequence states, restrictions and next actions. A read-back is a communication check, not proof that the underlying situation is safe.

Make the exchange accessible to the people expected to act. Expand uncommon abbreviations, identify assets consistently and provide an alternative to audio-only communication when needed. If language support or another reasonable communication adjustment is required, arrange it through the organization’s process rather than assuming a rushed handover is understood. Confirmation means the message was received, not that responsibility for every prior decision has silently transferred.

If the exchange is recorded, obtain meaningful agreement before recording begins and provide an equal manual-note option. The legally recording conversations guide offers general consent context, but local law, employment rules, works agreements and policy require appropriate review.

Need a reviewable source for an agreed in-person handover? Kuno supports visible, consented conversation capture and human-reviewed notes. It does not approve asset status or replace controlled safety records. Explore Kuno

Confirm acceptance and unresolved disagreements

Close with explicit confirmation that the incoming role received the record, understands the stated priorities and knows the escalation route. Acceptance should not force agreement with an unsupported claim.

Record reviewed:
Critical states read back:
Questions resolved:
Unresolved disagreement:
Temporary conditions acknowledged under local process:
Immediate next action and owner:
Escalation initiated if needed:
Outgoing / incoming confirmation:

Use a concise meeting follow-up when supervisors or planners must resolve a disputed priority after handover. Preserve the original observation and decision trail.

Copy the complete handover checklist

CURRENT PICTURE
[ ] Asset states and operational impact are explicit
[ ] Evidence time and source are recorded

OPEN WORK
[ ] Completed, active, waiting and deferred work separated
[ ] Every live item has one owner and next step

RISK AND CONTROL
[ ] Faults separate fact, report, hypothesis and unknown
[ ] Temporary conditions are prominent
[ ] Controlled permit / isolation records are referenced

RESOURCES
[ ] Parts, tools and external dependencies are located
[ ] Estimates are labeled and not presented as guarantees

NEXT SHIFT
[ ] Priorities include rationale and escalation triggers
[ ] Incoming role asked questions and read back critical points
[ ] Disagreements and unknowns remain visible
[ ] Handover confirmation is recorded

Review recurring handover failures in meeting note templates using a decision log, but keep operational source records in the approved maintenance system.

Preserve context without outsourcing responsibility. Kuno can help create a draft from a consented in-room handover; the incoming team must verify names, asset states, restrictions and actions before relying on it. See Kuno

Adapt this checklist to the organization’s roles, assets and controlled procedures. It is not evidence of legal, regulatory, safety or professional sufficiency.