What Did I Even Do Yesterday? A 30-Second Work Log for Standups and Timesheets
You can't reliably remember your workday afterward, but you can write it down as it happens. A one-line note every time you switch tasks, plus a 3-minute weekly review, covers standups, timesheets and invoices.
The best way to remember what you did at work today is not to rely on memory at all. Write one short line every time you switch tasks, and another whenever something unplanned eats your time. Those lines take about 30 seconds a day in total. They answer "what did I do yesterday?" at standup, fill in your timesheet, and back up an invoice.
That's the whole method. The rest of this guide covers what to write, when to write it, the work people usually forget, and a short weekly review that turns the notes into something useful.
Why you can't remember what you did yesterday
You probably did plenty yesterday. It just didn't stick, and there are good reasons for that.
First, memory for new, unrehearsed details fades fast. Ebbinghaus's forgetting curve, replicated by Murre and Dros in 2015, shows forgetting is steepest soon after learning something. Their test used lists of nonsense syllables, not work tasks. But the pattern fits a 10 a.m. phone call you never thought about again.
Second, workdays are broken up. In a study of interrupted work, Gloria Mark and colleagues found that people who were interrupted made up for it by working faster. They also reported more stress, frustration and time pressure. When you're racing to catch up, nobody stops to note what just happened.
Third, the big task crowds out the small ones. You remember the report you spent all afternoon on. You forget the three quick questions you answered, the printer you fixed and the 40 minutes you spent on a call that "would only take five."
How to remember what you did at work today: the one-line habit
The fix is a daily work log that you add to during the day, not at the end of it. End-of-day recall has the same gaps as next-morning recall, just smaller.
The rule: one line when you switch
Each time you stop one thing and start another, write a line about what you just finished or paused. Keep it this short:
- 9:40 Finished Q3 budget draft, sent to Priya
- 10:15 Call with Henderson re invoice dispute, 25 min, they'll resend PO
- 11:30 Covered front desk for Sam (sick)
- 2:05 Stuck on login bug, tried clearing cache, no luck
A good line has three parts: what, who or which project, and where it stands. Add a rough time if you bill hourly or fill in a timesheet. Skip anything that reads like an essay. If a line takes more than 15 seconds, you'll probably stop doing it by Thursday.
Three triggers worth a line
Task switches are the main trigger. Two more catch most of what slips through:
- After every meeting or call. Write one line on the outcome and any promise you made ("I said I'd send the slides by Friday"). Promises are easy to lose. There's more on that in keeping track of the small promises you make in conversation.
- When something unplanned takes over. A colleague's emergency, a client walk-in or a system outage. These are exactly the hours that vanish from timesheets.
- When you stop for the day. One line on where you left off and what's next. It gives tomorrow's you a place to start.
That last line does a second job. Research by Masicampo and Baumeister found that making a specific plan for an unfinished goal reduced how much that goal stayed on people's minds, even though it was still unfinished. A quick "next: email the supplier first thing" may help you switch off in the evening.
The work people forget to log
Ticket systems, git history and calendars only show part of your day. Tools that build your standup from commits miss everything that never touched a ticket. For nurses, admin staff, consultants and freelancers, that can be a large share of the day.
Watch for these:
| Often forgotten | Why it matters | Example line |
|---|---|---|
| Quick questions from colleagues | Small interruptions add up | "Helped Leo with expense codes, 15 min" |
| Unplanned firefighting | Explains why planned work slipped | "Server down 1–2:30, handled client calls" |
| Covering for someone | Real work, rarely recorded | "Covered Ward 4 meds round for Ana" |
| Waiting and chasing | Shows blockers at standup | "Chased legal for contract sign-off, 2nd time" |
| Prep and admin | Billable on many contracts | "Prep for Monday workshop, 45 min" |
| Small fixes | Easy to drop, nice to show | "Fixed broken link on pricing page" |
| Things you tried that failed | Stops you repeating them | "Tried vendor B's API, rate-limited, dropped" |
The last row is worth its own habit when you're stuck on a problem. See keeping a running log of what you've already tried.
Where to keep your daily work log
The best place is wherever you can add a line fastest, from wherever you usually are. Some options:
- A plain text file or document pinned on your work computer. Fast if you sit at a desk all day. Put a date heading at the top of each day.
- A paper notebook next to your keyboard. Great for people who think with a pen. Harder to search later.
- Your phone's notes app. Best for people who move around: nurses, site workers, field consultants, anyone between meetings. Voice dictation helps when your hands are busy.
- A message to yourself in a chat app. Quick, and timestamped automatically. It gets messy after a few months.
- Your timesheet tool directly, if it allows quick entries. Fine for billing, but it often lacks a field for "what happened" and context.
Whatever you choose, it needs two things: almost no steps to add a line, and a way to find old lines later. A note you can't find is close to a note you never wrote. A dated text file with Ctrl+F works, and so does any notes app with decent search.
Don't set up elaborate categories for this. A single list in date order, newest first or last, is all a work log needs. If you're tempted to organize it, read why organizing your notes keeps failing first.
Using the log: standups, timesheets and invoices
The log is only worth keeping if it saves you time when someone asks. Here's how it fits each situation.
"What did I do yesterday?" at standup
Open yesterday's lines two minutes before the meeting. Pick the two or three that matter to the team, plus any blocker. That's your update.
The official Scrum Guide describes the Daily Scrum as a 15-minute event for checking progress toward the sprint goal, and leaves the exact format to the team rather than prescribing the classic three questions. So don't read out every line. Your log is the raw material, not the script. A good standup answer sounds like: "Finished the budget draft, sorted the Henderson invoice, and I'm blocked on the login bug. I've tried clearing the cache, so I need someone who knows the auth setup."
How to fill in a timesheet from memory (and stop needing to)
If you're filling in a timesheet from memory right now, with no log, work backward from evidence:
- Check your calendar for meetings and calls.
- Scan your sent email and chat messages for each day. They show what you were working on and when.
- Look at file "last modified" dates in your recent documents.
- Check your phone's call log.
- Fill in the big blocks first, then mark what's left as best estimates.
This works, but it's slow and it misses unplanned work. Once you keep a log, the timesheet becomes copying. Add up the rough times next to each line, round to whatever unit your employer or client uses, and you're done. A couple of minutes each day is usually easier than a long reconstruction on Friday.
Invoices and client questions
For freelancers and contractors, a dated line like "10:15 Call with Henderson re invoice dispute, 25 min" is useful evidence. When a client asks what the hours were for, you can answer with specifics instead of "general project work." Keep the log as plain and factual as you'd want it to sound if you shared it.
The 3-minute weekly review
Once a week, pick a fixed moment. Friday afternoon or Monday morning works for most people. Read through the week's lines and do three things:
- Fill gaps. If Wednesday afternoon is blank, check your calendar or sent mail and add a line or two while you still can.
- Pull out open loops. Any promise, blocker or "they'll get back to me" that is still open goes on your to-do list or into next week's plan.
- Copy the wins. Anything you'd want to mention at a review, like a solved problem, praise from a client or a project shipped, gets copied to a separate list.
That third step is where this daily log connects to a longer-term record. The work log is about what happened today and this week. A running wins list is the shorter, curated version you'll want at performance review time. The weekly review is the bridge between them, and three minutes is enough.
The weekly review also makes status updates easy. Your manager's "what did you get done this week?" email is just your three or four best lines, rewritten as sentences.
Making the habit stick
A work log is easy to start and easy to drop. A few tweaks help:
- Tie it to something you already do. Write a line when you close a browser tab, hang up a call or come back from a break.
- Lower the bar. "Henderson call, PO coming" is a perfectly good entry. Grammar is optional.
- Accept gaps. A log with holes is far more useful than no log. Don't give up because you missed Tuesday.
- Talk instead of typing when you're walking between rooms or driving. A spoken line is still a line.
- Notice the first payoff. The first time your log saves you at standup or on a timesheet, you'll see why it's worth the seconds.
If interruptions are the main problem, the same notes also help you get back into a task. There's more in how to pick up where you left off after an interruption.
A few honest lines a day, written at the moment they happen, are enough. Do that, and "what did I even do yesterday?" becomes a question you can answer in ten seconds.
Frequently asked questions
What should I say at standup if I can't remember what I did yesterday?
Be brief and honest. Check your calendar, sent messages and recent files for clues, then name the one or two things you're sure about and any blocker. It's fine to say you'll confirm a detail after the meeting. Next time, a one-line note after each task switch means you'll have the answer ready before standup starts.
What should a daily work log include?
Each entry needs what you did, who or which project it was for, and where it stands now. Add a rough time if you bill hourly or fill in timesheets. Include meetings, unplanned interruptions, help you gave colleagues and things you tried that failed. Keep entries to one line so writing them takes seconds, not minutes.
Is it better to fill in timesheets daily or weekly?
Daily is usually more accurate, because details of small tasks fade and end-of-week recall tends to miss unplanned work. If your employer only needs weekly submissions, you can still jot times daily and total them at the end of the week. A couple of minutes a day is usually easier than reconstructing everything on Friday.
Can I keep a work log on my personal phone?
Often yes, but check your employer's or client's policy first. Some workplaces, especially in healthcare, law and finance, restrict what can be stored on personal devices. Keep entries general and leave out confidential details such as patient names, client data or passwords. If in doubt, keep the log in an approved work tool instead.
How is a work log different from a brag document?
A work log records everything you did, day by day, mainly for standups, timesheets and invoices. A brag document or wins list is a short, curated list of accomplishments for performance reviews and promotions. The log is the raw material. A quick weekly review lets you copy the best items from it into your wins list.
Sources
- Replication and Analysis of Ebbinghaus' Forgetting Curve (Murre & Dros, PLOS ONE, 2015)
- The Cost of Interrupted Work: More Speed and Stress (Mark, Gudith & Klocke, CHI 2008)
- Consider it done! Plan making can eliminate the cognitive effects of unfulfilled goals (Masicampo & Baumeister, 2011)
- The 2020 Scrum Guide