Pay transparency and what it changes for lean teams

Posted ranges do not just change job ads. They change what your own employees can infer about their pay — and how fast they can infer it.

Pay transparency requirements are usually discussed as a job-posting compliance task: put a range in the ad, keep it good faith, done. That framing understates the operational shift. Once ranges are public, your own employees can compare their pay to the range you posted for their role, and so can candidates, competitors, and anyone else who cares to look.

For a lean Total Rewards team, the practical consequence is not the posting itself. It is the volume and specificity of the questions that follow it.

The multi-state complication

Requirements vary by jurisdiction, and a company with employees in several states is often subject to several overlapping regimes at once. Some jurisdictions require the range in the posting; some require it on request; some require additional disclosure at offer or during employment; some attach requirements to remote roles that could be performed in that jurisdiction regardless of where the company sits.

For a distributed company, this means a single remote job posting can trigger obligations in multiple places simultaneously. The practical approach most lean teams land on is to apply the strictest applicable standard everywhere rather than maintaining separate posting logic per state — the compliance overhead of the alternative is rarely worth the flexibility it preserves.

The "good faith" range

The requirement that a posted range be made in good faith is the part with real teeth, and it is where the discipline of your underlying structure becomes visible externally.

• A range so wide it conveys nothing invites scrutiny and does not protect you.
• A range you routinely hire outside of is evidence that the posted range is not the actual range.
• A range that does not match what current employees in the role are paid will be noticed by those employees immediately.

That third point is the one that catches teams out. Posting a range for a role you already staff is, in effect, publishing information about your existing employees' pay relative to structure. If people in that job are sitting below the bottom of the posted range, you have surfaced a problem you may not have finished addressing.

Transparency does not create pay problems. It shortens the time between having one and being asked about it.

Preparing before you post

The work that actually reduces risk happens before the first posting goes up.

Audit current employees against the ranges you intend to publish. Identify anyone below the floor and decide what you are doing about it and on what timeline. Doing this after publication means doing it under pressure.

Prepare managers with real answers. The most common question — "why am I at this point in the range?" — needs a response grounded in level, scope, and performance, given consistently. Managers improvising here create commitments the comp team then has to honour or walk back.

Establish a record of reasoning for pay placements. When an employee asks why they sit where they sit, the quality of the answer depends entirely on whether anyone wrote down the reasoning at the time. Reconstructing it a year later, from memory, is not a position you want to be in.

The upside

Transparency requirements are frequently framed defensively, but they push toward practices that are good regardless: defensible ranges, consistent placement logic, documented rationale, and managers who can explain pay decisions in plain language.

Teams that already have those things treat transparency as a formatting change. Teams that do not treat it as a crisis. The difference is not the size of the compensation function — it is whether the reasoning behind decisions was ever captured in a form anyone else can read.