Which decisions should the success score feed, and how? Build a fair, transparent and defensible framework for tying pay rises, rewards, promotion and training to performance data.
When a performance review ends, most organisations face the same question: "So what do we do with these results?" If results feed no decision, employees see the review as a formality. If a single score is applied mechanically to every decision, the process feels unfair and reviews turn into negotiations. The right approach is to make performance data an input to decisions, without letting it replace the decision entirely.
This article looks at how performance results can be tied to pay rises, rewards, promotion and training, which data should come first for each type of decision, and how to keep the process transparent.
First, make sure the data can be trusted
If the score behind a decision is itself disputed, so is the decision. Before tying results to decisions, check three conditions:
- More than one perspective: Does the score rest on one manager's view, or do different raters contribute?
- Measurable components: Does the result include target actuals tracked through the period, not just impressions?
- Consistency: Are different managers' scoring tendencies close to each other?
In HibritİK Performance Management, evaluation rests on three pillars: scoring of department responsibilities, a competency evaluation with managers, direct reports and peers, and targets for which employees enter monthly actuals. These three results merge into a single success score using weights you set. For consistency across managers, see our performance calibration guide.
Different decisions need different data
The success score gives an overall summary, but different decisions call for looking at different layers of it:
| Decision | Data to emphasise | Key question |
|---|---|---|
| Pay rise and reward | Success score, target actuals | How much did they contribute this period? |
| Promotion | Competency results, trend across periods | Are they ready for the next role? |
| Training and development | Low-scoring competencies, gaps in responsibility scores | Which skills need support? |
Pay rise and reward decisions
Pay and reward decisions recognise contribution over the past period, so the period's success score and target actuals are the most meaningful data here. Even so, working with bands is more defensible than converting the score straight into a percentage:
- Divide success score ranges into a few performance bands.
- Set a rise or reward range for each band within the budget.
- Let the manager make the final decision within the band, with a reason.
- Put the bands and ranges in writing at the start of the period.
HibritİK's award eligibility report draws on the success score to show which employees meet the reward criteria, and the department report provides a basis for comparing units. All reports export to Excel, so they move easily into the sheets you use for pay reviews. One important note: HibritİK does not calculate payroll. Pay rises are processed in your own payroll process; employees can view the salary slips HR enters on their own screens.
Watch the weight of targets
Target actuals are a strong signal for pay decisions, but one exceptional result can dominate the whole picture. In HibritİK you can optionally cap the achievement rate at 100%. If a sales target is multiplied by one unexpected large order, for example, this setting stops weaknesses in other targets from disappearing from view.
Promotion decisions
Promotion is not a reward for past success; it is a judgement of readiness for a future role. A specialist who excels in their current role may not show the same success as a manager. Looking only at the success score can therefore mislead.
What should come first in a promotion review:
- Competencies of the target role: in HibritİK, competencies such as leadership can be applied only to managerial positions. For manager candidates, how these are rated by direct reports and peers is the most direct signal.
- Trend across periods: steady development across archived periods is a more reliable sign than one good period.
- Multiple views: contributions from managers, direct reports and peers add more than one perspective to the decision.
Keeping a written rationale next to the score makes it easier both to give candidates feedback and to answer questions that may come later.
Training and development decisions
The least contentious and often most productive use of performance data is training planning. The aim here is not ranking but seeing gaps. Even an employee with a high success score may have a competency to develop.
HibritİK's training needs report draws on the competency evaluation and the success score to show which employees need support in which areas. You can use it like this:
- Identify the most common competency gaps across the organisation; these become the topics of shared training programmes.
- Discuss individual gaps with the employee in the review conversation and write a development goal.
- Track the effect of training by looking at the same competency next period.
In the responsibility evaluation, a comment is mandatory when a score of 1 is given. Because these comments show concretely where an employee is struggling, they are a valuable source for defining training needs correctly.
Low performance: a plan, not a penalty
The most sensitive area when tying results to decisions is employees who fall short of expectations. A low success score alone should not justify a sanction; first you need to understand why. Were the targets realistic? Did the employee's responsibilities change during the period? Was enough support and resource provided? Once these questions are answered, prepare a development plan with measurable goals and follow-up dates. The next period's results are the fairest evidence of whether the plan worked.
Transparency: the rules are discussed up front
The most important condition for employees accepting results is that the rules were explained in advance, not afterwards. At the start of the period, share:
- The weights for responsibilities, competencies and targets.
- Which decisions will take results into account, and how heavily.
- The general framework of bands and reward criteria.
- How to raise an objection or comment on results.
In HibritİK, evaluation periods are prepared as drafts, started and archived, and past results keep their own rules. That means you can always answer "which rules did we use last year?". For period design, see our article on managing performance periods.
Common mistakes
- Applying the success score mechanically and identically to every decision.
- Promoting purely on success in the current role.
- Collecting training needs data and never turning it into a plan.
- Setting bands and criteria after results are announced.
- Not recording the rationale for decisions.
Data-driven decisions with HibritİK
HibritİK combines responsibility, competency and target results into a weighted success score; the department report, award eligibility report and training needs report draw on it and export to Excel. To try your own evaluation setup, start a 14-day free trial or see the pricing page.