Pay transparency is no longer optional in Minnesota

If you’re hiring in Minnesota—or applying for jobs here—pay transparency is now part of the baseline. The state’s job-posting rule is designed to reduce guesswork, level the playing field for applicants, and push compensation conversations earlier in the process.

For employers, it’s a compliance requirement with real operational ripple effects: job templates, recruiter training, compensation bands, and vendor oversight. For employees, it’s a tool you can use to compare opportunities, negotiate more confidently, and spot red flags.

What Minnesota requires in job postings (and who it applies to)

Minnesota Statute §181.173 requires covered employers to disclose (1) a starting salary range (or a fixed pay rate) and (2) a general description of benefits and other compensation in each posting for each job opening. (revisor.mn.gov)

Covered employers

The statute defines “employer” to include entities that employ 30 or more employees at one or more sites in Minnesota. (revisor.mn.gov)

Effective date

The requirement is tied to 2024 legislation and is widely implemented as an effective January 1, 2025 job-posting standard across Minnesota employers (including large public institutions aligning their posting processes to that date). (revisor.mn.gov)

What counts as a compliant pay range?

The law requires a “starting salary range.” In practice, that means:

  • A range with a low and high number (e.g., “24.50–29.25/hour” or “62,000–78,000/year”), or
  • If you don’t plan to offer a range, a fixed pay rate (e.g., “$27.00/hour”). (revisor.mn.gov)

Avoid these common pitfalls

Even well-intentioned employers stumble on the same issues:

  • Open-ended statements (“$60k+,” “up to $90k,” “competitive pay”) instead of a real range.
  • Ranges that are so wide they look like placeholders.
  • Pay that’s conditional but not explained (shift differentials, bonuses, commissions).
  • Missing benefits/compensation summaries—especially when postings are copied into third-party sites.

Benefits and “other compensation”: what you need to summarize

The statute requires a “general description” of benefits and other compensation, including (but not limited to) health and retirement benefits. (revisor.mn.gov)

A compliant description doesn’t need to read like a 20-page plan document. But it should give applicants a real picture of total compensation. Examples of items many employers include:

  • Medical/dental/vision availability
  • Employer HSA/HRA contributions (if offered)
  • Retirement plan type and employer match (if offered)
  • PTO/vacation structure and paid holidays (high level)
  • Shift differentials, bonuses, commission structure (general)
  • Tuition assistance, tool allowance, CDL training, uniforms, etc. (where relevant)

A practical employer checklist for Minnesota postings

If you’re building (or cleaning up) a Minnesota-compliant hiring process in 2026, this approach is usually workable for HR teams of any size.

1) Build real compensation bands—and document them

Create pay ranges by role and level (and location, if applicable). Keep a record of what you used to set the band (market data, internal equity review, union scale, budget). This helps show the range was established in good faith if questions arise later.

2) Create a “posting-ready” benefits template

Most posting failures happen because benefits language is inconsistent across departments. Draft two or three standardized benefit summaries (full-time, part-time benefit-eligible, seasonal/temporary). Make it easy for managers to choose the right block.

3) Train managers on what the range means

Applicants will ask: “Where would I fall in the range?” If your hiring managers can’t explain the factors (experience, certifications, shift, union step, etc.), transparency can backfire.

4) Control your vendors and third-party postings

If a recruiter or job board reposts your role without the range and benefits, candidates still experience it as your posting. Build a habit of periodically auditing where your jobs show up.

5) Prepare for internal equity conversations

Once ranges are public, current employees will compare their pay to posting numbers. That’s not a reason to avoid compliance—it’s a reason to plan communications and a pathway for pay questions.

What Minnesota applicants can do with pay transparency

A posted range is leverage—but it’s also information you should interpret carefully.

How to read the range

  • The bottom often reflects “meets minimum qualifications.”
  • The middle may reflect “fully proficient.”
  • The top may be reserved for deep experience, scarce credentials, lead duties, or longevity.

If a role lists a range and you meet (or exceed) the posted qualifications, it’s reasonable to ask where the hiring team expects the successful candidate to land.

Smart questions to ask in the first conversation

  • “Is this range hourly base, or does it include a differential?”
  • “Are bonuses or commissions typical in this role, and how are they calculated?”
  • “What experience or credentials place someone in the top half of the range?”

Pay history: know what employers shouldn’t be asking for

Under guidance tied to the Minnesota Human Rights Act, employers generally cannot ask, encourage, or prompt applicants to disclose pay history for the purpose of negotiating compensation. (mn.gov)

If you’re asked for pay history in an application or interview, you can redirect: “I’m happy to discuss my compensation expectations based on the posted range and the responsibilities of the role.”

Special situations: remote work, commissions, and seasonal jobs

  • Remote roles: If you’re hiring someone who will work in Minnesota (or recruiting Minnesotans into roles tied to Minnesota operations), treat postings as Minnesota-facing and align with §181.173 requirements.
  • Commission-heavy roles: Post the base (or draw) range and include a general description of how commissions/bonuses work (e.g., eligibility, frequency, whether typical earnings are tracked).
  • Seasonal/temporary roles: If the pay is fixed, say so. Still include the general benefits/other compensation description—even if that description is “not benefit-eligible” (where accurate).

The bottom line

Minnesota’s pay transparency rule works best when it’s treated as a system, not just a posting edit: define ranges, standardize benefits language, train the people doing interviews, and audit the places your jobs appear.

For applicants, pay transparency isn’t just about fairness—it’s a practical way to save time, compare offers, and negotiate within clearer boundaries.

This article is for general informational purposes and is not legal advice.