Research question and scope

This protocol measures the share of shift handoffs that omit at least one required field. The unit is one handoff event between an outgoing and an incoming specialist, tied to a specific queue and time. The review measures the completeness of the written note, not the quality of the verbal conversation that may accompany it. A complete note can still describe a bad plan, and that is outside this measure.

Set the scope to one team, one queue, and a fixed number of consecutive handoffs. Record the handoff template version and the required fields at the start of the window. If the template changes during the window, keep the earlier definition for the full sample or split the sample into two periods. A template edit can raise completeness without changing the underlying habit.

Keep the review of the written note separate from a review of the specialist's judgment. A complete note can still contain a poor plan, and an incomplete note can still accompany a good verbal handoff. Mixing the two makes the result feel like a performance grade. State clearly that the measure is about the record.

Record whether the handoff note was created from a template or written from scratch. A free-form note may be more thoughtful but less consistent, and the difference matters for the fix. Report the template use rate beside the completeness result. The owner can then decide whether to improve the template or its adoption.

Population and handoff unit

Define the population as every scheduled handoff during the window, including handoffs with no open items. Include the handoff even when the outgoing specialist writes a short note, because an empty note is a result. Exclude handoffs that were replaced by a live conversation with no written record, and count them separately. A verbal-only handoff cannot be checked for fields.

The unit is one handoff event, not one item, because the note is written once for the whole shift. If the note covers several items, check the required fields at the note level and at the item level separately. Record the number of open items in each handoff so a short note is judged against the actual load. An empty queue should not be penalized for a short handoff.

Record whether the handoff was written at the start, middle, or end of the shift. A note written in the final minutes may lose more fields than one written earlier. The timing is a process fact that the team can change. It is more useful than a general instruction to be more careful.

Count the handoffs that were skipped entirely, such as a shift with no written note. A skipped handoff is not a missing field, but it is a more serious gap. Report it separately so it does not inflate the field-level share. The owner needs to see both the partial notes and the absent ones.

Required-field standard

Define the required fields from the work, not from the template's history. A useful standard includes the state of each open item, the next action, the owner, the due time, and the evidence link for anything that cannot be recreated. Add a field for open decisions if the queue has them. Keep the list short enough that a writer can check it before leaving.

Publish one positive example and one missing-field example with identifying details removed. The examples should show the difference between a field that is present and a field that is meaningful. A note that says next action pending does not satisfy the standard. The reviewer should be able to mark each field present, weak, or missing using the example.

Keep the required-field list tied to the decisions the next shift must make. If a field never changes a decision, remove it before the next cycle. A long list produces a low completeness score without improving the handoff. The standard should be short enough to check in under a minute.

Make the evidence link a required field only for items that cannot be recreated from the record. Requiring a link for every routine item adds noise and encourages a placeholder. Tailor the standard to the risk of the item. A shorter, risk-based standard is easier to apply under time pressure.

Sampling and verification

Collect the handoff notes from the collaboration tool or the queue system rather than asking specialists to submit examples. Select every handoff in the window if the number is small, or a fixed interval if it is large. Record the export date and the selection rule. Check the note against the record as it existed at the handoff time, not as it looks after later edits.

Use two reviewers on a small overlap sample and compare their classifications. If they disagree on more than a few fields, rewrite the standard before continuing. A disagreement usually means the field definition is too vague. Record the reviewers' notes with the sample so a later analyst can see how the judgment was made.

Check whether the missing field was available in the source record at the time of the handoff. A field that was never captured cannot be blamed on the note writer. Separate an unavailable fact from an omitted fact in the classification. That distinction tells the owner whether to fix the system or the habit.

Note whether the reviewer had access to the queue at the handoff time or only later. A later view may show a state that the writer never saw. Use the historical record when the system keeps one. If it does not, state the limitation in the report instead of guessing.

Measuring loss by field

Report the share of handoffs missing at least one required field, then break it down by field. A single field that is missing in most notes is a template or training problem. A spread across many fields may mean the handoff is being written too late or by someone without the full picture. The pattern matters more than the overall percentage.

Also report the missing-field share by handoff direction and by day of week. A handoff into a weekend or a time zone gap may lose more detail than a weekday handoff. A difference by writer may reflect training, but do not report individual names unless the team has agreed to it. The purpose is to improve the note, not to rank people.

Report the results as counts as well as shares when the sample is small. A share based on twelve handoffs can swing wildly with one missing note. Show the denominator beside every percentage so the reader can judge the stability. Small samples are still useful if the counts are visible.

Report the share of handoffs that would have failed even with a perfect template because the source record was incomplete. This separates a note-writing problem from an upstream data problem. The fix for the latter belongs in intake, not in the handoff training. Show both shares side by side.

Limitations and review cadence

The note cannot show what was said in a verbal handoff or what the incoming specialist already knew. It also cannot show whether a missing field was available elsewhere and simply not copied. Treat the result as a measure of the written record, not of the whole transfer. Note any verbal supplement reported by the team.

Review the standard after two cycles and remove fields that nobody used to make a decision. Keep the fields that prevented a real question. Fix the template first, then offer coaching if the same field remains missing. A short standard that people follow is more valuable than a long one they abandon.

Review the template with the people who write it, not only with the people who read it. A field that takes ten minutes to complete will be skipped under pressure. Ask what could be filled automatically from the queue system. The best template removes work rather than adding a reminder.

Review the result with a small group that includes one writer and one reader. A review with only managers tends to produce rules that look good on paper. Ask the writer which field is hardest to complete and the reader which field is most often missing. The two answers usually point to the same fix.