Civil Service Judgement Test common mistakes
Civil Service Judgement Test · Understand the traps and how to avoid them.
When the scenario involves incomplete information or material risk, picking the option that commits to a course of action immediately rather than one that checks the facts, consults the relevant specialist, or runs a quick test first.
Speed and visible decisiveness feel like the behaviours a busy organisation rewards, so candidates rank 'act now' above 'act well' even when the stem signals uncertainty or consequences.
What to do instead
Before answering, underline the risk cues in the stem: irreversible, safety, legal, financial, reputational, other teams blocked. Whenever any are present, rank gather-evidence or consult-then-decide options above immediate-commitment options.
Answering the item as if it were a single-best-answer question, ignoring the ranking task or losing track of whether the question asked for most or least effective.
Time pressure plus long stems: the instruction line sits at the end and gets skimmed, and the single-answer habit carried over from other tests takes over.
What to do instead
Read the instruction first and say it back to yourself. Then nominate the single worst option before anything else - blame-shifting, concealing errors, ignoring policy, doing nothing - and use that as an anchor for ranking the rest.
Escalating to the line manager as the default 'safe' answer, including for decisions clearly inside your own remit and low in risk.
Fear of accountability: passing the decision upward feels low-risk because responsibility appears to move with it, and it looks conscientious.
What to do instead
Test three things before choosing escalation: is it inside my remit, is the risk genuinely high, and is someone else's authority actually needed? If the answers are yes, no, no, the top-ranked option acts and informs rather than refers.
In prioritisation items, ordering tasks by how urgent they feel or by arrival order in the inbox, and choosing to absorb the extra load by working longer rather than renegotiating.
Urgency bias makes recent and loudly-requested work feel important, and presenteeism frames extra hours as commitment rather than as a failure to prioritise.
What to do instead
Rank by impact, deadline, and who is blocked waiting on you. Where demand genuinely exceeds capacity, prefer options that tell the requester early and agree what moves, over options that promise everything and quietly work late.
Choosing to stay quiet about a slipping deadline or a mistake until it has been fixed, hoping no one notices in the meantime.
Reputation anxiety: candidates assume admitting a problem looks incompetent, so conceal-and-recover options get ranked higher than they deserve.
What to do instead
Treat early, specific disclosure with a revised plan as near-always top-ranked. Options that delay bad news, soften it into vagueness, or let someone else discover the problem belong at the bottom.
When a colleague is underperforming or blocking work, choosing to raise it with the manager, mention it to other team members, or drop hints rather than speaking to the colleague directly.
Conflict avoidance: a direct conversation feels personally risky, while going through channels feels more professional and safer.
What to do instead
Look for the option that raises it privately, directly, and specifically with the person, focused on behaviour and impact, with an offer of help. Rank escalation or third-party discussion above that only where a direct attempt has already failed or the issue is serious.
Treating influence as persistence: choosing to restate the case more forcefully, repeat the same argument, or copy in senior people when a stakeholder disagrees.
Candidates equate influence with assertiveness and assume a disagreement is a volume problem rather than a difference of interests.
What to do instead
Prefer options that first ask about and reflect the other party's concerns, reframe the proposal in terms of their priorities, and bring evidence. Escalation should only be ranked highly after a genuine attempt to understand their position.
Sending the same message in the same channel to everyone - a long technical email to a director, or a sensitive and emotional issue handled in writing.
Attention goes to getting the content right rather than to how the receiver will read it, so candidates default to their own preferred channel and level of detail.
What to do instead
Match to audience: senior readers get a short summary with the recommendation and the decision needed; sensitive or complex messages get a conversation first and written follow-up afterwards. Choose the option that adapts the message, not the one that merely transmits it.
In customer-facing scenarios, choosing to make an exception, bend the rule, or promise something outside policy because the customer is upset.
A generic 'customer is always right' instinct, plus a wish to end the discomfort of the conversation quickly, pushes candidates toward appeasement.
What to do instead
Separate empathy from compliance. Top options acknowledge the frustration, explain the reason for the constraint plainly, and offer legitimate routes - appeal, alternative service, complaint process, call-back - without breaching policy.
Responding to change with either blanket enthusiasm ('no concerns, implement immediately') or passive waiting ('see how it settles before doing anything').
Wanting to appear positive and adaptable pulls one way; discomfort with ambiguity pulls the other. Both avoid actually engaging with the change.
What to do instead
Pick options that engage constructively: ask clarifying questions, acknowledge real concerns with evidence, suggest a pilot or phased rollout, and feed issues back through the proper channel. Also prefer options that protect your own capacity over ones promising unsustainable extra hours.