What are performance appraisal criteria?

Performance appraisal criteria are the job-related results, behaviors, capabilities, and responsibilities used to assess an employee's contribution during a defined review period. Each criterion should have a clear standard describing what meeting expectations looks like, relevant evidence the manager can point to, and a reasonable connection to work the employee can actually influence. Criteria that fail this test, such as personality traits, visibility, or outcomes outside someone's control, tend to produce inconsistent ratings across managers even when the wording on the form looks identical.

How many criteria should a performance review use?

There is no universal number. Use enough criteria to cover the role's important results and behaviors without repeating similar concepts or creating shallow comments that managers can't meaningfully differentiate. A focused form typically combines two to four important goals or role outcomes, three to five shared core behaviors, two to four role- or level-specific criteria, and one development priority that may be discussed without a formal score. Adding more fields than managers can write specific evidence for usually produces generic comments rather than a more complete picture.

Should appraisal criteria differ by role and level?

Yes. Some organization-wide criteria, such as communication or collaboration, can stay consistent in name across every level, but the expected scope, complexity, independence, and impact behind that name should change. An early-career employee meeting the communication standard looks different from a vice president meeting it. Individual contributors, managers, and senior leaders also need distinct role-specific measures, since manager-only behaviors like delegation or coaching shouldn't be scored against someone with no direct reports.

What performance appraisal criteria should organizations avoid?

Avoid vague personality labels like "positive attitude" or "culture fit" without a behavioral definition, using visibility or hours logged as automatic evidence of performance, and treating protected or personal circumstances such as health, leave, or family status as performance factors. Also be cautious with outcomes largely outside the employee's influence, future potential presented as if it were current performance, and unverified AI-generated summaries or conclusions, which should never replace manager and HR judgment or count as evidence on their own.

25 Performance Appraisal Criteria by Role and Level

Q: How should performance appraisal criteria be weighted?

Use weights only when role priorities, evidence rules, calculation methods, exceptions, and approval authority are all clearly defined in advance. Essential requirements, such as a safety or quality standard, should never disappear inside a mathematical average just because other criteria scored well. Managers and employees should also understand whether a calculated result is a suggestion the manager can override or the final assessment, since treating a formula as automatically objective can hide real judgment calls behind false precision.

Table of Contents

Key Takeaways:

Performance appraisal criteria should be job-related, known before the cycle, supported by relevant evidence, and reasonably within the employee's influence.
The 25 measures in this guide are a design library, not a recommendation to place 25 scored fields on every review form.
Universal criteria can remain consistent while behavioral examples change by role level, scope, complexity, independence, and impact.
Weighting and calculated scores are useful only when definitions, evidence rules, exceptions, and approval authority are clear.
Manager testing and calibration should improve consistent application without forcing a predetermined rating distribution.

Performance appraisal criteria are the job-related results, behaviors, capabilities, and responsibilities used to evaluate an employee during a defined review period. A useful set of criteria is selected before the cycle, tied to the role and level, supported by evidence the employee can reasonably influence, and written clearly enough that two managers can apply the same standard in a similar way.

The mistake is treating a list of competencies as the appraisal system. A 25-item library can help HR design forms, but a real review should use only the criteria that matter for the role, explain what meeting the standard looks like, and separate role performance from goals, future potential, promotion readiness, and personal style.

Last reviewed: August 4, 2026.

Why Generic Appraisal Criteria Break Down

Imagine an organization using the same form for a customer support specialist, a senior engineer, a people manager, and a vice president. Every employee is rated on communication, leadership, initiative, teamwork, and results. The labels look consistent, but the standard is not.

One manager interprets leadership as helping coworkers. Another treats it as direct-report management. A third gives a low score because the employee has not led a department. The form creates numerical consistency without decision consistency.

A stronger performance review process separates four questions:

What results were expected? Use approved goals, deliverables, and role outcomes.
How was the work performed? Use job-related behaviors, judgment, quality, and collaboration criteria.
What evidence supports the assessment? Use records, work examples, feedback, and observed patterns from the full period.
What should happen next? Use development goals, recognition, support, or a separate formal process when required.

The broader employee performance measurement guide explains how results, quality, efficiency, behaviors, and context work together. This article focuses specifically on selecting and applying appraisal criteria.

The Four-Layer Appraisal Model

A practical review form does not need every available criterion. It needs a deliberate combination of the following layers.

Layer	Purpose	Typical examples	Design warning
Role outcomes	Assess the work the position exists to produce.	Goal achievement, service quality, delivery, customer outcome.	Do not use an outdated target after scope or resources changed.
Core behaviors	Apply a small set of organization-wide expectations.	Communication, collaboration, judgment, reliability.	Universal language still needs level-specific examples.
Role or level criteria	Measure responsibilities that apply to a defined population.	Technical proficiency, delegation, coaching, strategic alignment.	Do not rate individual contributors against manager-only behaviors.
Development priorities	Record capabilities to build for the current or next realistic responsibility.	Executive communication, delegation, technical depth.	Development does not always need a scored rating.

Goals should come from an approved goal management process, including documented changes to scope, timing, ownership, and dependencies. Ongoing 1-on-1 check-ins can preserve context so the final review does not depend on recent memory.

Build Review Forms Around the Role, Not a Generic Library

Connect role-relevant criteria with goals, evidence, rating definitions, manager guidance, and calibration inside one review workflow.

Explore Performance Reviews

25 Performance Appraisal Criteria by Role and Level

The following list is a design library, not a recommendation to put 25 scored fields on every form. Select a focused set that reflects the role, review purpose, and evidence available.

#	Criterion	Best fit	What it measures	Possible evidence
1	Goal achievement	Broad use	Progress and results against relevant, approved goals.	Goal records, milestones, approved changes, result quality.
2	Quality of work	Broad use	Accuracy, completeness, usefulness, and adherence to the role standard.	Work samples, acceptance criteria, error and rework patterns.
3	Reliability and follow-through	Broad use	Consistency in meeting commitments and communicating changes.	Completed actions, deadline updates, handoff records.
4	Communication	Broad use	Clarity, listening, audience awareness, documentation, and escalation.	Written updates, presentations, decisions, stakeholder feedback.
5	Collaboration	Broad use	Contribution to shared work across colleagues and functions.	Cross-functional outcomes, handoffs, conflict-resolution examples.
6	Customer or stakeholder focus	Broad use	Understanding needs, setting expectations, and following through.	Feedback, issue resolution, requirement clarification, follow-up.
7	Problem solving	Broad use	Defining issues, analyzing evidence, comparing options, and learning.	Decision records, root-cause work, experiments, lessons applied.
8	Learning and adaptability	Broad use	Applying feedback and responding constructively to changing work.	Changed behavior, new practices, transition outcomes.
9	Functional or technical proficiency	Individual contributor	Application of knowledge and skills required for the role.	Work samples, expert review, safe application, problem complexity.
10	Execution discipline	Individual contributor	Planning, prioritizing, and completing work through an appropriate process.	Plans, milestones, risks, delivery records, retrospectives.
11	Professional judgment	Individual contributor	Making proportionate decisions within authority, context, and risk.	Decision rationale, escalation choices, tradeoffs, later learning.
12	Ownership	Individual contributor	Taking responsibility for an outcome, including correction and closure.	End-to-end follow-through, issue correction, closed actions.
13	Knowledge sharing	Individual contributor	Making expertise reusable through coaching, documentation, or support.	Guides, mentoring, reusable resources, colleague feedback.
14	Goal clarity	Manager	Setting expectations employees can understand and act on.	Goal quality, alignment, employee understanding, updates.
15	Coaching and feedback	Manager	Providing timely, specific support that develops performance and judgment.	1-on-1 records, feedback examples, development follow-up.
16	Delegation	Manager	Assigning ownership with appropriate authority, context, and support.	Ownership distribution, handoff clarity, intervention patterns.
17	Team coordination	Manager	Creating workable priorities, roles, communication, and operating routines.	Plans, workload choices, handoffs, team delivery patterns.
18	Performance-management follow-through	Manager	Completing reviews, addressing gaps, recognizing contribution, and tracking actions.	Review quality, follow-up records, recognition, support plans.
19	Resource prioritization	Manager	Allocating time, attention, and available resources to the most important work.	Capacity tradeoffs, staffing rationale, priority decisions.
20	Strategic alignment	Senior leader	Connecting organizational direction to portfolio and operating decisions.	Portfolio choices, resource allocation, communicated priorities.
21	Cross-functional influence	Senior leader	Building alignment without relying only on formal authority.	Decision progress, stakeholder alignment, conflict navigation.
22	Organizational capability	Senior leader	Building systems, leadership capacity, talent, and operating practices.	Succession actions, capability indicators, operating improvements.
23	Decision quality under uncertainty	Senior leader	Making timely, reasoned choices with incomplete information and material consequences.	Assumptions, scenarios, risk review, decision timing, learning.
24	Change leadership	Senior leader	Preparing people and systems for material change while maintaining accountability.	Change plans, communication, adoption evidence, issue response.
25	Governance and risk awareness	Senior leader	Recognizing material risk and using appropriate controls, approvals, and escalation.	Risk reviews, approvals, decision records, escalation choices.

Universal Criteria Are Not Identical Criteria

Communication, collaboration, problem solving, and reliability may apply across the organization, but the expected scope changes by level. The criterion can stay consistent while its behavioral anchors change.

Criterion	Early-career employee	Experienced individual contributor	Manager or leader
Communication	Provides clear updates and asks questions when expectations are uncertain.	Adapts technical and nontechnical communication and documents decisions.	Creates clarity across teams, explains tradeoffs, and handles difficult messages.
Problem solving	Uses established methods and seeks help for unfamiliar issues.	Defines ambiguous problems, compares options, and records reasoning.	Creates decision conditions, allocates expertise, and manages material risk.
Collaboration	Contributes reliably to shared work and handoffs.	Builds cross-functional alignment and resolves working disagreements.	Creates operating agreements and addresses structural barriers.
Ownership	Completes assigned work and raises blockers.	Manages dependencies, corrects issues, and closes the loop.	Creates clear accountability across people, priorities, and decisions.

This distinction also matters when writing comments. The performance review strengths and weaknesses examples show how observable behavior can be described without using personality labels. For specific development wording, use the areas-of-improvement guide.

A Worked Example: One Criterion, Three Different Standards

Consider the criterion collaboration.

Operations coordinator: Shares accurate handoff information, confirms ownership, and raises missing inputs before a deadline is affected.
Senior project manager: Aligns multiple functions around dependencies, resolves working disagreements, and records decisions that affect delivery.
Vice president: Establishes decision rights across functions, resolves structural conflict, and aligns resources with enterprise priorities.

All three employees can meet the collaboration standard, but the scope and evidence differ. Using the same sentence for each level would either overstate the coordinator's responsibility or understate the vice president's.

Where a manager cannot observe enough of the work, relevant 360-degree feedback or a defined feedback workflow can add perspective. Multi-source input should still be interpreted in context rather than converted automatically into a rating.

How Many Criteria Should a Review Use?

There is no universal number. Use enough criteria to cover the role's important results and behaviors without creating repetition or shallow comments.

A focused form might contain:

Two to four important goals or role outcomes
Three to five shared core behaviors
Two to four role- or level-specific criteria
One development priority that may be discussed without a score

This is an illustrative design pattern, not a required formula. Combine or remove criteria when managers cannot explain the difference. Accountability, ownership, reliability, and execution often overlap unless each term has a distinct purpose.

How to Define Evidence Before the Cycle Starts

Each criterion should name the evidence that may support it. Possible sources include:

Approved goals and milestone updates
Work samples and quality records
Project outcomes and documented decisions
Recurring check-in notes and agreed commitments
Relevant customer or stakeholder feedback
Requested peer or multi-rater feedback
Development activities and evidence of application
Manager observations across the review period
Role standards and documented changes to responsibility

No source should automatically determine the assessment. A numerical output may need context, and a manager observation may need corroboration. Employees preparing their own perspective can use the employee self-appraisal template and the self-appraisal comments examples to organize evidence without copying unsupported claims.

How to Write Behavioral Descriptors

Begin with the definition of meeting expectations. Then write the lower and higher descriptors by changing consistency, scope, complexity, independence, or impact.

Criterion	Below the standard	Meets the standard	Above the standard
Reliability	Material commitments are missed without timely communication or recovery.	Commitments are generally met, and changes are communicated with practical next steps.	Complex dependencies are managed proactively, improving reliability for shared work.
Coaching	Feedback is delayed, vague, or not followed by appropriate support.	The manager provides specific feedback and follows through on agreed support.	The manager develops employee judgment and improves coaching practices across the team.
Strategic alignment	Priorities repeatedly conflict with approved direction without documented rationale.	Plans and resources reflect approved direction and relevant tradeoffs.	The leader helps other groups translate strategy into coherent operating decisions.

The performance review rating-scale guide compares three-, four-, five-point, and behaviorally anchored approaches. Use the annual performance review template as a starting point when testing criteria and descriptors together.

Should Performance Appraisal Criteria Be Weighted?

Weighting can reflect role priorities, but it creates false precision when definitions or evidence are weak. Before assigning percentages, decide:

Which criteria are essential requirements rather than tradeable points
Whether goals and role behaviors remain separate
How approved goal changes affect the calculation
How missing or not-observed criteria are handled
Whether the system calculates a suggestion or a final result
Who can change weights and at what stage
How employees and managers will understand the formula

A mathematical average should not hide a material safety, conduct, quality, or essential-role issue. Final review narratives should explain the evidence rather than repeat the score. Managers can use the performance review examples and phrases to turn evidence into clear comments.

Who Owns Each Part of the Criteria Process?

Owner	Primary responsibility	Required output
HR or performance-process owner	Defines the review purpose, governance, core criteria, rating approach, and cycle rules.	Approved design, definitions, timeline, permissions, and manager guidance.
Functional or role-family leader	Confirms job relevance and role-specific standards.	Role examples, evidence sources, and distinctions by level.
Manager	Applies the criteria using representative evidence and discusses the result.	Proposed ratings, narrative, examples, and agreed next actions.
Employee	Provides relevant context, evidence, and reflection where the process includes self-assessment.	Self-assessment, examples, context, and support needs.
Calibration group	Tests whether standards are applied consistently across comparable cases.	Approved changes, rationale, and unresolved issues routed to the correct owner.

A normal development priority may move into an individual development plan. When an employee is not meeting essential expectations and a formal process is appropriate, HR may determine that a separate performance improvement plan is required. These are not interchangeable.

Test the Criteria Before Launch

Create representative cases for different roles and levels.
Ask several managers to assess the cases independently.
Compare ratings, evidence, and written reasoning.
Identify criteria that overlap or produce inconsistent interpretation.
Revise definitions and behavioral anchors.
Test the form inside the real review workflow.
Confirm how not-observed criteria, changed goals, and exceptions are handled.
Prepare manager and employee guidance before the cycle opens.

Edge cases should include a high result achieved through weak collaboration, strong behavior with an incomplete goal, a recently promoted employee, a changed role, and an employee whose manager had limited observation.

Use Calibration to Test Application, Not Force a Curve

Performance calibration can help managers compare evidence, rating definitions, role context, and uncertain cases. It should not force a predetermined distribution or change a rating merely because one team has a different pattern.

The performance calibration best-practices guide covers preparation, meeting roles, evidence review, and decision documentation. After the cycle, performance reporting and analytics can surface missing narratives, rating distributions, workflow gaps, and criteria that managers rarely used. HR should investigate context before interpreting a pattern as bias or performance difference.

Criteria to Avoid or Use With Great Caution

Personality labels: Terms such as positive attitude, executive presence, culture fit, difficult, or naturally gifted require careful behavioral definition and can invite subjective interpretation.
Hours or visibility: Time online, office presence, message volume, and meeting attendance do not prove performance by themselves.
Potential as current performance: Future readiness is a different question from contribution in the current role.
Outcomes outside employee influence: Market conditions, team results, and organizational constraints require attribution and context.
Protected or personal circumstances: Health, disability, age, family status, leave, and other protected information are not performance criteria.
Unverified AI conclusions: AI-generated summaries or suggestions should not create evidence, determine a rating, or replace manager and HR judgment.

Final Appraisal-Criteria Checklist

The review purpose and downstream use are documented.
Every criterion is relevant to the role or defined employee population.
Universal criteria include examples that change appropriately by level.
The expected standard is known before the review period ends.
Evidence sources and employee influence are defined.
Goals, role behaviors, development, and future potential are not silently blended.
Weights and calculations are explainable.
Managers have practiced with representative cases.
Calibration tests standards without forcing a curve.
Post-cycle reporting identifies criteria that caused confusion or added little value.

How PerformSpark Supports Role-Based Appraisals

PerformSpark connects configurable review cycles with goals, self-assessments, manager assessments, check-ins, feedback, calibration, development plans, and reporting. HR teams can maintain shared organization-wide criteria while using different templates or examples for defined role families and levels.

The platform supports the workflow and record. Managers and HR remain responsible for selecting relevant criteria, evaluating evidence, resolving sensitive cases, and authorizing final ratings and follow-up actions.