Understanding the topic
Most state-law criminal cases are filed in local courts, and a county criminal search is limited to the selected jurisdiction and source. Candidates may have lived, worked, studied, or used prior names in more than one county, so employers sometimes build packages that search several relevant jurisdictions.
More searches are not automatically better. The employer should use a documented role and address-history rule, understand source coverage, and avoid ordering unnecessary jurisdictions merely because a database returns an old or uncertain address.
Factors that may identify relevant counties
The provider and employer should use approved identity information and consistent package rules.
- Confirmed current and prior residential addresses during the employer’s reviewed time period.
- Work, school, license, or assignment locations when the package specifically uses those jurisdictions.
- Approved prior names or aliases connected to a confirmed county.
- Possible records or jurisdictions developed from a broad database search that require source confirmation.
- Client, regulatory, or contract requirements that identify specific lawful searches.
How a multi-county package is applied
The process should show why each county was selected and avoid duplicate or overlapping work.
- 1
Collect and review address history
Use secure candidate information and identity-development data as research leads.
- 2
Apply the package rule
Select counties according to the employer’s documented role, time period, and jurisdiction criteria.
- 3
Identify the correct court source
Account for county, parish, borough, district, municipal, or state court structures.
- 4
Resolve possible records
Review identifiers and current source details separately in each jurisdiction.
- 5
Report scope clearly
List the counties, names, source dates, and limitations so the employer knows what was searched.
What additional counties do not solve
A multi-county search can improve jurisdictional coverage but does not become an all-records search.
- It does not search federal district courts, statewide repositories, registries, or international sources unless separately ordered.
- Old or associated addresses can create unnecessary searches if they are not confirmed.
- Courts within the same state can have different access, identifiers, and turnaround.
- A clear result in several counties does not prove that no record exists anywhere else.
- Adding counties without job-related and consistent rules can increase cost and inconsistency.
Package-design questions
Employers should choose a repeatable method that similarly situated candidates can understand and that reviewers can audit.
- How many years of address history are considered and why?
- Which types of addresses or work locations qualify under the rule?
- How are aliases connected to jurisdictions and duplicate searches avoided?
- When does a database lead trigger a county confirmation?
- How are third-party court fees, source delays, and unavailable counties communicated?
Putting the information into a screening program
Address history can support source selection but should not be treated as proof that every returned address belongs to the candidate. Candidate clarification and identity matching remain important.
Employers should compare the value of county, state, nationwide database, and federal searches rather than assuming one product substitutes for all others.
RELATED SERVICES
