THE NEW DYNAMICS BLOG

Employee incentive programme: designing variable pay that survives contact

How to design an employee incentive programme: what an incentive promises, the measurement traps, eligibility and leavers, and the UK tax and holiday pay duties to check.

Published Updated 14 min read

TL;DR

  • An incentive promises something in advance for hitting a defined outcome. That promise is the whole design problem, because once it is made, people will work to the measure rather than to the intent behind it.
  • Every volume measure needs a quality safeguard beside it. Tie reward to injury numbers and you will get better numbers, not a safer site, because people stop reporting.
  • In the UK a cash bonus is earnings: it goes through PAYE and Class 1 National Insurance, a regularly paid amount can affect holiday pay, and salary sacrifice must not take pay below the National Minimum Wage.

Most articles about an employee incentive programme are a list of ideas. The ideas are the easy part. The hard part is that an incentive is a promise made in advance, and people will keep their side of it exactly as you wrote it, not as you meant it.

This post covers what an incentive actually is, how measurement goes wrong, how to design a scheme that survives contact with real people, and the UK tax and pay duties that most articles leave out.

If the outcome you want to pay for is not written down anywhere yet, start there. New Dynamics goals and OKRs is where the goal, the measure and the evidence behind it live, which is what any incentive has to point at.

What an incentive is, and what it is not

Three things get mixed together, and they behave differently.

Base pay is what you pay someone for holding the job and doing it to standard. It is not conditional on an outcome. It is reviewed, not earned each period.

Recognition is after the fact. Someone did something good, you noticed, you said so. There is no promise beforehand and no entitlement. That is its strength: you can recognise anything you value, including the quiet work that no measure captures. Our companion post on reward and recognition programme design covers that side properly.

An incentive is before the fact. You say: if this defined thing happens by this date, you will receive this. It is also called an incentive program, a bonus program or performance based pay, and the mechanism is the same in each case. The payment is variable, the condition is published, and the person can calculate what they stand to gain.

That forward promise is the entire design problem. Recognition can be loose, because nobody planned their quarter around it. An incentive cannot be loose, because people will plan their quarter around it, and any gap between what you measured and what you wanted is a gap they will find.

The measurement problem, head on

An incentive does not make people work harder in general. It makes them work on the measure. If the measure is a good proxy for the outcome, that is useful. If it is a partial proxy, the parts it leaves out get quietly dropped.

Volume targets that damage quality

Pay a service team per ticket closed and tickets close faster. Some of them close because the problem was solved. Others close because the customer stopped replying, or because a complicated case was split into three simple ones, or because the fix was good enough to shut the ticket and not good enough to stop it reopening next month. The count goes up either way. You find out which it was from the reopen rate and the complaints, both of which arrive later than the bonus does.

The same pattern runs through sales units sold without regard to margin or churn, through recruitment roles filled without regard to how many of those hires are still there a year later, and through billable hours in professional services.

Individual targets that break collaboration

Give eight people an individual target each and you have told them, in the only language that carries weight, that helping a colleague is unpaid work. The senior person who would have spent a morning unblocking someone else now has a reason not to. Information that used to move freely becomes something to hold. Nobody is behaving badly. They are behaving exactly as the scheme asked.

This is the most common failure in interdependent work, because it is invisible while it happens. The individual numbers look fine. What degrades is the thing between the numbers.

Safety-linked bonuses that suppress reporting

This is the clearest case, and it is why our energy sector material advises against it. Tie an individual bonus to injury rates and you will get better injury rates. You will not get a safer site, because the cheapest way to improve the number is not to report.

HSE makes the underlying point about blame and reporting systems plainly: "Employers should not use accident reports to blame people as this may discourage employees from using it" (HSE, workplace transport: co-operation). A bonus that disappears when an incident is recorded is a financial version of the same mistake. The near miss that nobody wrote down is the one that happens again.

Where safety has to feature in reward, the measurable things are behaviours and leading activity: the quality of a risk assessment, stopping a job that looks wrong, closing out audit actions, the number of near misses reported. Reporting is the behaviour you want more of, so it belongs on the positive side of the measure, not the negative.

Three measurement traps in an incentive programme: volume targets that damage quality, individual targets that break collaboration, and safety-linked bonuses that suppress incident reporting.
Each trap improves the number and damages the outcome behind it.

Designing an incentive programme that survives contact

Six decisions. Make them before you announce anything, because every one of them will otherwise be made for you by whoever asks the first awkward question.

A small number of measures. Two or three. Four at the outside. People cannot optimise for six things at once, so what they do with six measures is pick the two that are easiest to move and ignore the rest. You have then designed a scheme you did not intend.

A quality safeguard beside every volume measure. This is the single change that fixes most schemes. Do not pay for tickets closed; pay for tickets closed where the reopen rate stays under a stated level. Do not pay for units sold; pay for units sold that are still with the customer after a set period. The safeguard can be a gate, where nothing pays out unless the quality condition holds, or a modifier that scales the payment. A gate is blunter and easier to explain.

A defined period. Say when the window opens and closes, and when payment follows. A scheme with no stated period becomes an argument about whether something counted.

Clear eligibility. Which roles are in, which are out, and the reason. If the reason cannot be said out loud to the people who are out, it is not a reason.

What happens to leavers and joiners mid period. This is the clause everyone omits and everyone later needs. Decide whether a joiner earns a pro rata share from their start date, and whether a leaver keeps anything. Decide separately for a resignation, a dismissal and a redundancy, because treating all three the same is what produces the grievance. Then write it into the scheme rules rather than deciding case by case.

Who can exercise discretion, and over what. Some discretion is necessary, because no scheme anticipates everything. Name the person who holds it, say what they may adjust, and require the reason to be recorded. Unbounded discretion is the problem, not discretion.

Five steps to design an employee incentive programme: a few measures, a quality safeguard beside every volume measure, a defined period, clear eligibility including leavers and joiners, and named discretion with recorded reasons.
Settle all five before the period opens, or they get settled for you.

Tax and pay duties in the UK

This section is general information about the position in the United Kingdom, not tax or legal advice. Check your own scheme with your payroll provider and, where the amounts are material, with an adviser.

A cash bonus is earnings. HMRC guidance on bonus payments is direct about this. The bonus you have paid counts as earnings, so you "add it to your employee's other earnings" and "deduct and pay Pay As You Earn (PAYE) tax and Class 1 National Insurance through payroll" (GOV.UK, expenses and benefits: bonuses). Non-cash incentive rewards for employees, such as vouchers or goods, have their own treatment and are not automatically tax free.

It can affect holiday pay. GOV.UK states that the normal rate of pay "includes commission, regular overtime payments, and any payments related to length of service or professional qualifications. It does not usually include bonus payments" (GOV.UK, holiday pay). The word doing the work there is "usually". Acas lists, among the payments that must be included, "other payments, for example overtime payments, if a worker has regularly been paid these during the last year" (Acas, calculating holiday pay). So a one-off exceptional bonus is one thing; a quarterly payment that everyone has received every quarter for a year is regular pay by another name, and your holiday pay calculation needs to reflect that.

Sacrifice and deductions must not breach the minimum wage. If people can give up a bonus for a pension contribution, or if the scheme involves any deduction, the floor still applies. HMRC is explicit: "A salary sacrifice arrangement must not reduce an employee's cash earnings below the National Minimum Wage (NMW) rates", and employers "must put procedures in place to cap salary sacrifice deduction and ensure NMW rates are maintained" (GOV.UK, salary sacrifice for employers).

Write the scheme rules so payroll can run them without interpreting them. If the rule needs a conversation every period, it is not a rule.

Fairness, and the equal pay risk

Three failures recur, and all three are design failures rather than bad intent.

Eligibility that quietly excludes people. Part-time staff left out because the target was set at a full-time volume. Shift workers left out because the measure runs on an office week. Support functions left out because their contribution does not appear in any revenue line, even though the scheme depends on them. If the work of the excluded group is what makes the included group's numbers possible, the exclusion will be read as a statement about whose work counts. Pro rata the target to hours before you decide someone cannot qualify.

Discretionary awards that cluster. Where awards are discretionary and unrecorded, they tend to concentrate in the groups closest to the people deciding. Over a few periods that becomes a pay gap with no documented justification behind it, which is exactly the position you do not want to be in if a pay claim or a pay gap review arrives. Our post on pay equity covers the analysis side. The design side is simpler: record the criterion applied to each award at the time, and look at the distribution across the whole population before payment, not after.

Rules published after the fact. An incentive only changes behaviour if people knew the terms while there was still time to act on them. Publishing the rules in advance also removes the most corrosive conversation available to a manager, which is the one where the target is explained once the result is already known.

When not to use an incentive at all

An incentive is a narrow instrument. Three situations where something else works better.

The work is complex and interdependent. Where the result depends on several people, a long cycle and judgement calls, you cannot attribute it cleanly to an individual, and any measure you can attribute will be a fragment of the job. Use a team measure, or do not use an incentive.

Quality matters more than volume. Where a bad output costs more than a missing one, in clinical work, safety-critical engineering, audit, legal advice, paying for throughput pushes in the wrong direction. The safeguard becomes the whole measure, at which point you are better off paying properly and managing the standard directly.

The real problem is an unclear expectation. This is the most common one. Someone is not doing the thing, and a bonus is proposed to make them do it. Before designing a scheme, check whether the expectation was ever stated plainly, whether they have what they need, and whether anyone has told them what good looks like. A conversation and a written goal fix a surprising share of what gets diagnosed as a motivation problem, and they cost nothing to try first.

Incentive ideas that are actually incentives

Most lists of work incentive ideas are recognition ideas wearing a different hat. An idea only belongs in an incentive programme if you can state the outcome, the measure and the payment in advance. These can be:

  • A team bonus on a shared outcome, such as delivering a programme of work within an agreed quality threshold, split evenly so the scheme does not price collaboration out.
  • A referral payment, paid on a defined milestone such as the new joiner passing probation, which builds the quality safeguard into the trigger.
  • A profit share or gainshare on a stated organisational measure, which has the useful property that nobody can move it alone.
  • A retention or completion payment tied to finishing a defined piece of work, which suits project and seasonal patterns better than an annual cycle does.
  • Non-cash incentive rewards, such as extra leave or paid development time, tied to the same kind of defined outcome. Check the tax treatment of each one rather than assuming.

Everything else that people call motivational incentives, the thanks, the awards, the time off for a job well done, is recognition. It is valuable, and it works on a different mechanism, and mixing the two is what produces a scheme nobody trusts.

What a performance system holds, and what it does not

New Dynamics does not run payroll and does not make bonus payments. What it holds is the goal and the evidence behind whether it was met: the measure as it was written at the start of the period, the updates against it, the manager's comments and the completed review. Payroll then pays from a decision that somebody can actually show you, rather than from a figure reconstructed at the end of the period from memory and a spreadsheet.

Frequently asked questions

What is an employee incentive programme?

It is a scheme that promises a defined payment or reward in advance for achieving a defined outcome within a defined period. The promise comes first and the payment follows the result, which is what separates it from recognition, where the gesture follows the behaviour with nothing promised beforehand.

What is the difference between an incentive and recognition?

Timing and entitlement. An incentive is announced before the period and creates an expectation that people can plan around, so the measure has to be precise. Recognition happens after the event, carries no entitlement and can therefore cover anything you value, including work that no measure captures.

How many measures should an incentive programme have?

Two or three, and rarely more than four. People cannot optimise for many things at once, so a long list produces the same behaviour as a short one: they move the two easiest measures and leave the others. Fewer measures with a quality safeguard beside each one beat a longer list.

Are bonuses taxed in the UK?

Yes. HMRC guidance says a cash bonus counts as earnings, so you add it to the employee's other earnings and deduct and pay PAYE tax and Class 1 National Insurance through payroll. Non-cash rewards have separate treatment. This is general information rather than tax advice, so confirm your scheme with your payroll provider.

Does a bonus count towards holiday pay?

It can. GOV.UK says the normal rate of pay does not usually include bonus payments, but Acas requires other payments to be included where a worker has regularly received them during the last year. A genuinely exceptional one-off payment is treated differently from a quarterly payment that everyone has had every quarter.

When should you not use an incentive?

Where the work is complex and interdependent and no individual measure is fair, where a poor output costs more than a missing one, and where the real issue is an expectation nobody stated clearly. In the last case a conversation and a written goal are cheaper, faster and more likely to work than a scheme.

Your next steps: write the rules before you announce the scheme

  1. Write the outcome you want in one sentence, before choosing any measure.
  2. Pick two or three measures, and put a named quality safeguard beside every volume measure.
  3. Write the period, eligibility, the leaver and joiner clauses and the limits of discretion into the scheme rules.
  4. Check the pay duties with payroll: PAYE and National Insurance, the holiday pay effect if the payment is regular, and the minimum wage floor on any sacrifice or deduction.
  5. Pro rata targets to hours, and look at who the eligibility rules leave out.
  6. Publish the rules before the period starts, and keep the evidence against each measure as you go.

For the pay principles, decision rights and review criteria that an incentive scheme has to sit inside, read and download our compensation policy guide. The guide is free to read, and the PDF uses our short download form.

Want the goals, the measures and the evidence behind them in one place, so that a bonus decision rests on a record rather than a recollection? Book a New Dynamics demo and bring the scheme rules you run today. You can also email contact@new-dynamics.com.

Keep the conversation going.

Bring out the best
in your people.

See what performance management could look like for your organisation.

Book a demo