What to say in standup when you can't remember yesterday

If you blank, say the one thing you're sure of, what you're doing today, and any blocker. That's a complete update. To stop it happening, spend two minutes before standup checking your calendar, sent messages and commit history. Then write two lines before you stop work each day. A paper log is enough for most people. Dayflow helps on a Mac if notes keep slipping.

It’s your turn in standup. The person before you gave a tidy update with ticket numbers. You open your mouth and realize you have no idea what you did yesterday. You know you were busy. You remember closing the laptop tired. But the actual work has gone, replaced by a vague sense of “some stuff on the dashboard, I think.”

So you say something like “still working on the same thing,” which is half true. Or you describe what you did two days ago, because that’s what comes to mind. Then you spend the rest of the call feeling slightly fraudulent, even though you worked a full day.

This article covers what to say in the moment when you blank, why yesterday disappears so easily, and a handful of small habits, mostly paper and a calendar, that make the morning update almost automatic. Dayflow publishes this blog and makes a Mac app that comes up once near the end. Most of what follows needs no software at all.

The short version

• If you blank right now, say the one thing you’re sure of, what you’re doing today, and any blocker. That’s a complete standup update.
• Before standup, take two minutes to check yesterday’s calendar, sent messages, tickets and commit history. Most of your day is sitting there.
• Before you stop work, write two lines: what moved forward, and what you’ll pick up next. Read them out tomorrow.
• Talk in outcomes, not activity. “The export now handles empty rows” is easier to remember than a list of files.
• Put the habit where you’ll trip over it: a sticky note on the monitor, or a kitchen timer at the end of the day.

Why can’t I remember what I did yesterday?

A typical work day isn’t one task. It’s a review, a reply, half a bug, a meeting, a different half of the same bug, three messages, and a long stretch reading something that turned out not to matter. Each piece is small, and small pieces don’t leave much of a mark. By the next morning they’ve blurred into one gray block labeled “work.”

Context switching makes this worse. When you move between things often, each one gets less attention, and memory tends to follow attention. Many people find that their most fragmented days are the hardest to recall, even when those days were genuinely productive. If you’ve ever asked where did my day go at 6pm, you know the feeling.

There’s also a timing problem. Standup asks you to recall yesterday at the exact moment your head is full of today: the inbox, the thing that’s on fire, the coffee you haven’t finished. You’re switching back to a day that’s already been overwritten.

None of this means you’re lazy or disorganized. It means you’re asking memory to do a job that writing does better. Every step below shifts a little of that job from your head onto paper.

What do I say when my mind goes blank mid-standup?

What to do: Keep a fallback structure in your head and use it without apologizing. Three parts:

1. One thing from yesterday you’re certain about, even if it’s small.
2. What you’re doing today.
3. Whether anything is blocking you.

If you truly can’t recall anything, say so and redirect: “I’ll post yesterday’s details in the channel after. Today I’m on the onboarding emails, no blockers.” The team cares most about today and blockers, because those are the parts they can act on.

Illustration: Instead of “Um, I was doing, uh, a few things on the API, I think, and some reviews,” try: “Yesterday was mostly reviews and the rate-limit fix. Today I’m testing that fix. I’m blocked on access to the staging logs.” It’s shorter, it’s true, and it gives someone something to do.

After a week: Notice whether your updates got shorter and whether you stopped feeling a jolt of dread when your turn came. If you still blank completely, that’s a sign the next steps matter more than the script.

Check the trail you already leave

What to do: Most of yesterday is already written down, just scattered across places you don’t think of as a record. Before standup, spend two minutes looking at:

• Yesterday’s calendar: meetings, and any blocks you scheduled.
• Sent messages and chat threads where you replied.
• Tickets or tasks you moved, closed or commented on.
• Your commit history or document edit history, if your work produces those.
• Your browser history, which is good at reminding you what you were reading at 3pm.

Write the two or three things that stand out on a scrap of paper. That’s your update.

Illustration: Your calendar shows a 2pm design review. Your sent messages include a long reply about button states. Your commit history has two small commits on the settings page. Now you have it: “Yesterday I was in the design review, followed up on button states, and pushed the first part of the settings page.”

After a week: Time the sweep. If it’s dropping under two minutes and you’re walking into standup with notes, it’s working. If you keep finding that the important work left no trail, like a long debugging session or a whiteboard conversation, the next habit covers that gap.

Write two lines before you stop work

What to do: At the end of the day, before you close anything, write two lines:

• What moved forward today.
• What you’re picking up first tomorrow.

Keep them in one place: a paper notebook, a text file, a pinned note. In the morning, read them. Your standup update is already written. If you’d like a ready-made layout, the end-of-day report template is built around this idea.

The second line does more work than it looks. It saves tomorrow-you from the “where was I” fog, and it gives you a ready answer for “what are you doing today.”

Illustration: “Moved forward: found the cause of the duplicate emails, it’s the retry job. Next: write the fix and a test for it.” Next morning: “Yesterday I tracked the duplicate emails to the retry job. Today I’m fixing it and adding a test.”

After a week: Count how many days you actually wrote the lines. If it’s most of them, keep going. If it’s one or two, the habit needs a better trigger. See the last step below.

Keep a running log while the day happens

What to do: Some people forget the end-of-day note because by 5pm the morning has already gone. If that’s you, jot a few words each time you switch tasks. No sentences, no times unless you want them. A notebook next to your keyboard works well because it’s visible and needs no app switching. The daily work log template gives you columns if you like structure.

You don’t need to catch everything. Even five or six entries across a day are enough to rebuild it the next morning.

Illustration:

• review: Sam’s PR
• bug: duplicate emails, checking logs
• call with support re: refunds
• back to emails bug, found retry job
• wrote up notes for design review

At standup, you scan the list and pick the two that mattered.

After a week: Look back at the full week’s entries. If you can rebuild any given day from them, the log is doing its job. If entries trail off after lunch, try the end-of-day note instead, or combine the two: a morning log and a two-line wrap-up. There’s more on this in how to remember what you worked on.

Change what you report

What to do: A lot of standup anxiety comes from feeling you have to account for every hour. You don’t. Report outcomes and decisions, not activity. “The import now skips empty rows” is one clear sentence. “I worked on the import, looked at some edge cases, read the docs, tried a couple of things” is a list of things to remember, and it says less.

If your team’s standups drift into time accounting, it’s fair to suggest a format: one outcome, one plan, one blocker. Shorter formats are easier on everyone’s memory, not just yours.

Illustration: A day of fiddly CSS might sound like nothing in activity terms. As an outcome: “The pricing page now lines up on small laptop screens.” That sentence is easy to remember because it describes something that changed.

After a week: Listen to your own updates. Are they getting to the point faster? Are teammates asking fewer follow-up questions? If people still look confused, add one line of context about why the outcome matters.

Put the habit where you’ll trip over it

What to do: The weakest part of any memory habit is remembering to do it. So don’t rely on remembering. Attach the habit to something that already happens:

• A sticky note on the edge of your monitor that says “2 lines before you go.”
• A kitchen timer or phone alarm set for 15 minutes before you usually stop.
• A recurring 5-minute calendar block at the end of the day called “wrap up.”
• A friend or teammate you swap end-of-day lines with by message.

The swap works surprisingly well. Knowing someone will see your two lines makes them more likely to exist.

Illustration: You and a coworker agree to send each other “done / next” at 5:15. It takes 30 seconds, and the next morning both of you have your updates ready.

After a week: If you wrote your note on most days, the trigger works. If the alarm went off and you dismissed it, move the trigger to something harder to ignore, like the moment you close your laptop lid. A paper note sitting on top of the keyboard is hard to miss.

Where seeing your actual day helps

Every habit above depends on you doing something: writing a line, checking a calendar, setting an alarm. On good weeks that’s fine. On bad weeks, the note is the first thing to go.

An automatic record removes that step. Dayflow is a free, MIT-licensed Mac app (macOS 14 or later) that records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. You don’t start a timer or remember to log anything. The next morning, you scroll back through yesterday and see what was actually on your screen. Full recordings and the timeline are stored on your Mac.

You choose where the analysis happens. A local AI model can keep screenshot analysis on your Mac. Or selected screenshots go to a cloud provider you configure, or to Dayflow Pro, an optional plan at $20 a month. You can export a date range as Markdown from Settings → Export, which makes a decent starting point for a standup note. There’s more on that in automatic standup updates.

One honest caution: AI summaries can miss or misinterpret work, so check the timeline before you read it out to your team.

Dayflow is our product, and Dayflow publishes this article. The details here come from Dayflow’s own documentation for version 2.2.0, not from testing.

Where Dayflow is the wrong pick

• You’re not on a Mac. Dayflow is Mac only. On Windows, Linux or a tablet, a notebook or a plain text file with two lines a day wins outright.
• The two-line note already works for you. If you write it most days, an app adds little. Paper is faster, private by default and free.
• Your work happens off-screen. Dayflow sees only the screen. Whiteboard sessions, phone calls, site visits and hallway decisions won’t appear. A running paper log covers those better.
• Your team needs a shared view. Dayflow has no team reports. If standup is really about a shared board, your team’s issue tracker is the better source of truth.
• You want to block distractions or bill clients. Dayflow has no website blocking, invoicing or payroll. If those matter, compare other options in our guide to Mac time trackers.
• You’d rather not have a screen record at all. That’s a reasonable choice. The manual habits above work without one.

It’s a record of your day, not a coach, a planner or a fix for why the day felt scattered. It shows you what happened. You still decide what to say.

The bottom line

Forgetting yesterday by standup is ordinary. Work days are fragmented, and memory isn’t built to catalog them. You don’t need a better memory. You need yesterday written down somewhere before you need it.

Start with the cheapest version: a fallback line for when you blank, a two-minute sweep of your calendar and messages, and two lines on paper before you stop work. Give it a week. If the note keeps slipping and you work on a Mac, an automatic record can pick up the slack. Either way, the goal is the same: walk into standup knowing what you did, and spend the meeting on what comes next.

Frequently asked questions

What should I say in standup if I can't remember what I did yesterday?

Say the one piece of work you're sure about, what you plan to do today, and whether anything is blocking you. For example: "Yesterday I was mostly on the export bug, today I'm finishing it, no blockers." That covers what standup is for. Nobody needs a full inventory, and a short, true answer lands better than a long, vague one.

Is it bad to say "I don't remember" in standup?

It's not a disaster, but you can say it better. "Let me check my notes and post the details in the channel after" is honest and keeps the meeting moving. What matters more is today's plan and any blockers, since teammates can act on those. If it happens often, the fix is a short note at the end of each day, not a better memory.

Why do I forget what I worked on the day before?

Most work days are a string of small switches: a review, a message, half a task, a meeting, another half task. None of these leaves a clear mark, and sleep tends to blur them together. Busy days with lots of context switching are usually the hardest to recall, even when they were productive. It's a common experience, not a sign that you weren't working.

How can I quickly figure out what I did yesterday before standup?

Do a two-minute sweep of the trail you already leave. Check yesterday's calendar, your sent messages and chat replies, the tickets you moved or commented on, your commit history if you write code, and your browser history. Write down the two or three things that stand out. Most of yesterday is usually sitting in those places, just scattered.

What's the simplest way to remember my work for standup?

Write two lines before you close your laptop: what moved forward today, and what you're picking up tomorrow. Keep them in one place, such as a paper notebook, a text file or a pinned note. The next morning, read the lines out. Most people find this easier than logging during the day, because it happens once and takes under a minute.

Can an app write my standup update for me?

Some tools can draft a summary from a record of your day. Dayflow, for example, records your Mac screen at one frame every 10 seconds and has AI write a timeline you can read back or export as Markdown. AI summaries can miss or misinterpret work, though, so check the draft before you share it. Treat it as a memory aid, not a finished update.

Is Dayflow the best option if I don't work on a Mac?

No. Dayflow runs only on macOS 14 or later, so it's no use on Windows, Linux or a phone. A plain notebook or a text file with two lines per day beats it there. It works on any device, costs nothing and needs no setup. Many people find that simple habit is all they need for standup anyway.

Should standup updates focus on tasks or outcomes?

Outcomes are usually easier to remember and more useful to hear. "The signup form now validates emails" sticks better than a list of files you touched. If your team agrees that updates should be one outcome, one plan and one blocker, there's far less to recall each morning, and the meeting tends to get shorter too.

Does Dayflow cost money?

The Dayflow app is free and MIT licensed. There's an optional Pro plan at $20 a month that handles cloud analysis for you. You can also keep analysis on your Mac with a local AI model, or connect your own cloud provider, whose charges and terms apply. It doesn't do invoicing, payroll, team reports or website blocking.