Research question and scope

This protocol asks how often an open action survives a shift handover and how often it disappears from the next shift's working view. The unit is one open action that existed at the moment of handover, identified by the case, the action, and the owner. The study measures whether the action appears in the handover note, whether it is acknowledged, and whether it is completed or explicitly reassigned. It does not measure whether the customer was satisfied with the outcome.

Set the scope to one queue, one shift pair, and one handover template. Record the ticketing system, the note template, and the shift schedule in force at the start. If the template changes during the window, keep the earlier definition for the full sample or analyze the change as a separate period. A template change can look like an improvement in handover behavior when it is only a change in the form.

Population and unit of analysis

Define the population as every handover that occurred during the observation window for the selected queue. The unit is the open action, not the handover itself, because one handover can carry several actions with different outcomes. A single action that moves across three shifts is one chain with three handover events. Record each event in the chain so the analysis can show where the action was lost.

Exclude actions that were already closed before the handover, and record the exclusion count. Include actions that were waiting on the client, because a waiting action still needs a next review date. Include actions that were reassigned during the handover, because a reassignment is a legitimate outcome only when it is recorded. Test the unit definition on two ordinary handovers before collection begins.

Definitions that make the measure reproducible

Define an open action as a task with a named owner and a next step that has not been completed at the moment the outgoing shift ends. Define a carried action as one that appears in the handover note with enough detail for the next shift to act. Define an acknowledged action as one the receiving person explicitly accepts. Define a lost action as one that is absent from the next shift's working view and was not explicitly deferred.

Do not count a general statement such as keep an eye on the queue as a carried action. Do not count an action as acknowledged when the receiver only read the note without responding. A verbal handover can count only when it is written into the shared record before the outgoing shift ends. Each definition should include one positive example and one boundary example so a second reviewer can apply it consistently.

Evidence standard and data dictionary

For each handover event, capture the case identifier, the action, the owner before and after, the promised date, the note reference, and the acknowledgement time. Add whether the action appeared in the note, whether it was acknowledged, and whether it was completed or reassigned by the next handover. Record the source system for each field and whether the value was observed or inferred. Store the thread reference with the sample so the evidence remains available. Keep the file in one approved repository so the evidence can be found later. Keep the packet with the case record so a later reviewer can repeat the check.

Also capture the shift pair, the queue, and whether the handover occurred on a weekend or holiday. These fields help explain a lost action that was caused by an unusual schedule rather than a weak template. If a note was edited after the handover, record the edit time and analyze the original version separately. A reviewer should be able to rebuild the event from the packet without asking the outgoing person. Store the packet with the handover record so the evidence stays available.

Sampling and collection

Draw the sample from the handover log or the shift schedule rather than from a list of memorable failures. Record the export date, the filters, the row count, and the selection rule. Include handovers from every shift pair and every day of the week so the result is not dominated by one busy Monday. If the population is ordered by date, a fixed interval spreads the sample across the window.

Collect the handover note as it existed at the time of the handover, not as it looks after later edits. Do not reconstruct a missing action from the eventual resolution, because that measures the investigator rather than the process. If a note is stored only in a chat channel, record the channel and the retention limit. Note the collection date separately from the handover date.

Analysis and reporting

Report the number of handover events, the number of open actions, and the share carried, acknowledged, and lost. Show the counts by shift pair and by action type. Present the median time between handover and acknowledgement and the share of actions that were reassigned without a written reason. Use the same denominator for every rate and show the number of actions with incomplete evidence.

Inspect the lost actions and describe the pattern without naming the person. A cluster in one shift pair may point to a schedule gap, while a cluster in one action type may point to a missing field in the template. Compare the result with the weekend schedule, because a handover at the end of a long week may fail for reasons unrelated to the note. Report the exclusions and the missing evidence separately.

A useful additional view is the action's age at each handover. An action that has crossed three handovers without a decision is a different risk from a new action that was lost once. Show the age distribution and the number of handovers per action. That view helps the owner distinguish a template problem from an ownership problem.

A second view is to compare the handover note with the next shift's first hour of activity. If the next person opens the same three cases and ignores the fourth that the note emphasized, the note may be prioritizing the wrong work. Record the first actions taken and compare them with the stated priorities. That comparison shows whether the handover changed behavior or only documented it.

Limitations and sources of error

The record cannot show whether the next shift understood the action but chose not to do it. It can show only what was written, acknowledged, and completed. A lost action is not proof of carelessness, and a carried action is not proof that the work was correct. The protocol also cannot capture a handover that happened entirely in person and left no written trace.

Handover notes can be edited, deleted, or stored in a channel with a short retention period. A note that was clarified in a call may look incomplete in the record. Record those cases and their treatment instead of dropping them silently. If the same person wrote the note and performed the next shift, note the independence limitation and analyze that subgroup separately.

Review cadence and next action

Give the result to the shift lead and the operations owner and ask them to choose one observable change. The change might be a required next-action field, an acknowledgement step, or a rule that no handover closes without a named receiver. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the template and the shift schedule at the same time.

Repeat the protocol with the same definitions after the change and compare the same fields. If carrying improved but completion did not, the note may be clearer without the work becoming easier. If acknowledgement improved but lost actions did not, the receiver may be accepting too many items without the capacity to act. Close the review when the owner accepts the finding and the next sample is scheduled.