How to send performance review proof without sounding desperate
Review season is a bad time to rely on memory.
Use this when
- Your review is coming up in the next few weeks.
- You need to remind your manager what changed because of your work.
- You want proof without writing a self-congratulatory essay.
Review prep note
Hi {{manager_name}},
Ahead of review prep, I pulled together the main outcomes from this cycle.
1. {{workstream}}: {{what_changed}}
Proof: {{metric/link/example}}
2. {{workstream}}: {{what_changed}}
Proof: {{metric/link/example}}
3. {{workstream}}: {{what_changed}}
Proof: {{metric/link/example}}
The main pattern I see: {{judgment/behavior you improved}}.
Happy to discuss what you think should be the focus for the next cycle.If you have no hard metrics
The clearest proof I have is:
1. {{risk reduced}}
2. {{decision unblocked}}
3. {{repeat issue prevented}}
4. {{stakeholder/customer/team helped}}Weak version
I worked on many projects and supported the team.
Better version
I reduced repeat support tickets, unblocked the onboarding launch, and documented the handoff so the same issue does not come back next sprint.
Why this works
- It gives your manager language they can repeat in the review room.
- It connects work to outcomes, not activity.
- It shows judgment, not just effort.
Do not do this
- Do not wait until the review form is due tomorrow.
- Do not list every task. Pick the proof that changed something.
- Do not exaggerate. A small true outcome beats a huge fake one.
Need the full set of work replies?
Get the scripts, review prep templates, proof system, and daily missions for managing up without sounding like a LinkedIn post.
Get the protocol