Reading Utah Salary Data Like a Payroll Person Actually Would
Utah State Salary Transparency Uncovering The Hidden Paychecks
Utah passed a salary transparency law back in 2023, and it's been in effect since then. It requires most private employers with 25 or more employees to post pay ranges in job postings. It's not as dramatic as the California or New York versions, but it does give you something useful if you know how to dig for it. The main tool at your disposal is the job posting requirement. Employers have to include a compensation range in any advertising or posting for a position. That range has to be good-faith based on the budget they actually set aside, not some aspirational number pulled from thin air. You can find these posted on company career pages, LinkedIn, Indeed, and sometimes in the footers of internal posting boards. Here's the thing most people miss. The law doesn't require employers to publish actual salaries. It only requires the range. So you'll see something like "$65,000 to $85,000" and you have to do the rest of the work yourself. The range itself is often a hint. Employers who list a narrow band like $70K to $78K are usually tighter on their budget and less flexible. A wide band like $60K to $95K signals they have room to negotiate depending on your experience level.
I spent a few years reviewing compensation data for a benefits consulting firm, and one of the first things I'd do when a client asked about a role was pull every Utah posting I could find for that title and company. The posted range gave me a floor. Then I'd cross-reference with self-reported data from Glassdoor and levels.fyi, being careful about the dates on those entries. Salary data older than 18 months in Utah is basically useless because the cost of living adjustments and market shifts eat away at it pretty fast. There's also the annual report angle. Utah employers covered by certain provisions have to report workforce demographic and compensation data, but the access to that is clunky. It's not a single downloadable database. You typically get it through public records requests or aggregated through third-party compensation surveys that buy the data. One workaround I used consistently was filing a Utah Public Records Act request for the most recent salary band data for a specific department. It took about three weeks and they gave me a spreadsheet with anonymized job titles and ranges. Not individual salaries, obviously, but enough to map what a Senior Analyst actually made versus a Manager at the same organization. One edge case that caught me off guard. A hospital system in Salt Lake County had classifications where the posted range for a nursing role didn't match the actual step scale in their collective bargaining agreement. The posting said $58,000 to $72,000 but the union contract had defined steps that pushed experienced nurses well into the $80,000s. The discrepancy was because HR hadn't updated the posting after a contract renegotiation. If you're using posted ranges to evaluate an offer, always ask whether the role is union-covered and pull the CBA if possible. That one mistake would have cost someone a significant lowball offer.
The other counter-intuitive detail is that Utah's law allows the range to be expressed as hourly or annual, and employers often use the one that makes the number look bigger. A $35 to $45 hourly range sounds more impressive than $72,800 to $93,600 annually, even though it's the same money. I've seen candidates get confused by this and undervalue roles that were simply posted in hourly terms. Always convert to annual if you're comparing across postings. If you want to look at actual aggregated numbers, the Utah Department of Workforce Services publishes quarterly wage data by occupation and county. It's not glamorous. The website looks like it was built in 2004 and the download buttons are buried under three menus. But the data itself is solid. You can pull median annual wages for hundreds of occupations broken down by metropolitan statistical area. The catch is the lag. The most recent complete quarter is usually three months behind, so if you're researching right now you're probably looking at data from early this year. For individual employer pay data beyond job postings, your options are limited. Utah doesn't have a public salary database like some states. The closest thing is filing those public records requests, and even then you're getting ranges, not individual paychecks. Some larger state-funded institutions post compensation reports for certain positions, particularly at the University of Utah system, but those are usually for exempt and higher-level roles, not the bulk of the workforce.
Get the Full Details
The law also doesn't protect you from retaliation complaints, but it does give employees a private right of action if an employer retaliates for asking about compensation. That's worth knowing if you're gathering this data as part of an organized effort with coworkers. Most people don't use that provision, but it exists. Bottom line, the Utah transparency law is a starting point, not a full picture. It gives you ranges. It doesn't give you individual salaries. It doesn't apply to all employers. The posted numbers are sometimes stale or inaccurate. But if you combine the job posting ranges, the DWS quarterly data, public records requests, and union contract information when applicable, you can get a pretty accurate sense of what a role actually pays in this state. It takes more effort than just checking one website, but the effort is worth it.
