Research question and scope

This protocol measures how often a shift handover names a next action, an owner, and a deadline for each open item. The unit is one open item in one handover note. A complete item has all three fields and a case reference. The measure describes handover usability, not the quality of the work described.

Set the scope to one team, one client queue, and a fixed period. Record the handover template and the shift schedule in force. If the template changes during the period, split the sample at the effective date. A different template creates a different denominator.

Keep the measure separate from a missed-promise count. A complete handover can still describe a promise that was already at risk, and an incomplete note can sit beside a case that was handled well. The purpose is to test the transfer of ownership. Report promise outcomes separately.

Name the decision the result will support before collection starts. The team may use it to shorten the template, add a required owner field, or change the handover time. A report that only lists missing fields gives the team no direction. Write the intended action beside the scope.

Record the handover location and the time it was posted. A note posted after the next shift started cannot guide the first hour. Note the posting time and the shift start. The timing is part of whether the handover worked.

Population and unit of analysis

Define the population as every open item recorded in a handover note during the period. Include items waiting on the desk, the client, a system, and the customer. The unit is the open item, not the note or the case. A case mentioned in two handovers is two units when each note assigns a new state.

Include items that were closed during the next shift and items that remained open. Mark the outcome at the next handover. Exclude items that were already closed before the note was written. Report the excluded count and the reason. A closed item does not need an owner.

Exclude a general note such as all clear or no open items from the item count but record it as a note. A no-open-items handover is a valid state, not a missing field. Report those notes separately so they do not distort the rate. The note count should appear beside the item count so the reader can see coverage.

Decide how to treat a group line such as three refunds pending. Count each case when the note lists the references, and count the group as one item when it does not. Record the rule and the example. A group line without references cannot be assigned or checked.

Decide whether a question for the next shift counts as an open item. Include it when it blocks a case and mark it as a question. Record the blocker reference. A question without a case is still useful but belongs in a separate count.

Definitions that make the measure reproducible

Define a next action as a sentence that starts with a verb and names the object of the work. Send the revised invoice and call the carrier are actions. Define an owner as a named person or a named role with a person on shift. Define a deadline as a date and time in the client's time zone. Publish one example of a complete item.

Define a partial item as one missing exactly one of the three fields. Define an incomplete item as one missing two or more. Define an unread note as one with no acknowledgement from the next shift by the first hour. Publish one example of each before sampling.

Define the handover window as the time between the note posting and the next shift's first action. Record both times. A note posted on time but read at noon did not support the morning. The window is part of the result.

Define the client's time zone and use it for every deadline in the sample. A deadline written in local time without a zone is ambiguous. Record the conversion when the note uses another zone. The reviewer should not have to guess which clock the writer meant.

Agree how to score a deadline that has already passed at the time of the note. Keep it as a field and mark it overdue. A passed deadline may be a valid escalation rather than a missing field. Report overdue items separately from missing ones.

Sampling and data collection

Draw the sample from the handover archive for the full period. Record the export date, the shifts covered, and the note count. Do not build the sample from notes that were praised or complained about. A selected sample cannot show the everyday handover.

Capture the note date, the shift, the client, the case reference, the next action, the owner, the deadline, and the acknowledgement time. Add the item state at the next handover. Store the notes with the report. The three fields and the acknowledgement are the core evidence.

Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a role counts as an owner, the rule is too vague. Rewrite the rule and retest before the full sample. Agreement matters more than sample size.

Record the time spent reading each note. A report that requires opening every case will not be repeated. Note whether the handover tool exposes the posting and read times. The collection cost belongs beside the result.

Take a pilot of five notes across two shifts before the full draw. Use the pilot to test the template and the archive. Record what was missing and how long each note took. A pilot that takes an hour per note is a warning about the full sample.

Measuring handover completeness

Report the share of items that are complete, partial, and incomplete. Show the counts behind each share. The three groups describe different levels of transfer and should not be collapsed. A single completeness rate hides the item that had an owner but no deadline.

Break the result down by shift, queue, and item type. A night shift may show more missing owners because fewer people are online. A refund queue may show more missing deadlines because the promise is unclear. Compare only groups with the same template and a similar volume.

Report the most common missing field. A missing owner may point to a roster gap, while a missing deadline may point to an unclear promise. Record one example for each. The pattern should lead to one template or staffing change.

Report the share of notes acknowledged within the first hour of the next shift. A complete note that nobody reads did not transfer ownership. Include the median acknowledgement time. The read is the other half of the handover.

Compare the completeness rate with the share of items that changed state during the next shift. A high completeness rate with little movement may mean the actions were too vague. Record both numbers. The pair describes whether the handover produced work.

Limitations and next action

The measure cannot show whether the next shift understood the note or whether the customer was served well. It also cannot show a verbal handover that never reached the archive. Treat the result as a measure of recorded transfer. Note the shifts and queues that were not included.

Give the result to the team lead and the client contact with one change to test. The change might be a required owner field, a shorter template, or a handover time before the shift ends. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.

Review the boundary cases before adding more required fields. A few group lines may explain a large share of incomplete items. Fix the template or the reference rule first if that is the pattern. The goal is a note the next shift can act on, not a longer form.

Repeat the measure after the change with the same scope and template. Report the before and after counts together, including the note count. Record any shift or queue change in the period. A comparison with a changed roster is not a comparison.