Federal, State, and County Criminal Searches Explained

June 15, 2026
Uncategorized
9 min read

Federal vs. State vs. County Criminal Searches: A Plain-English Breakdown

Estimated reading time: 6 minutes

Key takeaways

  • Jurisdiction matters: county searches often reveal local records that state or federal checks miss.
  • Use a layered approach: combine county, state, and federal searches based on role risk and legal requirements.
  • Fingerprint checks reduce identity risk: use them when accuracy is critical or legally required.
  • Follow FCRA and local laws: consent, disclosure, and adverse-action procedures are essential.

Table of contents

Why jurisdiction matters for criminal searches

Criminal records are created and stored by different courts and agencies. A single “national” search rarely tells the whole story because many offenses are adjudicated at the county level and never appear in state or federal indexes. Choosing the right search affects accuracy, turnaround time, cost, and legal risk—especially under the Fair Credit Reporting Act (FCRA), state ban-the-box and lookback restrictions, and anti-discrimination rules.

Tip: know the jurisdictions where the candidate has lived or worked; that determines which county searches to run.

Federal criminal searches: what they are and when to use them

A federal criminal search looks for offenses filed in federal courts—cases prosecuted under federal statutes rather than state law. Examples include large-scale drug conspiracies, mail and wire fraud, certain immigration crimes, tax evasion, and crimes that cross state lines.

Key characteristics

  • Scope: Only federal court records. It does not include state or local convictions.
  • Typical use cases: Positions requiring a security clearance, federal contractor roles, certain financial or compliance-sensitive jobs, or when a specific federal conviction is a disqualifier.
  • Accuracy: Federal records are definitive for federal offenses. However, many common workplace offenses (misdemeanors, most felonies) are prosecuted in county or state courts and won’t show up in federal searches.
  • Access method: Can be run via federal court record systems or through fingerprint-based FBI checks for a more complete national history. FBI checks require fingerprints and candidate authorization; they have longer turnaround times and stricter handling.

When to run a federal search

  • Role requires federal clearance or federal contract compliance.
  • You need to verify a history of federal-level criminal activity specifically.
  • State or county checks returned nothing but you have reason to suspect federal involvement.

State criminal searches: the middle layer

State criminal searches retrieve records from a state’s central repository or criminal history database. These repositories aggregate arrest and disposition information submitted by local jurisdictions—though coverage and timeliness vary by state.

Key characteristics

  • Scope: Statewide records submitted to the state repository. Some states include many county-level dispositions; others are incomplete.
  • Typical use cases: Most general employment screenings include a state repository check as a baseline because it covers convictions and sometimes arrests reported statewide.
  • Limitations: Not all counties report consistently to the state repository, and there may be delays. Sealed or expunged records may or may not appear based on state law.
  • Accuracy: Better than a single county search for seeing statewide patterns, but still can miss local cases or contain identity-match errors for common names.

When to run a state search

  • You want a broader view across the state without checking every county individually.
  • Role covers a statewide footprint (e.g., sales rep, multi-site supervisor).
  • You need to comply with state-level requirements for certain industries.

County criminal searches: the local deep dive

County criminal searches target court records maintained at the county level—where most arrests, misdemeanors, and many felonies are prosecuted. These are often the most complete source for local activity.

Key characteristics

  • Scope: County court case filings, dockets, judgments, and sentencing information.
  • Typical use cases: Hiring for location-based roles where local activity matters, positions of trust, or when you need to verify details of a specific incident.
  • Limitations: Court systems differ widely—some are online, some require in-person or clerk-assisted searches. Name-based queries can return false positives; matching requires corroborating data (DOB, aliases).
  • Accuracy: High for local cases; county searches often uncover records not present in state repositories.

When to run a county search

  • Candidate has lived, worked, or been arrested in a specific county.
  • You need to verify misdemeanor history or local cases not found in state records.
  • Role requires a very thorough background check for safety or regulatory reasons.

Name-based vs. fingerprint-based searches: choosing the method

Name-based searches: Faster and less costly. Useful for initial screening but prone to false positives (common names) and false negatives (misspellings, aliases).

Fingerprint-based searches (including FBI Identity History): The gold standard for identity accuracy and comprehensiveness. Require candidate cooperation and more time. Often required for regulated roles (healthcare, childcare, federal positions).

Best practice: Use name-based checks for routine hiring and add fingerprint-based checks where law, policy, or risk demands greater precision.

Common pitfalls that cost employers time and risk

  • Relying on a single database or “national criminal database” that claims to cover everything. Many such databases aggregate public records but miss county-level court files and may include outdated or erroneous entries.
  • Skipping county searches because state repository looks clear. Many convictions never make it to the state level.
  • Misinterpreting arrests versus convictions. Arrests without conviction, or arrests that did not lead to charges, require careful handling under many state laws.
  • Ignoring sealed or expunged records. Jurisdictions vary on whether sealed records are reportable; your screening policy must reflect current law.
  • Failing to follow FCRA adverse action steps when criminal records lead to a hiring decision—this opens you to legal exposure.

Compliance considerations HR teams can’t ignore

  • FCRA: If you use a consumer reporting agency to run criminal checks, you must get written authorization and follow pre-adverse and adverse action procedures if you decline or change a job offer based on the report.
  • Ban-the-box and local restrictions: Many states and cities limit when you can ask about criminal history and what offenses you can consider. Some jurisdictions also set lookback periods for arrests/convictions.
  • Equal Employment Opportunity (EEO) risk: Blanket policies that exclude candidates for any criminal history can create disparate impact on protected groups. Use targeted, job-related screening and documented individualized assessments when necessary.
  • Data security and retention: Criminal background information is sensitive. Limit access, store securely, and purge according to your retention policy and applicable law.

Practical screening strategies for reducing hiring risk

A layered, risk-based approach matches the depth of your check to the position’s responsibilities and legal mandates. Here’s a practical framework:

For low-risk, non-sensitive roles

  • Run a national criminal database and state repository check.
  • Consider county searches only when there’s reason to suspect local activity.

For mid-risk roles (customer-facing, cash handling, safety-sensitive)

  • Run state repository plus county searches for counties where the candidate lived or worked in the past 7–10 years.
  • Use name-based searches to start; consider fingerprint checks if identity concerns arise.

For high-risk or regulated roles (finance, healthcare, childcare, federal contract work)

  • Include fingerprint-based FBI checks, state repository, and thorough county-level searches.
  • Verify licensing sanctions and professional registries as applicable.

Ordering checklist

  • Obtain written candidate authorization under the FCRA.
  • Confirm the candidate’s jurisdictions (current and prior addresses).
  • Choose fingerprint-based checks for roles requiring the highest certainty.
  • Document job-related criteria and an individualized assessment process.
  • Follow pre-adverse/adverse action steps if taking adverse employment decisions.
  • Track local restrictions (ban-the-box, lookback periods) for each hiring location.

Practical takeaways for HR leaders and recruiters

  • Jurisdiction matters: County searches often uncover what state and federal checks miss.
  • Use a layered approach: Combine county, state, and federal checks based on role risk and legal requirements.
  • Fingerprints reduce identity risk: Use them when accuracy is critical or legally required.
  • Keep screening job-related and consistent: Tailor policies, document decisions, and use individualized assessments to limit legal exposure.
  • Follow FCRA and local laws: Consent, disclosure, and adverse action steps are non-negotiable.
  • Partner with experts: Experienced screening providers can help map jurisdictions, advise on compliance, and streamline searches.

Conclusion

Federal, state, and county criminal searches each serve different purposes. County searches are most likely to reveal local arrests and convictions; state repositories provide a broader but sometimes incomplete view; federal searches are narrow but necessary when federal offenses or federal requirements are at issue. Align your screening depth to the role’s risk profile, document processes for legal defensibility, and choose identity methods that match the need for accuracy.

If your team needs help designing a jurisdiction-aware screening program that balances thoroughness and compliance, Rapid Hire Solutions can advise on which searches to run for each role, manage consent and adverse-action workflows, and handle fingerprinting and court-level queries—so you get reliable results without added legal risk. Contact Rapid Hire Solutions to discuss a screening plan tailored to your hiring needs.

FAQ

What is the difference between federal, state, and county criminal searches?

Federal searches look for cases filed in federal courts (narrow scope but definitive for federal offenses). State searches query a central repository that aggregates submissions from local jurisdictions (broader but may be incomplete). County searches query local court records where most arrests and many prosecutions occur and are often the most complete source of local activity.

When should I run a fingerprint-based FBI check?

Run fingerprint-based FBI checks when you need the highest identity accuracy—typically for high-risk or regulated roles (healthcare, childcare, finance, federal contracts) or when a role requires federal clearance. Fingerprint checks require candidate cooperation and take longer.

Are arrests the same as convictions for hiring decisions?

No. Arrests are not convictions. Many jurisdictions and laws limit how you can consider arrests that did not lead to charges or convictions. Treat arrests carefully and verify dispositions before making adverse employment decisions.

What FCRA steps must I follow if a report affects hiring?

Under the FCRA, obtain written authorization before running a consumer report. If you plan to take adverse action based on the report, follow pre-adverse action (provide a copy of the report and a summary of rights) and adverse action notices (document the decision and provide required company and CRA information).

How do I avoid disparate impact when screening for criminal history?

Avoid blanket exclusions for any criminal history. Use targeted, job-related criteria, document individualized assessments, and consider time limits/lookback periods required by local laws. Consult with legal or compliance experts to align policies with EEO guidance.