How often do shift handovers leave safety notes unread?

Published November 10, 2026.

A safety note is only useful if the next shift sees it before the work starts. In many workplaces the note is delivered through the same channel as schedule changes, break coverage, and general chatter, so a serious warning can sit unread behind routine messages. This review sets out a bounded way to measure how often safety notes at shift handover go unread or unacknowledged. It does not estimate a national rate or claim that a read note prevents every incident. The protocol is designed so a small employer can test its own handover without a large safety department.

Question and scope

This review asks how often a safety note issued at shift handover is left unread or unacknowledged by the incoming shift before work begins. The unit is one safety note that applies to the next shift. The study records whether the note was created, delivered, opened, and acknowledged, and whether the incoming lead confirmed the control. It does not judge whether the original hazard assessment was correct.

Set the scope to one employer, one work area, and one handover process. Record the shift pattern, the note format, and the channel at the start. If the process changes during the window, keep the original definition for notes already in progress and analyze later notes separately. A new messaging app can look like an improvement when it is only a change in where the note is stored.

Exclude general announcements that do not describe a hazard, a control, or a restriction. Include notes that were created but never delivered, because the failure is part of the result. Include notes that were delivered after the shift started, because late delivery is a different failure from no delivery. Test the definition on two recent handovers before collecting the full sample.

Definitions that make the measure reproducible

Define a safety note as a written message that names a hazard, a required control, or a restriction that affects the next shift. A note that says "be careful" without naming the hazard is a reminder, not a safety note. Define delivery as the note appearing in the channel the incoming shift is required to check. Define acknowledgment as a named person on the incoming shift confirming that they read the note and understand the control.

Define an unread note as one with no open or acknowledgment record before the incoming shift started work. A note that was opened during the shift is late, not on time. Keep the read rate and the on-time rate separate in every table. A high read rate can hide a pattern of reading after the hazard was already present.

Record the note author, the shift, the work area, and the time the note was created. Add the time of delivery, the time of acknowledgment, and the name of the person who acknowledged. State the timing rule, especially whether the shift start is the scheduled time or the actual clock-in time. The rule should be the same for every note in the sample.

Evidence standard and data dictionary

For each note, capture the hazard category, the control, the affected area, and the shift window. Add the delivery channel, the read record, and the acknowledgment. Record whether the note required a response beyond reading, such as a check of a guard or a stop of a machine. Keep the raw record in the approved safety file.

Record whether the note replaced an earlier note or corrected it. A correction that arrives after the shift started may leave the team working to the wrong instruction. Add the version number and the time of the change. Do not infer the content of an earlier version from the latest file.

A useful field is whether the note was discussed at the handover meeting. A message that appears in a channel but is never mentioned may be treated as optional. Record the meeting time and the person who raised it. A second reviewer should be able to tell whether the incoming shift had a real chance to see the note.

Sampling and collection

Draw the sample from the safety note log, not from the acknowledgment report. The acknowledgment report hides the notes that were never acknowledged. Record the export date, the filters, and the number of notes excluded. If the employer has only a few notes, describe each case instead of computing a rate.

Collect the read record as it existed at the time of the shift, not as it was reconstructed later. If an acknowledgment was added after an incident review, record the later date. Do not treat a retrospective confirmation as an on-time acknowledgment. Note the collection date separately from the shift date.

Record whether the incoming shift had a designated person responsible for checking the log. A shared responsibility with no name often becomes no responsibility. Add the name and the time the check was completed. A handover that depends on everyone is a handover that depends on no one.

Analysis and reporting

Report the number of safety notes, the share delivered before the shift, the share acknowledged before work, and the share acknowledged at any time. Show the counts by hazard category, area, and shift. Present the on-time rate and the late rate separately. Use the same denominator for every rate and show notes with incomplete records.

Inspect the unread notes without blaming the incoming shift. A note that was buried in a busy channel or sent to the wrong group is a process problem. A note that was read but not acknowledged may show a training gap. Describe the pattern and the limitation rather than ranking teams.

A useful additional view is the share of notes that required a physical check and whether that check was recorded. A guard inspection that is never logged is difficult to distinguish from one that never happened. Report the check separately and avoid combining it into a single compliance score. A safety handover can be read and still fail at the point of control.

Limits of the evidence

The record cannot show whether the person who acknowledged the note understood it or whether the control was actually applied. It can show only what was sent, read, and confirmed. A high acknowledgment rate is not proof of a safe workplace. The protocol also cannot capture a verbal warning given at the machine that never reached the log.

A small employer may have too few notes to support a stable share. Describe the cases and the channels instead of ranking shifts. If one supervisor writes most of the notes, report that concentration. A general rate would hide a single handover habit.

A note may be unread because the incoming shift was dealing with an emergency at the start of work. The emergency is a finding, not a reason to drop the case. Record the trigger and whether a verbal handover covered the same hazard. Report the emergency route beside the planned route.

Applying the result

Give the result to the safety lead and the operations team and ask for one observable change. The change might be a separate safety channel, a required verbal read-back, or a rule that the incoming lead confirms the note before releasing the team to work. Record the owner, the effective date, and the measure that will show whether the change worked. Repeat the protocol with the same definitions for the next period.

If on-time acknowledgment rises but physical checks stay flat, the process may be improving the paperwork without changing the work. If late acknowledgment falls and near-miss reports rise, the team may be noticing hazards earlier. Report the movements together before drawing a conclusion. Close the review when the owner accepts the finding and the next period is scheduled.

Ask the last five incoming leads whether they could name the safety note that applied at the start of their shift. A direct answer is more useful than a general compliance score. Fix the step that made the note hard to find. The next measurement should show whether the same gap recurred.

Record whether the note was available in the language the incoming shift uses at work. A warning that cannot be read quickly is not a warning in practice. Report the language and the channel together. The two details answer different questions about access.

Ask the author whether the note described a control the incoming shift could actually perform. A warning about a hazard with no practical control leaves the team with nowhere to go. Record the control and whether the required tool was available. A safety handover is stronger when the next shift can act on it immediately.

Data Sources and Methodology

The review uses public employment and workplace safety guidance to bound the definitions and to keep the recommended record fields within common practice. The sources below are used as context, not as a claim that any one employer follows them in the same way. Each measure in this protocol is defined from the employer's own records, then compared with these public references where the reference is relevant. The citations are listed with the specific topic they support so a reader can check the boundary without searching the whole site.

The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.

Sources

Society for Human Resource Management, employee handbooks and policies - accessed November 10, 2026.
U.S. Department of Labor, workplace safety and health - accessed November 10, 2026.
Centers for Disease Control and Prevention, workplace health promotion - accessed November 10, 2026.
Project Management Institute, risk management resources - accessed November 10, 2026.

Question and scope

Definitions that make the measure reproducible

Evidence standard and data dictionary

Sampling and collection

Analysis and reporting

Limits of the evidence

Applying the result

Data Sources and Methodology

Sources

Related Research