PSARA Supervisor Exam common mistakes
PSARA Supervisor Exam · Understand the traps and how to avoid them.
Answering licensing questions from general impressions of how private security 'usually works' rather than from the specific statutory provisions governing PSARA licence grant, renewal, and conditions.
Candidates with field experience assume operational practice mirrors legal requirement, and skip the precise wording of the Act and Rules on eligibility, fee, and validity periods.
What to do instead
Build a one-page statutory map for each licensing topic (who may apply, eligibility disqualifiers, documents, validity, renewal window, consequences of lapse) and recite it from memory before attempting practice items.
Confusing the roles of the licensing authority, the controlling authority, and the police when answering questions about who grants, renews, suspends, or cancels a licence.
The terms sound interchangeable and candidates memorise duties without attaching each duty to the correct office.
What to do instead
Create a three-column table (authority / power / statutory source) and test yourself by covering one column at a time until each power is matched to the right office without hesitation.
Treating the supervisor's job as 'standing at the post with the guards' instead of describing the supervisory cycle of briefing, deploying, spot-checking, and debriefing.
Candidates answer from their own shift experience, which often involved static guarding rather than documented supervision.
What to do instead
Practise writing a supervisor's shift routine as a timed sequence (pre-shift briefing, post allocation, mid-shift checks, relief management, end-of-shift report) and use that sequence as the skeleton for every supervision answer.
Designing deployment answers that ignore threat assessment and site survey, jumping straight to the number of guards and post locations.
Candidates default to staffing arithmetic because it feels concrete, while survey and risk grading feel abstract.
What to do instead
For every deployment question, force yourself to write the survey step first (assets, vulnerabilities, access points, lighting, perimeter) and only then justify manpower from those findings.
Describing access control as a single checkpoint rather than a layered system covering perimeter, reception, internal zones, and material movement.
Candidates picture the main gate they know from their own site and generalise it to every scenario.
What to do instead
Memorise a layered model (perimeter, building entry, restricted zones, escorted movement, exit verification) and answer by walking through each layer in order.
Writing incident reports that mix observation with opinion, omit time stamps, or fail to record the sequence of events and the action taken.
Candidates write reports the way they speak, narrating conclusions ('the visitor seemed suspicious') instead of facts.
What to do instead
Practise the five-part report structure (who/what/when/where/action taken) and rewrite sample narratives until every sentence is either a verifiable fact or a clearly labelled inference.
Applying use-of-force answers that jump to the highest available response without addressing necessity, proportionality, and the graduated options below it.
Candidates conflate 'authority to use force' with 'duty to use force' and answer in absolutes.
What to do instead
Answer every force question using a fixed ladder (presence, verbal, physical, intermediate, extreme) and state explicitly why each lower rung was insufficient before justifying the rung chosen.
Ignoring the legal exposure of the supervisor personally, discussing only the company's liability when a guard acts improperly.
Candidates think of liability as a corporate matter and overlook personal and vicarious responsibility chains.
What to do instead
For each liability scenario, map responsibility at three levels (guard, supervisor, licensee) and identify the specific failure at each level before concluding.
Treating guard welfare obligations (rest, relief, equipment, training records, grievance handling) as optional good practice rather than mandatory supervisory duties.
Welfare topics are perceived as 'soft' and are skipped during revision in favour of enforcement topics.
What to do instead
Keep a checklist of welfare duties and rehearse answering welfare questions in the same structured way as security questions, citing the duty, the supervisor's action, and the record kept.
Answering audit and record-keeping questions by listing documents that should exist without explaining verification, retention, or corrective action on findings.
Candidates memorise registers as a list and never practise the audit cycle of check, record, escalate, and close out.
What to do instead
Rehearse a four-step audit answer (what is checked, against what standard, how the finding is recorded, what corrective action and follow-up follow) and apply it to each register or log named in the syllabus.