Segregate or Surrender: How Agencies Misuse the Logical Segregability Doctrine to Deny More Than the Law Allows
Among the procedural obligations embedded in the Freedom of Information Act, few are as routinely ignored—or as consequentially misapplied—as the logical segregability requirement. Codified at 5 U.S.C. § 552(b), the standard is deceptively simple: even when a document contains exempt information, the agency must release any portion that can be reasonably separated from the protected content without disclosing what the exemption is designed to shield. In practice, however, the doctrine is frequently treated as an afterthought, a formality to acknowledge in a denial letter rather than a genuine analytical obligation to discharge.
The result is a pattern that federal courts have documented with increasing frustration—agencies asserting blanket exemptions over entire documents, providing boilerplate segregability language that offers no actual analysis, and then watching those denials unravel under judicial scrutiny. For compliance officers responsible for FOIA response programs, understanding where the doctrine breaks down is not merely an academic exercise. It is a prerequisite for building exemption claims that will survive challenge.
What the Law Actually Requires
The segregability obligation is not discretionary. The statute directs that "any reasonably segregable portion of a record shall be provided to any person requesting such record after deletion of the portions which are exempt." Courts have interpreted this to mean that agencies bear an affirmative burden—not simply to assert segregability has been considered, but to demonstrate, with specificity, that a document-by-document review was actually conducted.
The D.C. Circuit, which handles a disproportionate share of FOIA litigation given the concentration of federal agencies in Washington, has been particularly pointed on this issue. In Mead Data Central, Inc. v. U.S. Department of the Air Force, the court articulated what has become the foundational standard: agencies must provide a detailed justification for non-disclosure, not merely conclusory statements. A declaration that states, in effect, "we reviewed the documents and determined no segregable portions exist" does not satisfy this requirement. The court expects to see the reasoning, not merely the conclusion.
The Exemptions Most Frequently Implicated
Segregability failures tend to cluster around specific exemptions, and understanding that pattern helps compliance officers focus their internal audits.
Exemption 5, which covers inter-agency and intra-agency memoranda protected by deliberative process, attorney-client, or attorney work-product privilege, is perhaps the most common site of segregability abuse. Agencies frequently treat an entire document as deliberative simply because it contains some deliberative content—ignoring the settled principle that purely factual material within a deliberative document must be released unless its disclosure would itself reveal the deliberative process. In EPA v. Mink, the Supreme Court recognized this distinction, and subsequent circuit decisions have reinforced it repeatedly.
Exemption 7(C), covering law enforcement records that could constitute an unwarranted invasion of personal privacy, presents similar challenges. Agencies sometimes withhold entire investigative files when the privacy interest attaches only to identifying information—names, addresses, and other personal identifiers—that could be redacted without compromising the remainder of the record.
Exemption 1, governing classified national security information, has historically been granted substantial judicial deference. Yet even here, courts have rejected wholesale withholding when agencies fail to demonstrate that non-classified portions cannot be meaningfully separated. The Vaughn index requirement—named for Vaughn v. Rosen—exists precisely to force agencies to articulate, document by document and exemption by exemption, why segregation is not feasible.
How Courts Have Responded
Federal district and circuit courts have grown noticeably less tolerant of perfunctory segregability analysis. In Wilderness Society v. U.S. Department of the Interior, the court found the agency's segregability declarations inadequate because they failed to address individual documents with the specificity required. The agency had submitted a declaration covering hundreds of pages with a single paragraph of analysis—an approach the court characterized as insufficient to meet the statutory burden.
Similarly, in Juarez v. Department of Justice, the court ordered in camera review after the agency's Vaughn index provided only categorical descriptions rather than document-specific segregability findings. The practical consequence was not merely a remand—it was a resource-intensive judicial review that the agency could have avoided with more rigorous internal analysis at the outset.
Fee-shifting under 5 U.S.C. § 552(a)(4)(E) adds another layer of institutional risk. When requesters substantially prevail in FOIA litigation—and losing on segregability grounds frequently qualifies—courts may award attorney fees and litigation costs against the agency. The financial exposure is real, and it compounds the reputational cost of a public judicial finding that an agency withheld more than it was legally entitled to.
The Anatomy of a Defensible Segregability Review
For compliance officers seeking to audit their organization's current practices, the following framework provides a structured starting point.
Document-level granularity is non-negotiable. A segregability determination must be made for each document, not each request or each exemption category. Declarations or response letters that address segregability in aggregate are presumptively inadequate under current case law.
Factual and deliberative content must be separated analytically. For Exemption 5 claims in particular, reviewers must identify whether a document contains purely factual material—even if that material appears alongside protected deliberative content. The question is not whether the document as a whole is deliberative, but whether any portion of it can be released without revealing the deliberative process itself.
The Vaughn index must reflect actual analysis. If your organization produces Vaughn indices as part of litigation or administrative appeal responses, each entry should describe the nature of the withheld material, the specific exemption claimed, and a particularized explanation of why segregation is not feasible. Generic language recycled across entries will not withstand scrutiny.
Train reviewers on the distinction between difficult and impossible. The standard is "reasonable" segregability, not perfect segregability. The fact that separating exempt from non-exempt content requires effort does not excuse the failure to make that effort. Reviewers who default to full withholding because partial release is administratively inconvenient are creating legal liability, not managing it.
Document the review process, not just the outcome. In the event of litigation, the agency will need to demonstrate that a meaningful segregability analysis occurred. Internal records reflecting who reviewed each document, what determination was made, and why should be maintained as a standard component of the response workflow.
A Compliance Gap Worth Closing
The logical segregability doctrine occupies an unusual position in the FOIA compliance landscape: it is simultaneously well-established in the law and poorly implemented in practice. Agencies that treat it as a checkbox rather than a substantive obligation are not merely cutting corners—they are systematically withholding information the statute entitles requesters to receive, and they are doing so in a manner that courts have repeatedly found indefensible.
For compliance officers committed to building FOIA programs that are both legally sound and institutionally credible, the segregability requirement deserves the same rigorous attention as the exemption claims themselves. A document that could have been partially released—but was withheld in full—represents a compliance failure regardless of whether the underlying exemption was valid. Addressing that gap is not a concession to requesters. It is an obligation under the law.