7-Year Lookback
A familiar default, but still subject to source availability, state and local restrictions, and product configuration.
Search Scope
Criminal Background Check Search Scope
Search scope is where mature screening programs separate good vendor advice from checkbox selling. A lookback label matters, but it is only one layer. Scope also includes jurisdictions, aliases, address history, source selection, reportability rules, court access, customer policy, and how exceptions are handled.
Lookback Options
Start with defaults, but do not stop there.
Many employers use 7-Year Lookback or 10-Year Lookback packages, but mature programs need to understand what the label actually controls and what it does not. A lookback period does not automatically define every source, jurisdiction, alias, or reporting rule.
10-Year Lookback
A broader default that can fit certain policies, but should be tied to role risk and legal review.
Shorter or longer scope
Configurable when customer needs, law, source access, and operational availability support it.
Cost implications
Longer or broader scope can increase paid searches, manual review, turnaround variability, and vendor fees.
Source mismatch
A lookback label can mean different things across county, federal, database, registry, and verification products.
Policy evidence
High-volume employers should be able to explain why one role uses one scope and another role uses a different one.
Beyond Time Periods
Scope also depends on geography, names, and sources.
A high-volume buyer should expect a vendor to explain how scope is formed. That means connecting candidate identity, addresses, aliases, product mix, and vendor escalation rules instead of relying on a generic package name.
Jurisdiction selection
County, statewide, federal, national database, and registry searches each answer different questions and carry different fee implications.
Name and address context
Address history, aliases, former names, and candidate-provided identity context can change which jurisdictions or name variations are relevant.
Name structure
Hyphenated names, compound surnames, apostrophes, spacing differences, suffixes, and generation markers can affect how records are searched and reviewed.
Primary-name-only risk
A package can appear broad while still missing important context if the vendor searches only one legal-name format.
Escalation rules
A national database signal should have a defined follow-up path, not trigger arbitrary paid county searches.
Client-specific scope
Staffing and enterprise programs may need scope that varies by client, branch, worksite, department, or role.
Exception handling
Programs should document what happens when a court is delayed, a source is unavailable, a name needs review, or a record needs follow-up.
Legal and Operational Limits
What can be searched is not always what can be reported.
Sophisticated buyers know that search scope is not the same as reportability. A source may return information that cannot be reported, or a package may be legally limited even when a buyer wants more history.
Reportability matters
Employers should distinguish what was searched from what may be reported or considered.
Local restrictions
State and local rules may affect lookback periods, timing, record types, salary exceptions, or use of information.
Adverse-action readiness
If a result may affect employment, workflows should support required candidate notices and review steps.
Fee reasonableness
Broader scope should not be used as a justification for unclear or unnecessary pass-through charges.
Periodic recalibration
Large programs should revisit scope as laws, source access, pricing, and business needs change.
Defensible documentation
Package logic should stand up to questions from HR, procurement, legal, customers, and candidates.
Related Services
Build the right screening package.
Buyer Questions
What employers usually ask.
What should high-volume employers review in criminal search scope?
Review lookback period, jurisdictions, source types, aliases, address history, escalation rules, court-fee handling, turnaround exceptions, and reportability controls.
Is 7-Year Lookback the same across every criminal search?
No. A lookback label can behave differently across county, federal, database, registry, and other source types. Legal and source limitations still apply.
When does a 10-Year Lookback make sense?
A 10-Year Lookback may fit higher-risk roles, customer requirements, or policy needs, but it should be reviewed against applicable law, source access, and cost impact.
Can criminal history scope go beyond 7 or 10 years?
Sometimes. Shorter or longer scope can be configured when customer needs, law, source availability, and operational realities support it.
How does search scope affect background check cost?
Broader scope can add counties, aliases, manual review, paid source access, and longer turnaround. Buyers should understand which added costs are legitimate.
Why is search coverage different from reportability?
A source may be searched and may return data, but law, customer policy, and reportability rules determine what can be included or considered.
How should national database results affect scope?
They can point to possible jurisdictions or records, but follow-up should be governed by policy and source logic, not automatic over-ordering.
Can aliases and address history change scope?
Yes. They can influence the counties, names, and jurisdictions considered relevant to a candidate search.
Should criminal search scope include name methodology?
Yes. Scope is not only time period and geography. It also includes whether aliases, former names, hyphenated names, suffixes, punctuation, spacing, and source-specific name formats are handled thoughtfully.
How can buyers compare name-search quality without seeing proprietary logic?
Ask whether the vendor considers relevant aliases and name variations, how exceptions are documented, and whether the workflow can explain why a result was reviewed or escalated without requiring disclosure of the vendor's matching algorithm.
What makes search scope defensible?
Defensible scope can be explained by role risk, source coverage, legal requirements, customer policy, cost treatment, and documented workflow.
Is this legal advice?
No. This is general screening program information. Employers should work with counsel on specific lookback, reporting, and decision policies.
Talk to BackgroundPro
Schedule a DemoBuild a screening program around the roles you hire for.
Tell us what you need to screen, where you hire, and how your policies handle scope, candidate intake, and review.