Judicial Watch, Inc. v. U.S. Department of Homeland Security

CourtDistrict Court, District of Columbia
DecidedMarch 4, 2026
DocketCivil Action No. 2024-0742
StatusPublished

This text of Judicial Watch, Inc. v. U.S. Department of Homeland Security (Judicial Watch, Inc. v. U.S. Department of Homeland Security) 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
Judicial Watch, Inc. v. U.S. Department of Homeland Security, (D.D.C. 2026).

Opinion

UNITED STATES DISTRICT COURT FOR THE DISTRICT OF COLUMBIA

JUDICIAL WATCH, INC.,

Plaintiff,

v. Civil Action No. 24-cv-742 (TSC)

U.S. DEPARTMENT OF HOMELAND SECURITY,

Defendant.

MEMORANDUM OPINION

On March 14, 2024, Plaintiff Judicial Watch, Inc. brought this action against Defendant

U.S. Department of Homeland Security, seeking records it previously requested under the Freedom

of Information Act, 5 U.S.C. § 552 (“FOIA”). See Compl. ¶ 6, ECF No. 1. After the Complaint

and Answer were filed, Defendant moved for summary judgment on the sole issue in the case—

whether it completed an adequate search pursuant to Plaintiff’s FOIA request. See Mem. in Supp.

of Def.’s Mot. for Summ. J. at 1 (“Def.’s Mot.”), ECF No. 15. Plaintiff opposed Defendant’s

motion and cross-moved for summary judgment, arguing that Defendant failed to complete an

adequate search for records, see Mem. in Supp. of Pl.’s Cross-Mot. for Summ. J. at 2 (“Pl.’s Mot.”),

ECF No. 17. For the reasons below, the court will DENY Defendant’s motion for summary

judgment and DENY Plaintiff’s cross-motion for summary judgment.

I. BACKGROUND

On August 25, 2023, Plaintiff submitted a FOIA request to U.S. Customs and Border

Protection (“CBP”), a component of Defendant. Compl. ¶ 6. The request sought “[a]ll documents

and communications from August 25, 2022 to August 25, 2023, relating to welding open 114 flood

Page 1 of 7 gates in the border wall in Arizona.” Id.; see also Decl. of Patrick Howard (“Howard Decl.”) ¶ 6,

ECF No. 15-3. CBP acknowledged Plaintiff’s FOIA request and assigned it a tracking number.

Howard Decl. ¶¶ 6–7. On or about August 28, 2023, CBP FOIA assigned a document and

communications search to a member of CBP’s Program Management Office Directorate, who

identified nine CBP custodians and several key terms, including “welding, flood gates, Yuma,

Tucson, and Sector,” which were then submitted to CBP’s e-Discovery team for an e-Discovery

search. Id. ¶¶ 8–9.

Having received no response from the agency, Plaintiff filed this case on March 14, 2024,

alleging that Defendant failed to “(i) determine whether to comply with Plaintiff’s request; (ii)

notify Plaintiff of any such determination or the reason(s) therefor; (iii) advise Plaintiff of the right

to appeal any adverse determination; or (iv) produce the requested records or otherwise

demonstrate that the requested records are exempt from production.” Compl. ¶ 8. On May 24,

2024, Defendant filed its Answer. ECF No. 7. And, on September 4, 2024, CBP’s FOIA office

issued its First Interim Response, a total of twelve responsive records consisting of eight pages of

photographs and four pages of emails with redactions. Howard Decl. ¶ 11; Howard Decl., Ex. D1

(“Responsive Emails”), ECF No. 15-8.

Subsequently, CBP reviewed an additional 489 documents and five spreadsheets, which it

eventually determined were non-responsive, Howard Decl. ¶ 12. CBP then issued its Final

Response on October 8, 2024. Id. CBP thereafter conducted a supplemental search, see Feb. 21,

2025 Joint Status Report, ECF No. 13, yielding 571 pages of documents and three spreadsheets.

Howard Decl. ¶ 13. It determined these records were similarly non-responsive. Id.

Defendant moved for summary judgment on April 10, 2025, Def.’s Mot., and Plaintiff

opposed, filing its own cross-motion for summary judgment on May 14, 2025, Pl.’s Mot.

Page 2 of 7 Following Plaintiff’s cross-motion, the Department performed an additional search of the U.S.

Border Patrol’s Sector Chiefs’ personnel records, see Supp. Decl. of Patrick Howard (“Supp.

Howard Decl.”) ¶ 6, ECF No. 21-2, which failed to generate any additional responsive records.

II. LEGAL STANDARD

Summary judgment is appropriate where, viewing the facts in the light most favorable to

the non-moving party, “the movant shows that there is no genuine dispute as to any material fact

and the movant is entitled to judgment as a matter of law.” Fed. R. Civ. P. 56(a); see also Anderson

v. Liberty Lobby, 477 U.S. 242, 247–48 (1986); Holcomb v. Powell, 433 F.3d 889, 895 (D.C. Cir.

2006). A fact is material if “a dispute over it might affect the outcome of a suit under governing

law” and an issue is genuine if “the evidence is such that a reasonable jury could return a verdict

for the nonmoving party.” Holcomb, 433 F.3d at 895 (quoting Anderson, 477 U.S. at 248).

In FOIA litigation, summary judgment may only be granted where an agency demonstrates

that no material facts are in dispute as to whether it conducted an adequate search for responsive

records and whether each responsive record has been produced or is exempt from disclosure. See

Jud. Watch, Inc. v. U.S. Dep’t of Homeland Sec., 59 F. Supp. 3d 184, 189 (D.D.C. 2014). In

determining whether an agency’s search for responsive materials was adequate, courts conduct a

reasonableness test. Rodriguez v. Dep’t of Def., 236 F. Supp. 3d 26, 34 (D.D.C. 2017) (citing

Campbell v. U.S. Dep’t of Just., 164 F.3d 20, 27 (D.C. Cir. 1998)). Under this test, the agency

“must show beyond material doubt . . . that it has conducted a search reasonably calculated to

uncover all relevant documents.” Weisberg v. U.S. Dep’t of Just., 705 F.2d 1344, 1351 (D.C. Cir.

1983). Although “the adequacy of a FOIA search is generally determined not by the fruits of the

search, but by the appropriateness of the methods used to carry out the search,” Iturralde v.

Comptroller of the Currency, 315 F.3d 311, 315 (D.C. Cir. 2003), “evidence that relevant records

Page 3 of 7 have not been released may shed light on whether the agency’s search was indeed adequate,”

Weisberg, 705 F.2d at 1351.

III. ANALYSIS

As noted above, this case turns solely on the adequacy of Defendant’s search. Plaintiff

contends that the agency’s search was inadequate on two counts. First, Plaintiff asserts that the

agency impermissibly failed to follow “clear and certain leads” revealed in a disclosed email that

referenced “an updated work request, a contractor’s work ticket, and a confirmation request from

the sender.” Pl.’s Mot. at 3 (citing Responsive Emails at 7). On this count, Plaintiff suggests that

the email’s reference to the agency’s decision to “additionally open 2 gates” reasonably implies

that other documents related to that decision exist. Id. at 4. Second, Plaintiff argues that

Defendant’s declarations are “too vague to know what systems were searched or how many

systems were searched.” Id. at 3. Upon review of Defendant’s proffered evidence, the court

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
Judicial Watch, Inc. v. U.S. Department of Homeland Security, Counsel Stack Legal Research, https://law.counselstack.com/opinion/judicial-watch-inc-v-us-department-of-homeland-security-dcd-2026.