bmax

On paper: the federal FOIA statute allows 20 business days, and most state public records laws promise responses in roughly 3–30 days. In practice: some entities respond in days, many take weeks to months, and some don't respond at all until you follow up. We submit public records requests continuously across state, local, and education government — the statutory deadline and the actual timeline are different numbers.

Why the real timeline varies so much

Response time is a function of the entity, not the law. A well-staffed state agency with a records portal might turn a request around in 48 hours. A small school district routes it to someone whose actual job is something else. Extensions, clarification requests, and fee negotiations all restart clocks. None of this is malicious — it's what "public record" actually means operationally: filing cabinets, inboxes, and PDFs released one request at a time.

What that means depending on who you are

• Requesting one document from one entity: budget weeks, follow up politely and persistently, and put the statutory citation in the request.
• Requesting at scale — hundreds or thousands of entities: the timeline distribution is the engineering problem. Submission is easy; tracking, follow-ups, intake, and processing are the system. That's why we built a pipeline for the full lifecycle — automated submission, response tracking, document processing — instead of treating each request as a one-off.

The part nobody prices in

A FOIA response isn't data when it arrives — it's a PDF in an inbox, useful to one person once. The value shows up when responses are processed into structured, queryable records: contract terms, pricing, and the end dates that tell you when an incumbent's deal opens to competition. The waiting is unavoidable; wasting what comes back is optional.

Full write-up on requesting public records at scale: The FOIA Advantage.