Preparing Salary Ranges for a Non-Profit Board Compliance Request

When the Board Chair Asks for the Range Documentation

It usually happens in a finance or governance committee meeting, not an HR meeting. A board member — often someone with a legal or audit background — asks how the executive director's salary was set relative to comparable roles, or whether the new program manager posting has a documented range behind it, or simply whether the organization has a written compensation policy at all. The question is reasonable. Non-profit boards carry fiduciary responsibility for how donor and grant dollars are spent on staff, and increasingly they're asking it before a funder, an auditor, or a state agency asks it first.

The problem is timing. Most small non-profits — the ones running lean with a part-time HR function or an operations director wearing the comp hat — don't have this documentation sitting in a folder. The range for the open role exists in someone's head, or in a two-year-old spreadsheet, or nowhere. The scramble to produce something presentable in the next 48 hours is where a lot of good intentions turn into a hastily built number that doesn't hold up to a second question.

This piece is about what to have ready before that question gets asked — what a board actually wants to see, how to build it without a dedicated compensation analyst, and how to keep it current so the next request is a five-minute export instead of a fire drill.

What a Board Is Actually Looking For

Boards rarely want a compensation consultant's full market study. What they want is evidence of a process — proof that a range wasn't guessed, that it was built against some external reference point, and that it's been applied consistently. Four things tend to satisfy that bar:

1. A documented methodology. Where did the range come from? A named data source (occupation-level wage tables, a peer non-profit salary survey, a published benchmark) beats "we looked around and asked a few people."
2. A visible range, not a single number. A minimum, midpoint, and maximum for the role — not just the number the current incumbent happens to earn.
3. A date. Wage data ages. A range built from a three-year-old table looks worse under scrutiny than one with a clear as-of date, even if the underlying number hasn't moved much.
4. Consistency across roles. If the executive director's range was built one way and the program coordinator's range was built another way, that inconsistency is usually the first thing a sharp board member notices.

None of this requires a certified compensation analyst. It requires a repeatable method and a record of having followed it — which is the actual substance behind the phrase non-profit salary range compliance: not a single legal standard, but a documented, defensible process a board, auditor, or funder can review without the organization having to reconstruct its reasoning from memory.

Where the Underlying Numbers Should Come From

For organizations with no comp background, the most defensible starting point is public, government-published occupation wage data rather than informal benchmarking. In the U.S., the Bureau of Labor Statistics' Occupational Employment and Wage Statistics (OEWS) program covers approximately 830 detailed occupations, built from a rolling sample of roughly 1.1 million establishments, published annually with a May reference date, and available down to the state and metro level at no cost. In Canada, Statistics Canada's National Occupational Classification system covers more than 40,000 job titles across 516 unit groups, with annual wage estimates published under the Open Government Licence — also free to use.

That public-domain status matters for a board packet specifically because it's independently verifiable. A board member — or an outside auditor — can look up the same BLS or Statistics Canada table and check the number themselves. That's a meaningfully stronger position than a range sourced from a private survey the board can't independently inspect, or from "comparable postings we found online."

If the organization already has a salary range process built this way but has never written down the methodology, that gap itself is worth closing before the next board cycle — see how to build a first salary range with no comp background for the underlying method.

Building the Packet Before the Audit Trail Is Requested

A board compliance request is really asking for three documents layered together: the range itself, the methodology behind it, and a record of when it was created or last revised. The third piece — the audit trail — is the one organizations most often lack entirely, because nothing in a spreadsheet naturally timestamps itself.

An audit trail doesn't need to be elaborate. At minimum it should show: when a range was built or changed, what data vintage it was built from, and who approved it. For organizations using a spreadsheet-based process, that means manually logging each change — a habit that's easy to let slip during a busy hiring season. For a more detailed walkthrough of what a defensible audit trail actually needs to contain, see building a compliance audit trail for salary ranges.

This is also where a standalone record-keeping tool earns its place. The Pay Action Ledger & Audit Trail Workbook is a structured spreadsheet template built specifically to pair with a salary range process — it gives you a single place to log every range creation, revision, and approval date in a format a board or auditor can review directly, without requiring any software setup. It's a downloadable document you fill in yourself, not an automated system, but for an organization that's never kept this kind of record before, having the structure already built is usually the difference between starting the habit and putting it off another quarter.

Pay Equity and Pay Compression: The Questions That Come Next

Once a board sees a documented range for one role, the next question is almost always about consistency across the staff roster — is anyone being paid below the range they should fall into, and has the range itself kept pace with new hires brought in at a higher starting point than longer-tenured staff? This is the territory of pay equity review and pay compression, and non-profit boards ask about it more often than for-profit boards do, because donor scrutiny tends to run in that direction.

Pay compression — where new hires are brought in close to or above the pay of longer-tenured employees in the same role — is a documented and fairly common issue. Pearl Meyer's 2022 survey found 60.9% of organizations reported experiencing pay compression, and an earlier Pearl Meyer survey found 80% of respondents said compression has a high or moderate impact on retention, with the issue most pronounced in IT and engineering/science roles. A board asking "are we at risk of this" is asking a fair question, and the honest answer requires actually comparing current salaries against range midpoints — the compa-ratio calculation (current salary ÷ range midpoint × 100) is the standard way to check this role by role.

For a full walkthrough of how to run that comparison across a staff roster, see the pay equity audit guide.

Making This a Standing Process, Not a One-Time Scramble

The organizations that handle board compliance requests well aren't the ones with the fanciest compensation software — they're the ones who treat range documentation as a standing part of every hire and every budget cycle, not a project triggered only when someone asks. That means building the range when the requisition opens, not after the offer is made; recording the data source and date at the moment the range is set; and keeping that record somewhere the next person in the HR seat can find it without asking around.

SalaryRange was built around that sequence specifically: the occupation typeahead pulls from BLS OEWS and Statistics Canada NOC tables so the underlying data source is always named and dated, the range configurator produces a visible min/mid/max instead of a single number, and every range you build generates a one-click compliance PDF with a data-vintage watermark and a timestamped audit trail — retained three years by default — so the next board request is an export, not a reconstruction project. The onboarding wizard is built to get a first range from blank to exported PDF in under thirty minutes, which matters most the first time you're doing this under a deadline rather than on your own schedule.

If your organization is heading into a board or funder review and doesn't yet have this documentation built, it's worth setting it up before the request lands rather than after. You can see current plans and what's included at each tier on the pricing page, and the broader library of HR operations guides — including range-building, audit, and pay equity resources — is collected at the HR operations resource hub.