Write a Federal Data Access Request That Produces a Usable Table

If you need grant records for a public analysis, ask for the underlying table—not just a report summarizing it. A useful data access request identifies the records, date range, fields and preferred file format. The intended result is a dataset whose rows you can check, explain and, where appropriate, publish.

The example below requests grant-award transactions. It is an illustrative structure, not a real request or dataset.

Choose the right kind of request

“Data access request” can mean different things:

• Your own personal information: in the UK, this is commonly called a subject access request (SAR or DSAR). It concerns an organisation’s use or storage of your personal information, not general access to its datasets. The ICO’s subject access guidance explains that route.
• Government records for analysis: use the relevant public-records process. In the United States, federal FOIA covers federal agency records; state and local bodies have separate public-records processes. Disclosure can be subject to exemptions, including personal privacy. See the federal FOIA guidance.
• A private or research dataset: follow the owner’s access process and ask about permitted uses, redistribution and publication.

The template here is for U.S. federal agency records, not a personal-data SAR. For another jurisdiction or data owner, adapt the request to its rules rather than copying the legal framing.

Define the table before writing

Start by checking the agency’s website and published datasets. FOIA.gov recommends checking for existing public information first.

Then define the observation represented by each row. For this example, one row is one recorded grant-award transaction, not one recipient or one grant program.

Requested field	Why it matters
Transaction identifier	Helps distinguish individual transactions
Award identifier	Links transactions belonging to the same award
Transaction date	Defines the reporting period
Program name or code	Supports filtering by program
Recipient organisation	Identifies the organisation receiving the award
Transaction amount and currency	Makes monetary values interpretable
Transaction type	Helps distinguish new awards, adjustments and other entries

Ask for existing field definitions too. Without them, an “amount” column might mean a transaction value, total award value or payment—different measures that should not be combined casually.

Use a focused request template

The following example assumes you have identified the federal agency and grant program that hold the records. Add the actual program name to the subject line and replace the dates with your research period before sending.

Subject: FOIA request for grant-award transaction records, calendar year 2025

Under the Freedom of Information Act, I request existing electronic records of grant-award transactions for the grant program named in the subject line, with transaction dates from January 1 through December 31, 2025.

I seek the existing fields for transaction identifier, award identifier, transaction date, program name or code, recipient organisation, transaction amount, currency and transaction type, where those fields are held.

Please provide the records electronically, preferably as CSV or in their existing spreadsheet format, rather than as a PDF rendering of the table. Please also provide any existing data dictionary, code lists or documentation explaining these fields, including how adjustments and negative amounts are recorded.

I am requesting existing records, not a new analysis or calculated summary. If the described scope is unclear or a narrower scope would help locate the records, please contact me before proceeding.

I am willing to pay up to $25 in fees. Please obtain my agreement before incurring fees above that amount.

The $25 is an example spending limit, not a standard FOIA fee. Add your contact details and meet any agency-specific submission requirements. Use the agency’s designated FOIA channel and retain a copy with the submission date and tracking number.

For releasable records, FOIA requires the requested format when the agency can readily reproduce the record in that format. That does not guarantee a CSV in every case. FOIA.gov explains that agencies are not required to create new records, conduct research or analyze data. Its fee guidance also permits requesters to state a spending limit.

Check the response before publishing

Keep the original response unchanged in restricted storage. Make a separate working copy and check:

• Coverage: do the dates and program match the request?
• Row meaning: are these transactions, award totals or a mixture?
• Identifiers: are duplicates genuine repeated transactions or import errors?
• Amounts: what do negative values, blanks and zeros mean?
• Disclosure limits: were fields or records withheld? Describe known gaps; do not present a partial release as complete.
• Publication suitability: review privacy, confidentiality and reuse restrictions separately from receipt of the file. Do not assume access authorises unrestricted republication.

Do not upload sensitive information. Review free-text fields and combinations of details that could identify people, not just names and email addresses. If the material is unsuitable for public release, keep it in a restricted workflow.

For an approved public copy, prepare a clean table with one header row and consistent values. Add the source agency, request reference, coverage period, receipt date, field definitions and any transformations to the accompanying description.

TablePage accepts CSV, TSV, XLSX and XLS files and generates a public, shareable dataset page with a filterable table. Upload only the reviewed publication copy, then compare its headers, row count and representative values with that copy before sharing the link.