Post the pay range after you can defend it
Seventeen states plus Washington, D.C. now require pay ranges in job postings. Colorado went first. That is the compliance story, and most teams have it covered. The part they miss is who reads the posting first.
Your current employees read it first
Former EEOC Chair Jenny Yang said at the American Bar Association's Labor & Employment Law conference that a posted range is often a notice to your current workforce that they might be underpaid. Her advice: assess your job architecture and your pay ranges before you post them.
Attorney Stephen Malone described the usual alternative. Pay audits were retroactive, one and done, and often prompted by litigation. Posting first and auditing later runs that same sequence in public.
What an operator sees
Picture the usual path. A recruiter gets a requisition, copies a range from the compensation file, and publishes it. Nobody checked whether the level behind that range matches what current employees in the role are paid, or what it takes to move up. Approved headcount doesn't recruit itself, and a posting that starts an internal pay argument doesn't fill itself either.
Three checks before the next posting goes live
- What decision are we actually making? Name the level, and say what separates it from the level above.
- What would have to be true for this range to hold? Compare it with what people in the role earn today.
- Who owns the next move if the answer is no? Name the person who fixes the level or the pay, and the date.
The offer
Talent Map shows where the people you want already work, gather, and get certified, so your recruiters stop guessing.
Book a Talent Map session with Jackye Clayton