BC Advanced Security (AST) common mistakes
BC Advanced Security (AST) · Understand the traps and how to avoid them.
On an arrest scenario, the candidate writes that a guard may arrest for any offence - including a summary offence like shoplifting - anywhere the guard happens to be, on the basis that 'a citizen can arrest for a crime in progress.'
Candidates collapse three different powers into one: the general citizen's power in s.494(1) of the Criminal Code (limited to indictable offences), the occupier/authorized-agent power in s.494(2), and police powers under s.495. Prep material written in plain language ('citizen's arrest') hides the distinction.
What to do instead
Answer two questions before writing anything: whose power is being used, and what category of offence is it? Any person = indictable offence found being committed (or reasonable grounds to believe one was or is about to be committed). Owner or authorized agent of the property = any criminal offence found being committed on or in relation to that property, followed by forthwith delivery to a peace officer. Practise writing both tests out in one sentence until they stop blending.
Cites the wrong statute or regulator - naming out-of-province security legislation or federal privacy law as the authority governing a BC guard's licence, conduct, or how a BC contract security company handles client personal information.
Much of the study material circulating online is written for other jurisdictions, and privacy statutes are the most commonly confused set (private-sector vs. public-sector vs. federal).
What to do instead
Build a one-line statute map and rehearse it: provincial security services legislation and its regulation govern licensing, training and conduct of guards in BC; BC's private-sector privacy statute governs how a private security company collects, uses and discloses personal information; the public-sector privacy statute governs public bodies such as hospitals, schools and municipal facilities. When a scenario names an employer type, state which privacy law attaches before analysing.
In a written scenario, the candidate jumps straight to a physical control technique - handcuffing, an escort hold, a takedown - on a subject who is only arguing, refusing to answer questions, or going limp, and lists no verbal de-escalation or lesser option before it.
Scenarios are written to feel urgent, and candidates treat any non-compliance as danger. 'Non-compliant' gets read as 'assaultive' because the behavioural categories were memorised as a list rather than as a decision rule.
What to do instead
Always name the subject's actual behaviour first using the continuum categories (cooperative / passive / active resistance / assaultive), then select the least intrusive option that fits that category, then write what de-escalation was attempted and why it did not work before any hands-on step. If your answer contains force and no failed-de-escalation sentence, you have skipped a step.
After describing a prone restraint or a handcuffing, the answer ends at 'subject controlled' - subject left face-down, no repositioning, no breathing check, no monitoring, no medical response.
The physical task (getting the cuffs on) feels like the finish line, and the risk that follows is invisible and undramatic compared with the struggle itself.
What to do instead
Every restraint answer closes with a fixed recovery sequence: reposition out of prone to sitting or recovery position as soon as it is safe, monitor breathing and level of consciousness continuously, never leave the person unattended or alone with a single guard out of view, treat severe agitation or a sudden calm as a medical emergency and summon EMS, and record times for each step. Say the sequence out loud in the same order every practice answer.
Writes the risk assessment as a single item completed at the start of a shift or before an event, then keeps that same plan unchanged while the situation shifts - a crowd grows, lighting fails, a hostile person arrives, or the exits become blocked.
Risk assessment is taught as a document to fill in, so it gets filed as a task rather than treated as a loop that runs continuously.
What to do instead
Structure every answer as a loop, not a list: identify hazards, assess likelihood and impact, apply controls, then re-assess. Name at least one concrete trigger for re-assessment and the revised control it produces (for example: crowd exceeds posted capacity, so entry is held and the secondary exit is opened and staffed). If your answer has no re-assessment trigger, it is incomplete.
Writes conclusions instead of observations: 'the male was aggressive and I feared for my safety,' with no words spoken, actions taken, distance, time, or description of what the guard did first.
Everyday narrative habits favour conclusion, and conclusions feel persuasive. Report templates with fields like 'brief description' actively reward compression.
What to do instead
Use a fact → interpretation → action structure in every paragraph: what you saw and heard (quote the words), what you concluded from it, what you did. Any opinion must be followed immediately by the observable basis for it. Run the test: could a reader who was not there picture the scene and tell the guard's conduct apart from the subject's?
Treats notes as scratch work: rewrites them neatly afterwards, leaves the time of first contact out, and omits a use-of-force entry from the report because 'it was minor' - for example a brief escort hold or a wrist lock used to move someone.
Notes feel personal and private, minor force does not feel like an event worth recording, and candidates underestimate that the report is the accountability record that will be read by a supervisor, a regulator, or a court months later.
What to do instead
Notes: contemporaneous, in the prescribed format, chronological, every entry timestamped, errors struck with a single line and initialled, never rewritten, recopied or destroyed. Any force used, however brief, gets documented with what was applied, why, duration, injuries observed and aftercare given. State in your answer who reviews the report and why retention matters.
Expands the guard's authority in a scenario - searching a bag without consent or legal authority, detaining someone to recover a debt or 'teach them a lesson', giving legal advice, or using the position to obtain personal favours or access.
Candidates want to resolve the problem helpfully, and popular media models a security role with far broader powers than a BC guard actually has. The line between contract authority, occupier authority and police authority is rarely drawn explicitly.
What to do instead
State the boundary and immediately pair it with the alternative that is available: 'I do not have authority to do X; what I can do is Y.' Searches only where a lawful authority or informed, voluntary, revocable consent exists - and consent is not consent if it is obtained by assertion of authority. No detention to resolve a civil or contractual matter; hand it to police or to management.
Gives a radio transmission with no identifier, no location and no request - 'yeah, I've got a problem out here' - or takes the earpiece out and handles the situation alone without telling anyone.
Nerves and urgency shorten the message, and the candidate assumes the listener can see what they can see. The radio gets treated like a phone call to a person rather than a broadcast to everyone.
What to do instead
Use one fixed order every time: who you are calling, who you are, exactly where you are, what is happening, what you need. Keep it under fifteen seconds. If you must disengage from the radio, say so and set a check-in time so a missed check-in becomes the trigger for assistance.
Describes walking up to a person or entering a room with no scan, no exits identified, no cover noted, no notification to dispatch or supervisor, and no plan for what to do if the contact goes wrong.
Tunnel vision on the subject, plus a sense of urgency that makes the pre-checks feel like delay. Candidates assume backup is implied by the scenario rather than stated in the answer.
What to do instead
Before contact, write the pre-checks as explicit observations: exits, hazards, number of people present, my position relative to cover, who knows where I am, and my disengagement route. Then add one pre-planned trigger in the form 'if X happens, I will Y.' Answers that begin with contact and never mention positioning lose marks even when the force decision itself is correct.