Auxiliary Police Written common mistakes
Auxiliary Police Written · Understand the traps and how to avoid them.
Reading a scenario question once and answering from the first plausible option that matches the gist, without returning to the passage to confirm which option is actually supported.
Auxiliary police written tests are timed, and candidates who feel time pressure substitute recognition of familiar words ('reasonable', 'suspicious', 'report') for verification. Distractor options are deliberately written to share vocabulary with the passage, so gist-matching produces confident wrong answers.
What to do instead
Adopt a two-pass routine for every comprehension item: first read the question stem so you know what to look for, then read the passage, then match each option against a specific phrase in the text and eliminate any option you cannot point to a supporting sentence for. Practise on 20-item sets with a hard 90-second-per-item cap so the verification habit survives time pressure.
Confusing easily swapped word pairs in formal police prose, such as affect/effect, ensure/insure/assure, principal/principle, then/then vs than, and fewer/less, and choosing the wrong one under time pressure.
These pairs are homophones or near-homophones that are handled automatically in speech but require explicit grammatical classification in writing. Candidates who read a lot of informal text have weaker automaticity on formal register, and the error is invisible to the writer because the sentence still 'sounds right'.
What to do instead
Build a personal error log of about 15 confusable pairs and write one original police-context sentence for each (e.g., 'The new policy will affect patrol assignments; the effect on response times was measurable'). Review the log before each practice session, and in practice tests mark any sentence containing a suspect pair before choosing an answer.
Writing narrative incident reports in first person, chronological storytelling ('I was driving down Main when I saw...') instead of the objective, third-person, fact-only format expected in a report-writing section.
Candidates transfer the storytelling style used in emails and social media, and first-person narration feels more natural and more honest. Report-writing items reward structure and neutrality, so a well-written but narrative answer loses points on format even when the facts are correct.
What to do instead
Memorise and drill a fixed report skeleton: date/time/location header, parties identified, concise chronological summary in past tense, actions taken, evidence or witnesses listed, disposition. Rewrite five practice incidents from first person into third person and remove every opinion word ('angry', 'obviously', 'clearly') in favour of observable behaviour.
Omitting required report elements such as exact time, location, names and identifiers, or the chain of who did what, because the candidate assumes the reader already knows the context.
In training scenarios the context is given in the prompt, so it feels redundant to restate it. Real reports are read by people with no access to the original call, and report-writing rubrics award points per required element, so omission is directly penalised.
What to do instead
Before writing, list the mandatory elements in the margin as a checklist (who, what, when, where, how, action taken, witnesses, property) and tick each one as it appears in the draft. Do a final read asking 'could a reader who was not there reconstruct this incident from my text alone?'
Losing points on memorisation items by trying to hold a whole plate of details in working memory at once rather than chunking them into categories.
Observation and memorisation sections present a scene, plate, or list briefly and then test recall. Untrained candidates attempt rote visual retention, which exceeds working-memory capacity within seconds, so later details overwrite earlier ones.
What to do instead
Practise a fixed chunking routine: split the target into four or five categories (people, vehicles, objects, numbers, spatial layout) and assign a short verbal label to each item as you scan. Rehearse with a 15-second exposure to a written list of 12 mixed items, then recall by category, and track your accuracy per category to find your weak channel.
Reporting a memorised detail with false confidence, or 'filling in' a detail that was not actually observed, rather than flagging uncertainty.
Memory gaps are uncomfortable and the test format invites a definite answer. Candidates also confuse familiarity (the detail feels seen) with accuracy, and stress increases both confidence and error rate.
What to do instead
In practice, separate recall into 'certain', 'probable', and 'unknown' columns and score yourself on calibration, not just raw hits. Learn to notice the specific details you reliably miss (often colours, numbers, and left-right position) and deliberately allocate attention to them during exposure.
Misreading directional language in spatial items, for example treating 'left of the intersection' or 'north of the building' from the observer's viewpoint when the item is stated from a fixed map orientation, or vice versa.
Everyday directions are egocentric ('turn left'), while map and report descriptions are often allocentric (fixed compass or page orientation). Candidates apply the habitual frame without checking which one the item uses.
What to do instead
Before answering, state the reference frame to yourself explicitly ('this item uses map north, not my facing direction'). Practise by drawing simple intersection diagrams from written descriptions and then verifying by re-reading the description against your drawing, including which corner each party occupies.
Skipping the sketch or diagram on spatial orientation questions and trying to rotate or track positions mentally.
Mental rotation is fast for simple shapes but error-prone once more than two objects or turns are involved, and the errors are silent. Candidates who are strong verbal reasoners over-trust verbal tracking of spatial relationships.
What to do instead
Make a rough sketch mandatory for any item with three or more positional statements or two or more turns. Use a consistent notation (arrow for facing direction, dot for location, letter for person) and re-derive the answer from the sketch rather than from memory of the text.
Answering problem-sensitivity items with the most forceful or punitive option, or with the option that resolves the immediate complaint fastest, rather than the option that balances safety, policy, and escalation.
Candidates assume a police test rewards decisiveness and authority, and action-oriented answers feel more competent. Problem-sensitivity items instead reward recognising when a situation exceeds one's authority, when to request a supervisor, and when a low-key resolution is appropriate.
What to do instead
For each scenario, rank the options on three axes before choosing: immediate safety risk, whether the action is within an auxiliary officer's authority, and whether it preserves the option to escalate. Eliminate any option that commits to force, admission, or a legal conclusion beyond the role, then pick the highest-ranked remaining option.
Rushing the final minutes by changing multiple-choice answers on a hunch, or leaving items blank when there is no penalty for guessing.
Fatigue near the end of a timed written test reduces discrimination between options, and anxiety produces last-minute second-guessing. Candidates also carry over a belief that wrong answers are penalised, which is uncommon on entry-level written tests.
What to do instead
Confirm the scoring rule for the actual test before exam day. In practice, adopt a rule: only change an answer if you can cite a specific passage or fact that contradicts your first choice, and always fill every blank in the last minute. Simulate full-length timed tests so end-of-test fatigue is familiar rather than novel.