An AO Changing and Improving statement should show that you can spot a better way of doing something, learn new procedures and help changes work in practice.
At Administrative Officer level, the example does not need to be a major transformation. A strong statement can come from improving a routine process, using a digital tool more effectively or helping colleagues adopt a new way of working.
Need more AO Changing and Improving examples?
The dedicated guide contains worked 250 word statements written for AO and AA applications.
What Changing and Improving means at AO level
🔎 Review how work is done: notice where a process causes delays, errors or unnecessary effort.
💡 Suggest improvements: put forward practical changes rather than only pointing out a problem.
💻 Use digital tools: consider whether technology can make routine work easier or more reliable.
📚 Learn new procedures: adapt when guidance or systems change.
🤝 Support colleagues: help other people understand the new approach where you can.
⚠️ Raise issues constructively: query problems caused by a change and respond appropriately when something unexpected happens.
How to structure the 250 word statement
Keep the background short so the assessor can see the change you made and the effect it had. B-STAR works well for this behaviour.
💭 Belief: one sentence on why you look for practical improvements.
📍 Situation: explain the process or problem.
🎯 Task: state what you were responsible for.
🛠️ Action: show what you changed, how you tested it and how you supported others.
📈 Result: finish with a clear improvement in service or efficiency.
AO Changing and Improving 250 word statement example
I believe small improvements to routine work can save time and make services more reliable for both customers and colleagues.
As an Administrative Officer, I noticed that our team stored customer correspondence across several shared folders with inconsistent file names. This made documents difficult to find and sometimes caused colleagues to duplicate work.
I reviewed the folders and recorded the most common problems. I suggested a simple naming convention and a single folder structure based on case number and document type. Before making any changes, I tested the approach on a small group of closed cases and asked two colleagues to use it and tell me what was unclear.
Their feedback showed that one category was too broad, so I split it into two clearer document types. I then created a one-page guide with screenshots and showed colleagues how to use the new structure. I also raised an issue with our existing permissions so the team lead could arrange the correct access before rollout.
Once the approach was agreed, I helped move current documents into the new structure and answered questions during the first week.
The team could find correspondence more quickly and stopped creating duplicate copies. The naming convention was then adopted for new cases, giving the team a clearer and more consistent way to manage records.
Why this example works
✅ It starts with a genuine problem in everyday work.
✅ The candidate suggests a practical improvement and tests it before wider use.
✅ Colleague feedback changes the final approach.
✅ A permissions issue is raised through the correct route instead of being ignored.
✅ The result shows a more consistent process rather than relying on a vague claim.
Common weaknesses
❌ Describing a change that somebody else designed while saying little about your own contribution.
❌ Choosing a change that did not improve the work in any clear way.
❌ Focusing only on technology without explaining the service problem it solved.
❌ Saying colleagues were trained without showing what support you personally gave.
Want examples across every AO/AA behaviour?
For interview preparation, see the related AO Changing and Improving interview guide.
Choosing an AO Changing and Improving example
The strongest AO examples are often small improvements with a clear practical benefit. You do not need to lead a major project. You do need to show that you noticed a problem and contributed to a better way of working.
📁 Simplifying a filing or record-management process.
☎️ Improving how common customer queries are handled.
💻 Learning a new system and helping colleagues use it correctly.
📝 Updating guidance after spotting repeated mistakes.
🚨 Responding sensibly when a change creates an unexpected issue.
Quick check before you submit
✅ Is the problem clear within the first few sentences?
✅ Does the assessor know what you personally suggested or changed?
✅ Have you shown how you learned or supported a new procedure?
✅ Is there a practical result that shows the new way was better?
Keep the example factual. A simple improvement explained properly is stronger than making a routine change sound larger than it was.
