Why an open inbox is not a handoff window

A shared inbox accepts work at any hour, which feels efficient until you count how often a request arrives while the receiving team is asleep. The sender finishes the day believing the handoff is complete, and the receiver starts the next day with an unread queue and no idea what is urgent. The gap is not a communication failure in the usual sense; it is a missing boundary that nobody owns. A handoff window fixes the boundary by making arrival time part of the agreement.

Without a window, each sender invents a private rule about what counts as ready. One person sends a finished brief at the end of their day, while another sends a rough idea and expects the receiver to chase the details. The receiving team then spends its first productive hour triaging quality instead of doing work. A visible window gives both sides one rule to point to when the queue is messy.

Set the window in the receiver's working hours

Define the window as the block when the receiving team will read and accept new work, not as the sender's entire day. A common pattern is a two-hour intake block at the start of the receiver's morning, with a cutoff late in the sender's previous day. The sender still has a full working day to prepare, but the package must be complete before that cutoff. Everyone can see the same clock even when their local hours differ.

Publish the window with the local times written out rather than as an offset from a headquarters time. State the cutoff in the sender's zone and the intake block in the receiver's zone, then link a world clock page beside both. During daylight-saving changes, confirm the displayed times instead of trusting a recurring calendar entry. A window that silently shifts by an hour twice a year will lose credibility faster than a window that is simply inconvenient.

Agree on a readiness bar before the cutoff

A window only helps if the sender knows what must be true before work enters it. Write a short readiness bar: a named deliverable, a stated outcome, the source material attached, and the decision the receiver must make. Work that fails the bar returns to the sender with the missing item named, not with a general request to improve it. The bar should fit on one line in the intake form so nobody needs to consult a handbook.

Apply the bar consistently to small and large requests, because exceptions teach the team that the rule is optional. The coordinator can accept an incomplete request only when the sender marks it as an early warning rather than a handoff. That warning goes into a separate list and does not consume the receiver's intake block. Keeping the two categories apart protects the window from becoming a dumping ground for half-formed work.

Write a note that survives the time gap

The handoff note has to do the job the sender would normally do in person, because nobody is awake to answer questions. Start with the outcome the receiver should produce, then list the constraints, the source links, and the deadline in the receiver's zone. Add one line about what has already been tried so the receiver does not repeat work. A note built in that order lets a reader act without reconstructing the sender's context.

Avoid a note that only forwards a long thread, since the receiver then has to infer which message matters. If a thread is genuinely necessary, quote the two or three messages that carry the decision and link the rest as background. Name the files by their exact titles and confirm the links open for someone outside the sender's permissions. A handoff that depends on access the receiver does not have is not complete, however well it is written.

Name the receiver and the fallback

Every package needs a named receiver, not a team name or a shared queue. The receiver confirms ownership when they accept the work, and the sender can see that confirmation in the same channel. If the named receiver is unavailable, a fallback owner takes the package rather than letting it sit. The fallback should be named in advance so the sender is not forced to guess during a live handoff.

Review the fallback arrangement whenever someone changes role or leave plans. A fallback who has never seen the work type is a name on a form, not a real backup. Pair the fallback with a short note about where the current state lives and what needs a decision first. The shift handoff checklist is a useful model for that short note because it forces the writer to separate state from speculation.

Run one dependency pair through the window

Test the window with one sender-receiver pair that already exchanges work every week. Ask both sides to record arrival time, acceptance time, and the first question the receiver had to ask. Run the pair for two weeks before adding more teams, because a single pair exposes the awkward parts without creating a site-wide change. The coordinator should join the first few handoffs as an observer rather than as a rescuer.

Use the trial to find the real cutoff, not the one that looks tidy in a planning document. If most packages arrive after the stated cutoff, either the sender's day ends later than assumed or the readiness bar takes too long to meet. Adjust the window or the bar, then run another two weeks. The pre-handoff capacity check can show whether the receiver's intake block is realistically sized for the volume.

Measure the window with two counts

Track two numbers: the share of packages that arrive before the cutoff, and the share accepted in the receiver's next intake block. The first number shows whether senders respect the boundary, while the second shows whether the boundary produces a real handoff. A high on-time rate with a low acceptance rate usually means the packages are arriving complete in form but incomplete in substance. Report both counts beside the same window definition so the comparison stays honest.

Review the counts monthly and look for clusters by sender and by work type. A single sender with repeated late packages may need a different cutoff because of a customer commitment, while a whole work type may need a lighter readiness bar. Do not publish a ranking of individuals; publish the pattern and the fix. The commitment log is the natural place to record the change so the next window inherits the lesson.

Sources