Small-business outsourcing research
How often does a task handoff note name an owner and a due date?
A protocol for measuring handoff note completeness, including the next action, the named owner, the due date, and the evidence attached.

Research question and scope
This protocol asks how often a task handoff note names an owner and a due date. The unit is one handoff note, identified by the task, the sending shift, and the receiving shift. The study measures whether the note states the next action, the owner, the due date, and the source record. It does not evaluate whether the task itself was important or well designed.
Set the scope to one small business, one queue, and one shift handover. Record the note template, the shift times, and the escalation rule 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 new required field can look like better handoffs when it is only a new prompt.
Population and unit of analysis
Define the population as every handoff note created during the window, including notes for work that was completed before the receiving shift started. The unit is the note, not the task, because a task can be handed off several times. A note that is edited after the handover remains one unit with an edit history. A new note for a different task is a new unit.
Record the queue, the shift, the task type, and whether the task was customer-facing. These strata matter because a billing handoff and a delivery handoff carry different deadlines. Include notes that were written verbally and logged later, because the delay is part of the finding. Test the unit definition on two ordinary handoffs before collection begins.
A note can be written for a task that is already complete, which makes the owner field look empty when no action is needed. Record the task status at the handoff and exclude completed work from the owner rate, or report it separately. Do not count a completed note as a failure. The distinction should be visible in the denominator.
Definitions that make the measure reproducible
Define a complete handoff note as one that states the next action, the named owner, the due date, and the source record. Define the owner as the person who will act, not the person who wrote the note or the manager who was copied. Define the due date as a calendar date, not a relative phrase such as soon. Define a missing element as any required field that cannot be reconstructed from the note.
Do not count a note that says review this as a next action. Do not count a team name as a named owner unless the team has one queue owner. A note that says waiting on customer needs the date of the last contact and the next follow-up date. Each definition should include one positive example and one boundary example.
Evidence standard and data dictionary
For each note, capture the task, the sending shift, the receiving shift, the next action, the owner, the due date, and the source reference. Add whether the task was completed, reassigned, or still open at the end of the receiving shift. Record the person who wrote the note and the time it was sent. Keep the note with the task record.
Also capture whether the receiving person confirmed the handoff and when they first read it. A note that was never read is not a handoff, even when every field is filled. If the owner changed during the shift, record the change and the time. A second reviewer should be able to follow the task from the note to the outcome without asking the sender.
A due date can be a calendar date, a shift label, or a time of day, and the three are not interchangeable when the team compares notes. Record the format the queue uses and convert the others before comparison. A date without a time zone is ambiguous when the team works across regions or across a daylight-saving change. The data dictionary should state the convention once and show an example.
Sampling and collection
Draw the sample from the queue rather than from a list of notes the team remembers. Record the export date, the filters, the row count, and the selection rule. Include notes from every shift and task type so the result is not dominated by one busy handover. If the population is ordered by time, a fixed interval spreads the sample across the window.
Collect the note as it existed at the handover, not as it looks after a later cleanup. If the note was edited after the receiving shift, record the edit time and analyze the original separately. Do not infer a missing owner from the person who eventually did the work. Note the collection date separately from the handoff date.
Analysis and reporting
Report the number of notes, the share with a next action, the share with a named owner, and the share with a due date. Show the counts by shift and task type. Present the share of tasks that were still open at the end of the receiving shift. Use the same denominator for every rate.
Inspect the incomplete notes and describe the pattern without naming the writer. A cluster on one shift may point to a time pressure, while a cluster in one task type may point to an unclear template. Compare the result with the customer-facing share, because those tasks may receive more attention. Report the verbal handoffs separately.
A useful additional view is the gap between the due date and the date the task was actually completed. A note can be complete and still set an unrealistic date that the receiver cannot meet. Show the distribution and describe the pattern. That view helps the owner decide whether the problem is the note or the workload.
A useful cut is the share of notes that were edited after the receiving shift began. An edit can add the missing owner or date, which makes the original note look better than it was. Show the edit rate beside the completeness rate and describe the pattern. That view helps the owner decide whether to measure at handover or at the end of the shift.
Limitations and sources of error
The record cannot show whether the receiving person understood the note or whether the task was done well. It can show only what the note contained and when it was read. A complete note is not proof of a good handoff, and an incomplete note is not proof of a missed task. The protocol also cannot capture a handoff that happened in a brief conversation and was never written down.
Queue systems can merge notes, change timestamps, and hide edits. A note that looks incomplete may have had a field removed by a later automation. Record those cases and their treatment instead of dropping them silently. If the sender and the receiver are the same person, note the independence limitation and analyze that subgroup separately.
Review cadence and next action
Give the result to the owner and the shift lead and ask them to choose one observable change. The change might be a required owner field, a due-date rule, or a handover confirmation step. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the template and the shift time at the same time.
Repeat the protocol with the same definitions after the change and compare the same fields. If completeness improved but handover time rose, the new field may be adding friction. If ownership improved but completion did not, the due dates may be unrealistic. Close the review when the owner accepts the finding and the next sample is scheduled.
Give the shift lead the same protocol and a sample of notes from both shifts during the same week. A template that works for one shift may fail when the handover is compressed or the volume is higher. Record the review date and the change that was tested. The next sample should use the same fields so the comparison is fair.
Sources
- U.S. Government Accountability Office, internal control standards, U.S. Government Accountability Office; checked 2026-11-06
- U.S. Small Business Administration, manage your business, U.S. Small Business Administration; checked 2026-11-06
- NIST Cybersecurity Framework 2.0, NIST Cybersecurity Framework 2.0; checked 2026-11-06
- U.S. Department of Labor, Wage and Hour Division, U.S. Department of Labor; checked 2026-11-06
Frequently asked questions
Does a favorable sample prove the routine caused the result?
No. The design is observational and supports a bounded operating decision, not a universal causal claim.
What should an owner review first?
Start with high-consequence defects, missing denominators, exceptions, and cases that required the owner to reconstruct the evidence.
Related research
How often do customer voicemails wait more than one business day for a reply?
A protocol for measuring voicemail reply delay, the handoff between phone and inbox, and the calls that never get a recorded outcome.
What share of supplier records contain a usable contact and payment term?
A protocol for measuring supplier master data quality, with clear tests for a usable contact, a current term, and an approved bank record.
How much shared-inbox work sits unassigned after one business day?
A protocol for measuring unassigned shared-inbox work, the age of the backlog, and whether a named owner picks up each conversation.