content

Performance Review Preparation

Prepare for a performance-review conversation with prompts for agreed outcomes, observable evidence, relevant context, and useful questions. Use the page to organize discussion notes; complete the review transaction in your organization’s performance app.

Request pricing See it in MangoApps

Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Professional services · Technology and software · Healthcare administration · Education

9:41

Sites

Overview

Performance Review Preparation is a single-page reference for employees and reviewers getting ready for a performance-review conversation. It begins with a fictional example from Rowan, a project coordinator at Northstar Services, and makes the page’s scope clear: use the prompts to prepare notes, then use the organization’s performance app for the formal review transaction. The page does not define career levels, submit a review, or replace the employer’s recorded review steps.

The prompts move from agreed outcomes to evidence, context, and questions. Readers first recall the goals, deliverables, or responsibilities discussed for the period, noting changes in priority, scope, or timing. A sample evidence table pairs contributions with observable examples and their scope, and states what each example does not establish. The context prompt helps readers describe dependencies or changed conditions without treating them as proof or assigning blame. A short FAQ addresses limited evidence, missed outcomes, and differing recollections; closing questions help prepare for a forward-looking discussion.

Use this page before a review conversation when either party needs a shared structure for organizing examples and questions. It can also help managers coach preparation without supplying a verdict. Do not use it as a rating rubric, career-level guide, policy statement, or substitute for the performance app or an authoritative review-process page. If your organization has defined terminology, deadlines, or required steps, follow those sources and ask the manager responsible for the review or the People Development owner when something is unclear.

Standards & compliance context

Treat this page as preparation guidance, not as a rating rubric, employment policy, or substitute for the organization’s applicable review procedures.
Follow the organization’s performance app and authoritative internal guidance for required review steps, deadlines, records, and terminology.
Limit examples and notes to information appropriate for the review, and follow organizational privacy and records-handling requirements for employee information.
Keep headings descriptive and content readable with assistive technology; review page accessibility against WCAG 2.1 AA when publishing or substantially revising it.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Performance Review Preparation

This introduction explains who the reference serves, how to use the fictional example, and where the formal review transaction takes place.

A practical reference for employees and reviewers preparing for a balanced review conversation. Fictional example: Rowan, a project coordinator at the fictional Northstar Services, is preparing for a review. Use the same prompts for your role and work setting: start with agreed outcomes, choose specific evidence, consider relevant context, and bring questions for discussion. This page supports preparation for the review transaction in your organization's performance app. It does not define career levels or submit or update a review. Prepare notes here, then use the performance app for the review transaction.

Recall outcomes

Start from the goals and responsibilities discussed for the period, then record changes without erasing the original plan.

Start with what was agreed, then note what changed. Look back at the goals, deliverables, or responsibilities discussed for the period. For each one, note the intended outcome and any change in priority, scope, or timing. Separate the original aim from work that became important later. Rowan's example: Rowan's original goal was to coordinate an onboarding handoff for a planned project launch. When the project schedule shifted, the handoff was reorganized around the revised launch sequence. Rowan records both the original goal and the revised work, rather than treating the change as if the original plan never existed. If an outcome was not completed, record what remained unfinished and what changed during the period. The conversation can then explore the reasons and next steps without assuming a conclusion.

Select evidence

This table helps readers pair a contribution with checkable evidence, its scope, and the limits of what it establishes.

Use examples that can be described and checked; state their scope and limits. Outcome or contribution Observable evidence Period or scope What it does not establish Coordinate an onboarding handoff A handoff document was completed and shared with the project group. For the revised launch sequence during the review period. By itself, this does not show that every team's onboarding improved. Respond to a changed project schedule The handoff sequence was reorganized after the launch schedule changed. The work affected by that schedule change. This does not establish the full effect of the change or assign responsibility for it.

Consider context

Use this prompt to describe conditions that shaped the work while keeping context distinct from proof or blame.

Explain conditions that shaped the work without using them as proof or blame. Consider changes in priorities, dependencies, workload, and opportunities to contribute. Include only context that helps explain the work. Distinguish what you observed from what you infer, and leave room for the other person to add information. Rowan's example: A supporting input arrived after the date Rowan had planned around. Rowan can say, “The handoff sequence changed after the supporting input arrived later than expected. I reorganized the remaining steps around the revised schedule. I’d like to discuss what we could coordinate differently next time.” This identifies a relevant dependency without treating it as proof of performance or assigning blame.

Prepare for common questions

These answers offer a way to discuss limited evidence, missed outcomes, and differing recollections without jumping to a verdict.

Use specific examples and keep the conversation open where evidence or perspectives differ. What if I have limited evidence? Use the clearest examples you do have, describe their period and scope, and name what you cannot conclude from them. Ask the other person what additional context or evidence would help. How should I discuss an outcome I missed? State the intended outcome, what was completed or remained unfinished, and any relevant changes or dependencies. Ask what can be learned and what should be prioritized next, rather than presenting an explanation as a verdict. What if the employee and reviewer remember events differently? Describe the specific example and the source of each perspective. Ask what information may be missing and agree which facts need clarification. A difference in perspective is a topic to discuss, not evidence by itself that either account is correct.

Prepare questions

Bring forward-looking questions that clarify what to build on, change, or prioritize next.

Bring questions that turn reflection into a clear discussion. Which contribution or outcome should I continue building on, and why? What is one approach I should change next period? What evidence or context is missing from this discussion? Which priorities should guide the next period, and how will we recognize progress? Use the organization's performance app for the review transaction and its recorded review steps. For questions about the applicable review process or terminology, ask the People Development owner or the manager responsible for the review.

How to use this template

Copy the page into the appropriate employee or manager site and replace the fictional Northstar Services scenario with clearly labeled sample content or organization-approved wording.
Check the performance app and authoritative internal review guidance for the applicable review period, terminology, deadlines, and required transaction steps.
Before the conversation, list the agreed outcomes and responsibilities for the period, then note changes in priority, scope, or timing.
For each contribution, record a specific observable example, its period or scope, and what it does not establish; add relevant context without presenting inference as fact.
Bring the prepared notes and questions to the review conversation, invite the other person to add missing context, and clarify any differing recollections.
Complete the formal review and any recorded follow-up in the organization’s performance app, and direct process or terminology questions to the responsible manager or People Development owner.

Best practices

Compare work with outcomes agreed for the review period before introducing accomplishments that were not part of the original plan.
For each example, state what happened, when or within what scope, and what the example cannot prove.
Record both the original objective and significant changes to priority, schedule, or scope instead of rewriting the plan after the fact.
Separate directly observed information from interpretation, and invite the other person to add relevant context.
Discuss unfinished outcomes by naming what remained, what changed, and what should happen next without treating context as an automatic excuse or verdict.
Use questions about future priorities and observable progress to turn reflection into specific next steps.
Keep formal ratings, policy definitions, and review submissions in the organization’s approved performance process rather than adding unofficial rules to this reference.
Have the page owner check the review-process links or directions whenever the performance app or internal terminology changes.

What this template typically catches

Issues teams running this template most often surface in practice:

Goals are discussed without checking what was agreed for the review period.

A changed priority or project schedule is omitted, making the final outcome appear disconnected from the original plan.

An example is presented as proof of broad impact even though its scope supports only a narrower conclusion.

Interpretation or an assumption about another person’s actions is reported as an observed fact.

A missed outcome is explained without stating what remained unfinished or what needs to happen next.

Employees and reviewers remember an event differently, but the missing information or follow-up is not identified.

Readers mistake preparation prompts for an official rating scale or a place to submit the review.

The performance app or review guidance changes, but the page’s directions are not checked for accuracy.

Common use cases

Project coordinator preparing for a changed delivery plan

A coordinator uses the fictional Rowan example as a model for recording an original handoff goal, a revised sequence, and evidence limited to the work completed. The prompts keep schedule context separate from claims about overall team impact.

Employee reviewing a partly completed objective

An employee records the intended outcome, what remains unfinished, and relevant changes in priority or dependencies. They bring a question about learning and next steps rather than treating the explanation as a final conclusion.

Manager preparing a balanced conversation

A manager uses the shared prompts to ask for specific examples, scope, and missing context before drawing conclusions. The page supports preparation but leaves ratings and formal documentation to the organization’s established process.

People Development owner publishing review guidance

A People Development owner places this reference near the authoritative review-process guidance and performance app entry point. They customize terminology while preserving the page’s clear distinction between preparation and the formal transaction.

Frequently asked questions

Who should use this preparation page?

Employees and reviewers can use the same prompts to prepare for a balanced discussion. Each person can bring relevant outcomes, evidence, and context to the conversation. The page does not determine ratings or define career levels.

When should I prepare for a review?

Use the page before a scheduled review conversation, while relevant examples and context are still available to recall. The template does not prescribe an organization-wide review cadence. Follow your employer’s review calendar and submission deadlines in its performance app.

How do I use this with the formal review process?

Use the page to organize preparation notes and questions, then use your organization’s performance app for the review transaction and recorded steps. Check the app or your internal process guidance for deadlines and required fields. This reference does not submit or update a review.

What if I have little evidence or an outcome was missed?

Describe the clearest examples available, including their period and scope, and be explicit about what they do not establish. For an incomplete outcome, note what remained unfinished and what changed during the period. Use the conversation to clarify context and agree on next steps rather than presenting an explanation as a verdict.

What should I do if the employee and reviewer recall events differently?

Describe the differing perspectives and identify what information may be missing. Clarify which facts or records could help resolve the question, and agree what needs follow-up. A difference in recollection is a discussion point, not proof that either account is correct.

Does this template determine ratings or meet legal requirements?

No. It is a preparation reference and does not define rating scales, career levels, eligibility, or an organization’s formal review policy. Applicable employment requirements and review procedures vary by organization and location. Ask the manager responsible for the review or the People Development owner about your process.

Can we customize the page for our review process?

Yes. Adapt the sample scenario and wording to your organization’s terminology, review period, and approved process guidance. Keep the distinction between observable evidence, context, and conclusions clear. Use an authoritative internal source for policy or rating definitions rather than creating competing guidance here.

Does this page integrate with the performance app?

The template does not show a configured app connection or transfer notes into a review system. It directs readers to use their organization’s performance app for the formal review transaction and recorded steps. Confirm any available connection or data-handling guidance with your internal system owner.

How is this better than preparing informally?

The page gives employees and reviewers a shared sequence: recall agreed outcomes, select evidence with clear scope, consider context, and prepare questions. Its example also shows how to describe changed plans without assigning blame or overstating impact. It remains a reference, so the organization’s own review process still governs.

Related templates

Sites

Procurement Exception Request

This procurement exception request page helps employees explain when the usual purchasing route c...

Sites

Ethical Scenario Discussion

A facilitator-ready fictional supplier-gift scenario helps managers guide a discussion about impa...

Sites

Legal Help Request Guide

The Legal Help Request Guide helps employees organize the question, parties, locations, dates, an...

Sites

Leaving the Company Well

Leaving the Company Well is a practical departure guide for handing off active work, preparing co...

Sites

Learning Transfer After a Course

A one-page guide for learners and managers to test one course idea in everyday work. Choose a sma...

Forms

Employee Onboarding Form

Employee Onboarding Form for collecting new hire details, tax references, direct deposit, emergen...

Inspections

Abandoned Channel Hygiene Audit

Abandoned Channel Hygiene Audit template for reviewing inactive, orphaned, and duplicate communic...

Sop

Fire Evacuation Procedure

A fire evacuation procedure that tells each role exactly what to do from alarm to accountability....

Go deeper on the topic

Related concepts

Digital Workplace vs Modern Intranet

A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Performance Review Preparation ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Performance Review Preparation A practical reference for employees and reviewers preparing for a balanced review conversation. Fictional example: Rowan, a project coordinator at the fictional Northstar Services, is preparing for a review. Use the same prompts for your role and work setting: start with agreed outcomes, choose specific evidence, consider relevant context, and bring questions for discussion. This page supports preparation for the review transaction in your organization's performance app. It does not define career levels or submit or update a review. Prepare notes here, then use the performance app for the review transaction. On this page Recall outcomes Start with what was agreed, then note what changed. Look back at the goals, deliverables, or responsibilities discussed for the period. For each one, note the intended outcome and any change in priority, scope, or timing. Separate the original aim from work that became important later. Rowan's example: Rowan's original goal was to coordinate an onboarding handoff for a planned project launch. When the project schedule shifted, the handoff was reorganized around the revised launch sequence. Rowan records both the original goal and the revised work, rather than treating the change as if the original plan never existed. If an outcome was not completed, record what remained unfinished and what changed during the period. The conversation can then explore the reasons and next steps without assuming a conclusion. Select evidence Use examples that can be described and checked; state their scope and limits. Outcome or contribution Observable evidence Period or scope What it does not establish Coordinate an onboarding handoff A handoff document was completed and shared with the project group. For the revised launch sequence during the review period. By itself, this does not show that every team's onboarding improved. Respond to a changed project schedule The handoff sequence was reorganized after the launch schedule changed. The work affected by that schedule change. This does not establish the full effect of the change or assign responsibility for it. Consider context Explain conditions that shaped the work without using them as proof or blame. Consider changes in priorities, dependencies, workload, and opportunities to contribute. Include only context that helps explain the work. Distinguish what you observed from what you infer, and leave room for the other person to add information. Rowan's example: A supporting input arrived after the date Rowan had planned around. Rowan can say, “The handoff sequence changed after the supporting input arrived later than expected. I reorganized the remaining steps around the revised schedule. I’d like to discuss what we could coordinate differently next time.” This identifies a relevant dependency without treating it as proof of performance or assigning blame. Prepare for common questions Use specific examples and keep the conversation open where evidence or perspectives differ. What if I have limited evidence? Use the clearest examples you do have, describe their period and scope, and name what you cannot conclude from them. Ask the other person what additional context or evidence would help. How should I discuss an outcome I missed? State the intended outcome, what was completed or remained unfinished, and any relevant changes or dependencies. Ask what can be learned and what should be prioritized next, rather than presenting an explanation as a verdict. What if the employee and reviewer remember events differently? Describe the specific example and the source of each perspective. Ask what information may be missing and agree which facts need clarification. A difference in perspective is a topic to discuss, not evidence by itself that either account is correct. Prepare questions Bring questions that turn reflection into a clear discussion. Which contribution or outcome should I continue building on, and why? What is one approach I should change next period? What evidence or context is missing from this discussion? Which priorities should guide the next period, and how will we recognize progress? Use the organization's performance app for the review transaction and its recorded review steps. For questions about the applicable review process or terminology, ask the People Development owner or the manager responsible for the review.