Understanding the topic
Courts and public-record sources are often searched by name, but a name by itself does not uniquely identify a person. Common names, spelling variations, initials, transliteration, suffixes, and data-entry differences can produce several possible results. Two unrelated people can share a full name and live in the same region.
A screening process therefore separates source discovery from identity confirmation. A possible name match may justify additional review, but it should not be treated as a confirmed candidate record until enough reliable identifiers and source context align.
Identifiers that help distinguish people
Reviewers compare the identifiers available from the candidate and the originating source. No single identifier is perfect, and not every source displays the same information.
- Full legal name, middle name, suffix, and approved prior names.
- Date of birth or age information, when the source lawfully makes it available.
- Current and former addresses that connect the candidate to the searched jurisdiction.
- Case, license, employer, school, or record details that provide source-level context.
- Name variations developed through an SSN trace or candidate-supplied history, reviewed as leads rather than proof.
How a potential match should be reviewed
Reliable matching is a documented comparison process, not an intuitive judgment based on how similar two names look.
- 1
Identify the originating source
Determine which court, registry, agency, employer, school, or licensing body produced the possible result.
- 2
Compare multiple identifiers
Use the available date, address, middle-name, suffix, case, or license details rather than a name alone.
- 3
Review the current source record
Check for updated dispositions, corrections, duplicate cases, or source limitations.
- 4
Resolve or exclude the result
Document why the result was confirmed, excluded, or left unresolved.
- 5
Use the dispute process
When the candidate challenges the information, allow the reporting process to investigate and update the report.
Why identity matching can remain uncertain
Some public records contain limited identifiers, and an employer should not force an uncertain result into a match.
- Older records may omit date of birth or show only an age.
- Common names can produce several records in the same jurisdiction.
- Aliases and prior surnames can improve coverage but also introduce unrelated leads.
- Aggregated database data may not include the latest disposition or complete source identifiers.
- A name-only internet search can introduce information that is unverified, irrelevant, or about a different person.
Employer practices that reduce mistaken associations
Employers should build report review around verified provider information and consistent role criteria, not informal investigation.
- Collect accurate candidate information through the approved secure workflow.
- Train reviewers to distinguish a possible match from a confirmed source record.
- Do not rely on screenshots, social-media posts, or name-only web searches to fill gaps.
- Ask the provider how common-name cases and aliases are handled.
- Replace assumptions with a corrected or supplemental report when the dispute process changes the result.
Putting the information into a screening program
An SSN trace can help organize names and address history, but it is not a criminal-record search and does not prove that every returned name belongs to the candidate. Source-level review and multiple identifiers remain essential.
The screening provider reports information under its matching and reporting procedures; the employer applies job-related criteria and makes the employment decision. Uncertain identity should be escalated, not converted into an adverse assumption.
RELATED SERVICES
