Making Effective Decisions: Civil Service Examples That Actually Score

Making Effective Decisions is, alongside Delivering at Pace, one of the two most frequently assessed behaviours in Civil Service recruitment — and it has the highest gap between how strong candidates feel their answers are and how those answers actually score.

The reason is specific and fixable: in most failed answers, the decision disappears. The candidate describes the analysis, the consultation, the options paper — and then says "we agreed" or "my manager decided to go with option B." All the work is visible; the judgement isn't. This article covers what panels actually score, the questions to expect, and a realistic answer rewritten from a borderline fail to a 6/7 so you can see the difference line by line.

What panels are actually scoring

Strip the framework language away and Making Effective Decisions comes down to four things:

A decision that was genuinely yours. Within your level, at your authority — but yours. If the honest answer to "who decided?" is "my manager," the example collapses no matter how well you tell it.

A rejected alternative. A decision, by definition, involves options. Strong answers name the road not taken and say why: "I could have done X, but chose Y because…" If your example has no discarded alternative, it isn't a decision; it's a task.

Proportionate evidence. You gathered what the decision needed — data, views from the people affected, precedent — without gathering everything forever. At senior grades, deciding before the evidence is complete is the whole point.

Reasoning you can explain. Panels probe decisions hard: "why that option?", "what would have changed your mind?", "how did others react?" An answer that survives probing is one where the reasoning was real.

The questions panels actually ask

• Tell me about a difficult decision you had to make.
• Give an example of a decision you made with limited or incomplete information.
• Talk me through a time you had to weigh up several options — how did you choose?
• Tell me about a decision you made that someone disagreed with.
• Tell me about a time you used evidence or data to support a decision.
• Tell me about a recommendation you made to someone senior — what happened?
• Tell me about a decision you got wrong.

That last one appears more often than people expect, and it's a gift if you're prepared: sound reasoning at the time, early recognition, honest correction, and a changed process afterwards scores highly.

A real answer, rewritten: from 3–4/7 to 6/7

The question: "Tell me about a time you had to make a decision by weighing up several options."

Read it as a panel member. The research is genuinely good — three options, real criteria, consultation. And then the hinge: "I presented all of this to my manager… we agreed." The candidate did everything except decide. The comparison table is the work of a capable analyst; the decision belongs to the room. There's also no risk anywhere — no downside weighed, nothing that could have gone wrong with the chosen option, nobody who preferred a different one. Thorough, safe, and capped at a 4.

What changed, ingredient by ingredient:

• The decision is explicitly the candidate's — "it was within my remit, so I owned the decision," with the manager appearing at sign-off with a recommendation, not at the choosing.
• Rejected options are named with reasons — the IT request ruled out on timing, the rebuild on root cause. This is where a panel can literally point to descriptor language being met.
• The chosen option's risk is owned — team resistance, named and managed, rather than a choice presented as free.
• A sceptic becomes part of the evidence — inviting challenge into the decision is descriptor-level behaviour at every grade from HEO up.
• The result is quantified and structural — deadlines met for six months, and a process (pilot-first) that outlived the original problem.

How Making Effective Decisions changes by grade

• EO: the decisions are within your own casework and tasks — timely, fair, within the rules, with reasoning you can explain. The key move: when guidance didn't cover the situation, you worked out a sensible answer rather than escalating a raw problem.
• HEO: you own decisions on work that's yours end to end, with a named rejected alternative. When you escalate, you escalate a recommendation with the file prepared.
• SEO: you know precisely what's yours to decide, you invite challenge before finalising, and you can name a decision that was unpopular or could have gone wrong — and that you owned anyway.
• Grade 7: the defining evidence is deciding on incomplete or conflicting information — the unknown named, the assumption stated, a trigger set for revisiting — and defending the call at senior level. Presenting neutral options for a board to choose is the classic G7 fail.

Our grade guides (EO, HEO, SEO, Grade 7) cover this calibration for all nine behaviours, with a full worked example at each grade.

Common mistakes that cap your score

1. "We agreed" / "it was decided" — the decision evaporates into consensus, and the panel can't score judgement they never saw.
2. No rejected option — without a named alternative and a "because," it's a task, not a decision.
3. A risk-free choice — every real decision has a downside; pretending yours didn't reads as either dishonesty or a decision that didn't matter.
4. Evidence-gathering as the whole story — the research is the setup, not the evidence. Panels score the choosing.
5. Escalating the interesting part — "it was complicated so I referred it up" hands your marks to whoever caught it.

---

Every example here was written against the same 1–7 rubric your panel will use — see how Civil Service interviews are scored for the full mechanics. To find out where your own answers land before the real thing, CS Interview Coach's AI scores them against grade-calibrated criteria instantly — try it free, or get every guide, the 250+ question bank and unlimited practice with Interview Sprint at £24.99/month.