Behaviours
Making Effective Decisions: Civil Service Examples That Actually Score
Published · Last updated
In most failed Making Effective Decisions answers, the decision disappears. The candidate describes the analysis, the consultation and the options paper, then says "we agreed" or "my manager decided to go with option B". All the work is visible; the judgement is not. It is why candidates consistently overrate their answers here.
What panels are actually scoring
Four things.
A decision that was genuinely yours, within your level and at your authority. 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 is a task, not a decision.
Proportionate evidence. You gathered what the decision needed, whether data, views from the people affected, or 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 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 is a gift if you are 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."
FailVersion 1: scores around 3–4/7
"In my last role our team's case-tracking spreadsheet kept causing problems — duplicated entries, missed deadlines, no visibility of who was doing what. It was clear something needed to change.
I researched the options thoroughly. I looked at whether we could rebuild the spreadsheet with better controls, whether we could use the project-tracking tool another team already had a licence for, or whether we should request a new system through IT. I gathered feedback from colleagues on what they needed, listed the pros and cons of each option, and put together a comparison covering cost, timescales and training needs. I presented all of this to my manager with the evidence laid out clearly, and after discussing it we agreed the best way forward was to adopt the other team's tool, since it was already licensed and proven.
The migration went smoothly, the duplicate-entry problem stopped, and the team found the new tool much easier to use. My manager praised the thoroughness of the comparison. It showed me how important it is to gather proper evidence before making a change."
Read it as a panel member. The research is genuinely good: three options, real criteria, consultation. Then comes 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 is 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.
PassVersion 2: scores around 6/7
"Our team's case-tracking spreadsheet was causing real failures — duplicate entries and two missed statutory deadlines in a quarter. Fixing it was within my remit, so I owned the decision rather than just the research.
I narrowed it to three options: rebuild the spreadsheet with tighter controls, adopt the project tool another team already licensed, or request a new system through IT. I ruled out the IT request first — a proper system was the best long-term answer, but procurement would take months we didn't have, and the missed deadlines were a live risk now. The real choice was rebuild versus adopt. The rebuild was tempting because the team knew spreadsheets, but it kept the single point of failure that caused the problem. So I chose the existing tool — because it fixed the root cause, cost nothing, and could be live in weeks — while being honest about its main risk: the team would resist learning a new system mid-workload.
I managed that risk directly. Our most sceptical caseworker was also our most experienced, so instead of working around her, I asked her to run the two-week pilot and set the criteria for whether we switched. Her verdict — 'better than I expected, fix the label names' — carried more weight with the team than anything I could have said. I then took the pilot results to my manager as a recommendation with the rollout plan attached; she signed it off in one conversation.
Duplicates stopped entirely, and we've hit every statutory deadline in the six months since. The pilot-first approach became how our team tests any tooling change. What I learned at my level: gathering the evidence is the easy half — the job is choosing, naming the risk in your choice, and owning it."
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 rather than 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 pilot-first process 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 is that when guidance did not cover the situation, you worked out a sensible answer rather than escalating a raw problem.
- HEO: you own decisions on work that is 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 is 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, with the unknown named, the assumption stated and a trigger set for revisiting, then 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.
Common mistakes that cap your score
- "We agreed" or "it was decided". The decision evaporates into consensus, and the panel cannot score judgement they never saw.
- No rejected option. Without a named alternative and a "because", it is a task rather than a decision.
- A risk-free choice. Every real decision has a downside. Pretending yours did not reads as either dishonesty or a decision that did not matter.
- Evidence-gathering as the whole story. The research is the setup, not the evidence. Panels score the choosing.
- Escalating the interesting part. "It was complicated so I referred it up" hands your marks to whoever caught it.
The mechanics behind the scale are in how Civil Service interviews are scored.
Common questions
It means using evidence and knowledge to make timely, fair decisions at your level — weighing options, risks and the people affected, explaining your reasoning clearly, and taking responsibility for the outcome. At senior grades it includes deciding confidently on incomplete evidence and defending unpopular calls.
Common patterns: tell me about a difficult decision you made; a decision made with limited information; a decision someone disagreed with; a time you weighed several options; and a recommendation you made to someone senior. Expect probing on why you chose what you chose.
The decision disappears. Candidates describe gathering information and consulting people, then say 'we agreed' or 'it was decided' — and the panel never hears the moment the candidate personally chose, or the option they rejected. If there's no discarded alternative, it isn't a decision; it's a task.
Yes, if you show sound reasoning at the time, early recognition, honest communication and what you changed afterwards. What you can't do is present a failure caused by your own inaction, or a mistake with no recovery.
That's normal at most grades — the evidence is that the recommendation was yours, arrived with the analysis done and a clear preferred option, and that you'd have stood behind it. 'I took it to my manager as a recommendation, not a question' scores.
Enough to show real comparison — one sentence per rejected option with the reason it lost is usually right. Don't recite the whole options paper.
Either, if the reasoning matches the stakes. A quick call with proportionate evidence under time pressure is excellent evidence; so is a careful one — what scores is the fit between the decision's weight and your process.
Practise before the real thing
Reading how panels score is step one. The candidates who pass are the ones who practised saying their answers out loud — and got scored feedback against the official Civil Service Behaviours framework before interview day.
Start Practising FreeStart a practice session3 free practice questions · No card needed · Cancel anytime