Can a Workplace Confidentiality Rule Bar Pay and Working-Condition Discussions?

A confidentiality rule can reach too far into protected workplace discussion
A policy that employees could reasonably read as banning discussion of wages, benefits, or collective workplace concerns may violate federal labor law. Calling the information confidential does not resolve the issue. The important questions are what the rule covers, how an employee would understand it, and whether its restrictions can be drawn more narrowly.
In Hoffmann Brothers, an NLRB administrative law judge found three confidentiality provisions unlawful on January 5, 2026. The Board later adopted that decision on February 23 after no exceptions were filed. The companion case analysis explains the procedural history and adopted remedy.
Read the definition before relying on the heading
In the official ALJ decision, pages 2–5, the original agreement defined confidential information broadly enough to include communications learned through employment and expressly listed compensation, benefits, and employee lists. The handbook reached employee contact details and information learned on duty. The problem was not simply that the employer protected trade secrets. The restrictions also reached information employees might use to discuss their working conditions or organize.
A practical review should mark each category of protected information. Does financial information clearly mean proprietary business records, or could an employee read it to include the employee’s own pay? Does employee information refer to a confidential personnel file, or also a coworker’s phone number voluntarily shared during ordinary work? Those differences affect what conduct the policy may discourage.
Ask four questions about the restriction
- What information is covered? Look for specific categories and catchalls, including anything learned at work, business-related communications, compensation, or employee lists.
- Who can receive it? A restriction on disclosure to anyone outside the company can reach a union or agency as well as a business competitor.
- Is permission required? An obligation to obtain management approval may itself discourage activity the law protects.
- What does the exception actually preserve? Compare the exception with each prohibition. A vague reference to rights under the law may leave the employee guessing.
The ALJ applied the rule from the perspective of an economically dependent employee considering protected activity. The employer’s benign intention did not answer how the text could reasonably be read. The employer’s business interests still mattered, but it had to explain why a narrower rule could not protect them. ALJ decision, pages 7–10.
An exception for coworker conversations may leave other gaps
The revised Hoffmann agreement allowed discussion of terms and conditions with coworkers and use of information in agency complaints. Yet it retained explicit references to compensation and employee lists, broad definitions, and restrictions on using information to the employer’s detriment. The ALJ found that employees were still left uncertain about protected communications with a union or other outside recipients.
For an employer, the lesson is to reconcile the whole policy, including older agreements that still bind former employees. For an employee, preserve the actual version received and any acknowledgment or disciplinary notice. A later policy revision may not establish which text governed an earlier event.
Distinguish workplace knowledge from protected records
The decision expressly distinguishes knowledge acquired in ordinary work from an employer’s private or confidential records. Discussing your pay or using contact information lawfully learned at work raises different issues from entering a restricted system or taking customer, personnel, or medical records. Do not assume a rule’s overbreadth authorizes access to records you were not entitled to obtain.
Section 7 concerns protected concerted activity for mutual aid or protection and includes core wage-discussion rights. Coverage and the conduct involved still matter. A handbook dispute cannot be decided solely by identifying one familiar phrase or assuming that every individual grievance or disclosure is protected.
What a useful review should produce
A useful employment-law review should identify the exact provision, the activity at issue, the source of the information, and the employer’s stated concern. It should also check the official case status and law applicable at the relevant time. The Hoffmann docket now records adoption, but that event should not be retold as having occurred in January or as a separate reasoned Board ruling on contested exceptions.
Bring the signed agreement, handbook, later revisions, and communications invoking the rule. Those documents allow counsel to distinguish an overbroad restriction from a properly focused protection of confidential business information and to assess the particular action taken.
Review the confidentiality language
Bring the handbook, agreement, discipline notice and the communications at issue. Call (949) 343-9735 or email office@mishrax.com.