PCG Sipahi Test common mistakes
PCG Sipahi Test · Understand the traps and how to avoid them.
Treating guard duty as passive presence: remaining seated or in one spot, not challenging unfamiliar people, and assuming 'someone else will report it', so scenario questions about active observation and intervention get answered with 'observe and do nothing'.
Candidates with prior experience at low-activity sites internalise a watch-only routine and carry it into the exam, where questions reward proactive deterrence, challenge, and escalation rather than passive monitoring.
What to do instead
For every scenario, ask 'what does the guard do in the next 60 seconds?' and prefer the answer that combines observation with a lawful, proportionate action (challenge, verify, report, escalate). Practise writing the three-step response for 20 common situations until proactive escalation becomes the default.
Confusing authentication with authorisation at the gate: accepting a valid-looking ID card or a name on a list as sufficient, and failing to check that the person is permitted for that specific area, time, and purpose.
Identity checks feel like the whole job, and candidates conflate 'this person is who they say they are' with 'this person may enter here now', especially when the visitor is confident or senior.
What to do instead
Drill the three separate questions: who are you (identity), are you expected and permitted here now (authorisation), and what are you carrying (property). For each access-control question, identify which of the three the scenario is testing before choosing an answer.
Skipping or compressing the visitor log: writing only a surname, omitting time out, failing to record the host or vehicle, or letting a regular contractor sign in 'on the way past' without a badge.
Under queue pressure, guards treat the log as paperwork rather than a security and safety record, and habitual visitors get waved through because familiarity replaces procedure.
What to do instead
Memorise the minimum data set (full name, ID checked, host, purpose, time in, time out, badge number, vehicle if any) and rehearse a 30-second sign-in script. In questions, reject any option that accepts an incomplete record or a familiar face without a badge.
Writing vague, conclusion-only reports: 'suspicious person seen, nothing further', 'all normal', or reports that state an opinion ('he looked dodgy') without time, location, description, action taken, and who was notified.
Candidates write as if reporting to a colleague who already knows the context, and they confuse a conclusion with evidence; many have never seen a report used in an investigation or disciplinary hearing.
What to do instead
Use a fixed skeleton for every report answer: when, where, who (full description), what was observed (facts only), what the guard did, what happened next, who was informed. Practise converting five opinion sentences into fact sentences, and check each report answer contains all seven elements.
Freezing or improvising at the scene of an incident: moving an injured person, entering a hazardous area without assessing it, or leaving a casualty alone to look for a supervisor instead of sending someone else and starting basic care.
Scenarios are written to feel urgent, and candidates answer with the most compassionate-sounding action rather than the safest sequence; they also forget that the guard's own safety is the first link in any rescue.
What to do instead
Learn and apply a fixed order for every emergency: scene safety, assess, call for help/raise alarm, then act within training. Rehearse 'send, don't leave' and 'do not move a casualty unless there is immediate danger' until these become automatic answer filters.
Choosing the most forceful option in a confrontation: grabbing, blocking with the body, raising voice, or pursuing a fleeing person off-site, instead of maintaining distance, using clear verbal commands, and observing and reporting.
Candidates equate authority with physical dominance and worry that backing off looks weak; exam distractors are written to reward that instinct with options like 'physically restrain the suspect'.
What to do instead
Memorise the proportionality ladder: presence, verbal request, clear warning, withdrawal and report, then police. For any use-of-force question, pick the lowest level that resolves the situation and reject any option involving pursuit off the premises or force used as punishment.
Answering legal questions with 'the guard can do whatever the client asks': searching a bag without consent or contractual power, detaining someone to 'sort it out', or disclosing personal data to an enquiring relative.
Candidates conflate customer instructions with legal authority and have not separated the roles of guard, citizen, and police; the lawful-sounding distractor is often the most confident-sounding one.
What to do instead
Build a one-page authority map: what a private guard may do (observe, record, ask, refuse entry per policy, call police), what requires consent or contract, and what only police may do (arrest, search on force, compel ID). Apply it to every legal scenario before reading the options.
Using a radio or phone badly under pressure: shouting, using slang or codes others do not share, transmitting opinions instead of facts, or failing to acknowledge and confirm a message.
Candidates treat communication questions as common sense and skip the structure, so they miss the standard sequence and the discipline of clear, brief, factual traffic.
What to do instead
Learn a transmit template (who you are, where you are, what you see, what you need) and use the acknowledge-repeat-confirm loop. Practise rewriting five rambling messages into under 20 words each, and always prefer the option with identification, location, and a clear request.
Ignoring the environmental and health layer of an incident: walking past a blocked fire exit, a spill, or a damaged light because 'that's maintenance', or failing to consider weather, lighting, and lone-working risk when planning a patrol.
Candidates separate 'security' from 'safety' and see hazards as someone else's responsibility, so they pick answers that respond to the intruder but leave the hazard unreported.
What to do instead
Adopt a rule that any hazard seen is reported and, where safe, made good or cordoned immediately. In patrol questions, check the answer covers hazard identification, reporting to the right owner, and record-keeping, and consider lighting, weather, and lone working before choosing a route or timing.
Patrolling by routine rather than by risk: fixed timings, same route every round, no check of doors, windows, and unlit areas, and no record of the round, so scenario questions about deterrence and detection are answered with 'complete the round as scheduled'.
Candidates learn patrol as a task to be finished rather than a deterrent and detection activity, and they underestimate how predictable patterns help an intruder.
What to do instead
Learn the principles: vary times and routes, check and record vulnerable points, use random checks, and log each round with time and findings. For patrol questions, prefer answers that combine unpredictability, physical verification, and documentation over answers that simply complete the schedule.