A security guard onboarding checklist that starts before day one

Most onboarding checklists assume the clock starts on day one. Send the offer, prep the desk, run orientation, check in at 30, 60, and 90 days. That’s roughly the shape of most first-time hiring checklists, and it works fine for a coordinator or a cashier.

It doesn’t work for a security guard, because the part of onboarding that actually protects you happens before day one. If you’re building a security guard onboarding checklist off a generic HR template, you’re missing the step that carries the most risk: confirming the person you’re about to put on a post is legally allowed to be there.

We’ve seen small businesses and small security staffing agencies run into this the same way, over and over. Someone gets hired, gets a badge and a schedule, and starts a shift before anyone has actually confirmed their license is current, their post orders exist in writing, or they know what to do the first time a situation gets tense. None of that shows up on a standard new-hire checklist, because a standard new-hire checklist wasn’t written for a role where the wrong day-one mistake is a legal one.

What a generic 30/60/90 template misses for a security role

A generic checklist is built around ramping someone up: paperwork, a desk, an intro to the team, a few check-ins to see how it’s going. That’s a performance framework. It assumes the biggest risk is a slow start.

For a guard, the biggest risk usually isn’t a slow start. It’s a guard on a post who shouldn’t be there yet.

• An unverified or lapsed license. A generic checklist has “collect ID and paperwork” somewhere in week one. It doesn’t have “confirm the state registry actually shows this license as active, not expired, and covers the duties you’re assigning.”
• No site-specific training. A guard who did the state-mandated coursework still doesn’t know your building’s evacuation route, your visitor policy, or who to call if the alarm goes off at 2am. That’s not covered by any state exam.
• No documented use-of-force sign-off. If something happens on a shift and there’s no signed record that the guard was trained on your policy and agreed to it, you’re defending the incident with nothing in writing.
• No shadow shift. The first time a new guard handles a radio call, checks a badge, or writes an incident report, it’s often for real, with nobody watching, because nobody built in a supervised rep first.

Each of these is a gap a generic checklist doesn’t ask about, because it isn’t built for a role where a document has to exist before the person can legally work.

Verify the license and permit before you schedule a single shift

This is the part that has to happen before onboarding starts, not during it.

Security guard licensing is state-regulated, and the requirements vary enough that you can’t assume one state’s rule tells you anything about another. California requires roughly 40 hours of guard-card training split across pre-registration and post-registration blocks, with annual continuing education on top of it, all tracked through the Bureau of Security and Investigative Services. Other states set a much lower bar for an unarmed role.

Armed positions almost everywhere require additional firearms certification and a higher minimum age, on top of the base license. A license issued in one state generally does not transfer to another, so a guard moving states starts the process over.

That range is exactly why “check the license” can’t be a box on a form. Before you schedule anyone’s first shift, verify three things directly:

• The license or registration is active, checked against the issuing state’s registry, not just a photo of the card.
• It covers what you’re actually assigning them to do. An unarmed registration doesn’t cover an armed post, and a license for one jurisdiction doesn’t automatically cover work in another.
• The renewal date is far enough out, or already on your calendar, so a guard doesn’t quietly go out of compliance mid-assignment.

For a small agency running guards across multiple clients or states, this step alone is worth building into your screening process rather than your onboarding process, so it happens before an offer goes out, not after someone’s already shown up for orientation. Structured qualification questions at the application stage (license number, state, expiration date, armed/unarmed status) catch a mismatch before you’ve invested a full onboarding cycle in someone who can’t legally start, the same logic behind running a background check before an offer instead of after one.

The first 30 days: post orders, radio procedures, and shadow shifts

Once the license is verified, the first 30 days are about making sure a guard can actually do the job on your specific site, under your specific procedures, not just in general.

Post orders and site-specific training

Post orders are the written instructions for a specific post: what to check, when, what’s off-limits, who to call, and what “normal” looks like at that site so a guard can recognize when something isn’t. If your post orders live in someone’s head instead of on paper, write them down before the new hire’s first shift, not during it.

A new guard should read the post orders, walk the site with a supervisor or a senior guard, and confirm they understand the specifics that don’t show up in any general training: where the panic buttons are, what the visitor sign-in process actually looks like in practice, which doors alarm and which don’t.

Radio protocol and incident-report procedures

Radio discipline and incident reporting are skills, not instincts. A guard who’s never used your radio codes or your incident-report format will improvise the first time it matters, and improvising during an actual incident is exactly what you’re trying to avoid.

Cover this in week one: how to check in and out, how to call for backup, what counts as an incident worth logging, and what a complete incident report includes. Have the new hire write a practice report on a non-event (a delivery, a routine walk-through) before their first real one, so the first time they fill out the form for something that matters, it’s not also the first time they’ve filled out the form at all.

Use-of-force and de-escalation policy sign-off

This is the step most likely to get skipped, and the one you can least afford to skip. Every guard should read your use-of-force and de-escalation policy, discuss it with a supervisor, and sign a document confirming they understand it, before their first solo shift. Not after. Before.

If a situation ever escalates on one of your sites, the question won’t just be what the guard did. It’ll be what they were trained to do and whether you can prove it. A signed policy acknowledgment, dated before the first shift, is the single piece of paper that answers that question.

Shadow shifts

Pair every new guard with an experienced one for at least a few full shifts before they work alone. This isn’t about watching someone stand at a post. It’s about giving them a supervised rep at the specific moments that go wrong when they’re unsupervised: the first radio call, the first visitor who pushes back on the sign-in process, the first time something looks slightly off and they have to decide whether it’s worth escalating.

How many shadow shifts is enough depends on the site. A guard on a quiet single-tenant office building needs less than one covering a large retail site with a high volume of foot traffic and a real chance of an incident in the first month. Set a minimum, and let the shadowing supervisor sign off that the new guard is ready, rather than defaulting to a fixed number regardless of the site.

Days 31 to 90: from shadowed to accountable

The second and third months shift from supervised to independent, with checkpoints instead of constant oversight.

Days 31-60: the guard works independently, with a supervisor doing spot checks rather than full shadow shifts, unannounced site visits, and a review of any incident reports they’ve filed on their own. This is where you catch the difference between “understood the training” and “actually applies it under real conditions.”

Days 61-90: full site certification, plus a 90-day check-in that covers performance and confirms nothing about their compliance status has changed since day one. Put the license renewal date on a calendar you actually check, not just in a file. Licenses lapse quietly, and a guard who was fully compliant at hire can drift out of compliance eight months later if nobody’s tracking the date.

Isn’t this overkill for a two-guard crew?

If you’re a small business with one or two guards, or a small agency placing a handful of people at a time, this can feel like a lot of process for a small operation. It’s a fair question, and the honest answer is that the risk doesn’t scale down with headcount.

One guard with a lapsed license or no documented use-of-force training is the same liability exposure whether you have two guards or two hundred. Your insurer and your clients care about the same paperwork either way. A staffing agency’s contract with a client typically requires proof that every guard placed on that site meets licensing and training requirements, and that requirement doesn’t shrink because the agency is small.

What scales down is the ceremony, not the substance. A two-guard operation doesn’t need a formal HR system to run this checklist, and it doesn’t need a recruiter to build it, either. It needs the same screening and onboarding discipline an owner-operator can run alone: verified license before the first shift, post orders and use-of-force sign-off in the first week, a shadow shift before solo work, and a renewal date somewhere you’ll actually see it.

Push the verification earlier, into how you screen

The pattern underneath all of this is the same one that shows up across hiring for small security staffing agencies: the fixes that actually reduce risk happen earlier than most people build them in. Onboarding checklists catch problems after an offer’s already out. Screening catches them before one goes out at all.

That’s where it’s worth pulling license verification and judgment checks into how you screen, not just how you onboard. Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, and for a security role, all three do something specific. Structured qualification questions at the application stage ask for license number, state, and expiration up front, so a mismatch surfaces before you’ve scheduled an interview.

A one-way interview lets you ask every candidate the same de-escalation scenario and hear how they actually talk through it, instead of guessing from a resume how someone handles a tense situation. A situational judgment assessment built around how your team actually wants a guard to respond adds a third check on the same judgment a use-of-force sign-off only confirms on paper.

None of that replaces the onboarding checklist above. A verified license at the application stage still needs a post-order walkthrough and a signed use-of-force acknowledgment before day one. But it means fewer surprises land in week one, because the compliance questions got asked when there was still time to walk away from a bad fit instead of scrambling to fix it after someone’s already on the schedule. See how the credit-based plans work on the pricing page; Starter runs $49 a month with a 7-day free trial and no card required, which is enough to screen a handful of guard roles before you decide whether it’s worth building into your process.

The checklist doesn’t fix a bad hire. It exposes one early enough to matter

A 30/60/90-day plan for a security guard isn’t really about ramping someone up the way it is for most roles. It’s about creating a paper trail that proves, at every stage, that the person on your site is licensed, trained on your specific procedures, and has agreed in writing to your policy on force. None of that happens by accident, and none of it happens on day 30 if you didn’t start it before day one.

The businesses and agencies that get burned aren’t usually the ones that skipped the checklist entirely. They’re the ones that ran it start to finish, but started the clock a week too late, after the guard was already on a post the license didn’t quite cover. Move the verification earlier, and the rest of the checklist does what it’s supposed to: catch the small gaps before they become the kind of incident that ends up in a report nobody wants to write.

Frequently asked questions about security guard onboarding

How long does it take to get a security guard license?

It depends entirely on the state and whether the role is armed or unarmed. Requirements range from a few hours of coursework in some states to around 40 hours split across pre- and post-registration training in states like California, where the Bureau of Security and Investigative Services sets the requirement. Armed roles almost always require additional firearms certification. Check the issuing state directly rather than assuming one state’s timeline applies to another.

Do security guards need CPR or first aid certification?

Some sites and some states require it, but it isn’t universal. Whether you require it should depend on the site: a guard at a facility with heavy foot traffic or medical risk benefits more from CPR certification than one monitoring an empty warehouse overnight. If a client contract or a state rule requires it, verify the certification is current during onboarding, the same way you verify the guard license.

What is a post order?

A post order is the written set of instructions for a specific security post: what to check, how often, what counts as normal versus something worth escalating, and who to contact in specific situations. Every site should have its own post orders, and every new guard should walk the site and review them with a supervisor before working that post alone.

How many shadow shifts should a new guard work before going solo?

There’s no universal number, and the honest answer depends on the site’s complexity and risk level. A guard on a quiet single-tenant office needs fewer supervised shifts than one covering a high-traffic retail site. Set a minimum for your operation, and have the shadowing supervisor sign off that the guard is ready, rather than defaulting to a fixed count regardless of the post.

Do unarmed guards need use-of-force training?

Yes. Unarmed doesn’t mean force never comes up; it means the guard isn’t carrying a firearm. Nearly every state requires some form of use-of-force and de-escalation training for unarmed guards, and every employer should have the guard sign an acknowledgment of the site’s specific policy before their first solo shift, regardless of what the state minimum requires.