Guide

How to write async standup updates

Updated November 2026 · by Jerry Liu, Dayflow's founder

Write three short lines: what you finished, what you will do next, and what is blocking you, with a name attached. A plain notes file kept during the day and a 10-minute timer are enough for most people. Dayflow, a free Mac app, helps when you forget to take notes, because it keeps an automatic timeline of your screen to draft from.

It is 9:52. The standup thread opened at 9:00, three teammates have already posted tidy little updates, and you are staring at an empty message box trying to remember what you did yesterday. You know you were busy. There was the bug that turned out to be a config issue, a call that ran long, a review you got halfway through. None of it feels like a sentence.

So you type “Worked on checkout, continuing today, no blockers.” It is true, and it tells nobody anything. Tomorrow you will write nearly the same line. Or you go the other way and spend twenty minutes polishing a paragraph that people skim past.

This guide covers why async updates are harder to write than they look, six habits that make them quick and useful, and where an automatic record of your day fits in. Almost everything here needs nothing more than a notes file, a timer and a teammate. We make Dayflow, a Mac app that shows up in one section near the end. The Dayflow details in that section come from its own documentation and settings as reviewed on 2026-09-06, not from any testing.

The short version

Why are async standup updates so hard to write?

A spoken standup has built-in help. Someone asks a follow-up, you see a teammate’s face when you mention the migration, and the meeting ends whether you are done talking or not. An async update has none of that. You are writing to an audience you cannot see, with no time limit, about a day you have to rebuild from memory.

Memory is the first problem. Most workdays are full of small switches: a message, a quick fix, a tab you opened to check one thing. By the next morning those blur into “I was busy.” Many people find they can recall the big meeting and the last thing they did, and almost nothing in between. If you often get to the end of a day unsure where it went, where did my day go covers that feeling in more detail.

The second problem is that activity is easier to remember than outcomes. You remember that you were in the codebase for three hours. You have to think harder to say what is different now because of those three hours. Activity feels safe to report, but it is the part your team needs least.

The third is the blank page. With no fixed shape, every update starts from scratch, and starting from scratch every day is tiring. That is where the vague one-liner and the over-long paragraph both come from.

And then there are blockers. Writing “I’m stuck” in a public thread can feel like admitting you are behind, so people soften it, bury it, or leave it out. The update then fails at the one job only it can do: getting help to you before a small delay becomes a big one.

None of this means you are bad at updates. It means the format asks you to do memory work, editing and social judgment at once, first thing in the morning. The habits below split those jobs apart.

Keep a running note while you work

What to do. Open a plain text file, a page in a notebook, or the daily work log template. Each time you finish something or switch to something else, write one line. No full sentences needed. The point is not to track your time, it is to leave breadcrumbs for tomorrow’s update.

Illustration. A running note for a Tuesday might look like this:

That took maybe two minutes across the whole day, and tomorrow’s update is mostly written.

How to tell after a week. Look at how long your updates took to write on days with a note versus days without one. If the noted days were faster and more specific, keep it. If you kept forgetting to write anything, try putting the file somewhere you see constantly, or a sticky note on the edge of your screen that says “one line.” There are more ideas for this in how to remember what you worked on.

Use the same three lines every time

What to do. Pick a fixed shape and never start from a blank box again. The classic is:

Write each item as an outcome. Ask yourself, “What is true now that wasn’t true yesterday?”

Illustration. Turning the Tuesday note above into an update:

Notice what is missing: the hours, the false starts, the reproducing. Those mattered to you. They do not help anyone reading.

How to tell after a week. Read your five updates in a row. Could a teammate who missed the whole week understand where your work stands from those alone? If yes, the shape is working. If they read like “worked on X” five times, push harder on the outcome question.

Draft at the end of your day, not the start

What to do. Spend the last ten minutes of your workday writing tomorrow’s update. Yesterday is still in your head, and you can decide what “Next” really is before you log off. If your team posts in the morning, save the draft and give it a quick edit before posting. The end-of-day report template has a layout that doubles as a standup draft.

Illustration. At 5:20 you jot “Next: refund emails draft, then the export bug.” At 9:05 the next morning you see that the export bug became urgent overnight, swap the order, and post. Total morning effort: under a minute.

How to tell after a week. Notice how your mornings start. If you are getting into real work sooner, and you are no longer spending the first half hour reconstructing yesterday, this one is earning its place. Some people also find it makes it easier to stop work at a reasonable hour, because the day has a clear ending.

Write blockers so someone can act on them

What to do. Every blocker gets three parts: who can unblock you, what exactly you need, and by when. Put blockers on their own line, last, so they are the thing people’s eyes land on. If you are not blocked, say “Blocked: nothing” so readers do not have to wonder.

Illustration. Compare these two:

The second one gives Dana a task, a deadline and a reason. It reads as coordination, not complaint.

How to tell after a week. Count how many of your blockers got a response the same day. If the number went up compared with your old style, the format is doing its job. If blockers still sit unanswered, ask your lead whether there is a better place to raise them, such as a direct message the moment they appear, with the standup as the record.

Set a 10-minute timer

What to do. Use a kitchen timer, your phone, anything that rings. Ten minutes to turn your note into three lines and post it. When it rings, post what you have. This is less about speed than about stopping the slow drift into polishing. If a teammate needs the full story, link the ticket or document instead of pasting it in.

If your team is still debating whether to move standups to writing at all, the meeting cost calculator puts a rough number on a daily call, which can make that conversation more concrete.

Illustration. Monday morning, you start the timer. Three minutes to read your note, four to write the three lines, one to add a link to the design document, and you post at the eight-minute mark. Without the timer, the same update might have grown a paragraph about why the estimate changed.

How to tell after a week. Did you beat the timer most days? If you often ran over, check whether you were writing a diary. Updates that need more than ten minutes are usually doing a job a weekly summary should do instead. For that, see how to write a weekly status report and the weekly status report template.

Ask one teammate what they actually use

What to do. Pick a teammate or your lead and ask a simple question: “When you read my standup, what do you look for?” Some people only read blockers. Some want to know when something will be ready for them. Some just want to see that work is moving. Write for the answer, not for an imagined critic.

You can also offer to swap: you read theirs closely for a week, they read yours, and you each send one note on Friday about what was useful and what was noise.

Illustration. You ask your lead, who says, “Honestly, I just want to know if anything will slip.” From then on you add one phrase to “Next” when a date is at risk, like “refund emails, may slip to Thursday if the copy review runs long,” and you stop explaining the details of finished work.

How to tell after a week. Fewer follow-up questions in the thread is a good sign. So is your teammate’s Friday note being short. If people keep asking “when will X be done?”, your updates are missing dates that readers care about.

Where seeing your actual day helps

Most of the habits above lean on one fragile thing: remembering to write the running note. On scattered days, that is exactly what slips, and you are back to rebuilding yesterday from guesswork.

Dayflow takes the remembering out of it. It records your Mac’s screen at one frame every 10 seconds and has AI write the day into a readable timeline, so the next morning you can see what was actually on your screen instead of trying to recall it. Recordings and the timeline are stored on your Mac. You choose how analysis runs: Local AI through Ollama or LM Studio keeps screenshot analysis on-device, your own cloud provider receives selected screenshots under its own terms, or Dayflow Pro handles cloud analysis and, under the privacy policy, deletes screenshots after processing. The local and cloud processing page explains each mode.

You can export a date range as Markdown from Settings → Export and pull lines into your draft. The export work history workflow walks through it, and automatic standup updates goes further.

Treat the timeline as raw material. It shows activity. You still decide what changed and what matters. AI summaries can miss or misinterpret work, so check before you post.

Dayflow is $0 and MIT licensed for macOS 14 or later, with an optional Pro plan at $20 a month (pricing). Dayflow publishes this article.

Where Dayflow is the wrong pick

You are not on a Mac. Dayflow runs only on macOS 14 or later. On Windows, Linux, or a day spent mostly on your phone, a plain text file or a paper notebook does the job better.

Your work happens off-screen. Dayflow sees only your screen. A whiteboard session, a hallway conversation, or an hour thinking through a design on a walk will not appear in the timeline. If much of your work looks like that, a running note on paper captures more.

You want a team standup tool. Dayflow has no team reports. It does not collect your teammates’ updates, remind anyone to post, or publish to your team chat. For running standups across a team, the chat thread or shared document your team already uses wins.

You want something to keep you on task. Dayflow is a record, not a coach and not a blocker. It has no website blocking and will not nudge you back to work.

You need billing or payroll. Dayflow does not provide invoices or payroll approvals. If that is what you need, start with our guide to time trackers for Mac.

Screen recording is off the table. If your employer does not allow it, or your screen regularly shows client data you should not record, a handwritten note is the safer choice.

The running note already works for you. If you keep the note reliably, you do not need another app. Keep the habit.

The bottom line

A good async standup update is three short lines about what changed, what comes next, and who can unblock you. The hard part is not the writing, it is remembering yesterday at 9 a.m. with a blank box in front of you. Fix that first with a running note and an end-of-day draft, keep the shape fixed, give blockers a name and a date, and stop when the timer rings.

Try two of these this week, not all six. The running note and the three-line shape are a good start. If you are on a Mac and the note keeps slipping, an automatic timeline can fill the gaps, but the judgment about what matters stays with you.

Frequently asked questions

What should an async standup update include?

Three things: what you finished since your last update, what you plan to work on next, and anything that is blocking you. Write each as an outcome someone else can use, such as "payment retry logic merged", rather than an activity like "worked on payments". If a blocker needs a specific person, name them and say what you need and by when.

How long should an async standup update be?

Short enough to read in under a minute. For most people that means three to six lines. If an item needs more explanation, link to the ticket, document or thread where the detail lives instead of pasting it in. A long update usually means you are writing a diary of your day rather than a summary of what changed.

Is it better to write a standup update in the morning or at the end of the day?

Many people find the end of the day easier, because yesterday is still fresh and you can set up tomorrow before you log off. A morning update is harder because you have to reconstruct the previous day from memory. If your team expects morning posts, draft at the end of the day and post the next morning after a quick edit.

What do I write in a standup when I didn't get much done?

Say what you learned or ruled out, because that is progress too. "Confirmed the bug is not in the API, now checking the cache layer" tells the team more than a vague "still investigating". If something pulled you away, like an urgent request or a long meeting, name it plainly. Teammates generally care more about where things stand than about how busy you looked.

How do I flag a blocker in a standup without sounding like I'm complaining?

Make it a request with a name, an ask and a date. For example: "Blocked on staging access. Priya, could you add me before Thursday?" That reads as coordination, not complaint. Put blockers on their own line so they are not buried in the middle of a paragraph, and remove them from the next update once they are cleared.

Can AI write my async standup update for me?

It can produce a rough draft from your notes or an activity record, which saves time on a blank page. It cannot know which items matter to your team or why a task changed direction, and summaries can miss or misread work. Use the draft as raw material, then rewrite it in your own words and check every claim before you post it.

Is Dayflow the best tool for running async standups across a whole team?

No. Dayflow is a personal record of one person's Mac screen. It has no team reports and does not collect or post teammates' updates. For gathering and reading a team's standups, the chat thread or shared document your team already uses beats it. Dayflow only helps an individual on a Mac remember what they did before writing their own update.

How do I remember what I worked on yesterday for standup?

Keep a running note during the day and add one line whenever you finish or switch tasks. It takes seconds and turns tomorrow's update into an edit instead of a memory test. If you often forget to write the note, an automatic record such as a screen timeline can fill the gaps, though you still decide what is worth reporting.

Does Dayflow send my screen recordings to the cloud?

Recordings and the timeline are stored on your Mac. With Local AI through Ollama or LM Studio, screenshot analysis stays on-device. If you choose your own cloud provider, selected screenshots go to that provider under its terms. With Dayflow Pro, Dayflow handles cloud analysis and, under its privacy policy, deletes screenshots after processing and may keep Activity Data for sync.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required