How to Request Data From a Federal Agency (October 2026)

To request data from a federal agency you usually file a written request under the Freedom of Information Act (FOIA, 5 U.S.C. 552) for agency records, or a Privacy Act request for records the government holds about you, and you check for a published bulk dataset before filing either. Anyone can file, with no fee to you for the request itself and no requirement to explain why you want the records.

The whole process takes an afternoon of setup, then weeks to months of waiting. Difficulty is low for a narrow request, high the moment you ask for something broad, so the drafting matters more than anything else you do.

• Anyone, anywhere, can request federal agency records. No reason required.
• Search public sources first. Published bulk data is faster and free.
• A request must name the records specifically enough to locate them.
• Agencies have 20 working days to respond; 10 days if you certify expedited processing.
• The first 100 pages and two hours of search time come free.
• Ask for native files and a data dictionary, not PDFs.
• Silence past the deadline is a violation you can escalate.

What You Need

Before you write a sentence, gather seven things. Missing any one of them is the most common reason a request comes back useless.

• The information itself. What specifically are you after? A dataset, a contract, an approval memo, correspondence.
• Identifiers. Case numbers, docket numbers, contract numbers, grant numbers, facility names, program codes.
• Date range. Start and end dates, not “recent.” Give a range you can defend as reasonable.
• Agency or program. The specific office that holds the records, not just the department.
• Delivery format. Native electronic format, and how you want it delivered.
• Deadline and fee position. Your due date and the fee you will pay, capped.
• Your contact details. Name, mailing address, phone, email. A request without them is not a valid request.

Now know which kind of request you are making, because these are genuinely different tools and mixing them up wastes months.

Route	Who files	What it produces	Typical timeline
Published bulk data or API	Anyone	The dataset itself, already released	Immediate
FOIA request	Anyone	Agency records that exist and are not already public	Weeks to months
Privacy Act request	You, about your own records	Records in a system of records about you, amended if inaccurate	Weeks to months
Mandatory Declassification Review	Anyone	Classification review of security records still held	Often longer than FOIA

The difference that trips people up: FOIA reaches records about a subject, such as a contract or a program, and anyone can ask. The Privacy Act reaches records about you personally, and only you can ask for those.

Step-by-Step: How to Request Data From a Federal Agency

Six steps, in order. Skipping step two is the expensive mistake, because a published CSV beats a nine-month request every time.

The statutory clock at a glance

Deadlines are the part requesters remember after the fact, so here is the whole sequence on one screen.

Moment	What happens	Who acts	Your move if it slips
Submission	Request enters the agency’s queue with a docket number	Agency FOIA officer	Keep the confirmation page; no docket means it was not logged
Within 10 working days	Determination on expedited processing if you certified it	Agency	Ask the FOIA Public Liaison to note the request internally
Within 20 working days	Determination on the request itself, with records or a written appeal notice	Agency	Send one dated reminder citing the statutory period
Extra 10 working days	Unusual circumstances extension, valid only with a written notice naming the reasons	Agency	Push for a partial or rolling production while the extension runs
90 days from denial	Administrative appeal to the Chief FOIA Officer, if the notice says so	Agency official	Escalate to the Justice Department Office of Information Policy

One practical warning: the clock runs in working days, which exclude federal holidays, and most agencies count from receipt rather than from the postmark. If your request matters on a deadline, work backwards from that date rather than forwards from the day you sent it.

Step 1: Identify the Agency and Dataset

Start with the office that actually holds the record, which is often narrower than the department name you have in mind. Cabinet departments operate as separate agencies for FOIA purposes, so a request for Internal Revenue Service records goes to the IRS FOIA office, not to the Department of the Treasury.

Four tools narrow an ambiguous ask. Agency FOIA requester statistics show what each office is actually being asked for and what it releases. FOIA reading rooms list what an office has already processed. System of Records Notices, published in the Federal Register, disclose which record systems an agency maintains and where they sit. Program directories identify which sub-office administers a contract, grant or inspection.

If you cannot tell which office holds the records, ask the parent agency with your best guess and request that they either search or refer you to the component that holds the records. Agencies routinely refer requests, which costs you a few weeks but beats six weeks of silence from the wrong inbox.

Step 2: Check Existing Public Data First

Federal open data portals host a great deal of material that used to require a request. Data.gov indexes datasets across agencies, and most large agencies run their own open data pages with bulk downloads and APIs rather than single-row exports.

Check the agency’s FOIA reading room too, which lists recently processed requests and released attachments. Publishing a reading room is a statutory expectation, and reading it tells you the vocabulary the agency uses for the records you want.

Then check the Federal Register for rules, notices and procurement announcements tied to your subject. Archived copies matter here too: public data pages have been taken down in recent years, and an archived snapshot of a portal page is itself evidence of what the agency published and when.

Judge what you find on four points. Is it current enough for your purpose, or is the most recent file two years old? Is it complete, or does it stop mid-series? Is it machine-readable in a stable format with a documented schema? Is the licensing clear enough for republication? A PDF table screenshot fails the third test outright.

Step 3: Define Exactly What You Need

This is where vague requests die. An agency is not obliged to create a record that does not exist, and it is not obliged to do extra analysis or research to answer a question. You are asking for records, so describe records.

Write the specification as a list. Fields: name the columns, categories or document types you want, and say explicitly if you want all of them. Geography: name the states, counties, facilities or jurisdictions. Population: name the group, cohort or case criteria. Unit of analysis: say whether you want one row per person, per case, per transaction or per inspection. Date range: give start and end dates tied to a field you know exists, such as the date of the transaction or the date of the letter.

Then add format. Ask for records in their native electronic format, such as CSV, JSON or a database extract, rather than PDF images. Ask for the accompanying data dictionary, schema documentation or field definitions. Ask for complete record sets rather than samples, and say that partial releases are acceptable on a rolling schedule if that gets you data sooner.

Say what you are excluding when a broad request would drag in irrelevant material. A short exclusion clause often turns a slow search into a fast one.

A worked example shows how much this matters. The vague version: “I want federal contract award data.” That request has no date range, no fields, no geography and no upper limit, and it will be answered, if at all, with a very large fee estimate. The scoped version asks for award notices for a single program code from a stated start date to a stated end date, limited to a named field set, in CSV format with the data dictionary, delivered to a named email address, with fees capped at a low amount and a waiver requested on public-interest grounds. That version is answerable on day one, and it is the difference between a usable file and an invoice.

The same logic applies to document requests rather than datasets. Instead of “emails about the program,” name the sender, the recipient role, the subject line keyword, and the date window. Agencies search far more effectively on narrow combinations, and a narrow request also makes the resulting production easier for you to review.

Step 4: Choose the Correct Request Channel

Each channel has a different job. A FOIA request goes to a FOIA officer, Chief FOIA Officer or the office’s public records team, through its portal, email, mail or fax. A Privacy Act request goes to the agency’s privacy office or records officer, and you should mark it clearly as a Privacy Act request on the envelope and at the top of the document, because a mislabelled request slows down while staff work out which rulebook applies.

Ordinary correspondence suits a question about a program’s rules or a request for a small clarification, and it carries no deadline. That is exactly why it is the wrong tool for records you need on a schedule.

Mandatory Declassification Review is the right route for classified national security records that are still held, where you are asking about the classification itself rather than asking an agency to search for existing documents. It is slower and rarely used for data work.

One more channel worth knowing: program staff and offices that maintain a database sometimes publish extract instructions or accept bulk requests outside the FOIA process. A polite question to the program office can save a formal request, though you lose the statutory deadline that comes with filing one.

Know where the route stops working, because these limits are structural rather than procedural. FOIA reaches federal agency records only, so state, municipal and tribal records fall under separate state open records laws with their own deadlines and fee rules. It does not reach records the agency never created, and agencies are not obliged to compile a dataset, run an analysis or answer a question in their response. And records held solely by a contractor or grantee can sit outside the agency’s custody entirely, which is a genuinely dead end rather than a delay.

Partly for that reason, archiving is now a normal part of the workflow. Several federal datasets and public data pages have been removed or restructured in recent years, so before requesting something you saw online, check an archived snapshot of the page and its files. If the archive shows a dataset that no longer exists on the agency site, that is a strong reason to file, and worth naming in your request.

Step 5: Write a Clear, Trackable Request — How to Request Data From a Federal Agency

Under 5 U.S.C. 552(a)(6), your request has to state your name and contact details, describe the records with reasonable specificity, state your willingness to pay reasonable charges, and give an upper limit on what you will pay. Adding an explicit demand for a response inside the statutory period makes the deadline enforceable rather than arguable.

Use this template and fill in the bracketed parts.

Subject: FOIA Request — [records described in one line]

This is a request under the Freedom of Information Act, 5 U.S.C. 552.

I request copies of the following records: [precise description, with fields, identifiers, geography and date range].

Format: native electronic format, such as CSV or JSON, with the data dictionary or schema documentation, delivered electronically. Rolling productions on a partial schedule are acceptable.

Fee arrangement: I request a fee waiver on the grounds that this information is in the public interest and is available to the public without charge, and I agree to pay up to [your cap] in fees. Please notify me before costs exceed that amount.

Expedited processing: I request expedited processing because [compiled evidence of urgency, such as a published deadline or publication commitment]. I am willing to pay the expedited fee.

Please respond within 20 working days as required by statute. If you intend to invoke unusual circumstances, please provide the written notice and the specific reasons.

Contact: [name, address, phone, email]

Three details carry most of the weight. The fee cap prevents a surprise bill, because agencies generally must give advance notice before they incur charges past a modest statutory threshold. The expedited processing certification puts the agency on a 10-day clock for the decision on your request. The format line stops you receiving scanned PDFs of data that exists as a spreadsheet.

Send it through the agency’s official portal where one exists, since that generates a tracking number automatically. Keep the confirmation page, the acknowledgment letter and every copy you send. Send the same request to only one office at a time; duplicate requests get routed and deprioritized.

Step 6: Follow Up and Verify the Response

An agency must acknowledge a request and respond within 20 working days. If it invokes unusual circumstances, meaning the request is unusually complex because of the volume of records involved, it gets a written extension notice plus ten additional working days, and it must tell you exactly what is taking so long.

Know the exemptions before the response arrives, because most denials are exemption claims rather than “no records” answers. Nine apply under 5 U.S.C. 552(b):

Exemption	What it covers in plain terms
1	Classified national defense and foreign policy information
2	Internal personnel and medical rules, plus some law enforcement techniques
3	Records exempt from disclosure by another statute, where that statute blocks release
4	Trade secrets, plus certain financial and commercial information
5	Inter-agency and intra-agency deliberative material, such as draft recommendations
6	Personnel and medical files, and personnel records where disclosure would be a privacy harm
7	Law enforcement records, where disclosure would interfere with an investigation, reveal a confidential source, or harm someone’s safety
8	Examination, operating or financial reports on financial institutions
9	Geological and geophysical data about oil, gas and minerals

Two ideas matter when a response is withheld. Segregable disclosure means an agency must release the non-exempt parts of a record, so a letter with nine blacked-out lines and one readable paragraph is a partial compliance. A Vaughn index, named after the case that established it, is the list of documents an agency claims are exempt and the exemption claimed for each, and you can challenge individual entries.

Verify before you publish. Check row counts against what the agency said it holds, look for gaps in the date series, confirm the field definitions match your assumptions, and confirm the licensing terms allow republication. Missing records and shifted definitions are the two failures that quietly corrupt a story.

When the deadline passes, escalate in order. Send one polite reminder citing the date you submitted and the statutory period. Contact the FOIA Public Liaison, whose name and contact details must be published by every agency, and ask them to note the request internally. File a complaint with the Justice Department’s Office of Information Policy, which publishes agency responsiveness reports and handles delay complaints. The Office of Government Information Services offers mediation, and after that, litigation in federal district court, where a decision can arrive in weeks rather than years.

Common Mistakes and How to Fix Them

• Asking an agency for data it does not hold. Fix: name the component and program, and ask them to refer you if wrong. Expect a referral to add two to four weeks.
• Leaving the period undefined. Fix: give start and end dates tied to a field you know the agency maintains.
• Not specifying a format. Fix: request native electronic files plus a data dictionary, and state that rolling productions are acceptable.
• Failing to cap fees or request a waiver. Fix: put a cap in the request itself and add one paragraph explaining public-interest value.
• Sending duplicate requests to several offices. Fix: one request, one office, tracked by its confirmation number.
• Assuming confidential means final. Fix: appeal within the deadline on the notice, and request a Vaughn index for any withheld document.
• Forgetting that records expire. Fix: retention schedules destroy records on a fixed timetable. Ask anyway, and ask what the retention schedule is for the record series, because that answer is often obtainable and useful on its own.
• Assuming the data lives with the department. Fix: check whether a contractor or grantee holds it. Those records are frequently outside the agency’s custody and outside FOIA entirely.

Key Terms You Will Meet in Agency Responses

Agency letters use a handful of terms that sound alarming and mostly are not. Knowing them saves a wasted appeal.

Rolling production

The agency releases records in batches over weeks or months rather than all at once. This is normal and acceptable, and asking for it early usually gets you usable data sooner.

Unusual circumstances

A written extension the agency may claim when a request is unusually complex, usually because of volume. It adds ten working days and must come with reasons.

Segregable disclosure

The obligation to release the non-exempt portions of a record. If nothing readable comes back, the agency may not have done this.

Vaughn index

The document-by-document list of exemption claims an agency must supply for withheld records. Ask for it whenever something is redacted.

Glomar response

A refusal to confirm or deny that records exist, permitted in narrow national security contexts. It is rare and difficult to challenge.

System of Records Notice

A Federal Register notice describing a database of records about individuals. Useful for discovering what an agency holds and where.

Records custodian

The office holding the records rather than the one administering the program. Often a different address, and the reason a request stalls.

Expedited processing

A faster determination, granted only if you show compelling need such as a documented deadline. Certification in the request triggers a 10-day decision.

Frequently Asked Questions

Conclusion

Five actions get you most of the way. Identify the specific office that holds the records, search open data portals and reading rooms for what is already published, write a request that names fields, geography and exact dates, submit it through the right channel with a fee cap and a format line, then keep a complete file of everything you send and receive.

Requesting data from a federal agency is mostly preparation. A precise request gets answered in weeks, and an imprecise one gets answered in a fee estimate.