Question and scope
This protocol asks how often a recurring operations handoff loses its named owner before the next cycle begins. A handoff loses its owner when the item moves to a new shift, site, or queue without a person who is accountable for the next action. The measure matters because ownerless work can look normal in a queue while it waits for someone to notice. The protocol describes frequency and stage, and it does not judge whether the original assignment was fair.
Scope is one recurring handoff process in a defined operating period, such as the daily shift change between two coordination teams. Include items that entered the handoff and items that were closed during the window. Exclude one-off projects and informal advice that never became a tracked item. State the scope in the report so a later reviewer can compare the same process across periods.
Population and unit of analysis
The unit is one handoff item, from the moment it enters the outgoing queue to the moment it is accepted by a named owner on the incoming side. An item with several actions should be split when each action has a different owner and time. If the team tracked it as one item, keep one unit and note the lower precision. Use a dated export from the handoff system as the starting list.
Record the process name, shift, item reference, entry time, acceptance time, and current state. Include items that were reopened so the analysis can separate first handoffs from repeats. Exclude items that were never intended to cross a shift boundary, but list the exclusions with reasons. A reproducible denominator is more useful than a large but unexplained sample. Keep the raw export unedited beside the coding sheet.
Definitions and measures
An owner is the person accountable for the next action, not the person who last touched the item. Owner continuity is present when the incoming record names the same accountable person or a documented delegate before the outgoing coordinator leaves. Compute continuity as the share of items with a confirmed owner at acceptance. Also record the time between entry and acceptance so a fast handoff cannot hide a missing owner.
Report ownerless counts by shift, by queue, and by item type. Show the median and 75th percentile for time to acceptance, and use age bands such as under one hour, one to four hours, four to twelve hours, and over twelve hours. Split the result by handoff channel, because a verbal briefing and a written queue have different failure modes. Do not collapse the channels into one average.
Evidence and data dictionary
Each item needs the handoff date, shift, item reference, next action, named owner, due time, and acceptance evidence. Acceptance evidence is a timestamp or message from the incoming owner, not the fact that the item appeared in a queue. If the owner was assigned verbally, record the date and the person who confirmed it. Keep the evidence with the analysis file so the result can be reconstructed.
Preserve owner changes and handoffs between shifts. An item that passed through three queues has a different history from one that waited in a single queue. Record the reason for each change when the team knows it, and mark unknown reasons rather than guessing. Sensitive details should stay in the approved system, with only a reference in the analysis file.
Test design and sampling
Use a census when the handoff volume is small enough to review completely. For a larger volume, draw a documented sample that includes every shift, every queue, and at least one busy period. Freeze the sample before coding so the reviewer cannot choose items that support a preferred result. Have a second person check a subset and record disagreements before resolving them.
A practical starting point is two weeks of handoffs, or the most recent complete operating cycle if the process runs monthly. If the process changes during the window, split the analysis at the change and report both parts. Do not mix a process redesign with the period that preceded it. The comparison is only honest when the definition of an item stayed stable.
Decision rules before the test
Write the decision rules before looking at the result. Decide what counts as a confirmed owner, how long an item may wait for acceptance, and which exclusions are allowed. State whether a delegate named in advance counts the same as the original owner. These choices change the number, so they must be fixed before the reviewer sees the data. Put the rules in the same file as the coding sheet.
Agree on the action that follows a high ownerless rate. One option is to change the acceptance step so an item cannot leave the outgoing queue without a named owner. Another is to add a daily exception review for items that wait too long. Do not begin with a coaching plan, because the pattern may come from the handoff design rather than from individual effort.
Analysis and reporting
Report the share of items accepted with a named owner, the share accepted without one, and the share still waiting at the end of the window. Show the oldest ownerless item and the queue where it sat. Pair the count with a short review of acceptance evidence, because a name in a field does not prove that the person agreed to act. The report should make the next management question obvious.
Break the result down by shift and channel, and show the number of items behind each percentage. A rate from six items should not look as firm as a rate from sixty. If the sample is small, report counts and describe the uncertainty in plain language. Do not present a single averaged rate as if it described every part of the process.
Reporting template
Use a one-page template with four blocks: scope, ownerless rate, time to acceptance, and the action agreed at review. Keep the raw counts beside every percentage so a reader can see the size of the evidence. Add a short note for each exclusion and each process change during the window. The template should be short enough to complete in the review meeting.
Store the completed template with the export and the coding sheet. A later reviewer should be able to open the folder and reproduce the main number without asking for context. If the folder contains several versions, mark the final one and date the change. Evidence that cannot be found is treated as missing evidence. Add the owner of the folder to the report so the chain of custody is clear.
Limits and sources of error
The cited public sources frame records, continuity, privacy, and internal-control practice in general terms; they do not provide a local result for a specific team. A named owner does not prove that the action was correct, and an ownerless item does not prove that the team was careless. The measure also depends on how the team defines acceptance. A broad definition can count a glance as a handoff, while a narrow one can miss a real transfer.
Missing timestamps and reconstructed records are common sources of error. Exclude an item from the time measure when the entry or acceptance time cannot be supported, but keep it in the owner count when the owner is known. Report the number of excluded items beside the result. A clear exclusion rule is better than an exact number built on invented timestamps.
Review cadence
Review the result at a fixed date and end with one process change, one owner, and one check date. A repeated gap should change the acceptance rule or the handoff template before it changes coaching. Keep the export, the coding sheet, and the notes together so the next reviewer can repeat the check. Compare like periods and state any process change beside the result.
Repeat the review after two full cycles, then move to a monthly rhythm if the measure is stable. Retire the measure if it stops informing a decision, because a metric that nobody uses will be maintained badly. The purpose is a handoff that the next person can act on, not a perfect record. Stop when the team can show that outcome consistently.
Sources
- U.S. Department of Labor — reviewed November 5, 2026.
- NIST Cybersecurity Framework — reviewed November 5, 2026.
- U.S. Small Business Administration — reviewed November 5, 2026.
- U.S. Government Accountability Office — reviewed November 5, 2026.
- Federal Trade Commission — reviewed November 5, 2026.
