Public records reporting starts with finding the right custodian

When a story is already in the news, the explanation that readers need often sits in a public record, and the first problem is knowing which office holds it. A reporting question is not yet a records request. Turn it into an identifiable document, then follow that document toward the office with authority to keep it. At each fork, choose the next step that reduces guesswork: define evidence, establish the rules, locate custody, and check whether the file is already public.

Use the branches below in order when useful, or jump to the one matching your uncertainty. A request can seek records that already exist, not an official explanation made for you. Keep that distinction in view as you move from reporting question to source file and, eventually, to a claim you can support.

If you can describe the evidence but not the document

If the issue is clear but the record is not, identify a claim to test and ask what existing document could provide direct evidence. Requests work best when they identify material an office can search for, rather than asking an official to explain a decision or answer a broad question.

Once you have a likely record type, specify the office, people or programs, date range, identifiers, and preferred format. The request checklist offers a way to make those limits usable in a search, instead of turning a focused inquiry into a request for every document about a broad subject.

Rule of thumb: Translate the reporting question into records that could answer it, then use names, dates, record types, and project or case identifiers to make the search manageable. Ask for an existing document, not a newly written explanation of what the office thinks happened.

A worked example: a story already in the news

The scenario is hypothetical. Suppose coverage reports that a county jail inmate has died and asks how the jail was inspected. The question maps to records and custodians like this:

One event, four custodians. Naming the right one first saves a referral round. Only then does a short, specific request make sense.

If the file may be governed by a different access system

If you are unsure which rules apply, first establish whether the records belong to a federal, state, local, tribal, or court system. That distinction determines where to direct the request and which procedures may apply, including rules on exemptions, fees, and appeals.

Federal executive agencies use the Freedom of Information Act, 5 U.S.C. § 552. State and local offices follow their state's law, while tribal governments and court files operate under their own codes or rules. Examples of state statutes include California's Public Records Act, Texas's Public Information Act, New York's Freedom of Information Law, Florida's Public Records Act, and Illinois's Freedom of Information Act.

The federal FOIA process is distinct from Canadian access requests, which follow a separate system. Before sending anything, match the record to the government body that holds it and confirm the access route for that body. This is general reporting guidance, not legal advice for an individual request.

Rule of thumb: Identify the government body and the rules governing its records before choosing a request route. Similar documents can face different procedures depending on the custodian, so check the system that applies to the office actually responsible for the file.

If an institution is named but the custodian is not

If you know the institution but not the office holding the official copy, trace who created the document, who received it, which system maintains it, and which unit has records authority. The department named in a document may not be the custodian able to search for or release it.

Custody may sit with a particular role rather than a whole department. City or town clerks keep contracts, minutes, and ordinances; county recorders or clerks keep deeds, liens, and vital records; police records units handle incident and arrest reports; and school district custodians handle student and spending files. Agency records officers and court clerks are also possible contacts.

A staff directory, retention schedule, or call to the public records officer can help identify the right unit before filing. North Carolina's public records law, § 132-2, names the official in charge of an office holding records as its custodian; the North Carolina custodian rule illustrates that approach.

A contractor may supply data while an agency keeps the resulting report, and a central portal may display a document owned by another office. When publication and custody are separated, start with the office that has records authority and ask for a referral if it is not the right contact.

Court materials may follow separate access procedures, so identify the relevant clerk before relying on an agency contact. The docket and ruling method addresses court-file reading, while the court records checklist flags sealing, redaction, and protected names.

Rule of thumb: Follow the document's creation and custody rather than relying only on the institution named on its face. Confirm the responsible office through a directory or records officer, and contact the court clerk when court rules govern access.

If an existing public copy could answer the question

If you know the agency or record type, look for an existing copy before filing. Check the agency website, reading room, meeting packet, procurement portal, regulatory docket, legislative system, court database, audit page, and archived pages that might contain the material.

For federal records, FOIA.gov provides a federal request portal and agency contacts; electronic reading rooms publish frequently requested documents, GovInfo holds federal publications, and PACER holds federal court filings. MuckRock also hosts requests and released records filed by journalists and others, so a published item may already have a stable identifier.

The FOIA FAQ says agencies do not have to create a new record, conduct research, analyze data, or answer a requester's questions. State and local laws set their own boundaries. If a public copy is complete and its provenance is clear, save its page, identifier, and access date so you can find it again.

Rule of thumb: Search likely public sources first, but do not assume that a page contains the complete or official file. Record enough identifying information to retrieve the copy later, and request an existing document rather than asking an office to prepare an explanation.

If no public copy settles the question

If a request is still needed, define the boundaries that make the record searchable: the responsible office, record type, relevant people or programs, dates, identifiers, and preferred format. A clear scope helps the custodian look for existing records without requiring it to create a new account of events.

If formulas, fields, or metadata matter, request the native electronic format because a printed spreadsheet can hide formulas or cut off columns. A data dictionary can explain unfamiliar codes. Keep the request focused on what you need to test, and specify a format when flattening the file would remove information that matters.

Rule of thumb: Give the custodian enough boundaries to find the records, and ask for a format that preserves relevant information. Dates, names, record types, and identifiers make the search more precise without asking the office to produce a new explanation.

If the response arrives before the records do

If the office responds, check what search it describes, whether material was withheld, which exemptions it cites, whether it made a referral, what fees apply, and what appeal options are available. Keep the original request, correspondence, response letter, released files, and download date together, especially when records arrive in stages.

A no-records response does not establish that an event never happened; the missing-record analysis explains that limit. The search may have missed the material because of the office, system, dates, or terms searched. Keep the result alongside the request and any later correspondence so the search can be understood in context.

If the response names another office, note the referral and direct the next inquiry to the named custodian. The request and response help show which office, systems, dates, and search terms were involved if you need clarification or want to challenge the result through the stated appeal route.

Rule of thumb: Treat the response as evidence about the search and its result, not as a complete account of whether an event occurred. Preserve the paperwork and use the stated appeal route if you need to contest a decision.

If a released file supports less than its contents seem to say

If a document arrives, check who created it and received it, its date and covered period, its version, its actual scope, its definitions, and any referenced attachments. These checks establish what the file is and what it can support before you rely on the statements inside it.

Compare the contents with another record, a knowledgeable source, direct observation, or independently obtained data. Official authorship shows where a file came from, but it does not establish that every statement is accurate. The official record types comparison helps distinguish what different records can demonstrate.

A contractor's data, a portal copy, or a file maintained by another office may point to a different custodian. If the released document refers to missing attachments or a later version, note what is absent before treating the copy as complete evidence.

Rule of thumb: Check identity, time period, version, scope, definitions, and attachments before interpreting a document. Test its claims against another source where possible; provenance establishes where a record came from, but does not by itself establish accuracy.

If the evidence is ready to describe

If the records support only a limited conclusion, keep the wording within that limit. Invoices may show that a city paid $84,000 without establishing the project's total cost if labor, change orders, or other accounts are absent. State what is documented, then make clear what the records do not show.

Match the conclusion to the record type: contracts and bid tabulations show what was promised; invoices and payment records show what was paid; emails and memos show what officials knew or intended; logs and databases show activity; audits and inspections show what a reviewer found.

Explain consequential redactions and missing attachments, and link to a specific source page when access is stable. Keep personal data out unless it has a clear public-interest role. An official document can be genuine while containing errors or disputed claims, so attribute its contents and test the underlying claim.

Rule of thumb: Describe what the record demonstrates, what remains unresolved, and what needs independent verification. Explain missing material when it affects the reader's understanding, and avoid publishing personal information without a clear public-interest reason.