Question and scope

This protocol measures the share of cross-team handoffs that reach their receiver through a single shared inbox or one named person. 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. A single route is a channel or individual that the sender must use because no alternative path is documented or monitored. The result is a percentage, a count of handoffs by route type, and a breakdown by sending and receiving team.

The question matters because a route that works today can disappear when one person takes leave or changes role. The sender rarely sees that risk, since the shared inbox accepts mail regardless of who is reading it. The receiving team may not see it either, because the inbox is treated as a team asset rather than a personal dependency. Measuring the route makes the dependency visible before an absence turns it into a missed commitment.

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 depends on one inbox may also be the only route for its own requesters. Exclude automated alerts that require no action, and exclude personal messages that never carry a deliverable. Record the channels searched, the window dates, and the reviewer names so the count can be rebuilt.

Why a shared inbox hides ownership

A shared inbox looks like a team control because the address survives staff changes. In practice, the address often forwards to one coordinator who has learned the quirks of each sender and keeps the queue moving through memory. When that person is unavailable, the mail still arrives, but nobody knows which messages need a same-day response. The inbox appears healthy while the work depends on a private routing habit.

The dependency also hides from dashboards. A tracker can show that a request was received and assigned, even if the assignment happened because one person read the inbox and recognized the sender. The system records the assignment, not the recognition step. That gap makes the process look more resilient than it is and makes the coordinator's knowledge harder to replace.

Defining the coding unit

The unit is one handoff package with one sender, one receiving team, and one expected action. Split the package when two receiving teams are expected to act independently, because each may be reached through a different route. Keep it as one unit when several people on one team 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 handoff as it existed when the sender first marked it ready. Later messages may add a direct contact or copy a second person, but counting those improvements measures how the team recovered rather than how the handoff was designed. If the ready moment is unclear, use the first message that names a receiver and an expected action. Record the source of that timestamp so another reviewer can follow the same path.

Identifying the routing path

Trace the handoff from the sender's first message to the receiver's first action. Record every channel and person in that path, including forwarding rules and assistant coverage. A request that lands in a shared inbox and is forwarded by one coordinator to the receiving team has a single human route even though two addresses appear. The forwarding step is the dependency, not the public address.

Check the documented process against the observed path. The process may say to use a form, while the actual work arrives through a direct message to the coordinator. That difference is a finding, because the documented route is the one a new sender will try and the observed route is the one the team actually monitors. Record both and note which one carried the handoff.

Look for silent routing rules such as inbox rules, aliases, and calendar invitations that send work to one person. These rules are easy to create and hard to see when the creator leaves. Export the rules with the mailbox owner's permission and record the ones that affect cross-team work. A rule that copies a second reader is a mitigation, while a rule that only moves mail is still a single route.

Building the concentration rubric

Score four elements for every handoff: the entry channel, the number of monitored readers, the named receiver, and the fallback route. The entry channel is where the sender sent the work, and the monitored readers are the people who actually check it. The named receiver is the person expected to act, and the fallback is the documented alternative when that person is unavailable. Each element should be supported by a message, a rule, or a roster entry.

Use three levels for the overall route: diversified, thin, and single. A diversified route has at least two monitored readers and a documented fallback. A thin route has a fallback that exists on paper but has not been tested. A single route depends on one reader or one unmonitored alias. Keep the definitions short enough to apply consistently 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 with a modest queue. Above that threshold, draw a random sample and publish the selection method. Stratify by receiving team so a large volume of routine work does not hide a small set of critical dependencies.

Freeze the sample before reading the handoffs. Selecting cases after seeing which routes look fragile invites the reviewer to choose the most dramatic examples. Store the random seed or the selection procedure with the sample file, and record every substitution. If a selected handoff is out of scope, replace it with the next item on the randomized list rather than picking a similar case by hand.

Quote the smallest passage that supports each score and link to the exact message or rule. A quote anchors the judgment and makes a second review possible, while a paraphrase can add a fallback that was not present. When the evidence is a mailbox rule, record the rule name and the date it was created. Do not credit a fallback that exists only in someone's memory of a conversation.

Handling shared-role cases

Some teams rotate inbox duty by week, with a different person reading each Monday. Code the route as diversified only when the rotation is published and the current reader is visible to senders. A rotation that lives in a private calendar is still a single route from the sender's point of view. Record the rotation source and whether the handoff arrived during a known handover gap.

When an assistant reads the inbox on behalf of a manager, code the assistant as the reader and note the delegation. Do not treat the manager's name on the mailbox as proof that the manager reads it. The relevant question is who sees the message in time to act, not who owns the address. If the assistant is also the only person who knows the sender's context, the route is still concentrated.

When two reviewers disagree, return to the quoted evidence rather than debating intent. If the evidence 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 handoff.

Calculating the concentration rate

Report the single-route share as the headline, with the thin-route share beside it. The gap between the two numbers shows how many routes have a fallback that has not been tested. 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.

Break the result down by receiving team, but suppress groups with fewer than five handoffs. Small groups produce dramatic percentages that invite overreaction. A team that receives sensitive or permission-heavy work may rely on a single trusted reader for good reasons, so pair the number with the type mix. The coordinator should be able to explain a dependency without implying that the reader is failing.

Report the count of handoffs that arrived through an unmonitored alias as its own line. These are the cases where the sender believes the work is moving and no one has accepted it. A single-route share without that line can understate the risk, because an alias with no reader is worse than a busy inbox with one. Keep the categories visible in every summary rather than collapsing them into a total.

Reporting patterns without blame

Present the first result as a description of the routing system, not as a judgment on the coordinator who reads the inbox. The number shows where the process depends on one person's attention, which is a design issue as much as a staffing issue. Name the most common concentration pattern, such as a vendor portal that only one login can reach or a client who only trusts one contact. Pair each pattern with one specific change to the routing rule or the coverage plan.

Publish team-level patterns instead of a ranking by reader. A leaderboard encourages people to add readers without training them, which creates the appearance of coverage without the substance. Share the coding file with the sending teams so they can see how their handoffs were judged. Invite one reader 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 internal control, contingency planning, and supply chain risk in general terms; they do not provide a benchmark for inbox concentration. 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 routing.

Reviewer judgment remains a large source of error. Two careful reviewers can read the same roster and disagree about whether a second reader is genuinely monitoring the queue. The evidence 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.

Channel coverage is a second limit. A handoff may arrive through a phone call or a hallway conversation that leaves no written trace, and the protocol will miss it. Note which channels were searchable and which were not. If a team relies heavily on verbal routing, 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 routing change, one owner, and one check date. A practical first change is to add a second monitored reader to the highest-volume alias and test it for a week.

Retire the measure when single routes are limited to deliberate controls and every other route has a tested fallback. If the team keeps it, report single and thin routes together, because a falling single-route share with a rising thin-route share can mean the team added names without adding coverage. Link the result to the vacation coverage plan so the routing map and the leave plan stay aligned. The purpose is to find the dependency while there is still time to build a second path.

Sources