The recommendation means this: anyone whose duties let them touch Criminal Justice Information (CJI) should go through a fresh, individual background re-investigation on a repeating cycle — the FBI CJIS Security Policy sets the baseline at five years, restated in its Security Addendum — with each person re-fingerprinted and re-adjudicated, not just re-screened against a database. The word doing the heavy lifting is "individual." A blanket annual check across a whole agency doesn't satisfy the policy. The recommendation applies to employees, contractors, and vendors with unescorted access to CJI, and the five-year cycle resets if a person moves into a role with broader access.

Why the Recommendation Exists in the CJIS Security Policy

The rule traces to the FBI Criminal Justice Information Services Division, which publishes the CJIS Security Policy as the contract that state and local criminal justice agencies sign when they connect to national systems. The policy's personnel security chapter requires a fingerprint-based record check before access is granted, then requires re-investigation at least every five years for personnel with access to CJI. That's not a suggestion an auditor invented; it's the controlling language in the policy itself, and the Security Addendum attached to every management control agreement repeats it.

The logic behind the cycle is that criminal history is a living record, not a snapshot. A person cleared in 2019 may have picked up a disqualifying conviction, a protective order, or a pending charge by 2024, and a name-and-date-of-birth check against a commercial database will miss it roughly as often as it catches it. Fingerprint-based re-checks hit the FBI's Next Generation Identification system and the state repository, which is why the policy insists on fingerprints rather than a web form.

The recommendation also exists because access privileges change. Someone hired as a dispatcher may be promoted into a role that reaches the state's Computerized Criminal History (CCH) repository, and the policy expects the agency to re-adjudicate at that point rather than let the original clearance ride. The five-year clock is a floor, not a ceiling — an agency can re-investigate more often, and many do when someone's role changes.

One detail that trips agencies up: the five-year requirement applies to personnel with access to CJI, which is broader than sworn officers. It covers IT staff who administer the records management system, contractors who install and maintain hardware in the server room, and vendor technicians who log in remotely with elevated privileges. If those people can see CJI, they're in scope.

The Minimum Scope of an Individual Re-Investigation

A compliant re-investigation covers three things, and agencies routinely do one and call it done. The first is a fingerprint-based search of the FBI's national repository and the state criminal history repository. The second is a check against the state and national sex offender registries. The third is a local records check covering the jurisdictions where the person has lived, worked, or attended school during the period since the last investigation.

The policy language is specific about what the fingerprint check must cover: state and national fingerprint-based record checks. It doesn't name a commercial vendor, and it doesn't accept a self-reported criminal history statement as a substitute. Some agencies layer on county court searches as a backstop because fingerprint results only reflect records that have been submitted to the repositories, and a county-level case that was never reported to the state won't surface.

That gap is the failure case worth understanding. A person with a misdemeanor conviction in a county that doesn't routinely report dispositions to the state repository can pass a fingerprint check and still have a record. The local records check — sometimes called a "local agency check" or a check of the courts of record in the person's counties of residence — is what catches it. An agency that skips that step on re-investigation because "the prints came back clean" is relying on a repository that isn't guaranteed to be complete.

The scope also has a time dimension. Re-investigation should cover the period since the last investigation, and if an agency can't confirm when the last one happened, the practical answer is to cover the person's entire adult residence history. That's more work, but it's defensible. An uncoverable gap in the record is the thing an auditor writes up.

Five Years Is the Floor, Not the Ceiling: Triggers That Force an Earlier Re-Check

The five-year cycle is the minimum re-investigation interval, but four events should push a re-check forward regardless of where the person sits on the calendar. The first is a change in access level, particularly a move into a role that reaches CCH or national systems rather than local records. The second is a credible tip, complaint, or incident that raises a question about the person's suitability. The third is a break in service longer than the agency's continuity threshold — many agencies use a year — because a returning employee's circumstances have had time to change.

The fourth trigger is a policy revision. When the FBI updates the CJIS Security Policy, as it does on a rolling basis, agencies sometimes get a new requirement that applies retroactively to existing personnel. The 2024–2025 policy cycle, for instance, tightened language around multi-factor authentication and personnel security documentation. Agencies that read the update and assumed it only affected new hires found themselves backfilling re-investigations for people hired years earlier.

A re-investigation isn't the only thing that should fire on these triggers. The policy also expects a fresh signed acknowledgment of the Security Addendum and, where the role requires it, a new user agreement. Those documents are cheap to collect and expensive to be missing when an audit arrives.

In practice, agencies often fold the trigger-based re-check into the annual security awareness training cycle, so the person re-signs agreements and confirms their residence history at the same time. That's an efficiency, not a substitute. The fingerprint check still has to happen on its own schedule.

Fingerprints, Name Checks, and What Each Method Actually Returns

The choice of screening method determines what a re-investigation can catch, and the methods are not interchangeable. A fingerprint-based check through the state and FBI repositories returns records that have been submitted to those systems, matched on biometric identity rather than name and date of birth. A commercial name-based check returns whatever the vendor's data sources contain, which is often wider in geographic coverage and shallower in currency. A local court search returns what's actually in the courthouse, which is sometimes the only place a disposition exists.

Method What it matches on Typical coverage What it misses Policy status
State/FBI fingerprint check Biometric identity State repository plus national Next Generation Identification Records never submitted to the repository; unreported dispositions Required baseline
Commercial name-based search Name plus DOB Multi-state aggregated databases Records with name changes, data-entry variants, recent filings Supplementary only
Local court/county records check Name in the county of record Courts of record in the person's residence history Jurisdictions outside the searched list Recommended backstop
Sex offender registry check Name plus identifiers State and national registries Non-registry offenses Required in most agency policies

The table makes the trade-off visible. Fingerprints are the most reliable identity match and the weakest coverage for records that never made it into a repository. Name-based searches cover more geography and are prone to false positives and false negatives alike. Local court checks find the gaps and require someone to actually walk the courthouse or use a court-records vendor with jurisdiction-by-jurisdiction access.

Most agencies combine all three for a reason. The fingerprint check is mandatory and defensible. The name-based check is fast and cheap and catches interstate records the state repository may not have. The local check is the one that takes time and is the one most often cut when budgets tighten — and it's the one an auditor will ask about if a CJI misuse incident later traces back to a person with an unreported record.

What a Complete Re-Investigation File Contains

An audit doesn't ask whether you did the re-investigation. It asks you to produce the file. A complete file for each person with CJI access contains the original fingerprint-based check and the most recent one, each with the date the result came back and the adjudication decision. It contains the signed Security Addendum and, where applicable, the user agreement. It contains documentation of the local records check and the sex offender registry check, even when the results are "no record found."

The file also needs the adjudication record itself: who reviewed the results, what criteria they applied, and what they decided. The CJIS Security Policy points to the agency's own suitability criteria, which typically follow the state's standards for the role in question. An agency that keeps fingerprints and nothing else has a file, but it doesn't have a defensible one.

Retention matters here. The policy expects these records to be retained for the duration of employment plus the period the state's records retention schedule requires, and the audit question is usually posed years after the fact. An agency that purges re-investigation records at the five-year mark to save space is destroying the evidence that it complied.

Agencies doing this work across dozens or hundreds of people quickly discover that the file is the hard part, not the check. The check takes a week. Assembling the documentation takes a records system that was designed for it, not a shared drive with inconsistent naming.

Building the Schedule: How Many Checks Per Year and What Each One Costs

The scheduling math is simple once the roster is known, and the result surprises agencies that think of the five-year cycle as a once-every-five-years event. If an agency has 200 people with CJI access, a five-year cycle produces 40 re-investigations per year on average — roughly three to four a month. That's a predictable workload, and it should be budgeted like one rather than absorbed as a surprise each time a name comes up.

Cost breaks down into three components: the fingerprint processing charge, the local records check fee, and staff time to adjudicate. The fingerprint charge is set by the state repository and varies by state and by whether the check is submitted through a live-scan vendor; agencies should confirm the current fee on their state repository's website because it changes with state fee schedules. The local records check may be free if a staff member walks the courthouse and costly if it runs through a court-records vendor per jurisdiction. The staff time is the largest and least visible line.

A worked example shows why the staff time dominates. Twenty minutes of adjudication per file across 40 files per year is about 13 hours of trained staff time — not large, but it has to be scheduled against someone's actual job, and that's the step agencies skip. When the re-investigation is folded into an existing onboarding or training cycle, the time cost is real but small. When it's treated as a special project each year, it gets deferred, and deferred re-investigations are the ones that show up in audit findings.

The scheduling rule that holds up: assign each person a fixed anniversary month, run the batch check monthly, and keep a dashboard that flags anyone approaching the five-year mark within 90 days. The dashboard is what turns a policy into a practice.

Common Scoping Failures That Survive an Audit

The failure that survives most often is the "whole-agency" re-check: the agency runs every employee through a background check once a year and considers the five-year requirement satisfied. It isn't, for two reasons. First, a blanket check rarely includes fingerprints, so it doesn't meet the biometric requirement. Second, it doesn't distinguish people with CJI access from people without, so the file doesn't document the individual re-investigation the policy asks for.

The second failure is the missing local records check, covered above but worth restating as a scoping issue rather than a method issue. The third is the contractor gap. Vendor technicians who support the records management system are often cleared at onboarding and then never re-investigated, because the agency's HR process only tracks employees. The policy language covers anyone with access, and a management control agreement should require the vendor to certify compliance, with the agency retaining the documentation.

The fourth failure is the marriage-name problem. A person who changes their legal name between investigations can pass a fingerprint check — the prints don't change — while the name-based and local court checks miss records filed under the new name. The fix is to collect a list of prior names in the re-investigation intake and search against each one. That's a one-line field on a form that saves a lot of trouble.

The fifth is the missing adjudication. The check comes back clean, the file records "cleared," and no one documents who made the decision or on what criteria. When the person's record changes and a later check returns a hit, the agency can't show what its own standard was. Write the criteria down before the first check runs.

Timing the Re-Check Around Promotions and Role Changes

The five-year calendar is the baseline, but the practical trigger to watch is the promotion. A records clerk who moves into a position that can query the state CCH repository has crossed into a role the policy treats more seriously, and the re-investigation should follow the change rather than wait for the anniversary. Many agencies handle this with a one-page access-change form that triggers a fingerprint check as a condition of the new role.

The same logic applies to temporary assignments. An officer detailed to a task force with national system access is in scope for the role, even if the detail lasts six months. The question isn't how long the access lasts, but whether the person has it. A six-month detail into a role that reaches CJI warrants the check.

The other timing issue is the break-in-service case. A person who leaves and returns after a year may have an unchanged record, but the agency can't know that without checking. The practical rule is to re-investigate any return from a break longer than the agency's continuity threshold, and to define that threshold in the written policy rather than leaving it to the supervisor's judgment.

Documenting the role change and the check together is what makes the file useful later. The question an auditor asks about a person who was promoted is not "did you re-check them" but "when and why." A one-page form with the promotion date, the new access level, the check date, and the adjudication decision answers it.

FAQ

Does a re-investigation every five years satisfy the CJIS requirement on its own?

No — the five-year cycle is the minimum, but the policy also expects a check before initial access is granted and a re-adjudication when a person's role changes to a broader access level. Many agencies run more frequently than five years because their state repository fee cycle or their own policy requires it. The requirement is not to hit five years exactly; it is to never let a person with CJI access go un-reinvestigated for longer than the policy allows. State-specific rules can be stricter than the federal baseline, and the state repository is the authority to confirm.

Can an agency substitute a commercial background check for the fingerprint-based check?

A commercial name-based check can supplement the fingerprint check but not replace it, because the policy requires a fingerprint-based search of state and national repositories. The identity match on fingerprints is what makes the result defensible; a name and date-of-birth match can return the wrong person's record or miss a person who has changed names. Agencies that rely on the commercial check alone fail the documentation test even when the outcome would have been the same. The commercial check is most useful as a backstop for records outside the state repository's coverage.

How far back should the local records check reach on a re-investigation?

The practical scope is every jurisdiction where the person has lived, worked, or attended school since the last investigation. If the last investigation date can't be confirmed, the defensible approach is the person's entire adult residence history. That's more work in the first cycle and much less work in later cycles because the agency has a documented baseline. A check limited to the person's current county misses the records that matter most in the first five years after a move.

What happens if an agency finds a disqualifying record during a re-investigation?

The agency applies its own written suitability criteria, which should be documented before any check runs, and the person's access is suspended or terminated while the review proceeds. The decision, the date, and the criteria applied go in the file. That's not a bureaucratic step — it's what distinguishes a re-investigation program from a data collection exercise. The written criteria should align with the state's standards for the role, and the agency's legal counsel should review them before the first case reaches that point.

Does the five-year clock reset if the person changes agencies?

No — the requirement follows the person's access to CJI, and a new agency must conduct its own fingerprint-based check as a condition of granting access. The old agency's file doesn't travel with the person unless the person discloses it, and the new agency shouldn't rely on a prior check it can't document. The practical result is that people who move between agencies get checked more often than every five years, which is a feature of how the policy works rather than a defect.

What's the audit risk for an agency that has the checks but not the documentation?

The audit finding usually lands on documentation, not on the checks themselves. An agency that ran every check correctly but can't produce the results, the adjudication decisions, and the signed agreements on request has the same exposure as one that skipped the checks. Build the file system at the same time as the check schedule, and treat the file as the deliverable. Records retention schedules matter here too — confirm the state's schedule before deciding how long to keep the files.

Can a vendor technician with remote CJI access be re-investigated by the vendor instead of the agency?

The vendor can run the check, but the agency remains responsible for documenting that the check happened and that the result met the agency's criteria. That responsibility is usually written into the management control agreement between the agency and the vendor, and the agreement should specify the frequency, the scope, and the documentation the vendor must provide. An agreement that says "the vendor will comply with the CJIS Security Policy" without specifying what the agency receives is the one that fails when the auditor asks for the file.

This article is general educational information and is not a legal opinion or a compliance certification for any specific agency. The CJIS Security Policy, state repository rules, and local records retention schedules change over time, and the controlling text for your jurisdiction should be confirmed with the FBI CJIS Division, your state CJIS systems agency, and qualified local counsel. Readers with compliance responsibility should consult a locally qualified professional before relying on any schedule or scope described here.