How to search public records without confusing people

Public records are records of events, filings, licenses, cases, property, or government activity. They are not ready-made profiles of people. When two records carry the same name, the safe default is that they may describe different people until the record itself and independent context support a match.

The governing rule is simple: a name is a search field, not an identity identifier.

Define the person before opening the database

Make a target card from facts you already obtained lawfully and can source:

• full name and genuine spelling variants
• middle name or initial, when known
• approximate age or year range rather than an unnecessary full birth date
• locations during the period you are researching
• organizations, roles, or professional licenses at that time
• the event, filing, property, case, or question you are actually trying to verify

Attach a date and source to every fact. Present-day location cannot safely identify a person in a 2008 filing. A current employer cannot distinguish two namesakes in a record created before either joined that organization.

Keep this card minimal and protected. Do not collect relatives, addresses, birth dates, or other sensitive details simply because a database exposes them.

Search the right system for the right event

Start with the agency, court, archive, or registry responsible for the record. Confirm three things before searching:

1. Jurisdiction: Does the system cover the state, county, court, or country where the event would have occurred?
2. Date range: Are records from the relevant period actually online?
3. Record meaning: Is the entry an index, a filed allegation, an issued license, a final order, a deed, or something else?

An aggregator can help locate a possible record, but verify the result in the official source or with the record custodian. Some official systems are indexes only. PACER, for example, provides access to US federal court case records and a nationwide case locator; it does not cover every state or local court.

Search broadly enough to catch known variations, but keep the result sets separate. Try a full middle name, an initial, no middle name, a previous surname, and documented spelling variants. Do not silently convert a partial name match into an exact one.

Give every result its own provenance row

Record the evidence before deciding who it describes:

| Field | What to capture | | --- | --- | | Record source | Agency, court, archive, database, and exact URL | | Record identity | Case number, document number, book/page, license number, or stable ID | | Named party | Name exactly as the record displays it | | Event context | Record type, jurisdiction, event date, filing date, and status | | Identity clues | Age/year range, location at the time, organization, role, or other fields actually present | | Limitations | Missing pages, index-only result, possible OCR error, sealed material, or unclear status |

A stable case or document number identifies a record, not necessarily the human you had in mind. Keep the record-level identity and person-level identity as separate questions.

Compare candidates across independent anchors

Use the fields contained in the record and contemporaneous sources. Stronger anchors include:

• full middle name or a consistent middle initial
• age or birth-year range appropriate to the record date
• location at the time of the event
• organization, occupation, or professional identifier at that time
• a case, license, parcel, or document number repeated in another authoritative source
• a timeline that can exist without requiring the same person to be in two incompatible places or roles

The National Archives notes that even a census age is an approximation and that record accuracy depends on the knowledge of the person who supplied the information. That is a useful model for public records generally: a field is evidence in context, not automatically a timeless fact.

Use relatives or household members only when the official record itself makes that relationship relevant and your purpose justifies it. Do not expand the search into a family map to compensate for weak evidence.

Keep namesakes in separate columns

Build a disambiguation matrix instead of a single merged profile:

| Anchor | Candidate A | Candidate B | Target card | | --- | --- | --- | --- | | Name as recorded | Exact text | Exact text | Known variants | | Place at record date | Place and source | Place and source | Expected place | | Age or year range | Range or unknown | Range or unknown | Expected range | | Organization or role | Detail and source | Detail and source | Expected context | | Record ID | Stable identifier | Stable identifier | Event being researched | | Contradictions | List them | List them | — |

Do not merge when only the name and a broad geography match. Do not average conflicting ages, assume an initial is a middle name, or move an address from one candidate to another. Preserve negative evidence and contradictions rather than hiding them in narrative notes.

For common names, require more distinctive agreement. “Alex Lee, California” may identify thousands of people. “Alexandra M. Lee, licensed under the same professional number, at the documented organization during the relevant year” is a much narrower claim—but it still needs the original record checked.

Read what the record actually says

An official source can accurately preserve a claim without establishing that the claim was true. Court complaints contain allegations. Dockets record procedural events. Arrest records are not convictions. A license may be expired, suspended, or issued to a business rather than an individual. Property records describe legal instruments and can lag real-world changes.

Use precise verbs:

• “the complaint alleges,” not “the person did”
• “the docket lists,” not “the court found”
• “the index returns a record under this name,” not “this is the same person”
• “the license was shown as active on the retrieval date,” not “is always licensed”

Open the underlying document when available and inspect its status, date, parties, and disposition. A search-result row or snippet is not enough for a consequential statement.

Report confidence and the unresolved alternatives

Use an explicit outcome:

• Matched: multiple independent, time-appropriate identifiers agree and no material conflict remains.
• Probable: the evidence strongly favors one candidate but a decisive field is missing.
• Ambiguous: two or more candidates still fit.
• Not matched: a material conflict excludes this candidate.
• No record located: the named systems and date ranges returned no usable record.

List which systems, jurisdictions, variants, and dates you checked. “No record located” must not become “the event never happened,” especially when coverage is partial, records are offline, names vary, or access is restricted.

Minimize harm when saving or sharing the result

Keep only the fields needed to support the conclusion. Redact full birth dates, home addresses, account numbers, signatures, children's details, and unrelated personal data before sharing notes. Link to the record and quote the relevant portion instead of republishing an entire personal file.

Do not use DeepSearch or an ordinary public-record workflow for employment, credit, housing, insurance, tenancy, or another regulated eligibility decision. The FTC explains that US employers using consumer reports must follow Fair Credit Reporting Act steps including notice, permission, and pre-adverse-action procedures. General public-web research is not a substitute for a compliant screening process.

If you began with only fragments, first use how to find someone with incomplete information. For the broader limits on collection and publication, read what we do—and don't do—with public data.