The Nonprofit Compensation Guide: Benchmarking and Transparency
Most nonprofits approach compensation the way they approach operations: reactively, and without systems. When someone is hired, their salary is negotiated privately, based on what the organization "can afford" and what the candidate will accept. Repeat that hire after hire and you end up with a payroll nobody designed, in which two people doing the same work earn different amounts for reasons nobody can now reconstruct. The approach creates invisible inequities, prevents fair comparisons, and makes every compensation conversation emotionally fraught. The alternative is a compensation system: a transparent, documented approach to determining salaries and benefits. This is not primarily about paying more, though sometimes it should be. It is about paying fairly, making informed decisions about trade-offs, and creating psychological safety around money.
Why Compensation Systems Matter
Beyond fairness, compensation systems serve the organization's own interests. When staff do not understand how salaries are determined, they assume the worst. They wonder whether they are paid less because they are a woman, because of their race, or because they were less assertive in negotiation. Even where there is no actual inequity, secrecy manufactures suspicion, and suspicion erodes trust and engagement long before anyone raises it out loud. Secrecy also removes the one thing that would settle the question, which is a visible explanation of how the number was reached.
When compensation is transparent and systematic, staff understand how decisions are made. They know what they need to do to advance, they can plan financially, and, most importantly, they can see that the organization operates with integrity around money. Systems protect the organization too. Compensation decisions that are documented and defensible are a defence against discrimination claims. An organization that has conducted benchmarking and made intentional decisions about where it sits in the market is also prepared for the harder conversations that come with turnover, because it can explain its position rather than improvise one.
Step 1: Define Your Compensation Philosophy
Start by answering one question in writing: what is our position on compensation? A compensation philosophy is a short written statement that settles the questions you would otherwise relitigate at every hire. Do we aim to pay above market, at market, or below market for our region? How much variation do we allow between the minimum and maximum within a range? Do we value equity of outcome, meaning everyone advancing together, or equity of opportunity, meaning everyone having advancement pathways? How do we value different types of experience, such as years in role against years in the sector? Which benefits are non-negotiable and which are flexible? And when and how do people advance?
The philosophy does not need to be complex. A statement along the lines of "we aim to pay at the 75th percentile of the nonprofit market in our region, with annual cost-of-living adjustments and performance-based advancement; we prioritize health insurance and retirement benefits; all salary ranges are published internally" is sufficient. What makes it useful is not its sophistication but the fact that it exists before the next hiring decision, so the decision is measured against a standard rather than made in the moment and rationalised afterwards.
Step 2: Conduct Market Benchmarking
You cannot build equitable compensation without understanding your market. Start by identifying comparable organizations, meaning nonprofits similar in mission, size and geography. A 50-person education nonprofit in Boston should not benchmark against a 500-person national organization; it should look primarily at regional education nonprofits. Comparability is the whole load-bearing assumption of benchmarking, and it is where most amateur attempts fail, because the easiest data to find is usually from the largest and least similar organizations.
| Source | What it gives you |
|---|---|
| GuideStar / Candid | Aggregate Form 990 data showing nonprofit salaries. A free version is available; the paid version is more detailed. |
| PayScale / Glassdoor | Crowdsourced nonprofit salary data by role and region. |
| Professional associations | Sector associations often publish compensation surveys, such as AFPNET for fundraisers or NALP for legal services. |
| Informal networks | Direct conversations with peer organizations. Most nonprofits share this data confidentially. |
| Local HR consultants | Some specialise in nonprofit compensation and conduct market studies for a fee. |
Document what you find rather than carrying it in your head. Create a spreadsheet showing each of your roles and how comparable roles are compensated in your market, then calculate percentiles so you can answer the only question that matters: given the range a role commands in your market, where do you actually sit? A percentile is more useful than an average because it tells you your position relative to the whole distribution, which is what your staff and your candidates are implicitly comparing you against.
Step 3: Create Salary Bands and Ranges
Do not set individual salaries without structure. Create salary bands, which are groupings of roles with similar complexity and responsibility, so that pay attaches to the shape of the work rather than to the individual negotiation that produced the hire. Most nonprofits have somewhere between five and ten bands. A common arrangement runs from Band 1 for entry-level coordinator roles, through Band 2 for mid-level specialists and Band 3 for senior specialists and team leads, to Band 4 for managers and Band 5 for directors and senior leadership.
Within each band there is a range rather than a single number. People typically start at the lower end of a band and progress toward the midpoint and then the upper range based on experience, performance and market conditions. That structure does two things at once. It gives you a defensible answer to why a particular person earns what they earn, and it leaves room for genuine differences in competency without forcing you to invent a new job title every time someone gets better at their work. Structure without rigidity is the aim; a band with no range is a rule, and a range with no band is a guess.
Step 4: Determine Progression Criteria
Bands only work if people can see how to move within them. Document what drives progression. Common criteria include years in the current role, with defined points such as two years and five years; demonstrated competency and impact; expanded responsibilities; market adjustments applied when a salary falls below the range minimum; and cost-of-living adjustments applied annually across the board.
Different organizations weight these differently, and there is no single correct weighting. What matters is being explicit. A stated rule such as "we do cost-of-living increases every year and merit-based increases annually for high performers" is clearer than hoping managers understand and apply an unwritten convention consistently. Unwritten progression rules produce exactly the pattern the system was built to prevent: the people who ask get moved and the people who do not ask do not, which reproduces the negotiation-based inequity in slower motion.
Implementing Transparency
Once you have built the system, the next step is transparency, and this is where many leaders hesitate. Transparency is nevertheless crucial for equity, because a system nobody can see cannot be checked by the people it applies to. There are three defensible levels, and even the lightest is more open than the sector norm.
Full transparency. Publish all salary ranges internally, so anyone can see what any role should pay. A simple document or spreadsheet showing bands and ranges is enough. This eliminates secrecy and signals trust, and most organizations that do it find minimal problems, because staff largely understand that the ranges are real and reasonable.
Moderate transparency. If full internal transparency feels risky, publish your compensation philosophy and your bands, show the ranges, but do not publish individual salaries. This is a genuine compromise rather than a fudge, and it is still far more transparent than industry norms.
Benchmarking transparency. At minimum, tell staff that you conducted benchmarking, what the results showed, and how they inform compensation decisions. The register to aim for is concrete: we benchmarked our Development Director role against 12 peer organizations in the Boston metro area, this is where our salary sits as a percentile for an organization of our size, and we review this annually. Even without publishing a single individual number, that tells staff the process exists and has been applied.
Addressing Inequities
Building the system will show you things you would rather not see. If you find gaps, whether staff paid below their range minimum or clear disparities that track demographics, you need a remediation plan. This is the hard work that having a system makes possible, and it is also the reason some organizations avoid building one.
Start by calculating the cost of bringing everyone to their range minimum, which will vary with the size of your organization. Then create a multi-year plan to close the gaps and say so plainly: we are increasing the salaries of staff paid below their band minimum this year and continuing increases over three years until everyone is within range. Naming the timeline signals commitment and prevents shock, and it is far better received than a silent partial correction that staff notice anyway.
Be particularly careful about disparities that correlate with protected characteristics such as race and gender. If your data shows systematic gaps, that is both an equity issue and a legal vulnerability, and the two reinforce each other: an undocumented pattern is harder to defend precisely because it was never examined. Address it urgently, with help from HR professionals or consultants if you need it.
Benefits as Part of Total Compensation
Compensation includes more than salary, and documenting the rest of it changes what you can offer. Build a total compensation statement for each role that sets out base salary alongside the employer contribution to health insurance, retirement matching, the cash value of paid time off, and the professional development budget, then total the figure. Paid time off is worth stating explicitly in value terms: a 15-day allowance is a real portion of annual salary, and staff rarely calculate it themselves.
This provides perspective in both directions. When you cannot increase base salary, you can still improve total compensation through benefits, and a candidate who sees the whole package can compare it honestly against an offer that is nominally higher but thinner underneath. It also helps you understand where you genuinely stand against the market, because benchmarking base salary alone will either flatter or unfairly penalise you depending on how your benefits compare.
Communicating About Compensation
When you implement a compensation system, explain it rather than quietly switching it on. Tell staff that you have reviewed your compensation practices and want to ensure they are fair and equitable, then walk through the philosophy, how you benchmarked, and how decisions are now made. Most staff respond positively to that clarity even when the news is not uniformly good, because the alternative they have been living with is not good news either, it is simply unexplained.
Follow the announcement with individual conversations. The shape of a good one is specific and unmysterious: your role sits in Band 2, here is the range for that band, you are at this point within it after three years, and based on your performance and expanded responsibilities you are tracking toward the next increment next year. Those conversations remove the guesswork that otherwise gets filled in with assumptions, and they give people something they can act on rather than something to worry about.
Anti-Patterns
Tying compensation to job length alone. Tenured staff should not automatically be paid more than newer staff in identical roles. Length of service as the sole driver discourages hiring new talent and fails to incentivise performance, and it quietly converts your salary structure into a seniority ladder you never chose to build.
Using past salary as the basis for a new one. Anchoring an offer to what someone earned previously perpetuates historical inequities. If you hire someone from an organization that underpaid them, matching or slightly beating that number continues the underpayment under your name. Use benchmarks, not history.
Benchmarking against organizations you do not resemble. Comparing a small regional nonprofit to a large national one produces numbers that are easy to find and useless to act on. Comparability in mission, size and geography is what makes benchmarking data mean anything.
Creating so many exceptions that the system stops meaning anything. Exceptions will exist, and they are legitimate when documented and explained, for instance because a candidate's specific experience was scarce in the market. An undocumented exception is indistinguishable from the private negotiation the system replaced.
Implementing a system and then ignoring it. Review compensation data annually, adjust ranges as the market changes, and check that progression is actually happening according to your stated criteria. A system that exists on paper but is not actively managed is worse than no system, because it provides the appearance of fairness without the substance.
Publishing ranges that were never benchmarked. Transparency amplifies whatever it exposes. Ranges grounded in market data survive scrutiny; arbitrary ranges published in the name of openness simply move the argument into the open without giving anyone a way to settle it.
Practice Prompts
- Draft your compensation philosophy in one paragraph, answering all six questions: market position, range spread, equity of outcome against equity of opportunity, how you value different kinds of experience, which benefits are non-negotiable, and how people advance.
- List the organizations you would benchmark against and, for each, note whether it genuinely matches you on mission, size and geography. Strike the ones that do not, and see how many you have left.
- Build a first-draft band structure for your organization, placing every existing role into a band. Note which roles you struggled to place, because those are usually roles whose scope has drifted.
- Calculate the total compensation figure for one role, adding the employer health insurance contribution, retirement matching, the cash value of paid time off and the professional development budget to base salary.
- Run your current payroll against a draft band structure and identify who sits below their band minimum. Cost the gap, then sketch a multi-year plan to close it.
- Write the script for one individual compensation conversation, naming the band, the range, the person's position within it, and what would move them.
Reflection
Think about the last salary decision your organization made and ask what it was actually based on. Was there a documented range, or was it what the budget allowed and the candidate accepted? Then ask what you would say if a member of staff asked you tomorrow to explain the difference between their salary and a colleague's in a similar role. If the honest answer is that the difference reflects when each of them was hired and how hard each of them pushed, you do not have a compensation problem you can fix with one raise. You have a missing system, and the raise will simply move the inconsistency somewhere else.
Glossary
- Compensation philosophy. A short written statement of the organization's position on pay, covering market positioning, range spread, how experience is valued, which benefits are non-negotiable, and how people advance.
- Salary band. A grouping of roles with similar complexity and responsibility, used so that pay attaches to the work rather than to an individual negotiation.
- Range. The span from minimum to maximum within a band, along which people progress based on experience, performance and market conditions.
- Market benchmarking. The process of comparing your roles against comparable organizations, meaning nonprofits similar in mission, size and geography, to establish where your pay sits.
- Percentile positioning. Your salary's place in the distribution of comparable salaries, which is more informative than an average because it locates you relative to the whole market.
- Cost-of-living adjustment. An annual across-the-board increase applied regardless of individual performance, distinct from merit or progression increases.
- Grandfathering. Retaining someone whose salary sits above the maximum of their new band, while limiting future increases until the range catches up with them.
- Total compensation. Base salary plus the employer contribution to health insurance, retirement matching, the value of paid time off, and professional development.
Related Lessons
- Equitable Compensation Practices for Nonprofits
- Staff Retention Without Raising Salaries: 12 Strategies That Work
- Inclusive Hiring for Nonprofits: Beyond the Diversity Statement
- The Nonprofit Workforce Crisis: Data, Causes, and Solutions
- The Essential Policy Library: 15 Documents Every Nonprofit Needs
- Remote and Hybrid Work Policies for Nonprofits
Closing
Compensation systems shift the conversation from "what can I negotiate?" to "what is fair?" That is a change in the question being asked, not just in the answer, and it is why the work is worth doing even when the resulting numbers are modest. For nonprofit leaders committed to equity and retention, the shift is essential: the most successful nonprofits treat compensation not as a burden to be managed quietly but as a strategic tool that they can explain, defend and improve deliberately over time.
Key Takeaways
- Private, case-by-case salary negotiation is a system, just a bad one. It produces invisible inequities, prevents fair comparison, and leaves you unable to explain your own payroll.
- Write the philosophy before the next hire. Market position, range spread, how experience is valued, which benefits are fixed, and how people advance, settled in advance rather than improvised.
- Benchmark against organizations you actually resemble. Mission, size and geography have to match, or the data is easy to gather and impossible to use.
- Bands plus ranges give structure without rigidity. Most nonprofits run five to ten bands, with people progressing from the lower end toward the midpoint and upper range on experience, performance and market conditions.
- Document progression criteria explicitly. Unwritten rules reward the people who ask and penalise the people who do not, which recreates the inequity the system was built to remove.
- Choose a transparency level and commit to it. Full internal publication, philosophy and bands without individual salaries, or benchmarking disclosure at minimum; all three beat silence.
- Fix what the system reveals, on a stated timeline. Cost the gap to range minimums, publish a multi-year plan, and treat demographic disparities as urgent and legally significant.
- Manage the system after you build it. Review annually, adjust ranges as markets move, and document every exception, or the structure becomes decoration.
Frequently Asked Questions
How do I handle staff hired at different salaries for the same role? This is common, and it creates inequity if left unaddressed. First, place everyone into your new bands. Some will sit above the range maximum, in which case grandfather them and limit future increases to cost-of-living until the range catches up. Some will sit below the minimum, in which case create a plan to bring them in. Some will already be in range and can be left as they are. Then document the decision so that the reasoning survives: record which roles existed at which points, which band you assigned them to, who was brought up to the minimum, and where everyone stands after cost-of-living adjustments.
Should entry-level and experienced people in the same role earn dramatically different amounts? Reasonable bands have a 20 to 40 percent spread from minimum to maximum, which accounts for growing competency without requiring a promotion every time someone improves. If the spread you need feels much larger than that, the likely explanation is that you have two roles rather than one, for example a coordinator and a senior coordinator, and you should split them rather than stretch a single band to cover both.
What if benchmarking shows we should pay more than we can afford? This is the honest conversation nonprofits have to have. If the market rate is above what you can fund, decide deliberately between the options: narrow the role and hire into a lower band, hire someone earlier in their career, improve other elements of total compensation, or fundraise specifically for compensation increases. What you must not do is solve it by quietly paying below market, because that produces turnover you then pay for twice. Be transparent instead: say what the role markets at, say where you are, and say that you are working toward market rate over three years.
How often should I update my compensation data? Conduct formal benchmarking every two to three years, or sooner when market conditions shift significantly. In high-inflation periods, benchmark annually; in stable times, every three years is sufficient. In between, do a lighter annual review: are the bands still reasonable, have regional market rates moved, and have professional associations published new surveys? That review takes little time and stops your ranges going stale without anyone noticing.
Is publishing salary ranges really safe? Many organizations fear that publishing ranges will create problems, and research shows the opposite: organizations that publish ranges have higher engagement and fewer disputes, because people can see how the system works. The condition is that the ranges must be defensible on the basis of benchmarking and applied consistently. If your ranges are arbitrary, publishing them will indeed create problems. If they are grounded in market data, they are safer published than hidden.
Skill.re