Wage bands in a spreadsheet or in software for a company under 200
A spreadsheet is enough for wage bands when you have fewer than about 15 jobs, one location and no posting law. Software pays for itself once you have more jobs, a pay transparency state, or anyone asking where a number came from. The deciding costs are not the arithmetic, which Excel does well. They are sourcing and aging the market data, keeping an audit trail, and catching drift between bands and posted ranges.
If you are the person who owns pay at a company of 10 to 200 people, you have probably already started wage bands in a spreadsheet, or been handed one by a predecessor. This page helps you decide whether to keep going or buy something. It builds one example by hand so you can see what the work is, then prices the alternatives.
A three band hourly ladder built from BLS data
Take the May 2025 national wage percentiles for Human Resources Specialists from the BLS Occupational Employment and Wage Statistics program: P25 $58,610, median $75,940, P75 $99,380 a year. Divide by 2,080 hours and the median is $36.51 an hour. Your pay applies in January 2027, 20 months after the reference period, so age it at 3.5 percent a year, a factor of 1.059. The aged median is $38.70 an hour. That is the midpoint of the middle band.
Now build a ladder around it. Set band midpoints 15 percent apart, so the lower band midpoint is $38.70 divided by 1.15, $33.65, and the upper is $38.70 times 1.15, $44.51. Give each band a spread of 15 percent either side of its midpoint.
| Band | Minimum | Midpoint | Maximum | Annual at midpoint |
|---|---|---|---|---|
| Band 1 | $28.60 | $33.65 | $38.70 | $70,000 |
| Band 2 | $32.90 | $38.70 | $44.51 | $80,500 |
| Band 3 | $37.83 | $44.51 | $51.18 | $92,600 |
That is nine numbers from one data point, and the process hid three decisions: the aging rate, the midpoint step and the spread. In a spreadsheet each is a cell someone has to remember. Notice the overlap. Band 1 tops out at $38.70, the same as the Band 2 midpoint, so a long-serving Band 1 employee can earn what a new Band 2 hire earns. That is intended, and it is worth writing down.
What a spreadsheet does well and where it breaks
The arithmetic above is trivial in Excel. What breaks is everything around it.
- Sourcing. Someone downloads the BLS tables, finds the right occupation code for each job and re-keys the percentiles. For 12 jobs that is an afternoon. Do it for 40 and it is days, with typos you will not find.
- Aging. The reference date is a year behind. If nobody applies an aging factor, every midpoint is stale on day one, and nobody remembers which rate was used last year.
- Audit trail. When an employee or a state agency asks where a range came from, a spreadsheet shows a number. It does not show the source, the date or who changed it.
- Posting drift. Bands change in January, job posts are written in March from last year's file. In Colorado, California, Washington and New York the posted range must be a good faith estimate, so the mismatch is a compliance problem and not only a tidiness one.
- Handoffs. The spreadsheet lives with the person who built it. When they leave, the logic leaves with them.
Spreadsheet or software: a break-even test
| Your situation | Spreadsheet | Software |
|---|---|---|
| Under 15 jobs, one state, no posting law | Enough | Optional |
| 15 to 60 jobs, one posting law state | Two to three days per cycle, risk of drift | Pays back in one cycle |
| Multiple states or remote hiring | Hard to keep consistent | Strongly favored |
| Hiring ten or more people a year | Offers drift from bands | Favored |
| Executives and equity heavy roles | Not enough data | Needs a licensed survey either way |
Put a price on your own time to make the test concrete. If you spend two days a year on bands at a loaded cost of $60 an hour, that is $960, already more than the $588 a year WageList costs. The compensation benchmarking software page shows the same cost comparison against surveys and consultants. The comparison does not change if you are a one-person HR team. It improves, because you have no one to review the file.
What to check before you move a spreadsheet into software
- List every job and its current band. Jobs without a band are the first thing software will surface.
- Decide your target percentile. The median is the default, and your compensation philosophy may say the 60th.
- Decide the spread and the step between bands. The guide on how wide a salary range should be covers the 15 and 20 percent rules.
- Pull current pay for every employee, so the first thing you see is the compa-ratio of each person against the new band.
A word about the broader point. Companies that run on spreadsheets tend to do the same with other chores, such as classifying imported goods. If that is you, a tool like an AI lookup for customs codes in plain English removes the same kind of manual lookup. The principle is identical: when a lookup repeats every quarter and the answer has to be defensible, stop doing it by hand.
How WageList builds wage bands
WageList anchors each job on BLS wage data, ages it to your pay date at a stated rate, sets the band and keeps the source and date on the record. It costs $99 a month or $588 a year for teams of 10 to 200, with no pay data to submit. It does not replace a survey for executives or equity, and it reports base wages only. See the salary bands page, the salary benchmarking tool, and how to create salary bands for the method in more detail.
Sources: U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics, May 2025 national estimates for Human Resources Specialists (13-1071), read from the BLS public data API. The aging rate and band spread are illustrative inputs.