CS Interview Coach

By grade

Making Effective Decisions Grade 7 Example Answers (Civil Service)

Published · Last updated


At G7 the descriptors abandon the comfort of thorough analysis: present reasonable conclusions from a wide range of complex and sometimes incomplete evidence, make decisions confidently even when details are unclear. The panel is scoring what you do when the analysis cannot finish, the data conflicts, and waiting for certainty carries a price someone else will pay.

That produces the G7 answer's signature move: reasoning about the uncertainty itself. Not "I gathered what evidence I could" but this was knowable, this was not, waiting cost this, so I decided on the following basis, watched these signals, and would have changed course if.

What Grade 7 panels score on this behaviour

The incompleteness, characterised. What you knew, what you could not know in time, and why not. Candidates who cannot describe the shape of their uncertainty have not reasoned about it. They have tolerated it.

The cost of waiting, priced. Deferral is a decision with consequences. Naming what delay would have cost, and to whom, is what makes deciding anyway judgement rather than impatience.

A basis for the conclusion. Under incomplete evidence something still did the deciding: the weight of what was known, an explicit assumption, a reversibility argument, a worst-case comparison. The panel wants that mechanism visible.

Uncertainty managed forward. Leading indicators watched, review points set, the change-course condition stated in advance. Confidence at G7 is instrumented, not asserted.

The right level, held. The descriptors say decisions should happen at the right level, and that cuts both ways: not escalated to dodge the discomfort, not hoarded when it was genuinely someone else's call.

Questions this appears as

  • "Tell me about a decision you made with incomplete information."
  • "Describe deciding between options when the evidence was unclear or conflicting."
  • "Tell me about a significant decision you made under time pressure."
  • "How have you handled a decision where waiting for more evidence wasn't an option?"

Probes to expect: "What would complete evidence have looked like?", "What did you assume, and what if the assumption was wrong?", "When would you have changed course?"

Fail vs pass at G7: the same funding call

FailVersion 1: thoroughness as the virtue, scores around 4/7 at G7

"I had to recommend how to allocate a £1.8m continuation budget between two programmes my area ran (an employment support programme and a digital inclusion programme) where the budget could sustain one at full scale or both at a reduced level that neither team believed viable. It was a significant decision, so I made sure it was properly evidence-based. I commissioned an internal review of both programmes' performance data, held structured sessions with both delivery teams and key external stakeholders, benchmarked against similar programmes in other departments, and built an assessment framework scoring both programmes against our strategic priorities, value for money, and deliverability. The analysis took around ten weeks. The framework pointed to the employment programme, and I recommended accordingly, with full documentation of the evidence and methodology. The recommendation was accepted, the transition was managed carefully, and the framework I built was praised as a model for future allocation decisions and reused twice since."

At SEO this would score well: rigorous, structured, defensible. At G7 the panel notices what the thoroughness is hiding. Ten weeks bought an analysis, and the answer never asks what the ten weeks cost: two delivery teams in limbo, contracts and staff decisions frozen, partners planning blind. More fundamentally, the framework is presented as having made the decision, which is the G7 anti-pattern, methodology deployed as a shield against exercising judgement. Nothing here reasons about what was unknowable, assumes anything explicit, or manages uncertainty forward, because the answer's implicit claim is that enough process made the uncertainty go away. It did not; it never does. A 4.

PassVersion 2: the same funding call, around 6/7

"I had to recommend how to allocate a £1.8m continuation budget between two programmes (employment support and digital inclusion) where full funding for one meant ending the other, and splitting the budget left both below viability. The uncomfortable core of the decision was that the evidence could not be made complete in the time available, and I said so explicitly rather than pretending otherwise. The employment programme had three years of outcome data; the digital programme was fourteen months old, and its evaluation — the evidence that would have settled the question — was eight months from reporting. Waiting for it wasn't neutral: both programmes' contracts needed six months' notice, both teams were already losing staff to uncertainty, and a deferred decision was in practice a decision to underfund both into failure. So I gave myself four weeks, not ten, and spent them characterising the uncertainty rather than performing completeness. What was knowable: the employment programme's outcomes were solid, stable, and close to what comparable programmes achieved — reliable, mid-range value. What wasn't knowable: the digital programme's true effect — but its fourteen-month leading indicators (engagement, early progression) sat above where the employment programme's had at the same age, and its theory of change addressed a gap no other local provision touched, which the employment programme's didn't. I made the reasoning explicit in the recommendation: this is a choice between a known moderate return and an unknown but plausibly higher one, the evidence gap on the digital programme is real and cannot be closed in time, and I recommend funding the digital programme at full scale — on the stated assumption that its leading indicators would convert to outcomes at even 70% of the rate the early data implied. I priced my own uncertainty into the design: the recommendation included a hard review gate at month ten, tied to three named indicators with thresholds agreed in advance, and a pre-negotiated wind-down option that preserved £300k of year-two budget if the gate failed — so the worst case was a bounded, orderly exit, not a sunk £1.8m. I also held the decision at the right level deliberately: my director offered to take it upward given the sensitivity, and I declined — the analysis was mine, the assumption was mine, and splitting the decision from the reasoning would have served nobody except me. The employment programme's closure was the hardest part and I fronted it personally with the provider and staff, on the honest basis: not that their programme had failed, but that its results were replaceable through mainstream provision and the digital programme's weren't. At the month-ten gate, two of three indicators cleared their thresholds and the third was marginal; the evaluation, when it finally reported, landed within 10% of my 70% assumption. I don't cite that as vindication — the decision was right when I made it or it wasn't, and the outcome doesn't change which. What I'd cite is the mechanism: a decision made at the speed the situation required, on reasoning anyone could inspect, with the uncertainty bounded instead of denied."

The annotation:

  1. The incompleteness is characterised, not endured. Three years of data versus fourteen months, an evaluation eight months away. The shape of the uncertainty is mapped precisely, and that map is the G7 evidence.
  2. Waiting is priced. Notice periods, staff attrition, deferral as slow failure. The cost of the ten weeks Version 1 spent is exactly what Version 2 refuses to spend. Four weeks, chosen and justified.
  3. The basis is explicit, assumption included. Known-moderate versus unknown-plausibly-higher, decided on a named 70% conversion assumption. The decision mechanism is inspectable, which is what reasonable conclusions from incomplete evidence means in practice.
  4. Uncertainty is engineered, not tolerated. The month-ten gate, pre-agreed thresholds and the bounded exit are confidence with instrumentation. The worst case is designed before the best case is hoped for.
  5. The right level, held under pressure. Declining the director's offer to take the decision upward performs the decisions-at-the-right-level descriptor at cost, and the line about splitting the decision from the reasoning serving nobody except the candidate is self-awareness panels rarely hear.
  6. Outcome and judgement, kept separate. "The decision was right when I made it or it wasn't" is the epistemically honest close that tells the panel this candidate's confidence comes from reasoning rather than results.

Calibrating either side of G7

At SEO, Version 1's rigour, sharpened with invited challenge and a carried risk, is genuinely strong, because the evidence there is mostly knowable and the virtue is weighing it well. At Deputy Director, the calibration adds strategic scope: bold decisions across political and national pressures. The full ladder is in the Making Effective Decisions pillar, and the rest of the G7 interview in the Grade 7 questions hub.

G7-specific mistakes on this behaviour

  1. Thoroughness as a shield. Ten weeks of process to avoid four weeks of judgement. Panels at G7 read exhaustive analysis of an unresolvable question as the discomfort dodged.
  2. The framework decided. Methodology is how you reason, not who decides. "The scoring pointed to X" hands your marks to a spreadsheet.
  3. Uncertainty unpriced. If your answer never states what waiting would have cost, the panel cannot distinguish decisiveness from haste.
  4. No explicit assumption. Every incomplete-evidence decision rests on one. Naming yours, and what would have falsified it, is the difference between judgement and hope.
  5. Confidence without instruments. No gate, no indicators and no change-course condition is bravado. The G7 mark is bounded risk.
  6. Vindication by outcome. Citing the result as proof the decision was right invites the obvious probe and fails it. Defend the reasoning and report the outcome separately.

Common questions

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 session

3 free practice questions · No card needed · Cancel anytime