Washington, D.C. Pay Transparency Law: Posting Requirements

The D.C. Posting Deadline That Passed — And the Fine Structure That Did Not

Picture this: it is a Tuesday morning and a hiring manager sends you a job description to post by end of day. You drop it into your ATS, push it to Indeed and LinkedIn, and move on. What you may not have flagged — and what your employment counsel almost certainly will — is whether that posting disclosed a minimum pay figure, a maximum pay figure, and a description of benefits. In the District of Columbia, that omission is not a formatting oversight. It is a violation of the Wage Transparency Omnibus Amendment Act, and the fine structure escalates quickly.

The Washington D.C. pay transparency law took effect on June 30, 2024, making the District one of the strictest pay-transparency jurisdictions in the country. It covers employers of any size — even a single D.C. employee is enough to trigger compliance obligations. By the end of this article you will know exactly what your D.C. job postings must include, what the penalty exposure looks like, and how to build a defensible pay range that holds up if your documentation is ever reviewed.

---

What the Law Requires

The Wage Transparency Omnibus Amendment Act (effective June 30, 2024) requires private employers with at least one employee in the District of Columbia to include three elements in every publicly advertised posting for a position located in D.C. (Cooley LLP, 2024):

1. The minimum projected compensation for the role
2. The maximum projected compensation for the role
3. A general description of all benefits and other compensation the employer reasonably expects to offer

"Compensation" covers salary, hourly wages, piece-rate, commissions, and other direct pay. "Benefits" typically includes health coverage, retirement contributions, paid leave, and any other forms of compensation separate from base pay — though you should confirm the current agency guidance on what must be described with the relevant D.C. authority (see the Verify and document section below).

A few points worth noting: the law applies to all employer sizes — there is no minimum headcount threshold, unlike the 15-employee floor in California, Washington State, and Illinois, or the 10-employee floor in New Jersey. If you post a role and at least one of your employees works in D.C., the requirement applies to that posting.

Always confirm the current scope, any rulemaking updates, and enforcement guidance directly with the DC Office of Human Rights or DC Department of Employment Services before acting on any posted summary.

---

Penalty Structure: Three Tiers, Escalating Fast

The D.C. washington dc pay transparency law fine schedule is tiered by repeat-violation status (Mercer, 2024):

Violation number	Civil fine
First violation	$1,000
Second violation	$5,000
Subsequent violations	$20,000

These are civil fines per violation — meaning each non-compliant posting is potentially a separate count. A single hiring push across five platforms without a disclosed range could, in principle, be treated as multiple violations. The penalty exposure at the third offense and beyond — $20,000 per posting — makes this a budget-material risk for any employer, regardless of headcount.

For a full comparative view of how D.C.'s fine schedule compares to other jurisdictions, see our pay transparency penalties explained guide. For a side-by-side of every active state law, the pay transparency laws by state overview is a useful reference.

---

Who Is Covered — and What "At Least One D.C. Employee" Means in Practice

The District's law is deliberately broad on employer coverage. Unlike several state laws that set headcount floors, D.C.'s statute applies to any private employer with one or more employees in D.C. (Cooley LLP, 2024). That includes:

• D.C.-based businesses of any size
• National or regional employers who have even a single remote employee physically located in the District
• Contractors and staffing agencies posting roles to be performed in D.C.

The practical implication for multi-state employers is significant: if your workforce includes anyone in D.C., every posting for a D.C.-based or D.C.-eligible remote role must carry a pay range and a benefits description — even if your headquarters is in a state with no pay-transparency law at all.

Multi-state compliance is genuinely complex. Our pay transparency laws by state guide covers the full landscape of the 16+ states and D.C. that now require salary disclosure, so you can assess your total compliance footprint in one pass.

---

What Goes in the Range: Building a Defensible Minimum and Maximum

The law does not prescribe how you calculate the minimum and maximum — it requires that you post them and that they reflect what you reasonably expect to offer. That word "reasonably" matters: a range so wide it communicates nothing (e.g., $30,000–$200,000 for a single-contributor role) is unlikely to survive scrutiny as a good-faith disclosure.

A defensible range typically has three properties:

1. A market anchor. The market median — the wage below which 50% of workers in that occupation and geography earn — is the standard benchmark. The U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics (BLS OEWS) program produces annual wage estimates for over 800 occupations at the national, state, and metropolitan-area level, drawn from a sample of approximately 1.1 million establishments (BLS, May 2025). D.C.-specific estimates are published in the same release cycle. Confirm the most recent release year for D.C. metro figures at bls.gov/oes before using any figure in your documentation.

2. A stated spread. The range spread is how wide your band is, expressed as a percentage of the midpoint or minimum. A spread of 30%–50% around the midpoint is common for professional individual-contributor roles; wider spreads are used for senior or highly variable roles. The spread should be documented and consistently applied — not set job-by-job to fit a preferred candidate.

3. An audit trail. Your documentation should answer, in writing: what data source did we use, what release year, what geography, what percentile did we anchor to, and what spread did we apply? If the D.C. Office of Human Rights or your outside counsel ever asks for your methodology, you want a written answer that does not start with "we looked at a few job postings on Indeed."

For a step-by-step walkthrough of the methodology, our how to build a salary range guide covers the full process — from pulling BLS OEWS data to calculating a compliant min/max — and our what to include in a salary range posting guide covers the specific disclosure language that belongs in a posting.

---

The Benefits Description Requirement: Often Overlooked

Many employers focus on the pay range and treat the benefits-description requirement as an afterthought. That is a mistake. The D.C. law explicitly requires a "general description" of all benefits and other compensation the employer reasonably expects to offer — not a brochure, but enough specificity that a candidate understands the total compensation picture.

In practice, a compliant benefits line might read: "Benefits include medical, dental, and vision insurance; 401(k) with employer match; 15 days PTO; and 10 paid holidays." A non-compliant version simply omits any benefits language, or includes a placeholder like "competitive benefits."

Because the benefits element is a distinct requirement — not just a salary-range rule — an employer who posts a correct pay range but omits the benefits description may still be in violation. Review your posting template against both elements before every new posting.

---

Verify and Document Before You Post

Pay-transparency law text is not self-executing. Agency guidance, enforcement interpretations, and rulemaking can change the practical scope of what is required — sometimes without a corresponding change to the statute itself. Before you act on anything in this guide:

• Confirm the current requirements with the DC Office of Human Rights (OHR) or DC Department of Employment Services (DOES). The statute in the library reflects Cooley LLP's analysis as of 2024; verify that no amendments or additional rulemaking have taken effect since.
• Pull current D.C. wage data from bls.gov/oes for the specific occupation and reference year — do not rely on figures from a prior release cycle without checking whether a newer one has been published.
• Document your methodology in writing at the time of posting, not after the fact. The goal is a paper trail that can be handed to counsel without explanation.

If you are managing D.C. compliance alongside obligations in Colorado, California, New York, Illinois, Washington State, New Jersey, or Massachusetts, the documentation burden compounds quickly. The pay transparency resource hub is a central starting point for jurisdiction-by-jurisdiction reference.

---

Build Your D.C. Posting Template — and the Audit Trail Behind It

The District of Columbia's washington dc pay transparency law is one of the broadest in the country by employer coverage: no headcount floor, a meaningful fine structure, and an explicit benefits-disclosure requirement that most posting templates were not built to handle.

Getting compliant means three things: a documented pay range (minimum, maximum, methodology), a benefits description in every posting, and a paper trail you can hand to counsel. The hardest part is rarely the law itself — it is building the internal process that applies consistently across every role, every platform, and every hiring manager.

Our Pay Transparency Compliance Kit includes a D.C.-ready job posting template, a range-methodology worksheet, and a compliance checklist covering the key elements the Wage Transparency Omnibus Amendment Act requires. Download it as a starting point, adapt it to your roles, and keep the completed worksheets on file.

For employers who need to build ranges at scale — or who want a BLS OEWS–anchored audit trail that does not live in a spreadsheet — review our pricing page to see which Salary Range Builder plan fits your team size and compliance footprint.

The posting due tomorrow does not have to be the compliance gap that shows up in a fine notice six months from now. Build the range, write down the methodology, and post it.