Posting Ranges You Can't Defend: The Job Architecture Gap Under Pay Transparency

Two numbers published this year describe the same organizations, and they do not fit together. The first is a disclosure number and it is climbing fast. The second is a structural number and it has barely moved.

Payscale's 2026 Compensation Best Practices Report, built on 3,413 responses gathered from October through December 2025, finds 57% of organizations posting salary ranges in job advertisements. Forty-nine percent say they are targeting transparency across the entire company or fully in public this year, a 16-point jump from the 33% who held that goal a year earlier.

Then there is Salary.com's 2026 Pay Practices Report, drawn from 525 HR and compensation professionals across 23 industries. Only 51.4% of those organizations have a formal job architecture. Twenty-two percent do not use job leveling at all. Which means a large share of the employers racing toward public pay ranges cannot say, internally, what a given job is worth or why one role sits above another.

You Cannot Publish What You Have Not Built

A salary range is an output. It is what falls out of a structure: job families, levels, market benchmarks, and a stated philosophy about where the organization intends to pay against that market. Take away the structure and the range is just a number somebody chose, which is exactly how it reads to the person asking about it.

"You can't communicate what you haven't built. When job architecture is missing or job leveling is inconsistent, transparency can become noise instead of clarity." – Amy Dwyer, CHRO, Salary.com

Noise instead of clarity is a precise description of the failure mode. The Salary.com data shows only 34.3% of organizations are transparent about how pay is actually determined, well below the 57% willing to publish the resulting range. Employers are disclosing the answer while keeping the method to themselves, in many cases because there is no method to disclose.

That gap shows up in how confident HR is compared with how confident HR expects employees to be. Salary.com found 74.8% of HR professionals believe their organization pays fairly, but only 44% believe their employees would agree. A 31-point spread between what a function believes about itself and what it expects its audience to believe is not a communications problem. It is an evidence problem.

Twenty-One Percent Are Running on Discretion

The most consequential number in the Salary.com report is smaller and easier to skip past: 21% of organizations set pay mostly or entirely through manager discretion. In those companies there is no framework producing the range. There is a manager producing it.

Pair that with what transparency now demands of the same manager. Once a range is public, every direct report can locate themselves inside it and arrive with a specific question about their specific position in that band. The manager needs an answer that holds up, and discretion does not produce answers that hold up.

"Managers need to know what it is, why it is this way and what it means for their direct report." – Nicole Bufanio, Senior Principal, Mercer

Writing in WorldatWork's Workspan Daily, practitioners describe the same asymmetry from the employee side. Payscale's Pay Confidence Gap research found 69% of employees trust their employers' pay decisions while 93% of employers believe employees trust those decisions. Employers are wrong about their own credibility by 24 points, and they are wrong in the flattering direction.

The recommended fix in that reporting is notably unglamorous: give managers the compensation philosophy in talking points, run role-play scenarios, hand over the actual pay grade detail, and coach tone. None of that is possible in an organization where the grades do not exist.

Sequence the Work in the Order It Actually Depends

The uncomfortable implication of putting these two reports side by side is that a meaningful share of transparency programs are being built in the wrong order. Publishing is the visible step, so it goes first. Architecture is invisible and slow, so it waits. Then the questions arrive and there is nothing underneath to answer them with.

The organizations getting this right are not necessarily the most transparent ones. They are the ones whose disclosure does not exceed their structure. A company with clean job levels publishing ranges for two departments is in a stronger position than one publishing everywhere on top of nothing, because the first can survive the follow-up question.

For compensation and HR leaders working a transparency roadmap, the practical order looks like this:

• Audit whether you have job architecture before you commit to a disclosure date. Only 51.4% of organizations do. If you are in the other half, the range you publish is an assertion, not a conclusion.
• Fix job leveling first, since 22% have none. Levels are what make two different roles comparable and one range defensible. Nothing downstream works without them.
• Close the 21% discretion gap deliberately. Identify where pay is still set by individual judgment and decide whether that is a philosophy or an accident. Under transparency it will be read as the latter.
• Publish the method, not only the number. Just 34.3% are transparent about how pay is determined. The range without the reasoning is the configuration most likely to reduce trust.
• Give managers the grades, not a script. Talking points fail when the manager cannot answer the second question. Hand over the actual structure and let them reason from it.
• Stop trusting your own read on employee trust. Employers overestimate it by 24 points. Measure it directly, and measure it after merit conversations rather than before.

Transparency was always going to expose whatever was underneath it. The disclosure statistics suggest most employers have accepted that. The architecture statistics suggest about half of them have not yet built the thing being exposed.