
An employee evaluation form is a document used to record an assessment of an employee's performance during a defined period. It commonly includes identifying information, job responsibilities, performance criteria, a rating scale, comments, accomplishments, development areas and goals.
Organizations may use the form for annual or semiannual reviews, probationary reviews, project evaluations, self-assessments or development discussions. The content should reflect the role and the purpose of the review rather than use the same generic traits for every employee.
A thoughtfully designed form can help an organization:
Communicate what effective performance looks like
Review job results and work behaviors in one place
Apply a repeatable structure across review periods
Record specific achievements and development needs
Support goal-setting and training decisions
Prepare managers and employees for a focused discussion
Track progress from one review to the next
Create documentation for employment decisions
A standardized form does not mean every employee receives identical goals. It means comparable roles are evaluated through a consistent process, using relevant expectations and evidence.
Record the employee's name, title, department, manager, review dates and evaluation type. Clear dates prevent confusion when a file is referenced later.
List the position's core responsibilities or attach the current job description. Evaluate work the employee is actually expected and equipped to perform.
Include the major goals established for the period, the intended measures and the actual outcome. Not every valuable contribution can be reduced to a number, but the criteria should still be observable.
Competencies describe how work is performed. Examples may include communication, collaboration, judgment, customer focus, quality, leadership or safety. Select only those relevant to the role.
Define every rating so managers and employees understand the difference between levels. A number without a behavioral definition invites inconsistent interpretation.
Require concise examples supporting each important rating. Facts, dates, outputs and observed behaviors are more useful than broad personality judgments.
Summarize capabilities to continue using and specific areas to improve. Development feedback should identify an action or resource, not merely name a weakness.
Document the next period's priorities, success measures, target dates and support needed from the manager or organization.
Give the employee space to add context, record disagreement or identify support needs. A signature can acknowledge receipt and discussion; it should not automatically be described as agreement unless company policy clearly says so.
A five-level scale can work when each level has a clear definition:
| Rating | Label | General definition |
|---|---|---|
| 5 | Exceptional | Results and behaviors substantially and consistently exceed the defined expectations for the role |
| 4 | Exceeds expectations | Performance regularly exceeds important expectations, with clear supporting evidence |
| 3 | Meets expectations | Performance consistently fulfills the established requirements of the role |
| 2 | Partially meets expectations | Some requirements are met, but improvement is needed in specific important areas |
| 1 | Does not meet expectations | Performance does not meet one or more essential requirements and requires prompt improvement |
| N/A | Not rated | The criterion was not applicable or there was insufficient opportunity to observe it |
Organizations may use three, four or five levels. More levels do not necessarily create more accuracy. The important work is defining standards, training reviewers and grounding ratings in evidence.
Decide whether the form supports compensation, development, probation, promotion, project feedback or a combination. The purpose affects the criteria, reviewers, documentation and approvals required.
Review the current job description, goals and essential responsibilities. Remove generic criteria that have little connection to the work. A software engineer and an account manager may both need collaboration, but the observable behaviors can differ.
Choose the results and competencies that matter most. A form with 20 overlapping categories can create busywork and dilute important feedback. Combine related concepts and explain each one.
Replace abstract traits with behaviors or outcomes. “Positive attitude” is difficult to assess consistently. “Responds constructively to feedback and communicates project risks promptly” is more observable and job-related.
Provide definitions and, where practical, role-specific examples. Clarify whether an overall score is an average, a weighted calculation or a manager judgment based on all evidence.
Create space for accomplishments, metrics, examples, customer feedback and relevant constraints. A rating should not stand alone when it may influence development, compensation or other employment decisions.
A self-assessment can surface accomplishments the manager did not observe and identify barriers or support needs. It should inform the conversation without forcing managers to copy the employee's rating.
Requirements differ by jurisdiction, sector, collective bargaining agreement and organizational policy. Review record retention, confidentiality, accessibility, employee access and decision-making procedures before implementation.
Test the form with a small group of managers and roles. Check whether criteria are clear, ratings produce usable distinctions and reviewers interpret standards similarly. Calibration discussions can identify inconsistent reasoning, but they should not force ratings into a predetermined distribution.
Use goals, project outcomes, work samples, recognition, customer feedback and notes from regular discussions. Avoid relying only on recent events. Consider context, but do not excuse or exaggerate performance based on assumptions.
The U.S. Equal Employment Opportunity Commission advises employers to communicate standards, apply them consistently and explain whether employees met them using relevant facts. Evaluate the employee against the role's established expectations, not against a manager's changing personal preferences.
An employee may reach a target while creating avoidable risks, or demonstrate good collaboration while missing an essential result. Reviewing both dimensions produces clearer feedback than allowing one positive or negative impression to determine every rating.
Describe the situation, behavior and effect. For example, “Completed the quarterly inventory reconciliation three days early with no material errors” is more useful than “Has an excellent attitude toward deadlines.”
Explain the evidence and invite questions. Listen for information you may have missed, including changed priorities, unavailable resources or work performed for another team. Correct factual errors when identified.
Convert development feedback into a specific plan. Name the skill or outcome, action, measure, deadline and support. Schedule a follow-up rather than waiting until the next annual review.
Copy and adapt the following template. Replace the example criteria with standards relevant to the role.
Employee name:
Job title:
Department:
Manager/reviewer:
Review period:
Evaluation date:
Evaluation type: Annual / Semiannual / Probationary / Project / Other
5 — Exceptional: Substantially and consistently exceeds defined expectations
4 — Exceeds expectations: Regularly exceeds important expectations
3 — Meets expectations: Consistently fulfills role requirements
2 — Partially meets expectations: Meets some requirements; specific improvement is needed
1 — Does not meet expectations: Does not meet essential requirements
N/A — Not rated: Not applicable or insufficient observation
| Goal or responsibility | Success measure | Result/evidence | Rating |
Standard: Produces work that meets defined requirements, checks important details and corrects errors promptly.
Rating:
Evidence/comments:
Standard: Completes agreed priorities on time and communicates early when risks may affect delivery.
Rating:
Evidence/comments:
Standard: Shares information clearly, listens to others and adapts communication to the audience and situation.
Rating:
Evidence/comments:
Standard: Contributes to shared goals, coordinates dependencies and treats colleagues and customers professionally.
Rating:
Evidence/comments:
Standard: Identifies relevant facts, considers risks and makes or escalates decisions at the appropriate time.
Rating:
Evidence/comments:
Competency:
Standard:
Rating:
Evidence/comments:
| Development area | Action | Success measure | Target date | Support/resources |
| Goal | Measure | Deadline | Check-in date |
Overall rating, if used:
Summary:
Employee signature/date:
Manager signature/date:
Additional reviewer/date, if required:
Signature acknowledges receipt and discussion of this evaluation and does not necessarily indicate agreement, subject to company policy.
“Jordan completed all four scheduled client migrations within the approved windows and documented open issues before handoff. Stakeholder updates were timely and included clear owners and next steps.”
“Priya exceeded the quarterly retention target by four percentage points and created a cancellation-analysis dashboard that the broader team now uses in weekly planning.”
“Three of the past six monthly reports were submitted after the agreed deadline, limiting the finance team's review time. Beginning next month, the draft is due two business days earlier, with risks raised during the weekly check-in.”
The final example states the performance gap, impact and next expectation. It avoids labeling the employee as careless or unmotivated.
A direct manager reviews the employee's results and behaviors. This is common because managers assign work and are accountable for coaching, but they may not observe every contribution.
The employee summarizes accomplishments, challenges and development priorities. Self-evaluations can improve preparation and reveal evidence, but ratings still require discussion and manager judgment.
Feedback comes from several groups, such as peers, direct reports, managers and internal customers. It can broaden perspective, especially for leadership behaviors. Confidentiality, question design and interpretation require care.
The review centers on agreed objectives and key results. This format clarifies outcomes but should account for changed priorities and avoid rewarding targets that encourage harmful shortcuts.
Each level includes examples of observable behavior. This can improve rating clarity but takes time to develop and maintain for different roles.
This form assesses early progress, training completion and readiness for core responsibilities. It should not replace frequent onboarding feedback.
Set expectations at the beginning of the review period.
Give feedback throughout the year, not only on the form.
Evaluate actual job performance using relevant evidence.
Apply standards consistently to comparable work.
Consider the full period and guard against recency bias.
Separate facts from assumptions about personality or intent.
Train managers to use the scale and write useful comments.
Review patterns across teams for possible inconsistency or bias.
Protect evaluation records according to policy and applicable law.
Give employees a way to ask questions or request correction of factual errors.
Connect improvement feedback with resources and follow-up dates.
Evaluation results can affect pay, promotion, discipline and other employment decisions. Employers should use job-related criteria and obtain qualified HR or legal guidance for their specific jurisdiction and circumstances. A general template is a starting point, not a substitute for applicable policy or law.
Managers often need to present review-cycle findings, team goals or development plans without exposing confidential individual details. Dokie can help turn approved aggregate data and planning notes into a structured presentation for leadership discussions, manager training or workforce planning.
Dokie is an AI presentation maker that creates polished, editable decks from prompts and documents. HR and team leaders can use Dokie to draft performance-review training, goal-setting workshops or anonymized talent summaries, while keeping sensitive employee information out of unnecessary tools and following company privacy requirements.
Many organizations use annual or semiannual formal reviews supported by regular check-ins. The appropriate cadence depends on the role, business cycle and policy. Important feedback should not wait for the formal review.
It can, but it is not required. A score is useful only when levels are defined and applied consistently. Written evidence and discussion remain important.
Yes. Organizations should explain how employees can add comments, identify factual errors or use an internal review process. Acknowledging receipt does not necessarily mean agreement, depending on policy.
Avoid vague personality labels, speculation about intent, irrelevant personal information and statements unsupported by evidence. Comments should relate to communicated job expectations and observable performance.
A common structure and rating method can support consistency, but goals and role-specific criteria should reflect the actual job. Using identical competencies for unrelated roles may reduce relevance.
Retention requirements depend on jurisdiction, industry, employer size, contract and how the records are used. Follow the organization's approved retention policy and obtain appropriate legal guidance.