Collect Performance Review Evidence Without Surprises

Agree expectations at the start

Write the expectations for the review period in observable terms. Each expectation should name the work, the standard, the evidence source, and the review owner. A statement such as handles tickets well is too broad. A statement such as closes assigned tickets within the agreed service window and records the resolution code is reviewable.

Share the expectations with the employee at the start and record that they were discussed. If the work changes during the period, update the expectations and note the effective date. Reviewing someone against a standard they never saw is not a fair test, even when the standard is reasonable.

Keep the role plan in one place and link each expectation to the evidence source. A plan spread across a job description, a chat message, and a slide is hard to apply consistently.

Log examples as they happen

Create a simple evidence log with the date, expectation, example, source link, and the person who observed it. Add both positive and corrective examples. A file with only problems is not a balanced record, and a file with only praise does not help the employee improve.

Keep the log short. One or two strong examples per expectation are more useful than a folder of screenshots. The purpose is to support a conversation, not to build a case. Delete duplicates and low value notes at the review, subject to the retention rule.

Separate observation from rating

The log records what happened. The rating is a judgment made by the manager under the approved process. Keep them in separate fields so a later reader can see the evidence without assuming the conclusion. This also lets the manager change a rating after calibration without rewriting the facts.

If the support lane prepares a summary, label it as a summary and keep it descriptive. Do not use words such as exceeds or below expectations unless the manager has assigned that rating and recorded the reason. The lane can organize the file, but it should not grade the person.

When a summary is prepared by support, have the manager review it before it enters the file. The manager owns the judgment, and the review catches language that sounds like a rating.

Give the employee the file

Share the evidence before the review meeting so the employee can read it and prepare a response. Record the share date and the channel. If the file contains sensitive information about other people, redact it before sharing and note the redaction.

A review that reveals new examples in the meeting creates defensiveness and weakens trust. The conversation is more useful when both people have the same record. If a new example appears late, add it with its date and source, then give the employee time to respond.

Use the same share method for every employee in the same role so the process does not depend on who the manager is.

Run calibration with evidence

Calibration compares ratings across managers using the evidence and the agreed standards. Bring a small sample of files, not just the scores. Discuss where the same evidence produced different ratings and record the reasoning that resolved the difference.

Calibration should not pressure a manager to match a distribution. Its purpose is consistency in applying the standard. Record the participants, the sample, the decisions, and any change to a rating with the reason.

If calibration cannot reach agreement, record the disagreement and route it to the review owner rather than forcing a score.

Handle disagreement and correction

The employee may disagree with a fact or a rating. Record the disagreement, the evidence they provide, and the response. If a fact is wrong, correct the log and note the correction. If the disagreement is about judgment, the manager records the rationale and the employee response stays with the file.

Do not remove a legitimate disagreement to make the file look clean. A record that shows a considered response is stronger than one that shows no conflict. Route any question about employment consequences to the authorized owner and qualified adviser.

If a factual correction changes a rating, record the old rating, the new rating, and the reason. Do not overwrite the original without a trace.

Protect private and sensitive notes

Review files can contain health, family, performance, or conduct information. Restrict access to the manager, the reviewer, and the roles that need it. Do not keep the file in a shared team folder or a chat channel.

Set a retention period and a deletion owner. Remove drafts and duplicate copies after the final file is approved. A private note that is not needed for the decision should not be kept just in case, because it can create risk without improving the review.

Close the cycle with a short record

Close with the final expectations, the evidence summary, the rating and rationale, the employee response, and the next period goals. Keep it short enough that both people can use it. Record the date of the conversation and the owner of the next check in.

Review the process itself after the cycle: files shared on time, evidence coverage per expectation, calibration completion, and open disagreements. Use counts and a denominator. The next cycle should fix one or two process problems, not add another form.

Keep the final file and delete the working notes that are no longer needed. A clean final record is easier to defend than a folder with six versions of the same conversation.