Changing and Improving Example: Civil Service Worked Answers

Updated 8 November 2026 · By K K Vasishtha

A strong changing and improving example for a civil service application or interview follows the STAR method: a specific problem you spotted, a change you drove (not just suggested), the resistance you managed, and a measurable result. The Civil Service Success Profiles framework assesses this behaviour at every grade, from AO to SCS, so the depth of your example should match the seniority of the role ^[1]^[2]. The four worked examples below cover different contexts and levels.

What the Civil Service is actually looking for

Changing and Improving is one of the nine behaviours in the Civil Service Success Profiles framework ^[1]. It is not about being busy or enthusiastic about change. Assessors want evidence that you identified a genuine problem, took ownership of a solution, brought others with you, managed risk, and delivered a result that stuck.

The behaviour is assessed at every grade. At AO and EO level, the expectation is that you improved your own work or a team process. At HEO and SEO, you should have led a change across a team or function. At G7 and G6, the change should have had departmental or cross-organisational reach. At SCS, you are expected to have shaped culture or strategy ^[2].

Before you write a word, ask yourself four questions about your example:

Did I spot the problem myself, or was I told to fix it? (Spotting it yourself is stronger.)
Did I implement the change, or just recommend it? (Implementation is what scores.)
Was there any resistance or risk? (How you handled it shows maturity.)
Can I point to a concrete outcome — time saved, error rate reduced, user satisfaction improved?

If you cannot answer all four, find a different example or build out the one you have before you submit. For more on structuring any behavioural answer, see our guide to the STAR method for civil service interviews.

Changing and Improving example 1: EO level — process improvement in a customer-facing team

Reducing duplicate casework at EO level (illustrative example)

Situation: I was working in a benefits processing team handling around 200 cases a week. I noticed that roughly one in ten cases was being reopened within a fortnight because a standard supporting document had been missed at the initial assessment stage. This was creating extra work for colleagues and delays for claimants.
Task: My role was as a caseworker, so I had no formal authority to change the process. I decided to investigate the root cause and propose a fix, then make the case to my line manager to adopt it.
Action: I spent two weeks logging every reopened case and identifying which document type was most commonly missing. I found that one particular form — a third-party income declaration — was the most frequent culprit by a clear margin. I drafted a one-page checklist to be completed before a case was marked ready for decision. I shared a draft with three colleagues to check it was practical, incorporated their feedback, then presented it to my manager with the data. I also offered to run a short team briefing so everyone understood why the checklist existed, not just what it asked.
Result: The checklist was adopted across the team within three weeks. Over the following two months, reopened cases in that category fell by around half. My manager asked me to document the approach so it could be shared with two other teams in the office.

This works at EO level because the candidate spotted the problem independently, used data to make the case, involved colleagues before escalating, and can point to a measurable outcome. The scope is appropriate — it is a team-level fix, not a departmental overhaul.

Changing and Improving example 2: HEO level — digital tool adoption across a team

Introducing a shared tracking tool to replace email chains (illustrative example)

Situation: I managed a policy support team of six people. We were coordinating responses to parliamentary questions using a shared email inbox and a spreadsheet that only one person could edit at a time. Deadlines were being missed because no one had a live view of which questions were in progress, with whom, and at what stage.
Task: As the team leader, I was responsible for our on-time delivery rate. I needed to find and implement a better system without disrupting output during a busy parliamentary session.
Action: I mapped our existing workflow and identified three pinch points where handoffs were failing. I then trialled a lightweight project-tracking tool already available on our departmental licence — no procurement needed. I ran a two-hour pilot with two willing colleagues, refined the workflow, then brought the rest of the team on board with a short demonstration. I was transparent about the learning curve and set a four-week review point so the team knew they could raise problems. One colleague was sceptical about the extra steps; I paired them with one of the early adopters for the first week, which resolved the concern.
Result: By the end of the parliamentary session, our on-time completion rate had improved noticeably. The team reported feeling less anxious about deadlines because they could see the status of every question at a glance. The approach was later adopted by a neighbouring team after our deputy director saw it in action.

This example is well-pitched for HEO because the candidate led the change, managed a sceptic constructively, used existing resources (no budget ask), and the outcome spread beyond the immediate team. Notice the risk management: the four-week review point shows the candidate thought about what could go wrong.

Changing and Improving example 3: SEO/G7 level — cross-team process redesign

Redesigning a grant assessment process to cut turnaround time (illustrative example)

Situation: I was a senior manager overseeing a grant-funding programme. An internal audit flagged that our average assessment turnaround was significantly above the published service standard, and a backlog had built up. The existing process involved four sequential sign-off stages, each sitting with a different team.
Task: I was asked to lead a review and bring forward recommendations within six weeks. The expectation was a report; I decided to go further and implement the changes myself, with senior agreement.
Action: I mapped the end-to-end process with representatives from each of the four teams. We identified that two of the four sign-off stages were duplicating the same quality check. I proposed collapsing them into a single parallel review, with a shared template so both reviewers worked from the same evidence pack. I ran a stakeholder session to get buy-in, including with a head of profession who was initially resistant because the change affected her team's sign-off authority. I worked with her to redesign the template so her team's specific concerns were captured explicitly — this addressed the substance of her objection rather than overriding it. I then piloted the new process on a cohort of ten applications before rolling it out.
Result: Average turnaround time fell by around a third within the first quarter of the new process. The backlog cleared within five months. The approach was written up as a case study for the department's continuous improvement community.

At SEO and G7 level, assessors expect you to have navigated genuine organisational complexity. This example shows cross-team working, a stakeholder who pushed back (and how that was resolved substantively, not just managed away), a pilot before full rollout, and a result that was formally recognised.

Changing and Improving example 4: G6/SCS level — cultural and strategic change

Embedding a user-research culture in a policy directorate (illustrative example)

Situation: I led a policy directorate that had historically developed guidance with limited direct input from the people it affected. An external review found that several recent guidance documents had needed significant revision after publication because they did not reflect how users actually operated. This was costly and damaged credibility with delivery partners.
Task: I needed to change how the directorate approached policy development — not just add a consultation step, but shift the underlying assumption that policy professionals knew best without testing their thinking.
Action: I worked with the head of our user research function to design a mandatory discovery phase for all significant guidance projects. I made the case to my director general by framing it in terms of rework cost and reputational risk, not process compliance. I then modelled the behaviour myself by sitting in on three user research sessions and sharing what I had learned in all-staff communications — being explicit that I had found the sessions challenging because they questioned assumptions I had held. I commissioned a small community of practice for policy leads to share what they were learning. I also adjusted performance objectives for deputy directors to include evidence of user insight in their project plans.
Result: Within 18 months, every major guidance project in the directorate included a documented discovery phase. Two projects were reshaped significantly as a result of early user research, avoiding the kind of post-publication revision that had triggered the original review. Staff survey responses on innovation and continuous improvement improved in the directorate's next pulse survey.

This example works at G6 and SCS level because the change is cultural, not just procedural. The candidate modelled the behaviour personally, used levers available at their level (performance objectives, all-staff communications), and the outcome is systemic rather than project-specific.

Common mistakes — and how to avoid them

Most weak changing and improving answers fail in one of five ways. Knowing them helps you check your own example before you submit.

Mistake	Why it hurts your score	Fix
Describing a change that was handed to you	Shows compliance, not initiative — the behaviour is about driving change	Find an example where you spotted the problem or volunteered to lead the fix
Stopping at the recommendation	Assessors want implementation, not just ideas	Make sure your action covers what you actually did to make the change happen
No resistance or risk	Sounds unrealistic; misses a key part of the behaviour	Include at least one person who was sceptical and how you brought them along
Vague results ('things improved')	Cannot be scored against the behaviour indicators	Quantify where you can: time saved, error rate, volume processed, satisfaction score
Scope too big for the grade	Suggests the example is exaggerated or borrowed	Match the reach of your change to the seniority of the role you are applying for

A common trap at every level is using 'we' throughout. Assessors are assessing you. Use 'I' for your actions and 'we' only when describing collective outcomes. For more on this, see the wider guide to civil service behaviours examples.

Check your example against the Success Profiles behaviour indicators for the grade you are applying to before you finalise it. The indicators are published on GOV.UK and differ meaningfully between levels ^[2].

Pre-submission checklist for your changing and improving answer

Run your draft answer through this checklist before you submit or walk into the interview room.

The situation is specific — a named project, team or problem, not a general description of your job.
You identified the need for change yourself, or took clear ownership when asked.
Your actions are in the first person and describe what you did, step by step.
You name at least one obstacle — a sceptic, a constraint, a risk — and explain how you handled it.
The result is concrete and attributable to your actions.
The scope of the change matches the grade of the role.
The whole answer fits within the word count (250 words for application forms; roughly two minutes spoken in an interview).

If you are applying for a role that also tests other behaviours, the worked examples for communicating and influencing and making effective decisions are worth reading alongside this page, since those behaviours often appear together with changing and improving on job descriptions.

Once you have a draft answer, the best way to stress-test it is to say it out loud under interview conditions. Interview Coach gives you eight role-specific questions, STAR feedback on each answer, and a model answer to compare against — with one free session.

Frequently asked questions

Can I use a non-civil-service example for changing and improving?

Yes. The Civil Service Success Profiles framework assesses the behaviour, not the sector ^[2]. An example from the private sector, NHS, local government, a charity or even a voluntary role is fine, provided it is specific, shows you driving change rather than just participating in it, and is pitched at the right level of seniority for the role you are applying for.

How long should a changing and improving answer be on an application form?

Most civil service application forms set a 250-word limit per behaviour. Use roughly 50 words on situation and task combined, around 130 words on your actions (this is what scores), and 70 words on the result and any learning. Do not pad the situation — assessors read dozens of answers and reward concision.

What if my example involved a change that was later reversed?

It is still usable. Focus on what you did, why you did it, and what you learned. If the change was reversed for reasons outside your control, say so briefly and explain what the experience taught you. Assessors value self-awareness. What they do not want is an answer where the candidate blames others for the reversal.

Do I need a different example for the application form and the interview?

Ideally, yes. Interviewers will have read your application, so using the identical example in the room adds nothing. Prepare your strongest example for the form, then have two or three others ready for the interview. Probing questions may also take you into territory your written example does not cover, so depth across multiple examples is valuable.

How do I show innovation if my role is quite routine?

Changing and improving does not require a dramatic transformation. A process you streamlined, a template you redesigned, a way of sharing information you introduced — these all count. The key is that you spotted the gap, took action, and can show the outcome. Routine roles often have the most visible inefficiencies, which makes them good hunting grounds for examples.

Is changing and improving the same as delivering at pace?

No. Delivering at pace is about maintaining quality output under pressure and meeting deadlines. Changing and improving is about identifying what needs to be different and making it so. An example can overlap — a process change that also improved speed — but the focus of your answer should match the behaviour being assessed. See the delivering at pace worked examples for comparison.

Related guides

Managing a Quality Service Example: Civil Service Worked Answers
Four worked STAR examples for Managing a Quality Service in civil service interviews, plus what good looks like and the mistakes to avoid.
Civil Service Personal Statement Example: How to Write One That Works
A practical UK guide to writing a civil service personal statement, with a full worked example, STAR structure, word count tips and common mistakes to avoid.
Communicating and Influencing Example: Civil Service Answers That Score
Four illustrative STAR examples for the Civil Service Communicating and Influencing behaviour, with grade-by-grade guidance and common mistakes to avoid.
Civil Service Behaviours Examples: What They Are and How to Answer Them
Clear civil service behaviours examples for every grade, plus how to structure STAR answers that score well at application and interview. Free to read.
STAR Method Civil Service: How to Structure Winning Answers
How to use the STAR method in civil service interviews and written applications. Practical steps, worked examples, and a pre-interview checklist.
Seeing the Big Picture Example: Civil Service Worked Answers
Four worked STAR examples for the Civil Service Seeing the Big Picture behaviour, from EO to G6. Includes what good looks like and common mistakes to avoid.

Sources

K K Vasishtha is a career coach and the founder of Your AI Career Copilot. She builds tools that help UK professionals prepare for interviews and adapt their careers to AI. We update this page when the facts change. Spotted something wrong? Email support@youraicareercopilot.com.