NZ Crowd Controller COA common mistakes
NZ Crowd Controller COA · Understand the traps and how to avoid them.
Treating the crowd controller's authority as if it were a police power - saying they can 'arrest', 'detain for questioning', or 'search' a patron as a matter of course - rather than describing the narrow statutory and common-law basis for touching or holding a person.
Candidates absorb the language of policing from media and from security-adjacent workplaces, and the COA syllabus overlaps with law-enforcement vocabulary, so they assume the powers are identical. They also conflate the licensed crowd controller role with the private security firm's contractual authority to refuse entry or remove a trespasser.
What to do instead
Learn the distinction explicitly: a crowd controller is a private citizen with a property owner's delegated authority to refuse entry, require a person to leave, and use reasonable force to remove a trespasser or defend persons and property. Practise writing the lawful basis for each action in one sentence ('asked to leave under the licensee's authority; refused; used minimum force to escort out') until the phrasing is automatic. Check the specific statutory wording for your jurisdiction and cite it by name rather than saying 'I can arrest them'.
Jumping straight to a physical response - moving in to grab, push, or 'escort' a person during a verbal dispute - without first attempting verbal de-escalation or giving a clear direction and a chance to comply.
Under time pressure and adrenaline, candidates rehearse the physical technique they practised in training and skip the communication steps, because those feel passive and slow. Scenario questions that describe a heated but non-violent argument tempt candidates to 'deal with it' decisively.
What to do instead
Use a fixed ladder in every answer: assess, engage verbally, give a clear lawful direction, allow an opportunity to comply, then escalate only if compliance fails and there is an immediate risk. In written answers, explicitly name the de-escalation step taken and the words used, then justify escalation by reference to a change in behaviour or risk, not by the person's attitude.
Writing incident reports that record conclusions and opinions ('patron was aggressive and drunk', 'he was being a nuisance') instead of observable facts, quoted words, times, and actions taken.
Candidates write reports as a narrative summary for their supervisor rather than as a contemporaneous record that may be read in court or at a licensing hearing. They also compress events to save time at end of shift, losing sequence and detail.
What to do instead
Report in the pattern: time, location, who was present, what was said (in quotation marks where possible), what was observed through the senses, what action was taken, and who was notified. Replace every adjective with the behaviour that prompted it - not 'aggressive' but 'clenched fists, stepped within arm's length, said "I'll smash you"'. Record the report before end of shift and note any CCTV coverage, witnesses, and injuries.
Describing use of force only in terms of the outcome ('we removed him') without addressing necessity, proportionality, minimum force, and the point at which force stopped.
Candidates think the question is asking whether the removal was successful, or they assume that because the person was trespassing, any level of force was lawful. They also do not distinguish between force used to remove a trespasser and force used in self-defence, which have different justifications.
What to do instead
For every force scenario, answer four things: what lawful purpose was being pursued, why lesser options were not sufficient, why the force used was the minimum reasonably necessary in the circumstances, and what was done once the risk ended (release, check for injury, first aid, handover). Note that force must stop as soon as resistance ceases, and that continuing force after compliance is itself an offence.
Failing to recognise crowd crush and density hazards - treating a packed queue or a surge at a barrier as 'busy' rather than as a developing risk - and not identifying the specific interventions available (flow control, opening routes, stopping entry, communicating with the event control room).
Crowd density risk is counter-intuitive: the danger is not panic but progressive loss of individual movement, and candidates have rarely experienced it. Exam scenarios often describe a calm-looking crowd, so candidates rate the risk as low because nobody is behaving badly.
What to do instead
Learn the density thresholds and their consequences, and learn the signs of distress in a dense crowd: loss of ability to move independently, people being carried by the flow, screaming or silence, rising heat, and pressure at fixed points such as barriers and pinch points. In answers, name concrete controls: halt admission, open additional exits or routes, create a gap by stepping the crowd back, brief the control room, and monitor the pressure point continuously.
Assuming that because a person is calm, compliant, well-dressed, or matches the venue's usual clientele, they present no risk - and applying more suspicion or force to people who are young, intoxicated, rough-looking, from a minority group, or known to staff.
Rapid unconscious categorisation is normal human cognition, and venue staff gossip about 'regular troublemakers' reinforces it. Candidates also confuse risk assessment with character judgement, and may not have been taught that selective enforcement is both unlawful discrimination and a safety failure.
What to do instead
Base every decision on observable behaviour and articulable facts, and be able to state the behaviour that triggered the intervention. Apply the same test to a well-dressed patron as to a scruffy one. In scenario answers, name the behaviour, not the person's appearance or group. Where a decision could look selective, record the objective basis for it in the report.
Not knowing the emergency sequence - who to notify, in what order, how to raise the alarm, where the assembly area is, and what the controller's specific role is during an evacuation - and improvising a plausible-sounding answer.
Emergency content is often studied last and treated as common sense, and candidates assume 'call 111 and get everyone out' is a complete answer. They have not memorised the venue's own emergency plan or their assigned post.
What to do instead
Learn the generic sequence and then apply the venue plan: raise the alarm, notify the control room or duty manager, call emergency services as directed, begin evacuation or lockdown as instructed, direct people to the nearest safe exit away from the hazard, sweep your assigned area, report your area clear, and account for colleagues. Be able to state what you would do if the control room could not be reached. Revise your own venue's assembly points and post assignments before the exam.
Ignoring the controller's own welfare and situational awareness - describing a single controller handling a large group alone, working through a break, or staying in a confrontation without support - as if endurance were the professional standard.
Candidates equate professionalism with coping, and many come from workplaces where asking for help is seen as weakness. Fatigue, dehydration, and tunnel vision are not visible in a written scenario, so they go unaddressed.
What to do instead
Build support and rotation into every operational answer: radio for assistance before engaging a group, work in pairs, maintain an exit route and awareness of what is happening behind you, take breaks and hydration, and hand over to a colleague when your judgement is compromised by fatigue or adrenaline. State that requesting backup is a control measure, not a failure.
Answering communication questions with what the controller says rather than how they say it - ignoring tone, body language, personal space, positioning, and the effect of an audience - and giving orders instead of explanations.
Written exams reward content, so candidates list phrases and forget that de-escalation depends on delivery and positioning. They also default to a command voice because it feels authoritative.
What to do instead
For every communication scenario, address four elements: what was said (short, clear, respectful, with a reason and a choice), how it was delivered (calm, slow, low volume, non-threatening posture, hands visible), where the controller stood (side-on, at a safe distance, with an exit route, away from the crowd's centre of attention), and what was offered (an alternative, a warning, a chance to comply with dignity).
Treating the report as finished once it is submitted, and not preserving evidence - failing to note CCTV coverage and retention, witness details, notebook entries, or the possibility that the controller will be a witness in a prosecution or a defendant in a complaint.
Candidates see reporting as an administrative chore that ends at the supervisor's inbox, and they do not know that CCTV is often overwritten within days and that memory fades fastest in the first hours.
What to do instead
At the end of every incident, secure the evidence chain: note camera locations and times and request preservation in writing, record witness names and contacts, keep your original notes and do not rewrite them, and complete the report before end of shift. Assume the report will be read aloud in a hearing and write accordingly.