Build salary bands that hold up
Bands, merit increases and budget guardrails are the three levers of a compensation cycle. Here is how to set each one, in what order, and what to do when market data and your internal equity data disagree.
Start with role architecture, not with numbers
Before you can set a band, you need to know what roles you are banding. Group similar work at similar scope into a job family, then define levels inside that family. A senior analyst in one department should mean roughly the same thing as a senior analyst in another, or the band will not hold across the org chart. This step is unglamorous and it is the foundation everything else rests on.
Write the family definitions down in plain language: what the role owns, what scope it works at, and what a level up actually adds. If two managers describe the same job title differently, that gap becomes a band exception later. Fix the description now and the arithmetic gets easier in every following step.
What a workable job family needs
- One clear scope statement per level, written before the numbers.
- Job titles that map to a level, not to a person or a tenure.
- A named owner who resolves disputes about level placement.
Families usually survive an annual refresh. Levels inside them need a check whenever a role's scope shifts, which happens more often than the market moves.
How to set a salary band from market data
Pull at least two market sources and note the date on each one. Payscale MarketPay is positioned around multi-source benchmarking, which reflects how most compensation teams work in practice. Set the midpoint at your target market position, then build a range around it. A band that is too narrow forces constant exceptions. A band that is too wide gives managers no guidance at all.
Record the source, the date you pulled it, and the role it covers. An undated benchmark is very hard to defend in a review two quarters later, when a manager asks why a candidate offer sits where it does.
Band build — midpoint and range, illustrated
The overlap band marks the working range a manager can move inside without an approval. Everything outside it is an exception, and exceptions need a process.
Choosing a market position you can defend
Pay at the 50th percentile is a common default. Pay at the 75th is a hiring argument. Pay below the 25th is a retention risk you should acknowledge out loud. The market position is a business decision, not a compensation decision, and it should be made by whoever owns the hiring plan. Write it down so it does not drift role by role.
Merit increase budgets and how to split them
A merit budget is a percentage of total base payroll, not a flat raise for everyone. If you set 3 percent, that is the pool. Managers allocate from it. High performers get more, low performers get less or nothing. The pool approach keeps the total cost predictable while giving managers discretion. The flat-raise approach is simpler to explain and removes most of the point.
Percentage pool
3–4%
Scales with base payroll, so total cost stays predictable when headcount changes mid-year. Managers decide who gets what inside the pool.
- Adjusts automatically as payroll grows
- Keeps the merit pool a decision, not a residual
Fixed amount
flat
Simpler to communicate because every employee hears the same number. It does not flex when headcount moves during the year.
- No link to payroll growth
- Rewards tenure more than performance
Before allocation
Tell managers the pool number and the distribution guidance in the same message. Splitting them invites every manager to invent a policy.
Bonus pools and the interaction with merit
Merit and bonus compete for the same compensation budget. If you fund merit at the top of the range, the bonus pool has to shrink. Decide the split at the planning stage, not after manager recommendations arrive, because by then the split has already been made for you one recommendation at a time.
A common structure is a merit pool of 3 to 4 percent of base payroll and a bonus pool sized to target payout. Your numbers will differ with your sector and your margin, but the split should be a decision you can point to, not a residual left over at the end.
Write both pools into the same planning document. When a manager asks for a merit exception in November, the document is the answer, and it was written before anyone had a name attached to the number.
The overlap zone on a printed sheet marks where two inks cross. In a compensation budget, the same overlap is the region where merit and bonus funding both live — and it is the region that runs out first.
Budget guardrails that managers can actually follow
A guardrail is a ceiling plus a process. The ceiling is the department budget. The process is what happens when someone wants to exceed it. Without a defined process, managers route around the ceiling. With one, exceptions become visible and reviewable. Compensation platforms with configurable approvals exist specifically to make this step enforceable rather than aspirational.
Pay equity analysis during the cycle
Run the pay equity check before approvals close, not after. Compare employees in the same role, level, and location, then look at gaps that tenure and performance do not explain. Bullseye Engagement lists budget limits and pay equity analysis together, including gender-based pay comparisons, which is the right pairing. A gap found in October is a budget adjustment. A gap found in a legal review is a different conversation entirely.
Keep the comparison narrow enough to be honest: same role family, same level, same location band. Broad comparisons across departments tend to surface differences that come from scope rather than from pay practice, and they make the real gaps harder to see.
Sort by role family, then level, then location. Anything left over is either a real gap or a scoping error, and both are worth knowing before approval.
What to do when market data and internal equity conflict
This happens most often with long-tenured employees in roles where the market has moved fast. The honest answer is that you have a retention decision, not a band decision. Quietly widening the band to accommodate one person is the one move to avoid, because the band is a shared tool and every other employee in that family is now priced against a number that was built for someone else.
A market adjustment outside the merit cycle
Moves the employee to the current market rate without consuming merit pool, and it is visible as its own line in the budget rather than hidden inside an exception.
A retention bonus
Keeps the base rate structure intact while addressing the immediate risk. It is a decision with an end date, which base salary is not.
Accepting the risk
Sometimes the correct answer. Write down that you chose it, and the reason, so it reads as a decision later.
Documenting the cycle so next year is easier
Keep the market sources, the date pulled, the market position decision, the merit and bonus split, and the exception log. Next year's planning starts from that record instead of from scratch. Teams that document their cycle spend less time re-litigating decisions and more time making them.
Store this with the budget model rather than in a manager's inbox. The point of the record is that it survives staff changes on the compensation team.
Questions that come up every cycle
Three questions we hear most often from HR teams planning a salary cycle for the first time, with the answers we would give a colleague.
How wide should a salary band be?
Many teams use a range of roughly plus or minus 20 percent around the midpoint, though the right width depends on role scarcity and internal leveling. Wider bands need more manager discipline, because every extra percentage point of range is another judgment call someone has to make and defend.
Should merit increases be a percentage pool or a fixed amount?
A percentage pool scales with payroll and keeps the total cost predictable. A fixed amount is simpler to communicate but does not adjust when headcount changes mid-year, which is exactly when the difference starts to matter.
How often should salary bands be refreshed?
Annually for most roles, more often for roles where the market moves quickly. Note the date on every source you use, because an undated benchmark is hard to defend later when someone asks why the midpoint sits where it does.
Put the plan through the press
Model the fully loaded cost of your next cycle, or look at how the platforms you are considering handle approvals, exception logs, and equity checks. If something on this page is unclear or missing, tell us and we will add it.
Everee Salary & Budgeting Guide — 4821 Maple Ridge Drive, Columbus, OH 43220 — Monday to Friday, 9:00 AM – 6:00 PM Central Time