Why training and licensing are a buyer's question
Most buyers treat training as the provider's internal business — something that happens before an officer appears, in a place the client never sees. That instinct is wrong for a simple reason: when an officer acts, the consequences arrive at the client's door as readily as at the security company's. A wrongful detention, an injury during an intervention, a fire door left blocked, a report so vague it cannot support an insurance claim — each of these is a training outcome, and each of them lands on the property owner too.
There is a second reason, less obvious and more expensive. Licensing status is frequently a condition inside insurance policies. If a policy requires that contracted security personnel be lawfully licensed and an incident occurs while an unlicensed officer is on duty, the exclusion is available to the insurer at exactly the moment you need the cover. That risk transfers to you silently, at signature, and becomes visible only during a claim.
So the practical stance is neither to audit a training academy nor to take a brochure at face value. It is to ask for a small number of specific documents, read them, and notice what is missing. This article sets out what those documents are, what a competent syllabus contains beyond the legal minimum, and how to check that the person standing at your entrance tomorrow is actually covered by all of it.
Verify the authorisations that apply today
Security work can be subject to authorisations that change over time and may apply differently to a provider, personnel, equipment, or a particular assignment. Ask the provider to identify the current requirement, issuing authority, evidence, scope, and validity for your proposed service. Confirm the answer with the competent authority rather than relying on this or any marketing website.
That gap is where most real-world problems live, and it is rarely malicious. An officer is hired quickly to cover a resignation. A renewal is late. A new recruit is put on shift while paperwork is “in process”. None of that is dramatic in an office; all of it means that on a given Tuesday night, the person holding your keys may not hold what the law and your insurer both assume they hold.
The contractual answer is a clause identifying which authorisations apply to the agreed service, who verifies them, what evidence is held, and how the client is notified if their status changes. Because the regulatory framework changes, confirm the requirement in force with the provider and the competent authority before deployment.
A licence is a floor, not a standard. It proves somebody outside the security company looked at this person at all — which is worth a great deal, and is not the same as competence.
What a licence proves, and what it leaves open
A licence is a floor, not a standard. It establishes that a person has been through a defined screening and is permitted to work in the field — which is genuinely valuable, because it means someone outside the security company has looked at that individual at all. It does not establish that they can write a usable incident report, de-escalate an argument at a barrier, recognise a fire-safety violation, or explain what they are not permitted to do.
This is why the interesting question to a provider is never “are your guards licensed?” — the answer is always yes and tells you nothing. The interesting question is: what does your company add on top of the licence, and can I see the syllabus? A serious operation has a written training programme that goes beyond the statutory floor, can show you its contents, and can tell you which parts were delivered to the specific officers who will work at your site.
It is also worth knowing what you are not entitled to. You cannot demand another client's records, and you should be suspicious of a provider willing to hand them over — a company casual with someone else's confidentiality will be casual with yours. What you can legitimately ask for is your own officers' records, redacted samples of the company's standard documents, and the syllabus itself. That is enough to tell a real programme from a claimed one.
The syllabus a competent company adds
Beyond whatever the law sets, a credible basic programme covers a recognisable list. Legal powers and their limits. Access control and identity verification. Patrol technique and observation. Report and occurrence-book writing. Radio and telephone discipline. Fire-safety awareness, evacuation roles, and the location and use of extinguishers. Basic first-aid awareness. Conflict de-escalation and customer-facing conduct. Emergency escalation, including when the correct action is to contact official emergency services rather than to handle something in-house.
Two items on that list are routinely underweighted and both are the ones a client feels. The first is report writing, because a report is the only part of the service that survives the night, and a badly written one converts a handled incident into an unprovable one. The second is de-escalation, because the overwhelming majority of an officer's difficult moments are not intruders — they are angry residents, delivery riders in a hurry, and visitors who feel insulted by being asked who they are.
Ask who delivers it, too, because the answer separates a training function from a filing cabinet. Is instruction given by a named trainer with operational background, by a supervisor who still works sites, or by handing a new officer a folder to read during a quiet shift? All three get recorded identically in a training log, and only two of them produce an officer who behaves differently at a barrier. Ask where it happens, how long it takes, and whether anyone watches the recruit perform a task before signing them off.
Ask how the programme is assessed, because a syllabus without an assessment is a reading list. Is there a written or practical test? What is the pass mark? What happens to a candidate who fails — retraining, reassignment, or nothing? A provider that can answer those three questions immediately is describing a system. One that cannot is describing an intention, and intentions do not survive a busy recruitment month.
The most important module: what an officer may not do
A security officer is not a police officer, and the single most valuable hour in any basic programme is the one that makes that concrete. Officers deter, observe, control access, document, and escalate. They do not conduct investigations, detain people at will, search individuals as a matter of routine, use force outside narrowly defined circumstances, or settle disputes between residents by imposing an outcome.
Get this wrong in either direction and it costs. An officer who believes they have police powers creates a liability the client will share. An officer who believes they have no authority at all will wave through the contractor who is not on the list, because refusing feels like something they are not allowed to do. The purpose of the module is not caution; it is precision — knowing exactly where the line is makes an officer more confident inside it, not less.
There is a simple field test for whether this has been taught. Ask an officer on site — politely, and with the provider's knowledge — what they would do if they saw someone taking something from a car in the car park. A trained answer describes observing, recording detail, alerting a supervisor, and contacting official services; it does not describe a chase. The answer takes fifteen seconds and tells you more than the training file.
Site induction: the training that is specific to you
General training makes an officer employable. Site induction makes them effective at your address, and it is the layer most often skipped because it costs the provider real hours before the first invoice. Induction covers the physical building, the post orders, the escalation list with names and numbers, the recurring contractors and their normal days, the residents or staff with particular needs, the alarm points, the fire strategy, and the specific rules the client cares about most.
Ask three questions about it and the answers are unusually diagnostic. How many hours of induction does an officer receive before their first unsupervised shift at my site? Who delivers it — a supervisor who knows the building, or the officer being handed a folder? Who signs it off, and can I see that sign-off sheet for the officers currently assigned to me? A provider that inducts properly will produce the sheet. A provider that does not will explain that the officer is experienced.
Induction also has to survive a substitution. When your regular officer is on leave and a replacement covers the shift, does the replacement receive a shortened induction, or do they simply arrive? This is the most common quiet failure in guarding: the contract is delivered as specified for eleven months and quietly not delivered during every relief week. Ask what the minimum induction is for a relief officer, and ask to see it recorded, which is one of the checks in the buyer's guide to choosing a security company.
Refreshers, and the decay everyone can predict
Competence is not a permanent state. Roughly six months into a posting, the site has become familiar, nothing has ever happened, and the procedures start to feel like paperwork rather than protection. Patrol routes settle into a fixed pattern. Visitor checks shorten. Report entries get briefer. Nobody decides to let standards slip; they slip because nothing in the environment is pushing back.
Refresher training is the designed counter-pressure, and it works best when it is short, frequent, and specific rather than an annual day in a classroom. A fifteen-minute briefing on one topic, delivered on site by a supervisor, is worth more than eight hours once a year — because it happens where the work happens and it can respond to what the site is actually getting wrong this month. Ask for the refresher calendar with real past dates on it, not a policy statement about frequency.
The other half of the counter-pressure is supervision, which is why training and supervision should be assessed together rather than as separate line items. Training establishes what good looks like; supervision is what detects that it has drifted and resets it. A provider strong on one and absent on the other will deliver a service that is excellent in month one and unrecognisable in month eight — the failure mode described in the guide to supervision and accountability.
How to verify, in one afternoon
The whole verification fits into a short document request: the current authorisations identified for the agreed service; written confirmation of their scope and validity; the training syllabus; dated records for the proposed personnel; the site-induction sign-off; the refresher calendar; and a redacted incident-report example.
Read them for three things: dates, names, and gaps. Dates tell you whether this is current or historic. Names tell you whether the records describe the people actually working at your site or the company in the abstract. Gaps tell you the rest — a syllabus with no assessment, an induction sheet with no signature, a refresher calendar whose only entries are in the future. None of this requires security expertise. It requires twenty minutes and a willingness to notice an empty field.
Finally, treat this as a recurring check rather than a one-off at tender. Licences expire, officers change, and a file that was complete in March is not necessarily complete in November. Building the review into a quarterly service meeting turns it from an accusation into a routine, which is both easier to sustain and far more likely to catch the gap while it is still small. If you are specifying a guarding contract from scratch, the professional security guarding page sets out how the pieces fit together, and security consulting covers the cases where the specification is itself the deliverable.
- Evidence that means something
- A dated record naming your officers
- Evidence that does not
- “All our staff are fully trained”
- Evidence that means something
- A syllabus with an assessment and a pass mark
- Evidence that does not
- A list of course titles on a slide
- Evidence that means something
- A signed induction sheet for your building
- Evidence that does not
- “The officer is very experienced”
- Evidence that means something
- A refresher calendar with past dates
- Evidence that does not
- An annual training policy document
- Evidence that means something
- An officer who can state what they may not do
- Evidence that does not
- A uniform and a confident manner
- Evidence that means something
- A defined induction for relief officers
- Evidence that does not
- A replacement who simply arrives
Practical checklist
- The company's current authorisation to provide security services, seen rather than described.
- A contract clause identifying the applicable authorisations, evidence, validity, and change-notification process.
- The written training syllabus — and whether it is assessed, with a pass mark and a consequence for failure.
- Report writing and de-escalation present on the syllabus, not assumed.
- A module on the limits of the role — what an officer may never do — and officers who can state it.
- Dated training records for the specific officers assigned to your site, not company-level totals.
- Site induction hours, who delivers them, and a signed sign-off sheet for your building.
- A defined minimum induction for relief officers — the gap that opens during every leave week.
- A refresher calendar with real past dates, not a stated frequency.
- The fifteen-second field test: ask an officer on site, with the provider's knowledge, what they would do — and would not do — if they saw a theft in the car park.
- The whole review repeated quarterly, because licences expire and officers change.
Related services
See today's conditions across Lebanon on the CIS Lebanon Security Index™.
Ready to talk about protecting your site, your people, or your operation?
Browse all services