Question and scope

This protocol measures the share of cross-team handoffs that receive an explicit acknowledgment from the person named as the receiver. A handoff is any transfer of work, context, or a decision request from one team to another with an expectation that the receiving team will act. An acknowledgment is a response that confirms the named person has seen the package and accepted ownership. The result is a percentage, a median acknowledgment delay in working hours, and a breakdown by handoff type and receiving team.

The question matters because a sent message is often treated as a completed handoff. The sender sees a timestamp and assumes the work has moved, while the receiver may be on leave, may believe someone else owns it, or may not recognize the package as actionable. The ambiguity stays invisible until a deadline passes. Measuring acknowledgment separates the act of sending from the act of receiving, which is where most coordination risk sits.

Scope is one coordination team and the handoffs it sent or received during a fixed window. Include handoffs that crossed a team boundary in either direction, because a team that receives poorly may also send poorly. Exclude messages that only share information with no expectation of action, and exclude automated notifications that nobody is expected to answer. Record the systems searched, the window dates, and the reviewer names so the count can be rebuilt.

Why acknowledgment is a separate event

Most tracking systems record when work was assigned, not when it was accepted. A ticket can show an owner field filled in minutes after creation, even if the named person never opened it. The field reflects the sender's intent rather than the receiver's agreement. Treating that field as acknowledgment measures data entry, not coordination, and it will make almost any process look healthier than it is.

A second reason is that acknowledgment carries different meanings in different teams. Some teams treat a reaction emoji as acceptance, while others require a written reply that names the next step. A single universal definition will either credit too much or too little. The protocol therefore needs a fixed evidence rule that states which responses count before any handoff is read. That rule should be published with the coding file rather than decided case by case.

Defining the coding unit

The unit is one handoff package with one named receiver and one expected action. Split the package when two receivers are expected to act independently, because each can acknowledge separately. Keep it as one unit when several people must act together on a single decision. Write the split rule into the codebook before sampling so two reviewers make the same choice on similar records.

Use the version of the handoff that existed when the sender marked it ready. Later edits may add context or a clearer owner, but counting those improvements measures how much the team learned during delivery. If the ready moment is unclear, use the first message that names a receiver and an expected action. Mark the source of that timestamp in the record so another reviewer can follow the same path.

Locating the receiver and the acknowledgment

Start with the field or sentence that names the receiver, then confirm that the named person is an individual rather than a group alias. A team inbox is not a named receiver for this measure because no single person has accepted ownership. If the handoff names both a primary and a fallback, code the primary as the receiver and note the fallback separately. The distinction matters when the primary is unavailable and the fallback acts instead.

Search for the acknowledgment in the same channel first, then in the systems the team normally uses for acceptance. A reply in a different channel can count if it clearly references the handoff and names the action. Record the exact channel and timestamp rather than a summary of the response. An acknowledgment that only says "got it" without accepting the action should be coded as a separate, weaker category.

Set a fixed observation window for acknowledgment, such as two business days after the handoff. A response that arrives after the window is still recorded but does not count toward the headline rate. Without a fixed window, a patient reviewer can find an acknowledgment for almost any handoff and inflate the result. The window should match the team's stated service expectation rather than a convenient number chosen after seeing the data.

Building the acknowledgment rubric

Score four elements for every handoff: the named receiver, the response author, the ownership statement, and the next action. The named receiver must be an individual, and the response author must match that person or an explicitly authorized delegate. The ownership statement must accept the work rather than merely acknowledge receipt. The next action must state what happens now, even if the action is to ask a clarifying question.

Use three levels for the overall score: acknowledged and accepted, acknowledged without acceptance, and not acknowledged. The middle category is the most useful because it captures packages that look answered but still leave ownership unclear. A response such as "thanks, will look" belongs there until a later message accepts the work. Keep the level definitions short enough to apply in seconds during coding.

Sampling and evidence rules

Use a census when the team handled fewer than roughly one hundred handoffs in the window. A census removes sampling error and is practical for a single coordinator. Above that threshold, draw a random sample and publish the selection method. Stratify by handoff type and receiving team so a large volume of routine handoffs does not hide a small set of complex ones.

Freeze the sample before reading the packages. Reading first and selecting later invites the reviewer to choose the most interesting cases. Store the random seed or the selection procedure with the sample file, and record any substitutions. If a selected handoff turns out to be out of scope, replace it using the next item on the randomized list rather than picking a similar case by hand.

Quote the smallest phrase that supports each score. A quote anchors the judgment and makes a second review possible, while a paraphrase can quietly add clarity that was not present. When the evidence is a link, record the link and the section heading rather than a summary. Do not credit an acknowledgment that exists only in the reviewer's memory of a meeting.

Handling ambiguous and disputed cases

Some handoffs are acknowledged by a manager on behalf of the receiver. Code the response author as a delegate and note whether the receiver later confirmed the work. Do not treat the manager's reply as equivalent to the receiver's own acceptance unless the team's rule says delegation is allowed. That distinction reveals whether ownership is actually clear or merely covered by a senior person.

When two reviewers disagree, return to the quoted evidence rather than debating intent. If the quote supports both readings, the rubric is ambiguous and should be tightened with a new example. Recode the disputed case and every similar case after the revision, then record the change in a codebook log. The log should name the rule that changed and the date, not just the individual case.

Exclude a handoff only when the record is genuinely unavailable, such as a deleted channel with no export. Mark it unverifiable and report the count separately rather than guessing from memory. A visible gap in the records is itself a finding about handoff hygiene. Hiding that gap inside the acknowledgment percentage makes the process look better than the evidence allows.

Calculating the acknowledgment rate

Report the accepted-and-acknowledged share as the headline, with the acknowledged-without-acceptance share beside it. The gap between the two numbers shows how many handoffs received a reply but not a clear owner. Include raw counts with every percentage so readers can judge how much weight the number deserves. A rate based on twelve handoffs should not be presented like one based on four hundred.

Report the median acknowledgment delay in working hours, not calendar hours, because a package sent on Friday afternoon is not late on Saturday. State the working-hours convention explicitly, including which time zones and holidays were applied. A median is more useful than an average here because one handoff acknowledged after two weeks can distort the mean. Show the count of handoffs that were never acknowledged at all as its own line.

Break the result down by handoff type and receiving team, but suppress groups with fewer than five handoffs. Small groups produce dramatic percentages that invite overreaction. A team that receives complex, permission-heavy work may score lower even with a strong process, so pair the number with the type mix. The coordinator should be able to explain a difference without reaching for a story the data cannot support. Pair the acknowledgment result with the intake delay measure so a slow acknowledgment is not mistaken for slow work.

Reporting patterns without blame

Present the first result as a baseline rather than a verdict on any person. The number describes how the handoff system behaves, not how hard individuals are working. Name the most common failure pattern, such as handoffs to a group alias or packages that arrive without the access the receiver needs. Pair each pattern with one specific change to the intake form or the handoff template.

Publish team-level patterns instead of a ranking by receiver or sender. A leaderboard encourages people to acknowledge quickly rather than accurately, which produces the middle category in bulk. Share the coding file with the receiving teams so they can see how their handoffs were judged. Invite one receiver from each team to review a small second sample, because that review improves the rubric and adds credibility.

Limits and sources of error

The sources cited here describe scheduling, internal control, and project communication in general terms; they do not provide a benchmark for handoff acknowledgment. The protocol therefore produces a local baseline, not an industry comparison. A team should not present its percentage as evidence that it is better or worse than another organization. Readers should treat the number as a starting point for a local conversation about ownership.

Reviewer judgment remains the largest source of error. Two careful reviewers can read the same short reply and disagree about whether it accepted the work. The quote requirement and the second-review sample reduce that risk but do not remove it. Report inter-rater agreement so readers can judge how much confidence the number deserves. A single reviewer should not be the only check on a published result.

Channel coverage is a second limit. A handoff may be acknowledged in a meeting or a phone call that leaves no written trace, and the protocol will code it as unacknowledged. Note which channels were searchable and which were not. If a team relies heavily on verbal acceptance, fix the record-keeping before trusting the rate. The measure is only as complete as the evidence the team leaves behind.

Review cadence

Review the measure after two full cycles before setting a target. One cycle is a baseline, and a target set from a single period is likely to reflect that period rather than the process. At the end of the review, choose one intake change, one owner, and one check date. A practical first change is to require an individual receiver rather than a group alias on every handoff form.

Retire the measure when most handoffs are acknowledged and accepted within the stated window and the middle category has stopped growing. If the team keeps it, report acceptance and mere acknowledgment together, because a rising acknowledgment rate with a rising no-acceptance rate means people are replying faster without taking ownership. Link the result to the request acceptance checklist so the coding rubric and the operating checklist stay aligned. The purpose is to catch an unowned handoff while it is still cheap to fix.

Sources