Contents

Offshore Advantages research · offshore staffing

How much of a handover is lost between shifts?

A proposed protocol for comparing the handover note with what the next shift actually knew.

How much of a handover is lost between shifts? — editorial guide illustration

· 5 sources · Research methodology

Key stats

  • Public method
  • Fixed sample rule
  • November 9, 2026 method date

Question and scope

This is a proposed research protocol, not a report of completed findings. It asks how much of a handover is lost between shifts. The result would describe the gap between the note and the next shift's understanding. Ask whether a new reviewer could act on the record without a conversation.

The protocol does not measure whether the next shift performed well. It measures whether the context transferred. Write the deadline as a date and a local time. If the source is unclear, route the question instead of guessing.

Population and unit of analysis

Define the population as handovers during a stated window. The unit is one handover, with the note, the decisions, and the next shift's questions recorded. Review the first few notes together before the process expands. Write the deadline as a date and a local time.

Link the handover to the shift so the same handover is not counted twice. Test the rule on one real shift before applying it to both. A short note with four fields is easier to use than a long narrative. Write the deadline as a date and a local time.

Definitions and measures

Define a loss as a decision or risk in the note that the next shift could not restate. Report the loss rate by category. Use the same format for every handover so the next reader can scan it. Keep the evidence with the record rather than in a separate log.

Report the questions asked separately. A question may show a gap or normal clarification. If the source is unclear, route the question instead of guessing. A short note with four fields is easier to use than a long narrative.

Evidence standard

Ask the next shift to restate the open decisions before reading the note again. Compare the restatement with the note. A control that depends on memory is not yet a control. Name the owner in the same line as the action.

Record the date and the reviewer. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log. Test the rule on one real shift before applying it to both.

Sampling and collection

Use a census of the handovers. If sampling is necessary, stratify by shift. Write the deadline as a date and a local time. A short note with four fields is easier to use than a long narrative.

Pilot the method on a few handovers and compare the reviewers. Clarify what counts as a restatement. Separate what was observed from what was assumed. A short note with four fields is easier to use than a long narrative.

Analysis and reporting

Report the loss rate by category. Show the decisions that were missed most often. Present the results as a description of the handover, not a judgment about the team. Update the template when the same question appears twice.

Limits and sources of error

The next shift may have prior context, which can inflate the restatement. The note may be written after the handover, which can change the record. Record the exception and the person who approved it. A short note with four fields is easier to use than a long narrative.

Review cadence

Repeat the review after a handover change or at the same interval each quarter. Assign the follow-up to the operations lead and set a date. Keep the original note beside the corrected version. Update the template when the same question appears twice.

Sources

  1. NIST Cybersecurity Framework
  2. NIST Privacy Framework
  3. U.S. Small Business Administration
  4. U.S. Department of Labor
  5. GAO Green Book