Continuous background check monitoring is an ongoing service that flags new criminal, court, or licensing activity on an employee as soon as it is reported, rather than waiting for a scheduled rerun of the full check. A one-time background check is a single snapshot taken at hire. Continuous monitoring adds a standing watch on public record sources between full checks, so an arrest or new filing can surface within days instead of at the next annual review.
The distinction matters for risk management and legal compliance. This guide covers how monitoring works, how it compares to a rescreening schedule, what the FCRA requires around consent, why an alert is not the same as a confirmed record, and which industries treat ongoing checks as close to mandatory.
How continuous criminal record monitoring works
Continuous monitoring is not a single technology. It is a layered process that combines automated data feeds with a manual verification step before anything reaches a hiring manager or supervisor.
Arrest and booking data feeds
Monitoring providers pull daily or near real time feeds from county jail booking systems, state repositories, and other law enforcement data sources, surfacing new arrests tied to a monitored name and date of birth. Booking data is fast but noisy: incomplete case numbers, common name mismatches, and charges later dropped or reduced are common, which is why a booking alert alone is never treated as a final result.
Court record alerts
Separate from booking feeds, monitoring systems track county and state court dockets for new filings, case updates, and disposition changes tied to a monitored individual. Court alerts tend to lag bookings by days or weeks, since cases have to be filed and indexed, but they carry more legal weight because they reflect an actual charge rather than a detention event.
Verified confirmation before action
Every credible screening program treats an automated alert as a lead, not a finding. Before any information is shared internally or acted on, it has to be confirmed against the original source, the actual court record or registry entry, to rule out mismatched identities, sealed or expunged cases, and clerical errors. This confirmation step is what separates a monitoring service that protects an employer from one that creates legal exposure through inaccurate reporting.
Continuous monitoring versus periodic rescreening
Periodic rescreening runs a full background check again on a fixed schedule, commonly annually or every two to three years. It uses the same process as the original hire check and reruns it against current databases.
The practical tradeoffs:
- Timing. Rescreening only catches what happened since the last cycle, so an incident early in the cycle may sit unnoticed for months. Monitoring surfaces new activity closer to when it happens.
- Coverage depth. A rescreen typically repeats the full scope of the original report. Monitoring is usually narrower, focused on criminal and court alerts, unless other data sources are added.
- Cost pattern. Rescreening is billed per rerun, so cost scales with frequency. Monitoring is usually a flat ongoing fee per employee. Employers comparing the two should look at total cost across the full population rather than estimating.
- Administrative load. Rescreening requires someone to schedule and review each cycle. Monitoring runs in the background and only creates work when an alert needs review.
Many employers use both, a scheduled rescreen for full-scope coverage plus monitoring in between to close the timing gap. Whether that combination makes sense depends on the role and what a missed incident would cost the organization. Reveal’s background check pricing page shows how ongoing monitoring is typically structured next to one-time and rescreening options.
The consent question: does one-time consent cover ongoing checks
This is the point where employers most often assume they are covered when they are not. The FCRA requires that before a consumer report is procured for employment purposes, the employer give the applicant or employee a clear, written, standalone disclosure that a report may be obtained, and get written authorization from that person, as set out in 15 U.S.C. 1681b and explained in the FTC’s guidance for employers, Using Consumer Reports: What Employers Need to Know. That guidance is direct about the mechanics: notify the person in writing, in a standalone document, and get written permission, which can be part of that same document, before a report is pulled.
None of that federal language was written with real time monitoring in mind, and it does not spell out whether a single signature at hire authorizes checks that continue for years afterward. Legal analysis of continuous monitoring programs concludes that under federal law a single signed authorization can cover ongoing monitoring for the duration of employment, but only if the disclosure itself says so, meaning it states clearly that reports may be obtained throughout employment, not just at the point of hire.
This is sometimes called an evergreen authorization: language covering both the pre-hire check and any later checks without a new signature each time. The gap is that some states do not accept this approach and require fresh consent before each new report, so a one-time authorization that satisfies federal law is not enough on its own in those states. Employers rolling monitoring out across multiple states should treat this as a state-by-state compliance question and have counsel confirm the authorization language covers ongoing checks everywhere it will be used.
Why alerts must be confirmed at the source before any adverse action
An automated hit from a booking feed or court docket alert is not a verified background check result, and treating it like one is a fast way to act on bad data. Booking data can reflect an arrest that never led to charges, a case later dismissed, or a name and date of birth match belonging to a different person entirely.
Before any alert influences a real decision, it has to be confirmed directly against the underlying court or agency record. If, after confirmation, the record supports adverse action such as suspension or termination, the same FCRA steps that apply to any consumer report apply here: a pre-adverse notice with a copy of the report and a summary of rights, a reasonable waiting period, and a final adverse action notice if the employer proceeds. The FCRA does not set an exact number of days for that waiting period, only that it be reasonable, which is why a written adverse action procedure beats deciding case by case.
Industries where ongoing monitoring is mandated or high value
Transportation
Transportation is the clearest case of monitoring being a legal requirement rather than a best practice. Under 49 CFR 382.701, employers of CDL drivers must query the FMCSA Drug and Alcohol Clearinghouse at least once per year for every CDL driver they employ, on a rolling twelve month basis from each driver’s last query date. A pre-employment query within the past twelve months satisfies that year’s requirement, and a limited query can too, though employers must first get general consent from the driver before running one. It is effectively a mandated form of ongoing monitoring built into federal motor carrier regulation. Reveal’s page on FMCSA Clearinghouse queries covers how employers stay current on this requirement across a driver roster.
Healthcare
Healthcare employers are expected to routinely check staff against federal and state exclusion lists, since employing an excluded individual can jeopardize an organization’s ability to bill federal healthcare programs. Because those lists update on an ongoing basis, a one-time check at hire does not protect an employer from someone being added later. Reveal’s overview of FACIS levels explains how the tiers of sanction and exclusion screening work, and the healthcare background check page covers how ongoing monitoring fits into a compliant program.
Childcare and education
Roles involving direct, unsupervised contact with children carry an unusually high cost if a new disqualifying record goes unnoticed between screening cycles. Many state licensing frameworks already require periodic rechecks, and ongoing monitoring extends that same risk logic between cycles.
Finance
Financial services roles with access to funds, accounts, or sensitive customer data carry similar reasoning. A new fraud, theft, or financial crime charge that would have disqualified a candidate at hire is just as relevant after they are already employed and still have that access.
Rollout checklist for employers
- Confirm whether the role has a mandated monitoring or requery requirement, such as FMCSA Clearinghouse queries for CDL drivers, before building a voluntary program.
- Update disclosure and authorization language so it explicitly covers ongoing checks during employment, not only the pre-hire check.
- Check state-specific consent rules before assuming one signature at hire covers every state the company operates in.
- Define in writing what counts as a confirmable alert, who reviews it, and what source verification is required before any internal action.
- Build a documented adverse action process: pre-adverse notice, reasonable waiting period, final notice, so alerts are handled the same way every time.
- Decide whether monitoring replaces, supplements, or runs alongside rescreening, and set that policy per role rather than company-wide.
- Revisit vendor pricing and scope periodically as headcount and role mix change.
Frequently asked questions
Does continuous monitoring replace the need for a background check at hire?
No. Continuous monitoring is designed to run after an initial pre-hire background check, not instead of one. It catches new activity that happens during employment; it does not establish the baseline record review that hiring decisions are typically based on.
Is a one-time signed authorization enough to cover ongoing monitoring?
Under federal law, a single signed authorization can cover ongoing monitoring for the duration of employment, but only if the disclosure explicitly states that reports may be obtained throughout employment, not just at hire. Some states require fresh consent for each report regardless of what the federal authorization says, so multi-state employers need to check state rules rather than relying on one national form.
Can an employer act on a monitoring alert right away?
No. An alert from a booking feed or court docket is a lead that has to be confirmed against the original source record first. Booking data in particular can include dropped charges or mismatched identities. Once a record is confirmed, standard FCRA adverse action steps, including a pre-adverse notice and a reasonable waiting period, still apply before any final decision.
Which industries are required to run ongoing checks rather than just choosing to?
Transportation is the clearest example. Employers of CDL drivers must query the FMCSA Drug and Alcohol Clearinghouse at least once per year for each driver under 49 CFR 382.701. Healthcare exclusion list checks function similarly in practice, since exclusion lists update continuously and a lapsed check can create billing and compliance exposure even without a single explicit annual mandate.
This article is general information for employers and is not legal advice. Background screening and monitoring programs should be reviewed with qualified counsel, particularly for state-specific consent requirements.
