Making Effective Decisions: Showing Judgement, Not Just the Outcome
Making Effective Decisions is scored on your reasoning, not the outcome. See the AA/AO and EO descriptors, plus a worked weak versus strong example.
Ask a candidate to describe a time they made an effective decision, and most reach straight for the ending. “I decided to do X, and it worked out well.” The problem sits in those last four words. An assessor reading that sentence has learned nothing about how the decision was made, only that it landed.
Making Effective Decisions is scored on the reasoning, not the result. A well-reasoned decision that produced a mediocre outcome is stronger evidence than a lucky guess that happened to come off, because luck is not a skill the Civil Service can hire for twice. Most answers get this backwards, which is why confident, outcome-shaped answers routinely score lower than the person writing them expects.
This post sets out what the official framework actually asks for at the grades most external applicants apply to, quotes the descriptors so you can check them against your own advert, and works through a matched pair of answers to the same prompt so you can see the difference between a decision described and a decision explained.
What Does “Making Effective Decisions” Actually Assess in the Civil Service Behaviours Framework?
It assesses how you reach a decision, not whether the decision paid off. The official definition, in the Success Profiles: Civil Service behaviours guidance, reads: “Use evidence and knowledge to support accurate, expert decisions and advice. Carefully consider alternative options, implications and risks of decisions.”
Read that sentence again and notice what is missing. There is no mention of the decision working out, or being praised afterwards. Every verb is about process: use, consider, weigh. Making Effective Decisions is one of nine Civil Service Behaviours, and Behaviours is only one of five Success Profiles elements, alongside Strengths, Ability, Experience and Technical skills. The advert for your role names the elements it uses, and the Success Profiles pages set out how each element is assessed.
Why Does an Answer That Ends Well Still Score Poorly?
Because the assessor cannot mark an ending. They can only mark what you show them of the thinking that led to it. A candidate who writes “I decided to escalate the case and it turned out to be the right call” has handed the assessor a single sentence to score against five descriptor bullets built almost entirely around process. There is nothing there to match against “identify and deal with any errors or gaps in information” or “demonstrate the consideration of all options, costs, risks and wider implications.” The outcome is not evidence of any of that. It is just an outcome.
This is also why a decision that did not go perfectly can still score well. If you gathered the right information, noticed what you did not know and did something about it, weighed genuine alternatives rather than one option dressed up as several, and can explain the trade-off you accepted, you have given the assessor exactly what the descriptors ask for, regardless of how the story ends. A fluent, confident account of a lucky guess is still a lucky guess.
PublicServicePathway is independent and is not affiliated with or endorsed by the UK Government or Civil Service. The wording quoted throughout this post comes directly from the published framework, so check it against your own advert rather than taking a prep site’s paraphrase of it on trust.
What Does the Framework Actually Ask for at AA and AO Grade?
Five things, and none of them require you to have made the decision alone. At Administrative Assistant and Administrative Officer grade, the published descriptors for Making Effective Decisions are:
- use guidance, analyse relevant information and ask colleagues for input to support decision making
- identify and deal with any errors or gaps in information before making a decision
- consider the diverse needs of those affected by decisions and how it will impact them
- provide advice and feedback to support others in making accurate decisions
- ask others to clarify decisions when confused and query any issues that arise constructively
Look at the shape of that list. Two of the five bullets are explicitly about using other people: asking colleagues for input, asking others to clarify. At this grade, an example built entirely around a solitary decision is missing half the evidence the descriptors are asking for. Knowing when to ask is part of the behaviour, not a weakness in the story.
What Changes at Executive Officer Grade?
Ownership moves onto you, and the descriptors say so directly. At Executive Officer grade, the same guidance sets out:
- take responsibility for making effective and fair decisions, in a timely manner
- analyse and research further information to support decisions
- talk to relevant people to get advice and information when unsure how to proceed
- explain how decisions have been reached in a clear and concise way, both verbally and in writing
- demonstrate the consideration of all options, costs, risks and wider implications, including the diverse needs of end users and any accessibility requirements
Three words carry most of the weight of the grade jump: “take responsibility.” At AA and AO grade you are asked to support and input into decisions. At EO grade you are asked to own one, including the timing of it, and then explain how you reached it in a “clear and concise way, both verbally and in writing.” That last phrase matters for how you write the example itself. If you cannot explain your own reasoning clearly on the page, you have not demonstrated the thing the descriptor is asking for, whatever the decision itself achieved.
What Separates a Weak Decision-Making Answer From a Strong One?
The two answers below respond to the same illustrative prompt. Both were written for this article to show the difference in practice. Neither is a real candidate’s submission, and neither should be copied.
The prompt
Tell us about a time you made an effective decision.
A weak answer
“A supplier missed a delivery deadline that affected a project I was working on. I decided the best option was to switch to a backup supplier we had used before, so I made the call and arranged the new order that afternoon. The replacement supplier delivered on time and the project stayed on track, and my manager thanked me for sorting it out quickly.”
A strong answer
“A supplier missed a delivery deadline two weeks before a project milestone. I did not know yet whether the delay was a one-off or a pattern, so I checked our order history and found two smaller late deliveries the previous quarter that nobody had flagged. That changed the decision from finding a quick fix to deciding whether to keep using this supplier at all. I looked at three options: wait and chase, switch the whole order to a backup supplier, or split it between both to protect the deadline without losing the relationship entirely. I talked to the colleague who managed that relationship, because she had context I did not, and she confirmed the pattern was new rather than typical. I chose to split the order, since it protected the milestone while giving the original supplier one more delivery to recover on, and I wrote a short note explaining the reasoning to my manager rather than just reporting the problem as fixed. The milestone held, and the note meant the next person to hit a delay with that supplier did not have to start from nothing.”
Why the strong answer clears the bar and the weak one does not
The weak answer is a single decision reported after the fact. “I decided”, “I made the call”: both are outcome statements, not evidence of reasoning. There is no sign of what information was checked, whether an alternative was seriously considered, or how the writer knew a quick supplier switch was the right call rather than just the fastest one. It reads as competent action under pressure, which is real, but it does not match the descriptor language at either grade. Nothing here shows the framework’s “identify and deal with any errors or gaps in information” or “demonstrate the consideration of all options, costs, risks and wider implications.”
The strong answer keeps a comparable situation and changes what is on the page. It names a gap, whether the delay was a one-off or a pattern, and shows what was done about it, which is the AA/AO descriptor on identifying and dealing with gaps before deciding. It sets out three real alternatives rather than one option retold three ways, answering the EO descriptor on considering options, costs and wider implications. It shows the writer bringing in someone with more context before deciding, the framework’s own language on talking to relevant people when unsure how to proceed. And it closes by explaining the reasoning in writing, which is the EO descriptor almost word for word. The outcome is similar in both answers. The evidence behind it is not.
What Should You Actually Be Able to Point to Before You Write the Example?
Four things, and if any one of them is missing, the example is not finished yet, whatever the ending looks like.
What information you gathered, and where it came from. Not “I looked into it”, but the specific thing you checked, the record you pulled or the person you asked.
What you did about the gaps. Every real decision has a piece of missing information. Naming the gap and saying what you did about it, rather than pretending you had full information, is itself evidence, not a weakness to hide.
What alternatives you actually weighed. One option described three different ways is not three alternatives. A genuine alternative is something you could have chosen and did not, with a reason attached to why you did not.
How you knew you had enough to decide. Decisions rarely wait for complete information. Being able to say what told you it was time to commit, a deadline, a growing risk, a point where more analysis stopped adding value, is exactly what “timely manner” in the EO descriptor is asking you to show.
Write those four down before drafting a single sentence of the example. The story you build around them carries the evidence automatically, instead of you trying to bolt it on afterwards.
FAQ
Can the decision I describe have gone badly? Yes. The descriptors are about your reasoning, information gathering and consideration of alternatives, not about the result. A well-reasoned decision that did not work out is still valid evidence, and pretending every decision you have made worked out perfectly usually reads as less credible, not more.
Do I need to have made the decision entirely on my own? No. At AA and AO grade the descriptors explicitly include asking colleagues for input and asking others to clarify. At EO grade you are expected to talk to relevant people when you are unsure how to proceed. Consulting others is part of the behaviour, not evidence against it.
How much detail should I give about the information I gathered? Enough that the assessor can see a specific source, not a vague gesture at “research”. Name the record, the report, the person or the data you actually checked.
Is this behaviour the same as Delivering at Pace? No. Delivering at Pace is about managing your workload and meeting deadlines under pressure. Making Effective Decisions is about the reasoning behind a specific choice, even if that choice took time to reach.
Explain the Decision the Way You Would Have to Explain It on the Day
Write the example the way the EO descriptor asks you to explain a real decision: clearly, and in a way that shows the reasoning rather than just the result. Once you can set that reasoning out on paper, the next step is talking the same case through out loud in a way a panel can follow, and communicating and influencing is marked on its own separate wording worth checking before your interview.