GOV.UK defines this behaviour as: "Take responsibility for delivering timely and quality results with focus and drive." (Success Profiles: Civil Service behaviours, GOV.UK, Open Government Licence v3.0.) It is the most commonly tested behaviour in operational roles, and the most commonly misread by candidates: panels are not looking for stamina stories. Timely and quality sit in the same sentence deliberately — pace bought by cutting corners fails the behaviour by definition.
This page banks the question in its main forms with four marked model answers: a seasonal surge absorbed, a hard external deadline hit by re-scoping, a fixed-date delivery where scope had to flex, and pace delivered inside governance by someone arriving from the private sector. The marking guidance shows the follow-up each answer is built to survive — usually some version of "what did the speed cost?".
A blunt calibration note: "I worked evenings and weekends" is not this behaviour. Evidence that scores is structural — re-sequencing, re-scoping, removing friction, protecting the critical path — because structure is repeatable and heroics are not.
Practise these questions out loud with a live AI interviewer — free. Start with Try Me
How the marking guidance works
Each model answer below is marked against the four criteria a live aurate session scores:
See how a full session is scored
aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.
Why it's asked: The surge form — standard in operational interviews. Panels want to see demand read early, capacity created by design, and the standard protected while volume ran hot.
Our documents team faced the same spring every year — application volumes roughly doubling for ten weeks — but the year I ran the rota, two experienced staff had just left and the surge forecast was the highest on record. Waiting to see how bad it got was the previous year's mistake; I planned for the forecast instead.
Three structural changes carried it. I moved quality checks from end-of-process to the two error-prone steps, so mistakes were caught in seconds not days. I negotiated with a neighbouring team to borrow two trained staff for the six peak weeks — in exchange for our quiet-season cover in return, which made it a trade my manager could approve rather than a favour. And I built the daily plan around our actual data: applications arrived heaviest Monday and Tuesday, so I stopped spreading effort evenly and front-loaded the week, which alone took two days off our turnaround.
We held our published turnaround standard through the whole surge for the first time in three years, with checked-error rates flat against the quiet season. The trade with the neighbouring team ran again the following year without me — which is the difference between a plan and a rescue.
Marking guide
Why it's asked: The compression form. 'Impossible' deadlines are met by changing the work, not the hours — panels score the re-scoping conversation, the sequencing, and your honesty with whoever owned the deadline about what they would and would not get.
A statutory review response fell to our team with four weeks left on the clock after sitting elsewhere for two months — the deadline was in legislation, so the usual answer of negotiating more time did not exist. The inherited plan needed nine weeks; the deadline needed four.
I spent the first day, not the last, on the scoping conversation with the review's owner. We split the response into what the statute strictly required, what stakeholders expected, and what was tradition — and it turned out nearly a third of the inherited plan was tradition. I cut it, in writing, with her agreement. Then I re-sequenced what remained: the two sections needing input from other teams went out as requests on day one with named deadlines, rather than when we reached them — the previous plan would have discovered a three-week dependency in week seven.
We submitted with two days to spare. The response was shorter than previous years' — 40 pages against a typical 65 — and the review's owner had one substantive amendment. The next year's team started from our four-week plan and our statute-versus-tradition split, which I'd left as a one-page note on the file.
Marking guide
Pace answers meet their own deadline in the room
Two minutes, follow-ups incoming, no notes that matter — the interview itself is a delivering-at-pace exercise. A live aurate session runs your examples under that clock and marks them on the same four criteria as the guidance above. Two free sessions. No credit card.
Try it freeWhy it's asked: The scope-flex form. When the date cannot move, scope is the honest variable — panels want the descope decided early, on user impact, with the right people signing it, and a real plan for what launched late.
We were launching a new online application route on a date that had been announced publicly — immovable in any practical sense — and five weeks out, testing made clear that one of the four planned features, saved-draft applications, would not be reliable in time. The instinct in the team was to push testing harder and hope.
I called it instead: hope is not a plan you can put a date on. I took a one-page recommendation to the service owner in week five, not week two — launch with three features, hold saved drafts, and be plain with users about it. The page set out the user impact honestly: without saved drafts, applications had to be completed in one sitting, which mattered most for the longest form. So the descope came with two mitigations that could be ready: the form's length shown upfront, and a printable preparation checklist so users could gather documents before starting.
We launched on the announced date with three features stable. Saved drafts followed seven weeks later, tested properly, and the completion data showed the checklist had done real work in the gap — abandonment on the long form stayed close to the projections that had assumed drafts would exist. The service owner's note afterwards said the early call was what made the launch calm; the same call in week two would have been a scramble.
Marking guide
Why it's asked: A form aimed at private-sector entrants — and a trap for them. Complaining about governance fails; treating it as a constraint to engineer around, and as protection that earns its keep, scores. Panels want pace achieved with the controls, not despite them.
Coming from an agency where we shipped changes daily, my first departmental project moved at what felt like geological speed — until I noticed that most of the delay wasn't the governance itself, it was the queueing around it. Approvals were sequential by habit, board papers were written after decisions were needed, and every gate was treated as a surprise.
I didn't fight the gates; I scheduled them. At project start I mapped every approval the delivery would need, booked the board slots then — months ahead — and worked backwards from each gate to when its evidence had to exist. Where the process allowed parallel tracks, I ran them: security review alongside user testing rather than after it, which the standards permitted and custom had never tried. And I started drafting each gate's paper the fortnight before, from a running decisions log, instead of in the panicked week it was due.
The project delivered in seven months against the nine of its nearest comparator, having passed every gate first time — which mattered to me, because first-time passes were the proof that the speed hadn't come from thinning the scrutiny. My honest revision: two of the checks I'd initially resented caught things my agency process would have shipped. I said so in the lessons-learned, because arriving sceptical and being converted is more useful evidence than arriving converted.
Marking guide
Why it's asked: The endurance form — 'focus and drive' from the definition, tested over months not days. Panels want the mechanism that kept momentum when novelty wore off: visible milestones, a drumbeat routine, early wins banked — and what you did in the mid-project trough.
Why it's asked: The early-warning form. The score follows the timestamp: risk raised while options still existed, with a recovery plan attached, to the person who owned the consequence. Raising it late with apologies is the failure mode this question exists to find.
Why it's asked: The prioritisation form. Panels want a working method — impact against effort, statutory against discretionary, who is harmed by delay — plus one real example of something you consciously dropped and told people you were dropping.
Why it's asked: The negative form, probing whether your speed has a feedback loop. Strong answers own the mistake specifically, fix the harm, and adjust the system that made the error likely — without retreating into a slower-is-safer answer that fails the behaviour from the other side.
Why it's asked: The strengths-format variant — under a minute, honest. Panels are matching your genuine operating rhythm to the role in front of them, and they can hear a tuned answer. One quick example of you at your best pace does more than any claim of thriving under pressure.
It is the Success Profiles behaviour about taking responsibility for timely, quality results with focus and drive. Panels score where your pace came from — method, sequencing, removed friction — how quality was protected while speed increased, and how honestly you handled what the speed cost.
On its own, no — panels read pure-effort answers as unsustainable and unrepeatable. Extra hours can appear as one honest element of a crunch, but the scoreable evidence is structural: what you re-scoped, re-sequenced or removed so the deadline became achievable. Structure repeats; heroics do not.
Name the check that stayed in place and its result: a sample re-inspected, an error rate held flat, a gate passed first time. The behaviour’s definition couples timely with quality, so an answer that quantifies the speed but not the soundness is only half-evidenced — and panels notice which half is missing.
A missed deadline handled well can still score: early warning given while options existed, a recovery plan proposed, the highest-value elements protected, and the consequence owned rather than narrated. What fails is discovering the miss late or presenting it as weather. Choose the version of events you can defend beat by beat.
Yes — with the Action section carrying the mechanics of where time was found, and the Result carrying both halves of the definition: the date met and the quality evidence. A closing sentence on what the approach made repeatable (a template, a trade, a plan reused) is this behaviour’s strongest final beat.
Two free sessions. No credit card.