A Delivering at Pace statement should show how you kept important work moving when the original plan came under pressure.
The best evidence is usually a set of choices: what became critical, what could wait, where resource moved, how ownership was kept clear and which standards remained non-negotiable.
For the broader behaviour explanation, use the Delivering at Pace Civil Service guide.
Choosing an example that gives you something to score
Choose a situation with genuine delivery pressure: a fixed deadline, late dependency, sudden workload, reduced resource or competing priorities.
The example needs enough ownership for you to change something. If your only action was to work faster on the task you were already given, the evidence may be too narrow.
At senior grades, look for a story where you delivered through other people and made deliberate trade-offs rather than personally absorbing every problem.
Use B-STAR underneath the writing
Start from B-STAR: Belief, Situation, Task, Action, Result. The purpose is to make the evidence easy to follow, not to turn the application into a formula.
Belief
Start with a simple statement of approach and avoid grand claims. For example:
I believe pace comes from making priorities clear and removing obstacles early, while protecting the controls that make the result safe and usable.
Situation
Make the delivery pressure clear in a few lines so most of the word count remains available for your response.
Task
Make your delivery responsibility clear before the recovery actions begin.
Action
Use Action to show how you reset priorities, changed resource, removed barriers, delegated decisions, monitored the critical path and escalated when something required support beyond your authority.
Result
The Result should show delivery against the important commitment while confirming that essential quality, assurance or service requirements were not traded away.
Full Delivering at Pace 250 word statement example
I believe pace comes from making priorities clear and removing obstacles early, while protecting the controls that make the result safe and usable.
As an HEO, I was coordinating a service update with a fixed launch date when a supplier delivered a required data feed five days late. Two lower-value enhancements were still in development, leaving a much shorter window for testing and operational preparation.
I needed to recover the plan without weakening mandatory assurance.
I rebuilt the critical path with the technical lead and moved the two enhancements into the next release so the team could concentrate on the core service. I reassigned an experienced analyst to prepare test data while the supplier completed the feed and agreed twice-daily decision points with the supplier for anything that could block testing.
I delegated routine coordination to the workstream owners and used a short risk review to focus only on issues that could affect launch. I kept security checks and operational acceptance in the plan despite pressure to compress them, because neither could be safely recovered after go-live.
The core service launched on the agreed date with the required assurance completed. The deferred enhancements were delivered in the following release, and no critical live issue was traced to the compressed timetable.
Example word count: 210. The statement fits under 250 words. Finishing early is better than weakening it with padding.
B-STAR breakdown
| B-STAR part | What the example shows |
|---|---|
| Belief | Frames pace around clear priorities, early obstacle removal and protected controls. |
| Situation | A supplier delay compresses the remaining delivery and assurance window. |
| Task | Recover the fixed launch without weakening mandatory assurance. |
| Action | Rebuilds the critical path, defers lower-value work, moves resource, sets rapid decision points, delegates routine control and protects key checks. |
| Result | The core service launches on time with assurance complete; deferred work follows later without a critical issue caused by the recovery. |
Why this statement works
The candidate does not treat every feature as equally important. Deferring two enhancements creates a credible priority rather than an empty statement about focus.
Reassigning an experienced analyst before the dependency arrives uses the waiting time productively and shortens the recovery path.
The answer is also clear about what cannot be sacrificed. Security and operational acceptance stay in the plan even when the timetable becomes uncomfortable.
The result is believable because it distinguishes the core launch from the deferred work instead of claiming that everything was somehow delivered early.
Need more complete Delivering at Pace statements?
The grade-specific statement packs cover all nine behaviours with worked examples at your level. They help you compare how prioritisation, control, recovery and delivery through others should develop as responsibility increases.
What changes by grade?
AA/AO
Organise your own work, keep quality steady, follow the right procedures and keep managers or stakeholders updated.
EO
Set clear goals, monitor workloads, remove barriers, make sure colleagues have what they need and take corrective action when delivery slips.
HEO/SEO
Keep the team focused on the highest priorities, monitor milestones, rebalance work when demands conflict and give people room to deliver while retaining accountability.
G6/7
Make priorities and ownership clear, set performance standards, provide the right resources, maintain delivery under pressure and keep legal, regulatory and security requirements intact.
Show what you deprioritised
A good pace example often becomes clearer when the reader knows what you deliberately stopped, delayed or reduced.
That is usually stronger than saying you “focused on priorities” without naming one.
Make ownership visible
If you were leading others, explain who owned the work and what decisions they could make without coming back to you.
Senior pace is often about creating fast decisions through others rather than increasing your own workload.
Protect the non-negotiables
Quality, legal, regulatory, security or safety controls may constrain the plan. Showing how you preserved them can strengthen the behaviour rather than making the example seem slower.
Fit the recovery plan into 250 words
You do not need to list every milestone. Name the thing that threatened delivery, the two or three decisions that materially changed the plan and the controls you kept in place.
That gives the assessor a much clearer picture than a chronological diary of meetings, trackers and reminders.
Show when you escalated
Escalation can be good evidence when the problem requires authority, resource or a decision beyond your control. Explain why you escalated at that point and what you asked for.
“I escalated the risk” on its own is passive. “I escalated for an additional engineer because the supplier could not recover the critical path with the existing team” shows judgement.
Common problems in 250-word statements
Busyness as evidence. Long hours and a full diary do not show how you controlled delivery.
Everything is urgent. If nothing can be stopped or deferred, the answer contains very little prioritisation.
Quality quietly disappears. Delivering faster by skipping essential controls is usually poor evidence, not pace.
Micromanagement. Senior candidates should show clear ownership and delegation rather than personally chasing every task.
No recovery signal. Explain how you knew the plan was getting back on track, not just that you kept pushing until the deadline arrived.
A final check before you submit
A final read should show the pressure, your priority choices, what you protected and the delivery result without relying on generic claims about working hard.
Delivery figures are helpful when they were part of the work. Do not invent savings, percentages or throughput claims simply to decorate the Result.
Build the rest of your application evidence
The grade-specific statement packs cover all nine behaviours with worked examples at your level. They help you compare how prioritisation, control, recovery and delivery through others should develop as responsibility increases.
Preparing for interview instead? Go to Delivering at Pace Civil Service interview questions and answers.
