A performance review should not be the first time you discover how your manager thinks you are doing. In a well-run performance process, expectations are set in advance, progress is discussed during the year, feedback is specific, and the formal review summarizes evidence that has already been building over time.
Real workplaces are not always that orderly. Goals change, managers forget projects, recent events can dominate memory, and an annual review may be the only structured career conversation you get. Preparing your own record helps you walk into the meeting with something stronger than “I think I had a good year.” It also makes the review more useful for decisions about development, scope, pay and promotion.
Key Takeaways
- Use the criteria as the baseline: review the goals, responsibilities and performance expectations that were supposed to define success.
- Bring evidence, not adjectives: projects, results, customer feedback, process improvements and added responsibilities are stronger than “hardworking” or “team player.”
- Do not rely on memory: keep a running record of accomplishments throughout the year so recent events do not crowd out earlier work.
- Own misses as well as wins: explain what happened, what you changed and what support or skill would improve the result next time.
- Ask for specific feedback: vague comments are difficult to act on, so ask for examples and the behavior your manager wants to see instead.
- Separate performance from career direction: a good rating does not automatically answer whether you are ready for promotion or whether your salary matches the role.
- Turn the review into next-period goals: leave with clearer priorities, measures and development actions.
- Document follow-up: write down important commitments, especially if the conversation includes a future compensation or promotion review.
Review the Goals and Expectations You Were Measured Against
Before writing a self-review, find the documents that defined your job during the period.
Depending on your employer, that might include:
- your job description;
- annual or quarterly goals;
- performance standards;
- project objectives;
- competency frameworks;
- previous review notes;
- development plans; and
- goals added or changed during the year.
The U.S. Office of Personnel Management describes performance management as a cycle that includes planning, monitoring, developing, rating and rewarding. OPM guidance applies directly to federal performance management, but the framework is useful more broadly because it emphasizes a basic principle: performance should be evaluated against expectations and goals that were communicated in advance.
Make a simple list:
| Expectation | What happened | Evidence |
|---|---|---|
| Reduce monthly reporting errors | Error rate fell after new validation step | Before/after quality data |
| Complete system migration | Delivered on schedule | Project plan, launch date, stakeholder sign-off |
| Improve client response time | Target partially met | Average response-time data and unresolved bottleneck |
This prevents the review from becoming a list of whatever accomplishments happen to come to mind first.
Build an Accomplishment File Before You Need It
If your review is next week, reconstruct the year from the evidence you have. For future reviews, keep a simple running file so you do not have to rebuild twelve months of work from memory.
Capture:
- projects completed;
- problems solved;
- revenue generated or protected where relevant;
- cost or time reduced;
- errors or risk reduced;
- customers retained or helped;
- new responsibilities;
- people trained or mentored;
- processes created or improved;
- positive feedback;
- important decisions you influenced; and
- skills or tools you learned and actually used.
Keep records of accomplishments, feedback and coaching throughout the review period, and use specific examples rather than impressions. The habit is useful in any workplace where the employee is expected to discuss results.
Record Enough Context to Make the Result Credible
Improved reporting.
Stronger note:
Rebuilt the weekly exception report in March, added automated duplicate checks and reduced manual review from about four hours per week to roughly 90 minutes across the next eight reporting cycles.
You do not need a precise metric for every contribution. Some work is qualitative. But if you use a number, keep enough context that you can explain where it came from.
Write a Self-Review That Is Specific and Balanced
A self-review should help your manager evaluate the period, not read like a sales brochure.
For each major goal or responsibility, use a simple structure:
Expectation: Improve onboarding for new analysts.
Action: Created a written checklist, sample files and two structured training sessions.
Result: Both new analysts completed the standard weekly process without escalation by their fourth cycle.
Evidence: Training documents, completion dates and manager feedback.
Next step: Add exception-handling examples based on the questions that came up during onboarding.
A self-assessment before the review can support a more constructive conversation about strengths and development.
Include Misses Without Undermining Yourself
Trying to make every result look successful can make a self-review less credible.
If something did not go well, explain:
- what the target was;
- what happened;
- which part you controlled;
- what you learned;
- what you changed; and
- what support or skill would improve the result next time.
“The vendor transition finished two weeks later than planned. I underestimated the time required to validate historical data and did not escalate that risk early enough. For the next migration I am adding a separate data-validation milestone before the final cutover date and will raise timing risk as soon as the test file misses the agreed threshold.”
That is stronger than pretending the delay did not happen or blaming another team for the entire outcome.
Prepare for Feedback You May Not Agree With
Do not assume every review comment will match your self-assessment.
If feedback surprises you, avoid arguing with the label before you understand the evidence behind it.
Ask:
- “Can you give me a specific example?”
- “What behavior would you have preferred in that situation?”
- “How often have you seen this issue?”
- “What impact did it have?”
- “What would stronger performance look like over the next few months?”
Specific feedback is more useful than a vague label. One practical structure is to identify the situation, the behavior and the impact so the employee can understand what happened and what should change.
“You need to communicate better.”
Useful follow-up:
“Can you give me one or two situations where my communication created a problem, and what you would have expected me to do differently?”
You do not need your manager to withdraw every criticism. You need to leave knowing what should change and how improvement will be judged.
Compare the Review With the Work You Actually Do
A performance review is also a chance to identify whether your role has drifted beyond its original scope.
Compare:
- what you were hired to own;
- what you own now;
- which decisions you now make;
- whether you coordinate other people or functions;
- whether the complexity or risk has increased; and
- whether you are regularly performing work associated with the next level.
Current role: Own the reporting calendar, resolve cross-team exceptions, approve final output and present monthly trends to directors.
That difference can support a separate conversation about compensation or level. It is stronger than saying only that you “have taken on more.”
Decide Whether to Discuss a Raise or Promotion
A strong performance review and a compensation decision are related, but they are not the same thing.
A good rating does not automatically mean:
- the employer has budget for a raise;
- your salary is below market;
- your role is ready to be re-leveled; or
- a promotion position exists.
If compensation is part of the employer’s review process, prepare the evidence and market research before the meeting. If it is handled separately, use the review to establish the performance record and schedule the pay discussion at the appropriate time.
If your responsibilities have expanded, prepare a separate case for asking for a raise. If you believe you are already operating at the next level, build a promotion case around next-level responsibilities and results.
Research Market Pay Before Making a Compensation Claim
If you plan to say your pay is below market, bring more than one salary website.
Use relevant occupation, location, industry and job-scope data. Market salary research should combine wage distributions with comparable current postings rather than treating one average as the answer.
Prepare Questions About Career Growth
A review should not focus only on what already happened.
Ask questions that make the next period clearer:
- What are the two or three most important priorities for me next?
- What would distinguish good performance from exceptional performance?
- Where do you see my biggest skill gap?
- What responsibility would stretch me in a useful way?
- What work should I stop doing or delegate?
- What would I need to demonstrate to be considered for the next level?
- Which skills will matter more as this role changes?
For development goals, focus on behaviors that can be observed: clearer communication, stronger judgment, more reliable execution, better collaboration or greater ownership. A goal is more useful when your manager can describe what improved performance would actually look like.
You do not need to turn the review into a discussion of every possible career path. Pick the one or two questions that would change what you do next.
If the review exposes a capability gap that affects your next role, focus on skills with clear market value rather than collecting training for its own sake.
Turn the Review Into Clear Goals for the Next Period
Do not leave with goals such as “be more strategic,” “show more leadership” or “improve communication” unless you can translate them into specific behaviors or results.
Translate broad feedback into observable work.
| Vague goal | More useful version |
|---|---|
| Improve communication | Send a weekly decision-oriented project update covering risks, owners and next steps |
| Show leadership | Own the next cross-functional rollout from plan through retrospective |
| Be more strategic | Present one quarterly analysis that identifies a business problem, options and recommendation |
| Improve stakeholder management | Define owner, deadline and unresolved dependency at the end of each major project meeting |
Performance management works better as an ongoing cycle of setting expectations, monitoring progress and giving feedback rather than treating the annual rating as the entire process.
Ask How Success Will Be Measured
A goal becomes more useful when both sides understand what evidence will matter.
“Improve the monthly close.”
Try:
“Reduce unresolved reconciliation items at the day-five close review, document the three most common causes and propose one process change by the end of Q2.”
Not every job can be reduced to a clean metric. Qualitative criteria can still be specific enough to evaluate consistently.
Document the Important Follow-Up
After the meeting, write down what you understood.
Capture:
- final rating, if applicable;
- major strengths discussed;
- development areas;
- new goals;
- projects or responsibilities you agreed to take on;
- training or support your manager agreed to provide;
- promotion criteria discussed;
- compensation follow-up; and
- the date of the next check-in.
A short follow-up email can prevent two people from remembering the conversation differently.
“Thanks for today’s review. My main priorities for the next quarter are completing the reporting migration, taking ownership of the monthly director presentation and improving escalation timing on cross-team dependencies. We also agreed to review promotion readiness in November after those responsibilities have been demonstrated. Let me know if I missed anything important.”
Document key performance discussions and keep records of accomplishments and feedback so later reviews do not depend on memory alone.
Do Not Wait Until Next Year’s Review
The annual meeting is a poor place to discover a problem that could have been fixed six months earlier.
Between reviews, ask for feedback when:
- you finish an important project;
- you take on a new responsibility;
- a meeting or stakeholder interaction goes badly;
- you are practicing a skill your manager asked you to improve;
- your priorities change; or
- you need to know whether you are on track for promotion.
OPM’s current performance-management playbook promotes frequent communication and real-time feedback rather than relying only on annual assessments.
Frequently Asked Questions (FAQs)
What should I bring to a performance review?
Bring or prepare your goals, a concise self-assessment, specific accomplishments, evidence of expanded responsibilities, important feedback you received, development questions and notes on what you want to discuss next. If compensation is part of the meeting, prepare relevant market-pay evidence separately.
How do I write a good self-performance review?
Organize it around the expectations you were given. For each major goal, explain what you did, the result, the evidence and what you learned or would do next. Include important misses as well as successes so the review is credible and useful.
What should I say if I disagree with my performance review?
Ask for specific examples, explain your evidence calmly and clarify how the rating was determined. Focus first on understanding the difference between your assessment and your manager’s. If your employer has a formal process for contesting ratings or correcting factual errors, follow that process where appropriate.
Should I ask for a raise during my performance review?
Some organizations combine performance and pay discussions, while others make compensation decisions separately. If you plan to ask for more pay, prepare evidence of your results, expanded scope and relevant market value rather than assuming a strong rating automatically produces a raise.
Should I discuss promotion during a performance review?
Yes, if career advancement is relevant, but frame it around the expectations of the next role. Ask what you already demonstrate, what gaps remain and what experience would show readiness. A positive performance rating and promotion readiness are related but not identical.
How should I respond to negative feedback?
Ask for a specific situation, behavior and impact, then clarify what different behavior is expected. If the feedback is valid, agree on a practical change and how progress will be evaluated. If you disagree, explain your evidence without turning the conversation into a personal argument.
What if my manager gives only vague feedback?
Ask for examples and convert the feedback into observable expectations. “Be more proactive” might become “identify project risks before the weekly status meeting and propose a response rather than waiting for escalation.”
How often should I ask for performance feedback?
There is no universal schedule. Ask often enough that you can correct problems and develop skills before the formal review. Important projects, new responsibilities and agreed development goals are natural points for a check-in.
Sources
- U.S. Office of Personnel Management: Performance Management Cycle
- U.S. Office of Personnel Management: Performance Management Roadmap
- U.S. Office of Personnel Management: Monitoring and Developing
- U.S. Office of Personnel Management: Measuring Employee Performance Quick Guide
- National Association of Colleges and Employers: Career Readiness Competencies
- National Association of Colleges and Employers: Employers Say New Grads Are Largely Prepared for Work, With Room to Improve
