How to remember what you did all year before your performance review

Start with the records you already have: your calendar, sent email, chat history, tickets, code history and shared docs' version history. Those can rebuild much of the year. To make next year easier, keep a five-minute weekly log on paper or in a template. If you'd rather not depend on remembering to write things down, Dayflow on a Mac records your screen and writes a daily timeline automatically.

The email arrives: self-assessments are due in two weeks. You open the form and see a box that says “Describe your key accomplishments this year.” Your mind offers last Tuesday, one bug from August, and a vague sense that you were busy the whole time.

You know you worked hard. You stayed late for that launch. You answered endless questions in chat and sat in a lot of meetings that seemed important. But when you try to list what actually happened between January and June, it’s mostly fog. The few things you can recall feel too small to write down.

This guide covers why a year of work disappears so quickly, how to rebuild it from records you already have, how to turn that pile into something a manager can read, and how to make next year’s review take an evening instead of a panic. Dayflow, the Mac app that publishes this blog, is our product. It comes up once near the end, along with the cases where it’s the wrong choice.

The short version

• Don’t try to remember the year. Rebuild it from your calendar, one month at a time.
• Search what you sent (email, chat, comments, tickets). It’s a cleaner record of your work than what you received.
• Ask two colleagues what they remember you doing. They’ll name things you forgot.
• Write outcomes, not activities: what the situation was, what you did, and what changed.
• Start a five-minute Friday note this week so next year’s review is mostly done before it starts.
• Keep a folder for thank-you messages. They’re evidence, and they’re easy to lose.

Why can’t I remember what I did all year?

You’re not bad at your job, and your memory isn’t broken. Memory isn’t built to keep a log. It keeps stories, and most work weeks don’t feel like stories while you’re living them.

A few things make work especially easy to forget:

Recent months crowd out early ones. The last six weeks are vivid, so they feel like the whole year. Spring feels as if it barely happened, even though it holds half your work.

Finished work stops feeling like yours. Once a project ships, it turns into “how things are.” The new onboarding flow is just the onboarding flow now. You stop seeing it as something you built.

A lot of real work leaves no trace. Reviewing someone’s draft, unblocking a teammate, interviewing candidates, sitting in on a call to calm a nervous client. None of it shows up as a deliverable with your name on it.

Prevented problems are invisible. If you caught a mistake before it went out, the result is that nothing happened. That’s hard to recall and harder to describe.

You remember feelings, not outputs. You remember that March was stressful. You don’t remember the three things you shipped in March.

Put that together and the blank self-review box makes sense. The work happened. Your head just didn’t store it in a form you can list. The fix is to stop relying on memory and go to the records.

How do I rebuild a year I can’t remember?

These first four steps are for right now, with the deadline coming. None of them need new software. You’ll use your calendar, your own message history, a sheet of paper and a couple of conversations.

1. Walk your calendar backward, one month at a time

Open your calendar to the current month and work backward. For each month, look at recurring meetings that started or stopped, project kickoffs, launch dates, workshops, customer calls, interviews and offsites. Each one is a clue about what you were working on. Write one line per piece of work on a sheet of paper, grouped by month. Don’t judge yet. If it took real time, it goes on the list.

Going backward helps because recent months jog your memory about the ones before them. “That review meeting was about the pricing page, which means the pricing work started in…” and so on.

Illustration: Someone scanning May notices a weekly “Vendor migration sync” that ran for six weeks and then stopped. They’d forgotten it entirely. It turns out they led the migration, and it finished without problems. That’s a review item.

How to tell it’s working: By the end of a week, doing a month or two each evening, you should have a few lines for every month. If whole months are still empty, that’s normal for heads-down periods. Step 2 fills those gaps.

2. Search everything you sent, not what you received

Your inbox is mostly other people’s priorities. Your sent folder is your work. Do the same with team chat (search for messages from you), comments on shared documents, tickets you opened or closed, code you committed, and the version history of documents you edited. Go month by month again and add lines to your list.

Look in particular for:

• Messages where you explained something. That’s often expertise other people relied on.
• Threads where you said “done,” “shipped,” “fixed” or “sent.”
• Long documents you wrote, even if you don’t think of them as projects.

Illustration: Someone searches their sent email for the word “attached” in February and finds a 12-page proposal they wrote for a new support process. The process is now standard on the team. They hadn’t thought of it as their work in months.

How to tell it’s working: After a week, the gaps from step 1 should be smaller, and you should find at least a few things you’re surprised you forgot. If you’re not finding anything new, try different search words: “draft,” “proposal,” “review,” “fixed,” “help.”

3. Ask two people what they remember you doing

Pick two or three colleagues who saw your work from different angles: a peer, someone you helped, maybe someone on another team. Send a short, low-pressure note: “Writing my self-review and my memory of the year is patchy. Is there anything I worked on or helped with that stuck out to you?”

People remember your work by what it did for them, which is often exactly what you forgot. They also tend to describe it in terms of impact, and impact is what reviews are looking for.

Illustration: A designer asks a product manager what stood out. The PM mentions the afternoon the designer spent walking a new engineer through the design system, which saved that engineer weeks of guessing. The designer had filed that as “just being helpful.”

How to tell it’s working: Within a week you should have at least one item you’d never have written down yourself. If people reply with “you did great!” and nothing specific, ask a narrower question: “Was there a project where I made something easier for you?“

4. Turn the pile into outcomes on one sheet of paper

Now you have a long, messy list. A review needs a short, clear one. Take a fresh sheet and draw three columns: Situation, What I did, What changed. Pick the items from your list that matter most (often three to six) and fill in a row for each.

“What changed” is the column people skip, and it’s the one that counts. It doesn’t need a number. “The team stopped asking me the same setup question every week” is a real outcome. So is “the launch went out on the date we promised.”

Illustration:

Situation	What I did	What changed
New hires took weeks to get set up	Wrote a setup guide and walked two people through it	Later hires got set up on their own in their first days
Vendor contract was ending in June	Led the migration to the new vendor over six weeks	Switched over with no customer-facing downtime

Group what’s left into a short “also” list: interviews, reviews, mentoring, the small fixes. Those show range without crowding the main items.

How to tell it’s working: Read each row out loud as if you were your manager. If you can’t answer “so what?” from the third column, the row needs a sharper outcome or should move to the “also” list. A good sign is that you can explain each row in two sentences without notes.

How do I make next year’s review easier?

The rebuild works, but it’s a lot of effort for something that could take an evening. These two habits mean you won’t have to do it again.

5. Start a five-minute Friday note

Pick a fixed time each week, such as Friday after lunch. Set a kitchen timer for five minutes and answer three questions:

• What did I finish or move forward?
• Who did I help, and with what?
• What changed because of something I did?

Bullet points are fine. Paper is fine. If you want structure, the weekly status report template works as a personal log even if nobody else ever reads it. If you prefer to jot a line at the end of each day instead, the daily work log template suits that rhythm. Our guide to keeping a work journal goes deeper if you want to build the habit out.

Illustration: A Friday note might read: “Fixed the export bug that support flagged. Paired with Sam on the API docs. Customer from the Tuesday call renewed; they mentioned the onboarding call specifically.”

How to tell it’s working: After a week you’ll have one note. That’s the point: it’s small. The real test comes after a month. Read back over four notes and check that you can see the shape of the month without opening your calendar. If you’ve skipped weeks, move the timer to a time that’s harder to miss, such as right before your last meeting on Friday.

6. Keep a folder for thanks and small wins

Make one email folder, label or note called “Wins.” Whenever someone thanks you, praises your work to your manager, or says something saved them time, move it there. Do the same for screenshots of a launch, a message that a customer renewed, or a kind comment in a document.

This takes about two seconds per item, and it collects exactly the evidence that’s hardest to rebuild later: other people describing your impact in their own words.

Illustration: In October, someone opens their “Wins” folder and finds nine messages. Two are from other teams. One is from a director they’d forgotten they ever worked with. Each one jogs a memory and suggests a review item.

How to tell it’s working: After a week, you may have one or two items, or none. Either is fine. The habit is moving things there without thinking about it. If the folder stays empty for a month, check whether you’re skipping chat messages. A lot of thanks lives there.

If the bigger question is about your days, not just your year, our guide to where your day goes covers the shorter version of this same fog.

Where seeing your actual day helps

The Friday note works when you remember to write it. The weeks you’ll most want back, the crunch weeks, are usually the ones where nobody writes anything down. An automatic record helps there because you have nothing to start and nothing to reconstruct from memory.

Dayflow is a free, MIT-licensed Mac app for macOS 14 or later. It records your screen at one frame every 10 seconds and has AI write the day into a readable timeline. Full recordings and the timeline are stored on your Mac. You choose how analysis runs: local AI keeps screenshot analysis on-device, while your own cloud provider or the optional Pro plan ($20 a month) processes selected screenshots off-device. The details are in local and cloud processing.

At review time, you can export a date range as Markdown from Settings → Export and read it next to your calendar. The export workflow shows how. It answers “what was I doing in April?” from what was on screen, not from what you happen to recall. AI summaries can miss or misread work, so treat them as notes to check, not text to paste. For other approaches, see our roundup of Mac time trackers and our guide to remembering what you worked on.

Dayflow publishes this article. The product details above come from Dayflow’s own documentation for version 2.2.0, reviewed on 2026-09-06.

Where Dayflow is the wrong pick

Be honest with yourself about what you need. In a lot of cases, something simpler wins.

• You’re not on a Mac, or your Mac is older than macOS 14. Dayflow won’t run. A paper notebook or the weekly template is the better tool, and it works anywhere.
• Much of your work happens off-screen. Dayflow sees only the screen. Meetings in a room, phone calls, site visits, whiteboard sessions and coffee chats with someone you’re mentoring won’t appear. If that’s most of your job, your calendar plus a written Friday note will capture more.
• Your employer doesn’t allow recording software on work machines. Check the policy before installing anything. If the answer is no, the notebook and the “Wins” folder are the right choice.
• You need team reports, invoices or payroll approvals. Dayflow doesn’t provide any of these. Use whatever system your company already runs for them.
• You want help focusing, not a record. Dayflow has no website blocking and doesn’t coach you. It shows what happened. It doesn’t change what happens.
• You need the review written. Dayflow can’t decide which work mattered or why. Steps 3 and 4 above, a conversation and a sheet of paper, do that job better than any timeline.
• Your work already lives in a well-kept ticket tracker. If every task you do is a ticket with a clear history, that history may be all you need for review season.

The bottom line

Forgetting a year of work is normal. Memory keeps stories, and most work weeks don’t feel like stories. Don’t try to remember harder. Go to the records: walk your calendar backward, search what you sent, and ask two people what stood out. Then boil the pile down to a few outcomes with a clear “what changed” for each.

For next year, a five-minute Friday note and a folder of thank-you messages will do most of the work. If you’re on a Mac and you’d rather not depend on remembering to write things down, an automatic record like Dayflow can fill in the weeks you didn’t capture. Either way, the goal is the same: walk into the review knowing what you did, with the details to show it.

Frequently asked questions

How do I remember what I did all year for my performance review?

Don't try to recall it in one sitting. Go through your calendar one month at a time, then search your sent email, chat messages, tickets and document history for each month. Write one line per piece of work. Then ask a colleague or two what they remember you doing. Records bring back far more than memory does on its own.

What should I write in a self-review if I can't remember my accomplishments?

Write a short list of outcomes, not a long list of activities. For each item, note the situation, what you did, and what changed afterward. Shipped projects belong on it, and so do problems you prevented, people you unblocked, and processes you made easier. Three to five strong items with concrete details usually read better than twenty vague ones.

How do I describe impact when I don't have numbers?

Describe what was different after your work. Fewer repeat questions from a team, a handoff that used to stall and now doesn't, a launch that went out on the date it was promised, a new hire who got productive faster. Name who noticed. Plain before-and-after descriptions are honest and specific, and specific is what makes a review easy for a manager to support.

What if I can't find any evidence of some of my work?

Some work leaves no trail: hallway help, calls, thinking through a problem with someone. Ask the people involved what they remember, and write the item down with whatever detail you can confirm. Leave out anything you can't stand behind. One accurate example of invisible work is more convincing than a long list you'd struggle to explain in the review conversation.

How do I keep track of my accomplishments for next year's review?

Pick a fixed time each week, such as Friday afternoon, and spend five minutes writing what you finished, what you helped with, and anything you were thanked for. A paper notebook or a weekly status template works fine. Add a folder or label for thank-you messages. At review time you'll be editing notes you already have instead of trying to recall twelve months at once.

What is a brag document?

A brag document is a running list of your work and its results that you keep for yourself. It isn't a boast, it's a memory aid. Each entry gets a date, what you did and what changed. It makes self-reviews, promotion cases and job applications much easier, because the raw material is already collected while the details are still fresh.

Can Dayflow write my performance review for me?

No. Dayflow records your screen on a Mac and has AI write each day into a timeline. You can export a date range as Markdown and use it to remember what you were doing. The AI summaries can miss or misinterpret work, and the timeline can't judge which work mattered. You still pick the outcomes, check the details and write the review.

Is there something better than Dayflow if I'm on Windows?

Yes. Dayflow runs only on Macs with macOS 14 or later, so it isn't an option on Windows. A paper notebook or a weekly status template is the better choice there. It works on any computer, costs nothing, and captures off-screen work like meetings and calls, which no screen recorder sees. Five minutes every Friday covers most of what a review needs.

Is it OK to run a screen recorder on my work laptop?

Check your employer's policy on recording software first. Some workplaces don't allow it. With Dayflow, recordings and the timeline are stored on your Mac, and the local AI option keeps screenshot analysis on-device. If you use your own cloud provider or Dayflow Pro, selected screenshots are processed off-device under that service's terms. If the policy says no, keep a written log instead.