Compensation Adjustment Template That Actually Gets Approved

1. Employee context that means something

Titles are useless without context.

“Senior Manager” could mean team leads or a commercial owner. Those are priced differently.

Anchor this section properly:

• What the level actually represents

• How the role compares internally

• Whether the scope has grown

If the scope has not changed, you are arguing market or retention. Be clear which.

2. Current compensation, fully loaded

Base salary alone tells half the story.

Decision-makers look at total compensation first.

Spell it out:

• Base

• Bonus or variable

• Equity

• Total

If you hide this, expect pushback.

3. The request, without vagueness

This is where most proposals drift.

“Market adjustment” is not a number.

State it cleanly:

• New base salary

• Updated bonus or commission

• Equity change if relevant

• Effective date

Then add one line most people skip:

Is this a correction or part of a progression path?

That single line cuts follow-up in half.

4. Rationale that holds up under pressure

Long explanations do not help. Evidence does.

Use this structure:

The 4-part justification model

Signal
What triggered this
Offer risk, expanded scope, performance

Gap
Where they sit now
Example: 15 percent below the market median

Evidence
What proves it
Market data, internal comparisons, performance metrics

Risk or upside
What happens next
Lose them, slow growth, or stabilise and retain

If you cannot fill all four, the case is not ready.

5. Benchmarking that makes the decision obvious

Bad benchmarking is a single number from a single source.

Good benchmarking triangulates:

• External market data

• Internal peer averages

• Role context

Lay it out cleanly:

Now the decision is not a debate. It is a choice.

6. Cost clarity removes friction

Finance blocks uncertainty, not requests.

Do not write “budget available”.

Write:

“£10k increase, covered by unused headcount budget”

Be specific:

• Annual cost

• Budget status

• Funding source

If this section is vague, everything stops here.

7. Approvals that move, not stall

Messy approval chains kill momentum.

Each approver needs:

• A clear recommendation

• A decision option

• Space for notes

No ambiguity. No silent delays.

What this looks like in practice

A manager wants to retain a high-performing account lead.

They submit a structured proposal:

• Shows a 12 percent gap to market

• Links performance to revenue growth

• Benchmarks against two internal peers

• Outlines a £9k increase, already budgeted

Approved in one pass.

Not because it was persuasive. Because it was clear.

Where this breaks down

Even strong templates fail when the system around them is loose:

• Different formats across teams

• Missing data

• Multiple versions

• No clear approval trail

Now every request feels different. Every decision takes longer.

Why the template is the system

A good compensation adjustment template does not just organise a request.

It forces discipline:

• You cannot skip the hard parts

• You cannot hide weak data

• You cannot send half-formed proposals

That is what speeds decisions.

Where Assemble fits

This only works if the template is consistent.

Assemble turns this into a repeatable workflow:

• Same structure every time

• Required fields enforced

• Benchmarking stays standardised

• Approvals are built in

No chasing missing info. No rewriting requests. No version chaos.

Just clean submissions ready for approval.

Build it once. Use it properly.

If compensation reviews are recurring, this is not admin. It is infrastructure.

Either you run them through loose documents and slow decisions.

Or you build a system that makes approval the easy part.

The difference shows up fast.

Build your compensation adjustment workflow in Assemble and stop guessing what “good” looks like.