Public Information Lookup

A public-information search succeeds when the request names an existing record

Broad requests often fail because they describe a topic instead of a record. “Everything about a property dispute” may span court filings, permits, assessor records, and agency correspondence, while “the final inspection report for a named permit” points to a specific custodian and document. Before submitting a request, write down the record type, date range, office, location, and identifiers you already know. That description can also help you discover that the record is already published online.

Jurisdiction matters as much as wording. FOIA.gov explains the federal agency process; it does not convert state or city records into federal records. State and local agencies operate under their own public-record laws and procedures, and courts often have separate access rules. A good lookup log therefore records both the source searched and the legal/government level of that source, which prevents an unanswered search from being mistaken for proof that the record does not exist.

Separate “no record found” from “wrong office searched”

A broad public-record search can fail for at least three different reasons: the record may not exist, it may exist but be exempt or restricted, or the office searched may not be the custodian. Those outcomes are not interchangeable. Before writing “no record,” confirm the government level and record owner, then record any official referral or exemption response. This is especially important when a topic crosses police, court, property, and administrative systems.

Think in record families when the query is as broad as “public information”

A broad search can include agency correspondence, meeting records, permits, property records, court files, vital records, licensing material, and many other categories, but those categories do not share one custodian or one access rule. Start by classifying the desired information into a record family, then identify the government body that creates it. If several families are relevant, run them as separate tracks and keep each track’s jurisdiction and access limitation visible. This avoids a common failure mode in which a researcher searches one convenient portal, finds nothing, and concludes that no public information exists. The more general the question, the more important source routing becomes.