The Solo HR Generalist's Playbook for Managing Compensation

You Are the Comp Team — Now What?

Picture this: it is the last week of October, a new pay-transparency law in your state takes effect in sixty days, and your CEO has just forwarded a candidate offer letter with a question mark where the salary should be. You are the HR function — recruiter, benefits administrator, policy writer, and now, apparently, the compensation analyst. There is no one to hand this off to.

If that scenario feels familiar, you are in the right place. Being a solo HR generalist managing compensation is one of the most technically demanding positions in the profession, because you are expected to produce work that larger companies staff entire teams to handle — salary bands, leveling frameworks, pay-equity analysis, compliance disclosures — while simultaneously running every other HR process. The good news is that compensation structure does not have to be elaborate to be defensible. It has to be documented, consistent, and anchored to something real.

This playbook walks you through four practical phases: anchoring your pay philosophy, building a band structure, maintaining it without drowning, and preparing for pay-transparency disclosures. Each phase is sized for a solo practitioner with limited time and no dedicated comp budget.

Phase 1 — Anchor Your Pay Philosophy Before You Touch a Number

Compensation structure without a written philosophy is just a collection of numbers. A pay philosophy is a short (one-page is enough) statement that answers three questions your management team will eventually ask anyway:

1. What labor market are we competing in? A 40-person accounting firm in Columbus competes for CPAs nationally but competes for receptionists locally. Defining this by role category prevents arbitrary decisions later.

2. What percentile of the market do we target? Common choices are the 50th percentile (market median — defensible and common among budget-constrained SMBs), the 60th–75th percentile (competitive positioning for hard-to-fill roles), or a tiered approach (median for support roles, 65th for revenue-critical roles). There is no universally correct answer; there is only the answer your leadership will fund consistently.

3. How do we move people through a band? Performance-based progression, tenure-based steps, or a hybrid? Document this before your first band is built, or you will face retroactive justification pressure every review cycle.

Once those three questions are answered in writing, all subsequent compensation decisions — every offer, every counter, every merit increase — become defensible in two sentences: "This role is benchmarked to the 50th percentile of national market data for this SOC code. The offer is at 97% of the midpoint, within our target range."

That documentation also becomes your evidence file if a pay-equity complaint ever surfaces. For context on what a more complete job leveling framework for a small company looks like, the linked guide covers the structural decisions behind that work.

Phase 2 — Build a Band Structure That Fits a Small Organization

For a company under 150 employees, you rarely need more than four to six pay grades. Over-engineering the structure at this stage creates maintenance debt you will pay for every quarter. Start minimal and add grades only when you genuinely have population density that justifies them.

The inputs you need before you start:

• A list of all active roles, grouped into three to five job families (e.g., Operations, Sales, Finance/Admin, Technology, People)

• A target midpoint for each role, derived from a benchmark source (the BLS Occupational Employment and Wage Statistics survey is free and published annually; it covers roughly 830 occupations across approximately 530 geographic areas, based on a sample of about 1.1 million establishments)

• A chosen range width (also called midpoint spread), expressed as a percentage — for individual-contributor roles, 40–50% is common (meaning the maximum is 40–50% higher than the minimum); for manager and director roles, 50–60% is common, reflecting wider variation in scope and tenure

The arithmetic for a single band (worked example):

Suppose the BLS OEWS May 2025 release shows an all-occupation annual mean wage of $69,770. Use that as a placeholder anchor to demonstrate the method — in practice, you would pull the figure for the specific SOC code and geographic area that matches your role.

• Target midpoint (anchored to market): $70,000

• Chosen range width: 50%

• Band minimum = midpoint ÷ 1.25 = $56,000

• Band maximum = minimum × 1.50 = $84,000

That three-number band (min/mid/max) is the foundational unit of every compensation structure. Repeat this for each job family and level, and you have a band matrix. For a deeper walkthrough of the construction mechanics, the guide on how to create salary bands covers the full process step by step.

A note on range overlap: adjacent bands should overlap modestly — typically 15–25% — so that a high-performing employee at the top of Band 2 is not stranded below the floor of Band 3 when they are promoted. Too much overlap (>50%) collapses your structure and makes levels meaningless. Too little (zero overlap) makes every promotion feel like a salary crisis.

One term worth knowing here: compa-ratio is simply an employee's current salary divided by their band midpoint, expressed as a percentage. A compa-ratio of 1.00 means the employee is exactly at midpoint. Tracking compa-ratios across your workforce — even in a simple table — gives you a fast read on where pay equity risk is concentrated and where you have merit-budget flexibility.

Phase 3 — Maintain the Structure Without It Becoming a Second Full-Time Job

Compensation maintenance is where solo HR generalists managing pay most often fall behind, because there is no scheduled forcing function. The band matrix gets built in Q1, sits untouched through a hiring sprint, and by Q4 it no longer reflects the market or the workforce.

Three habits keep the structure current without consuming your calendar:

Annual market refresh (January or after OEWS release). The BLS OEWS publishes updated data each spring. Block one day per year to pull updated figures for your ten to fifteen most critical SOC codes and recalculate midpoints. Adjust band mins and maxes accordingly. This is not a complete overhaul — it is a calibration.

Offer-letter trigger review. Any time a candidate negotiates your offer above the band midpoint, treat that as a market signal worth logging. If you are routinely landing candidates at 105–115% of midpoint, your midpoint is probably stale. Five such data points is enough to justify a band adjustment ahead of the annual cycle.

Promotion checkpoint. Before any promotion is approved, run the employee's proposed new salary against the destination band. If it falls below the new band minimum, document the plan and timeline to close the gap. If it exceeds the new band maximum, that is either a band design problem or a scope misclassification — both worth surfacing to leadership before the promotion letter is signed.

One important caution on tooling: if your band structure lives entirely in a spreadsheet, you are carrying a structural risk that the data itself may not catch. Research published in partnership with Frontiers of Computer Science has found that 94% of business spreadsheets used in decision-making contain errors — and compensation spreadsheets are not exempt. Formula errors in range calculations, copy-paste overrides that break linked cells, and version-control failures across shared drives are the three failure modes we see most often discussed in HR operations contexts. The article on spreadsheet compensation risks covers these in detail if you want a full accounting before your next audit.

Phase 4 — Prepare for Pay Transparency Without Panicking

Pay transparency compliance is increasingly unavoidable, and as the solo HR generalist, preparing for it falls on you. The scope is already significant: depending on how state and local laws are counted, somewhere between 17 and 25 jurisdictions in the United States have enacted pay transparency requirements, with more in progress. California's SB 1162 requires employers with 15 or more employees to include a pay scale in all job postings — and under the updated SB 642 (effective January 1, 2026), "pay scale" is defined as a good-faith estimate of what the employer reasonably expects to pay upon hire. In California, each non-compliant posting is treated as a separate violation, carrying civil penalties of $100 to $10,000 per violation, with escalating fines for repeat violations. If the same posting runs on five job boards without a salary range, that is potentially five separate violations.

A pay band structure is your pay transparency compliance infrastructure. Without documented bands, every disclosure is an improvised decision — and improvised decisions under regulatory scrutiny are where penalties originate.

Colorado's Equal Pay for Equal Work Act carries similar per-posting penalties of $500 to $10,000 per violation. Ontario's pay transparency rules, which took effect January 1, 2026, require employers with 25 or more employees to include compensation or a salary range in publicly advertised postings — with the range not exceeding $50,000 and applying to roles up to $200,000 in total compensation. British Columbia has required pay range disclosure in all job postings since November 1, 2023.

The practical upshot for a solo HR generalist: if your band structure is documented, pay transparency compliance reduces to a publishing step. If it is not documented, every new job posting requires a compensation decision from scratch, under time pressure, without a defensible record. The complete guide to job band structure covers the structural foundations in full, including the documentation standards that support compliance review.

For HR practitioners who eventually move into or report to a director-level role, the HR director's compensation governance guide addresses the oversight layer that sits above the practitioner work described here.

Phase 5 — Know When to Formalize Your Process

There is a point in most growing companies when the solo HR generalist's informal comp process starts to create more work than it saves. Common signals:

• Offer decisions require executive approval on an ad-hoc basis because there is no documented range to reference

• Employees are asking "how does pay work here?" and there is no honest, structured answer

• A pay-transparency law now applies to the company and posting without ranges is no longer an option

• Two or more people doing the same job are paid more than 15–20% apart with no documented rationale

When those signals appear, the issue is not that you have been doing it wrong — it is that the organization has grown past the capacity of an undocumented process. Formalizing at that point is not an admission of failure; it is the right operational response to scale.

If you are at that inflection point and want a structured starting place, the Job Band Structure Builder is designed for exactly this context: a solo HR practitioner who needs to build a defensible, documented band matrix without a comp analyst or a six-figure software contract. It works from BLS OEWS and Statistics Canada data, produces band documentation ready for leadership review, and takes hours rather than weeks to deploy. See the pricing and tier details at /pricing if you want to assess fit before committing.

The Honest Summary

Solo HR generalist compensation management is not glamorous work, and it is rarely finished. The market moves, the org chart shifts, a new law takes effect, and the spreadsheet that served you last year has a broken formula in column G. The answer is not a larger team — most of you do not have one coming. The answer is a structure that is documented well enough to survive a hiring sprint, a compliance audit, and a leadership question at 4 PM on a Friday.

Build the philosophy in writing. Build the bands from real data. Maintain them on a calendar, not on a crisis. Prepare your disclosures before the law requires them. And when the structure starts to crack under the weight of a growing company, formalize it — because a defensible process is the only one that scales without you being in every room. ```