Standard Operating Procedure: Performance Review Form Documentation

This document outlines the professional standards and procedural requirements for completing employee performance review forms. As an operations manager, the goal of this SOP is to ensure that all feedback is data-driven, actionable, balanced, and objective, thereby fostering professional growth while minimizing legal and interpersonal risk. These guidelines apply to all managers and supervisors responsible for documenting subordinate performance.

Phase 1: Preparation and Data Collection

• Review the employee’s job description and previously established Key Performance Indicators (KPIs).
• Compile "evidence logs," including completed projects, emails of commendation, and missed deadlines from the review period.
• Consult the employee’s self-assessment to identify alignment or discrepancies between manager and employee perspectives.
• Solicit 360-degree feedback from peers or cross-functional stakeholders if required by company policy.

Phase 2: Drafting the Content

• Structure: Use the S.T.A.R. method (Situation, Task, Action, Result) for all specific examples.
• Objectivity: Focus exclusively on observable behaviors and measurable outcomes; avoid subjective language regarding personality.
• Balance: Ensure a "Sandwich" approach where constructive criticism is supported by identified strengths and a clear path forward.
• Clarity: Use direct, professional language. Avoid ambiguity, such as "sometimes" or "often," in favor of "consistently" or "on three separate occasions."

Phase 3: Final Review and Compliance

• Cross-reference ratings against the department’s established grading rubric to prevent grade inflation or bias.
• Check for "recency bias"—ensure the evaluation covers the entire review period, not just the last month.
• Proofread for tone; ensure the document conveys a supportive rather than punitive message.
• Submit the draft to HR or skip-level management for calibration and final approval.

Pro Tips & Pitfalls

• Pro Tip: The "No Surprises" Rule. If an employee is receiving a negative review, they should have already been coached on these issues during 1-on-1 meetings throughout the quarter. The review form should summarize prior discussions, not introduce new disciplinary items.
• Pro Tip: Focus on Future Growth. Spend 40% of the text on past performance and 60% on future goals and development strategies.
• Pitfall: The Halo/Horns Effect. Avoid letting one high-profile success (Halo) or one minor error (Horns) color the evaluation of the employee's entire body of work.
• Pitfall: Vague Feedback. Avoid phrases like "needs to be more proactive." Instead, define what proactivity looks like, such as "proactively scheduling check-ins with stakeholders before the project deadline."

Frequently Asked Questions

Q: How do I handle a disagreement between my assessment and the employee’s self-assessment? A: Acknowledge the discrepancy during the review meeting. Use it as a starting point for discussion rather than a point of contention. Document the divergence in the "Employee Comments" section of the form if necessary.

Q: Should I include personal anecdotes in the performance review? A: No. Keep the content strictly professional. Anecdotes should be limited to work-related project successes or challenges.

Q: What if I have to provide a "Needs Improvement" rating? A: You must provide concrete examples of the deficit and a specific Performance Improvement Plan (PIP) or a clear action plan to address it. Ensure the tone remains constructive and focused on the employee's success, not their termination.