Minnesota Pay Transparency Rules for Employers

Which Minnesota employers must include pay ranges in job postings?

Any employer with 30 or more employees at one or more sites in Minnesota must comply, and the definition expressly covers nonprofits and public employers such as a county, city, or school district. The threshold is total employees in Minnesota, counted across all of your Minnesota sites combined rather than site by site. Employers under 30 Minnesota employees are not subject to the disclosure requirement, though many post ranges anyway because applicants increasingly expect them.

The defining language: “‘Employer’ means a person or entity that employs 30 or more employees at one or more sites in Minnesota and includes an individual, corporation, partnership, association, nonprofit organization, group of persons, state, county, town, city, school district, or other governmental subdivision.” (Minn. Stat. § 181.173, subd. 1(b)). That enumeration answers a question readers at a nonprofit or a public employer routinely get wrong. The state, counties, towns, cities, school districts, and other governmental subdivisions are named employers on the same 30-employee terms as a private company.

Past the aggregation rule, the statute is silent on how you run the count. Subdivision 1(a) limits the section’s definitions to “Employer,” “Posting,” and “Salary range,” so § 181.173 never defines “employee,” never says whether part-time or seasonal workers count, never mentions independent contractors, and names no measurement date. Minn. Stat. § 645.08(1) directs that words be construed “according to rules of grammar and according to their common and approved usage,” while words that have acquired a special meaning are construed by that special meaning. That canon supplies no counting rule of its own, and it applies only where the construction would not be “inconsistent with the manifest intent of the legislature, or repugnant to the context of the statute.” Section 645.08 names no words at all, so it does not tell you whether “employee” is a term with an acquired special meaning; that question belongs to a definitional statute in the operative chapter or to case law. Section 181.173 does not define “employee,” supplies no counting method, and says nothing about a worker misclassified as a contractor, so the question stays open until a court or the Department of Labor and Industry answers it. The contractor question is its own audit area in Minnesota; for the analytical framework, see our overview of the employee versus independent contractor test.

Two related gaps deserve naming rather than papering over. The threshold is tied to work sites, and the statute neither defines “site” nor says how a fully remote Minnesota employee counts. Count employees at Minnesota sites, treat the status of a fully remote Minnesota employee as an open question, and count conservatively where the answer moves you across 30. The statute likewise does not say when the headcount is measured. The only timing language in the section fixes your good faith pay estimate “at the time of the posting of an advertisement for such opportunity,” Minn. Stat. § 181.173, subd. 1(d), and that clause governs the salary figures rather than the employee count. If your Minnesota headcount moves across 30 during the year, treat the measurement date as an open question until a court or the Department of Labor and Industry answers it, run the count when each posting goes live, and keep the payroll record that supports it.

The threshold is fixed, not phased. There is no graduated rule for employers in the 25-to-29 range, and the section imposes no reduced or partial posting obligation below 30.

What does the pay-disclosure rule actually require?

Two disclosures, both in each posting: the starting salary range, and a general description of all of the benefits and other compensation. The controlling subdivision states: “An employer must disclose in each posting for each job opening with the employer the starting salary range, and a general description of all of the benefits and other compensation, including but not limited to any health or retirement benefits, to be offered to a hired job applicant.” (Minn. Stat. § 181.173, subd. 2(a)).

The “starting” qualifier is meaningful. The rule asks for the range a successful applicant would land in at hire, not the lifetime ceiling for the role, and the text ties the disclosure to hire-time pay in two places: subdivision 2(a) reaches compensation “to be offered to a hired job applicant,” and subdivision 1(d) fixes the range to your good faith estimate as of the posting date. A range that pretends a senior performer’s salary is the floor is not a starting range. Conversely, a range that tops out at the maximum you would ever pay misrepresents the actual hiring envelope.

The benefits description is “general” rather than line-by-line, so a category-level summary fits the phrase. It has to reach everything you will offer, though, including the other compensation the clause names alongside benefits. The statutory standard is a general description of all of the benefits and other compensation, which is a completeness standard rather than an effort standard. One point of precision worth carrying: the good faith standard in this section attaches to the salary range under subdivision 1(d), not to the benefits description.

The statute’s only examples of benefits are health and retirement, and the clause is expressly open ended, so a bonus, equity grant, profit sharing, or sign-on payment you will offer belongs in the posting. Vague boilerplate such as “competitive benefits package” does not satisfy this rule, because it identifies none of the benefits offered and does not disclose the health or retirement benefits the statute names. The cleanest postings list five to eight lines of benefits in plain English, with one or two lines on bonus or equity if either applies.

If you will not offer a range at all, the statute gives you an affirmative path rather than leaving you with a bare prohibition: “An employer that does not plan to offer a salary range for a position must list a fixed pay rate. A salary range may not be open ended.” (Minn. Stat. § 181.173, subd. 2(b)). Silence about pay is not an option, and neither is an open bottom or top end.

How specific does the salary range have to be?

It must be your good faith estimate of the minimum and maximum compensation for the job opportunity as of the posting date. The statutory definition: “‘Salary range’ means the minimum and maximum annual salary or hourly range of compensation, based on the employer’s good faith estimate, for a job opportunity of the employer at the time of the posting of an advertisement for such opportunity.” (Minn. Stat. § 181.173, subd. 1(d)).

Three operative points sit inside that one sentence. The range needs both a minimum and a maximum. An hourly range satisfies the statute for an hourly role. And the estimate is measured as of the posting date rather than against what you later pay, so a range that was honest when published does not become a violation because the hire was ultimately paid outside it.

“Good faith” is the operative phrase, and it works as a content rule. Because the good faith language sits inside the definition rather than in a separate command, a posting carrying a range you never honestly estimated has not disclosed a “salary range” at all, and so fails subdivision 2(a). Subdivision 2(b) then closes the two structural workarounds: no open-ended range, and a fixed pay rate where you will not offer a range.

Minnesota law sets no percentage limit on how wide a posted range may be. Subdivision 1(d) defines the salary range as the minimum and maximum compensation “based on the employer’s good faith estimate . . . at the time of the posting,” and subdivision 2(b) adds two things: a fixed pay rate where you will not offer a range, and that a range “may not be open ended.” What matters is whether you can show you would genuinely have paid both the floor and the ceiling for that job on the day the posting went up. A floor of $80,000 with a ceiling of $105,000 reads as a real range if both ends are ones you would actually pay; a floor of $80,000 with a ceiling of $200,000 invites the question of whether either number was an estimate at all.

Employers sometimes look to the early-adopter states for room to post a very wide range. Colorado is the closest thing to that room, and it is narrower than it looks. Colorado has required compensation in job postings since January 1, 2021, and its statute requires an employer to “in good faith disclose” the hourly or salary compensation or the range of it. Colo. Rev. Stat. § 8-5-201(2). That good faith duty dates from the 2023 amendment, effective January 1, 2024; the text enacted in 2019 carried no good faith clause. Colorado’s rule then allows a posted range that “may extend from the lowest to the highest pay the employer in good faith believes it might pay for the particular job.” 7 Colo. Code Regs. § 1103-18, Rule 11.1.2. California also rests the figure on good faith, but measures it more narrowly: a posted “pay scale” means “a good faith estimate of the salary or hourly wage range that the employer reasonably expects to pay for the position upon hire.” Cal. Lab. Code § 432.3(m)(1). That California definition took effect January 1, 2026. Within Minnesota’s own text, subdivision 2(b) bars an open-ended range while setting no limit on how wide a range may be, and subdivision 1(d) still requires the range to rest on your good faith estimate.

What benefits and bonus categories must appear in the disclosure?

Both benefits and other compensation. Subdivision 2(a) requires “a general description of all of the benefits and other compensation, including but not limited to any health or retirement benefits.” The “including but not limited to” language is intentional. It signals that health and retirement are the floor, not the ceiling, of what the description must cover. The disclosure obligation runs to whatever you would in fact extend at hire: any health care benefit, any retirement contribution, paid leave categories, and any other compensation an applicant should know about before deciding whether to apply.

A workable benefits description block lists, at minimum: health and dental coverage (with a brief note on employer contribution if material), retirement contribution (401(k) match percentage, vesting summary, or pension category), paid time off and holiday categories, applicable leave benefits, and any tuition assistance, equity, or wellness benefits you offer. Equity disclosure deserves its own attention: see our discussion of enforceability of equity promises in recruiting for why ambiguous equity language at the posting and offer stage causes the most disputes downstream.

Minnesota’s paid family and medical leave program sits differently from a benefit you fund and provide. Benefits under it “are paid from state funds and are not considered paid from any special insurance plan, nor as paid by an employer” (Minn. Stat. § 268B.03, subd. 2), the employee applies to the commissioner rather than to you (Minn. Stat. § 268B.04, subd. 1), and covered employment excludes the self-employed, independent contractors, and seasonal employees (Minn. Stat. § 268B.01, subd. 15). Section 181.173 does not name the program among the required disclosures; whether a state-administered benefit the employee claims from the commissioner sits inside “all of the benefits and other compensation . . . to be offered to a hired job applicant” is a question the text does not answer. Describing the program is still sound practice for most postings, particularly where your own terms beat the statutory floor. What chapter 268B actually requires is a workplace notice and a written notice to each employee (Minn. Stat. § 268B.26). Chapter 268B defines a seasonal employee at Minn. Stat. § 268B.01, subd. 35, as an individual employed no more than 150 days during any consecutive 52-week period in hospitality by an employer whose average receipts during any six months of the preceding calendar year were not more than 33 percent of its average receipts for the other six months, and it requires the employer to apply to the department and certify those facts. For such an employee the chapter requires the opposite of a benefits pitch: notice at the time of the employment offer that the employee is not eligible to receive paid family and medical leave benefits while so employed (Minn. Stat. § 268B.26(f)). Benefit payments under the program began January 1, 2026 under 2023 Minn. Laws ch. 59, art. 1, § 42, so the program is live rather than forthcoming.

The “other compensation” piece is where employers most often underdisclose. A role that pays a base of $80,000 plus a discretionary bonus historically running 10-to-15 percent should say so. A role with equity participation should name it, even if the structure is “RSU grant per executive compensation policy.” Generic boilerplate such as “comprehensive benefits” does not work. The disclosure is not asking for grant agreements; it is asking for honest categories the applicant can evaluate. For a parallel discussion of how Minnesota handles wage disclosure protections among existing employees, see our article on legal risk of salary disclosures under pay transparency laws.

How does the rule apply to commission, hourly, and tipped positions?

The statute uses “annual salary or hourly range of compensation” in the definition, which means hourly rates count and carry the same good faith estimate standard that applies to salaried roles. A retail role posted at “$18.00 to $22.50 per hour” is compliant if those numbers reflect the actual hiring envelope for the position. A role posted at “$15 to $40 per hour” invites the question of whether either end was an estimate.

Commission-based roles and tipped positions are not exempt. Section 181.173 limits its reach in only two ways, neither tied to pay structure: the employer must clear the 30-employee threshold, and the solicitation must meet the definition of a posting. For a commission-heavy role, the cleanest disclosure is the expected total annual compensation a typical performer earns, with a plain-English note on the commission structure (rate, draw, ramp), and commission itself falls inside the required general description of other compensation. A “base only” disclosure for a commission-heavy role tells an applicant almost nothing about the offer. Tips sit differently, because customers pay them rather than you offering them, and a posting that gives only the base hourly rate on a heavily tipped role still misstates the real offer, so disclosing the base rate alongside a labeled historical tip range is the better practice. The section never uses the word “tip,” and it does not require you to predict future tip amounts.

The recurring failure mode in sales-heavy organizations is a posting that lists only the base salary on a role where 60 percent of total compensation is variable. That misstates the real offer in a way you would not stand behind in a meeting. The fix is mechanical: publish a target on-target-earnings figure alongside the base.

How does the rule reach internal promotions, remote work, and out-of-state hires?

The statute applies to “each posting for each job opening with the employer.” A posting is “any solicitation intended to recruit job applicants for a specific available position, including recruitment done directly by an employer or indirectly through a third party,” and the definition does not stop there. The definition goes on to include “any postings made electronically or via printed hard copy, that includes qualifications for desired applicants” (Minn. Stat. § 181.173, subd. 1(c)). The definition reaches recruitment by you and recruitment through a third party, and it reaches electronic and printed postings alike. It carves out nothing for internal audiences, so an internal-only intranet listing, a public careers-page posting, and a recruiter’s distribution of a role specification are each a posting when the solicitation targets a specific available position and states qualifications.

Internal promotion solicitations open to current employees are covered on the same terms. The words “internal,” “promotion,” and “current employee” appear nowhere in the section, and the definition opens with “any solicitation.” Two limits do apply. A promotion filled without any solicitation falls outside the definition, and so does a general internal announcement not tied to a specific available position or stating no qualifications. A purely spoken “anyone interested in the warehouse manager role, talk to Nancy” hallway announcement states no qualifications, so it sits outside the definition on that ground. Whether the definition’s reference to electronic and printed hard copy media also excludes a spoken solicitation is untested, because no Minnesota court has construed the clause and the Department of Labor and Industry has issued no rule on it. A written internal listing is inside the definition when it is a solicitation intended to recruit applicants for a specific available position and it states the qualifications for that role, since both elements are required and the definition addresses the medium and the recruiter without addressing the audience.

Coverage turns on where your employees are, not on where the company sits. An employer is “a person or entity that employs 30 or more employees at one or more sites in Minnesota” (subd. 1(b)), so a company headquartered elsewhere with 30 or more employees at Minnesota sites is covered, and a company with no Minnesota site and no Minnesota employees is not. Once you are covered, the duty runs to “each posting for each job opening with the employer” (subd. 2(a)), with no geographic limit on the posting. Nothing in the section excuses a remote role, a role based outside Minnesota, or a posting a Minnesota resident is unlikely to fill, and the Department of Labor and Industry has adopted no rule under this section. The conservative rule is therefore also the simple one: publish a Minnesota-compliant range on every public posting. The cost of a single uniform format is small compared to the cost of explaining a state-by-state divergence in an audit.

What counts as a job posting under the rule?

Any solicitation intended to recruit applicants for a specific available position that includes qualifications for desired applicants. The statutory text: “‘Posting’ means any solicitation intended to recruit job applicants for a specific available position, including recruitment done directly by an employer or indirectly through a third party, and includes any postings made electronically or via printed hard copy, that includes qualifications for desired applicants.” (Minn. Stat. § 181.173, subd. 1(c)).

Two limiters sit inside that definition and decide most gray-zone questions: the solicitation must target a specific available position, and it must state qualifications for desired applicants. Three implications follow. First, a job-board listing on Indeed or LinkedIn is a posting. Second, a retained-search firm’s listing distributed by the recruiter to its network is also a posting if it names a specific open position and includes qualifications, and the disclosure duty still runs to you rather than to the search firm. Third, a brief social-media teaser saying “we are hiring,” with no qualifications and no identified open position, is not necessarily a posting. That reading is untested, because no Minnesota court has construed the definition and the Department of Labor and Industry has issued no rule on it, so treating a recruitment message as a non-posting is a position you would be taking without support.

A few items fall in the gray zone. Stock language at the bottom of a careers page such as “we are always interested in hearing from talented people” is not a posting because it is not about a specific available position. A LinkedIn post by a recruiter naming a specific role and listing required experience is a posting and triggers the rule. A networking-event flyer naming open positions and qualifications is a posting. The test runs to specificity plus qualifications, not the medium.

Who enforces the rule, and what triggers an investigation?

Section 181.173 stops at the disclosure duty. It contains no penalty, no damages remedy, no complaint procedure, and no private right of action, and the legislature has not touched it since it took effect.

The Division of Labor Standards in the Department of Labor and Industry administers chapter 181 as a whole, Minn. Stat. § 177.26, subd. 2, and the attorney general may enforce the chapter under Minn. Stat. § 181.1721. The legislature gave the commissioner no enforcement tool aimed at this section, though. Minn. Stat. § 177.27, subd. 4, which lists the sections the commissioner may order an employer to comply with, does not include section 181.173, and the private civil action list in Minn. Stat. § 181.171, subd. 1, does not include it either.

That omission matters more than it first looks, because the rest of the chapter’s machinery keys to the same list. The commissioner’s power to question an employer, employees, and other persons under § 177.27, subd. 1, runs to compliance with “any of the sections listed in subdivision 4,” though the entry-and-inspection power in the same subdivision reaches books, payrolls, and other records that “in any way relate to wages, hours, and other conditions of employment” without that limit. The injunction power in subdivision 5 reaches “any statute or rule listed in subdivision 4.” The cease-and-desist, back-pay, and liquidated-damages remedies in subdivision 7 fire only when an employer “is found by the commissioner to have violated a section identified in subdivision 4,” and the same subdivision’s additional civil penalty of “up to $10,000 for each violation for each employee” applies to a repeated or willful violation of a section identified in that list. The private action in subdivision 8 reaches only sections 177.21 to 177.44 and 181.165. None of those remedies attaches to a posting that omits the salary range.

The routes that remain open sit outside section 181.173. The attorney general may enforce chapter 181 under Minn. Stat. § 181.1721, which routes enforcement through Minn. Stat. § 8.31, where the attorney general may seek injunctive relief and “a civil penalty, in an amount to be determined by the court, not in excess of $25,000.” Subdivision 2(b) also prohibits an open-ended range, and Minn. Stat. § 645.241 makes a statutorily prohibited act a petty misdemeanor where no statute imposes a penalty for it. Whether that default reaches section 181.173 is unresolved, because sections 181.1721 and 8.31 already supply a civil penalty for a chapter 181 violation and no Minnesota decision has decided whether that forecloses the default. If the default does apply, it fits an open-ended range better than a bare failure to disclose, which is an omission rather than a prohibited act.

Practical pressure runs alongside those routes. Applicants self-screen out of rangeless postings. Complaints become public. And the posted range is a dated written record of what you said the job paid, which an applicant or employee can offer as ordinary relevant evidence in a compensation-discrimination claim under the Minnesota Human Rights Act, Minn. Stat. § 363A.08, subd. 2(3), which makes it an unfair employment practice, “[e]xcept when based on a bona fide occupational qualification,” to “discriminate against a person with respect to hiring, tenure, compensation, terms, upgrading, conditions, facilities, or privileges of employment” because of a protected class. The posting establishes the stated range, not discriminatory causation, so the claim still turns on proof that a pay difference was because of a protected characteristic.

The federal picture differs from the state one. No federal statute requires a pay range in a job posting, and the Equal Employment Opportunity Commission has published no guidance treating a posted range, or the absence of one, as evidence in a pay-discrimination case. Federal law reaches the pay decision itself. Title VII, 42 U.S.C. § 2000e-2(a)(1), makes it unlawful for an employer “to discriminate against any individual with respect to his compensation . . . because of such individual’s race, color, religion, sex, or national origin,” and the Equal Pay Act, 29 U.S.C. § 206(d)(1), separately bars paying one sex less than the other for equal work on jobs requiring equal skill, effort, and responsibility under similar working conditions. Both claims are proved by comparing what comparable employees are actually paid, so a published range sitting next to below-range offers is a fact you should be able to explain.

Federal enforcement priorities have also moved. The Commission’s current National Enforcement Plan for fiscal years 2025 through 2029, adopted June 4, 2026, states that “[w]ith the adoption of this National Enforcement Plan, the Commission hereby withdraws the Strategic Enforcement Plan, as well as any District Complement Plans or other local enforcement plans or priorities.” The replacement plan carries no standalone equal-pay priority, though it still names “patterns of discrimination in hiring, lay-offs, job mobility, fringe benefits and/or pay” among the intentional-discrimination matters it will pursue. It directs the agency to prioritize intentional discrimination over disparate impact, and states that it creates no rights enforceable at law. The same plan does list job advertisements that, “on account of a protected characteristic, exclude or discourage certain individuals from applying, or encourage certain individuals to apply,” so the posting document itself sits within federal enforcement attention even though the range is not federally required.

How does Minnesota’s rule compare to other states’ pay-transparency laws?

Minnesota joins Colorado (effective January 1, 2021), Washington (January 1, 2023), California (January 1, 2023, under Cal. Stats. 2022, ch. 559 (SB 1162)), and New York (September 17, 2023, the 270th day after the December 21, 2022 signing of its enacting act) as states requiring pay-range disclosure in job postings. California’s posting requirement dates from Cal. Stats. 2022, ch. 559 (SB 1162), which took effect January 1, 2023. That list is not closed: Mass. Gen. Laws ch. 149, § 105F took effect October 29, 2025, and New Jersey’s P.L. 2024, ch. 91, codified at N.J.S.A. 34:6B-23, took effect June 1, 2025, both described at the end of this section. This article does not survey every state with a posting requirement, so confirm each state in your footprint rather than treating the states named here as the complete set. Each state’s definition of “covered employer,” “covered posting,” and “salary range” differs.

Minnesota’s threshold is 30 employees (Minn. Stat. § 181.173, subd. 1(b)). Cal. Lab. Code § 432.3(c)(3) and Wash. Rev. Code § 49.58.110 each reach employers with 15 or more employees, N.Y. Lab. Law § 194-b reaches employers with four or more, and Colo. Rev. Stat. § 8-5-201 sets no employee-count floor at all. Measured against those four thresholds (Cal. Lab. Code § 432.3(c)(3); Wash. Rev. Code § 49.58.110; N.Y. Lab. Law § 194-b; Colo. Rev. Stat. § 8-5-201), the 30-employee floor in Minn. Stat. § 181.173, subd. 1(b), is the highest, which makes Minnesota’s coverage the narrowest rather than its rule the strictest. California’s 15-employee figure gates only the posting requirement: an employer of any size there must still provide the pay scale to an applicant on reasonable request and to a current employee on request.

Minnesota’s good faith standard and its bar on open-ended ranges sit at Minn. Stat. § 181.173, subds. 1(d) and 2(b). Colorado reached the good faith standard by statute in 2023, effective January 1, 2024, Colo. Rev. Stat. § 8-5-201(2), which also moved the trigger to notification of each job opportunity and added a third required item, the date the application window is anticipated to close. Neither that section nor Colorado’s Posting, Screening, and Transparency Rules expressly bars an open-ended range. Washington reached both points by rule rather than by statute two and a half years into its posting requirement: Wash. Admin. Code § 296-123-060(2), effective July 1, 2025, requires a posted range that reflects the employer’s most reasonable and genuinely expected compensation and that includes a minimum and maximum dollar amount. California redefined its own term effective January 1, 2026, so a posted pay scale is now “a good faith estimate of the salary or hourly wage range that the employer reasonably expects to pay for the position upon hire.”

Consequences differ too. Colorado’s director may fine $500 to $10,000 per violation, with all postings for one opening counting as a single violation. Colo. Rev. Stat. § 8-5-203(2)(c), (4). California’s Labor Commissioner may assess $100 to $10,000 per violation, with no penalty for a first violation if the employer shows every open posting has been updated to carry the pay scale. Cal. Lab. Code § 432.3(d)(4). Washington’s 2025 amendment added a temporary cure window: for postings from July 27, 2025 through July 27, 2027, an employer that corrects a noncompliant posting within five business days of written notice and, where applicable, contacts any third-party posting entity with a demand to correct the posting, faces no penalties, damages, or other relief under that section for the violation. Wash. Rev. Code § 49.58.110(1)(b).

Two duties in those states sit outside the posting itself, which is why a posting-only compliance program is incomplete. Colorado requires a post-selection notice naming the person selected within 30 days of the start date. Washington requires the range on request for an internal transfer or promotion. Colorado’s one break for an employer located entirely outside the state is narrow and dated: fewer than fifteen Colorado employees, all working only remotely, and only through July 1, 2029, during which the employer need give notice only of remote job opportunities.

The most important comparative point: a multi-state employer cannot rely on one state’s format to satisfy the others. A single posting can be lawful everywhere if it is written to carry every covered state’s required items, so the workable approach is one nationwide posting standard built to the most demanding jurisdiction in your footprint, verified state by state. Multi-state retailers and SaaS employers generally find that the compliance cost of one posting standard is materially lower than the cost of a posting matrix. For employers comparing Minnesota practice with neighboring states, see our overview of differences in Minnesota versus Wisconsin employment law compliance.

This area is moving fast. Massachusetts and New Jersey each have a posting requirement already in force (Mass. Gen. Laws ch. 149, § 105F, effective October 29, 2025; N.J. P.L. 2024, ch. 91, codified at N.J.S.A. 34:6B-23, effective June 1, 2025). Other states not discussed here have their own posting rules, so confirm each state in your footprint rather than working from this list. Mass. Gen. Laws ch. 149, § 105F took effect October 29, 2025 and requires an employer with 25 or more employees in the commonwealth to disclose the pay range in the posting. New Jersey’s P.L. 2024, ch. 91, codified at N.J.S.A. 34:6B-23, took effect June 1, 2025 and requires an employer with 10 or more employees to post the hourly wage or salary, or a range of it, plus a general description of benefits and other compensation programs. For employers building a 2026 hiring plan, the safer assumption is that more disclosure will be required by more states each year, not less.

What are the practical risks of getting the disclosure wrong?

Three practical risks, in order of likelihood. First, applicant attrition: candidates self-screen out of postings without a range, and the strongest candidates are the most likely to do so. A noncompliant posting is a hiring-funnel problem before it is a legal problem.

Second, enforcement authority sits at the chapter level rather than at this section. The Division of Labor Standards administers chapter 181 under Minn. Stat. § 177.26, subd. 2, and the attorney general may enforce the chapter under Minn. Stat. § 181.1721. Minn. Stat. § 181.173 itself supplies no complaint procedure, penalty, or private remedy, and the compliance-order list in Minn. Stat. § 177.27, subd. 4, omits it. That is a real limit on what the section itself carries. Minn. Stat. § 181.1721 still routes the attorney general’s enforcement of chapter 181 through Minn. Stat. § 8.31, and whether the petty-misdemeanor default in Minn. Stat. § 645.241 reaches this section is unresolved.

Third, internal-equity exposure. Once a public range goes live, current employees in the same role can see whether they are inside or below it, and a below-range current employee has the foundation for a question that can become a discrimination claim or a wage-disclosure-protected conversation.

The companion rule at the same hiring step is the pay-history ban in the same Human Rights Act section. An employer “shall not inquire into, consider, or require disclosure from any source the pay history of an applicant for employment for the purpose of determining wages, salary, earnings, benefits, or other compensation for that applicant.” Minn. Stat. § 363A.08, subd. 8(b). The same subdivision expressly preserves what a compliant posting already does: nothing in it prevents you from “providing information about the wages, benefits, compensation, or salary offered in relation to a position” or from “inquiring about or otherwise engaging in discussions with an applicant about the applicant’s expectations or requests with respect to wages, salary, benefits, or other compensation.” Subd. 8(e). Disclose your range, discuss what the applicant is looking for, and do not anchor the offer on what the applicant earned before.

The cleanest version of compliance is a written internal procedure: every posting goes through a single reviewer who checks the range against the actual hiring envelope, runs the range against the current pay band for the role, confirms the benefits description matches the offer letter you would issue, and dates the version. A single reviewer is what catches the three failure modes that produce most noncompliant postings: ranges nobody would honor, mismatched benefits descriptions, and stale postings.

A useful adjacency: Minnesota’s wage disclosure protection statute bars you from requiring wage nondisclosure as a condition of employment, from requiring an employee to sign a waiver of the right to disclose wages, and from taking “any adverse employment action against an employee for disclosing the employee’s own wages or discussing another employee’s wages which have been disclosed voluntarily.” Coworkers in the same role may compare their own pay with each other, and an employer that disciplines them for it is exposed under paragraph (a)(3) whether the conversation happens in a breakroom or in a group chat, because the statute says nothing about the medium. The protection does not depend on a posted range; it has applied since 2014.

Two limits the same section does state matter for anything posted publicly. Without your written consent, the section does not permit an employee “to disclose proprietary information, trade secret information, or information that is otherwise subject to a legal privilege or protected by law,” and it does not permit an employee “to disclose wage information of other employees to a competitor of their employer.” Three further points from the same section bear on your housekeeping. If you provide an employee handbook, you must include in it notice of employee rights and remedies under the section. The 2023 amendment broadened the retaliation bar to reach discharge, discipline, penalty, interference, threats, restraint, and coercion. And an employee may bring a civil action, in which a court may order reinstatement, back pay, restoration of lost service credit, and expungement of related adverse records. The pay transparency rule and the wage disclosure protection rule reinforce each other, and an employer that ignored either historically has more housekeeping to do now. For the sequence of duties that bear on the same hiring file (notices, recordkeeping, paystubs), see our employer’s guide to Minnesota wage payment law and the broader Minnesota Wage Theft Act employer obligations overview.

Minnesota’s pay transparency rule is short on words and long on consequences. The substantive ask is small: publish an honest range and an honest benefits description in each posting. The downstream effect is large because the data the rule surfaces, once public, makes prior pay practices visible in ways the prior posting culture obscured. Employers that do the housekeeping (calibrated ranges, clean benefits descriptions, internal review before posting) generally find compliance straightforward and the hiring funnel improves. Employers that do not face a slow accumulation of applicant attrition, internal-equity questions, and exposure to attorney general enforcement under Minn. Stat. § 181.1721 and Minn. Stat. § 8.31. For broader context on Minnesota’s employment-law layer cake, see our Minnesota employment law practice area. If you would like a second set of eyes on a posting template or your internal pay-band review process, email [email protected] with a sample posting and a brief description of the role mix.