Summary. Two related bodies of law now govern compensation. Pay equity statutes prohibit paying employees differently for comparable work absent a legitimate justification, and most state versions have broadened the comparison standard beyond the federal equal-work test while narrowing the available defenses. Pay transparency statutes require disclosure of pay ranges in postings, to employees on request, and in some jurisdictions reporting of aggregate pay data. This guide explains both, identifies where state requirements differ operationally, walks through a privileged pay audit and what to do with the results, and sets out the compensation infrastructure that makes compliance sustainable.

An employer posts a software engineering role in five states. In two, the posting must include a pay range. In one, it must include a range and a general description of benefits and other compensation. In another, the range must be posted only if the employer has fifteen or more employees. In the fifth, no range is required but the employer must provide one to an applicant on request after an interview.

The same employer maintains a single national compensation structure and hires remotely, so an engineer in the state with no posting requirement will see the range that was posted for the state that requires one, will compare it to their own salary, and will ask a question the employer must be able to answer.

That is the actual compliance problem. Transparency laws do not merely add a line to a job posting. They make the entire compensation structure visible, to employees and to plaintiffs' counsel, and they do so in a legal environment where the substantive standard for justifying pay differences has become materially stricter.

Pay equity: the substantive rules

The federal Equal Pay Act

29 U.S.C. § 206(d) prohibits paying employees of one sex less than employees of the opposite sex for equal work on jobs requiring equal skill, effort, and responsibility, performed under similar working conditions, in the same establishment.

The plaintiff's showing is straightforward and does not require proof of intent: identify a comparator of the opposite sex performing substantially equal work at higher pay. Job titles do not control; actual duties do.

The four statutory defenses, on which the employer bears the burden:

  1. A seniority system;
  2. A merit system;
  3. A system measuring earnings by quantity or quality of production; or
  4. A differential based on any other factor other than sex.

The fourth defense is where the litigation happens. Courts have divided over whether the factor must be job-related and whether it must serve a legitimate business purpose, and the Ninth Circuit's Rizo v. Yovino line held that prior salary alone cannot justify a differential — a position several other circuits and a growing number of state statutes have adopted by decision or by legislation.

Title VII independently prohibits compensation discrimination on the basis of race, color, religion, sex, and national origin, requires intent rather than merely a differential, does not require an equal-work comparator, and permits disparate impact claims. The Lilly Ledbetter Fair Pay Act provides that an unlawful compensation practice occurs each time compensation is paid pursuant to a discriminatory decision, so each paycheck restarts the charge-filing clock, with back pay limited to two years preceding the charge.

State pay equity statutes

Most states have their own, and the material differences are three.

1. A broader comparison standard. Many states replaced "equal work" with "substantially similar work" — a composite of skill, effort, responsibility, and working conditions — which permits comparisons across job titles and departments that the federal standard would not. California, New York, Massachusetts, New Jersey, Washington, Oregon, Colorado, and others use some version of it.

2. Broader protected categories. Several statutes reach race and ethnicity as well as sex, and some reach any protected characteristic.

3. Narrower defenses. The typical state formulation requires that a differential be based on a bona fide factor other than sex — such as education, training, or experience — that is not based on or derived from a sex-based differential, is job related with respect to the position, and is consistent with a business necessity. Several statutes add that the employer must show the factor accounts for the entire differential, and some permit the employee to defeat the defense by showing an alternative business practice that would serve the same purpose without producing the disparity.

Also common in state statutes:

  • A broader geographic scope than the federal "same establishment," reaching all of an employer's locations within the state or, in some formulations, statewide comparisons.
  • Prohibitions on pay secrecy — employees may not be forbidden to discuss their compensation, and retaliation for doing so is unlawful. Note that the National Labor Relations Act independently protects such discussions for non-supervisory employees at essentially all private employers.
  • Salary history bans, discussed below.
  • Longer limitations periods and enhanced damages, including liquidated or treble damages in several states.
  • Affirmative-defense safe harbors for employers that conduct a good-faith self-evaluation and remediate — Massachusetts and Oregon are the leading examples, and this provision is a significant reason to conduct an audit.

The operational consequence: an employer with employees in multiple states cannot maintain one analysis. It must know, for each state, what the comparison standard is, which characteristics are protected, and what will justify a difference.

Pay transparency: the disclosure rules

Requirements cluster into four categories, and jurisdictions combine them differently.

1. Pay range in job postings. A growing number of states and localities require that a posting include the salary or hourly range the employer in good faith expects to pay. Variations that matter:

  • Whether the requirement applies to all postings or only to those for positions that may be performed in the state — which for remote roles is nearly all of them.
  • Whether benefits and other compensation (bonus, commission, equity) must be described.
  • Employer size thresholds, which range from one employee to fifteen or more.
  • Whether third-party postings by recruiters and job boards are covered — several statutes reach them explicitly, and one imposes obligations directly on the third party.
  • Record retention requirements for job descriptions and wage rate history.
  • Whether promotional and transfer opportunities must be posted internally with ranges.

2. Disclosure on request or at a defined point. Some jurisdictions require the employer to provide the range to an applicant on request or after an initial interview, and to a current employee on request, on a change in position, or annually.

3. Salary history bans. Roughly half the states and many localities prohibit asking about an applicant's prior compensation. Variations: whether the prohibition extends to relying on volunteered information; whether the employer may verify history after an offer with the applicant's consent; and whether it reaches independent contractors and internal transfers.

4. Pay data reporting. A few jurisdictions require employers above a size threshold to file aggregated pay data:

  • California requires annual pay data reports, disaggregated by establishment, job category, race, ethnicity, and sex, with mean and median hourly rates, and a separate report covering labor contractor employees. Penalties apply for non-filing.
  • Illinois requires covered employers to obtain an Equal Pay Registration Certificate, submitting individual employee-level wage data and certifying compliance with equal pay obligations, with recertification on a cycle.
  • Other states have enacted or proposed reporting regimes, and the requirements change.

Federal contractors have historically faced additional affirmative action and compensation analysis obligations administered by the Office of Federal Contract Compliance Programs. That framework has been substantially altered by executive action, and contractors should confirm the current state of their obligations directly rather than relying on prior guidance — while noting that contract clauses already incorporated into existing agreements, and separate obligations under Section 503 and VEVRAA, continue to operate on their own terms.

Internationally, the EU Pay Transparency Directive requires member states to transpose by mid-2026 a regime including pay information for applicants before interview, a prohibition on asking about pay history, employee rights to information on average pay levels by category, gender pay gap reporting for employers above size thresholds, a joint pay assessment where an unjustified gap of 5% or more exists in a category, and a shift of the burden of proof to the employer in pay discrimination claims. Multinational employers should plan for it now, because the data infrastructure it requires takes more than a year to build.

Conducting a pay audit

The single most valuable exercise in this area, and the one most often done badly.

Set it up for privilege

An audit that finds disparities creates a document a plaintiff will want. Protect it:

  • Engage outside counsel to conduct the audit, in a written engagement letter stating that the purpose is to provide legal advice regarding compliance with pay equity laws and to assess litigation risk.
  • Counsel retains the statistician or consultant as counsel's agent, under a separate engagement referencing the privileged purpose.
  • Label documents appropriately and limit distribution to those with a need to know.
  • Communicate through counsel, and avoid parallel unprivileged analyses in HR systems and email that duplicate the work.
  • Understand the limits. Privilege protects the analysis and counsel's advice; it does not protect the underlying facts — compensation data is discoverable regardless. And if the employer later asserts a good-faith self-evaluation defense under a state safe harbor, or relies on the audit to justify decisions, it will likely be found to have waived privilege as to the audit. That is a deliberate trade, and it should be made consciously rather than discovered.

Do the analysis

Step 1 — Define comparator groups. This is the analytical heart. Group employees performing substantially similar work, considering skill, effort, responsibility, and working conditions — not job titles. Use the job architecture if one exists; build one if it does not. Document the reasoning for each grouping, because the grouping determines the result and it will be challenged.

Step 2 — Assemble the data. Base pay, bonus, commission, equity value, and total compensation; job level and title; location; tenure in role and with the company; performance ratings; education and prior experience; full- or part-time status; and demographic data. Data quality is usually the binding constraint, and cleaning it takes longer than the analysis.

Step 3 — Choose the method.

  • Cohort review — direct comparison within small groups. Appropriate for small populations and intuitive to explain.
  • Multiple regression — models pay as a function of legitimate factors and identifies unexplained variance associated with a protected characteristic. Appropriate where group sizes support it (roughly thirty or more per model), and the standard method in litigation.

Step 4 — Select explanatory variables carefully. Include only factors that are legitimate, job-related, and consistently applied. Two cautions:

  • Do not include a variable that is itself tainted. Prior salary is the classic example; including it "explains" a gap that the law says may not be explained that way. The same concern applies to a performance rating system that itself shows demographic skew.
  • Do not overfit. A model with enough variables will explain anything, and a model whose variables were chosen to make the gap disappear is worse than no model.

Step 5 — Interpret. Look at the magnitude of any unexplained difference, its statistical significance, and — importantly — the individual outliers that a regression may mask. Aggregate parity coexisting with several badly paid individuals is still a problem.

Step 6 — Investigate. For each flagged difference, ask what actually happened: a hiring negotiation, a market adjustment, a retention counteroffer, a performance history, a transfer at legacy pay. Frequently there is a legitimate explanation that is simply not written down anywhere, and writing it down is the remediation.

Remediate

Where a difference is unexplained:

  • Raise the underpaid employee. Do not reduce anyone; most state statutes prohibit remedying a violation by reducing another employee's wages, and it is terrible practice besides.
  • Decide on retroactivity. Prospective adjustment is the norm; back pay reduces exposure and increases the cost. Counsel should evaluate the limitations exposure in each state.
  • Communicate carefully. A memo saying "we are correcting a pay equity violation" is an admission. A conversation about a market adjustment or a compensation review is accurate and does not create the document. This is a genuine judgment call and it should be made with counsel; being cute about it is worse than being direct.
  • Fix the process that produced the disparity — a negotiation-driven starting salary, a manager-discretion bonus pool with no criteria, a promotion process with no posting.
  • Document the analysis and the remediation, because state safe harbors require it.

Where a difference is explained, write the explanation into the compensation record so that the next audit does not re-open it and so that a future plaintiff's counsel sees a contemporaneous rationale rather than a post hoc one.

Cadence. Annually, aligned with the merit cycle, and after any acquisition or significant reorganization.

Building the infrastructure

Compliance is not sustainable as a series of audits. It requires a compensation structure that produces defensible outcomes by default.

Job architecture. A defined set of job families, levels, and titles, each with a description of scope, required skills, and expected experience. Everything else — ranges, comparator groups, posting, and career paths — depends on it. This is the foundational project and it typically takes a quarter.

Pay bands. A minimum, midpoint, and maximum for each level and, where warranted, each geography, benchmarked against survey data. Bands should be wide enough to accommodate legitimate differences and narrow enough to be meaningful. Publishing them internally is increasingly the norm and it is what transparency laws are pushing toward in any event.

Documented criteria for placement within a band — experience, credentials, specialized skills, performance, geography, and internal equity — with a required written rationale for any offer above the midpoint or outside the band.

Approval discipline. Every offer, adjustment, and promotion reviewed against the band and the criteria, by someone other than the hiring manager, with the rationale recorded. This single control prevents most disparities from arising, because the great majority originate at hire and at counteroffer.

Geographic differentials applied by a stated rule rather than case by case — a national structure with defined tiers, or a location-based approach — and applied consistently to remote employees.

Removal of salary history from the process entirely: from applications, from screening scripts, from applicant tracking system fields, and from recruiter training. Where an applicant volunteers it, train recruiters not to record it and not to use it.

Performance and promotion process discipline, because compensation disparities frequently originate in ratings and advancement rather than in pay decisions. Calibrate ratings, post internal openings, and review promotion rates by demographic group.

Manager training. Managers make most of the decisions that create exposure, and most have never been told what the standard is. Train them on the bands, the criteria, the prohibition on asking about salary history, the prohibition on restricting pay discussions, and what to say when an employee asks about the posted range.

Handling the posting requirement in practice

Determine coverage per posting. For each open role, identify the states and localities in which it may be performed — which for a remote role is every state where the employer will hire — and apply the strictest applicable requirement.

The practical choice. Employers take one of three approaches:

  • Post ranges everywhere. Simplest, most consistent, and increasingly the market norm. It removes the operational complexity entirely and it signals confidence in the structure.
  • Post only where required, with jurisdiction-specific templates. Preserves flexibility, creates real complexity, and produces the awkward situation where the same role is posted with a range in one state and without in another — which employees notice.
  • Exclude covered jurisdictions from remote roles. Several employers tried this and most abandoned it: it shrinks the candidate pool, it is visible and reputationally costly, and at least one state has taken the position that excluding its residents from remote roles to avoid the posting requirement violates the statute.

Setting the range. It must be the range the employer in good faith expects to pay for the position. A range of $60,000 to $300,000 is not a good-faith range and several statutes and enforcement agencies have said so. Set it from the band, narrowed to the level and location actually being hired.

What else to include where required: hourly or salary basis, bonus and commission opportunity, equity, and a general description of benefits. Where not required, consider including it anyway — candidates compare total compensation, and a posting showing only base salary underrepresents the offer.

Update postings when the band changes, and remove stale postings. A posting that remains live for a year with an outdated range is an easy claim.

Recruiters and job boards. Provide the range to every external recruiter with a written instruction to include it, and audit their postings. Several statutes reach third parties, and in any event the employer will be the defendant.

Internal postings. Where promotional opportunities must be posted internally with ranges, build it into the process rather than treating it as an exception. Employers frequently comply externally and forget internally.

When an employee or a regulator asks

An employee asks why a new hire's posted range exceeds their salary. This will happen, and the answer determines whether it becomes a claim.

  • Do not be defensive, and do not suggest the question is inappropriate. Discussing pay is protected activity under state statutes and under the NLRA, and discouraging it is independently unlawful.
  • Explain the structure: how bands are set, what determines placement, and what drives progression.
  • Check the actual facts before responding substantively. If the employee is genuinely below where the criteria would place them, fix it.
  • Escalate patterns. Several similar questions from a demographic group is data.

An agency charge or a demand letter arrives.

  • Issue a litigation hold covering compensation records, offer approvals, performance ratings, and the communications of the decision-makers.
  • Assess privilege over any prior audit, and decide deliberately whether to rely on it.
  • Identify the comparators the claimant will use and the ones the employer would use, and analyze both.
  • Assemble the contemporaneous justification for each relevant decision. Its absence is the most common reason these cases settle.
  • Evaluate the safe harbor if the state has one and the employer conducted a qualifying self-evaluation and remediated.

A pay data report is due. Treat it as a compliance filing, not a data dump: run the analysis on the data before submitting it, because the state will, and because the filing itself frequently identifies the disparity that generates the inquiry. Several employers have first learned of a problem from their own report.

A twelve-month implementation plan

Months 1–2. Inventory obligations by jurisdiction for every state and locality where the employer has or will have employees. Build a matrix: posting requirement, on-request disclosure, salary history ban, pay data reporting, pay secrecy prohibition, comparison standard, protected characteristics, and safe harbor.

Months 2–4. Build or refresh the job architecture and pay bands. Benchmark against survey data. Define placement criteria and geographic differentials.

Months 3–5. Conduct a privileged pay audit. Investigate flagged differences. Design remediation.

Months 5–6. Remediate. Fix the processes that produced the disparities.

Months 6–7. Update the posting process, applicant tracking system fields, recruiter scripts, offer templates, and approval workflows. Remove salary history everywhere.

Months 7–8. Train recruiters, hiring managers, and HR business partners.

Months 8–9. Update the handbook and policies, including the pay discussion policy and any internal posting commitment.

Months 9–12. File required reports. Establish the annual cadence: audit, band refresh, obligation matrix update, and training.

Two candid observations

First, transparency is arriving regardless of law. Compensation data circulates among employees, on public platforms, and through recruiters, and the practical question for an employer is not whether its structure will be visible but whether it will withstand being visible. An employer with defensible bands and documented criteria is fine. An employer whose pay reflects a decade of individual negotiations is not, and no drafting fixes that.

Second, most disparities are not the product of bias in any deliberate sense. They accumulate: a candidate who negotiated harder, a counteroffer matched, a legacy salary carried through an acquisition, a manager who advocated for one report and not another. Nobody decided to pay anyone less because of a protected characteristic, and the outcome is nonetheless a legal problem and a real one.

Which means the fix is structural rather than corrective. Bands, criteria, approvals, and an annual audit prevent the accumulation. Everything else in this guide is downstream of getting those four things in place.

Litigating a pay equity claim

Understanding how these cases are tried informs how to prepare for them.

The plaintiff's case. Identify a comparator, establish that the work is equal or substantially similar depending on the statute, and show the pay difference. Under the federal Equal Pay Act this is a strict liability showing — no intent, no pretext analysis — and the burden then shifts entirely to the employer. Under Title VII the plaintiff must show intent, typically through the McDonnell Douglas framework or through direct evidence, but need not identify an equal-work comparator.

Comparator selection is the fight. Plaintiffs choose the highest-paid person doing arguably similar work; employers respond that the roles differ in scope, in reporting line, in revenue responsibility, or in the specialized skill required. The evidence is job descriptions, organizational charts, actual duties as testified to by the incumbents, and the employer's own job architecture — which is why building one matters even before any claim exists. An employer whose job descriptions do not match what people actually do has handed the plaintiff the argument.

The employer's defense. Identify the factor, show it is bona fide and job-related, show it was applied consistently, and — under most state statutes — show it accounts for the entire differential. That last element defeats many defenses: an employer proving that experience explains four percentage points of a nine-point gap has not carried its burden.

Class and collective treatment. Equal Pay Act claims proceed as collective actions under the FLSA's opt-in mechanism; Title VII claims proceed as Rule 23 classes. Certification turns on whether pay decisions were made under a common policy or by dispersed managers exercising discretion — and the irony is familiar from other contexts: an employer with a uniform, centralized structure is more susceptible to certification, while one with unfettered manager discretion may defeat certification and lose badly on the merits. The answer is a uniform structure that produces defensible outcomes, not decentralized chaos.

Statistical evidence is central in aggregate cases, and both sides retain labor economists. The disputes are about the model: which variables belong, whether prior salary or performance ratings are themselves tainted, whether the unit of analysis is the right one, and whether the sample supports the inference.

Damages. Back pay, and under the EPA an equal amount as liquidated damages unless the employer proves good faith and reasonable grounds. Several state statutes provide for treble damages or extended limitations periods. Attorney's fees are recoverable. Interest and, for future losses, front pay may be awarded.

Settlement dynamics. These cases settle on the strength of the employer's contemporaneous documentation more than on anything else. An employer that can produce, for each challenged decision, a dated approval showing the criteria applied and the rationale given, settles cheaply or wins. An employer producing a spreadsheet and a manager's recollection does not.

Special situations

Acquisitions. The most reliable source of new disparities. Two workforces with different structures merge, legacy salaries carry over, and within a year the combined population shows gaps that neither predecessor had. Run a pay analysis during diligence — it is a real liability and it should be priced — and again within ninety days after closing, with a plan to converge the acquired population into the acquirer's bands over a defined period. Budget for the convergence, because the answer is always to raise rather than to cut.

Commissioned sales roles. Compensation varies with territory, account assignment, and quota, none of which is neutral. The equity question is frequently not about the plan but about who got which territory, and the analysis should examine assignment as well as payout. Document the assignment criteria.

Executive compensation. Small populations defeat regression, so cohort review and market benchmarking do the work. Compensation committees should receive the pay equity analysis alongside the market data, and the minutes should reflect that they considered it.

Part-time and job-shared roles. Compare on a full-time-equivalent basis, and be careful that benefits eligibility thresholds do not produce a disparity that correlates with a protected characteristic.

Contingent workers and staffing agency employees. California's pay data reporting expressly reaches labor contractor employees, and several equity statutes reach joint employers. An employer whose lowest-paid workers are all contractors and whose demographics differ from its direct workforce has a data story it should understand before someone else tells it.

Unionized workforces. A collective bargaining agreement's wage scale is generally a strong defense — a negotiated seniority or classification system is a statutory defense under the EPA — but it is not absolute, and the classification structure itself can be challenged if it segregates by protected characteristic. Coordinate any remediation with the union; unilateral adjustments to represented employees' pay are a labor law problem independent of the equity question.

Startups and rapid growth. Disparities compound fastest where hiring is rapid, bands do not exist, and offers are negotiated individually by founders. The cheapest moment to build a structure is at roughly fifty employees; the most expensive is at three hundred, after two years of ad hoc offers and a transparency law arrives.

A sample compensation decision record

The documentation that prevents most of this exposure is short. Every offer, adjustment, and promotion should generate a record containing:

  • The position, its job family, level, and location tier.
  • The band — minimum, midpoint, and maximum — in effect on the decision date.
  • The proposed compensation, base and variable, and its position within the band expressed as a compa-ratio.
  • The placement rationale, referencing the stated criteria: years and relevance of experience, specific credentials or specialized skills, scope of prior responsibility, performance history for an internal move, and any market factor with the survey source cited.
  • Internal equity check — how the proposed pay compares to incumbents in the same job family and level in the same location tier, with any difference explained.
  • Approver and date, by someone other than the requesting manager.
  • Any exception to the band, with the business justification and a second-level approval.

That is a one-page form, it takes a manager ten minutes, and it is the single artifact that most reliably converts a contested pay decision from a credibility contest into a documented business judgment. Employers that adopt it typically find, in the first quarter, that a meaningful percentage of proposed offers do not survive the internal equity check — which is the control working exactly as intended, before the disparity exists rather than three years later in an audit.

On the question of whether to publish bands internally. Employers hesitate, expecting a wave of complaints. The experience of employers that have done it is generally the opposite: publication surfaces a small number of genuine problems immediately, which are cheaper to fix than to litigate, and then substantially reduces the volume of compensation conversations because employees can answer their own questions. It also forces the discipline that makes everything else in this guide work, because a band nobody sees can be ignored and a band everyone sees cannot. Employers that are not ready to publish should ask themselves why — and the answer is usually that the structure would not withstand scrutiny, which is the finding rather than the objection.

Primary authority

Pay transparency is a state-law patchwork sitting on top of two long-standing federal statutes.

  • 29 U.S.C. § 206(d) — the federal Equal Pay Act, its four affirmative defenses, and the "any other factor other than sex" catchall that most litigation turns on.
  • 42 U.S.C. § 2000e-2 — Title VII, which reaches compensation discrimination on additional protected bases and, unlike the EPA, requires intent.
  • 42 U.S.C. § 2000e-5(e)(3) — the Lilly Ledbetter Fair Pay Act accrual rule: each discriminatory paycheck restarts the charge-filing clock.
  • 29 U.S.C. § 215(a)(3) and § 206(d)(3) — retaliation, and the reason a pay-secrecy policy is dangerous even where no transparency statute applies.
  • 29 U.S.C. § 157 — Section 7 of the NLRA, which protects concerted discussion of wages for most non-supervisory employees regardless of state law.
  • Colo. Rev. Stat. §§ 8-5-101 to 8-5-203 — the Equal Pay for Equal Work Act and its job-opportunity posting requirements, the earliest comprehensive regime.
  • Cal. Lab. Code § 432.3 and § 1197.5 — pay scale on request, posting in job advertisements for employers with fifteen or more employees, the pay data report under Cal. Gov't Code § 12999, and the salary-history ban.
  • N.Y. Lab. Law § 194-b and § 194 — statewide range disclosure and the comparator standard of substantially similar work.
  • Wash. Rev. Code § 49.58.110 and Ill. Comp. Stat. ch. 820 § 112/10 — posting requirements with private rights of action and statutory damages.
  • 29 C.F.R. Part 1620 — the EEOC's Equal Pay Act interpretive regulations.

Related articles

This guide is provided for general informational purposes and does not constitute legal advice. Pay transparency and pay equity requirements differ substantially by state and locality, change frequently, and interact with federal contractor obligations that have themselves been altered by executive action. Consult qualified employment counsel before conducting an audit or changing a compensation practice.