Performance Evaluation Template

In plain language: Records the employee's full name, job title, department, employee ID, manager's name and title, and the date the evaluation is conducted.

Common mistake: Using informal names or nicknames instead of legal names. Discrepancies between the evaluation and payroll records create matching problems during audits or litigation.

In plain language: Defines the exact start and end dates of the performance period being assessed, ensuring the rating covers an agreed window rather than an undefined timeframe.

Common mistake: Leaving the review period blank or writing 'annual review' without specific dates. Courts and arbitrators rely on the period to test whether documented incidents fall within scope.

In plain language: Establishes the scoring system used throughout the form — typically a 1–5 numeric scale or a labeled scale — with a clear description of what each level means.

Common mistake: Defining the scale in the form but applying it inconsistently across departments. Inconsistency is the primary basis for discrimination claims comparing two employees rated by different managers.

In plain language: Rates the employee on defined behavioral and technical competencies relevant to their role, with a numeric or descriptive rating and supporting narrative for each.

Common mistake: Providing ratings without any supporting narrative. Bare numeric scores are nearly impossible to defend in an employment dispute — behavioral examples are what make a rating credible.

In plain language: Reviews each goal set at the beginning of the review period, records the outcome or measurable result, and assigns a rating for goal attainment.

Common mistake: Rating goals that were never formally set or documented at the start of the period. Evaluating employees against retroactive expectations is a common basis for wrongful termination claims.

In plain language: Summarizes all competency and goal ratings into a single overall score or category, which typically determines merit increase eligibility, promotion consideration, or PIP triggers.

Common mistake: Calculating the overall rating informally or by gut feel rather than from a documented weighting formula. Unexplained overall ratings that differ significantly from individual scores are a red flag in discrimination cases.

In plain language: Outlines agreed training, coaching, or stretch assignments to address gaps identified in the review, and sets measurable SMART goals for the next review period.

Common mistake: Writing vague development actions like 'improve communication skills' with no owner or deadline. Development items without accountability dates are rarely completed and provide no protection if the employee is later terminated for the same issue.

In plain language: Provides the reviewing manager's overall narrative summary, specific examples of strengths and areas for improvement, and a recommendation on compensation, promotion, or further action.

Common mistake: Including personal opinions, speculative language, or references to protected characteristics (age, health, family status) in the narrative. These create direct exposure to discrimination claims and should be replaced with specific behavioral observations.

In plain language: Provides a dedicated section for the employee to write their own perspective on the review, including agreements, disagreements, or additional context they want recorded.

Common mistake: Skipping the employee comment section or not offering it at all. Employees who have no formal avenue to respond are more likely to escalate disagreements externally through HR complaints or legal action.

In plain language: Records signatures from both the reviewing manager and the employee, with the date each signed, confirming the evaluation was conducted and the employee received a copy.

Common mistake: Obtaining only the manager's signature and filing the form unsigned by the employee. Without the employee's signature, the employer cannot prove the review was communicated — undermining the entire documentation record.

A performance evaluation is a structured, signed document that formally records a manager's assessment of an employee's job performance over a defined period — typically 6 or 12 months. It covers competency ratings, goal achievement, an overall score, and a development plan. Beyond guiding career development, it creates the documented record employers rely on for compensation decisions, promotions, and, when necessary, disciplinary action or termination.

A performance evaluation is not a contract in the traditional sense, but it carries significant legal weight. Once signed by both parties, it becomes a formal HR record that can be introduced as evidence in wrongful termination, discrimination, or constructive dismissal proceedings. Courts treat a signed evaluation as the employer's contemporaneous account of the employee's performance — making accuracy and specificity critically important.

In most jurisdictions, no law compels an employee to sign. However, the employer should make clear that the signature confirms receipt and review of the document, not agreement with its contents. If an employee refuses to sign, document the refusal in writing, note the date the form was provided, and have a witness sign. An unsigned-but-delivered evaluation is far stronger than a signed evaluation the employee was never shown.

Annual reviews are the most common cycle for established employees. Many organizations add a mid-year check-in — a shorter, less formal assessment — to address performance issues early and adjust goals. New hires typically receive a 30-, 60-, or 90-day evaluation before their first annual review. High-growth environments and regulated industries often require more frequent formal documentation.

A performance evaluation is a scheduled, comprehensive assessment of overall job performance covering all competency areas and goals. A Performance Improvement Plan (PIP) is a targeted, time-bound remediation document triggered when an evaluation — or ongoing observation — identifies performance that falls below an acceptable threshold. A PIP typically specifies the deficiency, the required improvement, a timeline, and the consequence of non-compliance. Evaluations document performance history; PIPs activate a formal corrective process.

Yes, a documented history of low performance ratings — particularly when paired with a development plan the employee failed to complete — is typically the strongest evidence an employer can provide to support a for-cause termination. Without this documentation, terminations are harder to defend, and employers may face larger wrongful dismissal awards. In at-will employment states in the US, documentation is not legally required, but it is strongly advisable to reduce litigation risk.

The most common scales are a 1–5 numeric scale and a five-label descriptive scale (Unsatisfactory through Outstanding). A 1–5 scale is easy to aggregate for calibration and compensation modeling. A descriptive scale reduces numeric anchoring bias, where managers avoid 1s and 5s regardless of actual performance. Whichever you choose, define each level explicitly on the form and apply it consistently across all managers and departments.

Provide a dedicated employee comments section on the form and allow the employee to write their perspective before signing. If the disagreement is substantive, offer a review meeting with HR present. Some organizations allow a formal written rebuttal to be attached to the evaluation and kept in the file. What you should not do is alter the manager's original ratings under employee pressure — document the disagreement, but do not change a rating without new, specific evidence that changes the factual record.

Avoid any reference to protected characteristics — age, health, pregnancy, disability, religion, ethnicity, national origin, or family status. Avoid speculative language about future behavior ("I worry she won't handle a promotion"). Avoid comparisons to other named employees. Avoid personal opinions framed as performance observations. Stick to specific, observable behaviors and measurable outcomes during the review period. Everything written in an evaluation is potentially discoverable in litigation.