Author: Joonatan Hongell
Most TA teams that track offer decline reasons find compensation at the top. Wider bands. Sign-on bonuses. A budget conversation with finance. Every adjusted offer assumes the candidate was the right person at the wrong price. The assumption is wrong. What looks like a pricing failure is a transparency failure.
The candidate was never going to accept the range, and the company never shared it early enough.
The United States spent over a trillion dollars on pollution control in the decades after the Clean Air Act. The environment kept getting worse. Paul Hawken wrote about this in The Ecology of Commerce. A factory produces toxic waste, so you bolt a filtration system onto the exhaust. The system is expensive, visible, and produces impressive reports. Tons of waste captured. Compliance targets met. What it never does is ask why the process creates so much waste. You can't count waste that was never created.
The adjusted offer is the filter on the exhaust.
When a recruiter logs "rejected for compensation," the number enters the system as a single category. Leadership sees the trend and responds. But that category is hiding two different problems.
Sometimes a candidate's expectations genuinely shift during the process. They learn the role is broader or more senior than they understood walking in, and they revise their number upward. Adjusting the offer makes sense here. The process revealed new information, and both sides are responding to it.
But most of the time, the candidate and the company had different numbers from day one, and nobody compared them until four weeks and three interview rounds later. A hiring manager who cleared her calendar for the final panel. A team that's already imagining the candidate in the role. Then the offer goes out and the number is 20% below what they'd need.
These two situations look identical in the data. When a candidate rejects an offer or you need to adjust above budget, ask whether their final expectation reflects something they learned during the interviews or something they knew walking in. Pull your last ten offer adjustments and run them through that question. The majority fall into the second category.
I discuss always compensation with the hiring manager before the search starts. There is no point sourcing candidates into a pipeline where they'll learn at the end that the compensation is too low. I believe the company should share the range first. A candidate needs to know the salary band, the total compensation, and enough about the role before anyone asks them for their number. Not all hiring managers agree. Most will when I explain the situation from the candidate's point of view.
A candidate budgeted at 130K gets an offer at 145K because that's what it takes to close. Multiply that across ten or fifteen hires. And when new hires come in above band, the people already in the role notice. What nobody counts is the cost of the alternative, because the alternative costs nothing.
Hiding the range doesn't just produce mismatched offers. It filters out the strongest candidates before they ever enter the pipeline. For senior and critical roles, the people with the most options are the least willing to invest weeks in a process where they can't evaluate basic fit. Some will apply anyway if the company is compelling enough. The pipeline skews toward candidates with fewer alternatives. You end up paying more for weaker alignment.
Leadership points to the acceptance rate as evidence the system works. The money worked. That doesn't mean the process is sound. A factory that captures 90% of its toxic output looks well-managed. It's still producing the toxins.
Share the compensation range before anyone invests serious time. In the job ad, in the sourcing outreach, or at the very latest during the first screening call. "We've scoped this role at X to Y, with these benefits. Does that work for where you are?" Screening calls work both ways.
Hiring managers worry candidates will anchor to the top of the range. Think about who you're trying to hire. These are people already employed and paid well, or between jobs with real options. They are not going to accept less than they're worth because you hid the number.
Many recruiters don't set the disclosure policy themselves. The decision often sits with HR leadership or a hiring manager who wants negotiating room. This is talent advisory work. When you show a hiring manager their own adjusted-offer data and separate the two categories, that second category is the business case. Most hiring managers respond to their own numbers differently than they respond to a policy conversation. Pay transparency legislation is accelerating across Europe, the US, and Australia, but the business case is the faster lever.
When you share the range early, the pipeline gets smaller. Fewer candidates enter, and more of them are genuinely aligned. The budget conversation with finance never needs to happen because the mismatches filtered themselves out before anyone spent four weeks on interviews. That's the hardest part for TA leaders to accept, because you can't point to a dashboard showing the offer rejections that didn't happen. You can only notice that the budget variance went quiet.
Models in this article
End-of-Pipe Fallacy: Systems that respond to bad outputs by filtering them at the end, rather than redesigning what produces them, spend increasing resources to maintain the illusion of improvement.
Discipline: Ecological Economics / Systems Thinking
Source: Paul Hawken, The Ecology of Commerce (1993)
The Recruiting Lattice takes mental models from fields like behavioral science, sociology, and decision theory and turns them into practical tools for talent acquisition.