Federal employee NDAs aren’t new, but expanding them requires careful guardrails

The recent proposal from the Office of Personnel Management to expand nondisclosure agreement (NDA) requirements across the federal workforce has generated predictable controversy. Critics see it as an attempt to suppress dissent. Supporters view it as a long-overdue effort to curb damaging leaks. 

But amid the political debate, one important fact is being overlooked: for hundreds of thousands of federal employees, NDAs are already a standard condition of service.

Anyone granted access to classified information signs the Standard Form 312 (SF-312), a legally binding nondisclosure agreement acknowledging their responsibility to protect national security information. Clearance holders understand that safeguarding sensitive information is part of the job. The expectation is clear, the boundaries are defined, and the consequences for violations are understood.

What makes the current proposal different is not the existence of an NDA. It is the expansion of the concept beyond classified information and into a much broader category of what the administration calls “confidential government information.”

That distinction matters, and it mirrors the already expanding government ecosystem of Controlled Unclassified Information (CUI), and the ongoing confusion about how to protect it.

Government agencies routinely handle information that is not classified but still sensitive. Procurement strategies, internal personnel matters, pre-decisional policy discussions, cybersecurity vulnerabilities, law enforcement operations, and draft regulations can all be compromised by unauthorized disclosures. Few federal executives would argue that every internal deliberation should immediately become public.

NDAs also certainly aren’t only the purview of the federal government. Many private-sector organizations require employees to sign confidentiality agreements covering proprietary business information. OPM Director Scott Kupor has pointed to this reality in defending the proposal, arguing that the federal government should not hold itself to a lower standard than private employers when it comes to protecting sensitive information.

From a management perspective, that argument has merit.

Federal agencies cannot effectively develop policy, negotiate contracts, conduct investigations, or plan operations if internal deliberations are routinely leaked before decisions are finalized. Public trust can be damaged not only by secrecy but also by incomplete information released without context.

Yet government is not the private sector. The federal workforce serves the public interest, not shareholders. That distinction requires a different balance between confidentiality and accountability.

The challenge is not whether federal employees should protect sensitive information. They already do. The challenge is defining exactly what information falls within the scope of protection. Confusion about that scope is where an NDA can extend beyond just protecting sensitive information and can become a weapon to unfairly penalize a federal employee, or incorrectly hide information that has no reason to be deemed protected.

Current draft language references “confidential government information,” including pre-decisional and deliberative materials that are not publicly available. Critics argue the definition is too broad and could create uncertainty for employees trying to distinguish between legitimate whistleblowing and prohibited disclosure.

Federal leaders should take those concerns seriously.

The federal government already operates under a complex framework of classification rules, privacy protections, procurement integrity requirements, and whistleblower laws. Any government-wide NDA policy should reinforce and not undermine that framework. Employees must have confidence that legally protected disclosures to inspectors general, Congress, and authorized oversight bodies remain fully protected. The proposal itself states that those rights would be preserved, but implementation details will ultimately determine whether employees trust that assurance.

The experience of the cleared workforce offers a useful lesson. Security clearance holders generally accept strict disclosure restrictions because the rules are accompanied by training, clearly defined categories of protected information, and established adjudication processes. The system is far from perfect, but employees understand where the lines are drawn.

If the administration moves forward with a broader NDA framework, it should adopt the same principles: clarity, consistency, transparency, and robust protection for lawful disclosures.

A poorly defined NDA regime could create confusion, chill legitimate reporting of misconduct, and generate unnecessary legal challenges. A carefully structured one could reinforce existing obligations and help agencies better protect sensitive information without compromising accountability.

The debate should not be framed as a choice between secrecy and transparency. Federal agencies require both. Effective government depends on candid internal deliberation, but it also depends on public trust and lawful oversight.

For federal executives, the real question is not whether nondisclosure agreements belong in government. They already do. The question is whether a government-wide expansion can be implemented in a way that protects sensitive information while preserving the accountability mechanisms that distinguish public service from private employment. That is where the conversation should be focused.