Guide · Pay bands

Grade vs band vs level: What does each one do?

Three words, one system. When a company uses them loosely, every pay decision turns into an argument about which one counts.

Short answer: A level says how big a job is. A grade groups jobs of similar value across different teams. A band is the pay range attached to a level or a grade. In the grade vs band vs level question, the order matters more than the words: Pay set before the jobs are sized is a number with nothing behind it. Pay laws now ask companies to show that link.

Three answers to one question

Northwind Analytics is a fictional 120-person data company based in Denver that hires remotely across the US. It is about to post its first job ad with a pay range, for a senior data engineer who can work from anywhere in the country. The recruiter asks a simple question: What is the band?

She gets three answers. The head of engineering says the role is "an L4" and that L4 engineers should earn more than the band in HR's spreadsheet. The finance lead says the role sits in "grade 6" in the budget model, next to the senior product designer. There, the grade 6 range is fixed. The HR lead points to a band labeled "Senior" that applies to every job with that word in its title.

Each of them is using a real tool the company built at some point. None of them is wrong about their own tool. But the three tools were never connected. The engineering ladder was written by engineering. The grades were added by finance for budgeting. The title bands came from a benchmarking export. Nobody had decided which one sets pay.

The gap shows up in the people first. Northwind has two senior data engineers, paid $133,000 and $155,100. One builds pipelines with light review. The other leads work across two teams. Under the title band they are the same job. Under the engineering ladder they are not. Under the grades nobody has checked.

The ad has to show one range. Washington's posting guidance, which covers remote jobs a Washington-based employee could do, expects a range set before the ad goes up. Whatever number Northwind posts will also be compared, within days, with what the two engineers are paid.

Northwind Analytics is fictional and its details and numbers are illustrative.

Why the words keep getting mixed up

The three terms are simple on their own. A level describes the size of a job: Its scope, impact and autonomy. A grade groups jobs of similar value, often from different teams, so they can share a pay range. A band is the pay range itself, with a minimum and a maximum, attached to a level or a grade.

They get mixed up for good reasons. Software tools, surveys and consulting firms use the words differently. Some treat grade and band as the same thing. Some use level for everything. Growing companies tend to meet all three in the same quarter: A benchmarking tool arrives with bands, a manager asks how promotions work and a new law asks for a posted range. Each need gets its own quick answer.

Underneath the vocabulary there is a real tension. The first goal is local fit. Each team wants a ladder that describes its own work in its own language, with pay that matches its own market. Engineering levels read nothing like sales levels. They should not have to. The second goal is comparability. The company needs to say that a senior engineer and a senior designer doing work of similar value are treated consistently, even if they are paid differently for market reasons.

Local fit pulls toward separate ladders and separate bands per team. Comparability pulls toward one shared frame. Levels serve the first goal best. Grades exist to serve the second. Bands sit on top of whichever frame the company chooses. When the company has not chosen, each team quietly picks its own and the structure stops being one system.

Until recently that was mostly an internal problem. It is becoming a legal one. The EU pay transparency directive asks employers to have pay structures that let them compare the value of different jobs on objective, gender-neutral criteria. US equal pay law has long looked past titles to the actual content of the work. And posting laws turn the band into a public number that has to rest on something.

Five ways the three get mixed up

Each of these is a shortcut that works for a while. Each one leaves the company unable to say why a job is paid what it is.

"A title is a level"

What it looks like: Pay ranges are attached to titles. Everyone called "Senior" shares a range, whatever the job involves. Titles were given out over the years by different managers, often to win a hire or reward someone without a raise.

Why smart teams fall into it: Titles already exist and everyone understands them. Writing level definitions feels like a project. Using titles feels like a decision already made.

What it costs: A title says what someone is called, not how big the job is. Northwind's two senior data engineers show the problem. Under a title band, the higher-paid one looks overpaid or the lower-paid one looks underpaid. The company cannot say which. That matters beyond fairness. The EEOC states that job content, not job titles, determines whether jobs are substantially equal under US equal pay law. A title band offers no answer when someone asks why two people with the same title earn different amounts. Title inflation adds a second cost: Once titles carry pay, every title request becomes a raise request.

"Grade and band are the same thing"

What it looks like: The company has a list of ranges labeled grade 1 to grade 10. Jobs were put in a grade by matching their market pay to the nearest range. No one ever compared the jobs inside a grade with each other.

Why smart teams fall into it: Many tools and templates label a pay range as a grade, so the two words feel interchangeable. Slotting jobs by market pay is fast and looks objective.

What it costs: A grade built from pay alone says only that two jobs cost about the same in the market. It says nothing about whether they are of similar value to the company. The difference matters when someone asks whether two jobs are comparable. The EU directive defines work of equal value through criteria such as skills, effort, responsibility and working conditions, not market price. Guidelines on gender-neutral job evaluation published by the European Commission and the European Institute for Gender Equality in March 2026, as summarized by one law firm, break those four criteria into subfactors. A grade made by sorting market rates cannot show any of that. A grade made by comparing jobs can.

"Every family gets its own ladder"

What it looks like: Engineering has seven levels. Sales has four. Customer success has five, named differently again. Each ladder was written by the team that uses it, at a different time, for a different purpose.

Why smart teams fall into it: Team leads know their own work best. Letting each one write a ladder is quick and gets buy-in. A shared frame feels like bureaucracy for a company of a hundred people.

What it costs: Separate ladders work until someone compares across them. A level 4 in one family may be a level 3 job in another. No one can say. Promotions and internal moves become negotiations. Pay gaps between families open quietly, because nothing links the ladders. Under the EU directive this becomes a reporting problem. Employers report pay gaps by category of workers, which the directive defines as workers doing the same work or work of equal value. A gap of 5% or more in any category that the employer cannot justify on objective, gender-neutral criteria triggers a joint pay assessment with worker representatives. A company with unconnected ladders has no defensible way to say which jobs belong in the same category.

"Bands first, structure later"

What it looks like: A posting law or a hiring push needs ranges now. The company buys data, builds bands for its current titles and plans to sort out levels afterward.

Why smart teams fall into it: The deadline is about the number. Levels feel like a nice-to-have that can follow. Bands also look like progress to a leadership team in a way that level definitions do not.

What it costs: A band without a level has nothing to point back to. Every exception becomes a debate, because there is no shared description of the job to point to. The bands also tend to set the levels by accident: Once people are paid inside a band, the later level work bends to fit the pay. Posting laws make this visible. Washington's guidance asks for a range for each possible title when one ad covers several, which assumes the company knows how those titles differ. Our guide on building bands from market data shows how weak job matches, often a symptom of missing levels, move the band more than the data does.

"One more grade will fix it"

What it looks like: A strong candidate needs more than the top of the band, so a grade is added between two existing ones. A long-serving employee hits the maximum, so a new grade is created above theirs. Over three years, eight grades become fourteen.

Why smart teams fall into it: Adding a grade solves today's problem without touching anyone else's pay. It feels more structured than a one-off exception.

What it costs: Each new grade is an exception that has been made permanent. The steps between grades shrink until no one can say how a grade 7 job differs from a grade 8 job. Ranges overlap so much that promotion stops meaning a pay change. Employees notice that grades follow negotiations rather than the work. When too many grades are a symptom, the cause is usually that the grades were never tied to job size in the first place. Our guide on how many job levels a company needs looks at the same problem from the level side.

What a structure you can explain looks like

There is no single right design. Some companies use levels and bands only. Some add grades once they have many families. What sound structures share, in our view, is that each of the three words does one job and everyone uses it the same way.

  • Levels describe work, in writing. Each level has a short definition of scope, impact and autonomy that a manager could use to place a job without knowing who holds it.
  • Levels mean the same size of job across families. A level 4 in engineering and a level 4 in finance are jobs of roughly similar weight, even if they are paid differently.
  • Grades, if used, come from comparing jobs. Jobs share a grade because they were judged similar in value on stated criteria, not because their market rates happened to be close.
  • Bands sit on the frame, not beside it. Every band is attached to a level or a grade. A manager can trace any range back to the job size it pays for.
  • Titles follow levels. A title tells people the level and the family. It is not a separate currency.
  • There is one owner. One person or team decides changes to levels, grades and bands. Engineering, finance and HR are not each keeping their own version.
  • The structure survives a question. When an employee asks why their range is what it is, the answer is the level, the market and the position the company chose. In Massachusetts, a current employee can ask for the range of the job they hold.

A good test is the one Northwind failed. Ask three leaders the band for the same open job. If the structure works, they give the same answer for the same reason.

The calls only you can make

A method can frame these choices. It cannot make them.

Whether to use grades at all. Levels with a band per family are simpler and fit companies whose families pay very differently. Grades add a shared frame that makes cross-family comparison easier, at the cost of more structure to maintain. Companies with EU employees, or many families doing comparable work, have more reason to add them.

How much the families should share. One common set of levels across the company makes moves and comparisons easier. Separate ladders let teams describe their work in their own terms. Many companies land in between: A shared set of level definitions, with family-specific wording underneath.

How much employees see. Some companies show only titles. Others show levels and the bands attached to them. Aon's 2025 study found that 61% of organizations had salary ranges but did not share them with employees. Each choice is defensible. Showing levels without bands, or bands without levels, tends to raise the very questions the structure was meant to settle.

What to do with people the structure does not fit. Placing jobs on levels usually shows some people in a different place from where their title suggested. Whether titles change, pay changes or the person keeps both for a while is a call about fairness and trust. It shapes how employees see the whole project.

The law and the numbers

As of 20 October 2026, these are the points we checked that bear on how levels, grades and bands fit together.

The EU directive expects pay structures that compare jobs. Directive (EU) 2023/970 defines work of equal value and categories of workers (Article 3). It requires pay structures that make it possible to assess whether workers are in a comparable situation regarding the value of work, using objective, gender-neutral criteria that include skills, effort, responsibility and working conditions (Article 4). Employers with 250 or more workers report on the gender pay gap by 7 June 2027 and yearly after that; employers with 150 to 249 workers by 7 June 2027 and every three years; employers with 100 to 149 workers by 7 June 2031 and every three years (Article 9). A gap of at least 5% in any category of workers that the employer cannot justify on objective, gender-neutral criteria triggers a joint pay assessment (Article 10) [1].

Transposition is uneven. The directive was due in national law by 7 June 2026. A law firm tracker reported on 1 July 2026 that four member states had fully transposed it and that there was no extension [2].

Job evaluation guidance is new. The European Commission and the European Institute for Gender Equality published guidelines and toolkits on gender-neutral job evaluation in March 2026. We have read them only through a law firm's summary, which says they break the four criteria into subfactors [3]. The guidelines are voluntary.

US equal pay law looks at the work, not the title. The EEOC states that jobs need not be identical but must be substantially equal and that job content, not job titles, decides that [4].

Posting laws assume the structure exists. Washington's guidance asks for a range set before posting and, where one ad covers several titles, a range for each title [5]. Massachusetts lets current employees ask for the pay range of the job they hold [6].

Most companies have ranges they do not show. Aon's 2025 Global Pay Transparency Study found 61% of organizations used salary ranges without communicating them to employees and 8% did not use ranges at all [7].

Our view

We think the order matters more than the vocabulary. Size the jobs first, in levels written down in plain words. Add grades only when the company needs to compare jobs across families. Build them by comparing jobs rather than market rates. Attach bands last, to the frame the company has chosen.

Most structure problems we would expect to find in a company of a hundred or two hundred people are not about pay levels. They are about three tools built by three teams for three reasons and never connected. Fixing the pay without connecting the tools only resets the argument.

The test of a structure is simple. When anyone asks why a job is paid what it is, the answer should start with how big the job is. It should never start with what the job is called.

Sources

  1. Directive (EU) 2023/970 on pay transparency, Articles 3, 4, 9 and 10 (EUR-Lex), checked 2026-10-20
  2. Lewis Silkin, EU Pay Transparency Directive: 2026 employer compliance (1 July 2026), checked 2026-10-20
  3. Lewis Silkin, EU guidelines for gender-neutral job evaluation (27 March 2026), secondary summary, checked 2026-10-20
  4. US Equal Employment Opportunity Commission, Equal Pay/Compensation Discrimination, checked 2026-10-20
  5. Washington L&I, Administrative Policy ES.E.2, Job Posting Requirements (issued 3 December 2025), checked 2026-10-20
  6. Massachusetts Attorney General's Office, Pay Transparency in Massachusetts (FAQ 9), checked 2026-10-20
  7. Aon, 2025 Global Pay Transparency Study, checked 2026-10-20

Can market data set your salary bands?

Benchmark data shows what others pay. The midpoint is still your choice. Five ways teams let the data decide and what a band you can explain rests on.

How many job levels do you need?

How many job levels a company needs depends on the work, not the headcount. Five traps in setting the count and what a sound ladder looks like.

Paid above the band maximum: Now what?

When pay sits above the band maximum, the answer depends on why. Five ways companies mishandle it and four honest options that hold up.

See Resources for every guide and the self-check.