A structured transfer of working state from one engineer — or one shift — to the next, made explicit before the outgoing person goes offline.
A declared handoff contains: what shipped, what is in progress, what is blocked and why, who owns the next action, and when the originating engineer will return. It is not a summary of what happened. It is an instruction set for what happens next.
The word "declared" is load-bearing. Declarations are explicit, timestamped, and attributable. They do not require the recipient to infer, ask, or guess.
Contrast with: async standup, which collects but does not transfer state.
Why Declared handoff Matters for Distributed Teams
The declared handoff is the atomic unit of distributed team continuity. Without it, every shift change creates an information vacuum that must be filled by asking questions — which requires the previous person to be available, which defeats the purpose of distributed work.
The 'declared' part is what makes it trustworthy. A handoff that is inferred from commits, ticket updates, and Slack messages is a guess. A handoff that is declared by the engineer before they go offline is a commitment.
Frequently Asked Questions
What is a declared handoff?
A declared handoff is a structured transfer of working state from one engineer or shift to the next, made explicit before the outgoing person goes offline. It includes what shipped, what is in progress, what is blocked, who owns the next action, and when the engineer returns. It is not a status update — it is an instruction set.
How is a declared handoff different from a status update?
A status update tells you what happened. A declared handoff tells you what to do next. Status updates are read-once information. Declared handoffs are queryable records of working state, decision authority, and next actions that the incoming shift can act on without asking the outgoing shift any questions.
Related Terms
Declared state
The explicit, published record of an engineer's or team's current working context — available to anyone who needs it, wi...
Read definitionEngineering wrap
A structured end-of-shift declaration made by an engineer before going offline. The wrap declares current state, outstan...
Read definitionState transfer
The act of passing the current working state of a piece of work from one person to another — explicitly and completely —...
Read definitionFurther Reading
Get the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See declared handoff in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.