Washington Post: A Continuing Salary-Data Settlement Defeated the Union’s Request

The NLRB proceeding against The Washington Post did not turn on a finding that employees’ named salary data was irrelevant. The administrative law judge found it presumptively relevant, but concluded that a continuing settlement arrangement, the parties’ bargaining history and their past practices justified refusing the union’s 2022 requests. Crucially, the judge did not treat the settlement itself as evidence of an express waiver: Its nonadmission clause prevented that use. Understanding those separate steps is essential to understanding the dismissal.

The request and the long-running information arrangement

The union sought salary data linked to employees’ names to evaluate pay equity and bargaining proposals. The employer admitted refusing that form of production. It relied on a 1989 settlement providing detailed non-name-linked salary information, a separate name-and-address list and a neutral verification mechanism. The agreement remained effective until modified or terminated by mutual written agreement. A 2005 side letter allowed more frequent electronic production while expressly preserving the settlement’s terms. WP Company, JD-04-26, at 3–5.

The record included subsequent bargaining proposals for named data, the employer’s refusals, repeated production under the non-name-linked arrangement, and later collective-bargaining agreements. The union renewed its request in 2022, explaining why named information would assist pay-equity and healthcare analysis. The dispute concerned the employer’s duty to provide information to the bargaining representative—not an employee’s right to discuss personal pay with coworkers.

Relevance was the starting point, not the employer’s answer

Information about bargaining-unit compensation is presumptively relevant under the framework the judge applied. The employer’s argument that the union could negotiate or conduct studies without names did not itself defeat that presumption. The judge instead asked whether the existing arrangement and other evidence supplied a legitimate reason not to produce the requested form. WP Company, at 10–12.

That matters because the decision is not permission to reject a salary request merely by calling it unnecessary or private. The employer’s defense depended on the particular agreements and course of dealing proved in this record. A different bargaining unit, request, contract or set of negotiations would need its own analysis.

The settlement could remain enforceable without proving express waiver

The settlement’s nonadmission clause barred treating the agreement as evidence or an admission of waiver of statutory rights. The judge honored that provision and declined to use the agreement as proof of an express waiver. A summary saying only that the union signed away its rights in 1989 would omit a finding favorable to the union. WP Company, at 12–13.

The judge separately concluded that the agreement remained effective. Its duration depended on a specified event—mutual written modification or termination—not on expiration of the later collective-bargaining agreements. The side letters referred to and reaffirmed the independent settlement; they did not incorporate it into each CBA or automatically make it expire with one. WP Company, at 14–15.

Bargaining history and practice supplied the remaining reasoning

Applying a clear-and-unmistakable-waiver framework, the judge examined whether the specific information issue had been fully discussed and consciously yielded. The opinion identified the 2005, 2014 and 2022 negotiations, including requests for named data that did not become part of the resulting agreements. It also examined repeated information requests and responses following the non-name-linked arrangement. WP Company, at 15–16.

The judge considered those circumstances together, rather than treating silence on one isolated request as enough. The conclusion rested on the continuing production terms, bargaining history and corroborating practices, despite the exclusion of settlement-based express-waiver evidence. The complaint was therefore recommended for dismissal in its entirety. WP Company, at 16–17.

The January ruling and the later Board order are not the same event

The ALJ issued the decision January 6, 2026, and an errata January 8 corrected specified text. As of this analysis’s assigned January 13 editorial date, the decision was an ALJ recommendation, not an already adopted Board order.

For the current update, the March 5, 2026 Board order supplies the later disposition: No exceptions had been filed, so the Board adopted the findings and conclusions and made the recommended dismissal its order. That procedural adoption should not be represented as a newly reasoned Board opinion independently revisiting every issue. The official docket records both stages.

What to examine in another information dispute

Read the complete settlement, including nonadmission, duration and modification clauses; every relevant side letter; the actual information requests and responses; and the specific bargaining proposals. Those documents answer different questions. Our salary-data settlement guide explains their practical use. This case does not authorize a blanket payroll-data refusal, establish that all past practice proves waiver, or decide whether the employer’s pay practices were discriminatory.