The FOIA 20-Day Clock: When Does an Agency Actually Have to Respond?

You file a Freedom of Information Act request and read that the agency has "20 days" to respond. Three weeks pass, nothing arrives, and you assume the agency is already late. Maybe it is — but probably not, because almost every part of that "20 days" works differently than it sounds. The clock counts business days, it starts later than the day you hit send, and "respond" does not mean the documents land in your inbox.

It's 20 business days, not 20 calendar days

The federal FOIA statute gives an agency 20 business days to make a determination on a request — weekends and federal holidays are excluded from the count. That single distinction is worth roughly a week of real time. Twenty business days from a request filed in early November, with Veterans Day and Thanksgiving in the window, can land deep into December on the wall calendar. Eyeballing "about three weeks" is how requesters convince themselves an agency is overdue when it isn't, and how agencies miss a date they thought they had more room on.

That's the default the FOIA Statutory Response Timer uses: it adds 20 business days to your start date and skips weekends and U.S. holidays, so the deadline you read is the one the statute actually sets rather than a calendar-day estimate.

Day zero is not the day you filed

Here is the trap that catches even experienced requesters. The 20-day clock does not necessarily start when you submit the request. Under the statute, it starts when the request is received by the proper component of the agency that maintains the records — and the law allows up to 10 business days for a misdirected request to reach that component before the clock is deemed to start. A request emailed to a giant department's general FOIA office may sit in routing for days before the right field office "receives" it for clock purposes.

The practical lesson is to pin your start date to the day the correct office acknowledges receipt, not the timestamp on your outbox. When you use the calculator, set the start date to the agency's stated date of receipt if you have it — that's the day-zero the deadline is measured from.

"Respond" doesn't mean "produce the records"

The most common misunderstanding is what the agency actually owes you on day 20. The statutory deadline is for a determination — a decision about whether the agency will comply with the request, which records it will release, the scope of any withholdings, the fees involved, and your right to appeal. Courts have made clear that a determination is not the same as handing over every page. An agency can meet the 20-day deadline by telling you it will release responsive records and is gathering them, then produce the documents on a reasonable rolling basis afterward.

So a response that arrives on day 20 saying "we're granting your request and will produce records on a rolling schedule" is, legally, on time — even if the actual files take months. Knowing the determination date matters because it's the date that triggers your right to treat silence as a constructive denial and, eventually, to sue.

The 10-day extension and other stretchers

The 20-business-day figure is a floor, not a ceiling, because the statute builds in ways to extend it:

• Unusual circumstances. In defined situations — needing to search field facilities, processing a voluminous request, or consulting with another agency — the agency may extend the deadline by up to 10 additional business days with written notice. For very large requests it may negotiate even longer or ask you to narrow scope.
• Tolling. The agency can stop the clock once to ask you a reasonable question to clarify the request, and can stop it as often as needed to resolve fee issues. The clock resumes when you respond.
• Expedited processing runs the other way: if you show a compelling need, the agency must decide whether to grant expedited treatment within 10 calendar days, and granted requests move to the front of the queue.

If your agency has invoked the unusual-circumstances extension, just change the day count in the calculator to 30 business days to see the new outside date. The math — skipping weekends and holidays — stays the same.

State public-records laws are a different animal

Federal FOIA only governs federal agencies. Every state has its own public-records or "sunshine" law, and they vary wildly: some give a set number of business days, some use calendar days, some demand only a "prompt" or "reasonable" response with no fixed count, and the start triggers differ. Because the timer lets you set the number of days and toggle between business and calendar days, you can model a state statute's clock just as easily as the federal one — enter the request date, set the count your jurisdiction requires, and pick the right day type.

Read the real deadline off the request date

None of this is hard arithmetic once you separate the questions: which date the clock starts on, how many days the statute gives, whether they're business or calendar days, and whether an extension applies. The FOIA Statutory Response Timer takes the receipt date and the day count, skips weekends and federal holidays for the business-day default, and returns the exact date the agency's response is due — so you know precisely when "they haven't answered" becomes "they're late."

General information, not legal advice. FOIA and state public-records rules change over time and turn on facts specific to your request — confirm any real deadline against the current statute, the agency's regulations, and counsel before relying on it.