Roles, Not Averages: A 90-Day Plan for Absorbing the Next Wage Uplift

The date is fixed and the direction is settled. Whatever the final figure turns out to be, the next National Living Wage uplift takes effect in April, and every UK employer knows it is coming. That is unusual. Most cost pressures arrive without warning, land on a monthly management account and are absorbed or argued over afterwards. This one is announced, timetabled and entirely foreseeable.

Certainty, though, tends to produce a strange response. Firms either do nothing until February, then apply a flat percentage across the payroll and a similar amount to the price list, or they note the change in a budget they intend to rewrite anyway. Both approaches treat a role-by-role change in cost as a company-wide average, and averages are where margin quietly disappears.

Ninety days is enough time to do this properly. Starting now, in early November, gives you a runway that finishes well before the uplift is paid, with a buffer left over for the decisions that need a conversation rather than a spreadsheet.

Why the headline percentage understates your exposure

The published rate sets a minimum hourly floor. Your actual cost depends on where your people sit relative to that floor, and what happens to everyone standing above it.

Three effects matter. The first is the ripple: staff already paid above the new minimum generally expect their differential to survive, so an uplift at the bottom tends to pull up the band above it, and sometimes the band above that. The second is on-costs: employer National Insurance, pension contributions and any overtime or shift premia calculated as a multiple of base pay all move with the underlying rate. The third is composition. A business with six full-time staff on modest salaries has a very different profile from one running a large part-time or shift-based team at identical headcount, even though both would apply the same headline percentage.

A flat uplift applied to total payroll will approximately capture the direct cost and will misstate everything else.

Days 1 to 30: rebuild the model by role

Begin with the payroll data you already hold and restructure it as a role-level table rather than a single total. For each role, record headcount, contracted hours, current rate, the gap to the new floor, the likely differential adjustment above it, the associated on-costs, and the annualised cost of all three combined.

The purpose is not precision. It is visibility. Two questions usually surface within the first fortnight: which roles carry the largest absolute increase, and which carry the largest increase relative to the revenue they help produce. Those are rarely the same list.

Tag each role to a revenue line or customer segment as you go. This is the step most often skipped, and it is the one that makes the following two months possible, because it converts a single unsettling number into a set of traceable ones. By day 30 you should be able to say not that payroll will rise by a given percentage, but that delivery in one service line will absorb most of the increase while another barely moves.

Days 31 to 60: productivity first, price second

With the cost allocated, the instinct is to reach for the price list. Resist it briefly and look at output per hour instead, because price rises are visible to customers and productivity changes are not.

In practice this means examining rota design against actual demand rather than habit, reducing reliance on overtime that has quietly become structural, simplifying administrative work that exists because it always has, and checking whether the grade mix in a team still matches the work being done. None of these are dramatic. Together they often recover a meaningful share of the uplift, and they cost nothing in customer goodwill.

Price comes next, and selectively. Identify the lines where the price has not moved in two or three years, and the customers who buy on value rather than on a line-by-line comparison. An increase applied where it can be explained is worth more than the same increase applied everywhere and defended nowhere.

Days 61 to 90: decide what can no longer carry the overhead

Some services, contracts and customers only worked because labour was cheaper than it is about to become. The test is straightforward: after the uplift, does this line still cover its fully loaded cost and leave a contribution worth having? If it does not, the options are to reprice it, change how it is delivered, reduce its scope, or stop offering it. Leaving it in place and hoping volume compensates is not one of the options.

The same scrutiny applies to structure. Some roles may be better configured as fewer, better-paid hours rather than more hours at a rate that no longer works. That territory involves contracts and consultation, so take advice before acting; the point here is to identify the candidates early enough that the decision is made calmly rather than in March.

By the end of the ninety days you should hold three things: a role-level cost model, a short list of productivity changes with owners and dates, and a clear view of which work you will no longer subsidise.

The conversation you should not postpone

Two communications matter, and they run in opposite directions.

Internally, staff should not learn about the change from a payslip in April. Explain the timing, what it means for them specifically, and what it means for the business. Ambiguity here is read as reluctance.

Externally, be careful about presenting April price changes as a direct consequence of the wage rise. Customers recognise pass-through pricing and treat it as an opening position. A price change justified by the value delivered survives negotiation better than one justified by your cost base.

A calendar, not a forecast

What ninety days buys is not an accurate prediction of next year's payroll. It is the ability to make a series of small decisions while they are still small. The uplift will arrive whether or not you have modelled it. The only variable is whether it lands as a managed adjustment spread across roles, prices and structures, or as a single line in April that everyone then has to react to at once.