The daily standup starts at 9:30. By 9:33 someone is unmuting and asking what was discussed yesterday. By 9:38 you're in the third tangent about a problem nobody on the call is best positioned to solve. By 9:50 you've been there twenty minutes and haven't actually surfaced any blockers. By 10:00 you're still talking and your 10:00 meeting is starting in another tab.
This is how most standups go. The format is supposed to be short and structured — yesterday, today, blockers — and instead it's a free-form catch-up that drifts because nobody came in prepped. The fix isn't a different format. The fix is making prep cheap enough that everyone actually does it.
This post is about running a fifteen-minute standup off the notes you and your team already write — and using an AI assistant to draft the "yesterday / today / blockers" three-liner from your existing notes in about ten seconds.
Why most standups drift
The honest reason standups drift is that prep is invisible work. People who prep look the same as people who don't, until the meeting starts. So most teams stop prepping, and the meeting becomes a slow group reconstruction of what happened yesterday.
A few cross-cutting patterns make it worse:
- Context switching. People come into standup from deep work. The first three minutes go to remembering what they did yesterday, which is information that already exists in their notes — they just haven't pulled it together.
- Blocker discovery in the meeting. Someone realizes they're blocked while they're talking. That's twenty minutes too late. Blockers should be surfaced before standup, so the meeting is for resolving, not discovering.
- No shared written record. The standup happens, and an hour later nobody can remember what was said. So the next standup re-discusses half the same things.
The fix is to make the prep happen automatically, hold it in a written format the team can actually scan, and use the meeting itself for the small set of things that actually need a synchronous conversation. Adjacent shapes — incident retros and SOP rot — show up in Running an Incident with AI Notes and Standard Operating Procedures, Without the Wiki Maintenance Tax.
Standup prep as a markdown page
In Docapybara, standup prep is just a daily markdown page. The simplest convention: a page titled with today's date, organized by team member, with the three lines each (yesterday / today / blockers).
A common shape:
Standups → 2026-04-26 (today's page) with one section per personStandups → Standup Notes Template (the template page that gets duplicated each morning)- Each person also has their own working pages — meeting notes, project pages, daily logs — that the standup page draws from
Plain markdown means the standup page is searchable, copyable, and exportable. When someone misses standup, they read the page. When you're trying to remember when something was first discussed, you grep across the standup pages. There's no separate standup tool to log into.
The agent drafts your three lines from your notes
Here's where standup prep stops being a chore. Capy, the assistant inside Docapybara, reads across your vault when you ask. So your morning prep is a single sentence:
"Based on my work yesterday — meeting notes, project pages, anything I wrote — draft my standup three-liner: what I did, what I'm doing today, what's blocking me."
What comes back is a draft. The agent reads your meeting notes from yesterday, looks at any project pages you updated, scans for explicit "tomorrow" or "next" notes you left yourself, and assembles a three-line summary in your voice. You edit the parts that need editing — usually adding the priorities you've decided overnight that aren't in your notes yet — and paste it onto today's standup page.
Total time: about a minute. The mechanical work of remembering what happened yesterday becomes the agent's job. You bring the human judgment about what matters most today. The agent-acts-on-docs idea behind this is described in Claude Code for Documents.
A live database of blockers that doesn't disappear after standup
A :::database::: directive embeds a live database directly inside any markdown page. The most useful place to put one in standup work: a team-level blockers page with columns for blocker description, person blocked, person needed (or "team"), date raised, target resolution, status (Active, In Progress, Resolved, Punted), notes.
Six column types are available, which covers most blocker tracking. Sort by date raised and you see what's been sitting longest. Filter by status and you see what's actually open. Filter by person needed and you know who to nudge.
When someone surfaces a blocker in the morning prep, they tell the assistant: "Add a blocker — I'm waiting on the marketing team to confirm the launch date before I can finalize the technical timeline." The agent adds the row. When the blocker resolves, you ask the assistant to mark it resolved. When you're in standup the next morning and the question is "anything still blocked from yesterday?", you read the database, not your memory.
This is the part that pays for the rest of the setup. Most blockers in most teams die quietly because nobody tracked them past the meeting where they were raised. A live blockers database keeps them visible until they actually move.
A quick walkthrough of a working morning prep
Here's what a working standup-prep routine looks like in practice for one person, every weekday:
- Open Docapybara. The previous day's standup page is right there — you scan it for what you said you'd do today, last yesterday.
- Open today's standup page (created by duplicating the template).
- Ask the assistant: "Draft my standup section for today's page. Pull from my notes since yesterday's standup." Wait about ten seconds.
- Read the draft. Edit the parts that don't sound right. Add the priorities you've decided overnight. Add any blockers to the team blockers database.
- Paste your section into today's standup page.
Total time: two to three minutes. Done before the standup starts. The standup itself is then for the three things that actually need synchronous conversation: cross-team coordination, blockers that need a real-time decision, and the small adjustments that come out of hearing what other people are doing.
Recording the standup, and rolling up across teams
Some teams record their standups so people who are out can catch up async. Docapybara records audio in the workspace and transcribes with speaker labels — so the standup recording becomes a searchable text artifact on the standup page. You don't have to do this; most teams shouldn't. But for teams that span time zones, or for teams where one or two key people are often out, having the standup transcribed against the standup page means async catch-up is reading a five-minute summary instead of watching a fifteen-minute video. You can ask the assistant: "From this standup transcript, extract any new commitments people made and any new blockers raised. Add the commitments to each person's section and the blockers to the team blockers database." What comes back is a clean delta from what was already on the prep page.
The same shape scales across multiple teams. For organizations large enough that there are several standups (engineering standup, design standup, ops standup) and a leadership team that wants a daily snapshot across all of them, each team's standup page lives at Standups → Engineering → 2026-04-26 etc. The leadership page asks the assistant: "Summarize what's happening today across all team standup pages — give me one paragraph per team and a roll-up of the top three blockers across the company." What comes back is a daily snapshot the leadership team can read in two minutes. No separate cross-team meeting required.
A weekly review that writes itself
The natural extension of daily standup prep is a Friday weekly review. Same pattern:
"Summarize what got done across the team this week. Pull from the daily standup pages. Flag anything that was committed to early in the week and didn't move."
What comes back is a weekly status that reads like something a person actually wrote — because it was assembled from the things real people wrote across the week. You read it, edit the parts that need editing, and you have your weekly status update without spending forty minutes writing it from scratch.
The same shape works for monthly retros, quarterly business reviews, and any other reporting cadence. The underlying notes do the work; the agent does the assembly; you do the smaller, valuable work of judgment and adjustment. For onboarding new hires onto the routine, AI Notes for Customer Onboarding Documentation covers the same playbook-plus-per-account shape.
Try Docapybara free
The smallest test: tomorrow morning, before standup, open Docapybara. Paste in your notes from yesterday — wherever they live now. Ask the assistant for your three-line standup prep. Read what it gives you. If it's at least 80 percent of what you would have said, the rest of the routine is just shape.
Try Docapybara free — bring your messiest meeting notes from this week, the standup format your team currently runs, and the blockers list that's been living in your head. See how the workspace handles them.