It's Wednesday, 4:40 p.m. A candidate replies to your screening email with two screenshots.

One is your careers page: "$140,000–$170,000."

The other is your LinkedIn post: "$130,000–$160,000."

"Which one is it?"

You don't know. The hiring manager changed the range last Thursday. Somebody updated one place. Not the other.

Pay ranges are moving from "nice to have" to "required," and the number is now the first thing a candidate checks. Pay transparency software can't fix a job post that lives in four places and belongs to no one.

Pay transparency software meets a job post nobody owns

Here's the backdrop. Virginia employers must include the pay range in postings from 1 July 2026. EU member states were due to transpose the Pay Transparency Directive by 7 June 2026, and most haven't finished. Applicants are meant to see pay information early enough to negotiate. Employers can't ask about pay history.

Late isn't the same as optional.

One job, six copies

Careers page. LinkedIn. Indeed. A Google Doc JD. A Slack message to the hiring manager. Your ATS.

Six copies. One range. Zero owners.

Now run it across your desk: 8 open roles × 4 channels = 32 places where a number can quietly go stale. You're not managing a job. You're managing a rumor of a job.

The range is the easy part

A pay range is two numbers. What sits behind them is the hard part: the level, the must-haves, the bar you actually screen against.

Posted range ≈ level ≈ screening criteria.

Move one, and the other two are wrong. Post "Senior" money, screen for "Staff" experience, and you've published the mismatch in public.

Here's the part nobody budgets time for. The hiring manager nudges the range on Thursday, and the screening bar stays where it was on Monday. Now your shortlist is built for a job that no longer exists. You won't notice until the third interview, when the candidate asks why the role sounds different from the post.

Candidates screenshot everything

Salary is the line candidates screenshot first. Candidates compare it across tabs, forward it to friends, and drop it in group chats.

A post with two numbers isn't a typo. It's a screenshot waiting to happen. And every screenshot asks the same question: do these people know what this job is?

The final-round reveal is expiring

For years the quiet strategy was simple: hold the number until the last round, then see who flinches.

No pay history. Pay information shared early. The range you post and the criteria you screen on are now the only anchors left. They'd better agree.

The Four Locks: a job record you can defend (it works in a spreadsheet)

A pay range isn't a compliance chore. It's a job-record problem. Four locks fix it, and you can run them in a Google Sheet today.

Lock 1: Range before reach

Agree the range with the hiring manager before the post exists. In writing.

• Floor
• Ceiling
• Level
• Sign-off date

No range, no post.

Lock 2: Criteria before screening

Write the top must-haves and their weights before the first CV lands. Same sitting as the range. If the hiring manager can't rank them, the role isn't ready.

Lock 3: One source, many mirrors

One record is the source. Every channel is a mirror.

Edit the source. Re-publish the mirrors. Never edit a mirror directly, because that's exactly how two numbers are born.

Lock 4: A change log

Who changed the range. When. Why. Two lines each.

Next time a candidate sends two screenshots, you answer in thirty seconds instead of thirty minutes.

What it looks like for one role

Say you're hiring a Senior Backend Engineer.

• Range: $150,000–$175,000
• Level: Senior
• Top four must-haves, weighted 35 / 25 / 20 / 20
• Source: one row in one sheet
• Mirrors: careers page, LinkedIn, Indeed

Two weeks in, two offers get declined on pay. The hiring manager raises the range. You change the source, re-publish three mirrors, and log one line: range raised, approved Oct 9, two declines. Nobody has to remember anything.

Four locks. One record. Zero guessing which number is real.

The Knoot Angle

Every role is different. Your criteria should be too, and so should the record they live in.

That's the idea behind Knoot's Job Management module. You create and manage every job in one place, with scoring criteria customized per role and the candidate-facing information kept right beside them. You track the whole application flow per job from the same screen. When the range changes, you change the job once, not six copies of it.

Knoot won't make you compliant. No software does that on its own, and the legal call still belongs to you and your counsel. What it gives you is a job with one home, so the number on the page and the bar behind it stay in step.

The range is public now. Make sure the job behind it isn't a mystery.