Daily standups vs async updates written from the work
By Soumen Sarkar · October 2026
Comparison. If your problem is unblocking people and settling hard calls, keep the daily standup. If your problem is the status round, where each person recalls yesterday from memory, let an update written from the work carry it. Most leads need both, and the standup gets shorter.
The short answer
If your problem is unblocking people and settling hard calls together, keep the daily standup. If your problem is the status round, where each person tries to recall yesterday's agent sessions at 9:30, let an update written from the work carry that part. Most leads have both problems. The standup stays; it just stops being a report.
What are you trying to fix?
- "Someone is stuck and nobody knows." The standup. A live question gets a live answer in a minute.
- "Two people are about to change the same thing." The standup, or a quick call. Noticing a collision early is what talking is good at.
- "Half the meeting is people reciting what their agents did, and I still can't tell my PM what shipped." An update written from the work. Memory is the weak link here, not the meeting.
The Scrum Guide describes the Daily Scrum as "a 15-minute event for the Developers", held to inspect progress toward the goal, and says the developers "can select whatever structure and techniques they want" (Scrum Guide). Nothing in it says the meeting has to be a round of yesterday's status. Atlassian's own stand-up template already treats the report as written: each person gives "priorities, progress, and problems each day" in an asynchronous check-in (Atlassian). The open question is who writes it.
The same day, with each
This is a scene, not a customer. A lead runs a team of four developers, each with three or four Claude Code sessions going. A PM owns the roadmap.
With a standup alone. At 9:30 each developer gives their round. One says "auth is mostly there." Another lists six small changes, and nobody follows the fourth. The fifteen minutes run to twenty-five. A real blocker, a missing API key for a test account, comes up last and gets "let's take it offline." Afterwards the PM asks the lead what actually landed. The lead opens pull requests to find out.
With an update written from the work. Each session records what it finished in a plain sentence, and each decision with its reason, as it goes. At the end of each person's day Campfyrr writes their update from those lines. The lead and the PM read it the evening before, or with coffee. At 9:30 nobody recites. The lead asks one question: "Who's stuck, and what's about to collide?" The API key gets ten minutes of everyone's attention. The meeting ends early.
At the end of the week, the first lead has a meeting that reports and a PM who still asks. The second has a meeting that unblocks and a PM who reads.
What does an update written from the work look like?
We build Campfyrr this way. This is one person's real update from 9 October 2026, written from what they logged that day:
In short: Daily updates now post to each project's page and Slack,
and Claude connects by signing in.
Done
- Enabled end-of-day updates on project pages and in Slack channels
- Connected Claude to Campfyrr through sign-in, removing the
token-copying step
- Simplified project navigation to open on Updates
Decided
- Only production releases change the live database
The same morning we changed the format on purpose. Our commit says each person's section "opened with counts and labelled every line" before; now it is one "In short" line, then Done, Decided and Next. We also made every line pass a filter that takes out file paths, code and commit hashes, whoever wrote it. The full story is in the real daily update.
When the standup alone is the better choice
- Two or three people on one product. Everyone already hears everything. A written update adds little.
- The team is new. People who don't know each other yet need the face time more than the report.
- Most work doesn't go through coding agents. Campfyrr only knows what sessions log. Design reviews, calls and hand-written changes stay out unless someone records them.
- You need a sign-off. The update is a summary, not an approval step. It doesn't replace your tracker or a release note.
What it costs
The standup has no licence fee. Its cost is time: at the Scrum Guide's fifteen minutes, eight people spend two hours of combined time on it each day, more when it overruns.
Campfyrr is free for one person. For 5 developers and 3 business teammates, five developers at $7 a month billed yearly comes to $35 a month ($45 billed monthly). The PM and other business teammates read and answer free. Everything is free during early access (pricing).
The cost that matters more is the habit. The update is only as good as what sessions log. Anything nobody recorded is missing from it, so a quiet update can mean a quiet day or an unlogged one. Campfyrr's hooks do the recording as agents work, so nobody writes a report by hand. See what a session gets.
For the wider problems, read telling your CEO and PM what shipped and silos at agent speed. If your status lives in Slack threads too, see status in Slack and standups vs one "where are we" page. For the lead's whole week, see for engineering leads. Every product we compared is in our research.
Verdict
Keep the standup if your team needs to unblock each other, argue a hard call, or spot a collision. Writing can't do those.
Choose updates written from the work if the status round eats the meeting and your PM still asks what shipped.
Use both if your developers run several agent sessions each. Let the record carry the report, and give the meeting back to the people in it.
The problem this answers: Nobody knows what shipped: "I can't tell my CEO or PM what shipped."
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).