Federal labor law protects the right of most private-sector employees to discuss wages and working conditions with each other, because that discussion is a step toward acting collectively. A handbook rule forbidding it is generally unlawful whether or not anyone is ever disciplined under it. The protection has real gaps — supervisors, independent contractors, agricultural and domestic workers sit outside it — and one long-standing protection for federal contractor employees was removed in 2025 when the executive order behind it was revoked.
The clause that should not be there
Somewhere in a great many employee handbooks is a line saying that compensation is confidential and should not be discussed with colleagues. It usually appears alongside genuinely sensible confidentiality provisions about client data and trade secrets, which is part of why it goes unchallenged. For most private-sector employees, that particular clause is unlawful, and it has been for a very long time.
The reasoning is not about privacy at all. Federal labor law protects employees acting together to improve their working conditions, and talking to each other about what you are paid is the first step of almost any such action. If you cannot compare, you cannot organize, and if you cannot organize the protection means nothing. So the right to have the conversation gets protected as a precondition for the right to act.
What surprises people is that the rule bites even where nobody has been disciplined. Simply maintaining a policy that a reasonable employee would read as prohibiting protected discussion can itself be a violation, because the effect of the policy is to stop the conversation happening at all. The chilling effect on the conversation is itself the harm the rule addresses.
What the protection actually covers
It covers discussing your own wages, asking colleagues about theirs, and comparing notes about hours, benefits and conditions. It covers doing so in person, in a group chat, or in a public post, and it covers doing so with people outside your own department. Importantly it is not limited to unionized workplaces — it applies to most private-sector employees whether or not a union exists anywhere near them.
It also covers raising the results of that comparison with the employer. Two colleagues who discover a discrepancy and go together to a manager about it are engaged in exactly the activity the law was written to protect. The joint character is what makes it concerted rather than individual, which matters more than people expect — one person raising their own pay alone is on weaker ground than two people raising the same issue together.
Who is not covered, and it is more people than you would think
Supervisors are excluded, and the definition is functional rather than a matter of job titles. It turns on whether you exercise independent judgment in hiring, firing, disciplining or responsibly directing others, so a title with “lead” in it may or may not put you outside the protection. Anyone genuinely supervising a team probably is outside it. That is worth establishing before starting a conversation that feels obviously reasonable, because the protection is what makes it safe rather than what makes it right.
Independent contractors are excluded because the protection runs to employees. Agricultural workers and domestic workers are excluded by the statute’s own definitions, which is a historical exclusion with an ugly history and no current justification. Public-sector employees are covered by a patchwork of state laws rather than by the federal provision, so the answer for a state or municipal worker depends entirely on where they work.
A protection that was removed, and almost nobody noticed
Employees of federal contractors had a separate protection from retaliation for discussing pay, which came from the executive order governing contractor non-discrimination obligations rather than from the labor statute. That executive order was revoked in January 2025. The enforcement agency was directed to cease and desist, contractors wound down their obligations that spring, and the regulations were proposed for rescission later in the year. It happened quickly and drew far less attention than the size of the change warranted.
The consequence is narrow but real: a layer of protection that specifically covered contractor employees, and that was easier to enforce than the general provision, no longer exists. The underlying federal labor protection still applies to those employees, since it comes from a statute rather than an executive order. But if you work for a federal contractor and were relying on the contractor-specific rule, it is worth knowing that it went. Guidance published before 2025 will not mention this.
What the protection does not do
It does not require your employer to tell you what anybody else earns. It does not require colleagues to tell you either, because this is a right to have a conversation rather than a right to an answer. A colleague who would rather not discuss it is entitled to decline, and asking twice after a decline is its own kind of problem. The protection removes the employer from the equation; it does not oblige anybody to participate.
It does not protect you if you obtained the information improperly. Accessing a payroll system you have no business in, or copying confidential records as part of your job duties and circulating them, is a different act with different consequences, and the protection for discussion does not extend to it. The distinction is between what you learned in conversation and what you took from a system.
And it does not require the employer to fix a gap you find. Discovering a discrepancy is the beginning of a conversation about pay rather than the conclusion of one. Whether a difference is lawful depends on the reasons behind it rather than on its existence, and there are plenty of lawful reasons two people in the same role are paid differently. Knowing the gap exists is still worth a great deal, because you cannot ask about something you cannot see.
The practical version
If you want to know how your pay compares, the useful approach is to ask specific people specific questions rather than to survey the department. “Would you be comfortable telling me what band you’re in?” is a far easier question to answer than a request for an exact number. Band information is usually enough for the comparison you actually want to make, and it lets somebody help you without disclosing anything they feel is private. Offering your own figure first tends to make the exchange easier still.
Published data is the other half. The percentile range for your occupation in your metropolitan area tells you where the market sits, and a colleague’s number tells you where your employer sits within it. Those two pieces of evidence together are far stronger than either one, and the first requires nobody’s cooperation at all.
If you are disciplined for it
Retaliation for protected concerted activity is itself unlawful, and the remedy runs through the National Labor Relations Board rather than through a court. Charges must generally be filed within six months of the conduct complained of. That is a genuinely short window, and it is the single most common reason a valid complaint goes nowhere — people spend the first four months hoping the situation resolves itself. If something has happened, find out about the deadline early even if you have not decided what to do.
Write down what happened, when, and who said it, on the day it happens. If the discipline was documented, keep a copy outside company systems. And if the handbook contains the clause described at the top of this article, keep a copy of that too, because the policy itself is part of the picture.
This is general information about how these protections are structured rather than legal advice about your situation. Coverage questions in particular — whether you count as a supervisor, whether you are an employee or a contractor — turn on facts specific to you, and an employment lawyer or the relevant agency can answer them properly.
Common questions
Can my employer stop me discussing my pay?
For most private-sector employees, no. Federal labor law protects discussing wages and conditions with colleagues, and maintaining a policy that appears to forbid it can itself be a violation even if nobody is disciplined.
Does this only apply in unionized workplaces?
No. It applies to most private-sector employees whether or not a union exists anywhere near them, because the protection is for acting together rather than for union membership.
Who is not covered?
Supervisors, independent contractors, and agricultural and domestic workers. Public-sector employees are covered by a patchwork of state laws rather than the federal provision.
How is a supervisor defined?
Functionally rather than by title — whether you exercise independent judgment in hiring, firing, disciplining or responsibly directing others. Anyone genuinely supervising a team is likely outside the protection.
Did anything change recently?
Yes. Federal contractor employees had a separate protection from retaliation for discussing pay under an executive order that was revoked in January 2025. The underlying statutory protection still applies; the contractor-specific layer does not.
Does this mean my employer must tell me what others earn?
No. It is a right to have a conversation, not a right to an answer, and colleagues may decline. It also does not oblige an employer to fix any gap you find.
What if I got the information from a system?
Different situation. Accessing payroll you have no business in, or circulating confidential records you handle as part of your job, is not protected discussion.
What if I am disciplined for discussing pay?
Retaliation for protected activity is unlawful, with the remedy through the National Labor Relations Board. Charges must be filed within six months, which is the most common reason a valid complaint fails.