How to Write a Daily Standup Update (2026 Guide)

Keep a running record of your day. Then write three short parts: outcomes since the last update, one to three commitments for today, and blockers with a named person and an ask. A notes file is enough. WakaTime suits editor-heavy developers. ActivityWatch suits Windows or Linux users. Timing suits Mac users who bill hours, and Dayflow suits Mac users who want a free AI-written timeline.

You want a standup update that takes a couple of minutes to write and that a teammate can act on: what moved, what’s next and what’s stuck. What usually happens is different. You open Slack at 9:55, can’t remember most of yesterday, and type “Continued work on the billing migration. Will keep going today. No blockers.” It’s true and it took no effort. Nobody learns anything from it.

The fix is mostly about the hours before you write, not the writing itself. If you have a record of yesterday, the update is an editing job. If you don’t, it’s a memory test. You’ll fail it on your busiest days, which are the days the update matters most.

Disclosure: Dayflow, which comes up in one step below, is our product. It’s a free, open-source Mac app that records the screen at one frame every 10 seconds and has AI write your day into a readable timeline. The method in this guide works without it. Details about the other tools come from each vendor’s own documentation, checked on 2026-10-04. This guide compares that documentation and does not report on using the apps.

The short version

1. Keep a running record of what you did, by hand or with a tool.
2. Pull outcomes out of that record, not activities.
3. Commit to one to three things for today.
4. Write blockers as requests, with a person and an ask.
5. Trim to your team’s format and post.
6. Save the update so the weekly report is mostly done by Friday.

What you need before you start

• Your team’s format. Most teams use some version of yesterday, today and blockers. Some use a free-form Slack thread, some a form in their project tool, some a spoken round. If nobody has said, ask once and stop guessing.
• A place to keep a log. A plain notes file, the daily work log template, or a tracker. Pick one and stick with it for two weeks before judging it.
• Your ticket tracker and repo. You’ll reference ticket and PR IDs so people can click through instead of asking.
• Five minutes at a consistent time. Write the update right after you sit down, before email. That beats writing it in the 30 seconds before the meeting starts.

Step 1: How do you remember what you did yesterday?

What to do. Write things down while they happen, or let a tool do it. After a night’s sleep, memory keeps the big items and drops the small ones: the half-hour fixes, the review you did for a teammate, the bug you ruled out. Those are often the most useful things to mention.

The manual version is a one-line note every time you switch tasks. The daily work log template gives that note a fixed shape so it takes seconds.

If you’d rather not rely on discipline, an automatic tracker can keep the record for you. They differ in what they see:

• WakaTime uses editor and terminal plugins to record coding time per project, language and editor, plus AI coding usage. The free plan keeps one week of dashboard history, which covers a daily update. It only sees supported editors and terminals, so meetings, browser-based code review and Slack threads don’t appear.
• ActivityWatch records the active app, window title and away-from-keyboard time. Browser extensions add tab titles and URLs. It’s free, open source under MPL-2.0, and stores data on your own device. No AI summaries are listed, so you get a raw timeline to read through yourself. See ActivityWatch vs Dayflow for the differences.
• Timing records apps, websites and documents on the Mac, down to URLs and Mail threads, and lists AI activity summaries on all plans. There’s no free tier. Professional is $9 per month billed annually or $11 per month billed monthly, with a 30-day trial and no credit card required. More in our Timing alternative page.
• Dayflow records a frame every 10 seconds and has AI write the day as a timeline of what you were working on. You can export the timeline as Markdown from Settings → Export.

For a wider view of the options, our guide to choosing a time tracker for Mac covers more of them.

Illustration. A manual log for one afternoon might look like this:

13:10 INV-412 retry logic, found duplicate webhook on refund path
14:30 reviewed Priya's PR #881 (pagination), left 3 comments
15:05 call with support re: stuck refunds, 2 accounts affected
15:40 back on INV-412, wrote failing test for duplicate case

Mistake to avoid. Logging every minute. A note per task switch is enough. If keeping the log takes longer than writing the update, you’ll quit by Thursday.

Step 2: How do you turn a list of tasks into progress?

What to do. Read yesterday’s record and ask of each item: did something change that a teammate would care about? Keep the items where the answer is yes and rewrite them as outcomes. An outcome says what’s now true that wasn’t before.

Illustration. The log above becomes:

• Before: “Worked on INV-412. Reviewed a PR. Call with support.”
• After: “INV-412: found the cause of duplicate refunds (webhook fires twice on the refund path), failing test written. Reviewed #881, pagination looks good after 3 small fixes.”

The support call disappears as its own line. Its useful part, that two accounts are affected, belongs in the INV-412 context or in a blocker.

Mistake to avoid. Reporting effort instead of results. “Spent 4 hours on INV-412” tells your team you were busy. “Found the cause” tells them the fix is close. Leave hours to timesheets.

Step 3: What should you commit to today?

What to do. Name one to three things you expect to finish or move to a clear checkpoint today. Use words like “ship”, “open a PR”, “decide” or “hand off” rather than “work on”. Teammates plan around this half of the update, so it should be specific enough to check tomorrow.

Illustration. “Today: fix INV-412 and open the PR. Pair with Sam on the refund dashboard query if he’s free after lunch.”

Mistake to avoid. Listing everything on your plate. A list of seven items is a backlog, not a plan, and it hides which one you’ll actually finish. If your “today” items regularly spill into tomorrow, try the time estimation test. It’s a short exercise for comparing your sense of time with a clock. It’s not a diagnostic, just a way to calibrate.

Step 4: How do you write a blocker so someone acts on it?

What to do. A blocker is anything that will slow you down if nobody else does something. Write it as a request: who, what and by when. A blocker without a name attached is a complaint, and it’ll sit in the thread until tomorrow’s standup.

Illustration.

• Weak: “Blocked on staging access.”
• Useful: “@Dana, need write access to the staging payments DB to reproduce INV-412. Can you grant it before noon? Otherwise I’ll test against a local copy and lose some fidelity.”

Mistake to avoid. Writing “No blockers” by habit while you’re waiting on a review, a decision or access. Waiting is a blocker if it changes your plan. Saying so early is cheaper than explaining a slip on Friday.

Step 5: How long should the final update be?

What to do. Put the three parts together, cut anything a teammate wouldn’t miss, and post. For a written thread, a few short lines is usually right. For a spoken round, aim for something you can say in under a minute and put detail in the ticket.

Illustration. A complete written update:

Yesterday: INV-412 cause found (duplicate webhook on refund path), failing test in. Reviewed #881, approved after small fixes. Today: Fix INV-412 and open the PR. Pair with Sam on the refund dashboard query. Blockers: @Dana, need staging payments DB write access before noon.

Mistake to avoid. Pasting a raw tracker export or an AI summary straight into the channel. You might draft the update with AI, from Timing’s summaries, a Dayflow timeline or your own notes. If you do, edit it first. AI summaries can miss or misinterpret work, and they don’t know which items your team cares about. Check every line before you post it. Our post on automatic standup updates explains how to draft from a timeline while still making the calls yourself.

Step 6: Why save daily updates for the weekly report?

What to do. Keep each update somewhere you can find it again: a notes file, a pinned thread or your log. On Friday, five dailies plus your log turn the weekly status report into a summarizing job instead of a reconstruction. The weekly status report template is built for exactly that.

If your record lives in Dayflow, you can export a date range as Markdown and have an assistant draft the week. The Claude weekly report and Codex work summary workflows show how. A cloud assistant receives whatever Dayflow data it retrieves in the conversation. Local storage doesn’t make that conversation local.

Illustration. Friday’s report opens with “INV-412 shipped Tuesday, duplicate refunds stopped; #881 merged; refund dashboard query in review”. You wrote none of it from memory.

Mistake to avoid. Treating dailies as disposable. They’re the cheapest written record of your work you’ll ever produce. They’re useful again at review time, and when someone asks in March why a decision was made. For more on that, see how to remember what you worked on.

Doing it by hand vs with a tool

None of the three other tools covered here is a plain start-stop timer. Timing comes closest, since it accepts manual time entries alongside automatic tracking.

Approach	Effort	What you get	Cost
Manual log (notes file or template)	A line per task switch, plus discipline	Exactly what you chose to write down, nothing else	$0
WakaTime	Install editor plugins once	Coding time per project, language and editor; AI coding usage. Nothing outside editors and terminals	Free plan with 1 week of history; Basic $9/mo billed monthly, or $8.25/mo billed $99 yearly
ActivityWatch	Install once, read the timeline yourself	App, window title, AFK time, browser tabs with extension; stored on your device	Free, MPL-2.0
Timing	Install once, review and tidy entries	Apps, websites, documents, URLs and Mail threads on the Mac; AI activity summaries; billing features	No free tier; Professional $9 per month billed annually, or $11 per month billed monthly; 30-day trial
Dayflow	Install once, skim and correct the timeline	AI-written timeline of your day from a frame every 10 seconds; Markdown export	$0, MIT; optional Pro at $20 a month

To repeat the disclosure: Dayflow is our product. It’s Mac only and needs macOS 14 or later. With local AI through Ollama or LM Studio, screenshot analysis stays on your Mac. With your own provider or Dayflow Pro, selected screenshots are processed off-device. The details are on local and cloud processing, and plans are on the pricing page.

Common mistakes

Writing for your manager instead of your team. The update is a coordination tool. If it reads like a justification of your time, it’s aimed at the wrong reader. Write what a peer needs to plan their day.

The same update five days running. “Continuing INV-412” for a week tells people something is wrong without saying what. If an item lasts more than two days, say what changed and what’s left.

Solving problems in the standup. When two people start debugging live, everyone else waits. Note it, take it to a thread and move on. If your standup routinely runs long, the meeting cost calculator puts a number on what that round costs your team each week.

Leaking private details. Window titles, URLs and screenshots can contain customer names, personal tabs or messages. Whatever tool keeps your record, the update you post should contain only what you’d say out loud.

Writing it at the last second. Updates written while the meeting is loading are vague by default. Write it first thing, from the record, and post it before you open email.

Where Dayflow is the wrong pick

Dayflow fits one person on a Mac who wants a free, AI-written record of their day. Plenty of situations call for something else:

• You’re on Windows or Linux, or a Mac older than macOS 14. Dayflow won’t run. ActivityWatch covers Windows, Mac, Linux and Android, is free, and keeps data on your device.
• You don’t want your screen captured at all. ActivityWatch records app and window titles rather than screen frames, and a manual log captures only what you type.
• Your standup is mostly about code and your team wants shared metrics. WakaTime gives per-project and per-language coding time, AI usage tracking and team dashboards. Its Team plan is $21/dev/mo billed monthly, or $19.25/dev/mo billed $231/dev yearly, with a 14-day Team trial and no credit card required. Dayflow has no team reports.
• You bill clients by the hour. Depending on plan, Timing has billing status tracking, report rounding and a GrandTotal invoicing integration. Dayflow has no invoicing or payroll approvals.
• You need website blocking to protect focus. Dayflow doesn’t block anything, so pair it with a dedicated blocker or choose a different tool.

The bottom line

A good standup update has three short parts: what changed, what you’ll finish today, and who you need something from. The hard part isn’t the writing. It’s having an honest record of yesterday when you sit down. A notes file and five minutes a morning are enough for many people. If you live in an editor, WakaTime fills in the coding half. If you want a full record without typing, ActivityWatch, Timing and Dayflow each keep one, with different tradeoffs on platform, price and privacy. Whichever you choose, read what it gives you and edit before you post. The update is yours, not the tool’s.

Frequently asked questions

What should a daily standup update include?

A good update answers three things. What did you finish or move forward since the last one? What do you plan to finish next? What is blocking you? For each blocker, name a person and make a specific ask. Reference ticket or PR IDs so teammates can click through. Skip time spent and routine meetings unless they changed something. If your team uses a different format, follow it. The point is that someone else can act on what you wrote.

How long should a standup update be?

Aim for something a teammate can read in under a minute. That usually means three to six short lines in a written thread, or thirty to sixty seconds if spoken. Longer than that and the useful parts, especially blockers, get skimmed past. If you have a lot to say about one item, post the short version. Move the details to the ticket or to a follow-up thread with the people involved.

How do I remember what I did yesterday for standup?

Keep a record during the day instead of relying on memory the next morning. A one-line note each time you switch tasks works, and a daily work log template makes it a habit. Automatic trackers can fill gaps: WakaTime logs editor time, ActivityWatch and Timing log apps and windows, and Dayflow writes a timeline from periodic screenshots. Your ticket history and sent messages make a useful backup.

Can AI write my standup update for me?

AI can draft one if it has a record of your day to work from, such as a tracker timeline, your commits or your notes. Dayflow and Timing both offer AI summaries of tracked activity. Treat the draft as a starting point. AI summaries can miss or misread work, and they cannot know which items matter to your team. Edit for outcomes, add blockers yourself and check every claim before posting.

What do I say in standup when I have nothing to report?

Say what actually happened in one line, such as "Mostly planning and interviews yesterday, no ticket progress." Then give a concrete plan for today. A quiet day reported honestly is fine. A vague update repeated for several days is what raises questions. If something is blocking your progress, that is your real update. Write it as a blocker with an owner and an ask.

Is WakaTime enough for writing standup updates?

If most of your day is in an editor, it covers a lot. WakaTime's plugins record coding time per project, language and editor. The free plan keeps one week of dashboard history, which is enough for a daily update. It only sees supported editors and terminals, so it misses code review in a browser, design discussions and meetings. Pair it with a short manual note for non-coding work.

What should I use instead of Dayflow on Windows or Linux?

ActivityWatch is the better pick there. Dayflow is Mac only and needs macOS 14 or later. ActivityWatch runs on Windows, Mac, Linux and Android, is free and open source under MPL-2.0, and stores data on your own device. It records the active app, window title and away-from-keyboard time, with browser and editor add-ons. No built-in AI summaries are listed, so you write the update from its timeline yourself.

Is Dayflow free?

Yes. Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month that manages cloud analysis for you. The free app can use local AI through Ollama or LM Studio, or your own cloud provider, whose charges and terms apply. It runs on macOS 14 or later only. It does not provide invoices, payroll approvals, team reports or website blocking.

Does a screen-recording tracker send my screen to the cloud?

With Dayflow, it depends on the processing mode you choose. Recordings and the timeline are stored on your Mac. With local AI, screenshot analysis stays on-device. With your own provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Pro deletes screenshots after processing and may retain activity data for sync. If you paste Dayflow data into a cloud assistant, that conversation is not local.