How to track the status of a FOIA request using agency portals

The Currency of Bureaucracy: The Request ID

The moment you submit a Freedom of Information Act request, the clock theoretically starts. In practice, the statutory clock remains frozen until the agency assigns a specific, perfected tracking number. A submission receipt from FOIA. gov is not a tracking number. It is proof of transmission. Until an agency validates the request and assigns its own internal case identifier, your inquiry exists in a bureaucratic limbo. Securing this alphanumeric string is the single most serious step in the entire lifecycle of a request. Without it, not litigate, not appeal, and not track progress.

Federal agencies processed a record-breaking 1. 5 million requests in Fiscal Year 2024. In this high-volume environment, requests without valid case numbers are frequently discarded or lost in the interoperability gaps between the centralized FOIA. gov portal and decentralized agency case management systems. You must distinguish between a “portal submission ID” (generated by FOIA. gov) and a “perfected request ID” (generated by the agency). The former is a receipt; the latter is a legal token.

The Post-FOIAonline Fragmentation

For over a decade, the “FOIAonline” portal served as a centralized hub for multiple agencies including the EPA, CBP, and the Navy. That era ended on September 30, 2023, when the system was decommissioned. This shutdown forced a massive migration to agency-specific portals, creating a fragmented terrain where tracking methods vary wildly by department. Data from late 2023 and 2024 indicates that migration errors caused thousands of legacy requests to from public view, requiring requesters to manually re-establish contact with agency FOIA officers.

You must identify the specific vendor or portal used by your target agency. The Department of Homeland Security (DHS), which received over 911, 000 requests in FY 2024, utilizes a “Public Access Link” (PAL) or the “SecureRelease” system. As of January 22, 2026, DHS strictly prohibits hard copy or email submissions, mandating portal use exclusively. This shift to digital-only intake creates a binary outcome: either you possess a valid portal account and tracking number, or your request is summarily rejected.

Validating the Identifier Format

A valid tracking number follows a specific syntax unique to the agency. If your confirmation number does not match the standard format for that department, you likely hold a temporary reference number that carries no legal weight. Review the table to verify your identifier.

Table 1. 1: Agency Tracking Number Formats and Portals (2024-2026)

Agency	Primary Portal System	Valid ID Format (Example)	Notes
Dept. of Homeland Security (DHS)	SecureRelease / PAL	2026-HQFO-00123	Strict digital-only submission as of Jan 2026.
FBI	eFOIPA	1500000-000	ID includes a seven-digit base plus a suffix.
Dept. of State	Public Access Link	F-2026-01234	Prefix “F” denotes FOIA; “P” denotes Privacy Act.
Dept. of Defense (OSD/JS)	FOIA. gov / PAL	24-F-1234	frequently uses Fiscal Year prefix (e. g., 24, 25, 26).
EPA	FOIAXpress	EPA-2026-001234	Migrated from FOIAonline in late 2023.

The Statutory Ten-Day Mandate

Federal law provides a specific method to force an agency to assign a number. Under 5 U. S. C. § 552(a)(7)(A), agencies are statutorily required to assign an individualized tracking number to any request that take longer than ten days to process. They must also provide this number to the requester. If ten business days pass without an acknowledgment letter containing this number, the agency is in violation of the statute.

Silence is not a processing status. If you receive a generic “submission received” email from FOIA. gov no follow-up from the agency within ten days, you must assume the interoperability failed. You must immediately contact the agency’s FOIA Public Liaison. Cite the statute and provide your FOIA. gov submission receipt. Demand the “perfected request tracking number.”

Distinguishing “Received” from “Perfected”

Agencies frequently delay assigning a tracking number by claiming a request is not “perfected.” A request is only considered perfected when the agency determines it reasonably describes the records sought and the requester has agreed to pay applicable fees. The statutory 20-day response clock does not begin until perfection. Agencies frequently use this technicality to stall. They may send a letter asking for clarification on the scope. Until you reply and they accept the clarification, no tracking number is assigned, and the request does not officially exist in their backlog queue.

To prevent this limbo, your initial submission must explicitly state your fee category (e. g., “News Media” or “Educational”) and your willingness to pay fees up to a specific amount (e. g., $25). This preempts the most common bureaucratic stall tactic and forces the immediate assignment of a tracking number.

Investigative Tip: Never rely on the “Check Status” button on FOIA. gov for granular updates. The data feed relies on agency APIs which are frequently broken or updated only quarterly. Always log directly into the agency’s specific portal (e. g., FBI eFOIPA or DHS SecureRelease) for real-time status.

ipt of transmission. Until an agency validates the request and assigns its own internal case identifier, your inquiry exists in a bureaucratic limbo. Securing this alphanumeric string is the single most serious step in the entire lifecycle of a request. Without it, not litigate, not appeal, and not track progress. Federal agencies processed a record-breaking 1. 5 million requests in Fiscal Year 2024. In this high-volume environment, requests without valid case numbers are frequently discarded or lost in the interoperability gaps between the centralized FOIA. gov portal and decentralized agency case management systems. You must distinguish between a “portal submission ID” (generated by FOIA. gov) and a “perfected request ID” (generated by the agency). The former is a receipt. The latter is a legal trigger.

The Statutory Definition of “Perfected”

A request is not “perfected” simply because you hit send. Under the Department of Justice’s Guide to the Freedom of Information Act, a request is perfected only when it meets two strict criteria: it must “reasonably describe” the records sought and it must comply with the agency’s specific regulations regarding fees and procedures. The distinction is financial and legal. The statutory 20-day response clock does not begin ticking when the agency receives your email. It begins only when the request is perfected. If an agency determines your description is vague or you have not agreed to pay chance search fees, the request remains in a “received” “unperfected” state. In this state, the agency has no legal obligation to process documents. Data from Fiscal Year 2024 indicates that agencies are increasingly using the “perfection” phase as a gatekeeping method. Of the 1. 5 million requests processed that year, approximately 46. 97% were closed for “procedural or administrative reasons” rather than a substantive release of records. of these closures from requests that agencies deemed “improper” or “not reasonably described” before the statutory clock ever started.

The Tolling Trap: When the Clock Stops

Once a request is perfected, the 20-day clock begins. Agencies possess a method to pause this clock, known as “tolling.” The FOIA Improvement Act of 2016 introduced strict limitations on this practice to prevent indefinite delays, yet agencies continue to use it aggressively to manage backlogs. You must understand the two specific scenarios where tolling is permitted.

Tolling Reason	Legal Limitation (2016 Improvement Act)	Requester Action
Clarification	Agencies may toll the clock only once to request information that clarifies the scope of the request.	Respond immediately. The clock resumes on the exact day the agency receives your clarification.
Fee problem	Agencies may toll the clock an unlimited number of times to resolve problem regarding fee assessments or waivers.	Pre-empt this by stating your “willingness to pay up to $25” or clearly substantiating a fee waiver in the initial filing.

If an agency attempts to toll your request a second time for “clarification,” they are violating the statute. You must immediately cite 5 U. S. C. § 552(a)(6)(A)(ii) in your correspondence. This section explicitly prohibits multiple tolling periods for clarification.

Decoding Processing Tracks: Simple vs. Complex

Upon perfection, agencies assign requests to specific processing queues or “tracks.” The track assignment dictates the speed of your request more than the statutory deadline does. Simple Track: This designation is for requests involving few documents and no consultations with other agencies. While the law mandates a 20-day response, the reality is different. In Fiscal Year 2024, the government-wide average processing time for “Simple” requests rose to 44 days, up from 39. 4 days in 2023. This 44-day average renders the 20-day statutory deadline obsolete for the majority of requesters. Complex Track: Requests involving voluminous records or requiring consultation with other agencies are routed here. There is no statutory limit on how long a “Complex” request can take, provided the agency shows “exceptional circumstances” and “due diligence.” In practice, this track is a graveyard for broad inquiries. The Department of State and the FBI frequently report average processing times for complex requests exceeding 300 days.

The “Still Interested” Loophole

A common tactic to clear older “perfected” requests from the backlog is the “Still Interested” inquiry. Agencies send a letter or email asking if you still require the documents. If you do not respond within a short window (frequently 10 to 30 days), they administratively close the case. The Office of Government Information Services (OGIS) has documented repeated instances where agencies use these letters to artificially reduce backlogs. In 2024, the backlog of pending requests reached 267, 056, a 33% increase from the previous year. To combat this swelling number without actually processing records, agencies utilize administrative closures. Your Countermeasure: If you receive a “Still Interested” letter, respond immediately via a verifiable method (certified mail or portal upload). State clearly: “I remain interested in this request. Please provide an estimated date of completion as required by 5 U. S. C. § 552(a)(7)(B).”

Interpreting Portal Status Codes

Agency portals like PAL (Public Access Link) or the DHS FOIA Public Access Portal use specific status codes that frequently differ from the legal terminology. * “Submitted” / “Received”: The request is in the system not perfected. The clock has not started. * “Evaluation” / “Assessment”: The agency is determining fee status or track assignment. * “Perfected” / “In Process”: The 20-day clock is ticking (or has already expired). * “Tolled”: The clock is stopped pending your response. * “Consultation”: Your documents are being reviewed by another agency. This status frequently precedes months of silence. You must monitor these statuses weekly. If a request remains in “Submitted” for more than 10 days, the agency is failing to conduct the initial intake required to perfect the request. A follow-up phone call to the FOIA Public Liaison is necessary to force the status change.

The DHS Public Access Link (PAL) and Component Fragmentation

The Department of Homeland Security (DHS) receives over 60% of all federal FOIA requests, processing more than 895, 000 inquiries in Fiscal Year 2024 alone. Yet, tracking a request within DHS is not a singular process. The agency operates a fragmented digital ecosystem where the “Public Access Link” (PAL) is one of three distinct portals. Your ability to extract real-time status updates depends entirely on identifying which specific component holds your records and logging into the correct silo.

As of January 22, 2026, DHS eliminated the paper trail for most requesters. The agency no longer accepts hard copy (mail) or email submissions for standard records, mandating the use of these digital portals. This policy shift forces all requesters into a centralized digital tracking environment, yet the backend processing remains decentralized. A request submitted to the wrong portal languish in a referral queue for months before being rejected or rerouted.

The Three-Portal System

DHS components do not share a unified tracking database. You must direct your browser to the specific portal governing the component you targeted. Using the wrong interface yields “No Records Found” errors, even if a valid request exists in a parallel system.

Component	Required Portal	Primary URL	FY24 Backlog Volume
ICE, HQ, OBIM, TSA	DHS PAL	foiarequest. dhs. gov	High (Litigation Heavy)
CBP (Border Patrol)	SecureRelease	securerelease. us	~3, 000+ (Complex Track)
USCIS (Immigration Files)	System	. uscis. gov	Voluminous (A-Files)

Decoding Status Codes in DHS PAL (ICE and HQ)

For requests directed to Immigration and Customs Enforcement (ICE) or DHS Headquarters, the PAL interface provides a status bar that frequently misleads novice requesters. The interface displays generic milestones that mask the actual bureaucratic activity, or inactivity, occurring behind the scenes.

“Received” vs. “Perfected”: A status of “Received” indicates your request sits in the intake queue. It has not been assigned to an analyst, and the statutory 20-day clock has not started. Only when the status shifts to “Perfected” or “Ack/Perfected” has the agency validated your description and identification. If your request remains “Received” for more than 10 business days, you must contact the Public Liaison immediately, as this signals a failure in the intake workflow.

“Gathering Records”: This code implies active searching. In reality, it frequently means the FOIA officer has sent a “tasker” email to a program office (e. g., ICE Enforcement and Removal Operations) and is waiting for a response. This phase is the primary bottleneck. If a request stagnates here for 60 days, it is highly probable the program office has ignored the tasker. You must file a follow-up inquiry demanding the date the tasker was sent.

“Complex” Track Assignment: DHS automatically routes requests into the “Complex” processing track if they involve multiple offices or voluminous records. In FY 2024, the average processing time for CBP Complex requests was 127 working days, compared to just 7 days for Simple requests. If your status shows “Complex,” expect a minimum six-month delay unless you narrow the scope to force a re-classification to “Simple.”

Navigating CBP’s SecureRelease

Customs and Border Protection (CBP) operates on the SecureRelease platform. Unlike the legacy PAL, this system offers a more granular “Request Details” view. yet, it suffers from a specific opacity regarding “referrals.”

If your CBP request involves records originating from another agency (common with FBI background checks at the border), SecureRelease frequently mark the request as “Closed” or “Partial Grant” while simultaneously routing the external documents to the originating agency for review. The portal rarely alerts you to this referral explicitly. You must download the final determination letter to see if a “Consultation” or “Referral” has occurred. If so, you must obtain the new tracking number for that external agency; the CBP tracking number becomes useless for that portion of the records.

The USCIS System

For Alien Files (A-Files), USCIS uses the Freedom of Information Act Immigration Records System ( ). This is the most modern yet rigid of the three. requires a verified myUSCIS account. Its status updates are binary: “Submitted” or “In Process.”

The serious metric in is the “Estimated Date of Completion” (EDC). Unlike other portals where the EDC is a static placeholder, USCIS updates this date based on the queue depth. If the EDC shifts forward by months, it indicates a surge in A-File requests, which historically comprise the bulk of the DHS backlog. In 2024, USCIS processed record volumes, yet the sheer density of paper files requiring digitization continues to throttle speed. If your status in is “In Process” the EDC has passed, you have immediate grounds for an administrative appeal on “Constructive Denial.”

The “Correspondence” Trap

Across all three portals, the most dangerous status is “On Hold, Fee Related” or “Clarification Requested.” Agencies pause the processing clock while awaiting your response. These notifications are frequently buried in a “Correspondence” or “Messages” tab within the portal, separate from the main status dashboard. The system does not reliably email you these alerts. You must manually check the Correspondence tab weekly. Failure to respond to a clarification request within 30 days allows the agency to administratively close your case without penalty.

Investigator’s Note: Never rely on the “percent complete” progress bar found in third-party tracking tools or the main FOIA. gov dashboard. These are algorithmic estimates, not real-time reflections of the agency’s work. The only verified data points are the Date Perfected and the Track Assignment (Simple/Complex).

The FBI eFOIPA Ecosystem: A Separate Reality

The Federal Bureau of Investigation operates a distinct digital fiefdom for information requests that functions independently from the centralized FOIA. gov infrastructure. While you may initiate a request through the general government portal, the Bureau immediately migrates valid submissions into its proprietary system, known as eFOIPA. Understanding the mechanics of this specific portal is mandatory for any requester seeking files on federal investigations, as the FBI processes a massive volume of the Department of Justice’s total load, which reached 157, 180 requests in Fiscal Year 2024. The point of failure for journalists is the confusion between the Electronic Tracking Number (ETN) and the FOIPA Request Number. When you submit a request via the eFOIPA portal, the system generates an ETN (e. g., R1234567). This is a receipt of transmission. It is not a perfected request identifier. not use an ETN to litigate, appeal, or even check the status of your case. The Bureau’s Record/Information Dissemination Section (RIDS) must review the submission for compliance with 28 C. F. R. § 16. 3. Only after this validation does the agency assign a FOIPA Request Number (e. g., 1555555-000). You must wait for the notification email containing the FOIPA Request Number before track anything. If you attempt to query the status portal with an ETN, the system return no results, leading to the false assumption that the request was lost. The conversion from ETN to FOIPA Number can take anywhere from 24 hours to three weeks depending on the intake queue volume.

Decoding the Five Processing Tracks

The FBI utilizes a rigid multi-track processing system based strictly on page count. This is a mechanical sorting hat that determines the velocity of your request. Unlike agencies that vaguely define “complex” based on the difficulty of the search, the FBI publishes specific page thresholds that dictate your queue. If you structure your request broadly, you inadvertently land in the “Large” or “Extra-Large” tracks, where processing times are measured in years. The tactical requester intentionally narrows the scope of a request to fit within the “Extra-Small” or “Small” tracks to secure a response within the statutory window.

FBI FOIA Processing Tracks (Page Count Thresholds)

Track Name	Page Count Range	Estimated Velocity	Tactical Recommendation
Extra-Small	0, 50 pages	High (20-60 days)	Target specific documents (e. g., “The opening EC”).
Small	51, 250 pages	Moderate (3-12 months)	Limit date range to <6 months.
Medium	251, 500 pages	Low (1-2 years)	Avoid unless necessary.
Large	500, 4, 999 pages	Glacial (2-5 years)	Break into multiple smaller requests.
Extra-Large	5, 000+ pages	Stagnant (Indefinite)	Do not use. Refine scope immediately.

The “Medium” track was temporarily eliminated in previous operational pattern has been reinstated in recent procedural guidelines. Note that the FBI counts responsive pages, not released pages. If a file contains 600 pages 550 are fully redacted, you still sit in the Large track behind other massive requests.

The Vault and the “Rule of Three”

The FBI’s electronic reading room, known as The Vault, is not an archive. It is an active component of the request lifecycle that can paradoxically delay your access to information. Under the Department of Justice’s “Frequently Requested Records” provision, frequently colloquially called the Rule of Three, agencies are required to post records online if they have been requested three or more times. When your request triggers this threshold, the processing workflow changes. Instead of a direct release to you, the records must undergo Section 508 compliance remediation to ensure accessibility for the visually impaired before they can be posted to The Vault. This additional formatting step frequently adds weeks or months to the release timeline. You must check The Vault before filing. The Bureau hosts over 6, 700 scanned files covering civil rights, counterterrorism, and unusual phenomena. If the records are already there, filing a new request is a waste of resources. The agency simply close your request and direct you to the URL.

Correlating Status Codes

The eFOIPA status portal (located at `vault. fbi. gov/fdps-1/@@search-fdps`) provides limited granularity. It updates only once per week, on weekends. Real-time tracking is nonexistent. * “Open”: The request is in the queue. This status can for years without change. * “Awaiting Consult”: The FBI has located records they originated from another agency (e. g., CIA, NSA). The file has been sent to that agency for review. This is a black hole; the FBI pauses its clock while the other agency reviews. * “Closed”: A determination has been made. The status remains visible for only six months after closure. If you do not download your release or save your decision letter within this window, the record of the case from the public portal, and you have to file a new request just to get the old case notes.

Tactical Analysis of FY 2024 Metrics

Data from the Department of Justice’s Fiscal Year 2024 reports indicates a system under extreme pressure. While the DOJ reported a backlog reduction of over 50% in components, the “Simple” track average processing time across the department rose to approximately 44 days. This exceeds the statutory 20-day limit by more than double. For the FBI specifically, the “Extra-Small” track (0-50 pages) is the only viable lane for journalists requiring timely data. If you are investigating a large subject, do not ask for “any and all records.” Instead, submit a sequence of “Extra-Small” requests. For example, Request A asks for “The Case Opening Electronic Communication (EC).” Request B asks for “The Case Closing EC.” Request C asks for “FD-302s from January 2023.” This method keeps each individual request in the fast lane, whereas combining them would dump you into the “Large” track abyss.

Investigative Note: The FBI eFOIPA portal allows you to upload attachments. Always upload a PDF of your specific subject’s death certificate (if applicable) or a privacy waiver (Form DOJ-361). Failing to do this triggers a “Proof of Death/Privacy” administrative closure, forcing you to restart the process and lose your place in the queue.

Visualizing the Bottleneck

The following chart illustrates the estimated processing velocity based on the FBI’s page-count tracks. The exponential decay in speed as page count rises is the serious metric for request structuring.

The “No Records” Trap

A frequent status result on the portal is “No Records Located.” This does not necessarily mean the FBI never investigated the subject. It frequently means the search terms were too specific or the files were transferred to the National Archives (NARA). The FBI transfers permanent historical records to NARA when they are no longer operationally relevant. If your subject is from the 1970s or 80s, the eFOIPA portal likely return a “No Records” status because the physical files are sitting in College Park, Maryland, not in the FBI’s Central Records System (CRS). You must verify the “Cutoff Date” listed in your final response letter. The FBI only searches for records created up to the date the search began. If an investigation is ongoing and generates new records the day after your search starts, those records are excluded. You must file a new request to capture the delta.

The statutory mandate that federal agencies respond to Freedom of Information Act requests within 20 business days is a legal fiction. In Fiscal Year 2024, the federal government received a record-breaking 1. 5 million requests, a 25% surge from the previous year. This volume collapsed the standard processing timelines. To track a request, you must ignore the statutory deadline and calculate a “Real-World Completion Date” (RWCD) using the agency’s specific performance metrics from the FY2024 Annual FOIA Report.

The Zombie Statute: 20 Days vs. 44 Days

The Freedom of Information Act nominally requires a determination within 20 working days. Yet, the Department of Justice’s FY2024 summary data reveals that the average processing time for “Simple” track requests, those requiring minimal review, has climbed to 44 days. This is more than double the legal limit. For investigative reporters and data scientists, the “Simple” track is irrelevant. Most substantive inquiries involving contracts, emails, or datasets are routed to the “Complex” track. The wait times here are not measured in weeks, in months or years.

The “Average” Trap: Agencies frequently cite an “Average Processing Time” that is artificially lowered by thousands of “No Records Found” responses, which are frequently closed within 48 hours. These quick closures dilute the data, masking the true wait time for requests that actually yield documents.

FY2024 Agency Performance Benchmarks

To estimate your specific wait time, you must identify which agency holds your records. The variance in performance is extreme. The Department of Homeland Security (DHS) alone accounted for 61% of all government-wide requests in FY2024, creating a distinct processing ecosystem compared to smaller agencies. The following table aggregates verified performance data from the FY2024 Annual FOIA Reports submitted to the Attorney General:

Agency	FY2024 Requests Received	Backlog Size	Backlog Growth (YoY)	Processing Reality
DHS (in total)	911, 000+	142, 000+	+30%	Processed simple requests in <20 days (claimed), yet backlog grew by 30, 000+.
Dept. of Defense	61, 858	21, 436	+8%	Only 52% of processed cases resulted in information release.
Dept. of Justice	~100, 000+	High Variance	Variable	Processed 13, 000+ more requests than FY23, yet demand outpaced capacity.
Gov-Wide Average	1, 501, 432	267, 056	+33%	Simple Track Avg: 44 Days

The “Oldest Pending” Indicator

Every agency must report its “Ten Oldest Pending Requests” in Section VII of their Annual Report. This is the single most accurate indicator of an agency’s structural failure. If the oldest pending request at your target agency dates back to 2015, a complex request submitted today has a near-zero probability of completion within the fiscal year. For example, while the Department of Defense claims to complete 83% of requests in fewer than 100 days, the existence of requests pending for over a decade in the “Complex” queue signals that difficult requests are frequently parked indefinitely. You must check the specific component’s “Oldest Pending” date. If the oldest request is less than 2 years old, the queue is moving. If it is 5+ years old, the queue is stagnant.

Calculating Your Real-World Completion Date (RWCD)

Do not rely on the estimated completion date (ECD) provided by the FOIA portal. These are frequently auto-generated based on statutory defaults (20 days) rather than queue realities. Use this formula to benchmark your wait time:

RWCD Formula:
(Median Complex Days from FY2024 Report) × 1. 5 = Minimum Wait Time

Why the 1. 5 multiplier? 1. Queue Jumping: Expedited requests (which increased by 37% in FY2024) cut in front of standard requests. 2. Litigation Priority: Agencies prioritize requests involved in lawsuits. With $54 million spent on litigation-related activities in FY2024, resources are constantly diverted to sue-happy requesters. 3. Consultation Lag: If your request involves records from multiple agencies (e. g., State Department emails referencing the CIA), the “Consultation” process pauses your clock entirely while the documents are shipped to the other agency for review.

The “Full Grant” Probability

Wait times are only half the equation. The probability of receiving unredacted documents also plummeted in FY2024. Only 22. 83% of processed requests resulted in a “Full Grant” (full disclosure). The majority (70. 88%) resulted in partial grants, where exemptions are applied. If you are tracking a request that involves law enforcement (Exemption 7) or internal deliberations (Exemption 5), you should anticipate a “Partial Grant” response. This adds a secondary wait time: the administrative appeal. In FY2024, the government received 20, 115 appeals, a 39% increase. If your strategy relies on appealing redactions, add an additional 96 days (the average appeal processing time) to your total timeline.

Actionable Steps for Benchmarking

1. Locate the Raw Data: Go to FOIA. gov/data. Download the “FY 2024 Annual Report” CSV file. 2. Filter by Component: Do not look at “Department of Justice” in total. Filter for “FBI” or “Drug Enforcement Administration.” The parent agency average is useless; the component data is predictive. 3. Find the Median: Look for the column `Median Days to Process, Complex`. 4. Check the Backlog Ratio: Compare `Requests Received` vs. `Requests Processed`. If `Received`> `Processed`, the backlog is growing, and the `Median Days` figure is likely a lagging indicator that underestimates current delays. By using the FY2024 data to set a realistic baseline, you move from passive waiting to active monitoring. You know exactly when a delay becomes statistically abnormal, which is the trigger point for filing an appeal or a lawsuit.

The Statutory Mandate: 5 U. S. C. § 552(a)(7)(B)

Once you possess a perfected request ID, you unlock a specific, enforceable right that most requesters ignore: the right to an Estimated Date of Completion (EDC). Under 5 U. S. C. § 552(a)(7)(B)(ii), federal agencies are statutorily required to establish a telephone line or internet service that provides information about the status of your request, including “an estimated date on which the agency complete action on the request.”

This is not a courtesy. It is a codified requirement. Yet, agencies frequently default to vague non-answers like “your request is in the complex queue” or “we are processing requests in the order received.” These responses violate the spirit and letter of the law. In Fiscal Year 2024, federal agencies faced a backlog of over 267, 000 requests, a 33% increase from the previous year. Without a firm EDC, your request becomes a ghost in this expanding machine.

The “Complex Queue” Trap

Agencies use the “queue” defense to avoid accountability. They tell you that you are number 450 in the “complex track” refuse to translate that into a calendar date. This is insufficient. The Office of Government Information Services (OGIS) issued Advisory Opinion No. 2020-01, explicitly stating that agencies must provide an estimated date when asked. While the date is an estimate and not a binding contract, the refusal to provide one can constitute a “pattern or practice” violation of FOIA, actionable in federal court.

Verified Processing Realities (FY 2024-2025)

The need of demanding an EDC is driven by deteriorating processing times. Data from the Department of Justice’s Office of Information Policy reveals that waiting passively is a failed strategy.

FY 2024 Federal FOIA Processing Metrics

Metric	Statistic	Trend (vs FY 2023)
Total Requests Received	1, 501, 432	+25% (Record High)
Backlogged Requests	267, 056	+33%
Avg. Time (Simple Track)	44 Days	+5 Days
Requests Granted in Full	12%	Lowest on Record

The Enforcement Script

Do not ask for an update; demand compliance. Use the following script to compel the agency to provide a specific date. This language signals that you are aware of your statutory rights and prepared to escalate.

Subject: Status Inquiry and Demand for EDC, Request No. [INSERT AGENCY ID]

Body:
To the FOIA Public Liaison,

I am writing to request the status of my FOIA request, assigned case number [INSERT AGENCY ID]. This request was perfected on [INSERT DATE].

Pursuant to 5 U. S. C. § 552(a)(7)(B)(ii), I am formally requesting the estimated date on which the agency complete action on this request. Please provide a specific calendar date (Month/Year) for completion.

If you are unable to provide a specific date, please explain the specific factors preventing this estimation and provide a date by which you be able to offer an EDC. Note that OGIS Advisory Opinion No. 2020-01 affirms that agencies must provide an EDC upon request and that a refusal to do so may constitute a pattern or practice of non-compliance.

Vague assertions regarding “queue position” or “processing order” do not satisfy the statutory requirement to provide a date. I expect a substantive response within 3 business days.

Respectfully,
[Your Name]

Escalation Tactics

If the agency ignores this script or replies with a generic template, you must escalate immediately. The law requires them to give you a date. If they fail:

1. Contact the FOIA Public Liaison: Every agency has a Public Liaison responsible for resolving disputes. Forward the refusal to them, citing the specific statute again.
2. File an OGIS Mediation Request: Submit a request for assistance to the Office of Government Information Services. Attach the email chain showing the agency’s refusal to provide an EDC.
3. Litigation Warning: In extreme cases, such as the March 2026 lawsuit filed by the Washington State Attorney General against the Department of Energy, courts have entertained claims where agencies systematically fail to provide determinations or EDCs. While you may not sue immediately, reminding the agency of recent litigation outcomes can force movement.

Common Agency Deflections and Counter-Moves

Agencies have developed a playbook to deflect EDC demands. You must recognize these moves to counter them.

The “Rolling Production” Dodge

Agency Claim: ” release records on a rolling basis, so we cannot give a final completion date.”
Your Counter: Demand an EDC for the interim release. 5 U. S. C. § 552 does not exempt rolling productions from status reporting. Ask: “Please provide the estimated date for the interim release of records.”

The “Consultation” Black Hole

Agency Claim: “Your records are out for consultation with another agency.”
Your Counter: Demand the identity of the consulting agency and the date the records were sent. You then have the right to track the consultation directly with that agency. A consultation does not absolve the primary agency of its duty to track the request.

Q&A: Enforcing the EDC

Q: Does the agency have to give me an exact day?
A: No. Courts generally accept a “reasonable” estimate, such as “Late Q3 2026” or “November 2026.” yet, they cannot refuse to give any timeframe.

Q: What if they miss the estimated date?
A: An EDC is non-binding. Missing it does not automatically win you a lawsuit. yet, repeated missed dates without explanation can be evidence of “bad faith” or failure to exercise “due diligence,” which strengthens your position in fee waiver disputes or litigation.

Q: Can I use the EDC to get expedited processing?
A: Indirectly. If an agency provides an EDC that is years in the future (e. g., “September 2030”), use that egregious delay to for expedited processing if demonstrate a “compelling need” for the information.

Q: Does the FBI have a special exemption?
A: No. While the FBI handles sensitive data, they are subject to the same procedural requirements of 5 U. S. C. § 552(a)(7)(B). They frequently use the “complex” track defense, they are still required to estimate completion.

Q: What is the “10-day” rule for tracking numbers?
A: Under 5 U. S. C. § 552(a)(7)(A), agencies must assign a tracking number to any request that take longer than 10 days to process. If you haven’t received a tracking number after 10 days, the agency is already in violation.

The Lagging Autopsy vs. The Live Pulse

Most journalists and researchers rely on the Annual FOIA Report, a document published months after the fiscal year concludes. By the time you read an Annual Report in April 2026, the data regarding a backlog spike in October 2024 is eighteen months old. This is an autopsy, not a diagnostic tool. To detect processing stalls in real-time, you must use Quarterly FOIA Reports. These datasets are the only leading indicators available to the public that reveal when an agency’s processing capacity is collapsing.

The Department of Justice Office of Information Policy (OIP) mandates that all federal agencies report four specific metrics every quarter. Unlike the sanitized Annual Report, which aggregates data into broad averages, quarterly raw data allows you to pinpoint the exact moment a specific component (e. g., the FBI within the DOJ) stops working. access this data directly via the FOIA. gov Quarterly Report tool, the browser interface is insufficient for serious auditing. You must download the raw CSV files to perform a comparative analysis.

The “Ten Oldest” Litmus Test

The most revealing metric in the quarterly data is the status of the “Ten Oldest Pending Requests.” Agencies are required to list the closing date of the ten oldest requests from the previous fiscal year. This field acts as a canary in the coal mine for complex processing queues.

If you are tracking a request that has been pending for years, you must examine this data point across consecutive quarters. A functioning FOIA office show movement in this list, Request #1 closes in Q1, Request #2 moves up, and new dates appear. A stalled office report the exact same dates for its ten oldest requests in Q1, Q2, and Q3. This indicates that the agency has abandoned its oldest complex cases to focus on “low-hanging fruit” (simple requests) to pad their processing statistics.

How to Audit the “Ten Oldest” Stagnation

Download the quarterly CSVs for Fiscal Year 2024 and 2025. Isolate your target agency and compare the “Ten Oldest” columns. If the agency reported closing zero of its ten oldest requests in the three quarters of FY 2024, you have verified proof of administrative negligence. This data point is legally potent in litigation; it demonstrates a “pattern and practice” of delay that overrides the agency’s standard defense of “unusual circumstances.”

Table 7. 1: Detecting Stalls via “Ten Oldest” Data (Hypothetical Pattern)

Quarter	Ten Oldest Closed?	Oldest Date Listed	Analysis
Q1 FY2025	0	2018-04-12	STALL: No movement on oldest cases.
Q2 FY2025	0	2018-04-12	STALL: Oldest date remains static.
Q3 FY2025	2	2018-06-05	ACTIVE: Agency closed 2 oldest; date shifted forward.
Q4 FY2025	0	2018-06-05	STALL: Processing halted again at year-end.

Calculating Backlog Velocity

The raw number of backlogged requests is less important than the velocity of its growth. In FY 2024, the government-wide backlog surged by 33% to over 267, 000 requests. yet, this growth was not uniform. By analyzing quarterly inputs, identify which specific components are responsible for the explosion.

Calculate the Backlog Velocity Ratio using the following formula from the raw data:

(Requests Received in Q_Current, Requests Processed in Q_Current) = Net Backlog Add

If the “Net Backlog Add” is positive for three consecutive quarters, the agency is in a “death spiral.” For example, Department of Homeland Security (DHS) components frequently receive thousands more requests than they process in Q1 and Q2, creating a deficit that is mathematically impossible to clear in Q4. If your request is assigned to a component with a positive Net Backlog Add of 500+ requests per quarter, your estimated completion date (ECD) is likely fiction.

Component-Level Granularity

A common error is analyzing the “Agency in total” numbers while ignoring the “Component” columns. The Department of Justice (DOJ) may report healthy processing numbers in total, that aggregate success frequently masks catastrophic failures at the FBI or the DEA. The raw CSV data separates these components.

In FY 2024, the DOJ processed over 13, 000 more requests than the previous year, yet specific components like the Executive Office for Immigration Review (EOIR) continued to carry the bulk of the backlog. When you download the quarterly data, filter immediately by Component. If you are investigating the State Department, do not look at “State in total”; look at the specific bureau metrics if available, or track the “Complex” queue processing times which are frequently buried in the raw datasets.

The “End-of-Year” Dump

Experienced auditors watch for the Q4 anomaly. Agencies frequently engage in an “end-of-year dump” to sanitize their Annual Report statistics. You frequently see a massive spike in “Requests Processed” in Q4 (July, September) compared to Q1, Q3. This is rarely the result of increased efficiency.

Instead, this spike frequently represents:

• Administrative Closures: The agency closes hundreds of cases for “failure to pay fees” or “failure to reasonably describe records” to get them off the books.
• Bulk Denials: A wave of “Glomar” responses (refusal to confirm or deny) or “No Records Found” determinations.

If you see a Q4 processing spike of 50% or more compared to the Q1, Q3 average, treat every closure notice received in September with extreme skepticism. It is highly probable the agency closed the request to meet a metric, not because they located the records.

Using Raw Data in Appeals

When you file an administrative appeal for “Constructive Denial” (failure to respond in time), do not simply state that the agency is late. Cite the quarterly data. A compelling argument looks like this:

“The agency’s own Quarterly FOIA Reports for FY 2024 indicate a widespread failure to process complex requests. In Q1, Q2, and Q3, the agency reported closing zero of its ten oldest requests. also, the agency’s backlog increased by 15% in the last two quarters alone. This data proves that the delay in my case is not an error, part of a total collapse in processing capacity that violates the statutory requirements of the FOIA.”

This forces the appellate authority to confront their own verified metrics. They cannot claim “diligence” when their own spreadsheets prove stagnation.

The Potemkin Portal

Government FOIA portals are designed to pacify, not inform. The status bar that reads “In Process” or “Gathering Records” is frequently a digital fiction that masks a statutory violation. While the agency’s internal system may calculate a due date based on when a clerk opened your email, the Freedom of Information Act operates on a strict biological clock that begins the moment your request is received by the correct component. To successfully litigate or appeal a delay, you must maintain a “Shadow Docket”, a forensic ledger that tracks the agency’s performance against the hard metrics of 5 U. S. C. § 552.

The 20-Day Statutory Reality

Federal law mandates a determination within 20 working days. This is not a suggestion. It is a statutory command codified in § 552(a)(6)(A)(i). Yet, data from Fiscal Year 2024 reveals a widespread collapse of this mandate. The average processing time for “simple” requests, those requiring minimal review, ballooned to 44 days, more than double the legal limit. Complex requests at agencies like the Department of State averaged 564 days, creating a functional denial of access through delay.

The Shadow Docket serves one primary purpose: to identify the exact date of “constructive exhaustion.” This legal doctrine triggers when an agency fails to comply with applicable time limits. Once the statutory clock runs out, you are deemed to have exhausted your administrative remedies. immediately file a lawsuit in federal district court without waiting for a final response or filing an administrative appeal.

Anatomy of the Shadow Docket

Do not rely on the “Estimated Date of Completion” (EDC) provided by the agency portal. These dates are frequently algorithmic guesses that adjust automatically as the backlog grows. Build your own tracking matrix with the following verified data points:

Table 8. 1: The Shadow Docket Schema

Data Point	Definition	Why It Matters
Transmission Timestamp	The exact second your request hit the agency server (from your email sent folder or portal receipt).	Agencies frequently log the “Receipt Date” days or weeks later. The clock starts on receipt, not acknowledgement.
Statutory Start Date	The business day after transmission.	This anchors your 20-day countdown.
Tolling Events	Specific dates the agency asked for fee clarification or scope narrowing.	Agencies can only toll the clock once for scope clarification. They cannot toll repeatedly for “status updates.”
Statutory Due Date	Start Date + 20 working days + 10 days (if “unusual circumstances” invoked).	The precise date the agency violates the law.
Constructive Exhaustion Date	The day after the Statutory Due Date.	The date you gain standing to sue.

The Tolling Trap

Agencies frequently attempt to pause the 20-day clock, a practice known as “tolling.” The FOIA Improvement Act of 2016 placed strict limits on this method to prevent abuse. An agency may toll the clock only in two specific scenarios:

1. Reasonable Request for Clarification: The agency may toll the clock one time to obtain information needed to reasonably process the request. Once you respond, the clock resumes. They cannot toll again for further clarification.

2. Fee problem: The agency may toll the clock as times as necessary to resolve fee assessment disputes, such as a denial of a fee waiver or a refusal to commit to payment.

If an agency status updates to “Pending Consultation” or “Awaiting Review,” the clock does not stop. These are internal processing stages, not valid tolling events. Your Shadow Docket must reflect the running clock during these periods. If the portal shows a “Paused” status for any reason other than the two listed above, the agency is manufacturing a delay that not hold up in court.

Visualizing the Violation

The between the law and agency performance is clear. In FY 2024, the backlog of pending requests surged by 33% to over 267, 000 cases. This backlog is not a queue; it is a graveyard of statutory deadlines. The following chart compares the legal mandate against the actual performance of high-volume agencies.

Chart: The Statutory Gap (FY 2024)

The following data contrasts the 20-day statutory limit against the average processing times for complex tracks at major agencies.

Agency	Statutory Limit	Avg. Processing Time (Complex)	Violation Factor
Dept. of State	20 Days	564 Days	28. 2x
Dept. of Justice (OIP)	20 Days	~98 Days	4. 9x
Govt-Wide Average	20 Days	44 Days (Simple Track)	2. 2x

Documenting the Constructive Denial

When your Shadow Docket indicates the 20-day limit has passed, you must memorialize the violation. Take a timestamped screenshot of the agency portal showing the “Pending” status. Save this alongside your original transmission receipt. This evidence package proves that the agency failed to make a determination within the statutory window.

Agencies frequently rely on the “Still Interested” letter, a tactic where they email requesters months or years later asking if they still want the records. If you do not reply within a short window, they close the case. This is an administrative purge method designed to artificially lower backlog numbers. Your Shadow Docket prepares you for this. When you receive a “Still Interested” inquiry, your immediate response should cite the number of days the request has been in violation of the statute, referencing your specific calculations.

The statutory clock for a Freedom of Information Act request is rigid, yet federal agencies treat it as a suggestion. Under 5 U. S. C. § 552(a)(6)(A)(i), an agency has 20 working days to make a determination. If they fail to respond within this window—and have not issued a valid 10-day extension for “unusual circumstances”—you have entered the legal territory of Constructive Denial. This status changes your tactical position. You are no longer waiting for a favor; you have exhausted administrative remedies by default, granting you the immediate right to file a lawsuit in federal district court. yet, litigation is expensive and slow. For requesters, the intermediate step, triggering an administrative appeal based on silence, is the most method to dislodge a stuck request without paying court filing fees.

The Mechanics of Constructive Denial

Constructive denial is not a formal rejection letter. It is the absence of a determination. In Fiscal Year 2024, federal agencies faced a record-breaking surge, receiving over 1. 5 million requests. This volume paralyzed processing queues, forcing agencies to ignore statutory deadlines en masse. When the 20th business day passes (or the 30th, if an extension was claimed), the agency has legally denied your request. You must document this silence. Take a screenshot of the agency portal showing “Status: Pending” or “Received” with a date stamp exceeding the statutory limit. This evidence supports your appeal or future litigation.

Filing an Appeal on “Adverse Determination by Silence”

Most agency portals (PAL, FOIAonline archives, and decentralized component sites) have an “Appeal” button. If the request is still marked “Open,” this button may be inactive. You must then file your appeal via email or certified mail, citing the request number and the specific statutory violation. Your appeal language must be precise. Do not complain about customer service. State that you are appealing the constructive denial of access due to the agency’s failure to comply with the time limits set forth in 5 U. S. C. § 552(a)(6)(A)(i).

Template Segment for Constructive Denial Appeal:
“This is an administrative appeal regarding Request ID [INSERT ID]. The agency has failed to make a determination within the statutory 20-working-day limit. This failure constitutes a constructive denial of access. I request an immediate determination on my request. If this appeal is not adjudicated within 20 working days as required by 5 U. S. C. § 552(a)(6)(A)(ii), I deem my administrative remedies fully exhausted for the purposes of litigation.”

The Agency Split: The “State Department Trap”

Not all agencies accept appeals for constructive denial. A dangerous procedural split exists. Agencies like the Department of Homeland Security (DHS) and the Department of Justice (DOJ) generally process these appeals, frequently “remanding” the request back to the FOIA office with instructions to expedite. This acts as a priority bump. yet, agencies such as the Department of State and the Department of Housing and Urban Development (HUD) frequently take the position that not administratively appeal a absence of response. Their stance is that the only remedy for silence is a federal lawsuit. If you file an appeal for silence with these agencies, they may dismiss it procedurally, stating no “adverse determination” has been made yet. You must know the specific regulations of your target agency to avoid wasting 90 days on a futile appeal.

FY 2024 Appeal Metrics

The backlog of administrative appeals is growing, though not as fast as the initial request backlog. In FY 2024, the government received 20, 115 administrative appeals, a 39% increase from the previous year. The processing times vary wildly by agency, dictating your strategy.

FY 2024 Administrative Appeal Processing Times (Selected Agencies)

Agency	Average Processing Time (Days)	Strategic Implication
Dept. of Homeland Security (DHS)	12. 00	High Utility. Fast remands can speed up initial search.
Dept. of Justice (DOJ)	68. 82	Moderate Utility. Slower, OIP oversight is rigorous.
Dept. of Defense (DOD)	173. 22	Low Utility. The appeal itself be backlogged.
Government-Wide Average	96. 91	Caution. Exceeds the 20-day statutory appeal limit.

The data shows that appealing a delay at the Department of Defense is likely to result in further delay. In contrast, DHS processes appeals in an average of 12 days, making it a highly tool to force a “remand” order that compels the component office to act.

The OGIS Pivot

The Office of Government Information Services (OGIS) serves as the federal FOIA Ombudsman. In FY 2024, OGIS handled over 6, 000 requests for assistance. Engaging OGIS does not stop the statutory clock or extend your deadline to file a lawsuit. It is a parallel track. For constructive denial, OGIS mediation is frequently limited. They can inquire about the status cannot force an agency to release records. yet, an OGIS inquiry creates an official government record of the delay, which can be evidence of “bad faith” or widespread failure in subsequent litigation. Use OGIS when you are not ready to sue want to escalate pressure beyond the agency’s FOIA Public Liaison.

The “Still Interested” Purgatory

Agencies use “Still Interested” letters to purge backlogs. After months of silence, you may receive an email asking if you still want the records. If you do not respond within a short window (frequently 10 to 30 days), they administratively close your request. This is a trap. Always respond immediately: “I remain interested in the release of these records.” Failure to respond to this inquiry counts as a voluntary withdrawal, stripping you of your appeal rights and your ability to sue for constructive denial. You must treat every “Still Interested” letter as a soft denial requiring immediate action.

Litigation as the Escalator

If the administrative appeal for constructive denial is ignored for 20 working days, or if the agency affirms the delay (a rare occurrence), you have “exhausted” all remedies. At this point, the only remaining lever is a lawsuit. In FY 2024, the government spent $54 million defending FOIA lawsuits. Agencies are risk-averse; frequently, the mere filing of a complaint prompts the agency to release documents to moot the case and avoid paying your attorney fees.

The Ombudsman Option: Leveraging OGIS for Dispute Resolution

When an agency stonewalls a perfected request, either through silence, dubious fee estimates, or vague “unusual circumstances” delays, you possess a non-litigious escalation route: the Office of Government Information Services (OGIS). Operating within the National Archives and Records Administration (NARA), OGIS serves as the federal FOIA Ombudsman. While OGIS absence the statutory authority to compel an agency to release records, its mediation process creates an official administrative record of agency non-compliance. This paper trail is invaluable if you eventually proceed to litigation. More importantly, OGIS intervention frequently dislodges requests stuck in low-level bureaucratic queues by elevating the inquiry to agency Public Liaisons.

The Distinction Between Facilitation and Mediation

OGIS classifies its dispute resolution services into two tiers. Understanding this distinction is important for managing expectations. * Facilitation (Informal): The vast majority of OGIS cases fall under this category. OGIS staff contact the agency’s FOIA Public Liaison to inquire about the status of a request, clarify the scope, or explain the agency’s position to the requester. This is frequently enough to break a logjam caused by simple negligence or miscommunication. * Mediation (Formal): This is a structured process used for complex disputes, such as fee waiver denials or specific exemption challenges. It involves substantive negotiation between the requester and the agency, guided by an OGIS facilitator.

By the Numbers: OGIS Performance Metrics (FY 2020, 2024)

Recent data indicates a system under functioning with high throughput. In Fiscal Year 2024, OGIS received 6, 057 requests for assistance, a sharp increase from the 5, 536 requests received in FY 2023. even with this volume, the office maintained processing times.

Table 10. 1: OGIS Caseload and Processing Metrics (FY 2023, 2024)

Metric	FY 2023	FY 2024
Requests for Assistance Received	5, 536	6, 057
Cases Closed	5, 470	6, 098
Acknowledged within 10 Days	98. 4%	88. 5%
Closed within 90 Days	98. 5%	98. 9%

Analyst Note: The high closure rate within 90 days (98. 9% in FY 2024) suggests that OGIS resolves most inquiries through rapid facilitation, providing status updates or explanations, rather than prolonged formal mediation. Do not expect a months-long negotiation; expect a quick, definitive check on the agency’s processing logic.

Procedural Steps to File a Request for Assistance

You may seek OGIS assistance at any stage of the FOIA process, it is most after you have attempted to contact the agency’s FOIA Public Liaison without success. 1. Prepare the Case File: You must compile a single PDF package containing: * The initial FOIA request (with the date stamp). * The agency’s acknowledgment letter (with the perfected tracking number). * Any adverse determination letters (denials, fee estimates). * Copies of your correspondence with the agency’s Public Liaison. 2. Draft the Narrative: Briefly describe the dispute. Focus on procedural failures rather than the content of the records. * Valid Dispute: “The agency has failed to provide an Estimated Date of Completion (EDC) even with my request on [Date], in violation of OGIS Advisory Opinion 2020-01.” * Invalid Dispute: “I believe the agency is hiding aliens.” 3. Submit the Request: * Email: `ogis@nara. gov` (Preferred method). * Subject Line: “Request for Assistance: [Agency Name], [Tracking Number]” * Consent: You must include a signed consent statement authorizing OGIS to discuss your case with the agency. OGIS provides a specific Privacy Act consent form for this purpose.

Strategic Application of Advisory Opinions

Although OGIS issued no new advisory opinions in FY 2023 or FY 2024, its historical opinions remain binding guidance for best practices. You should cite these opinions in your complaint to force agency compliance. * Advisory Opinion 2020-01: This is your primary weapon against silence. It states unequivocally that agencies must provide an Estimated Date of Completion (EDC) upon request. If an agency refuses to give you a date, or gives a vague “we are working on it,” cite this opinion in your OGIS filing. * Advisory Opinion 2018-01: This opinion addresses communication breakdowns. It emphasizes that agencies must communicate with requesters to clarify scope before rejecting a request as overly broad.

The Litigation Clock Warning

serious WARNING: Engaging OGIS does not stop the statutory clock for filing an administrative appeal or a lawsuit. * Appeal Deadline: If an agency denies your request, you have 90 days to file an administrative appeal. Contacting OGIS does not extend this 90-day window. You must file your appeal to preserve your rights, even if OGIS mediation is ongoing. * Litigation Bar: OGIS generally cannot assist with a request once a lawsuit has been filed in federal court. If you sue, OGIS closes your case immediately.

When to Skip OGIS

Do not use OGIS if you require immediate results for a breaking news pattern. While, the intake and assignment process can take 1-2 weeks. If you have a “expedited processing” denial that is time-sensitive, an immediate administrative appeal is the faster procedural step. OGIS is best reserved for “stuck” requests where the agency has gone silent or is making unreasonable fee demands that do not require immediate judicial intervention.

The “No Records” Determination: Forensic Analysis of Search Adequacy

A “No Records” response is rarely a statement of fact; it is frequently a statement of effort. In Fiscal Year 2024, federal agencies closed nearly 47% of the 1. 5 million processed requests for “procedural or administrative” reasons, a category that heavily obscures search failures under the guise of non-existence. When an agency asserts that no responsive documents exist, they are legally claiming that a “reasonable search” calculated to uncover relevant documents was performed and yielded nothing. You must not accept this claim on faith. Instead, you must use the agency’s own portal metadata to prove that their search was cursory, misdirected, or legally insufficient.

20-Point Forensic Fan-Out: Diagnosing the “No Records” Response

1. What is the “No Records” legal standard? The agency must prove it conducted a search “reasonably calculated to uncover all relevant documents.” It does not have to find every document, it must look where they are likely to be.	2. Does “No Records” mean the file doesn’t exist? No. It frequently means the specific keyword query used by the analyst returned zero hits in the specific database they chose to query.
3. What is the “Velocity of Denial”? The time elapsed between “Request Perfected” and “Request Closed.” A duration of under 48 hours for a complex topic suggests no substantive search occurred.	4. How does the “Track” assignment affect search depth? If your request was assigned to the “Simple” track, the agency likely only searched a central index, not individual custodian emails.
5. Can portal timestamps prove negligence? Yes. If a request is closed at 9: 05 AM after being opened at 9: 00 AM, it is physically impossible for an analyst to have queried complex archives.	6. What is a “Glomar” response? A refusal to confirm or deny existence. This is distinct from “No Records” and requires a national security or privacy justification.
7. Do agencies log search terms in the portal? Rarely visible to the user, the absence of search notes in the release letter is grounds for appeal.	8. What does “Referral” metadata indicate? If the portal shows no “Referral” or “Consultation” steps for a multi-agency topic, the search was too narrow.
9. How does American Oversight v. HHS (2024) help? The D. C. Circuit ruled that a search is insufficient if it fails to use “obvious alternative terms.” cite this if they only searched your exact phrasing.	10. What is the “Custodian” gap? If the agency did not task specific individuals (custodians) likely to have the records, the search is legally insufficient.
11. Can I appeal a “No Records” determination? Yes. It is the most common successful appeal type. You must attack the adequacy of the search, not the existence of the documents.	12. What is the “Date Cut-off” trap? Agencies frequently only search records up to the date the request was received. If the event happened after, they find nothing.
13. How do I spot a “Database vs. File” error? If you asked for data and they searched for PDFs, the search format was improper. CareSet investigations reveal agencies frequently claim “no records” when they simply refuse to query a database.	14. What is “Fee-Related” closure masquerading as “No Records”? Sometimes agencies close a request because they estimate high fees, mark it as “No Records” to avoid the fee correspondence.
15. Does the “Estimated Date of Completion” (EDC) matter? If the EDC jumped from “TBD” to “Closed” instantly, it indicates a triage rejection rather than a search.	16. How does “Record Destruction” appear? Agencies must follow General Records Schedules (GRS). If they claim records were destroyed, demand the specific GRS citation and destruction log.
17. What is the “Wrong Office” defense? Agencies frequently search the main FOIA office fail to task the specific sub-component (e. g., searching DHS HQ instead of ICE).	18. Can I request the search notes? Yes. In your appeal, explicitly request the “search worksheets” or “analyst notes” that document the negative search.
19. How does the 2024 DOJ report affect this? With 1. 5 million requests, agencies are using automation to close cases. “No Records” is a volume-management tool.	20. What is the “Boilerplate” indicator? If the “No Records” letter is identical to the portal status update text, no human likely drafted a specific response.

Analyzing Portal Metadata for Search Adequacy

The agency portal is a chain of custody log. When an agency claims they found nothing, you must audit the digital footprint of their attempt. In 2024, the Department of Justice reported that nearly half of all requests were closed without a substantive release. To challenge this, you must correlate the Processing Track, Time-to-Close, and Tasking Logs.

1. The Time-to-Close gap
A proper search involves: reading the request, determining search terms, identifying custodians, tasking those custodians, waiting for their return, and reviewing the results. This process takes weeks. If your portal account shows a status change from Processing to Closed: No Records within 24 to 72 hours, the agency likely performed a “centralized index search” rather than a “custodian search.”

Investigative Action: In your appeal, cite the timestamp delta. “The agency closed this request 26 hours after perfection. It is administratively impossible to task subject matter experts and review their email archives in this timeframe. This suggests an improper reliance on a central index.”

2. The “Simple” Track Classification
Agencies categorize requests into “Simple,” “Complex,” and “Expedited” tracks. The “Simple” track is reserved for records that are already located or easily retrieved. If your request for “all communications regarding Project X” was placed in the “Simple” track and then closed with “No Records,” the agency pre-determined the outcome. They treated a complex search as a simple retrieval, failed to find the file in the easy spot, and stopped looking.

3. Missing Tasking Orders
Advanced portals (like the FBI’s FOIPA portal or DHS’s FOIAonline legacy data) sometimes list “Tasking” or “Referral” steps. If you requested records involving a specific operation (e. g., “Operation Sentinel”), and the portal shows no sub-tasking to the relevant division (e. g., “Criminal Investigative Division”), the search was fatally flawed. Under American Oversight v. HHS (2024), agencies must look where records are likely to be. Failure to task the obvious component is a reversible error.

Constructing the “Adequacy of Search” Appeal

When you receive a “No Records” determination, you must file an administrative appeal within 90 days. Do not that the documents must exist; that the search was insufficient based on the evidence.

The “Obvious Alternative Terms” Argument
Agencies frequently search only for the exact string provided. If you requested “emails regarding the ‘Green Initiative’,” they might search for “Green Initiative” and find nothing, ignoring “Green Project” or “Environmental Initiative.” The D. C. Circuit’s 2024 ruling in American Oversight v. HHS explicitly states that agencies cannot ignore “obvious alternative terms.”

The “Improbable Absence” Argument
If you have a public record (a news article, a press release, or a congressional testimony) that

The “Grant in Full” Mirage

Receiving a “Grant in Full” notification is not the end of the FOIA process; it is the beginning of a race against digital decay. In the modern federal, agencies no longer mail CDs or paper stacks. Instead, they provision temporary, secure download links via proprietary portals, primarily FOIAXpress (Public Access Link or PAL) and the emerging NextGen systems. These links are volatile. They carry strict expiration timers, download count limits, and security wrappers that can render data inaccessible if not handled immediately.

The decommissioning of the centralized FOIAonline portal on September 30, 2023, fractured the release ecosystem. Data that was once permanently archived in a shared repository resides in decentralized agency silos, most of which are managed by Tyler Technologies’ FOIAXpress. This fragmentation shifts the load of archival entirely to the requester. If you fail to extract the data within the agency’s specific window, the case is administratively closed, and you must file a new request, and pay new fees, to get the same records again.

Navigating FOIAXpress and PAL Architectures

Tyler Technologies’ FOIAXpress, used by agencies like the Department of Justice, Department of Education, and Customs and Border Protection, controls the vast majority of federal releases. The public-facing component, the Public Access Link (PAL), operates on a “retrieval token” system. When a request is processed, the system generates a unique URL sent via email.

serious Vulnerability: These links frequently expire after 7 to 30 days, depending on agency configuration. also, portals enforce a “download count” limit, frequently set to three or five attempts. If your connection drops during a 5GB transfer and you retry three times, the system locks the file. You must then petition the FOIA Public Liaison to reset the token, a process that can take weeks.

Protocol for Large- Extraction

For releases exceeding 1GB, agencies rarely provide a single file. Instead, the portal splits the data into multi-part ZIP archives (e. g., Release_Part1. zip, Release_Part2. zip).

• Do not unzip immediately: You must download every segment before attempting extraction. Missing a single 100MB chunk frequently corrupts the entire archive structure.
• Verify file size: Compare the “reported size” in the portal metadata against the “downloaded size” on your disk. A gap of even 1KB indicates a failed transfer.
• Screenshot the manifest: Immediately capture the portal screen showing the file list and file sizes. If the files are corrupt, this screenshot is your only proof that the agency failed to provide usable records, grounding your administrative appeal.

The NextGen Interoperability Gap

Following the Department of Justice’s 2024 guidelines on interoperability, agencies are slowly migrating to “NextGen” portals that integrate with FOIA. gov. While these systems pledge better tracking, they introduce new extraction blocks. NextGen portals use JavaScript containers that prevent direct “Right-Click -> Save As” operations.

The “Interim” Trap: NextGen systems frequently mark cases as “Closed” once an interim release is posted. If you requested 10, 000 pages and the agency releases 500 pages as an “interim” batch, the portal may auto-close the ticket. You must manually check the “Case Status” field. If it reads “Closed” you absence the full dataset, you have 90 days to file an appeal arguing “Constructive Denial” of the remaining records.

Data Integrity and Format Sanitization

Agencies use automated tools to scrub metadata before release. In doing so, they frequently break the files.

Common File Integrity Failures in Federal Portals (2024-2025)

File Type	Agency Method	Requester Risk	Remediation
Excel (. xlsx)	Converted to PDF or “Flattened” CSV	Loss of formulas, hidden columns, and pivot tables.	Appeal immediately citing “failure to provide records in native format.”
Email (. pst)	Converted to PDF Portfolio	Attachments become unsearchable images; header metadata is stripped.	Request “load files” (DAT/OPT) for eDiscovery re-assembly.
PDF	“Secure” Wrapper	File requires a password or certificate to open; prevents OCR text extraction.	Demand a “clean” copy; 508 Compliance requires accessible text.
Video	Downsampled Transcoding	Resolution drops to 480p; timestamps become illegible.	Specify “original resolution” in the initial request.

Security Gates: Login. gov and 2FA

As of 2024, agencies including the Bureau of Consumer Financial Protection and the Small Business Administration mandate Login. gov authentication for their FOIA portals. This adds a of Two-Factor Authentication (2FA). While this secures your request history, it breaks automated scraping scripts. If you manage requests for a newsroom, not share a generic “foia@newsoutlet. com” password. Each reporter must have a verified identity linked to the specific case number.

Technical Warning: Never use a personal email address for Login. gov if you are filing on behalf of an organization. If you leave the organization, the FOIA requests tied to your personal identity cannot be legally transferred to a colleague. Always use an organizational email that you control.

The “Fees” Gate

Portals like FOIAXpress have a hard-coded “Fee Gate.” Even if you have a fee waiver, the system may erroneously assign a $0. 00 invoice that must be “paid” (processed) before the download link activates. If you see a “Payment Pending” status on a granted request, do not wait. This is a system error. Contact the agency liaison immediately. The clock for your download window frequently starts ticking when the status changes to “Payment Pending,” not when you actually resolve the glitch.