How Long Does a FOIA Request Take?

Quick answer

• A federal agency ordinarily must determine whether it will comply with a perfected FOIA request within 20 working days after the proper component receives it. Saturdays, Sundays, and legal public holidays are excluded. The current FOIA statute states the timing rule.
• The 20-working-day rule is not a guaranteed production date. A determination must communicate the agency’s decision, reasons, appeal rights when applicable, and access to assistance; records the agency agrees to release must then be made promptly available. Read the determination and production provisions in the statute.
• An agency may give written notice of unusual circumstances and extend the ordinary period by up to 10 working days. If it needs longer, it must offer a chance to narrow the request or arrange an alternative time frame and make the FOIA Public Liaison available. See the statutory extension procedure.
• Real processing time varies by agency component and track. In its FY 2025 report, the Department of Justice reported an agency-wide median of 6 days for processed simple requests and 53 days for processed complex requests. Those figures describe completed DOJ cases, not a promise for a new request. Check DOJ’s FY 2025 response-time table.
• A request expected to take longer than 10 days should receive an individualized tracking number, and the agency’s status service must provide the received date and an estimated completion date. The tracking requirements appear in the FOIA statute.
• Expedited processing does not mean delivery within 10 days. The agency must decide whether to grant expedition within 10 calendar days, then process an approved request as soon as practicable. Review the expedited-processing provision.

The honest answer to “how long does a FOIA request take?” is therefore two-part. The legal framework creates an early decision deadline, while actual record production may take days, months, or longer depending on the office, request, queue, searches, consultations, and review. A useful estimate starts with the correct agency component’s data and your request’s assigned track, not a government-wide slogan.

This guide focuses on timing after submission. Use the federal FOIA filing guide for the full filing process, the FOIA request form guide to choose the correct intake route, and the annotated FOIA request example to draft a searchable records description.

What does the 20-working-day FOIA deadline actually require?

The ordinary deadline requires the agency to make a determination about whether it will comply with the request and to notify the requester. It does not require every responsive page to arrive within that period. This distinction explains why an acknowledgment can arrive quickly, a determination can follow later, and production can continue after that.

The statute requires the notice to state the agency’s determination and reasons. It also requires notice of appeal rights for an adverse determination and access to the agency’s FOIA Public Liaison. If the agency decides to comply, the statute says the records must be made promptly available. The operative requirements are in 5 U.S.C. section 552(a)(6).

“Determination” has more substance than “we received your request.” A receipt email or tracking number is an acknowledgment. It proves intake and gives you a case reference, but it may not say whether records will be released, withheld, referred, or produced in stages. Treat those documents as different events in your log.

The word “response” causes confusion because people use it for all of these events. When you ask an agency for status, name the event you mean: acknowledgment, initial determination, first production, next installment, or final production. A precise question is more likely to produce a usable answer.

When does the FOIA clock start?

The ordinary period begins when the appropriate agency component receives a perfected request that follows the agency’s published rules. If a designated receiving component gets a properly made but misdirected request, the statute says the clock begins when the proper component receives it, but no later than 10 days after the designated component first received it. The routing and commencement rule appears in the FOIA statute.

A “perfected” request is one the office can process under its rules. A request may not be treated as perfected if it does not reasonably describe the records, goes to a channel the regulations do not accept, or omits information the published procedure requires. DOJ’s requester guidance, for example, says a request must be written, reasonably describe the records, and supply component-specific required information. Review DOJ’s current intake requirements.

Do not assume that a portal timestamp and the statutory start date are always identical. Compare the confirmation with the acknowledgment. If the dates differ, ask which component received the request, when the office considered it perfected, and what rule explains any gap. Save the answer rather than trying to reconstruct it months later.

How do you count FOIA working days?

Count forward from receipt by the appropriate component while excluding Saturdays, Sundays, and legal public holidays. The statute uses those exclusions for the ordinary determination period. See the exact time-limit language.

Do not substitute your employer’s business calendar or an agency office-closure assumption. After the lapse in appropriations during 2025, DOJ’s Office of Information Policy explained that annual-report calculations still include days other than Saturdays, Sundays, and legal public holidays, even though furloughed staff could not process requests during the shutdown. Read OIP’s November 18, 2025 guidance.

For a live request, the safest method is to record the component’s received date and ask the office to confirm any extension or tolling. A homemade calendar can help you spot a question, but the correspondence shows what the agency believes happened to the clock.

Why can actual FOIA production take longer than 20 working days?

Actual production can take longer because locating and reviewing records is separate from making the initial determination, and because FOIA expressly recognizes searches in remote facilities, large record volumes, and consultations. Component backlogs and processing tracks also affect when staff reach a request.

The statutory definition of unusual circumstances covers three operational situations: records must be collected from field facilities, a single request demands a voluminous amount of separate records, or consultation is needed with another agency or multiple components. The three categories are listed in the FOIA statute. An agency invoking them must connect the extension to the particular request rather than treating “busy office” as a magic phrase.

Several ordinary tasks can add time without changing the requester’s underlying right to a decision:

• Staff identify custodians, record systems, search terms, and date ranges.
• Program offices search email, shared drives, case systems, paper holdings, or archived material.
• The FOIA office removes duplicates and reviews responsiveness.
• Specialists review classified, law-enforcement, privacy, confidential business, privilege, or other potentially exempt material.
• Another component or agency may need to consult on records in which it has a substantial interest.
• The office may make rolling productions while review continues.

The requester’s scope affects nearly every task on that list. DOJ tells requesters that small-volume requests can often enter a simple track, while requests requiring line-by-line review of hundreds or thousands of pages may take longer. DOJ describes this processing difference in its current requester guide. That is not a reason to abandon needed records. It is a reason to define the smallest record set that answers the research question.

What is multitrack processing?

Multitrack processing allows an agency to place requests in different queues based on the work or time involved. The statute permits agencies to create these systems by regulation and to offer a requester the chance to narrow a slower-track request so it can qualify for faster processing. See the multitrack authority in the statute.

Track names and thresholds are agency-specific. “Simple” does not mean unimportant, and “complex” does not mean invalid. The label estimates processing effort. Ask what made the request complex: the number of custodians, estimated pages, consultations, sensitive review, record format, or another published factor. You can then decide whether a narrower first phase preserves your objective.

Do not compare your complex request with an agency’s simple-track median. Those are different populations. Also avoid comparing a request at one component with a department-wide average. Large departments contain offices with very different records, staffing, intake volume, and review duties.

How can you estimate a realistic FOIA completion time?

Use three layers of evidence: the agency component’s recent annual-report data, your assigned processing track, and a case-specific estimated completion date. No single layer is enough by itself.

Federal agencies publish annual FOIA reports with median and average processing times, ranges, pending-request ages, backlog counts, and track-specific data. The statute requires agencies to report median days for different request types and other response-time measures. See the annual-report data requirements. FOIA.gov and agency report pages make those data available for comparison.

Start with the median, not only the average. A small number of very old cases can pull an average upward. Then read the range and pending-age table to see how wide the distribution is. A median describes the middle completed case in a historical group; it does not predict your exact position or account for a new backlog shock.

The DOJ FY 2025 report shows why component and track matter. Across DOJ, processed perfected requests had a median of 6 days in the simple track, 53 days in the complex track, and 7 days in expedited processing. The same table shows component results that differ sharply from those department-wide figures. Use DOJ’s official FY 2025 response-time table. These are retrospective processing measures for cases closed during that fiscal year, not statutory substitutes or service guarantees.

Government-wide demand also supplies context. OIP’s FY 2025 summary reports that agencies received 1,707,197 FOIA requests and processed 1,635,055 during that fiscal year. It also reports that receipts rose 13.7% from the prior fiscal year. Read OIP’s July 2, 2026 summary. Those totals show system scale, but they cannot tell you how long a request to a specific office will take.

Build an estimate in this order:

1. Confirm the processing office. Match the tracking number and acknowledgment to the agency component that actually controls and processes the request.
2. Reconstruct the timing record. Record submission, receipt, perfection, acknowledgment, tolling, extension, scope change, determination, and production dates separately.
3. Check the processing track. Ask whether the request is in a simple, complex, expedited, or other published track and whether narrowing could move it.
4. Request a useful status update. Use the tracking number to ask for the received date, current stage, outstanding issue, and estimated completion date.
5. Resolve a defined blocker. Answer a reasonable clarification or fee question, or negotiate a documented scope change that preserves the records you need.
6. Escalate deliberately. Contact the FOIA Public Liaison, seek OGIS assistance, or obtain qualified legal advice without losing an appeal or litigation deadline.

This process produces a range, not certainty. An estimate may change when a search finds more records than expected, a consultation expands, a fee issue pauses work, or another review becomes necessary. OGIS advises agencies to explain that an estimated completion date is an estimate rather than a guarantee. See the OGIS recommendations table.

Can the agency stop or extend the clock?

Yes, but extension and tolling are different. An extension adds time for specified unusual circumstances. Tolling pauses the running period while the agency awaits particular information or fee clarification.

The statute permits one tolling request for information reasonably needed from the requester. It also permits tolling when necessary to clarify fee-assessment issues, and the clock resumes when the agency receives the requester’s response. Review the tolling language in the FOIA statute. OIP’s implementation guidance explains that the numerical one-request limit applies to information clarification, while necessary fee clarification may occur more than once. Read OIP’s tolling guidance.

An unusual-circumstances notice must be in writing, state the circumstances, and give the expected dispatch date. The notice ordinarily cannot specify an extension longer than 10 working days. If the request still cannot be processed within the extended period, the agency must offer an opportunity to limit scope or arrange an alternative time frame and must make the FOIA Public Liaison available. See the full procedure in the statute.

Read every clarification request promptly. Answer the exact question and preserve the original and revised scope. If the office asks for undefined “more detail,” ask what record system, custodian, date range, or record category would make the search workable. Do not silently rewrite the request so narrowly that it no longer answers your research need.

Does a backlog automatically qualify as unusual circumstances?

No. The statute’s unusual-circumstances definition lists remote searches, voluminous records, and consultations. Predictable agency workload is not automatically an exceptional circumstance in court unless the agency also demonstrates reasonable progress in reducing its backlog. The distinction appears in the FOIA statute.

Backlog still matters as a practical predictor. OGIS notes that delays are a reality for many offices and recommends that requesters retain the acknowledgment and tracking number, monitor status, and contact the Public Liaison when concerned. Read OGIS requester best practices. The point is to separate a practical explanation from the legal procedure the agency must follow.

Will narrowing a FOIA request make it faster?

It can, when the change reduces identifiable processing work and preserves the records that matter. A useful narrowing agreement targets a defined cost driver such as custodians, date range, record type, office, search term, or production sequence. “Please hurry” is not a scope change.

Ask the processor which element placed the request in its current track. If the answer is a broad date range across many offices, consider a first phase covering the program office and final records. If the answer is consultation on attachments, ask whether non-consultative records can be released first. If the answer is a large email set, discuss named custodians and objective search terms.

OGIS recommends using an estimated-completion-date discussion to explore whether narrowing could produce an earlier estimate. It also recommends that agencies use average processing times for simple and complex requests when developing estimates. See OGIS’s assessment recommendations. A narrowing conversation is therefore most useful when it connects a specific edit to an updated track or estimate.

Does expedited processing guarantee a fast FOIA response?

No. Expedition changes priority, but it does not create a guaranteed record-delivery date. The agency must decide whether to grant expedited processing within 10 calendar days and must process an approved request as soon as practicable. The statute states both obligations.

The statutory compelling-need standards cover an imminent threat to an individual’s life or physical safety, or an urgency to inform the public about actual or alleged federal government activity when the requester is primarily engaged in disseminating information. The requester must certify the supporting statement as true and correct to the best of their knowledge and belief. Agencies may establish additional grounds in their regulations. Review all expedition criteria in the statute.

Do not claim expedition only because the ordinary queue is inconvenient. DOJ says a court deadline alone will not normally qualify under its regulations. It publishes additional DOJ-specific grounds, including potential loss of substantial due process rights and a defined category of exceptional media interest involving government integrity. Read DOJ’s current expedited-processing guidance.

Keep the decision on expedition separate from the underlying request. A denial of expedition is not necessarily a denial of access to the records. Read the notice for appeal instructions and continue tracking the ordinary request unless the agency says otherwise.

How should you ask for FOIA status and an estimated completion date?

Use the individualized tracking number and ask a short set of operational questions. The statute requires a tracking system for a request expected to take longer than 10 days and requires the status service to provide the original received date and an estimated completion date. See the tracking and status provisions.

A useful status message can ask:

• Which component is processing the request, and what received date does it use?
• Is the request perfected, or is any information still required from the requester?
• Which processing track applies, and what factor determined that track?
• Has any tolling period, unusual-circumstances extension, referral, or consultation been recorded?
• What is the current estimated completion date, and does it refer to a determination, first production, or final production?
• Could a defined narrowing or staged release materially change the estimate?

Avoid sending the same request again as a status tactic. Duplicate cases can create routing confusion and more correspondence. If the portal does not show useful detail, contact the Requester Service Center listed in the acknowledgment. If routine contacts do not resolve the issue, the FOIA Public Liaison is the next agency-level resource.

An estimated completion date is not a guarantee. OGIS recommends that agencies provide one on request, explain its limits, refresh it when an earlier estimate passes, and place delay in context with queue data. Review the OGIS best-practice table. Ask for the assumptions behind the date so you can understand a later revision.

What can you do when a FOIA request is overdue?

First, verify that the applicable period actually started and identify what is overdue. A missing acknowledgment, missed determination date, passed production estimate, and ignored appeal are different problems. The remedy and contact may differ.

Use a staged response:

1. Send a concise status request with the tracking number, received date, requested scope, and the specific event you are waiting for.
2. Ask for the current estimated completion date and whether any tolling, extension, consultation, referral, or scope issue affects it.
3. Contact the component’s FOIA Public Liaison if ordinary status channels do not produce a clear answer. The statute assigns the liaison a dispute-resolution role during extended processing. See the liaison requirement.
4. Seek help from the Office of Government Information Services when direct efforts fail. OGIS describes itself as the federal FOIA ombudsman and recommends contacting it after unsuccessful efforts to reach the agency liaison. Read OGIS requester guidance.
5. Read every determination for its own administrative-appeal deadline. For an adverse determination, the statute requires an appeal period of at least 90 days. The appeal-notice rule is in the FOIA statute.
6. Get qualified legal advice before relying on constructive exhaustion, filing suit, or making a litigation decision. The statute addresses missed time limits, exceptional circumstances, and judicial review, but their application depends on the record and procedural posture. Review the statutory text rather than treating delay as an automatic court victory.

Do not let a productive status conversation erase formal rights. A liaison discussion or OGIS mediation can help clarify scope and timing, but it may not suspend an appeal deadline in an adverse determination. Record dates, keep the original notices, and ask a qualified attorney about consequential choices.

What delay records should you preserve?

Keep the submitted request, portal confirmation, acknowledgment, tracking number, scope clarifications, fee correspondence, extension notices, status messages, estimated dates, productions, and determination letters. Save the files outside the portal as searchable documents.

Maintain a small event log with separate fields for agency receipt, perfection, tolling start and end, extension, revised scope, determination, each production, appeal, and agency reply. This avoids the common failure of calling every communication a “response.” It also lets a liaison, mediator, or attorney see the sequence without reconstructing it from an inbox.

For rolling productions, keep an inventory by installment. Record the cover-letter date, file names, stated page count if the agency supplies one, redaction labels, referrals, and whether the letter calls the release interim or final. Do not assume silence after an installment means the request is closed.

Which timing mistakes cause avoidable FOIA delays?

The most preventable delays come from routing, scope, proof, fees, and poor recordkeeping. None of these guarantees a fast result, but correcting them removes uncertainty the requester can control.

• Wrong component. A department name may hide several FOIA offices. Use the Federal Data agency directory as an orientation tool, then follow the component’s current official instructions.
• An unsearchable request. A question about why government acted may not identify existing records. Name record types, likely offices, objective identifiers, and a bounded period.
• A request for every possible record. Broad wording can expand custodians, systems, duplicates, review, and consultations. Ask only for material that changes the research answer.
• Missing identity or consent procedure. Requests for records about yourself or another person may remain unperfected until the agency receives required verification through the correct channel.
• Ignored fee correspondence. The statute permits tolling for necessary fee clarification. Answer promptly and keep the exchange. See the fee-tolling provision.
• Duplicate submissions. Multiple copies through different channels can create parallel cases rather than priority.
• Vague status demands. Ask for the component, received date, track, current stage, outstanding issue, and estimated completion date.
• Unrecorded narrowing. A phone agreement that is not confirmed in writing can create later disagreement about what the agency searched.

Specificity has a boundary. Do not invent custodians, systems, or search terms you cannot support. Ask the FOIA contact what the office calls the relevant program and record series. A precise but wrong restriction can exclude the documents you need more efficiently than a broad request would.

FAQ

Does a federal agency have to release FOIA records within 20 working days?

No. The usual 20-working-day period is for the agency’s determination on the request, not a guarantee that every responsive record will be produced by that date. The statute separates the determination period from prompt production after a decision to comply.

Do weekends and federal holidays count toward the FOIA deadline?

No. The statute excludes Saturdays, Sundays, and legal public holidays when it sets the ordinary response period. Read the statutory time-limit language.

Can an agency extend the FOIA deadline?

Yes. The statute permits written notice of unusual circumstances and an extension of up to 10 working days, with additional procedures when more time is needed. See the unusual-circumstances procedure.

Can I ask for an estimated completion date?

Yes. The agency’s tracking service must provide the received date and an estimated completion date for a request assigned an individualized tracking number. The tracking and status duties appear in the statute.

Does expedited processing guarantee records within 10 days?

No. The agency generally must decide the expedition request within 10 calendar days; a granted request is then processed as soon as practicable. Review the expedition timing rule.

What should I do when my FOIA request is overdue?

Confirm the component and scope, request a written status and estimated completion date, contact the FOIA Public Liaison if needed, and consider OGIS assistance or qualified legal advice.

Conclusion

FOIA’s ordinary 20-working-day period is an initial decision framework, not a universal delivery promise. Estimate actual timing from the correct component, the assigned processing track, recent official data, and a case-specific estimated completion date.

When delay occurs, preserve the timeline and ask concrete operational questions. Clarify a real blocker, narrow only when the change preserves your research goal, and use the Requester Service Center, FOIA Public Liaison, or OGIS in sequence. Treat appeal and litigation choices as deadline-sensitive legal decisions rather than automatic consequences of a late response.

Sources

1. FOIA.gov, Freedom of Information Act Statute
2. U.S. Department of Justice, Make a FOIA Request to DOJ
3. U.S. Department of Justice, FY 2025 Annual FOIA Report, Response-Time Tables
4. Office of Information Policy, Summary of FY 2025 Annual FOIA Reports
5. Office of Information Policy, Calculating FOIA Response Times after the 2025 Government Shutdown
6. Office of Information Policy, New Limitations on Tolling the FOIA Response Time
7. Office of Government Information Services, Requester Best Practices
8. Office of Government Information Services, Issue Assessment Recommendations and Best Practices

This guide explains federal FOIA timing using current official sources. It is not legal advice, does not predict a particular agency’s completion date, and does not promise access to any requested record.

Editorial source check: 2026-08-26 · Topic ID: FED-006