Pay in professional services

Linking performance ratings to bonus: a fair, explainable model for professional-services firms

Frederic C. Rupprecht · Updated 16 October 2026 · 12 min read

In short

Link ratings to bonus through a rule you publish in advance. One explainable form: target bonus for the level band × an individual factor from the normalised, calibrated score × a firm factor, scaled to the bonus pool and capped. Normalise before you pay, because ratings tend to grow more lenient once money depends on them. Be open about criteria and the calculation, not about rankings. Check outcomes for bias, and have a named person approve every payout.

Key takeaways

  • A traceable bonus model separates three decisions: the pool size, the performance rating, and the rule that turns a rating into an amount.
  • Once ratings decide money, they tend to become more lenient, and in one experiment less informative; a fixed budget, calibration and normalisation push back.
  • In a study of pay rises, the amount explained more of the satisfaction with the pay, the process more of the trust in supervisors and commitment to the organisation.
  • Be open about criteria and the calculation, not rankings: in one firm, a bonus below the reference point did less harm when people did not learn their standing against it.
  • Rating-based bonuses are not automatically free of bias; check whether equal scores lead to equal amounts across groups.
  • Keep development feedback such as a 360° out of the bonus calculation; in Germany, a works council, where there is one, co-determines the principles of pay.

How consultancies structure bonuses: target, individual factor, firm factor

Linking performance ratings to bonus means making three decisions that are easily blurred: how much money is distributed, how well each person performed, and which rule turns a rating into an amount. Separate the three and justify each, and you can explain any bonus afterwards, to the person and to any works council.

Definition

Performance-related bonus A form of performance-related pay: variable pay whose amount depends, by a rule set in advance, on a person’s appraised performance. It can be combined with the firm’s results and is limited by a budget, the bonus pool. Unlike a bonus tied to agreed targets, it rests on a judgement of performance, not only on whether pre-set metrics were hit.

The model: bonus = base salary × target bonus % for the level band × individual factor × firm factor, then scaled to the bonus pool and capped. We give no market percentages: the consulting figures circulating online come, as far as we found, from forums and job-seeker sites and are undocumented.

The components of a bonus model and what to watch in each (illustration without market values; LEADBeyond practice recommendation, not a measurement instrument).
ComponentWhat it capturesWhere the value comes fromWhat to watch
Target bonus per level bandVariable pay at expected performanceThe firm’s pay policyPublish the bands in advance
Individual factor (multiplier)Performance against the agreed standardNormalised, calibrated score via a conversion tableNever one project lead’s raw rating
Firm factor (multiplier)Results of the firm or unitThe year’s results against planExplain why everyone carries the same factor
Bonus poolTotal budget to distributeDecision by the firm’s leadershipFix it before anyone rates
Cap and floorRange upwards and downwardsThe bonus ruleLimit outliers, keep real differences

Fair process and fair outcomes: what justice research says

Fairness is about more than size. In a study of 217 employees, distributive justice explained more of the satisfaction with a pay rise. Procedural justice explained more of the trust in the supervisor and commitment to the organisation (Folger and Konovsky, 1989). From this we derive a checklist for the process (practice recommendation, not a research finding).

  • Criteria known in advance. Criteria, rating steps and the conversion into bonus are fixed before the year starts.
  • The person has a voice. Self-assessment and their own evidence come in before the rating is final.
  • The decision is explained. Everyone learns, in conversation, how their bonus was put together.
  • A route to challenge. With a deadline, and with someone who did not do the rating.
  • Consistent standards. The same rule for every project lead, team and office.

Pay pressure inflates ratings, and what counters it

When money depends on a rating, the rating tends to get more generous. A meta-analysis of 22 studies found ratings for pay or promotion on average about one-third of a standard deviation more lenient than ratings for research or development. The gap to research ratings was larger in the field and among practising managers (Jawahar and Williams, 1997). An online experiment confirms the effect under controlled conditions: when ratings determined bonuses, they became more lenient and less informative (Kusterer and Sliwka, 2025). Five levers push back:

  1. A fixed budget. Set the bonus pool before anyone rates; without a fixed budget, ratings are typically found to be too generous (Sliwka, 2020).
  2. Better information. Behavioural anchors per rating step and evidence from several projects; in the experiment, more detailed information made ratings more informative.
  3. Accuracy as part of the job. Project leads are also assessed on how carefully they rate; in the experiment, rewarding accuracy reduced leniency.
  4. Calibrate. A calibration meeting aligns standards before any money moves.
  5. Normalise. Statistical methods remove the leniency and severity of individual raters, provided raters can be compared through people they rated in common. A bias all raters share stays invisible.

From normalised scores to bonus: pools, caps and differentiation

Fix the route from score to amount so that equal final scores in the same level band get the same factor, whoever rated them. We recommend five steps in a fixed order (practice recommendation, not a research finding):

  1. Normalise. Correct raw ratings for rater effects and combine them per person across projects.
  2. Calibrate. Review the scores in the meeting and record every change with its reason.
  3. Convert. Translate the final score through the published table into a few clearly described steps. An example with arbitrary figures: exceptional 1.5; clearly above expectations 1.2; meets 1.0; partly meets 0.5; does not meet 0.
  4. Scale and cap. Scale all calculated bonuses together to the pool, then apply cap and floor.
  5. Check and approve. Check results across groups; a named person approves and can deviate with a stated reason.

How far you differentiate is a deliberate choice. In panel data from several banks, stronger differentiation in subjective evaluations went with higher subsequent bonus payments. The link tended to be stronger for wider spans of control and at higher levels, and reversed at the lowest levels. In the authors’ model, it can also reverse where cooperation matters (Kampkötter and Sliwka, 2018). For close-knit consulting teams, we read this as a case for noticeable, not extreme, gaps.

Transparency without league tables

Openness about relative position can have a cost. In data from a large multinational, a bonus that fell behind a natural reference standard for a fair bonus reduced managers’ satisfaction and later performance. The effects were weaker when people were not told their standing relative to that standard (Ockenfels, Sliwka and Werner, 2015).

The firm’s managers in Germany learned their bonus percentage against an average of 100%; in the US, only the amount. In Germany, those below 100% were significantly less satisfied, while those above were barely more so (Sliwka, 2020). We read this as separation, not secrecy: publish criteria and the calculation, not each person’s position against colleagues.

A clean score alone does not prevent bias in pay. In three experiments with 445 participants with managerial experience, a man received a larger bonus than an equally qualified woman when the organisation was explicitly presented as meritocratic (Castilla and Benard, 2010). In reward decisions for almost 9,000 employees of a large company, women, ethnic minorities and non-US-born staff received lower rewards at equal evaluation scores. Accountability and transparency in pay decisions narrowed the gap (Castilla, 2015).

  • Publish: criteria, rating-step descriptions, level bands, the conversion table and how the pool is set.
  • Explain: each person’s own calculation, in conversation.
  • Do not publish: league tables, percentages relative to others, names from the calibration matrix.
  • Check: whether equal final scores lead to equal amounts across groups, for example by gender, part-time status or office.

Keep development feedback out of pay

A bonus needs an appraisal, not development feedback. Toegel and Conger argue that a 360° used for conflicting purposes risks losing its value as honest feedback, and propose separate instruments: more qualitative for development, quantitative for appraisal (Toegel and Conger, 2003). In a field study, direct reports’ ratings were of better quality when made for development than for administrative use; this did not hold for peers (Greguras et al., 2003).

Development feedback and performance appraisal for bonus compared (LEADBeyond practice recommendation, not a measurement instrument).
FeatureDevelopment feedback, e.g. 360°Performance appraisal for bonus
PurposeLearning, changing behaviourRating and rewarding performance
Feedback fromSelf, supervisors, peers, direct reportsProject leads and supervisors responsible for the work
Who sees the resultThe person and, if agreed, a coachThe person, raters, calibration meeting, approver
ConsequenceDevelopment goalsFinal rating, promotion, bonus

LEADBeyond 360° is built for leadership development and is never used for pay, promotion or selection. Why access to development feedback matters for its honesty is covered in Can HR see individual 360° feedback results?

EU and German rules: GDPR, Pay Transparency Directive, works councils

This section covers the EU and Germany, not the UK. The first two points apply wherever you employ staff in the EU; the rest are German law. Points to check:

  • Art. 22 GDPR. A bonus paid without human review can be “a decision based solely on automated processing” with significant effect. Build in a person who can intervene, an explanation and a route to contest. Whether the software is a high-risk AI system under the AI Act (Annex III, point 4(b)) is a separate check.
  • Directive (EU) 2023/970. “Pay” includes variable components; Recital 21 names bonuses. Under the Directive, pay criteria must be easily accessible, “objective and gender neutral” (Art. 6). Art. 7 provides for information on pay levels by sex. Transposition was due by 7 June 2026; a German government answer of 8 July 2026 (BT-Drs. 21/7026) said the legislative procedure had yet to begin. Until transposition, Germany’s Pay Transparency Act of 2017 applies. Check the current status.
  • § 87(1) no. 10 and § 94(2) BetrVG (Germany). The works council co-determines the principles of pay. In our reading, that includes a rule that turns ratings into bonuses (whether no. 11 also applies needs checking), and the rating criteria are general appraisal principles that need its consent. Works councils do not necessarily hold appraisal back: in German panel data they went with more use of bonus-relevant appraisal (Grund, Sliwka and Titz, 2020).
  • § 82(2) BetrVG and § 315 BGB (Germany). Employees can ask for the calculation and make-up of their pay to be explained, and a bonus set at the employer’s discretion binds only if it is fair.

How ValueScore supports the step from rating to bonus

ValueScore is LEADBeyond’s appraisal platform for consultancies and professional-services firms. A cross-project view shows how several project leads rated the same person, and leniency and severity are detected statistically and removed. The calibration meeting fits on one page, and final rating, promotion and bonus are derived from normalised scores. We recommend fixing the bonus pool and the conversion rule in advance and having a named person decide.

Frequently asked questions

How do you calculate a bonus from performance ratings?

With a rule fixed before the rating year, for example: base salary × target bonus % for the level band × individual factor × firm factor. The individual factor comes from the normalised, calibrated score via a conversion table, not from one project lead’s raw rating. Amounts are then scaled to the pool and capped; a named person approves.

What is a bonus multiplier?

A factor that scales a target bonus up or down. In the model described here there are two: an individual multiplier from the calibrated score and a firm multiplier from results. Publish the individual multipliers in a conversion table or bonus matrix, rating steps against level bands, so everyone can see which rating leads to which factor.

How are bonuses structured in consulting firms?

Descriptions on careers and job-seeker sites mostly name two drivers: individual performance and the firm’s results. Because several project leads often rate one person, aligning their standards in a calibration meeting matters. We found no reliable figures on consulting bonus levels.

How does a bonus pool work?

It is the year’s total bonus budget, set by the firm’s leadership, for example from results. Individual bonuses are calculated by the rule and scaled so their sum fits the pool. Fix the pool before ratings are made: without a fixed budget, ratings are typically found to be too generous (Sliwka, 2020).

Should performance and pay conversations be separate?

We recommend it: once money hangs on a development conversation, it can turn tactical. Ratings made for pay are on average more lenient (Jawahar and Williams, 1997), and conflicting purposes can undermine candid feedback (Toegel and Conger, 2003). Hold the bonus conversation with the calculation and the development conversation with observations, at different times.

How do you stop rating inflation when bonuses depend on ratings?

You cannot stop it entirely, but you can contain it. Fix the bonus pool before rating, use behavioural anchors per rating step, hold a calibration meeting and use statistical normalisation that removes the leniency and severity of individual raters.

How do you make a bonus scheme fair and transparent?

Publish criteria, level bands and the conversion table in advance, explain each calculation, offer a route to challenge and apply one rule to everyone. Keep rankings private, and check before approval whether equal scores lead to equal amounts across groups (Castilla, 2015).

Can an algorithm decide bonuses under GDPR?

Only within narrow limits. Article 22 GDPR gives people the right not to be subject to “a decision based solely on automated processing” with legal or similarly significant effects. Where the decision is necessary for performing a contract or rests on explicit consent (Article 22(2)(a) and (c)), Article 22(3) requires at least the right to obtain human intervention, to express one’s point of view and to contest the decision. Our recommendation: software calculates and proposes; a named person decides. Not legal advice.

Sources

  1. Folger, R., & Konovsky, M. A. (1989). Effects of procedural and distributive justice on reactions to pay raise decisions. Academy of Management Journal, 32(1), 115–130., Academy of Management (1989). Peer-reviewed field study of 217 employees. Cited for distributive justice explaining more of satisfaction with the pay rise and procedural justice more of trust in the supervisor and organisational commitment. It studies pay rises, not bonuses, and no consulting sample.
  2. Jawahar, I. M., & Williams, C. R. (1997). Where all the children are above average: The performance appraisal purpose effect. Personnel Psychology, 50(4), 905–925., Wiley (1997). Peer-reviewed meta-analysis of 22 studies. Cited for administrative ratings being on average about one-third of a standard deviation more lenient, with larger effects in the field. Not cited for any fixed inflation figure for a given firm.
  3. Kusterer, D. J., & Sliwka, D. (2025). Social preferences and the informativeness of subjective performance evaluations. Management Science, 71(5), 4028–4048., INFORMS (2025). Peer-reviewed online experiment. Cited for the abstract’s findings: more lenient, less informative ratings when they determine bonuses; less leniency when accuracy is rewarded; more informative ratings with more detailed information. No field effect size taken from it.
  4. Sliwka, D. (2020). Bonuses and performance evaluations. IZA World of Labor, 478., IZA Institute of Labor Economics (2020). Review article, read in full. Cited for the typical claim that ratings are more generous without a fixed budget, and for its account of the Ockenfels, Sliwka and Werner study (bonus percentages disclosed in Germany, only amounts in the US). Not cited for any recommended distribution.
  5. Ockenfels, A., Sliwka, D., & Werner, P. (2015). Bonus payments and reference point violations. Management Science, 61(7), 1496–1513., INFORMS (2015). Peer-reviewed study using data from a multinational firm, plus a laboratory experiment. Cited for the effects of falling behind a reference point and their mitigation when standing relative to the reference point is withheld. Not cited for “more transparency is always better”.
  6. Kampkötter, P., & Sliwka, D. (2018). More dispersion, higher bonuses? On differentiation in subjective performance evaluations. Journal of Labor Economics, 36(2), 511–549., University of Chicago Press (2018). Peer-reviewed study with a formal model and panel data from several banks. Cited for the abstract’s findings on differentiation, hierarchy levels and the reversal at the lowest levels. No consulting data; not an argument for forced distribution.
  7. Castilla, E. J., & Benard, S. (2010). The paradox of meritocracy in organizations. Administrative Science Quarterly, 55(4), 543–576., SAGE (2010). Peer-reviewed study with three experiments (445 participants with managerial experience). Cited for the abstract’s finding of larger bonuses for men when the organisation was presented as meritocratic. Says nothing about prevalence in the field.
  8. Castilla, E. J. (2015). Accounting for the gap: A firm study manipulating organizational accountability and transparency in pay decisions. Organization Science, 26(2), 311–333., INFORMS (2015). Peer-reviewed longitudinal study of reward decisions for almost 9,000 employees of a large US company. Cited for the reward gap at equal evaluation scores and its reduction after accountability and transparency procedures. No German data.
  9. Toegel, G., & Conger, J. A. (2003). 360-degree assessment: Time for reinvention. Academy of Management Learning & Education, 2(3), 297–311., Academy of Management (2003). Peer-reviewed conceptual article without its own data. Cited for the argument that conflicting purposes can undermine candid feedback and for proposing separate instruments. No figures taken from it.
  10. Greguras, G. J., Robie, C., Schleicher, D. J., & Goff, M., III. (2003). A field study of the effects of rating purpose on the quality of multisource ratings. Personnel Psychology, 56(1), 1–21., Wiley (2003). Peer-reviewed field study. Cited for direct-report ratings being of better quality for development than for administrative use, which did not hold for peers. Not cited for “all 360° ratings degrade when pay is attached”.
  11. Grund, C., Sliwka, D., & Titz, K. (2020). Works councils and performance appraisals. Journal of Participation and Employee Ownership, 3(1), 29–50., Emerald (2020). Peer-reviewed study using German panel data (Linked Personnel Panel and SOEP). Cited for works councils going with more use of performance appraisal, particularly bonus-relevant appraisal. No legal conclusions drawn from it.

See ValueScore in 30 minutes

We walk you through an example with synthetic data, showing how appraisal, calibration and bonus come together in one flow, and tell you honestly whether it fits your firm.

Book a demo