FOIA Sanctions Must Not Force Overbroad Disclosure That Harms Innocent Third Parties; FOIA Release Injunctions Must Satisfy Rule 65(d)
1) Introduction
This appeal arises from a protracted Freedom of Information Act (FOIA) dispute between Jacqueline Stevens, a Northwestern University professor,
and U.S. Immigration and Customs Enforcement (ICE). Stevens sought records relating to three named immigration detainees. FOIA requires agencies
to respond within 20 business days, 5 U.S.C. §552(a)(6), but after about a year with “without much progress,” Stevens sued in the Northern District of Illinois.
The district court became increasingly dissatisfied with ICE’s pace, search methodology, and explanations, ordering monthly production targets and later
additional searches for categories such as detainee grievances, commissary accounts, and work programs. ICE also asserted FOIA exemptions and provided
a Vaughn index for redactions across more than 2,000 pages. After finding the Vaughn submissions deeply deficient and inferring bad faith, the district court
ordered ICE to release the entire set of pages unredacted. ICE appealed.
The Seventh Circuit addressed two core issues: (1) whether the district court’s release order, framed as an injunction, was sufficiently specific to be enforceable;
and (2) whether “release everything” is a permissible litigation sanction in a FOIA case—especially where unredacted release risks exposing sensitive information
of innocent third parties and other law-enforcement entities.
2) Summary of the Opinion
The Seventh Circuit vacated the injunction and remanded. It held that the injunction failed to comply with
Fed. R. Civ. P. 65(d)(1)(C) because it did not “describe in reasonable detail” what ICE must release; it vaguely ordered production of
“all records identified as responsive” without specifying which list or set of documents controlled.
On the sanction itself, the court assumed (without finally deciding) that ICE’s performance may have warranted sanctions, but concluded the district court abused its discretion
by selecting an overbroad remedy—unredacted disclosure—without explaining why that sanction was appropriate despite foreseeable harms to innocent third parties (e.g., Social Security numbers)
and the potential exposure of law-enforcement database access codes and confidential investigative details. The Seventh Circuit instructed the district court to reassess sanctions and
to limit disclosures to information concerning ICE’s own operations and to privileges ICE can waive.
3) Analysis
A. Precedents Cited
-
Vaughn v. Rosen, 484 F.2d 820 (D.C. Cir. 1973)
The opinion references Vaughn to explain the function of a “Vaughn index”—a structured log that justifies each withholding or redaction by linking it to a specific FOIA exemption
and a reasoned explanation. The district court’s frustration stemmed from ICE’s index entries that were “effectively unreasoned” or internally inconsistent.
The Seventh Circuit did not reject the Vaughn mechanism; rather, it treated the Vaughn failures as part of the broader litigation mismanagement potentially justifying sanctions.
-
MillerCoors LLC v. Anheuser-Busch Cos., 940 F.3d 922 (7th Cir. 2019)
Cited for the proposition that injunction commands must appear in a separate, operative document; “narration in an opinion does not suffice.”
This case supplies the procedural baseline the district court initially missed when it issued a release directive without an injunction compliant with Rule 65.
-
Schmidt v. Lessard, 414 U.S. 473 (1974)
Cited to support vacatur where injunctive language is too vague to be enforceable. The Seventh Circuit relied on Schmidt to underscore that injunctions must be precise enough
to provide notice and permit contempt enforcement without guesswork.
-
Auto Driveaway Franchise Systems, LLC v. Auto Driveaway Richmond, LLC, 928 F.3d 670 (7th Cir. 2019)
Cited to distinguish enforceability defects from jurisdictional defects: vague language can warrant vacatur but does not eliminate appellate jurisdiction.
The court used this to proceed with review even though the injunction was flawed.
-
Gunn v. University Committee to End the War in Viet Nam, 399 U.S. 383 (1970)
Used as a contrast: a complete absence of an injunction can create a jurisdictional problem. Here, although the initial appeal preceded entry of an injunction,
the district court later entered one, allowing consolidated appellate review.
-
United States v. Boyle, 469 U.S. 241 (1985)
Invoked to illustrate a general sanctions principle: the legal system often imputes an agent’s misfeasance to the principal (client), but over time the loss can be shifted back to the responsible agent
(e.g., through malpractice). The Seventh Circuit used Boyle to frame why sanctions should, where possible, concentrate injury on responsible actors.
That logic breaks down, the court explained, when the sanction’s primary harm falls on nonparties (e.g., individuals whose Social Security numbers would be disclosed).
-
Chrysler Corp. v. Brown, 441 U.S. 281 (1979)
Cited for the proposition that private persons may lack a legal right to prevent an agency from deliberately disclosing confidential information.
The Seventh Circuit used Chrysler to emphasize the practical stakes: even if third parties cannot readily block disclosure, they have strong interests in avoiding harm from negligent disclosure,
and courts should not impose sanctions that unnecessarily externalize costs onto those third parties.
B. Legal Reasoning
Two tracks drive the decision: (1) injunction specificity under Rule 65; and (2) proportional, explained sanctioning that does not gratuitously harm nonparties or nullify statutory protections.
1) Appellate jurisdiction and the nature of FOIA release orders.
Because the district court’s order was not a final judgment under 28 U.S.C. §1291, ICE invoked 28 U.S.C. §1292(a) on the theory that FOIA release orders are injunctive.
The panel pressed a practical question: where is the injunction that can be enforced? Rule 65 requires injunctions to specify, in reasonable detail, the required acts.
The district court’s initial failure to enter a Rule 65-compliant injunction triggered the court’s discussion of MillerCoors and Gunn. Once an injunction was entered, its vagueness became the central Rule 65 defect.
2) Rule 65(d)(1)(C): the injunction must be precise enough for contempt enforcement.
The district court ordered ICE to produce “all records identified as responsive ... in full without redactions,” but did not specify whose identification controlled or which dated list governed.
Given multiple evolving lists from ICE and alternative lists proposed by Stevens, the order did not provide “reasonable detail.”
The Seventh Circuit emphasized that contempt power requires clarity: a party must be able to tell exactly what compliance requires. Under Schmidt v. Lessard, vagueness warrants vacatur.
3) Bad faith versus incompetence—and why the distinction mattered to remedy selection.
The district court inferred bad faith from ICE’s flawed Vaughn index (including an attempt to redact an attorney’s name and address under §552(b)(6) even though briefs and dockets are public).
The Seventh Circuit did not endorse that inference on this record, noting that “errors—even howlers—are inevitable” when clerical staff process thousands of documents.
Still, the panel assumed arguendo that ICE’s “performance had hit nadir” and that sanctions could be justified, shifting the focus to whether the chosen sanction was permissible and explained.
4) Sanctions must be reasoned and proportionate, with attention to who bears the harm.
The court accepted that sanctions can bypass merits (analogizing to discovery sanctions under Rule 37), but stressed that courts “should take care that any injury ultimately falls on the party responsible.”
That is where “release everything” failed: the record (as summarized by ICE without contradiction) suggested unredacted production would expose Social Security numbers and sensitive law-enforcement database access codes,
potentially revealing informants, unsubstantiated allegations, and other confidential investigative material. Those harms would fall on unconsenting third parties and other agencies—not on the misbehaving FOIA office or litigators.
5) The district court’s failure to consider narrower, administrable alternatives.
The panel faulted the district court for not explaining why it declined to use tools suited for high-volume review when the judge lacked time: referral to a magistrate judge or appointment of a special master.
The absence of an explanation for (a) the breadth of the disclosure sanction and (b) the rejection of alternative review mechanisms rendered the sanction order an abuse of discretion.
6) Remand instructions: limit disclosures to ICE’s own operations and waivable privileges.
The panel did not foreclose sanctions or disclosure; instead, it directed reassessment and limitation. The court drew a line between:
(i) information about the agency’s own operations (which may properly be disclosed as a sanction or remedy), and
(ii) information whose disclosure primarily injures innocent third parties or implicates other law-enforcement bodies.
It also noted that some withheld information may involve privileges (e.g., deliberative-process privilege) that ICE can waive, suggesting waiver may be an appropriate lever—but only within reasoned bounds.
C. Impact
-
FOIA litigation sanctions are constrained by third-party harm.
The opinion signals that “release everything unredacted” is not a default sanction for Vaughn-index failures or delay, especially where disclosure predictably injures nonparties
(identity theft risks, informant exposure, investigative-file sensitivity). Courts must tailor sanctions to target culpable actors and minimize collateral damage.
-
Rule 65 specificity is non-negotiable in FOIA production orders.
District courts must anchor production commands to a specific, identifiable universe (e.g., a dated list, a specific Vaughn index, defined Bates ranges).
Vague references to “responsive records” invite enforcement breakdown and appellate reversal.
-
Encourages institutional solutions for large FOIA records disputes.
By criticizing the failure to consider magistrate/special-master review, the opinion nudges district courts toward scalable adjudication methods when reviewing voluminous redactions.
-
Limits “bad faith” findings based solely on high-volume processing errors.
While not eliminating bad-faith findings, the decision cautions against inferring malice from incompetence in large productions—raising the evidentiary bar when the remedy would be extreme.
4) Complex Concepts Simplified
-
FOIA exemptions (5 U.S.C. §552(b)): Statutory categories that permit (and sometimes require) withholding information. Even when an agency behaves badly,
courts generally must still respect Congress’s exemption scheme unless a lawful, tailored sanction is justified and explained.
-
§552(b)(6): Protects information in “personnel and medical files and similar files” when disclosure would be a “clearly unwarranted invasion of personal privacy.”
The district court found it “egregious” to use (b)(6) to redact an attorney’s name/address on a public brief; the Seventh Circuit treated that as an error but not conclusive proof of bad faith.
-
Vaughn index: A document-by-document (or segment-by-segment) justification log that allows a court and requester to evaluate redactions without seeing the unredacted material.
Poor Vaughn indices frustrate judicial review and can justify remedial orders—but the remedy must still be reasoned and proportionate.
-
Deliberative-process privilege: A privilege (often invoked under FOIA Exemption 5) protecting predecisional, deliberative agency communications.
The privilege belongs to the agency and may be waived, but waiver should not be used to justify disclosures that principally harm third parties.
-
Rule 65(d)(1)(C) injunction specificity: An injunction must clearly state what must be done so the enjoined party can comply and a court can enforce it.
“Produce all responsive records” is too vague when responsiveness is disputed or lists change.
-
Abuse of discretion (sanctions review): Appellate courts defer to district courts on sanctions unless the sanction is inadequately explained, based on legal error,
or imposes unreasonable consequences—here, collateral harm to nonparties without justification.
5) Conclusion
The Seventh Circuit’s decision underscores two practical rules for FOIA litigation. First, FOIA production injunctions must be enforceably specific under Rule 65:
courts must tie production obligations to a clearly defined set of documents. Second, even when an agency’s FOIA handling is sanction-worthy, a court may not leap to an unredacted “release everything”
remedy without explaining why that remedy is appropriate—particularly where it foreseeably harms innocent third parties and implicates sensitive law-enforcement information.
On remand, the district court must reassess sanctions with proportionality and clarity, limiting disclosures to information about the agency’s own operations and to privileges the agency can waive,
and considering administrable review mechanisms (magistrate judge or special master) rather than substituting blanket disclosure for statutory exemption analysis.