Guide · Pay bands

Paid above the band maximum: Now what?

Find the reason first. Then move the job, move the band, hold the base or protect the pay for a stated period.

Short answer: It depends on why the pay is above the band maximum. Re-level the job if the work has grown. Review the band if the market moved. Hold the base and pay lump sums if the pay is simply high. Protect it for a stated period where the company asked the person to move. Record the reason either way.

Eleven people over the line

Northwind Analytics, a 160-person software company, has just finished its first proper salary bands. The new structure fits most people well. Eleven people sit above the maximum of their new band.

They are not one group. Four are long-serving engineers whose pay grew with every review while their jobs stayed the same size. Two came in through a small acquisition on their old employer's pay. Two are senior specialists who were hired in a hot market at whatever it took. One manager moved into a smaller role last year and kept her salary. And two are people whose jobs have quietly grown into something bigger than the level they were placed at.

The CFO wants a single rule. Several managers want each case handled their way. The head of people knows that whatever the company does will be visible. These people will see their next raise and their colleagues may ask how pay compares. The posted ranges for their jobs now show a maximum below what they earn.

Northwind Analytics is a fictional company and the figures are illustrative.

Why pay above the maximum is hard to handle

A band maximum is the most the company intends to pay for a job at that level, however long someone has done it or however well. Pay above it is often called "red-circled". The person keeps their pay, but the structure says it is more than the job is worth.

Two good goals pull against each other. The first is integrity of the structure: A band only means something if the company holds to it. Every exception makes the next one easier and the posted range less true. The second is fairness to the person: Most people above the maximum did nothing wrong. They were hired when the market was hot, kept by a manager who valued them, or moved into a smaller job for reasons the company accepted.

The reasons people end up above the maximum differ. The right answer depends on the reason. That is the core difficulty. A single rule applied to everyone will be right for some and wrong for others. Treating every case on its merits invites inconsistency.

Pay transparency makes all of this more visible. Posting laws now put band ranges, or something close to them, on job ads in many US states [6]. In the EU, workers can ask for the average pay of colleagues doing the same work or work of equal value [4]. People above the maximum raise that average and may be asked about. And US equal pay guidance accepts red-circle pay only where sex is not a factor and a valid business reason supports it [1].

Budgets add one more pressure. In a July 2026 survey of about 1,000 US organizations, three in four said they adjust their salary structures every year, by an average of 2.6% [5]. Structure movement slowly brings some people back inside their band. For people far above it, that can take many years.

A first structure project usually finds more people above the maximum than anyone expected. That is not a sign the bands are wrong. It is a sign that pay was set before the bands existed, one decision at a time. The number of people above the maximum is a measure of how much history the new structure has to absorb. How the company treats them tells everyone else whether the structure is real.

Five ways companies mishandle pay above the band

Each of these resolves the immediate tension. Each creates a bigger problem later.

"Raise the maximum to fit them"

What it looks like: Rather than leave someone above the band, the company stretches the band until they fit.

Why smart teams fall into it: It makes the problem disappear in the system. Nobody has to have a difficult conversation.

What it costs: The band now fits one person and misdescribes the job for everyone else. Its maximum rises, so other people in the band gain headroom they were never meant to have. Any posted range built from it widens or rises. And the next time someone sits above a band, the precedent is set. If the band really is too low for the market, that is a different question with a different answer. Our guide on how wide a posted pay range can be looks at what width does to a range's credibility.

"Find them a bigger title"

What it looks like: The person is moved to a higher level or given a new title so their pay fits the band, without the job itself changing.

Why smart teams fall into it: It feels generous and solves the band problem. The person is usually pleased.

What it costs: The level now describes pay, not work. Colleagues doing the same job see someone with a bigger title and no bigger role. The structure loses its link to job size, which is the thing that lets the company explain pay. Equal pay comparisons get harder too, because two people doing the same work now sit at different levels. A promotion is the right answer only when the work has really grown. For the two Northwind employees whose jobs did grow, re-leveling is the honest fix. For the others it is a workaround.

Title workarounds also spread. Once one person has been moved up to fit their pay, others in the same position ask for the same treatment. Managers learn that a level can be negotiated. Within a cycle or two, the levels describe a mix of work and history that nobody can explain to a new hire.

"Freeze their pay and say nothing"

What it looks like: People above the maximum simply get no raise. Nobody explains why.

Why smart teams fall into it: It holds the structure without a confrontation. It also saves money.

What it costs: A silent freeze feels like a punishment to someone who has performed well. Many of the people above the maximum are experienced and valuable. They are also the people most able to leave. A freeze can be a reasonable policy. Public employers often run one openly: One university pays classified staff at the top of their range an annual lump sum equal to the general increase, with base pay unchanged [2]. A state government's rules let performance increases be paid as a lump sum but never above the range maximum [3]. The difference is that those rules are written down and the person knows what will happen.

"It's only a few legacy cases"

What it looks like: The company treats people above the maximum as a historical oddity and leaves them be, without recording why each one is there.

Why smart teams fall into it: The numbers are small and the reasons feel obvious to the people who were there at the time.

What it costs: The reasons fade faster than the pay. Two years later nobody remembers why one person is protected and another is not. If the people above the maximum are mostly men, or mostly one group, the pattern looks very different to an employee, a regulator or a court. US guidance accepts red-circle pay only where sex is not a factor and there is a valid business reason that investigators can check against the facts [1]. A reason that was never written down is hard to check. In the EU, the same people sit inside the averages that colleagues can ask about [4]. Our guide on which pay gaps you can defend covers why the reason needs to exist before the question does.

"Bring their pay down to the band"

What it looks like: The company reduces pay to the new maximum, sometimes in steps.

Why smart teams fall into it: It is the only option that makes the structure fully consistent at once.

What it costs: Pay cuts damage trust far beyond the person affected. Everyone watching learns that a new structure can take money away. They can also raise legal and contractual questions that differ by country and contract. In most cases the cost of protecting the pay is lower than the cost of cutting it. A cut is rarely the right answer and never one to make without legal advice.

There is one narrow exception companies sometimes consider: Pay that sits above the maximum because of a clear error, such as a misread offer or a duplicated allowance. Even then, how the correction is handled matters more than the correction itself. Most companies phase it, explain it and take advice first.

The four honest options

Once the reason is known, most cases fit one of four answers. Each is honest because it says what is really happening.

  • Move the job, if the work has grown. If the job is now bigger than its level, re-level it and the pay may fit. This is a promotion on evidence, not a workaround.
  • Move the band, if the band is wrong. If many people in a job sit above the maximum because the market has moved, the band needs review, not the people. That is a decision for the whole job, made with market data.
  • Hold the base and pay lump sums, if the pay is simply high. The person keeps their salary. Future increases are paid as one-off amounts, or not at all, until structure movement catches up. The rule is written down and explained.
  • Protect the pay for a stated reason and period. Some cases deserve protection: A role change the company asked for, an acquisition, a health-related move. The protection has a reason on record, a review date and an end condition.

The fifth option, doing nothing and recording nothing, is the one to avoid. Our guide on grades, bands and levels explains why the structure depends on those three staying distinct.

What a sound approach looks like

In our view a sound approach to pay above the maximum has these qualities.

  • Every case has a recorded reason. Each person above the maximum is placed in a reason category, such as job grown, market moved, hired high, role changed or acquisition, with a line of explanation.
  • The answer follows the reason. Re-level, review the band, hold with lump sums or protect for a period, depending on which reason applies. The same reason always gets the same answer.
  • The lump-sum rule is written. Who gets one, how it relates to the normal increase and what performance it needs are stated in policy, as the public employers above do [2] [3].
  • Protection has an end. Every protected rate has a review date and a condition under which it ends.
  • The group is checked as a whole. Someone looks at who sits above the maximum by gender and other groups the company tracks. Any pattern has an explanation.
  • Many cases trigger a band review. If a large share of a job sits above the maximum, the band is reviewed before the people are.
  • The person is told. Each person knows their position, the rule that applies and what would change it.

None of this is a procedure to copy. Each quality is a test a reviewer can put to the cases a company already has.

Timing matters as well. The conversation with each person should happen before the first pay review under the new bands, not during it. Someone who learns at review time that their raise is a lump sum, with no warning, hears it as a cut. Someone who heard the rule two months earlier hears it as the policy it is.

The calls only you can make

Whether lump sums are paid and how much. A lump sum equal to the normal increase keeps the person whole each year without raising the base. A smaller one or none saves money and signals more firmly that the pay is above the job.

How long protection lasts. Some companies protect pay indefinitely for long service. Others set a fixed period. Shorter protection is cleaner. Longer protection may be kinder and is easier to defend for people moved at the company's request.

When to move the band instead. Moving a band costs money across a whole job. Leaving it costs credibility if the market really has moved. That is a judgment about the market and the budget.

Who decides each case. A single owner applying the rule keeps answers consistent. Letting each manager propose the answer for their own people is faster and invites the same case to be handled three different ways. Most companies at this size let managers make the case and one person decide.

How open to be. Some companies publish their rule for pay above the maximum. Others handle each case privately. A published rule is easier to apply consistently and easier to challenge.

The law and the numbers

  • US equal pay. Red-circle rates do not violate the Equal Pay Act if sex is not a factor and a valid business reason supports them. Investigators check whether the reason holds up or is a pretext [1].
  • Public employer practice. One university pays top-of-range classified staff an annual lump sum equal to the across-the-board increase if their rating is acceptable, with base pay unchanged [2]. A state government's December 2025 rules allow performance increases as base adjustments, lump sums or both, but never above the range maximum [3].
  • EU. Workers can ask for their own pay and the average pay of colleagues doing the same work or work of equal value, broken down by sex [4].
  • Structure movement. Three in four US organizations in a July 2026 survey adjust salary structures every year, by an average of 2.6% [5].

Our view

We think there is no single right answer to pay above the maximum, but there is a right way to decide. Find the reason first. Then apply the answer that fits it: Re-level if the work grew, review the band if the market moved, hold the base with lump sums if the pay is simply high and protect it for a stated period where the company asked the person to move.

We would argue hardest against two habits: Bending the structure to fit each person and leaving cases unrecorded. The first erodes the bands for everyone. The second leaves the company unable to explain a group of high-paid exceptions just when someone asks.

Handled well, the people above the maximum become proof that the structure is fair. Each has a reason, each knows the rule and the rule is the same for everyone in the same situation. That is a story any employee can follow, which is more than most structures can say about their exceptions.

Sources

  1. US Equal Employment Opportunity Commission, Compliance Manual Section 10: Compensation discrimination, section 10-IV.F.2.e (red circle rates), checked 2026-10-25
  2. Bowling Green State University, Human Resources, Annual increase (page updated 19 January 2026), checked 2026-10-25
  3. Minnesota Management and Budget, Performance based salary increases, office memorandum (9 December 2025), checked 2026-10-25
  4. Directive (EU) 2023/970 on pay transparency, Article 7 (EUR-Lex), checked 2026-10-25
  5. Mercer, Results of the July 2026 QuickPulse US Compensation Planning Survey (31 August 2026), checked 2026-10-24
  6. Washington L&I, Administrative Policy ES.E.2, Job Posting Requirements (issued 3 December 2025), checked 2026-10-24

Who approves a pay exception?

Every pay exception is a precedent. Five traps in approving offers, raises and counteroffers outside the rules and what sound approval looks like.

How wide can a posted pay range be?

Virginia now weighs range width in good faith and Delaware will from 2027. Five ways posted ranges go wrong and what a defensible range looks like.

Which pay gaps can you defend?

An explained gap is not a defensible one. Five ways a pay equity review explains away a real gap and what a review you can rely on looks like.

See Resources for every guide and the self-check.