Performance Review Meeting Agenda: Evidence, Development and Follow-Up

A performance review meeting agenda helps an employee and manager discuss the review period with evidence, clarity and room for genuine dialogue. It should connect role expectations and outcomes with context, employee perspective, a fair evaluation, development priorities, manager support and specific follow-up.

This article concerns employee-manager performance reviews, not client reviews or project retrospectives. The agenda is not employment, legal or HR advice. Applicable law, collective arrangements, contracts, approved policy and qualified HR or legal guidance take priority, especially for ratings, pay, promotion, accommodation, discipline or termination.

Confirm the purpose, period and process

State the review period, employee role, manager, meeting date and purpose. Clarify whether the conversation covers development, a formal rating, goal setting, compensation or only some of these. If decisions occur in separate processes, explain the boundaries so the employee is not left to infer hidden outcomes.

Check required notice, forms, participants, rating definitions, calibration steps and employee response rights under policy. Confirm whether the employee may bring a support person or request an accommodation. Do not repurpose a routine review as an unexpected disciplinary meeting.

Share the agenda and relevant materials early enough for meaningful preparation. Provide accessible formats and a private, suitable setting.

Check whether the designated manager has observed enough of the period to evaluate fairly. If reporting lines changed, gather appropriate input through the approved process and tell the employee how it will be used. Do not let a new manager convert limited familiarity into unwarranted certainty.

Prepare balanced and relevant evidence

Start with the role description, agreed goals, prior feedback and documented work outcomes. Gather evidence across the full period rather than relying on recent, vivid or isolated events. Consider quality, collaboration, customer or operational outcomes and role-specific behaviors only where they are relevant and fairly assessed.

Distinguish direct observation, system data, stakeholder feedback and inference. Verify sources and give the employee a fair opportunity to respond. Avoid using anonymous comments as unchallengeable proof, and never introduce protected characteristics, health information or unrelated personal circumstances into evaluation.

Check data quality and context. Counts can be incomplete, differently defined or shaped by work allocation. Use approved measures as evidence alongside qualitative judgment, not as an automatic ranking. If monitoring data is involved, confirm that its collection and use comply with applicable policy and law.

Use a decision log template when formal decisions require a traceable rationale, but follow HR rules for access and retention. The manager remains accountable for the assessment.

Copy this performance review agenda

EMPLOYEE PERFORMANCE REVIEW MEETING

Employee / role / manager:
Review period / meeting date:
Policy / rating framework / process owner:
Meeting purpose and decisions in scope:
Accommodation or support arrangements:

AGENDA
1. Purpose, process and respectful discussion agreements — 5 min
2. Employee reflection and context — 10 min
3. Role expectations, goals and verified outcomes — 15 min
4. Strengths and contributions — 10 min
5. Obstacles, support and manager responsibilities — 10 min
6. Evaluation and evidence-based feedback — 15 min
7. Development priorities and opportunities — 10 min
8. Future goals, measures and dependencies — 10 min
9. Employee questions, disagreement and response route — 5 min
10. Actions, owners, dates and next checkpoint — 5 min

FOLLOW-UP RECORD
Evidence discussed / source:
Employee perspective or correction:
Evaluation decision / authorized owner:
Development action / support / owner / date:
Goal / measure / dependency / review date:
Unresolved disagreement / review route:
Employee comments / acknowledgment meaning:

Adapt timing and fields to policy. An acknowledgment should mean only what the policy says; it must not be framed as agreement if it merely confirms receipt. Do not use the form to waive rights.

Open with clarity and psychological safety

Explain the meeting structure, time available, decisions in scope and how notes will be used. Invite the employee to correct factual errors and ask questions. A respectful review can still contain difficult feedback, but it should not rely on ambiguity, surprise or pressure.

Reconfirm confidentiality limits. Managers should not promise absolute secrecy where HR, legal or leadership review is required, yet information should be shared only with authorized people. If a participant needs a pause, interpretation or an accommodation, follow the applicable process.

An accessible meeting checklist can help remove participation barriers. Accessibility is not a favor or a proxy for performance; route requests appropriately and protect private information.

Invite the employee’s account first

Ask the employee to describe achievements, challenges, changed priorities, support received and work they believe is underrepresented. Listen before presenting a settled narrative. Their account may identify dependencies, resource constraints or invisible contributions that the initial evidence missed.

Use specific, neutral questions: What outcome are you most proud of? Which expectation became harder to meet, and why? What feedback changed your approach? What support would improve the next period? Avoid questions that pressure disclosure of health, family or other protected personal details.

Record relevant corrections and verify them after the meeting when necessary. The employee perspective is evidence to consider, not automatically proof or a ceremonial section to ignore.

Discuss achievements and expectations with evidence

Connect feedback to documented role expectations and agreed goals. Describe the situation, observable contribution and effect without exaggeration. Recognize work that supported the team, quality or risk reduction even when it is less visible than headline outputs.

Where goals changed, assess against the approved updated expectation rather than an obsolete plan. Discuss dependencies and manager decisions that affected delivery. Do not attribute systemic shortages, unclear priorities or missing authority solely to the employee.

For employees early in a role, the employee onboarding checklist may show whether training, access and expectations were actually provided. Context informs fair judgment without eliminating accountability.

Deliver constructive feedback and evaluation

Present feedback in specific behavioral and outcome terms. Explain the applicable standard, evidence, impact and expected change. Separate a capability gap, conduct concern, resource issue and preference; they require different responses and may follow different formal processes.

If a rating is part of the review, use only approved definitions and explain how evidence maps to them. Check consistency with comparable roles through the organization’s authorized calibration process. Do not use demographic data or automated recommendations to justify an individual rating.

Give the employee time to respond. If material evidence is disputed, record the disagreement and follow the review route rather than forcing immediate assent. Qualified HR or legal owners should handle high-stakes or potentially discriminatory concerns.

Agree development and manager support

Choose a small number of development priorities connected to the role, employee aspirations and organizational needs. Options may include practice, coaching, mentoring, training, stretch work or clearer feedback loops. Do not treat development as a coded disciplinary message.

Specify what the manager and organization will provide: budget approval, protected time, access, coaching, clearer priorities or removal of a blocker. Development plans fail when every action belongs to the employee while the required environment remains unchanged.

Make opportunity allocation fair and transparent. Consider workload and accessibility, and do not assume that travel, after-hours activity or unpaid extra effort is available to everyone.

Set future goals and review points

Write goals that describe the desired outcome, evidence, timeframe, dependencies and decision rights. Use measures appropriate to the role and avoid a single metric that encourages poor quality or gaming. Clarify which goals are commitments, which are experiments and which depend on resources not yet approved.

Agree how progress feedback will occur before the next formal review. A meeting follow-up structure can preserve actions and dates, but ongoing manager feedback should not be deferred to an annual conversation.

If priorities change, update the goal record and communicate the effect. Evaluating someone against hidden or retroactively changed expectations is not a fair process.

Handle disagreement and sensitive decisions properly

Tell the employee how to submit comments, request correction or use an appeal or review process. Record the exact point of disagreement and supporting evidence without characterizing respectful challenge as poor attitude. Provide documents and timelines required by policy.

Compensation, promotion, performance improvement, discipline and termination require authorized processes and qualified review. If these are out of scope, do not imply a decision. If they are in scope, give required notice, explain authority and document the next step clearly.

Exit-related themes belong in the relevant process; exit interview questions should not be introduced as a veiled signal during a standard employee performance review.

Use Kuno only with informed authorization

Performance conversations contain sensitive employment and personal data. Recording can affect candor and power dynamics. Capture only when the employer is authorized, notice is clear, consent is valid where required, a suitable alternative exists, and HR-approved access, retention and deletion controls are applied.

Turn an authorized review into draft notes and actions for careful verification. Kuno can support consented capture, while the manager, employee and qualified HR owners validate every sensitive detail. Explore Kuno

Never use generated summaries to infer emotion, personality, health, protected characteristics or future potential. Human reviewers must correct errors and make all employment decisions.

Document follow-up without reducing dialogue to a score

Issue the reviewed record through the approved system. Include evidence discussed, evaluation, employee response, goals, development support, manager actions, unresolved items, review route and next checkpoint. Give the employee access as policy requires and correct factual errors visibly.

Managers should follow through on promised support and provide timely feedback. HR owners should monitor consistency and process quality using appropriately protected information, not treat software output as proof of fairness.

Keep employee review discussions connected to responsible follow-through. Kuno supports authorized capture and draft action notes; accountable people remain responsible for fairness and employment decisions. See Kuno

A good review leaves expectations, evidence, support and next steps clearer, while preserving the employee’s ability to question the record and be treated with dignity.

FAQ