How to remember what you worked on last week

Rebuild last week from the trails you already left: your calendar, sent email, chat history, recent files and commits, one line per day. After that, write two lines at the end of each day on paper or in a daily log, and do a short Friday review. If you're on a Mac and habits keep slipping, Dayflow records your screen and writes the timeline for you.

It’s Monday morning and someone asks what happened last week. Maybe it’s standup, maybe it’s your manager, maybe it’s a client wondering what the invoice covers. You know you were busy. You were at your desk every day. But when you try to say what you actually did, you get the meeting that ran long, the bug that annoyed you on Thursday, and then a blur of tabs, messages and half-finished drafts.

It stings most when it matters: a performance review, a timesheet, a status report due in an hour. You end up guessing, and the work that took the most effort is often the work you forget, because it left the least to show for it.

This guide covers why last week fades so quickly, how to rebuild it from trails you already have, and a few small habits that mean you never have to rebuild it again. Most of them need nothing more than paper and a calendar. One section near the end covers Dayflow, which is our product.

The short version

• Rebuild last week from evidence, not memory: calendar, sent email, chat messages you sent, recently edited files, commits. One line per day.
• From today on, write two lines at the end of each workday: what moved forward, what’s next.
• Keep a “done” list next to your to-do list, and put unplanned work on it too.
• When you switch tasks, leave yourself a one-line note about where you stopped.
• Block fifteen minutes on Friday afternoon to read the week’s notes and turn them into three themes.
• Tell one person, once a week, what you got done. Saying it out loud fixes it in place.

Why can’t I remember what I did last week?

Nothing is wrong with you. Memory keeps what was unusual and lets the routine go. A week of similar meetings, similar messages and similar small tasks tends to collapse into one gray block, while the one surprising afternoon stays sharp. That is useful for surviving a normal life and unhelpful when someone asks for a list.

A few other things make it worse.

Small switches add up. A typical workday is not five tasks. It’s dozens of small moves between email, documents, chat and the thing you were supposed to be doing. None of those moves feels big enough to remember on its own, so none of them get remembered.

Effort and output don’t match. Two hours spent figuring out why a report was wrong might end in a one-line fix. Your memory files it under “fixed the report,” and the two hours disappear. The same goes for helping a teammate, reading up on something new, or untangling a confusing email thread.

Your calendar only shows the scheduled parts. When you try to rebuild a day, the meetings are easy to find because they’re written down. The work between them, which is often most of the work, has no record unless you made one.

Friday-you fills the gaps with guesses. When memory comes up short, the mind smooths it over with a plausible story. That story usually favors whatever felt important, not what took the time.

If you want to see this on a smaller scale, try reconstructing just yesterday. There’s a longer walk through that in where did my day go.

1. Rebuild the week from trails you already left

You don’t need to remember last week. You need to find it. Almost everything you did on a computer left a timestamp somewhere.

What to do: Open a blank page with five lines, one per weekday. Then go through these, one day at a time:

• Your calendar, for the anchors.
• Your sent email folder, sorted by date.
• Chat messages you sent (most chat apps let you search for messages from yourself).
• Recently edited documents and files, sorted by modified date.
• Commits, tickets you moved, or anything in a shared tracker with your name on it.
• Browser history, if the rest leaves gaps.

Write one plain line per day about what moved forward. Ignore how long each thing took; you’re after the shape of the week.

Illustration: Thursday’s calendar shows only a 2pm one-on-one. The sent folder shows three replies in a procurement thread before lunch. The recent files list shows a pricing draft edited at 4:40pm. Thursday becomes: “Procurement back-and-forth on the vendor contract, second draft of pricing page.”

After a week: This step is a rescue, not a habit. The test is whether you can produce a believable five-line summary of last week in one sitting. If you can, you have something to say on Monday. If some days stay blank, that’s useful too. It tells you which kinds of work leave no trail, which is exactly what the next steps cover.

2. Write two lines at the end of every workday

The cheapest way to remember last week is to write it down while it’s still this week.

What to do: Before you close the laptop, write two lines. The first is what you moved forward today. The second is what comes next. Paper works. A note on your phone works. If you want a ready-made structure, the daily work log template has a simple one. Keep it short on purpose. A log you’ll actually write beats a detailed one you’ll abandon by Wednesday.

Illustration: “Tue: Found why the March numbers didn’t match (duplicate rows in the export). Next: fix the export and tell finance.”

That entry takes under a minute, and it saves the two hours of investigation that would otherwise have vanished into “fixed the report.”

After a week: Count the entries. If you have four or five, the habit is holding. Then read them back on Friday and ask whether they’d be enough to write a status update. If they’re too vague (“worked on stuff”), add one concrete noun per line: the name of the project, the person, the document. If you want to go further, there’s more on structure in what a work journal is and how to keep one.

3. Keep a done list next to your to-do list

A to-do list shows what you planned. A done list shows what actually happened, which is often very different.

What to do: Put a second column, sticky note or text file next to wherever you keep your tasks. Every time you finish something, write it down, including the things that were never on the plan: the urgent favor, the surprise bug, the forty-minute call that was supposed to take ten. Write the unplanned items with a small mark so you can spot them later.

Illustration:

• Sent revised quote to client
• • Helped Sam debug the login issue (unplanned, most of the afternoon)
• Reviewed onboarding draft
• • Covered the support inbox while it was short-staffed (unplanned)

After a week: Compare the done list with the to-do list. Many people find that a big share of their real work was never on the plan. If that’s true for you, it’s worth knowing before your next review, because unplanned work is the first thing people forget to mention. The list is working if it has entries from most days and if, reading it, you think “oh, right, I did do that.”

4. Leave yourself a note when you switch tasks

Part of what makes a week blur is that you leave things in the middle and come back to them cold. A short breadcrumb fixes the coming-back, and the breadcrumbs together form a trail.

What to do: When you step away from a task, whether for a meeting, lunch or a different project, write one line saying where you stopped and what the next move is. Put it where you’ll see it: at the top of the document, in the ticket, on a sticky note on the monitor.

Illustration: At the top of a half-written proposal: “Stopped at budget section. Need Q3 numbers from Priya before finishing. Intro and scope are done.” Coming back the next morning, you know exactly where you are, and on Friday that note is proof the proposal got real work on Tuesday.

After a week: Two signs it’s working. First, picking tasks back up feels faster, with less rereading to figure out where you were. Second, when you rebuild the week, the notes fill gaps that the calendar and sent folder couldn’t. If you keep forgetting to write them, attach the habit to something you already do, like closing a document or joining a call.

5. Do a fifteen-minute review on Friday

Daily notes are raw material. The Friday review turns them into something you can say out loud on Monday.

What to do: Put a recurring fifteen-minute block on your calendar for Friday afternoon. In it, read the week’s notes and done list, then answer three questions:

1. What were the two or three main things this week was about?
2. What slipped or got blocked, and why?
3. What’s the focus for next week?

The weekly status report template follows roughly this shape if you need to send it to someone. If you’d like a rough picture of where your hours tend to go before you start, the where does my week go calculator gives you a quick estimate to compare against.

Illustration: “Themes: vendor contract (nearly signed), March reporting fix, a lot of support coverage. Slipped: onboarding draft, because support ate Wednesday and Thursday. Next week: finish onboarding, hand support back.”

After a week: The real test is Monday. When someone asks what you did, can you answer in two sentences without opening anything? If yes, it’s working. If the review keeps getting skipped, it’s usually because Friday afternoon is a bad slot for you. Try Monday morning instead, before email.

6. Tell one person what you got done

Saying something to another person tends to fix it in memory better than writing it alone, and it adds a small, friendly reason to keep the habit going.

What to do: Pick one person: a friend, a teammate, a partner, someone else trying to keep better track of their own work. Once a week, send them three lines about what you got done. Ask them to do the same. Nobody grades anybody. The point is the sending.

Illustration: A Friday text: “This week: contract almost signed, fixed the March numbers, covered support for two days. Next week: onboarding draft. You?”

After a week: Did you send it? That’s the whole measure for now. After a few weeks, notice whether Monday questions feel easier. Many people find that the act of summarizing for someone else makes the week stick, even on weeks when the daily notes were patchy.

Where seeing your actual day helps

Every step above depends on remembering to do something: write the note, keep the list, sit down on Friday. On calm weeks that works. On the weeks that most need a record, the ones with a launch, a crisis or a sick kid at home, the habit is usually the first thing to go.

An automatic record covers those weeks. Dayflow is a Mac app that records the screen at one frame every 10 seconds and has AI write the day into a readable timeline, so there’s no timer to start and nothing to reconstruct from memory. Full screen recordings and the timeline are stored on your Mac. You choose how screenshots are analyzed: Local AI runs a model on your Mac through Ollama or LM Studio and keeps analysis on-device, while your own cloud provider or Dayflow Pro processes selected screenshots off-device. The details are in local and cloud processing.

For a weekly report, you can export a date range as Markdown from Settings → Export and edit it from there. The export work history workflow shows how.

Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month, and needs macOS 14 or later. This description is based on Dayflow 2.2.0, its settings and its published policy as reviewed on September 6, 2026. Dayflow publishes this article, so weigh that accordingly.

Where Dayflow is the wrong pick

Be clear-eyed about what a screen record can and can’t do.

It can’t rescue a week that already happened. Dayflow builds its timeline from recordings it makes going forward. For last week, step 1 is your tool.

It’s Mac only. If your work happens on Windows, Linux, a tablet or your phone, it won’t see it.

It only sees the screen. Phone calls, whiteboard sessions, thinking on a walk and reading on paper leave nothing for it to record. A written two-line log catches all of those, and it also catches the why behind a decision, which no screen record can.

It’s a record, not a coach or a blocker. It won’t remind you to start tasks or stop you from drifting to a news site. It has no website blocking.

It isn’t a billing tool. Dayflow doesn’t provide invoices, payroll approvals or team reports. If your real need is billable hours and client invoices, one of the dedicated Mac time trackers built for invoicing will serve you better.

AI summaries can be wrong. They can miss or misinterpret work, so read them before you send anything to a manager or client.

Screen recording isn’t right for every job. If your workplace prohibits it, or your screen regularly shows information you shouldn’t keep, a paper log is the safer choice. There’s a fuller discussion in is Dayflow safe.

The bottom line

Forgetting last week isn’t a character flaw. Routine work blurs, and the effort that leaves no trail is the first to go. For a week that’s already gone, rebuild it from your calendar, sent mail, messages and file history, one line per day. For every week after that, write two lines each evening, keep a done list, leave breadcrumbs when you switch, and spend fifteen minutes on Friday turning it into three themes. Tell someone if it helps the habit stick.

If you’re on a Mac and the habits keep slipping when things get busy, an automatic record can fill in behind them. Just keep a short written note too, because the screen only shows what you did, not why you did it.

Frequently asked questions

How do I remember what I did last week at work?

Work from evidence, not memory. Open your calendar, sent email, chat messages you sent, recently edited documents, commits and browser history, and go one day at a time. Write one line per day describing what moved forward. Meetings anchor the day, and the messages and file edits around them usually show what filled the gaps. Most of a week can be rebuilt this way in a single sitting.

What should I write in a daily work log?

Keep it short enough that you will actually do it. Two lines work for most people: what you moved forward today, and what comes next. Add anything unplanned that ate real time, such as a surprise bug or a long call. The goal is a record your Friday self can read in a minute, not a diary. A paper notebook or a simple template both work.

Why do I forget what I worked on so quickly?

Routine work rarely sticks. Many people find that days of similar meetings, messages and small tasks blur together, while surprises and finished milestones stay vivid. Work that took effort but left no visible output, like investigating a problem or unblocking a teammate, is the easiest to lose. That is a normal feature of memory, not a personal failing, and a written or automatic record fixes most of it.

How long should a weekly review take?

Fifteen minutes is plenty if you kept daily notes. Read the week's entries, group them into two or three themes, note what slipped, and pick next week's priorities. Without daily notes, the review turns into reconstruction and takes longer. If the review keeps getting skipped, move it to a fixed calendar slot on Friday afternoon and treat it like a meeting with yourself.

Is a written work log better than an automatic tracker?

For some things, yes. A written log beats Dayflow at capturing why you made a decision, what you were thinking, and work that happened away from the screen, like calls on your phone, whiteboard sessions or reading on paper. Dayflow only sees what was on your Mac's screen. Many people get the best result by keeping a two-line written note alongside any automatic record.

Should I use Dayflow to bill clients for my hours?

Probably not on its own. Dayflow does not provide invoices or payroll approvals, and its AI summaries can miss or misinterpret work, so they need checking before you share them. If billing is the main job, a dedicated time tracker with invoicing built in is the better pick. Dayflow can still help you remember what happened, which you can then copy into a timesheet.

Can Dayflow show me what I did last week if I just installed it?

No. Dayflow builds its timeline from screen recordings it makes going forward, so it has nothing from before you installed it. To rebuild a week that already happened, use the trails you already have: calendar, sent email, chat history, file edit dates and commits. From the day it is running, the next week is covered without you having to remember to do anything.

Does Dayflow send my screen recordings to the cloud?

Full screen recordings and the local timeline are stored on your Mac. With Local AI, a model runs on your Mac through Ollama or LM Studio and screenshot analysis stays on-device. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Under the privacy policy, Dayflow Pro deletes screenshots after processing and may retain Activity Data for sync.

How can I write a weekly status report without remembering everything?

Collect the raw material during the week, then write the report from it. Daily two-line notes or a done list give you most of what you need. Group the items into a few themes, add what is blocked, and list next week's focus. If you use Dayflow on a Mac, you can export a date range as Markdown from Settings and edit it into the report.

Is Dayflow free?

Yes. Dayflow is $0 and MIT licensed, and it runs on macOS 14 or later. There is an optional Pro plan at $20 a month that manages cloud analysis for you. The free app does not include paid API usage, so if you connect your own cloud provider, that provider's charges and privacy terms apply. Local AI runs on your own hardware instead.