Shifting Pay Scales: Unpacking Mayor Bowser’s Pay Transparency Act in Washington, D.C.

In an effort to promote pay transparency and tackle existing wage disparities, the District of Columbia has enacted D.C. Act 25-367. This legislation, which applies to employers with at least one employee in the District, aims to ensure that job seekers have access to important information about pay rates and healthcare benefits when considering employment opportunities. This article will delve into the disclosure requirements for employers, the consequences of non-compliance, the enforcement measures established, the workplace notice requirement, and the necessary steps for D.C. employers to prepare for a smooth transition to pay transparency compliance.

Disclosure Requirements for Employers

Under D.C. Act 25-367, employers will be required to provide detailed information regarding pay rates and healthcare benefits for all open positions. This represents a significant shift towards increased transparency in the hiring process.

Requirement to Disclose Pay Rates for all Open Positions

To promote a fair and transparent job market, employers must now disclose the minimum and maximum projected salary or hourly pay in all job listings and position descriptions advertised. By providing this information, employers enable candidates to assess whether the offered compensation aligns with their expectations and worth.

Requirement to Disclose Healthcare Benefits

In addition to pay rates, employers will also be obligated to disclose the existence of healthcare benefits that employees may receive. This information is crucial for potential job seekers as it allows them to evaluate the overall compensation package offered by the employer.

Consequences of Non-compliance

D.C. Act 25-367 establishes consequences for employers who fail to meet the disclosure requirements outlined in the legislation. Candidates are permitted to inquire about undisclosed pay rates or healthcare benefits, and employers must respond truthfully. Screening applicants based on their wage history is strictly prohibited.

Enforcement Measures

To ensure compliance, the legislation grants the District of Columbia’s Attorney General (AG) the authority to investigate alleged violations. In cases where violations are identified, the AG may initiate civil actions against the employer, seeking restitution or other forms of relief to rectify the situation. These enforcement measures demonstrate the seriousness with which the District of Columbia is approaching pay transparency.

Workplace Notice Requirements

In addition to the disclosure requirements, employers covered by D.C. Act 25-367 must post a notice in the workplace outlining workers’ rights under the act. This notice serves as a reminder to employees and reinforces the commitment to pay transparency.

Preparing for Pay Transparency Compliance

While D.C. Act 25-367 is under review, it is essential for D.C. employers to use this time to prepare for the pending changes. By undertaking proactive measures, employers can ensure a smooth transition to pay transparency compliance. This may involve conducting internal audits to gather accurate and up-to-date information on pay rates and healthcare benefits. Additionally, employers should review their job listing and advertising processes to ensure the inclusion of the required pay rate details. Training HR personnel on the new mandated practices and policies is also crucial during this preparation phase.

D.C. Act 25-367 marks a significant step towards pay transparency and equal opportunity in the District of Columbia. By requiring employers to disclose pay rates and healthcare benefits, candidates have access to crucial information necessary for making informed decisions. It is crucial for employers to understand and comply with the new disclosure requirements, as violations can result in legal consequences. By taking proactive steps to prepare for compliance, D.C. employers can navigate this transition successfully and contribute to a more equitable and transparent job market environment.

Explore more

AI Drives the Shift to Specialized Data Center Design

The rigid architectural paradigms that once defined data center engineering are currently being dismantled by the insatiable computational demands of modern artificial intelligence. For several decades, the industry adhered to a singular gold standard of universal redundancy, where every piece of hardware was supported by massive backup systems regardless of its actual function. This era of over-engineering is rapidly coming

Global Industrial Motherboard Market to Grow Through 2035

The digital nervous system of the modern smart factory is no longer found in centralized data centers but resides within the ruggedized circuitry of industrial motherboards that power everything from robotic arms to precision medical scanners. This fundamental shift marks a transition for these specialized circuit boards, elevating them from niche hardware components to essential pillars of the global industrial

How Did Microsoft Migrate 70TB to SAP S/4HANA Private Cloud?

Managing the financial heartbeat of a global tech giant involves processing millions of complex transactions across diverse product lines ranging from gaming to cloud services. When Microsoft decided to modernize its core financial infrastructure, it faced the monumental task of migrating a 70-terabyte SAP ERP Central Component system to the SAP S/4HANA Private Cloud. This specific environment, known as SAP

Is Your VPN Gateway an Open Door for Qilin Ransomware?

The sudden realization that a primary security perimeter has been compromised often sends shockwaves through an entire organization, especially when that perimeter is a trusted VPN gateway. When Palo Alto Networks disclosed the CVE-2026-0257 vulnerability in its GlobalProtect firewalls, the severity was immediately clear through its critical CVSS score of 9.1. This specific flaw allows unauthorized actors to bypass authentication

How Data Contracts Stop Data Pipelines From Breaking

A silent failure in a data warehouse often begins with a seemingly harmless change made by an upstream software engineering team that has no visibility into how their data is consumed. When an application developer decides to rename a field from “user_id” to “customer_uuid” or changes a data type to optimize performance, the ripple effect can be catastrophic for the