The short version
- A written standup format works when it is short enough to finish in two minutes and aimed at the person who reads it next.
- Three prompts do the job: what moved, what is blocked, what the next person needs to know.
- Longer templates get abandoned, because more fields make more to write and more to read, not more clarity.
- StandIn is not a standup tool. It answers questions from what you wrote down while you are off, in your words, and never guesses.
A written standup format that people finish is short, has three prompts, and is written for the next reader rather than for a manager. The three prompts are: what moved since my last note, what is blocked and who can clear it, and what the next person needs to know. That is the whole format.
Most written standups fail for the opposite reason to the one people expect. They do not fail because they are async. They fail because someone tried to fix a thin standup by adding fields, and the ten-box form is now so heavy that everyone half-fills it. A format people finish is a format that asks for less.
The template, copy-ready
Paste this into your chat tool or doc and delete nothing. The prompts are ordered so the most useful line comes first.
- Moved: the one or two things that actually progressed since your last note. Not everything you touched, the things that changed state.
- Blocked: what is stuck, and the exact person or decision that would unblock it. If nothing is blocked, write "nothing," which is real information.
- For the next person: one line for whoever picks this up while you are off. Where you left the thread, what not to touch, what you would do next.
Three prompts, two minutes, aimed at a reader. If your team hands work across the clock, that third line is the whole ballgame, and it pairs with the end-of-day handoff template.
Why short is the whole point
A format is a contract about effort. Every field you add says "spend more time here," and people answer that by spending less time on each field or by skipping the note entirely. The longer the form, the thinner the answers. This is why the ambitious eight-question template dies in a month while the three-line note survives for years.
Short also protects the reader. A two-minute note takes fifteen seconds to read, so people actually read it. A long update takes minutes to read, so people skim it, so the one line that mattered gets missed. Adding fields feels like adding rigor; it usually just adds to the pile, which is exactly how status update fatigue sets in.
What to leave out
The fastest way to a format people finish is a short list of things you refuse to ask for.
- Leave out "what I did yesterday" as a full log. Nobody needs the whole diary. They need what changed and what is stuck.
- Leave out mood and confidence scores. They look tidy in a dashboard and tell a teammate nothing they can act on.
- Leave out per-project duplication. One note per person beats one note per project per person, which is how the spiral starts.
- Leave out anything a live board already shows. If the card moved, the note does not need to say so again.
What the format cannot do
Here is the honest limit. Even a perfect written standup is a snapshot. It says where things stood when you wrote it, and then it goes quiet. The moment someone reads your note and needs the one detail it did not include, the format has nothing left, and the question waits for you to come back online.
Sarah in Tokyo writes a clean three-line note before she logs off. Alex in Amsterdam reads it, gets moving, and then hits a wall on something the note did not cover. The format did its job and still left him stuck until her morning. A shorter or longer template would not change that, because no template answers a follow-up.
That gap is where StandIn sits, and it is why StandIn is not a standup format or tool. It answers questions on your behalf from what you wrote down, your brief and the record, so Alex gets your answer in your words instead of waiting. When the record does not hold it, StandIn says so rather than guessing. See why bots fail for why saying "I do not have that" beats a confident wrong answer.
Common Questions
What should a written standup include?
Three things: what moved, what is blocked and who can clear it, and one line for the next person. Anything past that lowers the odds the note gets finished.
How long should a written standup be?
Two minutes to write, fifteen seconds to read. If it takes longer to write, people will skip it; if it takes longer to read, people will skim it. For the wider menu, see standup alternatives, ranked by what they cost.
Does StandIn fill in my written standup?
No. StandIn does not write or collect standups. It answers questions from what you already wrote down while you are off, and when the record has no answer, it says so instead of guessing.
A written standup format people finish is a small, honest contract: three prompts, aimed at the next reader, and nothing added just to look thorough. Keep it short and it survives. Then remember its limit, that a note answers once and goes quiet, and let your work keep answering when you are off: from your brief, in your words, without guessing. Size your current ritual first with the standup audit.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to retire your daily standup?
Distributed teams use StandIn to start every shift with full context, no standup required. Engineers publish a 60-second brief. The next shift wakes up knowing exactly what to work on.