Feds for Freedom v. U.S. Department of Defense

CourtDistrict Court, District of Columbia
DecidedFebruary 18, 2025
DocketCivil Action No. 2023-3607
StatusPublished

This text of Feds for Freedom v. U.S. Department of Defense (Feds for Freedom v. U.S. Department of Defense) is published on Counsel Stack Legal Research, covering District Court, District of Columbia primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Feds for Freedom v. U.S. Department of Defense, (D.D.C. 2025).

Opinion

UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA

FEDS FOR FREEDOM,

Plaintiff,

v. Civil Action No. 23-3607 (TJK)

U.S. DEPARTMENT OF DEFENSE,

Defendant.

MEMORANDUM OPINION

In December 2023, Feds for Freedom filed this Freedom of Information Act case seeking

to compel the Department of Defense to process its request for records relating to the COVID-19

pandemic and Operation Warp Speed. Defendant now moves for summary judgment, arguing that

it need not respond to Plaintiff’s request because it is unduly burdensome. The Court agrees.

Accordingly, the Court will grant Defendant’s motion and enter judgment in its favor.

I. Background

On March 10, 2023, Feds for Freedom, an organization formed “to protect employee rights

by confronting the federal government’s mandates requiring vaccination for COVID-19,” sent a

Freedom of Information Act (“FOIA”) request to the Department of Defense seeking “all commu-

nications to/from or carbon copying (cc) or blind carbon copying (BCC) [Captain] David Soldow

related to COVID-19 and Operation Warp Speed.” ECF No. 1 ¶¶ 8, 13; ECF No. 1-1 at 4. Oper-

ation Warp Speed was “a partnership between the Departments of Health and Human Services and

[Defense] aimed to help accelerate the development of a COVID-19 vaccine.” ECF No. 17-1 (“Herrington Decl.”)1 ¶ 5. And Captain Soldow—the Executive Secretary for the Office of the

Secretary of Defense from April 2020 to August 2021—was tasked with “support[ing]” the Of-

fice’s “immediate office management by tasking,” “processing,” and “manag[ing] all correspond-

ence sent to and prepared for the [Secretary] and [Deputy Secretary of Defense].” Id. ¶ 7.

Defendant confirmed that it received the request. ECF No. 1 ¶ 14. And at Defendant’s

request, Plaintiff provided a date range for the records it sought: April 1, 2020, to May 1, 2022.

Id. ¶ 15. Still, Defendant failed to timely respond. ECF No. 1 ¶¶ 14–18. So Plaintiff sued, seeking

“[a]n Order from this Court that [Defendant] is to process and release all records responsive to the

Request immediately.” Id. at 5.

Defendant represents, without contradiction, that Plaintiff refused to consider narrowing

its request any further. ECF No. 13 at 2. So Defendant now moves for summary judgment, arguing

that it need not respond to the request because its scope is so unreasonably expansive that pro-

cessing and responding to it would be unduly burdensome. Id. at 3–4.

II. Legal Standards

“Summary judgment is appropriately granted when, viewing the evidence in the light most

favorable to the non-movant[] and drawing all reasonable inferences accordingly, no reasonable

jury could reach a verdict in [its] favor.” Lopez v. Council on Am.-Islamic Rels. Action Network,

Inc., 826 F.3d 492, 496 (D.C. Cir. 2016). “The evidence presented must show ‘that there is no

genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law.’”

Id. (quoting Fed. R. Civ. P. 56(a)). “In the FOIA context, a district court reviewing a motion for

summary judgment conducts a de novo review of the record, and the responding federal agency

1 ECF No. 17-1 includes two declarations by Mark. H. Herrington. Both are organized by paragraph. The Court’s reference to the Herrington Declaration refers to the earlier declaration, ECF No. 17-1 at 2–6.

2 bears the burden of proving that it has complied with its obligations under the FOIA.” MacLeod

v. DHS, No. 15-cv-1792 (KBJ), 2017 WL 4220398, at *6 (D.D.C. Sept. 21, 2017) (citing 5 U.S.C.

§ 552(a)(4)(B)).

III. Analysis

There is no genuine dispute of material fact that Plaintiff’s FOIA request would be unrea-

sonably burdensome on Defendant. As such, Defendant is entitled to judgment as a matter of law,

and the Court will enter summary judgment in its favor.

FOIA requires agencies to produce responsive records to requests that “reasonably de-

scribe[]” the records sought. 5 U.S.C. § 552(a)(3)(A). FOIA requests fail this requirement, mean-

ing agencies need not respond to them, when the requests (1) rely upon “vague words and descrip-

tions,” (2) “seek[] difficult to locate records,” or (3) impose “overly burdensome post-search ef-

forts.” Ctr. for Immigr. Stud. v. USCIS, 628 F. Supp. 3d 266, 271–72 (D.D.C. 2022). Defendant

argues that Plaintiff’s FOIA request falls squarely within this third category.

The D.C. Circuit established this category in American Federation of Government Employ-

ees v. Department of Commerce (AFGE), 907 F.2d 203 (D.C. Cir. 1990). There, the FOIA requests

at issue sought two “broad” categories of records that included “every chronological office file and

correspondence file, internal and external, for every branch office, staff office, assistant division

chief office, division chief office, assistant director’s office, deputy director’s office, and director’s

office” and “every division or staff administrative office file in the [Census] Bureau which records,

catalogues, or stores SF–52s or stores promotion recommendation memos, or both.” Id. at 205,

208–09. According to the Circuit, such requests, which “might identify the documents requested

with sufficient precision to enable the agency to identify them,” still do not “reasonably describe[]

a class of documents subject to disclosure” because they are “so broad as to impose an unreason-

able burden upon the agency.” Id. at 209 (quotation and internal quotation marks omitted). In

3 other words, even when a request describes the records it seeks with sufficient precision, that de-

scription is still not reasonable as required by 5 U.S.C. § 552(a)(3)(A) when responding to the

request would unduly burden the agency. Id.

The Circuit identified two reasons for concluding that the requests at issue would impose

an unreasonable burden on the agency. First, responding would be quite costly as it “would require

the agency to locate, review, redact, and arrange for inspection a vast quantity of material.” AFGE,

907 F.2d at 209. Second, the requests were “largely unnecessary to the [requesters]’ purpose.” Id.

Because the purpose animating the request was to shed light on the agency’s promotion practices,

the Circuit concluded that the broad requests were unreasonably burdensome because they were

unnecessarily duplicative and extended to documents “in no way tied to [the requesters’] expressed

concern.” Id.

Defendants argue that Plaintiff’s request is unreasonably burdensome under AFGE because

responding to Plaintiff’s request (1) would require substantial time and resources and (2) is to a

large degree unnecessary, considering Plaintiff’s goals. The Court agrees.

A. Plaintiff’s Request Would Require Defendant to Invest Substantial Time and Resources

Starting with the first of AFGE’s considerations, Defendant’s declaration from a former

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Wolf v. Central Intelligence Agency
569 F. Supp. 2d 1 (District of Columbia, 2008)
International Counsel Bureau v. United States Department of Defense
723 F. Supp. 2d 54 (District of Columbia, 2010)
Hall v. Central Intelligence Agency
881 F. Supp. 2d 38 (District of Columbia, 2012)
Ayuda, Inc. v. Federal Trade Commission
70 F. Supp. 3d 247 (District of Columbia, 2014)
Pinson v. U.S. Department of Justice
80 F. Supp. 3d 211 (District of Columbia, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Feds for Freedom v. U.S. Department of Defense, Counsel Stack Legal Research, https://law.counselstack.com/opinion/feds-for-freedom-v-us-department-of-defense-dcd-2025.