There is a conversation that happens in every guard company at least once a year. A supervisor wants to put someone on post tonight. The state check came back clean, but the company’s own screening turned up something — a dismissed charge from a decade ago, a gap in employment nobody can explain, a former supervisor who declined to comment. The post needs a body. What do you do?
The answer depends on facts nobody in the room has. But the structure of a defensible answer is knowable in advance, and most companies never build it. A security guard background check is not one process; it is two processes with different owners, different rules and different consequences for getting it wrong, and confusing them is how companies end up either putting the wrong person on post or rejecting a qualified applicant in a way that creates its own liability.
This is general orientation and not legal advice. Background screening is governed by federal consumer reporting rules, by state and local law that varies considerably — including limits on what may be considered, how far back records may be reported, when criminal history may be asked about, and what notice must be given — and by state security licensing requirements that are separate again. Requirements change. Verify with employment counsel and with your state regulator; in Texas that regulator is the Texas Department of Licensing and Regulation (TDLR). Nothing here should be used as a substitute for that.
Two screens, not one
The state licensing screen
In most states, an individual cannot work as a security officer without a registration or license, and obtaining it involves a criminal history check administered through the state — commonly with fingerprinting. The state applies its own disqualification standards, which are set by statute and rule rather than by you, and it decides. Some states publish those standards in detail; some maintain discretion; many distinguish between unarmed work and armed work, with a materially higher bar for the latter.
Two things follow. First, a state credential is a floor and not a recommendation. The state approved this person to work in the industry; it did not assess whether they should hold the keys to your client’s data center. Second, processing takes real time, and the queue is outside your control. Build the lead time into hiring rather than discovering it when a start date slips.
Your own screen
Your screening exists for a different reason: negligent hiring and negligent retention exposure, and the specific demands of the posts you sell. It typically looks at criminal history through a consumer reporting agency, employment verification, identity verification, driving records for anyone operating a vehicle on duty, and — where lawful and relevant — drug testing.
The critical point is relevance. Screening should be tied to the duties of the job. A driving record matters enormously for a patrol officer and much less for a lobby post. A financial screen might be defensible for an officer with unescorted access to a cash room and much harder to justify for an unarmed officer at a construction gate. Blanket screening applied uniformly regardless of role is both more expensive and more legally exposed than screening designed around the work.
What is typically checked, and what it actually tells you
Criminal history. The most commonly requested and the most commonly misread. Records are fragmented across jurisdictions; a single database search is not comprehensive. Dispositions matter more than charges — an arrest without a conviction is not a conviction, and treating it as one is where employers get into trouble. Many jurisdictions restrict how far back records may be reported or considered, and several restrict when in the hiring process the question may be asked at all. This is the area most heavily regulated and most locally variable.
Employment verification. Underrated. In guard work, the pattern that matters is rarely a dramatic offense; it is a series of short tenures ending in no-shows. Former employers increasingly confirm only dates and title, but dates alone reveal the pattern.
Driving records. Non-negotiable for anyone operating a company vehicle, and worth re-pulling periodically rather than once at hire. A license suspended in month seven is invisible if you only checked in month one.
Drug testing. Legally variable, increasingly so, and worth reviewing with counsel rather than carrying forward a policy written years ago.
References. Low signal for most applicants, high signal for the small number where the reference hesitates. Pay attention to what people decline to say.
Adverse action is a process, not a decision
If you obtain a background report from a third-party screening company and decide not to hire someone based even partly on what it contains, federal consumer reporting rules impose a defined process before and after that decision. The general shape is that the applicant must be told before the decision is finalized, given a copy of the report and a statement of their rights, and given a meaningful opportunity to dispute or explain what it contains — followed by a further notice once the decision is final. The specific requirements, timing and content of those notices are set by rule and are updated from time to time; confirm the current form of them with counsel and with your screening provider.
The reason this matters operationally is that it is slow by design, and hiring managers under coverage pressure will be tempted to shortcut it. Do not let the process be owned by the person who needs the post filled tonight. It should be owned centrally, run identically every time, and documented.
There is a substantive point underneath the procedural one. Many jurisdictions expect an individualized assessment rather than a blanket rule — considering the nature of the offense, how long ago it occurred, and its relationship to the specific duties of the job. That is not just compliance; it is good hiring. A guard company that automatically excludes anyone with any record will lose a lot of people who would have been excellent officers, in an industry that is always short of them.
Re-screening: the gap nobody closes
Background screening is almost universally treated as an intake event, and the officer file freezes at hire. Meanwhile the officer works for you for three years. Licenses lapse. Driving records change. Charges arise. Some states require an employer to report certain events to the regulator, and some require officers to self-report — but self-reporting depends on the officer choosing to tell you.
Decide your position deliberately: periodic re-screening for defined roles, continuous monitoring where lawful and available, or a clear self-reporting obligation in the handbook with real consequences. Whatever you choose, write it down and apply it consistently, because inconsistent application is where discrimination claims live.
The practical control that closes the gap is the same one that closes the licensing gap: eligibility has to be a live attribute of the officer record, visible at the moment someone is assigned to a post. If an officer’s driving record disqualifies them from patrol, the person building coverage at 9 p.m. needs to see that in the schedule, not in an email thread from four months ago. If a credential is suspended, the officer’s ability to work should reflect it immediately, and the mobile app they use to clock in should be governed by the same record rather than by a separate list.
Records, retention and consistency
Keep the authorization the applicant signed, the report, the notices sent, the assessment you made and the reasoning behind it. Store screening results with access limited to the people who genuinely need them — this is sensitive personal information and treating it casually is its own risk. Retention periods are set by rule and by state law; confirm yours rather than defaulting to “forever,” and confirm your disposal method too.
Then audit yourself. Pull a handful of hiring decisions from the last year and ask whether the same standard was applied to each. If the answer is “it depended on how badly we needed someone that week,” you have found the real problem, and it is not a screening problem.
If you want to see how officer eligibility, scheduling and field operations stay connected to one record, explore CGuardPro or get in touch.