How to Draft a Structured Daily Standup Update

Standup is in five minutes and you’re trying to quickly organize what you did yesterday, what you’re doing today, and whether anything’s actually blocking you — the classic three-part structure that’s supposed to keep daily check-ins fast, but only works if everyone’s update is actually organized that way rather than a rambling summary of everything on their mind. Especially for async or remote teams posting updates in Slack instead of speaking them live, having a consistent, quickly-readable format matters even more.

The three-part structure (yesterday, today, blockers) exists specifically to keep updates fast and scannable — deviating from it, even with good information, makes updates slower to read and harder to compare across a whole team.

What makes a standup update actually useful

Each of the three sections answers a distinct, specific question: yesterday covers what was actually completed (not just attempted), today covers the concrete plan for the current day (specific enough to be checkable tomorrow), and blockers surfaces anything actually preventing progress — genuinely worth flagging, not a vague “things are a bit slow” comment that doesn’t give the team anything actionable to help with. Keeping each section concise and specific is what makes a standup update fast to both write and read, which is the entire point of the format.

Different teams use different actual output formats — some speak updates live, some post plain text in a chat channel, some use Markdown in a shared doc, some specifically want Slack-formatted text with the right emphasis syntax — and matching the format to how your team actually consumes updates removes friction on both ends.

Why people get stuck here

• Rambling instead of following the structure. Without deliberately organizing thoughts into yesterday/today/blockers before speaking or writing, updates tend to sprawl into unstructured narrative that’s slower to follow.
• Vague blockers that don’t invite help. A blocker mentioned too vaguely to act on doesn’t actually get resolved faster just because it was mentioned — specificity is what makes a blocker report useful.
• Formatting mismatches for async updates. Posting plain text into a channel that expects Markdown formatting, or vice versa, produces an update that looks worse than the actual content deserves.
• Reconstructing yesterday’s plan from memory. Without notes, accurately recalling exactly what got done yesterday (versus what was merely attempted) takes more mental effort than it should right before a live meeting.

What a good standup notes tool looks like

Uses the standard three-part structure

Prompting specifically for yesterday, today, and blockers keeps the update organized in the format teams actually expect and can scan quickly.

Supports multiple output formats

Plain text, Markdown, or Slack-style formatting covers the range of ways different teams actually consume standup updates, so the output matches wherever it’s headed.

Produces a clean, ready-to-share result

The generated update should be immediately postable or speakable without further editing, since the whole point is speed right before or during a fast-moving daily meeting.

Common mistakes to avoid

• Writing a rambling update instead of sticking to the three-part yesterday/today/blockers structure, slowing down the whole team’s standup.
• Reporting a blocker too vaguely to actually invite help — “stuck on something” versus a specific, actionable description of what’s actually blocking progress.
• Mismatching output format to the channel it’s headed to, posting plain text where Markdown or Slack formatting is expected.
• Padding “today” with an unrealistic list of tasks that won’t actually get attempted, rather than a genuinely achievable plan.
• Forgetting to update “yesterday” honestly when a planned task didn’t actually get finished, blurring what was truly completed versus attempted.

How to do it with Standup Notes Tool

Online Tool Store’s Standup Notes Tool generates your update entirely in your browser.

1. Open the Standup Notes Tool.
2. Fill in yesterday, today, and any blockers.
3. Choose your output format — plain text, Markdown, or Slack-style.
4. Copy the formatted update to share or read from during standup.

Because it’s quick to fill in, it’s practical to use right before a live standup or when posting an async update.

Frequently asked questions

What makes a good “blockers” entry, as opposed to a vague one?

A good blocker entry is specific enough that someone else on the team could actually help — naming the exact issue, what’s been tried, and ideally what kind of help would resolve it — rather than a general statement that something feels stuck without enough detail to act on.

Should “today” list every task I might work on?

It’s usually more useful to list a realistic, prioritized plan rather than every possible task — an honest, achievable list is easier for the team to track against tomorrow than an aspirational one that rarely matches what actually gets done.

Why does output format matter for a standup update?

Different teams consume updates differently — a live spoken standup, a plain-text Slack message, or a Markdown-formatted shared doc all expect slightly different presentation, and matching the format to your team’s actual workflow keeps the update readable without extra manual reformatting.

Final thought

The three-part standup structure works because it’s fast to write and fast to read — sticking to it, with specific rather than vague blockers, is what actually keeps a daily check-in efficient for the whole team.

Try the free Standup Notes Tool