Consider an analyst drafting a self-review after improving a recurring report. “Supported reporting improvements” fits on the page, but it leaves out the decision to revise the definitions, the teams who adopted them, and the errors the change helped catch. Before submitting your review, check whether your performance review phrases give someone enough detail to understand your contribution. A phrase that sounds polished but hides the work will not help much when your manager discusses your case.
If your draft lacks supporting facts, this checklist of what to document before your performance review covers the ownership, decisions, outcomes, and proof to capture.
Use the items below to inspect your own draft. The sample wording is a starting point, not a claim to copy. Fill each blank with work you can explain and evidence you can find.
Performance review phrases for ownership and decisions
Promotion discussions need a clearer account of your role than a shared team result alone. Check these lines against what you actually did, especially when the work involved several contributors.
- Name your responsibility. Try “I owned [specific part of the work] from [starting point] through [decision or delivery].” Use “owned” only when you had that responsibility; otherwise, name the part you contributed.
- Show a judgment call. Try “I chose [approach] because [constraint or evidence], then [action].” The decision gives your manager something concrete to discuss beyond effort.
- Credit collaboration precisely. Try “I worked with [team] to [shared result], contributing [your distinct action].” This keeps the team’s work visible without losing yours.
- Explain an obstacle you handled. Try “When [problem] blocked progress, I [response], which allowed [next step].” Name the obstacle only if it affected the work.
Phrases that connect work to impact and scope
“Worked hard” says little about the change your work produced. Results can be measured, observed, or still developing, but the wording should make that distinction clear. Scope matters too: a change adopted across several teams asks something different of you than a one-off fix for your own work.
- State a verified change. Try “After [action], [measure or observable process] changed from [baseline] to [result].” Check the underlying source before using a number.
- Describe a result without inventing a metric. Try “The revised definitions gave [group] a consistent way to identify [issue].” Be ready to point to an example of that change in use.
- Show who used the work. Try “[Team or audience] adopted [deliverable] for [purpose].” Adoption is more informative than saying the work was “well received.”
- Mark an unfinished outcome honestly. Try “I completed [contribution]; [result] is still being evaluated against [criterion].” Do not write a projected benefit as though it has already happened.
Checks before a phrase goes into your review
Read each draft sentence as though your manager had to repeat it without you in the room. If it depends on context they do not have, add the missing detail. If it implies a result you cannot substantiate, narrow the claim.
- Find support for the claim. Identify an approved source, such as a report, decision record, or completed work item, that lets you verify the result.
- Check that the scale is accurate. Distinguish a local improvement from a practice adopted more widely. Both can matter, but they make different cases.
- Remove praise that substitutes for evidence. Replace “I was a key contributor” with the action and outcome that would let someone reach that conclusion.
- Protect sensitive details. Summarize what you accomplished without transferring private customer information, trade secrets, or restricted work files into a personal record.
Turn checked phrases into a stronger draft
Choose one vague sentence from your self-review and work through the items that apply. You might change “supported reporting improvements” to “I reconciled conflicting metric definitions with the reporting team and documented the agreed rules; the revised report now uses those rules.” Add a verified outcome if you have one. If you do not, the decision and adoption still give your manager a more accurate account to assess.
The easiest time to collect that detail is when the work happens. Keep the evidence behind your review language in ImpactLogr, then draft each claim from what you can substantiate rather than what you can remember.