Negotiating After A Restructure Changes Your Job

Restructures change what people do without changing what they are paid. The pay conversation that should follow is rarely scheduled by anyone.

Scope moves before pay does

A reorganisation redistributes work. Teams merge, layers are removed and responsibilities are reassigned to whoever is available and competent.

Pay is set against a role definition that was written before the change. Nothing in the restructure automatically triggers a review of that definition.

The gap can persist for years, because the individual absorbing extra scope is the person least likely to be flagged as a problem by the process.

Why the timing works against the employee

Restructures are usually driven by cost, so the immediate context is one of reduction rather than increase. Raising pay in that moment reads as poorly judged.

The people who would approve a change are also occupied with the reorganisation itself, and requests that are not urgent are deferred until it settles.

By the time it settles, the enlarged role has been performed for months without complaint, which the organisation reasonably reads as evidence that the current pay is sufficient.

Documenting the role as it now stands

The strongest case is a comparison between the role description on file and the work actually being done, expressed in scope rather than effort.

Concrete measures travel best inside an organisation: people managed, budget held, systems owned, decisions taken without escalation, and functions that would need covering if the person left.

Effort-based arguments are weaker because every team is busy after a restructure. Scope-based arguments point at structure, which is what the pay framework responds to.

Levelling is the usual route

Most employers set pay against internal levels rather than against individual negotiation. The question that gets answered is which level the role now sits at.

Framing the request as a re-levelling exercise puts it into an existing process with defined criteria, rather than asking a manager for an exception.

It also means the answer can be checked. Where the criteria are published internally, the role can be tested against them by both sides.

When the answer has to wait

Where a pay budget is fixed until the next cycle, the achievable outcome is often an agreed position rather than immediate money.

A written record that the role has been re-levelled, with effect from a stated date, converts an argument that has to be remade later into one already settled.

Without that record, the enlarged role becomes the baseline. The next review then treats the additional scope as the normal expectation of the job rather than as a change.