Rolling Out a New Commission Plan: A Change Management Playbook for UK Sales Teams

Most comp post-mortems blame the plan. The accelerator was too steep. The split was wrong. The clawback window was punitive. Sometimes that's fair. More often, the plan was fine — and the rollout killed it.

A new commission plan is a contract change for most UK reps. It is also a trust event. Get the mechanics wrong and you don't just lose a quarter; you lose the people you most needed to keep. The good news is that there's a repeatable way to do this, and it doesn't require a change-management consultancy. Six weeks, a written doc, a few meetings, and a discipline most sales orgs skip entirely: a tracked Q&A log.

This is the playbook.

Why "send the deck on Monday" is how you lose your top biller

Commission is rarely a bonus the business can flick on and off. Acas is explicit: commission is usually one of the contractual terms agreed between the employee and employer, and to change it the employer "needs to change the employee's contract" (Acas, Commission).

That has two consequences most founders and sales leaders underweight:

1. You can't unilaterally impose a new plan. Changing a contractual commission scheme means following the proper consultation route. Acas guidance lists what employers must inform affected employees about: what the changes are, who's affected, why, the timeframe, and the alternatives considered (Acas, Proposing changes).
2. If you skip consultation, the legal exposure is real. Acas warns that a contract change without genuine consultation can lead to claims for breach of contract, unauthorised deductions from wages, or constructive dismissal (Acas, Consulting).

Even where a scheme is genuinely discretionary, Acas still expects employers to act reasonably, communicate changes clearly, and give "reasonable notice" before changing or removing it (Acas, Commission). "Reasonable notice" is doing a lot of work in that sentence. A Monday morning all-hands and a slide deck is not it.

The asymmetry: design gets the headlines, rollout gets the blame

Walk into any RevOps team mid-redesign and you'll see weeks of modelling. Accelerator curves. SPIF stack-ranking. Quota-to-OTE ratios. Margin scenarios where the top 10% earn double and the bottom 20% sit on base.

Then look at the rollout plan. It's a date. Sometimes a deck. Maybe an email.

This is the asymmetry that breaks comp launches. The plan that took eight weeks to model gets ninety minutes to land. Reps — who have built a year's worth of personal financial assumptions around the old plan — are expected to absorb structural changes to their pay in a single town hall, ask intelligent questions, and get back to selling by Tuesday.

It does not work. It has never worked. It produces the same three outcomes every time:

• Confused reps quietly start shadow accounting to verify what they're being paid.
• The best reps — the ones with the best outside options — leave.
• Disputes spike for two quarters as people argue about how the new rules apply to deals that were partially worked under the old ones.

The fix is to give the rollout as much structure as the design.

The six-week rollout timeline

Six weeks isn't sacred. It's the minimum I've seen work for a non-trivial plan change at a team of 10–50 reps. Smaller teams can compress. Larger teams or material structural changes (moving from gross-margin to revenue-based, introducing clawbacks for the first time, changing the split) need longer.

The phases below assume "Week 0" is go-live.

Week –6: Modelling and impact analysis

Before anyone outside finance and RevOps hears a word about a new plan, you need to know what it does to individual reps' take-home pay.

Run the new plan against the last four full quarters of closed-won data. For each rep, produce:

• Earned commission under the old plan
• Earned commission under the new plan
• Delta in £ and %
• Whether they would have hit accelerator thresholds under the new plan

If more than ~20% of reps would have earned materially less (say, 10%+ down) on the same performance, you don't have a comp plan, you have a pay cut, and you need to either redesign or run a structured consultation. This is the moment to find that out — not after the deck has gone out.

Week –4: Manager pre-brief

First-line sales managers find out before anyone else. Always. Two reasons.

First, managers are the people reps will turn to when they read the new plan. If a manager learns about it at the same town hall as their team, they have nothing to offer except shrugs, which is corrosive to authority.

Second, managers are your best stress-test. They know which reps will spot the gotcha in clause 4.2 and which will rage-quit over the new clawback window. Pre-briefing them gives you a fortnight to fix the language, plug the loopholes, and pre-empt the worst objections.

The manager pre-brief is a working session, not an announcement. Bring the modelling, walk through five named reps' before/after numbers, and ask: where will this break? Then change the plan if the answer is "everywhere."

Week –3: Written plan document

The single most important artefact in any comp rollout is the written plan document. Not the deck. The document.

It should include, at minimum:

• The OTE, base, and variable split for each role
• The quota and how it's set
• The commission rate, accelerator and decelerator structure
• The crediting rules (when is a deal "earned" — booking, invoice, cash collection?)
• The clawback policy with specific triggers and timeframes
• The treatment of splits, house accounts, and overlay roles
• The treatment of commission during notice periods, leave, and termination
• The dispute process

This isn't optional polish. Acas's written-statement guidance lists pay among the items that must be in the principal statement of employment particulars, including "how often and when" it's paid (Acas, What must be included). If your plan document is the reference attached to that statement, it needs to actually answer the questions reps will be paid against.

The document is also what protects you. When a rep disputes their February cheque in May, the only document that matters is the one they signed, not the slide that said "uncapped earnings!"

Week –2: Rep 1:1s

The town hall is not where you launch the plan. The 1:1 is.

Every affected rep gets a calendar invite from their manager for a 30-minute conversation that covers, specifically, their own numbers. Not the company-wide rationale. Not the strategic context. Their numbers, their quota, their accelerator, what would have happened to their last four quarters under the new plan.

This is where the modelling work from Week –6 pays back. A rep who sees their own historicals re-run under the new plan can argue about something concrete. A rep who only sees a slide deck argues about feelings, which is a much worse conversation.

Acas guidance is clear that where proposed changes are specific to a particular employee, the conversation should be private — typically a meeting between the employee and their line manager — and that information should then be put in writing afterwards (Acas, Proposing changes). The 1:1 + follow-up email is not just good practice; it's the documented expectation.

Week –1: Q&A log open, final adjustments

By Week –1, every rep has had a 1:1 and read the document. They have questions. So do their managers.

Open a single shared Q&A log — a Notion page, a spreadsheet, a Slack channel with a pinned doc, doesn't matter. The rules are simple:

• Every question gets logged, even the dumb ones
• Every question gets an answer in writing, within 48 hours
• Every answer is visible to the entire affected sales org
• When the answer changes (because you found a bug in the plan), the change is dated and the prior answer kept

This single artefact does more for trust than any town hall. It tells reps that the company is willing to be pinned down, that the rules are knowable, and that they can read what their colleagues asked. It also gives you, the operator, a list of every ambiguity in the plan in time to fix it before launch.

The Q&A log is the most underrated artefact in commission management. It is the only document that tells reps "the rules are knowable, and we will be pinned down by them."

Week 0: Go-live with grace period and parallel run

Launch day is anticlimactic if you've done the prior five weeks. The plan is documented, the managers have walked their teams through the personal impact, the Q&A log has eaten the worst ambiguities.

Two things still matter on day one:

1. A written grace period. For the first 30–60 days, any rep-side calculation challenge gets investigated without penalty. No "you should have flagged this in the consultation window." If the plan is unclear, the unclarity is the company's fault.
2. A parallel-run period of at least one full pay cycle. Calculate the next month's commission under both the old plan and the new plan. Show reps both numbers. Pay the higher of the two, or pay the new plan but disclose the old-plan figure. This costs you one month of incremental commission. It buys you trust that survives the next four quarters.

The contrarian thread: never roll out at the start of a quarter without a parallel run

Conventional wisdom says comp plans should launch at the start of a quarter or year. Clean cut-over, clean attribution, clean reporting.

This is wrong for almost every UK sales team I've worked with, for one specific reason: pipeline doesn't respect quarter boundaries.

A new plan that goes live on 1 April lands on a pipeline that was built, qualified, forecast, and partially worked under the old plan. Deals that closed on 31 March pay one way; the same deal, slipped by 48 hours, pays another. Reps notice. Reps remember. The reps who lose money on the slip will tell every new hire about it for two years.

A parallel-run period — where the old plan still governs deals that were in pipeline before the new plan landed — fixes this. So does an "in-flight deal" carve-out: any opportunity created before Week 0 is paid under the old plan; any new opportunity from Week 0 is paid under the new plan.

Pick one. Document it. Stop pretending the calendar is doing the work for you.

Anti-patterns to refuse

A short list of rollout mistakes that show up in every botched launch:

• Verbal-only changes. "We talked about this on Monday" is not a documented plan. If it isn't written, it didn't happen.
• Manager-by-manager improvisation. Different teams hearing different versions of the same plan. Usually because the central doc was incomplete and managers filled the gaps.
• Retrospective changes mid-quarter. Changing the rate or the quota after deals have been worked. This is the fastest way to a constructive dismissal conversation (Acas, Consulting).
• No named owner for the Q&A log. If everyone owns it, no one does, and questions go stale.
• "It'll come out in the wash." It will not.

What this looks like with a commission tool in the loop

Most of this playbook is process, not software. But two parts of the rollout are dramatically easier when commission isn't living in a spreadsheet.

The Week –6 modelling — running the new plan against four quarters of historical deals — is a half-day job with a commission platform and a multi-week job in Excel. That's the difference between modelling everyone's before/after and just modelling the top and bottom three reps and hoping the middle works out.

The Week 0 parallel run is also where spreadsheets fall over. Running two plans against the same dataset, exporting both to payroll, and showing reps both numbers in their own dashboard is exactly the workflow Commit was built for — including the Xero export at the end. But the playbook works without us. It just takes longer and produces more disputes.

The thing to remember

You can't make a comp plan land by sending the deck on Monday. Commission is contractual or near-contractual for most UK reps. The legal expectation is consultation, not announcement. The operational expectation is documentation, not slides. The trust expectation is that the rules are knowable and that the company will be pinned down by them.

Six weeks. Manager pre-brief. Written doc. Rep 1:1s. Tracked Q&A log. Grace period. Parallel run.

It is more work than "send the deck on Monday." It is much less work than rebuilding the team after your top biller resigns in Q2.