Behaviours
Delivering at Pace: Civil Service Interview Questions and Example Answers
Published
Delivering at Pace is one of the two most commonly assessed behaviours in Civil Service recruitment, alongside Making Effective Decisions. It appears constantly in job adverts from EO to Grade 7, it's a standard fixture in DWP and HMRC campaigns, and it is one of the easiest behaviours to score badly on with an example that feels strong.
That last part is the bit nobody tells you. Most failed Delivering at Pace answers aren't weak stories — they're good stories told at the wrong level. This article covers what the behaviour actually means, the questions panels ask, and then does something you won't find in most guides: it takes a realistic answer that scores a 3–4 out of 7 and rewrites it into one that scores a 6, so you can see exactly what changes.
What Delivering at Pace actually means
The official Success Profiles definition is about delivering timely performance with energy and taking responsibility for the quality of outcomes. In practice, panels are scoring three things:
Prioritisation under conflict. When two demands couldn't both be met, what did you choose, and why? The word "because" is where the marks live.
Responsibility for the outcome. Not "I contributed to" — the delivery was yours, and when it came under threat, you did something about it rather than watching it slip.
Standards under pressure. Pace without quality is just rushing. Strong answers show what you protected while moving fast, and what you deliberately let go.
What it does not mean is working hard. This is the single most common misunderstanding: candidates hear "pace" and reach for their busiest week. Panels hear "I worked extra hours" as the absence of a plan — effort that replaced prioritisation rather than following from it.
The questions panels actually ask
These are the recurring patterns across departments. You'll usually get one main question plus probing follow-ups:
- Tell me about a time you had to work to a tight or moved deadline.
- Tell me about a time you had to balance competing priorities to deliver on time.
- Give an example of delivering a piece of work with fewer people or resources than planned.
- Tell me about a time a deadline was at risk — what did you do?
- Tell me about a time you struggled or failed to meet a deadline.
- How do you maintain quality when working at speed?
Note that last two. Panels want to hear about things going wrong. A story where the deadline was comfortable and the plan survived contact with reality contains no evidence of judgement — which is why smooth stories cap out around a 4.
A real answer, rewritten: from 3/7 to 6/7
The question: "Tell me about a time you had to balance competing priorities to deliver on time."
Both versions below describe the same underlying events. Read the first and notice it isn't bad — it's organised, honest, and has a result. That's what makes it dangerous: it feels like a pass.
FailVersion 1 — scores around 3–4/7
"In my role I was responsible for our team's monthly statistics return when an urgent batch of information requests came in with the same deadline, and two colleagues were off sick. It wasn't possible to do everything to the usual standard in the time.
I spoke to my manager to explain the situation and agree which work should come first. She said the information requests were legally time-bound, so I prioritised those. I made a plan breaking both tasks into steps, worked through the requests methodically, and stayed late two evenings to keep the stats return moving as well. I kept my manager updated throughout so she always knew where things stood.
In the end the requests all went out on time and the stats return was only two days late, which my manager said was understandable given the circumstances. It taught me the value of staying organised and communicating early when workloads clash."
Put yourself behind the scoring sheet. The panel asked how you balance competing priorities — and the answer given is: my manager balances them. The one decision the whole story turns on belongs to someone else. After that, everything is execution: lists, method, late nights. The stats return quietly slips two days with no evidence anyone warned the people waiting for it, no trade-off is ever named, and the learning point — "stay organised, communicate early" — could come from any grade.
PassVersion 2 — scores around 6/7
"I owned our team's monthly statistics return when an urgent batch of legally time-bound information requests landed with the same deadline — and two of the four people who'd normally share the work were off sick. Doing both to full standard wasn't possible, so I treated it as a prioritisation decision rather than a workload problem.
The requests were legally immovable, so they came first — but rather than just letting the stats return slip, I contacted the analyst who receives it and asked what her real cut-off was. It turned out the return feeds a report compiled a week later, and only two of its five tables were needed early. So I agreed a revised package with her: the two critical tables on time, the rest three days later. The deadline everyone assumed was fixed effectively moved, with nothing late where it mattered. I told my manager what I'd arranged and why — as a heads-up, not a request.
On the requests themselves, I front-loaded the risk: I triaged all of them on day one and started with the two that needed input from another team, because external dependencies are what actually sink deadlines, not volume. One did stall — the other team's contact was away — so I escalated it the same day with a suggested alternative contact rather than waiting.
Everything legally time-bound went out on time, the critical tables hit the original date, and the receiving analyst thanked us for asking rather than guessing. I've since made 'check what the deadline actually is' our team's standard first step when demands clash. What I took from it: competing priorities are rarely solved by working harder — they're solved by finding out which constraints are real and negotiating the ones that aren't."
Same week, same events. What changed:
- The decision became the candidate's. Version 1 asks the manager to prioritise; Version 2 makes the call on stated logic and informs the manager afterwards.
- The demand got managed, not absorbed. Contacting the receiving analyst and discovering the real constraint is the single highest-value move in the answer — and it's available in almost every real situation.
- The trade-off is named. Split the return, front-load the dependency-heavy work — each with a "because."
- Something goes wrong and gets handled. The stalled request is escalated same-day with a suggested fix, not logged and awaited.
- The reflection is at the grade. "Find the real constraints, negotiate the false ones" versus "stay organised."
A 250-word written example
If you're asked for Delivering at Pace as a written behaviour statement, the same principles compress. Structure it roughly as: situation and your ownership (~40 words), two or three actions each with a "because" (~140 words), quantified result (~50 words), one grade-level reflection sentence (~20 words). The Version 2 answer above, compressed to 250 words with the numbers kept, is exactly the shape a sifter wants — most of the word count on decisions and actions, almost none on scene-setting.
For a full breakdown of the written format, see our guide to 250-word behaviour statement examples.
How Delivering at Pace changes by grade
This is what most guides miss entirely: the same behaviour is scored against different expectations at every grade, and an answer that passes at one level fails at the next.
- AO/EO: own your workload, prioritise it yourself, deliver reliably, flag risks early with the facts gathered. Personal organisation is genuine evidence here.
- HEO: own a piece of work end to end, make the prioritisation call yourself, negotiate constraints with the people who set them, and re-plan when it stops working. The Version 2 answer above is pitched here.
- SEO: re-plan a team, not yourself — delegate with real authority, renegotiate scope upward with a recommendation, and protect the quality steps that manage your biggest risk. Personal heroics actively read as failure to re-plan at this grade.
- Grade 7: pace becomes a system you build — priorities re-set across multiple workstreams, resources moved between teams, pre-agreed triggers and review points so delivery is protected by structure rather than by your hours.
If you're preparing at a specific grade, our complete grade guides (EO, HEO, SEO, Grade 7) cover this calibration in depth for all nine behaviours.
Common mistakes that cap your score
- Outsourcing the decision — "I asked my manager which should take priority." The question was how you prioritise.
- Heroic hours as evidence — extra effort reads as the absence of a plan from EO upward.
- No named trade-off — if nothing was cut, deferred or renegotiated, the panel either doesn't believe the pressure was real or concludes the deadline had slack.
- A frictionless story — nothing goes wrong, nobody is unhappy, and therefore no judgement is visible.
- Spending half the answer on context — the panel knows workloads are high. Get to your actions inside the first thirty seconds.
Every example in this article was written against the same 1–7 rubric your panel will use. If you want to know where your own answers actually land before the real thing, CS Interview Coach's AI gives instant, grade-calibrated feedback on your answers — try it free, or get every guide, the full 250+ question bank and unlimited practice with Interview Sprint at £24.99/month.
Common questions
Delivering at Pace means taking responsibility for delivering timely, quality outcomes — organising your own work, reassessing priorities when demands conflict, and maintaining standards under pressure. At more senior grades it means keeping a whole team focused on the right priorities, not just working quickly yourself.
Common questions include: tell me about a time you worked to a tight deadline; how did you handle competing priorities; describe delivering something with fewer resources than planned; and tell me about a time a deadline was at risk. Panels usually ask one main question plus follow-up probes.
No — personal effort alone is one of the weakest forms of Delivering at Pace evidence. Panels are scoring prioritisation, re-planning and judgement, not hours worked. An answer built on 'I stayed late and got it done' will usually score below the pass mark from EO level upward.
In an interview, two to three minutes. In a written application, most departments ask for a 250-word statement. In both cases the majority of the content should be your actions and the reasoning behind them, not the situation.
Usually yes — most campaigns set the pass mark at 4 per behaviour, though oversubscribed campaigns raise it. A 4 passes; it rarely wins, because appointments are made in merit order.
Yes, especially at EO — volunteering, study and part-time work all count if the prioritisation and ownership were genuinely yours.
Yes, but weight it heavily toward Actions with reasoning. Situation and Task together should be two or three sentences.
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 Free3 free practice questions · No card needed · Cancel anytime