How to find and request public records, step by step

What to take away

• Define the existing records you need before choosing a request law or portal.
• Search public databases, reading rooms, agendas, audits, filings, and prior releases first.
• Send the request to the office that creates or maintains the records.
• Describe custodians, systems, fields, event, and date range without asking the agency to answer a question.
• Audit the response against the request, search description, exemptions, page count, and missing attachments.

A strong public-records request begins as a reporting specification. "Tell me why the project failed" asks for research and explanation. "All final monthly status reports sent by the project manager to the oversight office from January through June" describes records that may exist.

This workflow addresses U.S. federal FOIA practice as a model. State, local, court, legislative, and international access systems have different laws, exemptions, deadlines, fees, and appeal procedures. Check the rule that governs the actual custodian.

Step 1: define the reporting question

Write the fact you are trying to establish. Then list the records that would be created if the event occurred.

Reporting question	Possible record
Who approved the contract change?	Signed modification, approval memo, workflow log
When did officials learn of the failure?	Incident ticket, briefing, email, meeting minutes
How much was paid?	Invoice, payment ledger, obligation and expenditure records
Why was a license denied?	Application, reviewer notes, notice, final decision

Prioritize records with fixed fields, dates, senders, recipients, identifiers, and systems. These details make a request searchable.

Step 2: identify the record creator and custodian

Map the process that creates the record. The office announcing a program may not hold its invoices. A parent agency may have separate FOIA components. A contractor may maintain records on behalf of an agency under terms that affect access.

Call a public liaison, clerk, archivist, records officer, or program specialist when the system is unclear. Ask which office maintains the record series, what it is called, and how it is arranged. Do not ask the person to prejudge disclosure.

Step 3: search before requesting

Check the agency site, FOIA reading room, inspector general reports, meeting packets, procurement databases, court dockets, legislative systems, regulatory dockets, archives, and prior media releases. Search by program aliases, form numbers, contract IDs, office names, and record-series titles.

The federal government's instructions on making a FOIA request advise checking whether the information is already public, submitting a written request to the relevant agency office, and reasonably describing the records. They also clarify that FOIA does not require an agency to create records, conduct research, analyze data, or answer questions.

Public material can narrow the request and reveal exact custodians or identifiers. Preserve the search date because published collections change.

Step 4: scope the record precisely

Use a request frame with six parts:

1. Record type: final inspection reports, approval memoranda, or message exports.
2. Custodian or office: named roles, units, mailboxes, or systems.
3. Subject or identifier: contract number, incident ID, facility, case, or project.
4. Date range: explain whether it applies to creation, sent date, filing, or event.
5. Fields or attachments: include exhibits, native files, metadata, and data dictionaries.
6. Exclusions: remove duplicates, newsletters, public copies, or irrelevant routine notices when useful.

Avoid "all records related to" when narrower identifiers exist. Avoid a list so brittle that a different filename defeats the search.

Step 5: choose format and metadata

Ask for records in their native electronic format when structure matters. A spreadsheet converted to PDF can lose formulas, sheets, filters, full values, and machine readability. Email exports can preserve sender, recipient, date, subject, attachment relationships, and message identifiers better than printed pages.

Request the fields needed to interpret data, plus documentation, code lists, layout, and revision history. State a preferred delivery method.

Step 6: write a neutral request

A clear request can read:

Please provide final monthly status reports created from January 1 through June 30, 2027, for Project Harbor under contract HC-27-104, including attachments. Please search the project manager's official email account and the Program Status Repository. I request electronic records in their native format where readily reproducible, with associated record-level date, author, and file-name metadata.

The request describes records and likely locations without arguing the story or demanding a conclusion.

Step 7: address fees and processing

Identify the applicable requester category and fee rules. If seeking a waiver or expedited processing, make the required factual showing rather than using a slogan. Offer a fee ceiling and ask for notice before costs exceed it.

The category is worth arguing for. The Justice Department's decision tree for assessing fees sets out the basic rule that when an agency misses a statutory time limit it may not charge duplication fees to a news media requester, alongside the three narrow exceptions that let it charge anyway, including requests running past 5,000 pages.

Keep the submission, confirmation, tracking number, portal copy, correspondence, clarification, and dates. Calendar statutory or agency response points, but distinguish an acknowledgment from a substantive determination.

Step 8: negotiate scope in writing

If the office says the request is burdensome, ask which term drives volume, which systems will be searched, and what narrower date, custodian, or record type would preserve the reporting purpose. Confirm every agreed change in writing.

Do not accept a narrowing that silently removes the likely decision maker, attachments, or relevant system. A faster empty search is not success.

Step 9: audit the response

Create a production log:

Check	Question
Scope	Which request items did the response address?
Search	Which offices, custodians, systems, and terms were used?
Count	Do page, file, attachment, and row totals reconcile?
Withholding	Which authority applies to each deletion or withheld record?
Completeness	Are referenced attachments and earlier versions present?
Format	Were native data and needed documentation supplied?

Look for broken sequences, missing pages, blank attachments, unexplained duplicates, and references to unproduced records. Do not assume every gap is improper; ask for an explanation.

Step 10: challenge or appeal precisely

Use the response letter's process. State the disputed search, exemption, segregation, fee, format, or procedural issue and explain the requested remedy. Preserve deadlines and proof of filing. Mediation or liaison contact may resolve a narrower problem without formal litigation.

Step 11: verify before publication

Confirm names, identifiers, dates, versions, and status through the record system. Separate the agency's statements, a requester's allegations, and the newsroom's analysis. Seek comment on material interpretations and give the custodian enough detail to locate the point at issue.

Common questions

Should I request "information" or "records"?

Describe identifiable existing records. Access laws generally do not require an office to answer questions or create an analysis.

Can I request emails by keyword only?

Yes, but custodian, date, account, subject, and event identifiers usually produce a more reviewable search.

Is a no-records response proof that nothing happened?

No. It reports the result of a stated or unstated search. Assess custodian choice, systems, terms, retention, dates, and the response's wording.

Should I publish a received record immediately?

First verify authenticity, completeness, status, context, privacy risks, and what its statements can prove.