Performance Scorecards Linked to Review Decisions

A performance score looks objective when it appears as one decimal number. The decision behind it may depend on who chose the measures, whether evidence was complete, and how a manager handled exceptions. We advise Philippine HR teams to evaluate an employee KPI system through one review cycle with a visible policy and an illustrative employee case. Start with role-specific expectations, then follow the evidence, manager assessment, employee response, and any salary recommendation. The system should make a decision explainable; it should not be treated as the final decision-maker.

Define the role before scoring the person

Consider a fictional professional-services team in Laguna. A project coordinator's work may be assessed on on-time deliverables, quality review, and client handoff. A helpdesk analyst needs different measures, even if both report to the same manager. Publish the scorecard template, measurement period, weights, evidence sources, and exception rules before the period starts. Retroactively changing a target because someone scored unexpectedly undermines trust in the whole cycle.

For a simple coordinator example, set on-time deliverables at 40%, quality review at 35%, and handoff completeness at 25%. The weights total 100%. Suppose the approved ratings on a five-point scale are 4, 3, and 5 respectively. The weighted result is 4 × 0.40 + 3 × 0.35 + 5 × 0.25 = 3.90. That calculation is only a check of the arithmetic. It does not prove that a rating of 3 for quality was fair or that a 3.90 result should produce a particular salary action.

Ask the manager to show the evidence behind each rating. “Three deliverables were late” is incomplete if two were delayed by an approved scope change. A quality rating should point to a defined review rubric, not an undocumented impression. A handoff score may require an agreed checklist of files, status notes, and owner acknowledgments. The employee should know which records the reviewer can use and how to contest an incorrect one.

Make the review cycle inspectable

We would give the process five stages: template approval, evidence collection, manager assessment, calibration or second review, and employee acknowledgment with a response path. Record the effective template version. If a metric changes halfway through the period, decide and document whether the old or new rule applies to each segment. Managers need room for context, but a free-text comment should not silently replace the published measure.

Calibration is a conversation between authorized reviewers about consistent application of the rubric. It is not an instruction to force every team into a predetermined score distribution. If one reviewer gives a 5 where another gives a 3 for comparable evidence, ask which criterion they applied differently. Record any approved change and its rationale. For employees who changed roles during the cycle, avoid applying the new role's metrics to work completed in the old role without an agreed transition rule.

Let the employee see the evidence and provide a response before a consequential decision is finalized. A response may correct a missing project record or explain an approved absence. The reviewer should be able to leave the original score, amend it, or escalate the dispute, with the record of what changed. An “acknowledge” button should be defined clearly: receiving a review is not necessarily agreement with every assessment.

Respect the data used for monitoring

Some scorecards pull from attendance, tasks, tickets, or other employee records. The National Privacy Commission's advisory on employee monitoring software says such processing needs a lawful basis and must follow transparency, legitimate purpose, and proportionality. HR should tell staff which sources are used, why, who may see the result, and how inaccuracies are corrected. Collecting every available activity signal because a system can do so is not a useful metric design.

Limit access to the people who need to prepare, review, approve, or respond to the scorecard. Do not expose client names or confidential ticket details to a wider calibration group when a summarized, verified measure will answer the question. Decide how long supporting records and final reviews are retained under the organization's policy and applicable obligations. A performance dashboard is part of the employee data environment, not merely a chart.

Keep a salary recommendation separate

ERPat's module directory describes KPI Matrix scorecards with role-weighted metrics and salary recommendations. Its KPI Matrix guide was updated before this review period and describes the module's scoring approach. These sources support an evaluation of the capability, but do not turn a recommendation into an authorized salary change. Compensation budgets, job level, internal equity, policy, and a designated approver may all affect the final decision.

In a demonstration, ask the presenter to build the 40/35/25 template, attach evidence to the coordinator's ratings, correct one input, and show what happens to the calculated result. Then ask what the salary recommendation displays and who can approve or reject an actual pay decision. The record should distinguish the score, the recommendation, and the approved action with their dates and owners. Do not accept a single “final rating” field as proof of an accountable review workflow.

Our buyer checklist is practical: Can templates differ by role? Are weights and effective dates visible? Can reviewers inspect evidence and corrections? Is employee feedback retained? Can HR compare reviews without exposing unnecessary personal data? Does a rejected salary recommendation leave an explanation? Use your own policy and anonymized cases in the demo. If you want to map the review process to a system, explore our professional-services solutions.