Shift Handover Log Template
Four documents and four sheets that track every open issue by carry count, so one that quietly stops appearing gets caught instead of assumed fixed.
Free download · No account needed
Two Lists, One Gap
Redcliff Logistics, Distribution Center 1
21 shifts, one week, 40 issues logged. Two issues leave the open list between the same two shifts.
| Open at close, shift 8 | Open at close, shift 9 |
|---|---|
| OI-006, guard rail loose, dock 4 | missing, nothing logged |
| OI-031, dock plate 7 sticking | OI-031, carried again |
| OI-034, cycle count variance, aisle 9 | resolved, count corrected |
| OI-035, new: bander strap loose |
OI-006 and OI-034 both leave the list between shift 8 and shift 9. OI-034 leaves with a resolution note. OI-006 leaves with no carry and no resolution anywhere in shift 9's log. That is the drop. It resurfaces on shift 16, seven shifts later, logged again as though new.
| This week | |
|---|---|
| Issues logged | 40 |
| Resolved same shift | 21 |
| Carried, then resolved | 14 |
| Dropped | 5 |
Four of the five drops landed on a shift running short of its planned headcount, out of six short-staffed shifts that week.
Every shift handover template on the market is the same shape: a form with one field per open issue, still open today, yes or no. SmartQHSE's own handover framework requires the incoming supervisor to acknowledge each section before the handover counts as complete, and every other result on page one just adds its own sign-off or audit trail on top of that same field. None of them check today's open list against yesterday's, which is the only way to catch an issue that quietly stopped appearing without anyone deciding it was fixed.
This pack tracks three outcomes instead of one field. An issue resolved within the shift that opened it never reaches a carried-in list. A carried issue gets a status update and a carry count on every log until it closes. A drop is different: open at shift's end, missing from the next log, never marked resolved in either one, caught only by lining the two lists up. The UK's Health and Safety Executive names this failure, information lost at shift handover, among the factors behind the Piper Alpha disaster.
On the worked week in this pack, Redcliff Logistics ran three shifts a day for a week at one distribution center: 21 shifts, 40 issues. Twenty-one closed same shift, fourteen carried forward and resolved, five went quiet. Three resurfaced four to seven shifts later, logged again as though new; two are still missing. Four of the five drops landed on a shift short of its planned headcount, out of six short-staffed shifts that week. Multi-location standards is the job once a pattern spans sites; catching one drop is a single-site job, shift by shift.
What's in the pack
Handoff Procedure
The order a handoff runs in: reconcile the carried-in list first, then log headcount and every carry count, so a new site's opening runbook can hand off into this log from day one.
Escalation Contacts
Who to call by category and by hour, the same job an escalation matrix does estate-wide, scoped here to one shift's own categories.
How a Dropped Issue Gets Caught
The two lists every shift produces and the one comparison that tells a fixed issue apart from one nobody carried forward.
Weekly Continuity Report
Every dropped issue named individually with its gap in shifts, next to the staffing pattern behind it, not a single blended count.
Shift Log
One row per shift with planned and actual headcount, new issues opened, and how many carried-in issues went missing that shift.
Open Issues Carried Forward
One row per issue that carries its own status forward, so a row stuck on open after the log has moved past it stands out.
Incident Note
Hazard observations and injuries logged separately from open issues, linked back to the issue ID, with the OSHA recordable determination stated rather than left blank.
Staffing Actuals
Planned versus actual headcount per shift, so a dropped issue can be checked against whether that shift was running short.
How to use it
- 1
Open in River, or take it blank
Open the pack in River and hand it your last week or two of shift logs, or download the Word documents and CSV sheets and work through them yourself.
- 2
Reconcile before logging anything new
Go down the prior shift's still-open list first: mark each item resolved with what fixed it, or carry it forward with an updated status and count.
- 3
Check every gap against staffing
Cross-reference every dropped issue against planned versus actual headcount for the shift it went quiet on, and roll the pattern up once there are enough to see one.
- 4
Roll the week up honestly
Report same-shift, carried-then-resolved, and dropped counts together, plus the share of drops on a short-staffed shift, not one blended number.
Frequently asked questions
Is this template free?
Yes, and nothing is gated. The zip holds four Word documents and four CSV sheets, no account and no card. Edit with AI is the optional half: River reconciles each shift's carried-in list against the one before it and flags anything that went quiet. More packs sit in the template library.
What format are the downloaded files?
Four Word documents and four CSV sheets, zipped. Excel, Numbers and Google Sheets open the sheets directly, and the procedure, contacts, drop-detection note and continuity report open in Word or Pages. The open issues sheet carries the carry count and drop flag, so the comparison survives the download.
How is this different from a digital handover or sign-off tool?
Most digital handover tools add a mandatory acknowledgment or a sign-off trail on top of the same still-open field every paper log already has. None of them compare today's open list against yesterday's, which is the only way to catch an issue that stopped appearing without anyone deciding it was fixed.
How is a drop different from an issue that's still open?
An issue still open is on both the prior shift's list and this shift's list, carried forward with a status update. A drop is on the prior list and missing from this one, with no resolution note anywhere in this shift's log either. The two look identical on a single log; only comparing both catches the difference.
How do you tell a rediscovered issue from a new one?
Check its description, equipment, and location against the Open Issues Carried Forward sheet's history before logging it as new. On the worked week, three of five dropped issues resurfaced four to seven shifts later, matching an earlier entry closely enough to log as a rediscovery with the gap stated, not a fresh issue with no history.
Does this track OSHA-recordable incidents?
It logs them, separately from the open issues list, because the two answer different questions: one tracks whether something got fixed, the other whether a regulator needs a record. OSHA requires a recordable injury entered on the 300 Log within seven calendar days of the employer learning of it, and the Incident Note sheet states that deadline against the date logged.
Does this replace our multi-location standards or site visit checklist?
No. This space holds the handoff procedure and the open issues log. Estate-wide consistency across sites is a multi-location standards job, and checking whether a safety-tagged drop got fixed in person is a site visit and field audit one.
Find out which of this week's open issues actually went quiet
Take the Word documents and CSV sheets blank, or open this pack in River and let it reconcile your last few shift logs first.
Edit with AI