Async standups were supposed to fix the timezone problem. They replaced the meeting but kept the format — and the format is the problem.
The standup format asks: what did you do yesterday, what will you do today, what is blocking you? This is a status collection format. It tells you what happened. It does not tell you what needs to happen next, who owns it, or what authority the next person has to act.
The wrap format is a structured alternative designed for distributed engineering teams that need to transfer state, not collect status.
What Is the Wrap Format?
A wrap is a structured end-of-shift declaration. It is published before the engineer goes offline — not the next morning when context has faded. The format has five required sections:
- What shipped — PRs merged, deployments completed, tickets closed
- What is in progress — active workstreams with current status
- What is blocked — blockers with owner, reason, and expected resolution
- Decisions made — what was decided during the shift and why
- Next actions — what happens next, who owns each action, and what authority they have
The key difference from a standup: the wrap is forward-looking and ownership-explicit. It does not just report what happened — it transfers responsibility for what happens next.
Async Standup vs. Wrap Format
| Dimension | Async Standup | Wrap Format |
|---|---|---|
| When written | Start of day (context faded) | End of shift (context fresh) |
| Question answered | What did you do? | What does the next person need to do? |
| Includes decisions? | Rarely | Always — what was decided and why |
| Includes authority? | Never | Always — who can act in my absence |
| Queryable? | No (posted to channel, scrolled past) | Yes (structured, AI-queryable) |
| Time to complete | 2-5 minutes | 60 seconds (structured format eliminates blank-page) |
| Output | A message | A commitment |
Why the Wrap Is Faster Than a Standup
Most engineers report that wraps take 60 seconds. Async standups take 2-5 minutes. The paradox: the wrap contains more information but takes less time.
The reason is structure. An async standup presents a blank text box. The engineer must decide what to write, how to organize it, and what level of detail to include. A wrap presents five structured sections with clear expectations. The structure eliminates the blank-page problem.
How Teams Adopt the Wrap Format
Week 1: Parallel Run
Keep your existing async standup. Add the wrap as an end-of-shift habit. Do not force adoption — let engineers experience the difference.
Week 2: Comparison
Ask the team: when you started your shift, was the standup or the wrap more useful? The answer is always the wrap, because it was written while context was fresh and includes next actions.
Week 3: Switch
Drop the async standup. The wrap replaces it. Most teams report that the standup was already redundant by week 2.
Frequently Asked Questions
What is the wrap format?
The wrap format is a structured end-of-shift declaration designed for distributed engineering teams. It has five sections: what shipped, what is in progress, what is blocked, what decisions were made, and what happens next. Unlike an async standup, it transfers state and responsibility — not just status.
How is the wrap format different from an async standup?
An async standup asks "what did you do?" and is typically written at the start of the day when context has faded. A wrap asks "what does the next person need?" and is written at the end of the shift when context is fresh. The wrap includes decisions, authority, and next actions — an async standup does not.
How long does a wrap take to write?
Most engineers complete a wrap in 60 seconds. The structured format eliminates the blank-page problem that makes freeform async standups take 2-5 minutes. Structure is faster than freedom.
Can the wrap format replace our daily standup meeting?
For most distributed teams, yes. The wrap replaces the information-transfer part of standups entirely. Some teams keep a short 10-15 minute sync for relationship and culture, but the 45-minute catch-up meeting disappears because context is already declared.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.