How to Build a Job Band Structure: The Complete Guide for SMB HR Teams
Why Your Current Compensation Approach Will Hurt You in 2026
Picture this: It's a Tuesday morning and you've just received a pay inquiry from a senior accountant who noticed that a newly posted role at your company — the same title she held three years ago — shows a salary range $14,000 above her current pay. She's not unreasonable. She just wants to understand. You open the spreadsheet you inherited from the last HR manager, and the formulas in column F reference a tab that no longer exists.
This scenario plays out thousands of times a year at companies between 25 and 250 employees. There's no malice involved — just the accumulated weight of ad hoc hiring decisions made without a coherent job band structure underneath them. Individual managers negotiated what they needed to close a candidate. Ranges were never written down. Now, with pay transparency laws spreading rapidly across the US and Canada, those informal practices are a compliance liability — and a retention liability.
This guide gives you a practical, step-by-step method for building a defensible job band structure from scratch. You'll leave with a clear picture of how job families, levels, min/mid/max salary bands, and benchmarking data fit together into a framework that survives a pay equity audit, satisfies a pay transparency posting requirement, and holds up in a conversation with your most tenured employee.
What a Job Band Structure Actually Is (and Why It's Not Just a Salary Table)
A job band structure is a two-dimensional framework that organizes every role in your company along two axes: what kind of work it is (the job family) and how much scope and complexity the role carries (the level). Every intersection of family and level maps to a salary band — a defined minimum, midpoint, and maximum pay range for roles at that combination of type and level.
If you've ever heard the terms "compensation band structure," "salary band framework," or "pay band setup," they all describe the same underlying architecture.
Four concepts do most of the structural work:
Job family. A cluster of roles that perform related work and progress along a recognizable career path. "Finance," "Operations," "Software Engineering," and "Customer Success" are common families. A company with 80 employees might have eight to twelve families. Understanding where to draw those boundaries is covered in detail in our guide to job families vs. job levels.
Job level. A defined stage within a family, characterized by increasing scope, autonomy, and accountability. Individual-contributor tracks typically run four to six levels (IC1 through IC5 or IC6); management tracks run two to four (M1 through M3 or M4). The critical discipline is that levels are defined by the work itself — not by tenure, title inflation, or how much a manager likes someone. A clear job leveling framework for a small company is the precondition for bands that actually hold. See our guide to building a job leveling framework.
Salary band. The pay range assigned to a level. A band has three structural points: the minimum (the floor below which the company will not pay for this scope of work), the midpoint (the market anchor, typically your target competitive position), and the maximum (the ceiling above which a pay increase requires promotion rather than a merit raise). The math behind those three points is explained fully in our min/mid/max band math guide.
Band spread (range width). The percentage distance from minimum to maximum, expressed relative to the midpoint. A 50% spread on a $65,000 midpoint produces a minimum of $48,750 and a maximum of $81,250. Wider spreads reward long tenure within a level; narrower spreads create more urgency to promote. Our band spread and range width guide covers when to widen or tighten.
These four elements combine into a structure that answers the two questions every employee and manager will eventually ask: "What does this role pay?" and "What has to change for that number to go up?"
For a deeper look at what job bands are before building your own, start with our foundational explainer.
Step 1 — Inventory Your Roles and Identify Job Families
Before you can build bands, you need to know what you're bandying. Pull a complete list of every active role from your HRIS or payroll system: job title, department, current pay, and hire date. If your titles are inconsistent — "Sr. Accountant," "Senior Accountant," "Acct Sr." — normalize them now. You are building a structure, and a structure needs clean inputs.
Group the normalized titles into job families by asking a single question: Would a strong performer in Role A be a plausible candidate for Role B, and vice versa? Roles that share a career pipeline belong in the same family. Roles that are functionally adjacent but require distinct expertise (a Staff Accountant and an FP&A Analyst, for example) may belong in the same broad family or in two adjacent sub-families, depending on how your organization uses them.
Practical limits: most SMBs with 50–200 employees find 8–15 families covers the entire org without creating so many narrow families that the structure becomes unmanageable. If you discover you have 30 job families at 80 employees, the real problem is title proliferation — that's worth cleaning up as part of this project.
What you'll produce: A clean role inventory organized into a provisional family list. Save it — this becomes the row headings on your job architecture grid.
Step 2 — Define Levels Within Each Family
With families identified, define the levels inside each one. The most durable approach is to write a brief level profile for each step — three to five sentences describing the scope of work, the nature of decisions the person makes independently, and what distinguishes this level from the one above and below.
A common SMB level structure looks like this:
| Level | Individual Contributor | Management |
|---|---|---|
| 1 | Entry — executes defined tasks under close supervision | — |
| 2 | Developing — executes with growing independence | — |
| 3 | Fully proficient — owns a domain or workstream | First-line manager |
| 4 | Senior — leads complex work, influences peers | Manager with cross-functional scope |
| 5 | Staff / Principal — org-wide impact, rare | Senior manager / Director |
Not every family needs every level. A 90-person company may have only three levels in its Facilities family and five in its Engineering family. That's correct — the structure follows the actual work.
Common mistake to avoid: defining levels primarily by years of experience. Tenure is a proxy. What you want is scope and accountability. A five-year employee doing Level 2 work is a Level 2 employee. A two-year employee carrying Level 4 responsibilities is a Level 4 employee. Basing your levels on scope rather than tenure is what makes the structure defensible in a pay equity challenge.
Step 3 — Anchor Each Band to External Market Data
This is where the structure connects to the real world. A salary band that isn't tethered to external wage data is just internal math — it tells you nothing about whether you can actually hire or retain at those numbers.
The most credible free source for US SMBs is the Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) program. OEWS publishes annual wage estimates for approximately 830 occupations across the nation, all 50 states, and roughly 530 metropolitan and nonmetropolitan areas, drawn from a sample of approximately 1.1 million establishments. Every figure is publicly available, methodologically transparent, and accepted as authoritative in pay equity proceedings.
The OEWS releases wage percentiles — 10th, 25th, 50th (median), 75th, and 90th — for each occupation and geography. Most SMBs set their band midpoint at the 50th percentile (market median) for a "meet the market" philosophy, or at the 60th–75th percentile to compete above the median. The choice depends on your compensation philosophy — not on what seems generous.
A worked example (illustrative): Suppose the BLS OEWS May 2025 release shows a median annual wage of $65,000 for a given accounting occupation in your metro area. You decide to meet the market at the 50th percentile, so your midpoint is $65,000. With a 50% spread, your band runs from $48,750 (minimum) to $81,250 (maximum). That's the formula: minimum = midpoint ÷ 1.25; maximum = midpoint × 1.25. (The actual May 2025 BLS release shows an all-occupation annual mean wage of $69,770 — your specific SOC code and geography will produce a different figure; always pull directly from the OEWS data tool.)
For Canadian operations, Statistics Canada's Table 14-10-0417-01 provides NOC-based wage percentiles by province and census metropolitan area under the Open Government Licence, and is the appropriate anchor for Ontario and British Columbia bands. Our full BLS OEWS benchmarking guide walks through the data-pull process step by step.
Document your source, the release date, the SOC or NOC code, and the geography for every midpoint. This documentation becomes your audit trail — proof that ranges were set by method, not by intuition.
Step 4 — Build the Min/Mid/Max for Every Band
With a market-anchored midpoint for each level in each family, you're ready to build out the full band. The three decisions you need to make:
1. What spread (range width) will you use? Spreads typically vary by level. Entry and developing roles (Levels 1–2) often carry narrower spreads (30–40%) because there is less legitimate variance in the work at those levels. Senior and staff roles (Levels 4–5) often carry wider spreads (50–70%) because the difference in impact between a competent Level 4 and an exceptional one is large. Management bands often sit in the 40–60% range. These are common practices; your spread choices should be deliberate and documented.
2. How will bands relate to one another (band overlap)? Adjacent-level bands almost always overlap. Some overlap is healthy — it means a highly paid Level 3 employee earns more than a newly hired Level 4, which is realistic. Excessive overlap (a Level 2 maximum exceeding a Level 4 minimum, for instance) erodes the incentive to advance. A common design target: adjacent bands overlap by 25–40% of the lower band's range.
3. What is your pay structure review cycle? External wages move. A band built on 2022 OEWS data is likely below market by 2025. Build an annual or biennial review into your process from day one. The review does not require rebuilding the structure — it means pulling updated OEWS figures, recalculating midpoints, and adjusting band boundaries accordingly.
Once these decisions are made, the arithmetic is mechanical. Build a simple grid: families across columns, levels down rows, each cell containing the minimum, midpoint, and maximum. Our guide to creating salary bands covers the construction process in full.
Step 5 — Map Every Current Employee to a Band
A band structure that exists only on paper changes nothing. The next step is slotting every current employee into a level and checking where their pay falls within the corresponding band.
Three outcomes are possible:
Below the band minimum (green circle, or "below range"). This is a compliance and retention risk. An employee paid below the minimum of their band is, by definition, underpaid relative to your stated market position. In a pay transparency state, you'll be required to post the range — and a current employee outside it will notice. Prioritize these employees for off-cycle adjustments.
Within the band (healthy). No immediate action required, though you should still track where in the range each person sits. The ratio of an employee's actual pay to the band midpoint is called the compa-ratio — a 1.00 compa-ratio means the person is paid exactly at midpoint; a 0.85 means 85% of midpoint. Compa-ratios help you see patterns in pay distribution across demographics.
Above the band maximum ("red circle," or "above range"). These employees are not immediately at risk — they should not have pay cut — but they are typically excluded from merit increases until the band is adjusted upward to absorb them, or until they are promoted. Document this explicitly. Do not let "above range" become invisible.
This mapping exercise will surface equity issues you didn't know you had. That is the point. It is much better to find them in a structured review than in a regulator complaint.
Step 6 — Prepare for Pay Transparency Posting Requirements
Once your bands exist, they become the source of truth for pay range disclosures. This matters urgently: at least 16–18 US states (depending on whether individual locality laws are counted separately) have enacted statewide pay transparency laws as of 2026, according to commonly cited analyses. One 2026 assessment covering all jurisdictions — including individual city and county laws — counted 25 separate jurisdictions where pay transparency requirements have been enacted.
Among the most consequential provisions for SMBs:
California requires employers with 15 or more employees to include a pay scale in all job postings. Each posting that lacks a required range is treated as a separate violation — a single open role simultaneously posted on five platforms can generate up to five distinct penalties. Civil penalties run from $100 to $10,000 per violation, with escalating fines for subsequent violations. California's SB 642, effective January 1, 2026, sharpened the definition of "pay scale" to mean a good-faith estimate of what the employer reasonably expects to pay upon hire, and extended the statute of limitations for willful violations from three years to six. See our full pay transparency compliance hub for state-by-state detail.
Colorado imposes fines of $500 to $10,000 per violation of its Equal Pay for Equal Work Act posting requirements, with each non-compliant posting treated as a separate violation.
Ontario brought pay transparency requirements into force on January 1, 2026 for employers with 25 or more employees. Posted ranges must not exceed a $50,000 spread and apply to roles paying up to $200,000. Administrative fines under the Employment Standards Act can reach up to $500,000. Employers must retain postings, application forms, and interview notifications for a minimum of three years after a posting is removed.
British Columbia requires all provincially regulated employers to include expected pay or a pay range in every job posting as of November 1, 2023. Critically, open-ended ranges are not permitted — "up to $30/hr" or "$20/hr and up" are both non-compliant.
A job band structure does more than organize pay internally — it becomes the compliance infrastructure that makes legally required pay-range disclosures possible without a scramble every time a role opens.
The practical implication: without a band structure, every new job posting requires someone to decide in real time what range to disclose. With a band structure, that decision is already made. You pull the band for the relevant family and level, confirm it reflects current market data, and post it. The structure turns a recurring compliance task into a routine lookup.
How to Keep the Structure Current: Governance and Audit Trails
A job band structure is a living document, not a one-time project. The organizations that build bands and then fail to maintain them often end up in worse shape than those who never built one — because they have a documented structure that no longer reflects reality, which is a more visible problem than an informal one.
Four governance habits prevent structural decay:
Annual market-data refresh. Pull updated OEWS percentiles each spring after the prior-year release publishes (typically in April or May for May-reference data). Compare the new medians against your current midpoints. If your midpoints have fallen more than 5–8% below the updated median, a band adjustment is warranted.
Documented change log. Every time a band minimum, midpoint, or maximum changes — and every time an employee's pay changes — record the date, the reason, who approved it, and the market reference that justified it. This is your audit trail. In a pay equity investigation or an employment standards complaint, a documented audit trail showing consistent, market-referenced decision-making is your best defense. Our guide to maintaining an audit trail for compensation changes covers the record-keeping requirements.
Promotion and off-cycle increase protocols. Define in writing how pay changes when someone is promoted (the typical approach is to move to the minimum of the new band, or to a compa-ratio in the new band that matches their compa-ratio in the old one, whichever is higher). Define the approval path for off-cycle increases. Without written protocols, managers make ad hoc decisions that re-introduce the equity problems the structure was built to eliminate.
Pay equity review cadence. At least annually, run a compa-ratio analysis cut by gender, race/ethnicity (where you have the data), and tenure. You are looking for patterns, not isolated cases — a systematic gap between demographic groups at the same level is a structural problem that needs a structural response. A single job band structure does not guarantee pay equity, but it creates the analytical precondition for finding and correcting disparities.
Common Mistakes SMB HR Teams Make Building Their First Structure
Starting with titles instead of work. Title inflation is endemic at SMBs. "Senior" gets attached to roles as a retention tool, not because the scope changed. Build levels around what the work requires, then decide what titles attach to those levels — not the reverse.
Setting midpoints from internal pay history. If your current pay practices are unstructured, using current employee pay to anchor your midpoints will encode existing inequities into the structure. Always anchor on external data first; use internal pay as a check, not a starting point.
Building too many bands. A 50-person company does not need 40 salary bands. Proliferation creates administrative overhead and, paradoxically, makes individual pay decisions harder — too many narrow bands mean more edge cases and more exceptions. Eight to fifteen families with three to five levels each covers most SMB organizations completely.
Treating the structure as confidential. In a pay transparency environment, communicating your band structure to employees is both a legal requirement in many jurisdictions and a retention benefit. Employees who understand the structure — how levels are defined, where their pay sits, what it takes to advance — report higher trust and engagement than those who work in a black box. The research on what motivates the decision to include salary ranges in job descriptions reflects this: 44% of hiring managers surveyed believe including salary ranges in postings will be the most effective way to attract talent in 2026.
Skipping the compensation philosophy step. A band structure is the implementation of a compensation philosophy. If you haven't articulated your philosophy — what percentile you're targeting, how you weight base versus variable, how you handle geographic differentials — the structure will have no logical foundation. Our compensation philosophy guide covers how to write one before you build.
Building the Structure: Tooling Considerations
The most common tool for a first-generation band structure is a spreadsheet. It works, up to a point. Research consistently shows that spreadsheets used in business decision-making carry a high rate of formula errors — one analysis found that 94% of business spreadsheets used in decision-making contain errors. When those spreadsheets are your compensation structure, errors have direct financial and compliance consequences: a formula referencing the wrong cell can produce a band minimum higher than the midpoint, or generate a disclosure range that doesn't match your stated philosophy.
Beyond errors, spreadsheets offer no audit trail, no automated benchmarking refresh, no export to job-posting formats, and no built-in compliance guardrails. For a company with fewer than 25 employees and a simple role inventory, a well-built spreadsheet may be sufficient. For a company in a pay transparency jurisdiction with 50 or more employees — or any company anticipating growth — the maintenance cost and compliance risk of a spreadsheet-based structure tend to exceed the cost of purpose-built tooling. We've written a full comparison of Job Band Builder versus spreadsheets if you want to look at that tradeoff specifically.
If you're ready to move your structure off a spreadsheet and into a tool designed for it, you have two options with us.
The Job Band Structure Builder is a structured digital download — a guided workbook that walks you through every step in this guide, pre-loaded with OEWS-anchored benchmark prompts and a compliant min/mid/max template. It's a good fit if you want a one-time build you control in your own environment.
If you want continuous benchmarking updates, a built-in audit trail, and pay-transparency-ready exports, Job Band Builder's SaaS platform handles the ongoing maintenance that a one-time build can't — including automatic reminders when OEWS data refreshes and export formatting for compliant job postings.
Your Job Band Structure Checklist
Use this list to confirm your structure is complete before any role opens for external posting:
- All active roles inventoried and normalized
- Roles grouped into job families with documented rationale
- Level profiles written for each level in each family (scope-based, not tenure-based)
- Midpoints anchored to external wage data (BLS OEWS or Statistics Canada), with SOC/NOC code and release date documented
- Band spread chosen and documented for each level tier
- Min/mid/max calculated for every family × level combination
- All current employees mapped to a band and level; compa-ratios calculated
- Below-range employees identified and remediation plan in place
- Above-range employees identified and exclusion-from-merit-increase policy documented
- Pay transparency requirements confirmed for every jurisdiction where you post roles
- Promotion and off-cycle increase protocols written and approved
- Change log / audit trail process established
- Annual market-data refresh scheduled
A job band structure is not a bureaucratic exercise. It is the foundational infrastructure that makes fair, consistent, and legally defensible compensation decisions possible at scale — even at 50 or 80 or 150 employees. The companies that build it early spend far less time on pay inquiries, pay equity remediation, and compliance scrambles than those who wait until a law, a lawsuit, or a resignation forces the conversation. ```
Ready to go beyond the guide?
Build a defensible, BLS-benchmarked band structure in under 30 minutes.