Pay transparency is now a per-posting, per-applicant problem

Take a single posting in a state with per-applicant damages. Say it pulls 200 applicants over the six weeks it's live, which is a normal number for a high-volume role. If that posting is missing a compliant pay range, you're not looking at one violation. You're looking at 200 potential claims, each with its own damages range.

Now multiply that by every posting you have live in that state. Then multiply by every state with a law on the books. This is why compliance teams have stopped thinking of pay transparency as a policy question and started thinking of it as a monitoring question.

Most teams handle this with a review cycle: someone checks the postings quarterly, or legal sends a reminder when a new law passes. That worked when three states had laws. It doesn't work now.

Postings change daily. Recruiters edit them, hiring managers request tweaks, templates get updated. A posting that was compliant in March can be non-compliant in April because someone removed the range to "stay flexible." Nobody meant to create exposure. They just didn't know the rule had teeth.

The teams getting this right treat every posting like a regulated artifact. Every new or edited posting gets checked against the rules in the states where it runs, the same day it changes. When a new law takes effect, every affected posting gets rescanned before the effective date, not after the first complaint.

And they keep the receipts. A documented record of what was checked, what was fixed, and when is the difference between an uncomfortable conversation and a defensible one.