All Posts

Pay Scales & Salary Grades: How to Build a Compensation Structure

The Fabric Team
July 31, 2026
•
15 min read

Most compensation problems inside a growing company come down to inconsistency. Two engineers with similar experience end up 22% apart because one negotiated harder in year one, one manager quietly stretched an offer to close a candidate, and no one has looked at the pattern since. A pay scale exists to prevent exactly that.

A pay scale is a structured framework that groups jobs into grades and assigns each grade a defined salary range with a minimum, midpoint, and maximum. It ties pay to the value of the job and to the external market, rather than to how well a candidate happened to negotiate or how much budget a hiring manager had that quarter. According to SHRM's research on salary range structure practices, 78% of organisations with formal structures use traditional pay ranges, and 94% use market data to design them.

This guide covers what a pay scale actually is, how it differs from a salary grade or pay band, how to build one from scratch, how to run the benchmarking exercise that feeds it, and where a pay structure quietly touches hiring, particularly at the eligibility-screening stage where Fabric operates.

Table of contents

What is a pay scale?

A pay scale is the internal system a company uses to decide what every job in the organisation should pay. It works by grouping jobs of similar value into a small number of grades, and giving each grade a salary range that a person in any job at that grade can be paid within. When you hear that a role is "at Grade 7" or "in Band 4," what the company means is: the job has been evaluated, mapped to a specific tier of the internal structure, and any offer or raise has to sit somewhere between that tier's minimum and its maximum.

The point of the structure is defensibility. When a manager asks why one person earns more than another, or a regulator asks whether pay is administered consistently, the pay scale is the answer. Without one, every offer becomes a one-off decision, and the pattern of those decisions is almost always unequal in ways the company did not intend.

Pay scale, salary grade, pay band, paygrade: what's actually different?

These four terms get used interchangeably in most conversations, and that is fine in a hallway. In an HR system or a policy document it matters more.

  • Pay scale is the whole framework: every grade, every range, and the rules for how people move through it.
  • Salary grade (sometimes written as paygrade as one word) is a single tier inside the pay scale. Grade 5 is one row of the structure. It holds a group of jobs the company treats as equivalent in value.
  • Pay band is a specific style of salary grade, usually wider than a traditional grade. Traditional grades have a 30 to 50% spread from minimum to maximum. A broadband can be 100% or more, giving managers wider discretion but weaker pay control. SHRM's data on structure practices puts broadband adoption at around 11% of organisations, compared to 78% still using traditional narrow-range grades.
  • Salary range is the actual minimum, midpoint, and maximum dollar figures attached to a grade or band.

Short version: the pay scale is the shelf, the grade is one row on the shelf, and the range is the width of that row.

The three components of a pay scale

Every pay scale reduces to three moving parts.

Grades. The number of tiers you need is a function of how many meaningfully distinct levels of work exist in the company. A 40-person startup might need 5 grades. A 5,000-person enterprise might need 18. More grades give tighter control and clearer progression; fewer grades give managers flexibility and reduce administrative overhead. Neither is right by default.

Ranges. Each grade needs a minimum, a midpoint, and a maximum. The midpoint is usually anchored to a market benchmark (see the benchmarking section below), and the minimum and maximum are calculated from a chosen range spread, typically 30% for lower grades, widening to 50% or more for senior grades where individual variation is larger.

Steps or progression rules. Some structures, especially in the public sector, use fixed steps inside each grade so that progression is mechanical: step 1, step 2, and so on. Private employers more often use discretionary progression with rules like a minimum time-in-grade before promotion consideration, or a policy that raises within a grade cannot exceed a certain percentage per cycle.

How to build a pay scale from scratch

Building one the first time is a project measured in weeks, not days. The order matters.

1. Write clear job descriptions and evaluate every role. You cannot grade jobs you have not defined. Every role needs a description that captures scope, decision authority, required experience, and specialist skill. Job evaluation methods range from simple ranking (small companies) to point-factor systems (larger organisations), but the output is the same: a defensible ordering of jobs from least to most complex.

2. Group jobs into grades. Bundle jobs of similar value into a small number of grades. A common test: if two jobs would command similar pay in the outside market and require similar levels of experience and impact, they belong in the same grade. Cluster the evaluated jobs and draw the lines where the natural gaps appear.

3. Benchmark against the external market. For each grade, pick a handful of benchmark jobs that are common enough to have solid survey data. Match those to a published compensation survey (see the next section) at the 50th percentile as a default. This gives you the target midpoint for each grade.

4. Define range spreads and calculate min and max. Decide the range spread by grade. A typical convention is a 30% spread at the lowest grade widening to 50% at senior levels. The minimum equals the midpoint divided by (1 + spread ÷ 2), and the maximum equals the midpoint multiplied by (1 + spread ÷ 2). That gives you the full range for each grade.

5. Set your compensation philosophy per grade. Decide, grade by grade, whether the company pays at market (50th percentile), below market (25th percentile, common for early-career roles), or above market (75th or 90th percentile, common for hard-to-fill senior technical roles). This is a strategic call, not an accident, and it should be written down.

6. Write the administration rules. Time-in-grade minimums, promotion criteria, out-of-range approval process, cost-of-living adjustment rules, and re-benchmarking cadence. Most organisations re-benchmark annually; SHRM's data shows 17% do it every two or three years, which is the outer limit before drift becomes serious.

Salary benchmarking: how to actually run it

Salary benchmarking is the process of finding out what other employers pay for a comparable job, then deciding where your grade should sit against that market data. The temptation is to skip the paid surveys and use free sources; the risk is that free sources are self-reported, geographically messy, and rarely job-matched, which is exactly what makes them dangerous as a primary benchmark.

Reliable survey providers include Mercer, WTW, Aon, Radford (Aon's tech-heavy cut), and Culpepper. What you pay for is job-matching methodology: their analysts read your job descriptions and match each one to a specific survey job, so your Software Engineer II is compared to other companies' equivalent Software Engineer II, not to the average of every software engineering role reported anywhere.

The benchmarking pass itself is straightforward once the survey is in hand.

  1. Select 15 to 25 benchmark jobs that cover every grade. These are your anchor points.
  2. Match each one to the survey using job scope and level, not job title.
  3. Pull the 50th percentile total cash compensation (base + short-term incentive) for each match, cut by industry, company size, and geography relevant to the role.
  4. Compare to your current pay for people in those jobs. The gap tells you how far your existing pay drifts from the market.
  5. Set the target midpoint for each grade based on your compensation philosophy for that grade (see step 5 in the build section above).

Do this once and you have a defensible market anchor. Do it every year and you catch pay compression and market drift before they turn into offer-rejection or attrition problems.

Paygrade math: midpoint, range spread, compa-ratio

Three numbers are worth knowing well.

Midpoint. The target market rate for a grade, typically set to the 50th percentile of the survey match unless the compensation philosophy says otherwise. It is the anchor. Everything else is calculated from it.

Range spread. The distance from minimum to maximum, expressed as a percentage of the minimum. A 40% spread means the maximum is 40% above the minimum. Formula: (max − min) ÷ min. Junior grades typically use 30 to 40% spreads, senior grades 50% or more.

Compa-ratio. An individual employee's pay divided by their grade's midpoint. A compa-ratio of 1.0 means the employee is paid at market for their grade. Below 0.80 usually means someone is being underpaid relative to their grade and should either be raised or reclassified. Above 1.15 without a promotion path usually means the person is being paid for a role bigger than their nominal grade, and the grading itself may be wrong.

Track compa-ratios by grade, by manager, and by demographic group. It is one of the fastest ways to spot both individual pay inequity and structural grade drift.

Pay compression and how it happens

Pay compression is what you get when new hires come in at rates close to, or higher than, tenured employees in the same grade. It happens for two reasons, and both are structural.

The first is market drift. Salary structures drift out of date fast, sometimes within 12 months in tight labour markets. If your grade midpoints have not been re-benchmarked in two years and the market for that grade has moved 8% a year, a new hire at market rate now sits at a compa-ratio well above someone hired at the old midpoint who has received modest raises since.

The second is uneven raise policy. If merit budgets are 3% while the market is moving 5%, everyone already in a grade quietly falls behind the market until they leave and get replaced at a higher rate. The remedies are unglamorous: re-benchmark on a fixed cadence, and separately budget for compression-fix adjustments when the analysis surfaces them.

Pay transparency and what your structure has to expose

A growing number of jurisdictions require employers to publish salary ranges on job postings and, in some cases, share the range on request with existing employees. Colorado, California, New York, Washington, and Illinois are among the US states that already require it in some form. The EU Pay Transparency Directive brings similar rules across the bloc. For a public-sector reference point on how structured, published pay ranges look in practice, the US Office of Personnel Management publishes its General Schedule and locality pay tables in full each year.

Two implications for a pay scale.

First, the ranges have to be defensible on their face. A range like "$60,000 to $180,000" is technically transparent and functionally useless; regulators and candidates read it as evasive. A range that reflects the actual grade the role sits in, and is narrow enough to mean something, is what compliance is really asking for.

Second, internal ranges become external artefacts. Once ranges are on postings, current employees can read them. If a tenured employee in the grade is sitting below the posted range for a new hire, that is a compression problem you will hear about within a week of posting. Get the structure right before the ranges go public, not after.

Where pay structure meets hiring

A pay scale is a compensation artefact, but it also shapes hiring in ways that are usually invisible until they fail.

Every role in a well-defined pay scale has a grade, and every grade has eligibility criteria: minimum years of experience, required qualifications, sometimes location tiers. Those criteria are exactly what recruiters filter against at the top of the funnel. When they are vague or unwritten, screening becomes inconsistent and offers get made to candidates who do not actually fit the grade, which is where compression and out-of-range approvals accumulate.

This is where Fabric's Round 1 screening fits into the compensation picture. Fabric's Interview Engine screens candidates on the exact eligibility parameters attached to the role: budget, location, and years of experience. The recruiter still decides who to hire, but they get a shortlist where every candidate has already been checked against the grade's structural requirements, not just against a keyword-matched resume. On bulk hiring for well-defined grades, this closes the gap between a clean pay structure on paper and messy, out-of-range offers in practice.

Stop screening 5,000 resumes to fill 50 seats.
Fabric runs Round 1: eligibility screening on budget, location, and YOE, plus a live AI interview. See it on your roles.
Book a 30-minute walkthrough

*This article is for informational purposes only. Fabric's Interview Engine screens, scores, and records Round 1 interviews; it does not make the final hiring decision. The recruiter or hiring panel using Fabric remains responsible for all hiring decisions.*

Common pay scale mistakes

A short list of the failures that show up most often when a structure is audited a year or two after it is built.

  • Too many grades. A 15-grade structure inside a 200-person company creates administrative work with no control benefit. Fewer, wider grades usually work better at small scale.
  • Ranges too wide. A grade that spans 100% from min to max stops functioning as a control; it is a broadband in denial. Either commit to broadbanding openly or narrow the ranges.
  • No re-benchmarking cadence. Structures set once and left alone drift into irrelevance within 18 months. Book the annual pass on the HR calendar.
  • Compensation philosophy not written down. If nobody can name where the company chooses to pay against market by grade, offers get made to whichever percentile the recruiter thought was reasonable that day.
  • Grade criteria never enforced at hiring. The structure says Grade 6 requires 8 years of experience, and yet a 4-year candidate keeps getting hired into Grade 6 because "we needed the skill." Either change the grade criteria or hold the line.
  • Ignoring pay transparency in structure design. Ranges that were fine internally can be indefensible when published. Design as if they will be public, because increasingly they will be.

Related Posts

FAQ

What is a pay scale?

A pay scale is a structured framework that groups jobs into grades and assigns each grade a defined salary range with a minimum, midpoint, and maximum. It ties pay to job value and market data rather than to individual negotiation.

What is the difference between a pay scale and a salary grade?

A pay scale is the overall framework of grades and ranges across the organisation; a salary grade is a single tier inside it that holds jobs of similar value with one shared range. The pay scale is the shelf; the salary grade is one row on the shelf.

What are time-in-grade requirements?

Time-in-grade rules set a minimum period an employee must spend at one grade before being eligible to move up. They exist to prevent uncontrolled grade inflation and to give managers a defensible timeline for progression conversations.

How do I benchmark salaries for a new pay scale?

Pick 15 to 25 benchmark roles that cover every grade, buy a published market survey for your industry and geography, and match each role at the 50th percentile as a default anchor. Then decide by grade whether you want to pay at, below, or above market.

What is the best website to check salaries?

For structured pay design, licensed surveys from Mercer, WTW, Aon, or Radford are the professional standard because their data is job-matched and cut by industry, size, and geography. Free tools like Glassdoor, Levels.fyi, and PayScale are useful for a sanity check, not as a primary benchmark.

Where can I find pay ranges for different roles?

For US federal jobs, pay ranges are published by OPM on opm.gov; for private-sector roles, ranges come from your own internal structure once you have built one, informed by a paid compensation survey. Jurisdictions with pay transparency laws increasingly require ranges to appear on job postings themselves.

Try Fabric for one of your job posts