NY Court Officer common mistakes
NY Court Officer · Understand the traps and how to avoid them.
Selecting an answer choice because it matches the candidate's own knowledge of courts, police work, or current events rather than because the passage states or implies it.
Court officer candidates often have prior security, military, or legal-office experience, so familiar-sounding statements feel 'obviously correct' and get chosen without returning to the text. The distractors are written to reward exactly that familiarity.
What to do instead
Before selecting, point to the sentence (or the two sentences) that support the choice. If you cannot locate support in the passage, eliminate the option even if you believe it is true in real life. For inference items, require that the answer be 'must be true' rather than 'could be true.'
Skimming the question stem and answering the opposite of what is asked on EXCEPT / NOT / LEAST / INCORRECT items, or missing qualifiers such as 'primarily,' 'best,' and 'according to the author.'
The stem is short and the passage is long, so attention is spent on the reading and almost none on the question. Under time pressure the eye registers the topic but not the logical operator.
What to do instead
Read the stem first and mentally rewrite it in plain words ('three of these are in the passage; one is not - find the odd one out'). Physically underline the operative word. On EXCEPT items, mark each option T or F against the passage and select the single odd one.
Solving a multi-step word problem correctly but then bubbling the intermediate number - the subtotal, the per-unit rate, or the amount removed - instead of the quantity the final sentence asks for.
The last computation feels like the finish line, so the candidate stops reading before the actual question, which is often the final clause of the prompt.
What to do instead
Before computing, write down what the question asks for with a label and units (e.g., 'officers remaining = ?'). After computing, re-read only the final sentence and confirm the number you are about to grid matches that label and its units.
Mixing units or rates within a single calculation - converting hours to minutes inconsistently, applying a percentage to an already-discounted figure without noting it, or treating a per-day rate as a per-shift rate.
Word problems bury the conversion in prose rather than in the numbers, so the arithmetic looks clean while the units are silently incompatible.
What to do instead
Set up the calculation with units written out and cancel them (miles/hour × hours = miles). If the units left over are not the units of the requested answer, the setup is wrong. Finish with a rough estimate to confirm the magnitude is plausible.
Accepting an answer choice that merely restates a premise, gives an example, or sounds like a reasonable explanation, instead of identifying the choice that actually strengthens, weakens, or is required by the argument.
Candidates evaluate options by plausibility and topic relevance rather than by logical function, and test writers deliberately make the wrong options on-topic and believable.
What to do instead
First write the argument's conclusion and its evidence in one line each. Then label each option by function: restates evidence, introduces a new issue, or bears directly on the gap between evidence and conclusion. Only the third type can be correct. For assumption items, apply the negation test - if negating the option destroys the argument, it is the assumption.
Importing real-world facts into formal-logic items - assuming that because all X are Y, some specific real thing that is Y must be X, or drawing 'some' conclusions from 'all' premises.
The content of the statements is familiar (officers, courts, uniforms), which triggers everyday reasoning and overrides the formal rules governing all/some/none/no.
What to do instead
Treat the category words as meaningless letters (A, B, C) and test each conclusion only against what the premises license. Remember that 'all A are B' supports no claim about whether any A or B exists, and 'some A are B' cannot be converted into 'some B are A' unless existence is already given for both.
Choosing the most forceful, punitive, or morally satisfying response - issuing a threat, physically intervening immediately, or 'making an example' of someone - rather than the least-escalating action that is within the officer's authority and consistent with procedure.
The exam is testing judgment, but candidates answer as though they are being scored on toughness or decisiveness, and high-intensity answers read as decisive.
What to do instead
Rank candidates against a fixed priority order: safety of people first, then policy and lawful procedure, then verbal de-escalation and clear direction, then documentation, then notification up the chain. Eliminate any option that exceeds your role (disciplining a coworker, changing policy, releasing information) or skips a required step, even if it feels more effective.
Selecting 'wait and see,' 'take no action yet,' or 'handle it quietly myself so it doesn't become a big issue' on interpersonal and reporting scenarios, instead of acting and documenting or escalating as policy requires.
Candidates fear overreacting or being seen as a troublemaker, and the passive option is worded calmly, which makes it feel mature.
What to do instead
Ask two questions of each option: does it leave a hazard or a rule violation unaddressed, and does it leave the event undocumented or unreported? If either answer is yes, eliminate it. When a situation involves a possible safety issue, a policy violation, or a supervisor's need to know, the correct answer almost always includes both an action and a record of it.
Transcribing names, badge or docket numbers, addresses, and dates with small silent alterations - writing 'St.' as 'Street,' dropping a leading zero from an ID, reordering a date from MM/DD to DD/MM, or 'fixing' what looks like a typo in the source.
The brain reads in chunks and normalizes familiar patterns, so the copy matches what the candidate expected to see rather than what is on the page. Corrections feel helpful, but the task is verbatim transfer.
What to do instead
Copy character by character, and verify by comparing the source and the form in reverse order - last character first - so chunk-reading is broken. Reproduce the source exactly, including abbreviations, punctuation, and leading zeros. Never correct the source; if it appears inconsistent, flag it per instructions instead of changing it.
Filing or ordering entries by the whole string as it appears on the page, mishandling names with Mc/Mac, O-apostrophes, hyphens, compound surnames, or numeric identifiers of unequal length.
Candidates alphabetize by habit and by first-glance impression, and these name and number patterns are exactly where habit and filing convention diverge.
What to do instead
Apply one rule consistently and mechanically: alphabetize letter by letter as though spaces, apostrophes, and hyphens were not there, and treat nothing as a 'space' that sorts before letters. For numeric identifiers, compare as fixed-width strings from the leftmost digit so that shorter numbers are not treated as smaller. Sort in small batches and re-check the pairs on either side of each entry you place.