Performance Review Process: A Practical Manager and HR Guide

01Performance review process: design rules people understand before it begins

The review period should not be the first time an employee hears what good work means. Define the process in ordinary language, and make each criterion relevant to responsibilities that were actually assigned.

Start by identifying the decisions the appraisal is meant to support. A development conversation, confirmation discussion and compensation recommendation may require different evidence and approval routes. Do not quietly blend these purposes into a single score. State whether the review informs a particular decision, who can see the record and which authorised person makes that decision. HR should check these details against the organisation’s own policies and applicable advice rather than relying on a generic form.

Set the review dates and covered population. Explain how a new joiner, someone who changed teams, an employee on an extended absence or a manager who leaves mid-cycle will be handled. These are predictable cases; leaving them undefined creates inconsistent exceptions. Assign an owner for each exception and tell employees where to ask questions. A process is easier to trust when people can distinguish a rule from a one-off decision.

Translate broad values into criteria that can be discussed. “Be proactive” is hard to assess consistently unless the role’s expected actions and boundaries are clear. For a customer-facing role, examples might concern follow-up quality or accurate handovers; for an operations role, evidence may instead concern safe, dependable completion of assigned work. Do not use an employee’s visibility, confidence or similarity to a manager as a proxy for contribution.

Rating labels need descriptions. If a scale is used, explain what distinguishes each level and provide role-appropriate examples. Avoid definitions that merely repeat the label. Managers should know whether a rating describes results against goals, demonstrated behaviours, or both. Where a target changed during the period, record the approved change and assess against the updated expectation rather than the obsolete one.

Use Performance Management to discuss the workflow, then verify it against approved criteria. Related conversations may connect to Goals and OKRs and Continuous Feedback; those links do not replace local decisions about purpose, access or policy.

• Publish dates, eligibility and review purpose before launch.
• Give criteria and rating descriptions to employees and managers together.
• Name owners for transfers, new starters and non-standard cases.
• Explain confidentiality, access and the route for factual corrections.

View Full Size

02Build the conversation from examples and employee context

An appraisal is not a verdict delivered at the end of a form. It is a structured discussion in which the manager explains observations, listens to the employee and checks whether the record reflects the work and conditions of the period.

Invite employees to prepare a short reflection before the manager completes a final assessment. Ask what they delivered, which agreed goals moved forward, what changed, and where they need support. Make clear that a self-assessment is input rather than a demand to defend every month of work. Employees may identify contributions the manager did not directly observe, as well as barriers such as a changed priority or delayed dependency.

Managers should collect examples across the whole review period. Recent events can feel disproportionately important, while a visible success may obscure recurring work that kept a team functioning. Use dated notes, completed deliverables, agreed target records and relevant feedback where appropriate. Avoid unsupported character judgments. “The handover omitted the revised delivery date on two occasions” is discussable; “careless” is a label that does not tell the employee what to change.

Separate outcome from circumstance. A target may have been missed because execution fell short, priorities changed, or a dependency was unavailable. Those explanations do not automatically settle the rating, but they matter to a fair assessment and the next plan. Ask what the employee knew at the time, what was within their control and what support was requested. Record material context without turning the form into an exhaustive personal dossier.

Hold the meeting with enough time for questions. Begin with the employee’s account, then discuss strengths, gaps and differences between the two views. Refer to the relevant criterion and example. If either person needs to verify a fact, mark it for follow-up instead of improvising a definitive answer. End by checking that the employee understands the outcome, what remains open and how to submit a correction or response under the employer’s process.

Illustrative Pakistani example: A Lahore-based distribution business asks a depot coordinator to review the quarter. The dispatch completion target was revised after a route change, but the manager’s draft still uses the original target. The employee shows the dated revised instruction and notes that two delays followed a supplier hold. The manager checks the instruction with operations, updates the target reference, and separates that delay from an independently documented handover issue. This is an illustrative scenario, not a claim about a particular employer or a universal Pakistani practice.

The example shows why employee response is operationally useful: it can uncover an outdated criterion before the record closes. It does not mean every explanation must be accepted untested. The manager verifies relevant details, explains any remaining disagreement and records the basis of the conclusion. HR can facilitate where the relationship makes an open discussion difficult.

• Ask employees for examples, changed responsibilities and support needs.
• Tie manager observations to a criterion and a review-period event.
• Check target revisions and material dependencies before finalising.
• Record unresolved differences and give them a named reviewer and due date.

A self-appraisal should not become a contest in writing skill. Provide prompts and explain that concise evidence is welcome. Managers remain responsible for their own assessment and should not copy employee wording as if independently verified. See Employee Self-Service and Employee Profiles as related operational topics.

View Full Size

03Check consistency, approve the record and follow through

A review is complete when an authorised person has checked the record and the employee knows what happens next. Consistency means applying the same reasoning standard, not pretending different jobs produce identical evidence.

Before closure, ask managers to confirm that every rating has an explanation and that the evidence belongs to the stated period. HR can look for missing reviews, unexplained changes, identical comments across employees and patterns that deserve closer examination. A pattern is a prompt for inquiry, not proof of unfairness. Ask whether managers had comparable expectations, whether work opportunities differed and whether relevant context was captured.

Calibration meetings can help leaders compare how criteria are understood. Keep discussion anchored in role expectations and examples. Do not force a predetermined spread of ratings across a small or mixed group: a neat distribution does not establish that individual judgments are sound. Where leaders disagree, document the point, evidence considered and authority to resolve it. Avoid changing a rating merely to make a chart look balanced.

Use a clear approval route. The manager submits a completed assessment; a designated approver checks completeness and returns queries where evidence or explanation is missing; the responsible authority confirms closure. Tell employees whether they can add a comment and how to raise an error. If a separate review or grievance route exists, refer to the actual policy and contact rather than promising an informal process that may not exist.

Keep the record proportionate. Include criteria, relevant examples, material employee context, final rationale, approval and agreed actions. Restrict access to people with an appropriate role. Do not use an appraisal record as a catch-all for unrelated sensitive information. Follow the employer’s retention and access practices and obtain appropriate advice where requirements are unclear.

Translate the meeting into a small number of observable next steps. An action says what will change, who will provide support, when progress will be discussed and what evidence will show movement. “Improve communication” is too vague on its own. A practical agreement might be that manager and employee review a sample of customer handovers at their next scheduled check-in. Development should not be framed as a promise of promotion unless an authorised decision-maker has approved it.

Finally, review the cycle as a process. Ask employees and managers which instructions were unclear, which questions did not fit the work and where approvals stalled. Compare completion status and exception categories; do not invent a performance benchmark from a single cycle. Make a change log for the next cycle, name its owner and communicate revised guidance before reviews open again.

• Check evidence and explanations before approving a review.
• Use calibration to test reasoning, never impose automatic ranking.
• Keep a route for corrections and documented disagreement.
• Assign each development action to a person and follow-up date.
• Use cycle feedback to improve instructions, not claim unsupported impact.

PayPeople describes appraisal cycles, self-appraisal, weighted goals, KRAs and competencies, and an approval chain for submitted ratings. Whether a workflow suits your organisation depends on agreed practices and configuration. Review Performance Management with HR and operational owners, then verify relevant steps in a demonstration.

View Full Size

Summary

A useful appraisal process brings expectations, evidence, employee context and accountable decisions into one understandable cycle. Make the rules visible before reviews begin, allow questions while they can still be checked, and close with actions that have owners. Then use what employees and managers learned to improve the next cycle without treating a score as the whole story.

Next step: see how this works in PayPeople Performance Management.