Objective Performance Review: Criteria and Evidence Worksheet

Short answer

An objective performance review is better understood as a disciplined evidence process, not a bias-free verdict. Define role-relevant expectations before the review period, record what acceptable work looks like, gather dated examples across the full period, test contradictory evidence and let the employee correct factual errors. An accountable manager then explains the decision and the support or action that follows.

Replace “objective” with a testable standard

A number can be subjective if someone chose the wrong denominator, target or scope. A written behaviour can be reviewable if the expected work, conditions and evidence are clear. The practical goal is to make judgment traceable and consistently applied.

The US Office of Personnel Management advises that performance standards should be objective, measurable, realistic and clearly recorded. Its guidance on developing performance standards separates general measures such as quality, quantity, timeliness and cost effectiveness from the specific evidence used for a role. It also recognises that some work must be observed and verified rather than reduced to a number.

UK guidance reaches a similar practical point. Acas performance-management guidance says objectives should be fair, reflect the employee's usual tasks and workload, and be specific, measurable, achievable, relevant and time-bound.

Neither source supplies a universal scorecard. Build criteria around the actual role and the decision the review informs.

Copy this criteria and evidence worksheet

Use one row for each material responsibility. Avoid one broad row such as “leadership” or “communication.”

The worksheet should sit beside the organisation's policy, not replace it. Performance evidence may affect pay, promotion, support or formal employment processes. Apply the rules and review routes that govern the actual decision.

Write criteria that match the role

Start with the work, then decide how it can be verified.

Do not use a team outcome as proof of one person's contribution unless that person had relevant control and the individual contribution is defined. Do not measure style when the criterion is work quality. A polished presentation, rapid typing or constant visibility may be irrelevant to the result.

Match each conclusion to its source

Different sources answer different questions:

• Work output: can show what was produced under stated conditions, but not every contribution or obstacle.
• Operational record: can show volume, quality or timing if definitions are stable, but may omit difficult cases or shared work.
• Manager observation: can add task context, but covers only what the manager saw and remembers.
• Stakeholder feedback: can show how work landed for that stakeholder, but may reflect one relationship or expectation.
• Employee account: can provide goals, constraints, decisions and examples to check, but should not be treated as independent verification of every claim.
• Qualification or training record: can show completion of a requirement, but not current application to a different task.

Record the source date and coverage. A production count for the final month does not represent an entire six-month period. A recent incident should not silently outweigh five contrary examples.

Review evidence in a fair order

Use the same sequence for every employee in the comparison group:

1. Confirm which criteria applied and when they were communicated.
2. Check whether the role, priority, workload or available support changed.
3. Review evidence across the full period, organised by criterion rather than by personality label.
4. Identify missing sources and seek relevant counterexamples; record when none are available.
5. Share factual material with the employee and invite corrections or context.
6. Separate observed work from the manager's interpretation.
7. Apply the documented standard and record the rationale.
8. Route any pay, promotion, development or formal action through its accountable process.
9. Give the employee the review record and available challenge route.

The US Equal Employment Opportunity Commission advises employers to communicate standards, apply them consistently and include relevant factual detail in evaluations. Its performance-evaluation guidance also reminds employers not to impose higher standards or negative evaluations because of protected characteristics. UK employers should consider the applicable Equality Act framework; the Employment Statutory Code of Practice discusses transparent, justifiable criteria, consistent procedures and reasonable adjustments.

Fictional example: a weekly exception file

This example is invented to demonstrate the worksheet.

A distribution coordinator, Alex, is expected to send the weekly stock-exception file by Tuesday noon. The agreed standard requires the current location, item code, issue owner and next review time. The manager's first draft says Alex “often delivers late and needs closer oversight.”

The evidence review finds 12 weekly files in the period:

• nine were complete and sent before Tuesday noon;
• one was sent on time but omitted an owner, then corrected the same afternoon;
• two were sent on Wednesday after the inventory source was unavailable to the whole team;
• a stakeholder says Alex's files make escalations easier, but refers only to the final four weeks;
• Alex provides the outage notice and explains that the backup source had not been approved.

The initial label is not supported as written. The manager revises the record: one preventable completeness error, nine complete and timely files, and two delays linked to a documented dependency outside Alex's control. The human decision is to keep the existing standard, approve a backup data route and review the next six files. No personality trait or overall performance score is inferred from this one criterion.

Use counterexamples before closing the review

A counterexample is evidence that would make the current conclusion narrower, different or unresolved. Ask:

• What work in the period contradicts this label?
• Did the same evidence receive the same interpretation for a comparable role?
• Was the standard changed after the work occurred?
• Did absence, disability, leave, tools or authority affect what could reasonably be delivered?
• Does a team result include work the employee did not control?
• Is the source describing output, behaviour, effort or preference?
• What would the employee need to show to correct a factual error?

Counterexamples do not automatically reverse a decision. They prevent a reviewer from treating the first plausible story as the complete record.

Keep measurement and judgment separate

A KPI can establish that an agreed event occurred. It does not decide the weight that event deserves among other role requirements. Define weighting before results where the process uses it, and do not invent precision by averaging unrelated evidence.

If a criterion cannot be supported with a fair source, mark it unresolved or improve the standard for the next period. Do not fill the gap with an AI-generated score, a sentiment label or an inference about potential. For a practical discussion once the evidence is assembled, use the effective performance conversation guide. For criteria based on demonstrated capability, see the skills gap analysis worksheet.

Where Lontra can help with context

Lontra can prepare a focused employee conversation and a manager brief when a work example, constraint or point of disagreement needs clarification. Managers do not receive raw employee responses. People still verify the relevant source, apply the organisation's performance criteria and own any decision about performance, pay or promotion. Lontra does not create an individual performance score or automate that decision.

The Lontra product overview explains the conversation and manager-preparation workflow. Use it as one source of reviewable context, not as the performance record or a substitute for the organisation's evidence and appeal process.