PNP-SOSIA Security Officer Exam common mistakes
PNP-SOSIA Security Officer Exam · Understand the traps and how to avoid them.
Treating a private security officer as if they hold police powers - asserting a right to detain a suspect indefinitely, force a person to answer questions, or enter a residence without consent because 'security has authority'.
Candidates transfer assumptions from police procedurals or from jurisdictions where security officers are sworn special constables. Training material about citizen's arrest and property-owner authority is often skimmed, so the distinction between the powers of a peace officer and those of a private citizen acting on private property is never firmly fixed.
What to do instead
Build a one-page powers table before the exam: for each action (arrest, search of person, search of bag, entry to premises, use of force, seizure of property) write the source of authority (citizen's arrest statute, owner/occupier consent, contract, common law) and its limit. Rehearse the phrase 'authority comes from the property owner plus the citizen's arrest provision, nothing more' and check every scenario question against that table.
Arresting on suspicion alone or delaying the arrest to keep investigating, then justifying it as 'I was still gathering evidence'.
Candidates conflate the threshold for detention or investigation with the threshold for arrest. They also fear being wrong, so they hold a person in a back room while they check CCTV instead of articulating grounds at the moment of arrest, which converts a lawful arrest into an unlawful detention.
What to do instead
Memorise and practise articulating grounds in one sentence using facts observed, not conclusions ('I saw him put the item in his jacket and pass the last payment point'). Learn the difference between reasonable grounds to arrest and reasonable suspicion to investigate, and drill the rule that once grounds exist you arrest promptly and document the grounds verbatim in your notebook at the time.
Conducting a full search of a person's pockets or bag after a shoplifting detention without consent, incident to an arrest, or any lawful basis, and calling it a 'safety check'.
Retail loss-prevention habits and peer practice normalise emptying bags in the office. Candidates do not separate a pat-down for weapons (justified by safety concerns) from a search for evidence or property (which generally requires consent, arrest, or statutory authority), so they label every search a safety search.
What to do instead
Learn the three-question test before any search: what is my legal basis, what exactly am I looking for, and how intrusive is it. Practise the consent script ('I'd like to check your bag for the missing item - may I? You can refuse') and know that refusal is not an offence and does not itself create grounds. In scenarios, state the basis explicitly in your answer; examiners award marks for naming it.
Escalating force in a step-by-step ladder (verbal, then hands-on, then baton) regardless of what the subject is actually doing, or using a technique because it worked before rather than because it fits the situation.
Candidates memorise force 'continuums' as a fixed sequence and treat them as a checklist. Under stress they default to the technique they drilled most, and they confuse the requirement that force be proportionate with a requirement that it escalate.
What to do instead
Reframe the continuum as a menu, not a ladder: the officer may move up or down at any moment based on the subject's behaviour. For each scenario, write the objective (protect self, protect others, prevent escape), the threat indicator observed, the option chosen, and why lower options were not feasible. Study case law examples where force was found unreasonable because it continued after the threat ended.
Writing incident reports that record conclusions and opinions ('subject was aggressive, appeared to be a known troublemaker') instead of observable facts, times, and exact words.
Officers write reports at the end of a long shift from memory, in a hurry, and in the same casual register they use with colleagues. They assume the reader shares their context, so they omit the sequence of events and the basis for their judgements.
What to do instead
Use a fixed skeleton every time: who, what, when (clock times), where, how, witnesses, actions taken, evidence secured, notifications made. Convert every judgement into the observation behind it ('he clenched his fists, raised his voice to a shout, and stepped within arm's length'). Write the report before end of shift, use objective language, and never include information you learned second-hand without attributing it.
Handling evidence casually - putting a seized item in a desk drawer, letting a colleague hold it, or failing to record the chain of custody because 'it's just a bottle of perfume'.
Candidates underestimate how often minor theft cases go to court or to an internal hearing, and they assume the item's value determines whether continuity matters. Busy shift handovers mean items get passed along without documentation.
What to do instead
Apply the same evidence routine to every item regardless of value: photograph in place if possible, bag and tag with date, time, location, your name and the exhibit number, record every transfer with signature and time, and store in the designated secure location. Practise writing a continuity entry so it becomes automatic, and remember that a break in continuity is what opposing counsel attacks first.
Failing to preserve and export digital evidence correctly - viewing CCTV footage without recording the export, overwriting footage past the retention window, or relying on a screenshot of a screen.
Candidates treat CCTV as something to watch rather than evidence to preserve. Retention systems overwrite automatically, and staff assume 'IT will keep it' without submitting a preservation request. Screenshots feel sufficient because they are quick.
What to do instead
Learn the preservation workflow: identify the camera and time window, submit a written preservation or export request immediately, export in native format with a hash or system-generated log where available, record the export time and operator, and keep a working copy separate from the original. Note the retention period for each system on your site and treat it as a deadline. Never substitute a phone photo of a monitor for a proper export.
Jumping straight to evacuation or to a physical intervention in an emergency without confirming the nature of the incident, the alarm zone, or whether the area is safe to enter.
Urgency feels like competence, and drills often reward speed over sequence. Candidates also lack confidence in the fire safety sequence (raise alarm, call emergency services, evacuate, assemble, account) and skip steps such as checking whether the alarm is a drill or a real activation.
What to do instead
Drill a fixed first-minute routine: confirm the alarm or report, identify location and type, raise the alarm and call emergency services with a scripted message (address, what, where, casualties, your name), then act on evacuation or containment. Learn your site's assembly points, isolation points for utilities, and the difference between a phased and full evacuation. In scenario questions, always state the notification and confirmation steps before the physical action.
Treating de-escalation as 'being nice' or as a script of calming phrases, then abandoning it the moment the person does not comply, or conversely talking so long that a deteriorating situation is not acted on.
Candidates confuse de-escalation with conflict avoidance and have no structured model, so they rely on tone alone. They also fear that any assertive action contradicts a de-escalation policy, so they freeze.
What to do instead
Learn a structured model - for example, position for safety and exit route, reduce stimuli, use the person's name, acknowledge the grievance, give clear limited choices, set boundaries with consequences, and allow time to comply. Rehearse recognising the point at which de-escalation has failed and a different response is required. In answers, show both the communication techniques and the trigger for moving to another option.
Applying screening rules inconsistently - waving through a colleague, a contractor, or a VIP, or letting a prohibited item pass because the person 'seemed fine' or the queue was long.
Social pressure and familiarity override procedure, and throughput targets make officers reluctant to stop the line. Candidates also do not know the escalation path for a refusal, so they avoid the confrontation by not screening properly in the first place.
What to do instead
Memorise the prohibited-items list and the resolution options (deny entry, surrender the item under the applicable policy, store it, or escalate to a supervisor) and the exact words to use. Practise the principle that screening is consistent or it is worthless, and that exceptions must be authorised in writing by a supervisor. For scenario questions, always name the escalation step rather than improvising a compromise.