How to Prepare for a Performance Review With a New Manager

A new manager may be responsible for rating work they did not see. You may be tempted to send them everything: every project, compliment, deadline, and explanation from the year. That creates more information without necessarily creating understanding. Prepare a short evidence brief that explains your Role, the expectations in effect during the period, your most important contributions, and the context behind work completed before the manager arrived. Then use the conversation to check alignment for the next period, not to test whether they memorized your history.

Clarify who owns the review and what evidence they will use

Ask early how the review will be handled. Will your new manager write the full assessment? Will your previous manager provide input? Are project leads or calibration partners consulted? Which goals and competency framework apply? The answer determines which context you need to supply and where gaps may remain.

Keep the question neutral: “Because part of the review period predates our working relationship, I’d like to understand how earlier work will be assessed and what evidence would be most helpful.” You are asking about the process, not accusing the manager of being unable to judge you.

Create a one-page review context brief

Give the manager a short map before the full self-review. Include the dates covered, your Role and scope during each phase, the goals you were working toward, three to five major contributions, material changes in priority, and the people or records that can verify work completed before they arrived.

• Review period and any manager or Role transitions
• Goals and expectations agreed at the start of the period
• Three to five contributions with your ownership and outcome
• Important constraints, changed priorities, or cancelled work
• Relevant feedback and where supporting evidence lives
• Questions that require the new manager’s judgment

The brief is an orientation document, not a campaign dossier. Link to supporting material instead of pasting every artifact. If the manager needs more detail for one claim, you can provide it without making them sort through the entire year first.

Explain the expectations that existed before the transition

A new manager may reasonably apply the company’s current framework, but they should understand the goals and tradeoffs you were actually asked to manage. Include the original goal, any written change, and the person who made the change. Avoid relying on “my old manager said” when a goal document, project update, or planning note is available.

If expectations were unclear, say so plainly and show how you sought direction. Do not reconstruct a precise agreement that never existed. A sentence such as “The team did not have a documented success measure; I used adoption by the support group as the working signal and raised that assumption in the April review” is more useful than pretending the metric was formal.

Write accomplishments for someone who lacks the backstory

Name the problem, your specific contribution, the people involved, and the result. Spell out acronyms and explain why the work mattered. What felt obvious to the previous manager may be invisible to someone who joined after the project ended.

For example: “When two teams used different definitions for an activated account, I led the working session that produced one shared definition and updated the reporting brief. Product and Customer Success used it for the next launch review.” This gives the new manager scope, action, and consequence without requiring months of history.

Use prior-manager and peer input carefully

If the process allows input from your previous manager or project leads, ask them to comment on specific work. Provide the project, dates, your understanding of your contribution, and the review deadline. A narrow request produces more useful evidence and is easier to verify.

Do not assemble testimonials as a substitute for evidence. Feedback supports a claim when it describes what changed or how you worked. Your self-review should still explain the accomplishment in your own words and give collaborators appropriate credit.

Surface changes in Role, scope, and opportunity

Manager transitions often change priorities and access to work. Separate performance from opportunity. If a project moved away from you after the transition, describe what you completed before the handoff and what remained. If your scope expanded, identify when and what you took on.

Ask the new manager to confirm the Role they are evaluating now. A review can become confusing when the first half of the period reflects one job and the second half reflects another. A simple timeline helps both of you distinguish results from transition effects.

Prepare questions for the review conversation

Use the meeting to understand judgment, not just the final rating. Ask which evidence was most useful, what remained unclear, how your work maps to current expectations, and which two outcomes should matter most next. If you disagree with an assessment, point to a specific expectation or example and ask how the manager interpreted it.

End with a lightweight visibility agreement. You might send a monthly outcome summary, use one-on-ones to discuss one completed contribution, or keep a shared goals page current. Choose the smallest practice that gives the manager enough context without turning your job into continuous self-reporting.

Your new manager does not need to witness every past event to hold a fair review, but they do need credible context. Give them a concise map of the period, support your strongest claims, name the people and sources that can verify work they did not observe, and ask how they will evaluate it. End by agreeing on current expectations and a simple evidence habit for the next cycle. The review can then serve as both a fair account of the past and a clearer contract for the future.