Washington, D.C. Pay Transparency Law: The 2026 Employer Guide
Date Published
Washington, D.C. Pay Transparency Law: The 2026 Employer Guide
If you hire anyone in the District of Columbia, your job postings already have to show pay. The Wage Transparency Omnibus Amendment Act of 2023 took effect on June 30, 2024, and it reaches further than most people expect. It covers any employer with even one employee in D.C., no matter how small the company. From that date, you must publish a salary or hourly range in every advertised role, tell candidates about health benefits before the first interview, and stop asking about wage history. The Office of the Attorney General enforces it, and fines climb to $20,000 per violation for repeat offenders. If you recruit across the DMV — D.C., Maryland, and Virginia — you now juggle three overlapping rulebooks. This guide breaks down who is covered, what a compliant range looks like, how enforcement works, and the steps to lock down before your next posting goes live.
TL;DR
- D.C.'s Wage Transparency Omnibus Amendment Act took effect June 30, 2024, amending the D.C. Wage Transparency Act (D.C. Code § 32-1451 et seq.).
- It applies to any employer with at least one employee in D.C. — there is no size threshold. Federal and D.C. government employers are excluded.
- Every advertised job listing and position description must state the minimum and maximum projected salary or hourly pay, based on a good-faith belief at the time of posting.
- You must disclose the existence of healthcare benefits to applicants before the first interview, and you may not ask about or rely on wage history.
- You must post a workplace notice telling employees their rights under the law.
- The Attorney General enforces the law. Fines are $1,000 (first violation), $5,000 (second), and $20,000 (each later one). There is no private right of action.
What the D.C. Wage Transparency Act actually requires
D.C. already had a Wage Transparency Act on the books from 2014, but it mostly protected employees who discussed their pay. The 2023 amendment, signed into law and effective June 30, 2024, added the posting rules that make D.C. look like the other pay transparency states. It sits in the D.C. Code at § 32-1451 and following.
As Mercer's analysis of the law notes, the amended law does four distinct things. First, it forces you to put a pay range in every job posting. Second, it makes you disclose whether the role comes with healthcare benefits, and to do that before you interview anyone. Third, it bans wage-history questions during hiring. Fourth, it requires a physical notice in your workplace so employees know these rights exist. Each piece is simple on its own. Together, they push you to have clean, defensible pay data before you advertise a single role.
The posting rule is broad by design. It reaches "all job listings and position descriptions advertised," which includes external ads and internal announcements about promotions and transfers. Whether you post the job yourself, use a recruiter, or run it through a job board, the range has to be there.
Who is covered
This is where D.C. is stricter than most states. The law applies to any individual, firm, association, or corporation that employs one or more employees in the District. There is no 10-, 15-, or 25-employee floor like you see in Maine, Illinois, or Massachusetts. A single part-time employee in D.C. is enough to pull you in, as Jackson Lewis explains in its compliance summary. Only the federal government and the D.C. government itself are carved out.
For multistate employers, the practical takeaway is straightforward. If you have any D.C. footprint at all, treat every D.C.-tied posting as covered. If you already publish ranges to satisfy Colorado, New York, or California, you are most of the way there — but D.C. adds the healthcare-benefits disclosure and the workplace-notice steps that those states do not all require.
What counts as a compliant pay range
You cannot post a placeholder like "$1 to $1,000,000" and call it done. The statute requires the minimum and maximum projected salary or hourly pay you actually expect to offer for the role.
The good-faith standard
The range has to reflect a genuine, good-faith belief of what you would pay a successful applicant at the time you publish the posting. That standard is the same idea you have seen in other jurisdictions: the number should be tied to a real pay structure, not invented to satisfy the letter of the law. If your posted range is wide, be ready to explain why — a role that genuinely spans two levels, a wide geographic band, or a market you are still calibrating. The cleanest defense is a documented salary structure and defensible pay ranges that show where each number comes from.
One nuance worth flagging: the D.C. law speaks to "salary or hourly pay." It does not, on its face, require you to spell out bonuses, commissions, or other variable pay in the range the way some states encourage. Disclosing that context is still good practice, but the core obligation is the base pay range.
Health benefits and the wage-history ban
Two requirements set D.C. apart from a plain posting law.
First, you must disclose the existence of healthcare benefits that the employee may receive, and you must do it before the first interview. Note the wording: you disclose that benefits exist, not every plan detail. A short line in your posting or your pre-interview communication handles it.
Second, D.C. joins the growing list of jurisdictions with a wage-history ban. You may not screen prospective employees based on their wage history, ask about it, or require that prior pay meet certain criteria. This matters because wage history is one of the ways pay gaps get carried from job to job. Pulling that question out of your process protects candidates and protects you. If you want to see where a candidate should land, anchor the offer to your internal range and a structured job evaluation, not to what they made before.
How D.C. enforces the law (and what it costs)
The D.C. Office of the Attorney General has investigatory and enforcement authority. The Attorney General can investigate complaints, bring civil actions, and seek relief for an individual or for the public at large, as laid out in the OAG's business advisory on wage transparency. The Mayor assesses the civil fines. Importantly, there is no private right of action — an aggrieved employee cannot sue you directly under this law, but they can file a complaint that triggers government enforcement.
The fines escalate with each violation:
Violation | Civil fine |
|---|---|
First violation | $1,000 |
Second violation | $5,000 |
Third and each subsequent violation | $20,000 |
Because "violation" can attach to individual postings, a company that leaves ranges off a batch of listings can see exposure add up quickly. The workplace notice requirement is easy to overlook and easy to fix: post the required notice where employees congregate, alongside your other labor-law postings.
D.C. vs. Maryland and Virginia: the DMV picture
Most D.C.-area employers hire across all three DMV jurisdictions, and the rules do not line up neatly.
Jurisdiction | Range in postings? | Covered employers |
|---|---|---|
Washington, D.C. | Yes, plus benefits disclosure and wage-history ban | 1+ employee in D.C. |
Maryland | Yes, in the posting or on request | Employers hiring for D.C.-area and Maryland roles |
Virginia | Recently tightened disclosure rules | See the Virginia guide |
If you operate across the region, build one process that satisfies the strictest rule in each column, then apply it everywhere. For the details on your neighbors, see the Maryland pay transparency guide and the Virginia pay transparency guide. For the national view, the 2026 multi-state compliance guide maps every active law in one place.
If your ranges are inconsistent from posting to posting, that is usually a sign your underlying pay structure needs work before you worry about the notice board. See how PointFactors builds defensible ranges so the number in your posting can survive a challenge.
How to comply before your next posting
Work through this short list and you will cover the D.C. requirements:
- Add a minimum and maximum salary or hourly range to every advertised D.C. role, internal and external.
- Make sure each range reflects a good-faith offer tied to a real pay structure, not a token spread.
- State that healthcare benefits exist before the first interview.
- Remove wage-history questions from applications, screening scripts, and interview guides.
- Post the required workplace notice where D.C. employees congregate.
- Document how you set each range so you can defend it if the Attorney General asks.
Frequently asked questions
When did the D.C. pay transparency law take effect? The Wage Transparency Omnibus Amendment Act of 2023 took effect on June 30, 2024. It amends the earlier D.C. Wage Transparency Act at D.C. Code § 32-1451 et seq.
Which employers have to comply? Any employer with at least one employee in the District of Columbia, regardless of size. Only the federal government and the D.C. government are excluded. A single part-time D.C. employee is enough to trigger coverage.
What has to be in a D.C. job posting? The minimum and maximum projected salary or hourly pay for the role, based on your good-faith belief at the time of posting. You must also disclose that healthcare benefits exist before the first interview.
Can we ask candidates about their salary history in D.C.? No. The law prohibits screening prospective employees based on wage history and prohibits asking about it. Anchor offers to your internal range instead.
What are the penalties for non-compliance? The Mayor assesses civil fines of $1,000 for a first violation, $5,000 for a second, and $20,000 for each subsequent violation. The Attorney General enforces the law, and there is no private right of action.
Does the law require a workplace notice? Yes. You must post a notice informing employees of their rights under the Act in a conspicuous place where employees congregate, alongside your other required labor-law postings.
Pay transparency is no longer a patchwork you can wave off. D.C.'s one-employee threshold means almost every regional employer is covered, and the only durable way to comply across the DMV is a pay structure that produces the same defensible range every time. Book a PointFactors demo and see how point-factor job evaluation gives you ranges you can post with confidence — in D.C. and everywhere else you hire.
Justin Hampton is the founder and CEO of PointFactors, where he helps HR and compensation teams build defensible, transparent pay structures with AI-powered point-factor job evaluation.