Utah Salary Transparency How The New Pay Disclosure Rules Are Changing Hiring In The Beehive State

Utah's Pay Transparency Law Is A Real Shift For Employers

The Utah Equal Pay Amendment went into effect on May 1, 2024, and it changed how employers in the state handle compensation during hiring. The law requires job postings for positions with an annual salary of $75,000 or more to include a good faith estimate of the pay range. That estimate has to reflect what the employer actually plans to pay, not a number pulled from a competitor or a broad bracket that spans $40,000. If you're hiring for a role above that threshold and your posting doesn't include the range, you're already out of compliance before the first candidate interviews. The requirements go beyond just posting a number. Employers also have to provide the pay range to any applicant who asks for it before an interview, and if you hire someone, you need to give them written notice of the pay range within five days of the offer. There are penalties for violations too, up to $2,500 per violation, and there's no statute of limitations that caps this at a short window. The Utah Anti-Discrimination and Retaliation Act also protects employees who raise complaints about pay transparency, which means retaliating against someone for asking about their compensation is itself a legal exposure.

Utah Salary Transparency How The New Pay Disclosure Rules Are Changing Hiring In The Beehive State

What I've noticed working with companies across Utah is that the biggest disruption isn't the legal requirement itself. It's the internal work required to figure out what the good faith estimate actually is. A lot of employers, especially smaller ones, have been operating with salaries that vary based on negotiation skill rather than structured bands. The law effectively forces those companies to define a range and stick to it. I had a client in Provo who was hiring a mid-level account manager and had always offered anyone between $62,000 and $88,000 depending on what they could extract in negotiations. After the law passed, they needed a single range posted publicly. We ended up settling on $70,000 to $85,000 as the posted range, but I had to push them hard on capping the top end. Their original maximum offer had been $88,000, and leaving that off the posting created a discrepancy between what was disclosed and what was actually budgeted. That gap matters under the good faith standard. The good faith estimate definition in the statute is pretty specific. It's the range the employer reasonably expects to pay in good faith at the time of the posting or request. This means you can't post a range that intentionally inflates the upper bound to make the role look competitive while planning to lowball every candidate. The law doesn't define "good faith" with bright lines, but the Utah Antidiscrimination and Labor Commission will look at whether the range is consistent with what you actually pay your current workforce and whether it aligns with the duties and qualifications listed. If someone posts $50,000 to $120,000 for a role that requires no experience and pays no one above $65,000 internally, that's a lawsuit waiting to happen.

The Mechanics Of Compliance Are Straightforward But Messy In Practice

You need to identify every open position with a target salary above $75,000. That sounds simple until you realize most companies have requisitions sitting in an ATS with no salary field filled in, or with a placeholder number like "$80K commensurate with experience." The word "commensurate" is meaningless under the new law and won't satisfy the requirement. You need a concrete minimum and a concrete maximum. Once you have the positions, you need to calculate the range. I typically recommend starting with your existing compensation data for similar roles, adjusting for the specific responsibilities of the open position, and then applying market benchmarks from sources like Radford or Mercer if you have access to them. The range should normally span no more than a certain proportion unless you can justify a wider band based on legitimate factors like seniority levels or geographic differentials within the state. Salt Lake City roles often command higher ranges than positions in Logan or St. George, and the law doesn't prevent you from accounting for that, but you do need to document why the variance exists. Here's something most guides miss. The law applies to the employer, not the job board. If you post through LinkedIn or Indeed, those platforms now have built-in salary range fields because of this law, but the legal obligation is yours. The platform's form field doesn't transfer compliance to them. You still need to verify that the number you enter matches your internal range and that you've reviewed every other channel where the posting appears, including your career page, company social media, and any employee referral links that include the job details.

Common Pitfalls That Cost Companies Money

The most frequent mistake I see is using a range that's too wide. A range from $60,000 to $120,000 for a single role looks like an attempt to obscure the real number rather than disclose it. The commission and courts will likely view a range wider than roughly 50% above the midpoint as suspicious unless there's a clear and documented reason. I've seen employers try to use extreme ranges to keep negotiation flexibility, and that approach backfires fast. Another issue is outdated postings. A company can get compliant on day one and then forget about it six months later when they repost the same role with the same salary range. If market conditions shift or the company adjusts its compensation philosophy, that old range might no longer represent a good faith estimate. The obligation resets every time you publish a new posting or extend a new offer. Static compliance checklists don't work here. You need a process that reviews active requisitions periodically, not just at hire time. The five-day written notice requirement after a hire is another area where companies stumble. This isn't the same as the job posting range. The notice to the new employee should reflect the actual agreed-upon salary, and it needs to be in writing. Email counts. I've had clients use verbal offers without follow-up documentation and then realized too late that they hadn't met the written notice requirement. The fix is simple enough, but the ignorance of the rule itself is common among small business owners who've never dealt with anything like this before.

A Note On What The Law Doesn't Cover

The $75,000 threshold creates a significant gap. Positions below that amount don't require a posted range under Utah law. Some employers interpret this as permission to keep all sub-$75,000 roles opaque, and technically they're right. But there's a practical risk in drawing a hard line at that number. If you're hiring someone for a $74,000 role and a candidate finds out a peer in a similar position is making $82,000, the disparity will create morale problems regardless of what the law requires. Several companies in Salt Lake County have voluntarily extended pay range disclosure to all postings as a matter of policy, and they report that it actually simplified their recruiting process rather than complicating it. The administrative cost of including ranges on lower-salary postings is minimal, and the trust benefit is measurable. There's also the question of internal equity audits. The law doesn't explicitly require them, but if a company is subject to a discrimination complaint, the pay transparency data becomes evidence. Employers who have proactively audited their pay ranges by gender, race, and other protected characteristics are in a much stronger position if that audit ever comes under scrutiny. Companies that haven't done this work should treat the new law as a trigger to finally address internal pay disparities before someone else does it for them through litigation or a commission investigation. Remote work adds another wrinkle. If you hire someone remotely who lives in a different state but the role is posted under Utah law, the Utah requirements apply to the posting itself. However, the actual compensation might need to reflect the employee's state of residence for tax and wage law purposes. I worked with a company that had a remote sales role based in Idaho but posted under Utah guidelines. The range they posted satisfied Utah's disclosure rule, but their actual offer to the Idaho-based candidate had to account for Idaho's own pay transparency requirements, which are different. Managing multiple state regimes is harder than it sounds, and most small Utah employers aren't set up for multi-state compliance.

The enforcement mechanism relies heavily on employee complaints. There's no routine audit program that I'm aware of, which means most employers won't know they're out of compliance until someone files a charge. That's a high-risk posture for any company that hasn't systematically reviewed its hiring practices. The practical recommendation I give is to treat this as an ongoing operational requirement, not a one-time fix. Set up quarterly reviews of all active postings, maintain written records of each range and the methodology behind it, and train recruiters and hiring managers on the five-day notice rule. The companies that get this right early are the ones that won't be caught scrambling later.