Stanard & Associates describes its entry-level public safety exams as assessing the fundamental skills needed for a law enforcement career, so your preparation target is applied basic skills in police-flavored content, not memorized law. The discipline this guide builds is separating what a passage or log actually says from what you assume about it, then producing clean verifiable statements and correct multi-step math. Start today with one rule: before choosing any reading answer, point to the sentence that proves it. That single habit, drilled through the scenarios and exercises below, transfers across reading, writing, and math items.
Answering from the page, not from plausibility
Entry-level selection passages are self-contained: a defensible answer comes only from text on the page. An option can be true in real policing and still be wrong here if the passage never states it.
Consider a passage stating that bicycle registration is free at the police station and required within 30 days of purchase. If an answer option mentions a small annual fee, it may feel familiar because some real cities charge fees — and that familiarity is the trap. The defensible choice is 'free,' because the passage says so, regardless of what real cities do. Practice treating every option as a claim to verify against the text, and locate the proving sentence before you select anything.
Train this with a two-pass habit. First pass: read the question stem before the passage so you know which detail you are hunting. Second pass: after answering, write the line number or the first few words of the proving sentence next to your choice. When you cannot produce a proving sentence, you have picked a plausible option rather than a supported one. Log those picks by stem type; a cluster of unsupported picks on inference-style stems tells you exactly which passages to re-drill instead of guessing that reading is weak in general.
Attribution: who said it is not the same as what happened
Report-style passages mix direct observations with reported speech and conclusions. A witness's statement is an attribution: the passage establishes that it was said, not that it happened. Confusing the two produces wrong answers.
Worked scenario: a passage says the sedan driver told Officer Reyes that the pickup ran the red light. Asked what the passage establishes, the tempting answer is 'the pickup ran the red light.' The defensible answer is that the sedan driver reported it. The passage records a statement; it does not confirm the collision's cause. When both versions appear among the options, the attributed version is the one the text actually supports, and the unattributed version overstates what the page contains. The better decision is to underline 'told' and 'said' while reading so attributions stay visible.
Extend the same check to characterizations. If a report sentence calls a subject 'belligerent,' ask what was observed — loud speech, refusal to leave — and treat the label as the writer's conclusion. For exam purposes, a conclusion stated by the passage is something you can use in statements about the passage, but it is not direct evidence the underlying event occurred as described. Before answering any question about people's actions, sort the passage's sentences into observed, reported, and concluded, then check which category the question draws on.
| Passage element | What the page establishes | Defensible statement | Trap to avoid |
|---|---|---|---|
| Direct observation ('the officer saw...') | That the observed event occurred as described | Restate only what was observed | Adding a motive or cause the passage omits |
| Reported speech ('the witness said...') | That the statement was made | Name the speaker and the claim | Dropping the attribution and treating the claim as established fact |
| Numbers, times, addresses | Specific details you can match to the stem | Verify each figure against its referent in the question | Swapping times, units, or similar-looking values |
| Characterizations ('belligerent,' 'suspicious') | The writer's conclusion about behavior | Describe the behavior behind the label when asked to write | Reusing the label as if it were an observation |
Multi-step math: write the setup before touching the numbers
Entry-level selection math arrives as short word problems chaining two or three steps. The workable habit is to list knowns, the unknown, and units before computing, because setup slips — wrong base, dropped multiplier — are the difficulty to manage.
Worked example: a log shows 6 overtime hours one week and 9 the next, paid at 1.5 times a $24 base rate. A quick attempt multiplies 15 × 24 and gets $360 — total hours times the straight rate, which drops the multiplier. The better sequence computes the effective rate first (24 × 1.5 = $36), then multiplies by total hours: 15 × 36 = $540. A closing sanity check — overtime pay should exceed straight-time pay for the same hours — catches the dropped multiplier immediately. Why it matters: the wrong answer here comes from a single skipped step, and writing the setup makes that step impossible to skip silently.
Percent change carries the same risk on a different axis. If calls for service fall from 80 to 60, the decrease is 20 divided by the original 80 — 25 percent. Dividing by 60 instead gives roughly 33 percent, a natural slip worth guarding against because the wrong-base number looks as reasonable as the right one. Your drill: for every percent problem, write the sentence 'change over original' and circle which number is the original before computing. Two lines of setup turn both failure modes into visible, correctable steps.
The rewrite drill: turning messy notes into verifiable sentences
Written-expression skill responds to one exercise: rewrite an incident brief into short, chronological, observable sentences. The rubric gives expected observations and a pass standard you can apply to your own drafts before test day.
Take any 150-word incident summary from a news brief and rewrite it as five sentences in time order. Scan your draft for conclusion words — 'clearly intoxicated,' 'fled,' 'uncooperative' — where observable behavior belongs. The better version replaces each conclusion with what a camera would show: unsteady on his feet, left at speed, stated he would not provide identification. Catching and replacing those words is the skill; the label-versus-behavior distinction from the attribution section is what makes the replacement possible. The plausible mistake is polishing grammar while leaving the conclusions untouched.
Score each rewrite against five checks: every sentence describes something a camera or recording could verify; events appear in time order; who, what, when, and where appear wherever the source supplies them; tense stays in the simple past; and every quoted or claimed statement names its speaker. A draft passing five of five twice in a row is the milestone. Expect early drafts to fail the verification check most often — that is where conclusion words hide — and re-drill with a fresh brief until two consecutive drafts pass all five.
Grammar choices that change who did what
Grammar items reward clarity choices: pronoun references and tense shifts can make a sentence ambiguous about the actor or the sequence. Train yourself to spot the ambiguity, not only the agreement rule.
Compare 'The officer told the driver that he had run the stop sign' with 'The officer told the driver that the driver had run the stop sign.' The first is ambiguous — 'he' can reach either man — while the second names the actor even if it reads stiffly. When an item asks you to revise for clarity, the defensible revision is the one a second reader cannot misread about who did what, even over an alternative that merely sounds smoother. Practice by circling every pronoun in a sentence and asking what noun each one points to.
Tense shifts work the same way on time. A report sentence that slides between 'the subject walks to the car' and 'entered the store' blurs whether the events were simultaneous or sequential; holding simple past tense keeps a timeline readable. Practice on your own rewrite drafts: read only the verbs in order and check that the sequence they imply matches the event order in the source. This pairs naturally with the previous section's exercise, since the same draft can carry both an ambiguous pronoun and a tense slip.
An error log sorted by cause, not by topic
A useful log records why an answer was wrong: misread stem, unsupported pick, dropped detail, setup slip, or time-pressure guess. Each cause points to a different drill, so the log sets next week's practice.
After each practice set, spend ten minutes tagging every miss with one of five labels: misread the stem, picked a plausible but unsupported option, dropped or swapped a detail, made a setup slip in math, or guessed under time pressure. Keep the proving-sentence notes from your reading drill — they make unsupported picks obvious on review. One page per set is enough; what matters is that each miss receives exactly one cause, because a miss can be mis-tagged as 'careless' when it was really an unsupported pick that a proving sentence would have exposed.
Then let the counts set your schedule. A set with three setup slips and one unsupported pick means a math-setup week; the reverse means evidence-only reading. Re-test the tagged weaknesses with fresh items rather than the same ones, and require the setup lines or proving sentences as part of each answer. Over three or four sets you get a picture no general review provides: which of the five causes actually produces your misses, and which drills have already done their job and can be dropped.
An adaptable sequence and concrete readiness checks
Build the sequence around your error log rather than a calendar fixed in advance. A four-block cycle — diagnose, skill drills, mixed timed practice, cold re-test — adapts to whatever the counts show.
Block one: a full practice set with the error log attached, no studying first, so the baseline is honest. Block two: skill drills matched to your two largest error causes — math setup lines, proving-sentence reading, or rewrite drills against the rubric. Block three: mixed timed practice sets, log attached. Block four: re-attempt every item you tagged in blocks one and two, cold, and log the results again. Repeat the cycle; each fresh pass through block one tells you whether the previous drills landed or need adjusting.
Treat these as learning milestones, not score predictions: you can produce a proving sentence for every reading choice before selecting it; two consecutive rewrite drafts score five of five on the rubric; you write knowns, unknown, and units before computing any word problem; and you finish a full timed set with the log attached and no untimed rescoring needed. For scheduling, format, fees, and retake rules — which are set per administration — check Stanard & Associates at stanard.com or your recruiting agency; the issuer's site is the authority for those administrative details.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.