Which Pay Transparency Laws Cover a Public Agency, and at What Headcount

Your HR team is about to add a pay range to every job posting because a compliance newsletter said the law now requires it. Before anyone spends a week rewriting those templates, find out whether your agency is covered at all. The answer comes from a definition inside each statute, and 2 of those definitions name public employers while another writes some public positions out.

The spread is wider than most summaries suggest. A city with 12 employees sits outside every one of those definitions, while a school district with 40 is inside 4 of them. Hawaii can leave a state agency outside the duty at any size, where the pay comes from a bargaining agreement.

Government and public sector agencies tend to adopt the strictest rule they have read about and apply it everywhere. That costs effort where it was never owed. It also misses the 1 state where the duty did apply.

Coverage Is Decided Inside Each Statute's Definition

Every one of these laws opens with a definitions section, and the definition of employer is where the public-sector question is settled. Some legislatures wrote that definition out in plain terms. Others wrote the same definition generally, and left the sector question to be inferred from the ordinary meaning of employer.

Checking the difference is worth an hour of your time before it is worth a policy. An hour spent now replaces a quarter of template rework later on, and it tells you which states to ignore. Reading 1 definition tells you whether the rest of the statute applies to your postings, and reading it wrong commits your team to work in the wrong jurisdictions. 2 legislatures removed the guesswork by writing the answer into the definition itself.

The 2 States That Name Public Employers Outright

The 2 legislatures that did so are Massachusetts and Minnesota. Both of those legislatures settled the question inside the definition itself. Each did it in a single phrase:

• Massachusetts General Laws chapter 149 section 105F defines a covered employer as any employer, public or private, that employs 25 or more employees in the commonwealth. The same section defines a pay range as the annual salary range or hourly wage range that the covered employer reasonably and in good faith expects to pay for the position at that time.
• Minnesota Statutes section 181.173 applies to an employer with 30 or more employees at 1 or more sites in Minnesota, and its definition of employer includes an individual, corporation, partnership, association, nonprofit organization, group of persons, state, county, town, city, school district, or other governmental subdivision.

Minnesota's version is the most useful to a public agency, because it enumerates the entities. A school district reading those enumerated entities needs no opinion from counsel about whether it counts as an employer. Massachusetts gives a district the same certainty in 3 words.

Both drafting choices spare an agency the argument. Hawaii drafted its own provision the other way round, starting from coverage, and the difference is not cosmetic for an agency near the line. Read it as written and the carve-out is the operative part of the provision.

The State That Writes Public Positions Out

Starting from coverage is the reason a blanket public-sector policy misfires. Hawaii Revised Statutes section 378-2.8 is where the misfire starts. It which requires a job listing to disclose an hourly rate or salary range reasonably reflecting the actual expected compensation. Its second paragraph then removes 3 categories:

• Positions that are internal transfers or promotions within a current employer.
• Public employee positions for which salary, benefits, or other compensation are determined pursuant to collective bargaining.
• Positions with employers having fewer than 50 employees.

The middle exclusion covers a large share of public employment in the state, and most career classifications in a Hawaii agency fall under it. A recruiter filling one of those posts has no listing duty at all. Nothing about the agency's headcount changes that, in either direction.

The same agency filling an unbargained management role may well be inside the duty. Nothing about the 2 posts differs except the classification. Position is the unit of analysis here, so coverage can differ between 2 vacancies posted in the same week by the same recruiter.

The Threshold Ladder, 4 Employees to 50

Those position-level questions decide whether a law applies to you, and the headcount decides when. Read together, the 7 provisions verified for this article run across a 46-employee spread.

Why the Wording of a Threshold Changes the Count

Hawaii is the row to read twice. Its figure appears as an exclusion for employers with fewer than 50 employees. The drafting starts from coverage and carves downward from there.

Washington puts its figure under a heading marked application. California and Illinois put theirs inside the duty sentence. The effect is identical at the extremes and different near the line, where a definition running to the whole statute reads more broadly than a limit in 1 subsection.

What These Laws Ask for, and How Long the Records Last

Those subsections matter once a law covers you, and then the duties are narrow and concrete. Each statute names what a posting has to contain, and 1 of them sets a retention period that outlasts the employee:

• Washington RCW 49.58.110(1)(a) requires the employer to disclose in each posting for each job opening the wage scale or salary range, and a general description of all of the benefits and other compensation to be offered to the hired applicant.
• California Labor Code 432.3(c)(3) requires an employer with 15 or more employees to include the pay scale for a position in any job posting.
• Illinois 820 ILCS 112/10(b-25) makes it unlawful for an employer with 15 or more employees to fail to include the pay scale and benefits for a position in any specific job posting.
• California Labor Code 432.3(c)(4) requires the employer to maintain records of a job title and wage rate history for each employee for the duration of the employment plus 3 years after the end of the employment.

That last item is the one agencies underestimate. A retention period measured from the end of employment means the record has to survive the person, the hiring manager, and usually the applicant tracking system that produced it. Your records schedule has to name it, because nothing about a job posting feels like a record worth keeping at the moment it is written.

Why No Statute Here Requires Public Sector Training

Those duties are the whole of the list, and nothing follows them. None of the 7 provisions above imposes a training obligation on an employer, a manager or an HR team. What does exist is posting content, record retention and the prohibition on retaliation.

Any vendor presenting a course as the compliance requirement for pay transparency is describing something the statutes never ask for. That is worth saying plainly before anybody opens a procurement conversation. Training still has a job here, and it is not this one. Ask a vendor 3 questions before you sign anything:

• Ask which statutory provision the course is said to satisfy.
• Ask whether that provision names training, or names a posting duty.
• Ask who in your agency the duty really falls on.

Where Public Sector Training Does Change the Outcome

These laws place a compliance decision with people whose job title has nothing to do with compliance. A department administrator drafts the vacancy notice, a hiring manager copies the previous posting and updates the closing date, and a recruiter sends the same text to 3 boards. One of those boards is read in another state. None of the 3 is deciding to break a rule, and each of them can.

Public sector training earns its place at that point, and its role is narrow. KC Library carries HR and employment compliance training for the people who write and approve postings. The definition and the threshold then reach the person drafting the notice. That is the only place either of them changes an outcome.

Where the wider hiring process needs attention, the same approach covers the steps around the posting. Annual training keeps that knowledge current as definitions change. Anything beyond it is a policy choice your agency makes on its own. No statute in the table above requires any of it.

Which Postings You Should Check First

That choice comes after the coverage question, and the coverage question is answerable in an afternoon. The order matters more than the effort, so start with the definition, then the headcount, then the position, because each one can end the inquiry before the next one is needed.

Work through these before the next requisition opens:

1. Read the definition of employer in each state where your agency posts, and write down whether it names public bodies.
2. Count your employees the way the statute counts them, by commonwealth, by state, or across sites, since the tests differ.
3. Check each vacancy against the position-level exclusions, and treat a bargained classification in Hawaii as a separate case from an unbargained one.
4. Name the person who owns the posting template, and give them the definition and the threshold in writing.
5. Add the posting and its pay range to your records schedule, with a retention date measured from the end of employment.

Step 4 removes most of the risk. It is a training and documentation problem with a settled legal answer behind it. A definition held in a memo to counsel never reaches the administrator drafting a notice on a Thursday afternoon, and that administrator is the person the duty runs through.

KC Library carries the HR and employment compliance courses that put the definition and the threshold in front of them. That is the practical answer to a duty the statutes assign to whoever writes the posting. No memo to counsel does the same job, because nobody drafting a notice reads one.

The laws will keep changing, and the definitions will keep being the part that decides coverage. An agency that knows which of its postings are covered, at what headcount, and by which position-level exclusion can answer a complaint with a document. One that adopted the strictest rule it read about is doing more work than it owes in some states, and still missing the one place the duty applied.

Frequently Asked Questions

1. Do pay transparency laws cover public agencies?

It depends on the state, and the answer is in each statute's definition of employer. Massachusetts General Laws chapter 149 section 105F defines a covered employer as any employer, public or private, with 25 or more employees in the commonwealth. Minnesota Statutes section 181.173 defines employer to include a state, county, town, city, school district, or other governmental subdivision. Other statutes define employer generally and leave the question to the ordinary meaning of the term.

2. What is the smallest employer covered by a pay transparency posting law?

Of the provisions verified for this article, New York reaches the smallest employer. Labor Law section 194-b defines an employer as an entity employing 4 or more employees in any occupation, industry, trade, business or service. Washington, California, and Illinois each set 15, Massachusetts sets 25, and Minnesota sets 30.

3. Are collectively bargained public positions exempt?

In Hawaii, yes. Hawaii Revised Statutes section 378-2.8 does not apply to job listings for public employee positions whose salary, benefits, or other compensation are determined pursuant to collective bargaining. The exclusion operates position by position, so a single agency can have covered and excluded vacancies at the same time. No equivalent exclusion appears in the other statutes cited here.

4. How long does an employer have to keep pay range records?

California Labor Code section 432.3(c)(4) requires an employer to maintain records of a job title and wage rate history for each employee for the duration of the employment plus 3 years after the end of the employment. Because the period runs from the end of employment, the record has to outlast the applicant tracking system that generated the posting.

5. Do any pay transparency laws require employee or manager training?

No. None of the provisions cited here imposes a training obligation. The duties are posting content, record retention, and anti-retaliation. Training is a business decision an agency makes on its own, and it matters because the people who draft and approve postings are the ones the duty runs through.

References

1. M.G.L. c.149 s.105F, Wage range transparency, Massachusetts General Laws.
2. Minn. Stat. 181.173, Salary ranges required in job postings, Minnesota Statutes.
3. HRS s.378-2.8, Job listing; disclosures, Hawaii Revised Statutes.
4. RCW 49.58.110, Disclosure of wage or salary range by employer, Revised Code of Washington.
5. Cal. Lab. Code 432.3, Salary information, California Labor Code.
6. 820 ILCS 112/10, Illinois Equal Pay Act, Illinois General Assembly.
7. N.Y. Lab. Law 194-b, Pay transparency, New York State Legislature.