Salary bands turn pay decisions from one-off negotiations into a repeatable system. They give recruiters a range for offers, give managers a basis for promotion conversations, and give finance a clearer view of payroll cost.
Contents
- What salary bands include
- Build job levels first
- Set a usable range
- A worked salary band example
- Keep the structure working
What are salary bands?
Salary bands are pay ranges for roles or job levels. A typical band has a minimum, midpoint, and maximum. The minimum suits a person still building capability in the role. The midpoint represents solid, fully proficient performance. The maximum leaves room for deep expertise without changing the job level.
The important distinction is simple: the band belongs to the role, while the employee’s skills, experience, and impact influence their position within it. That makes similar decisions easier to explain and review.
1. Build job families and levels before salary bands
Do not start with current salaries. Start with the work. Group related roles into job families, then describe the difference between levels in terms of scope, judgement, technical depth, and business impact.
For example, a customer support specialist and a senior specialist should not be separated only by tenure. The senior role may own difficult cases, coach colleagues, or improve a workflow. Those are observable differences in job value.
A small company does not need a grade for every title. Six or seven levels can cover a growing organisation. Too many grades make the framework hard to use and encourage title inflation.
2. Choose the market you are comparing against
Market data is useful only when the comparison is clear. Set the location, industry, company size, and role scope before reading a survey or a job-board range. Then make an explicit choice about your pay position: do you want to target the market median, pay above it for scarce skills, or take another approach?
Use more than one input. Compensation surveys, recent recruiting feedback, and credible job-market data can reveal different parts of the picture. Keep the sources and the date of the review with the band. A range copied from an old spreadsheet loses value quickly.
Pay range communication also matters. The European Commission’s work on pay transparency shows why organisations need a defensible approach to pay information, even where a disclosure requirement does not apply to them.
3. Set each salary band around a midpoint
Once the market position is chosen, set a midpoint for each level. Then build the minimum and maximum around it. Narrower bands can work for roles with a short learning curve. Roles where expertise expands over many years usually need a wider range.
| Level | Minimum | Midpoint | Maximum |
|---|---|---|---|
| Specialist | $54,000 | $60,000 | $66,000 |
| Senior specialist | $64,000 | $76,000 | $88,000 |
This is a worked example, not a market benchmark. The specialist band runs 10% below and above its $60,000 midpoint. The next level begins at $64,000, so the two ranges overlap by $2,000. A small overlap can support progression before a formal promotion. Too much overlap makes levels hard to distinguish.
4. Test salary bands with compa-ratio
Compa-ratio shows where pay sits relative to a midpoint: current salary divided by band midpoint. If a specialist earns $57,000 in the example above, the calculation is $57,000 / $60,000 = 0.95. That does not automatically mean the salary is wrong. It starts a useful review.
A new hire may reasonably sit below the midpoint. A person with rare skills or sustained high impact may sit above it. Look at performance, relevant experience, role scope, and internal comparisons before acting. The value of the ratio is consistency: it reveals where similar cases receive very different treatment.
5. Write the decision rules managers will use
A pay framework breaks down when every urgent offer becomes an exception. Document the rules before the first exception appears. Define who can approve a starting salary above the midpoint, how promotions move people into a new range, and how often bands are refreshed.
- Offer placement: What evidence supports a low, middle, or high-range offer?
- Promotion: How does pay move when level and scope change?
- Exception handling: Who approves pay outside the range, and when is it reviewed?
- Annual review: Which market sources and internal checks trigger a band update?
Keep these decisions in one current record rather than in private spreadsheets. A structured compensation review process makes it easier to track approvals, role changes, and the rationale behind each decision.
6. Explain the framework without overpromising
Publishing every number is not the only way to improve trust. Employees should understand how jobs are levelled, what supports progression, and how pay decisions are reviewed. Managers need training too. A good band structure can still create confusion if different managers describe it differently.
Review salary bands when the organisation changes, not only during the annual pay cycle. New job families, a new hiring market, or repeated exceptions are signals that the structure needs attention. The first version does not have to be perfect. It needs to be clear, consistently applied, and easy to improve.
Start small: choose ten high-impact roles, define the levels using the same criteria, and set a midpoint for each. A short, workable first version beats a complex model that never reaches a manager’s desk.
