A Changing and Improving statement should show a real improvement, not simply that you were present while something changed.
With only 250 words, the strongest answers move quickly from the problem to the decisions you made: how you understood the cause, involved people, tested the change and made sure the result was genuinely better.
For the broader behaviour explanation, use the Changing and Improving Civil Service guide.
Choosing an example that gives you something to score
Choose a situation where you had some ownership of the improvement. It can be a small process, a piece of guidance, a digital change or a different way of organising work.
The example becomes stronger if you can show that the first answer was not obvious. Perhaps different colleagues wanted different things, the existing system had constraints, or a change that looked efficient would have created a problem elsewhere.
Avoid choosing a story where senior management designed the change and your only role was to tell people about it. That may demonstrate communication, but it leaves very little Changing and Improving evidence for you personally.
Use B-STAR underneath the writing
Interview Detectives structures behaviour evidence with B-STAR: Belief, Situation, Task, Action, Result. Use it to keep the story complete, but let the finished statement read like a normal account of what you did.
Belief
Keep the Belief to a natural sentence rather than a slogan. One workable version is:
I believe improvement works best when you understand the problem first, involve the people who use the process and make the simplest change that solves it.
Situation
Set up the problem in a few lines. The reader needs the obstacle, not the history of the process.
Task
Make your role in the improvement unambiguous before describing the change.
Action
Use the Action to show how you diagnosed the problem, tested ideas, involved users, handled challenge and adjusted the solution. “I implemented” is never enough on its own.
Result
Show what became easier, clearer, faster or more reliable. Use real measures where you have them, but a credible operational result is better than an invented percentage.
Full Changing and Improving 250 word statement example
I believe improvement works best when you understand the problem first, involve the people who use the process and make the simplest change that solves it.
My EO team logged new casework in a shared mailbox, copied the details into a spreadsheet and then entered them into the case system. The spreadsheet had become a duplicate record, but colleagues were reluctant to remove it because they used it to see ownership at a glance.
I was asked to reduce the administration without losing that control.
I mapped the process with two experienced caseworkers and checked which spreadsheet fields were genuinely used. Most information was already available in the case system; the gap was allocation and exception tracking. I built a simple intake form and ownership view using our existing SharePoint tools rather than requesting a new system.
I asked colleagues to use it alongside the spreadsheet for a short trial. Their feedback showed the exception route was unclear and one field was awkward to complete using keyboard navigation, so I changed both before the wider switch. I also produced a short guide based on the cases people handled most often.
The team stopped maintaining the duplicate spreadsheet and used the new view for daily allocation. Morning backlog checks became quicker, ownership was clearer and the revised approach remained in place after the trial.
Example word count: 223. This leaves some room below the maximum. A statement should stop when the evidence is strong enough, not when the counter reaches 250.
B-STAR breakdown
| B-STAR part | What the example shows |
|---|---|
| Belief | Sets out a practical approach to improvement: understand, involve, simplify. |
| Situation | The team maintains a duplicate spreadsheet because it still provides one useful control. |
| Task | Reduce unnecessary administration without losing visibility of ownership. |
| Action | Maps the process, checks what is actually used, builds on existing technology, trials the change and adjusts it after accessibility and exception feedback. |
| Result | The duplicate record is removed, allocation is clearer and the new approach is retained. |
Why this statement works
The candidate does not assume the spreadsheet is pointless simply because it duplicates data. They first work out why colleagues still rely on it.
The solution is proportionate. Rather than inventing a large technology project, they use tools the organisation already has and focus on the missing control.
The trial adds credibility because the first version is not perfect. Feedback exposes two practical problems and the candidate fixes them before wider use.
The result is operational and believable. The process is simpler and clearer, with no need for a suspiciously precise time-saving claim.
Need more examples before you write yours?
The grade-specific statement packs cover all nine behaviours with worked examples at your level. They show how improvement evidence develops from practical fixes into wider change, challenge and sustainable implementation.
What changes by grade?
AA/AO
Notice better ways of working, learn new procedures, make sensible use of technology and raise problems with change constructively.
EO
Review how work is done, suggest practical improvements, respond positively to change and help colleagues understand and use new approaches.
HEO/SEO
Work with others to simplify processes, use technology intelligently, invite ideas from a wide range of people and explain the reasons for change.
G6/7
Create space for challenge and innovation, understand the full effect of change on people and users, use technology where it adds value and challenge senior proposals when needed.
Explain what was wrong before you explain what was new
A reader cannot judge whether your improvement was worthwhile unless they understand the original problem. One or two concrete symptoms are usually enough.
Then move on. The statement should not become a history of why the organisation had always worked that way.
Show how other people shaped the change
Good consultation is visible in the final design. If a colleague, customer or specialist raised a concern, explain what you did with it.
This is particularly useful when the feedback made your first idea better rather than simply confirming you were right.
Keep the improvement proportionate
Senior-sounding technology does not make an example stronger. The best solution may be a simpler form, a clearer handoff or a better sequence of work if that is what the problem actually needs.
Show the before and after without wasting words
You need enough of the old process to make the improvement meaningful, but not a full process map. One concrete sentence about the duplicated work, delay or error is usually enough.
Then make the new state equally concrete. “The spreadsheet was removed and allocation moved into the shared view” is more useful than “efficiency improved significantly”.
Use resistance as part of the evidence
If somebody questioned the change, do not automatically edit that difficulty out. A valid concern gives you a chance to show listening, adaptation and proportionate implementation.
What matters is how you handled it. Treating every objection as negativity can make the answer look less open to improvement, not more.
Common problems in 250-word statements
Starting with the shiny solution. The assessor needs to understand the problem and your reasoning, not just the technology or process you introduced.
Change for its own sake. Replacing something that already works is not automatically improvement. Show the benefit that justified the disruption.
Consultation theatre. Saying people were consulted adds little unless their input affected the design or decision.
Ignoring adoption. A technically clever improvement that nobody uses is not a strong result.
Pretending there was no resistance. Real change usually creates concerns. Handling them well is often part of the best evidence.
A final check before you submit
Before submitting, read it without the B-STAR headings in mind. The problem, your improvement decisions and the outcome should still be obvious.
Do not bolt a percentage onto the ending just to make it look measurable. Use the evidence the role could realistically know.
Build the rest of your application evidence
The grade-specific statement packs cover all nine behaviours with worked examples at your level. They show how improvement evidence develops from practical fixes into wider change, challenge and sustainable implementation.
Preparing for interview instead? Go to Changing and Improving Civil Service interview questions and answers.
