How to Write a Self-Assessment When You Don't Remember What You Did

Start From the Record, Not Your Memory

Most self-assessment advice assumes you can list your accomplishments from memory. In practice you remember the last month or two and whatever went wrong, which means writing from memory underreports most of your year and skews it negative. The blank page is not a writing problem yet; it is a records problem.

The fix is mechanical. Your work left traces in systems that do not forget: your calendar, your sent mail, your ticket queue, your file history. Spend the first couple of hours pulling those traces into one rough list. Once the inventory exists, you are no longer trying to remember what you did; you are choosing which documented items deserve the space.

The Template

Copy this structure into your review form or a working document. Every section is explained below.

SELF-ASSESSMENT - [Name], [Review period] ACCOMPLISHMENTS (5-6 entries, biggest first) 1. [What you did, stated as a direct claim] Evidence: [dates, ticket numbers, links, before/after numbers] Impact: [who this helped and what changed for them] 2. [Next accomplishment, same shape] GROWTH [What you can do now that you could not do at the start of the period, and one place you used it.] CHALLENGES HANDLED [One or two hard situations: what made them hard, what you did, how they resolved. A setback counts if you can say what you changed because of it.] AREAS TO IMPROVE [One real, bounded weakness: what it has cost, and what you are already doing differently. Not a strength in disguise.] NEXT PERIOD [Two or three goals tied to team priorities, each with a concrete first step.]

Build the Inventory Before You Write a Word

Open a blank document and sweep these four sources in order. Collect everything; do not evaluate yet.

• Calendar. Page back through the whole period, week by week. Recurring meetings show which projects you carried; one-off meetings mark launches, incidents, and decisions. Note anything you prepared for, ran, or presented at.
• Sent mail. Sent, not inbox: it is the record of what you produced rather than what arrived. Skim it month by month. Long messages are usually decisions or explanations you authored, and attachments are artifacts you made.
• Closed tickets. In whatever tracker you use, filter to items you resolved during the period. Note the total count, then pull out the five hardest or most visible.
• Files you touched. Sort your drives, repos, and shared folders by last modified. Decks, runbooks, spreadsheets, and documents with your name in the edit history are evidence of work you have probably forgotten.

Expect 30 to 80 raw lines. That list is the inventory, and nearly every claim in the finished document should point back to something on it.

Select by Impact, Not Chronology

The most common structural mistake is a tour of the year in date order. Date order buries your biggest win somewhere in the middle and gives your smallest the same billing. Pick the five or six inventory items where the outcome mattered most, and lead with the biggest.

The test for each candidate: can you name who was affected and what changed for them? “Migrated the team off the legacy VPN” passes. “Attended the weekly platform sync” does not. Routine work can make the cut, because volume and reliability are impact, but state it as an outcome with numbers rather than a duty you held.

Two Filled Examples

Here is the accomplishment shape filled in for two different jobs. Notice that no adjectives are doing the work; the evidence carries each claim.

IT Administrator

1. Led the migration from on-prem Exchange to Microsoft 365 for 340 mailboxes, completed in one weekend cutover with no data loss. Evidence: project plan (March-June), cutover runbook, and the following week's ticket volume: 11 tickets, all minor. Impact: retired two aging servers, cut annual maintenance spend, and removed our last single point of failure for email.

Project Coordinator

1. Rebuilt the design team's intake process after requests had been arriving through five separate channels. Evidence: intake form launched April 12; tracker shows median response time down from six days to two since launch; process doc adopted by the marketing team in Q3. Impact: designers stopped triaging requests by hand, and requesters now get an answer within two days.

Write It Strong and True

The doctrine is the same as for a brag document: the strongest phrasing the facts support, and not one word stronger.

• Claim your role accurately. If you led it, write “led.” If you contributed, say exactly what you contributed. Inflating “helped with” into “led” is dishonest, but deflating “led” into “helped with” is the more common failure, and it is just as inaccurate.
• Never invent outcomes. No estimated percentages you cannot back. If you do not have the number, describe the change in words you could defend in the review meeting.
• Attach evidence wherever you have it. A date, a ticket number, a link, a named person who can confirm it. Claims with receipts get read differently, so lead with the ones you can back.

Handle the Weaknesses Section Honestly

“I care too much” and “I am a perfectionist” read as evasions, and your manager has seen both many times. A useful entry has three parts: a real limitation bounded to a specific behavior, what it actually cost, and what you have already changed.

For example: “My status updates on the storage project were too infrequent, and the slipped date in October surprised my manager. Since then I send a short written update every Friday, and I flagged the December risk three weeks early.” That is honest, it is scoped to one behavior rather than your character, and it ends on a documented change. Handled this way, the section demonstrates self-awareness, which is the thing it exists to measure.

Make Next Year an Editing Job

Everything above is recovery work. The cheap version is prevention: a short running record kept as the work happens. A few lines at the end of each week covering what shipped, what broke, and what you decided will turn next year’s inventory step from a couple of hours of archaeology into a few minutes of reading.

A text file works fine. If you want less friction, Journaled turns a free-text description of your day into a structured entry with a written summary you can edit before saving, and everything stays searchable and exportable. Its reports cover up to 90 days, which is roughly a quarter: pull a record every three months, keep the four files, and write the annual self-assessment by editing material you already trust.

Common Questions

How Long Should a Self-Assessment Be?

One to two pages. Five or six accomplishments with evidence beat fifteen bullets without it. If your form has character limits, write the full version first and cut; the long version gets reused in the review meeting and in any promotion case.

What If I Can’t Find Evidence for Something I Did?

Look one layer out: the meeting where it was discussed, the document that changed because of it, the colleague who can confirm it in one line. If there is genuinely no trace, include the claim anyway: evidence makes an entry stronger, but a true claim without a paper trail still belongs in the document. Just lead with your best-documented work.

Should I Mention Work That Failed?

Yes, under challenges, when you can show what you did and what you changed afterward. A cancelled project handled cleanly says more about you than a routine success. Leave out anything you cannot yet discuss without assigning blame.

How Do I Write About Routine Work With No Big Wins?

As an outcome with numbers. “Kept the helpdesk running” becomes “closed 214 tickets with no missed SLA and cut repeat tickets by writing the five most common fixes into a runbook.” Routine work almost always contains one improvement you made to it, and that improvement is the accomplishment.

Isn’t Writing This Way Just Bragging?

Bragging is claiming more than you did. This is claiming exactly what you did, in plain language, with receipts. The self-assessment is a primary input to your rating, and understating your work leaves the official record wrong.