Minnesota Pay Transparency. Single-State Compliance.
Bay Lake Software. Minneapolis. Monday, 8:47 AM CT.
An interactive scenario about a MN DLI inquiry, fourteen postings missing the starting salary range under Minn. Stat. 181.173, and the Minnesota Equal Pay Law's quiet rule that "market rate" is not a defence.
One day to make three decisions.
VP of People at Bay Lake Software. A 220-person digital publisher headquartered in Minneapolis. Every employee is in Minnesota.
Your pay bands have not been updated in 18 months. This morning, the Minnesota Department of Labor and Industry opened a review of your active job postings under the state's pay disclosure law. Within the hour, a senior engineer will email you invoking Minn. Stat. 181.173.
This is a decision-driven scenario. You will face three real decisions that a VP of People encounters when Minnesota's Department of Labor comes knocking, and your choices shape how the story unfolds.
The 4 Stakeholder Bars (top right)
Each bar starts at 50%. Your decisions shift them. There’s no perfect answer. only trade-offs.
Minnesota Stack
Minnesota's pay laws stack. Minn. Stat. 181.173 (posting disclosure), the Equal Pay for Equal Work Act, and the salary-history ban work together. Your decisions must account for all three.
Legal References
Law references appear throughout. Click them to read the relevant statute.
Minn. Stat. 181.173. Pay Range in Postings.
Effective January 1, 2025. Employers with 30+ employees in Minnesota must include a starting salary range (or a fixed pay rate if no range exists) and a general description of benefits and other compensation in every posting. Enforced by the MN Department of Labor and Industry; an aggrieved applicant or employee may also bring a private action.
MN Equal Pay Certificate of Compliance.
Required for 40+ employee businesses bidding on state contracts worth $500,000+. Loss blocks state contracting in Minnesota. Recertified every four years.
MN Equal Pay for Equal Work Act.
No employer may pay employees less than another for "substantially similar work." Permissible justifications: a documented seniority or merit system, or a bona fide factor such as education, training, or experience.
MN Whistleblower Act (Statutes 181.932).
An employee who raises a pay disparity or requests pay range information under Minn. Stat. 181.173 is protected from retaliation. Damages: reinstatement, back pay, attorneys’ fees. Any adverse treatment adds a parallel claim.
You're halfway through your first coffee when Legal forwards you an email marked URGENT. RESPONSE REQUIRED.
"Dear Ms. Wahlberg, MN DLI is reviewing Bay Lake Software's compliance with Minn. Stat. 181.173. Our public-records review identifies fourteen (14) active postings lacking the starting salary range and the general description of benefits and other compensation required for Minnesota roles."
"Because Bay Lake holds a state contract, separate Equal Pay Certificate obligations under Minn. Stat. 181.101 may also be implicated. We encourage you to confirm your certificate status with the Department of Human Rights independently of this posting review."
"Please respond within ten (10) business days with (1) a remediation plan, (2) documentation of good-faith ranges and methodology, and (3) your forward-looking compliance process."
"Sincerely, Investigator S. Goldberg, Labor Standards Division, Minnesota Department of Labor and Industry"
Before you can finish reading, Jordan Reeves, Head of Recruiting, calls from down the hall.
"Anika, fourteen postings. I counted them. None have a pay scale."
You "How did that happen?"
Jordan "Nobody built a check into the ATS. The template defaults to 'competitive compensation.' Hiring managers don't override it."
You "And our pay bands are 18 months old."
Jordan "Worse. The L5 engineering band says $95K to $125K. We hired three people last quarter at $130K to $142K. The posted range won't match our offer letters."
Jordan "And we hold a $1.2M DOE contract up for renewal in Q2, so our Equal Pay Certificate is in the mix too. But the immediate problem is the postings. Ten business days. What do we tell them?"
Fourteen non-compliant postings under Minn. Stat. 181.173, enforced by the MN Department of Labor and Industry. Because you hold a state contract, your Equal Pay Certificate (a separate, contractor-only regime) is also in play. And the stale bands expose you to MN Equal Pay for Equal Work Act claims: back pay plus liquidated damages plus attorneys’ fees.
Ten business days. Your bands are 18 months stale.
How do you respond?
"Update every pay band to current market and put a compliant pay scale on every active posting within 48 hours. Then we respond to the MN DLI with a corrective action plan AND a commitment to a privileged pay equity audit run through outside counsel."
Jordan "The audit is going to show that six current employees are below the new minimum of their own band. And probably that the MN DLI penalty layer is real."
You "I know. We find it before the MN DLI does. Privileged audit, then remediation. We choose the order."
By Friday, the updated postings are live. Your response to the MN DLI includes a corrective action plan, a timeline, and a confidential commitment to a privileged pay equity audit. Senior Deputy Director Alvarez's office acknowledges receipt and notes that the voluntary audit will be considered in any further enforcement evaluation.
Minn. Stat. 181.173 penalties are per-employee, per-posting. Proactive remediation is a mitigating factor in MN DLI enforcement. Crucially, committing to a privileged pay equity audit run through outside counsel does two things: it surfaces the MN Equal Pay for Equal Work Act exposure before a plaintiff's attorney does, and it creates an attorney-client privileged process that, properly run, protects the working papers from civil discovery while preserving your obligation to remediate.
"Fix the 14 postings. Respond to the MN DLI addressing exactly the posting violation. The pay gap finding is a separate matter we'll evaluate internally."
Jordan "What if the MN DLI asks for the bona fide factor documentation? They specifically requested it in the letter."
You "We send what we have. We don't manufacture documentation we don't have."
Your response addresses the 14 postings. The Labor Standards Division writes back: "Your remediation of the postings is noted. Your response is silent on the good-faith methodology and the bona fide factor documentation requested in our original correspondence. Please advise within ten days whether Bay Lake Software intends to provide this documentation, or whether we should proceed under our independent investigative authority."
Responding only to what was asked is technically permissible. But the MN DLI asked for two things: the posting remediation AND bona fide factor documentation under MN Equal Pay for Equal Work Act. Answering only the easy half signals to the regulator that the harder half is the part you cannot defend. The follow-up letter is worse than the original because now you have demonstrated awareness of the gap without willingness to address it.
"Ask outside counsel to request a 30-day extension. We need time before we commit."
Jordan "And the 14 live postings without a pay scale?"
You "They stay up. I don't want to post ranges we'll have to change."
Investigator Goldberg denies the extension: "Each posting that stays live without the required disclosures keeps the violation open. We are moving to a formal investigation under our independent authority. We have also flagged your state-contract status to the Department of Human Rights for separate review of your Equal Pay Certificate."
A candidate screenshots a still-live posting. LinkedIn: "Bay Lake under MN DLI investigation. Postings STILL up." 800 likes and climbing. Three class-action firms start advertising to Bay Lake employees in Minneapolis.
Under Minn. Stat. 181.173, every posting that stays live without a starting salary range and a benefits description is an ongoing breach. Extension requests don't pause the exposure: they extend it. MN DLI can escalate to a formal investigation, at which point the timeline is no longer yours.
While you were drafting, this landed in your inbox.
"Hi Anika, Under Minn. Stat. 181.173, I'm formally requesting the pay scale for my current position (Sr. Software Engineer, L5). Thank you."
You pull up the L5 compensation file in Minneapolis:
| Employee | Title | Years | Rating | Salary |
|---|---|---|---|---|
| Lauren Mitchell | Sr. Software Engineer | 4.5 | Exceeds | $118,400 |
| Brian Kowalski | Sr. Software Engineer | 3.5 | Meets | $142,000 |
| Gap | −16.6% | |||
Same title, same level. She has more experience and better ratings. He was hired during the Q3 2024 talent crunch at a 20% premium. Everyone called it a market adjustment.
Under Minnesota's Equal Pay Law, "the market" is not a defence.
Bay Lake Software's legal team has listed three reasons for the $23,600 gap between Lauren and Brian. Under Minnesota's Equal Pay Law, which of these can legally justify a pay difference?
Click each to mark it LEGAL or ILLEGAL, then submit.
0 of 3 marked
"Thank you for the call, Anika. I'll be direct."
She shares her screen. On it: her last three performance reviews, her offer letter, and the text of Minn. Stat. 181.173.
"Two weeks ago, a recruiter from Stripe told me they'd start me at $145K for the same role. I wasn't looking, but I ran the numbers. That's when I started asking questions internally."
"I can't confirm exact numbers, but based on conversations, I believe I'm significantly below at least one male colleague at the same level. He was hired after me. His ratings are lower."
"Under Minn. Stat. 181.173, I have the right to request the pay scale for my position. I'm making that request formally."
Lauren has invoked Minn. Stat. 181.173. Minnesota law requires you to provide the pay scale for her position. But your L5 band is 18 months old and doesn't reflect the premiums you paid during the talent crunch. Whatever number you share will either confirm her suspicion or create a new problem.
"Lauren, I'm going to update our L5 band to reflect current market rates. I'll have the updated pay scale to you by end of week. And I'm going to be straight with you. I think you're right that there's a gap worth looking into."
Lauren "I appreciate that. But Anika, when I get that pay scale and see where I sit versus where Brian sits, we both know what the next conversation is going to be."
You "I know."
Lauren "I don't want to leave Bay Lake Software. I want Bay Lake Software to be the kind of company that fixes this without me having to hire a lawyer."
She pauses.
Lauren "But I will hire one if I have to."
Minn. Stat. 181.173 requires employers to provide the pay scale for the position. Sharing an outdated band that doesn't match what you're actually paying creates discoverable evidence of a broken system. Updating first is more work.but it's defensible work.
"Lauren, here's the L5 pay scale: $95,000 to $125,000."
A pause.
Lauren "The max is $125K?"
You "That's the current band on file, yes."
Lauren "Then how is someone at the same level making more than $125K? Because I know they are. Either the band is wrong, or someone is being paid outside the system. Both of those are problems."
She's right. Brian's $142K blows through the top of the band. You've just given Lauren proof that Bay Lake Software's compensation framework is broken.or selectively applied.
Sharing a pay scale that doesn't match reality creates worse evidence than sharing nothing. If Lauren's lawyer later discovers Brian is paid $17K above the band maximum, the outdated scale becomes Exhibit A: proof that the company doesn't follow its own rules.
"Lauren, I want to make sure I give you accurate information. Let me pull the data together properly. Can I get back to you in two weeks?"
Lauren "Two weeks for a number you should already have?"
She's polite about it. But you can hear the Stripe offer ticking in the background.
Lauren "I'll wait two weeks. But Anika.the fact that it takes two weeks to tell me the pay range for my own job title tells me something about how this company thinks about pay. And it's not great."
She accepts Stripe's offer eleven days later. She doesn't file a complaint. She doesn't need to.she just leaves. And she tells the other three women on the engineering team why.
Under Minnesota’s Equal Pay Act, Lauren had the right to know the pay scale for her position. Taking two weeks to produce a number you should already have signals that pay data isn’t managed. which is exactly the conclusion she drew. The compliance cost was +1. The real cost was losing a top-performing engineer to a competitor who publishes ranges publicly. Under Minn. Stat. 181.173, maintaining current pay scales isn’t optional. it’s a recordkeeping requirement.
Tom Brennan has modeled three scenarios. Click each card for the breakdown.
Under MN Equal Pay for Equal Work Act, "market rate" is not a defence. Back pay plus liquidated damages is the floor. Minn. Stat. 181.173 violations stay open.
Posting fix clears the immediate MN DLI finding. The privileged audit surfaces MN Equal Pay for Equal Work Act exposure before a plaintiff's attorney does. MN DLI weights voluntary remediation in mitigation.
A class action attorney is already tagging Bay Lake employees on LinkedIn. Lauren has spoken to a lawyer. The Minn. Stat. 181.173 violations are public record.
Before the CFO meeting, reflect. There's no right answer.but where you stand shapes how you lead. Click on the grid to place yourself.
CFO Tom Brennan has run the numbers.
Brennan "Update every band and level up everyone below the new minimum: $2.1 million annually. 1.8% of revenue."
"Adjust only formal complaints — Lauren plus two or three more — $280K. A fraction."
"You're about to tell me why the smaller number costs more."
You "Lauren alone, under Minnesota Equal Pay Law: $94K back pay, plus liquidated damages equal to that, plus attorney's fees. 'Market rate' is not a defence."
Brennan "How many more Laurens are there?"
You "I don't know. That's the problem."
"Present your options at the leadership meeting tomorrow."
Brennan wants targeted fixes. $280K. Your General Counsel just told you a class action attorney has been advertising on LinkedIn, tagging Bay Lake Software employees in posts about Minnesota pay equity rights. Three more employees have filed Minn. Stat. 181.173 pay scale requests this week.
The CEO is in the room. She'll back whoever makes the stronger case.
"The full audit will cost us $2.1 million in remediation, phased over twelve months. Here's what it buys: a defensible position if the MN DLI investigates our Minnesota pay data report. A response to the class action attorney circling our employees. And a story we can tell candidates.we fixed it before anyone made us."
Brennan "I don't love the number. But I like the alternative less. The last company the MN DLI went after settled for $15 million."
The CEO nods. "Do the audit. Under privilege. And Anika. I want a timeline on my desk by Friday."
A privileged pay equity audit, conducted under attorney-client privilege with outside counsel, lets you find and fix gaps before they become lawsuits. The key: the audit itself may be protected from discovery. Individual complaint-by-complaint fixes are not.
"Two tracks. Resolve Lauren now — adjustment plus back pay. Commission a pay equity analysis over Q2. Full remediation next comp cycle."
Brennan "Does that create documents a plaintiff's attorney can subpoena?"
You "Through outside counsel, it's privileged."
Brennan "Then run it through outside counsel. And make sure Lauren signs something."
Lauren accepts the adjustment but doesn't sign a release. The analysis reveals 11 more employees with similar gaps. Six months later, you're back in Brennan's office with a bigger number.
Outside counsel creates attorney-client privilege protecting the document, not the underlying facts. The 11 employees still have the same rights Lauren exercised under Minnesota’s Equal Pay Act. Privilege buys time, not absolution.
"This is the right approach. We handle the squeaky wheels."
Narrator Six weeks later, Lauren's attorney files a charge with the MN Department of Human Rights and notice of a civil claim under the state Equal Pay Act. The complaint names 11 other women in the Minneapolis office, all paid below male comparators.
"Our clients, twelve current and former Bay Lake employees, have filed alleging systemic violations of the Minnesota Equal Pay for Equal Work Act (Minn. Stat. 181.66-181.71). We are also evaluating Minn. Stat. 181.173 claims for failure to maintain compliant pay scales."
The complaint-by-complaint approach lasted six weeks.
Twelve named employees turns a pay dispute into a systemic claim. Under Minnesota’s Equal Pay for Equal Work Act, each can recover the unlawful pay differential plus liquidated damages and attorney fees. It also keeps Minn. Stat. 181.173 posting exposure open as a separate matter.
Read Bay Lake Software's draft Compensation Policy. Click on any section that contains a compliance violation.
Some sections are compliant. Click Submit when you've flagged all the problems you can find.
Bay Lake Software Inc.
Compensation Policy 2026. Draft for Review
Section 2. Job Posting Policy.
"Pay scales will be included in job postings for positions physically located in Minnesota. Fully-remote roles, roles where the hiring manager has not finalised the band, and confidential executive searches may use 'competitive compensation' language at the recruiter's discretion."
Section 3. Workforce Demographics
Total headcount: 2,200 across 5 states. Gender split: 61% male, 39% female. Breakdown by level, function, and location available in the HRIS.
Section 4. Pay Setting Methodology
"Compensation is determined by market benchmarking, individual negotiation, and prior salary history where available and legally permitted."
Section 5. Pay Scale Disclosure
"Pay scales will be provided to Minnesota employees upon written request to their HRBP. Requests will be processed within 30 business days."
Section 6. Posting Recordkeeping
Bay Lake Software maintains records of the pay scales and benefits descriptions used in postings, consistent with Minn. Stat. 181.173. Records are retained for the duration of the role plus three years.
Section 8. Pay Discussion Policy
"Employees may discuss their own compensation with colleagues. However, sharing compensation data of other employees obtained through HR system access or managerial authority is prohibited and may result in disciplinary action."
0 section(s) flagged
Minn. Stat. 181.173. Effective Jan 1, 2025. Employers with 30+ Minnesota employees must post a starting salary range (or a fixed rate if no range) plus a general description of benefits and other compensation. Enforced by MN DLI; private action also available.
Equal Pay Certificate (Minn. Stat. 181.101). Contractor-only regime via MN Department of Human Rights. Applies solely to businesses seeking large state contracts, not a general posting-enforcement route.
MN Equal Pay for Equal Work Act (181.66-181.71). Equal pay for substantially similar work.
Salary History Ban (Minn. Stat. 181.172). Effective Jan 1, 2024. Cannot ask. Cannot use, even if volunteered.
MN Whistleblower Act (181.932). Anti-retaliation. Employees may raise pay disparity, request 181.173 ranges, or report violations without reprisal.
You scored . Every choice had a cost. Try a different path?