Civil service behaviours examples: 9 winning answers (2026)

Civil service behaviours examples are the single biggest hurdle between you and a Grade 7 offer. The Civil Service receives over 270,000 applications a year (gov.uk Civil Service Statistics, 2024), and 80% fail at the sift because their behaviour examples lack the specificity recruiters score against. This guide gives you nine fully-worked examples — one per behaviour — calibrated to the Success Profiles framework used across all UK government departments in 2026.

Whether you are applying for Fast Stream, an Executive Officer (EO) role at HMRC, or a Senior Civil Service (SCS) position at the Cabinet Office, the behaviours stay the same. Only the level descriptors change.

Table of contents

• What are civil service behaviours?
• Behaviours within Success Profiles (Strengths, Experience, Ability)
• The STAR+L method (and why L is critical)
• Nine civil service behaviours examples
• How sifters score your answers
• Five mistakes that fail the sift
• Reasonable adjustments at sift and interview
• FAQs

What are civil service behaviours?

Civil service behaviours are nine standardised competencies defined in the Success Profiles framework (Civil Service HR, 2018, updated 2024). They describe the actions and activities expected to perform a role well. Each behaviour is assessed against six grade levels, from Level 1 (Administrative Assistant) to Level 6 (Permanent Secretary). Departments specify which behaviours apply to each vacancy and at what level.

The nine behaviours are:

1. Seeing the Big Picture
2. Changing and Improving
3. Making Effective Decisions
4. Leadership
5. Communicating and Influencing
6. Working Together
7. Developing Self and Others
8. Managing a Quality Service
9. Delivering at Pace

Most vacancies test three to five behaviours at sift, with the same behaviours probed again at interview. You will typically have 250 words per written behaviour example on Civil Service Jobs.

Behaviours within Success Profiles (Strengths, Experience, Ability)

Behaviours are only one of four elements assessed under Success Profiles. The full framework also tests:

• Strengths — what you enjoy and do often. Increasingly used at interview alongside behaviours (e.g. "Tell me about a time you felt energised at work"). Strengths-based questions are short, unscripted, and harder to rehearse — answer honestly rather than over-engineering with STAR.
• Experience — your CV or personal statement, where you evidence relevant career history. For Grade 7 and above, expect a 750-word personal statement linked to specific essential criteria.
• Ability — verbal, numerical and judgement tests, particularly for Fast Stream and HEO Faststream entry routes.
• Technical — specialist skills for technical roles (e.g. statisticians, lawyers, engineers).

Strong candidates calibrate every element to the published role profile. A behaviour example that contradicts your CV will fail at interview.

The STAR+L method (and why L is critical)

The Civil Service explicitly recommends STAR (Situation, Task, Action, Result), but the highest-scoring examples we have analysed add an L — Learning. Sifters call this STAR+L or STARL.

Element	Word target	Purpose
Situation	30-40	Context, dates, scale
Task	20-30	Your specific responsibility
Action	120-150	What YOU did (use "I", not "we")
Result	30-40	Quantified outcome
Learning	10-20	Self-reflection, transferability

The Action section is where 70% of marks are awarded. If you spend 150 words on Situation and 50 on Action, you will score Level 2 even if the example is genuinely Level 5.

Nine civil service behaviours examples

The following examples are calibrated to Level 4 (Grade 7 / SEO) — the most contested grade in the Civil Service. Each is 240-250 words to fit the standard character limit.

1. Seeing the Big Picture (Level 4)

Situation: In October 2025, my local authority faced a £4.2 million budget gap in adult social care for 2026-27, with cabinet decisions due within six weeks.

Task: As Policy Officer, I was asked to identify cross-cutting savings that aligned with the Department of Health and Social Care's Joining Up Care priorities.

Action: I started by mapping our spend against the national NHS England Integration Frontrunner programme, identifying three areas where pooled budgets with our ICB could release efficiencies. I reviewed Public Accounts Committee reports from 2024 on similar councils, then interviewed seven service leads to test feasibility. I built a one-page strategic brief connecting our local pressures to the Spending Review 2025 settlement and the government's mission-led approach. I presented options to the Director, flagging political sensitivities around domiciliary care providers and the risk of judicial review if consultation was inadequate.

Result: Two of my three proposals were adopted, generating £1.8 million in confirmed savings and a further £900k in projected savings across 2026-27. The brief was shared with two neighbouring councils as best practice.

Learning: I learned to read sub-national policy through the lens of national strategy — a skill I now apply to every brief.

2. Changing and Improving (Level 4)

Situation: Our team processed 1,400 Subject Access Requests annually with a 38% breach rate against the one-month statutory deadline (UK GDPR, Article 12).

Task: Lead a review of the process and reduce breaches to under 10% within six months.

Action: I mapped the end-to-end process using Lean methodology, identifying that 62% of delay occurred at the initial triage stage. I interviewed eight caseworkers, then benchmarked against the Information Commissioner's Office published guidance and two government departments (DWP, HMRC) via the Cross-Government Data Sharing Group. I designed a tiered triage system: simple requests to a dedicated junior caseworker, complex requests to specialists. I piloted with 100 requests, measured cycle time, then iterated. I built buy-in by running two listening sessions with the team, addressing concerns about workload imbalance.

Result: Within four months, breach rate fell to 7%. Average response time dropped from 28 to 14 days. ICO complaints fell by 60%.

Learning: Frontline involvement in redesign is non-negotiable — my initial draft missed three operational blockers that caseworkers spotted in one meeting.

3. Making Effective Decisions (Level 4)

Situation: During the 2025 winter pressures, my NHS trust faced a 72-hour ambulance handover backlog with no clear escalation lead.

Task: As the on-call Operations Manager, I had to decide whether to declare a Critical Incident, knowing it would trigger NHS England regional involvement and media scrutiny.

Action: I gathered data within 30 minutes: bed occupancy (98%), staffing levels (12 unfilled shifts), regional comparator data from the South West Ambulance Service Trust dashboard. I consulted the on-call Director, the Emergency Department lead, and the regional NHS England duty officer. I weighed the risk of premature escalation (reputational, resource drain) against patient safety risk under the NHS Constitution. I documented my reasoning in a formal decision log, citing the Trust's Critical Incident policy thresholds. I made the call to declare at 19:47.

Result: The declaration unlocked mutual aid from two neighbouring trusts. Handover delays cleared within nine hours. The post-incident review (CQC-aligned) commended the decision timing.

Learning: Decisions under pressure require pre-written thresholds — I now lead quarterly tabletop exercises to test ours.

4. Leadership (Level 4)

Situation: I inherited a team of nine analysts with an engagement score of 41% (Civil Service People Survey 2024), the lowest in our directorate.

Task: Restore engagement above the departmental median (62%) within 12 months while delivering on three statutory reports.

Action: I started with one-to-ones with every team member in my first three weeks, using the Civil Service Leadership Statement as a framework. I identified that the previous manager had withheld stretch opportunities and that two analysts felt sidelined due to part-time working patterns. I rebuilt the work allocation system around capability development, not historic ownership. I championed an analyst's secondment to the Cabinet Office and sponsored two team members for the Government Statistical Service Fast Track. I held myself accountable by sharing my own development plan at team meetings and inviting feedback through anonymous Slido polls quarterly.

Result: Engagement score rose to 71% in the 2025 survey. Two analysts were promoted to HEO. All three statutory reports delivered on time.

Learning: Visible vulnerability builds psychological safety faster than any policy intervention.

5. Communicating and Influencing (Level 4)

Situation: I needed to convince a sceptical Director of Finance to approve a £180k investment in case management software the team had requested for two years.

Task: Secure approval within the Q3 2025 budget cycle, with no precedent in our directorate.

Action: I researched the Director's published priorities — efficiency savings of 5% across 2026-27 — and reframed the request not as a tools upgrade but as a productivity intervention. I commissioned a two-week time-and-motion study showing caseworkers spent 31% of time on administrative duplication. I built a one-page business case using the HM Treasury Green Book five-case model, with NPV calculations over five years showing payback in 22 months. I rehearsed objections with a peer Director, then requested a 20-minute meeting (not 60) to respect her time. I led with the financial outcome, not the technology.

Result: Approval granted within two weeks. Procurement launched October 2025. The Green Book model is now used by three other team leads.

Learning: Tailoring the message to the audience's KPIs, not yours, is the difference between a yes and a no.

6. Working Together (Level 4)

Situation: A cross-departmental project (DWP, HMRC, DfE) on benefit fraud detection had stalled for four months due to data-sharing disagreements.

Task: As DWP lead, restart the project and deliver a working pilot within six months.

Action: I diagnosed the blockage as cultural, not technical: each department feared reputational risk from data exposure. I convened a workshop with information governance leads from all three departments, jointly drafting a Memorandum of Understanding referencing the Digital Economy Act 2017 information-sharing powers. I created a shared OKR dashboard so each department could see progress against their own priorities. I rotated chairing duties to share ownership. When HMRC raised a new concern in week eight, I held a bilateral within 48 hours rather than waiting for the next steering group.

Result: MoU signed within eight weeks. Pilot launched April 2026, identifying £2.3 million in suspected fraudulent claims in the first quarter.

Learning: Cross-government collaboration succeeds when every party can answer "what's in it for my Permanent Secretary?"

7. Developing Self and Others (Level 4)

Situation: I identified a capability gap in policy evaluation across my team of seven, with only one member trained in HM Treasury Magenta Book methodology.

Task: Build evaluation capability across the team within nine months on a zero training budget.

Action: I negotiated free access to the Evaluation Task Force's Knowledge Exchange Programme, securing places for three team members. For the others, I designed an in-house learning circle: weekly 45-minute sessions where team members presented Magenta Book chapters to peers. I matched each team member with an external mentor through the Cross-Government Evaluation Network. I built evaluation skills into objectives at the November review point. For my own development, I enrolled in the National Audit Office's evaluation masterclass and shared learnings monthly.

Result: All seven team members now hold accredited evaluation credentials. The team delivered three Magenta Book-compliant evaluations in 2026, two of which were cited in PAC reports.

Learning: Constrained budgets force more creative development pathways — peer-led learning often outperforms paid courses.

8. Managing a Quality Service (Level 4)

Situation: Our Freedom of Information response service had a 73% on-time rate against the 20-working-day statutory deadline, with rising ICO complaints.

Task: Improve service quality to 95% on-time within six months while maintaining response accuracy.

Action: I introduced weekly quality assurance reviews using a sample of 10% of completed responses, scored against the ICO's published guidance. I created a request-complexity scoring matrix so triage was consistent. I established a 'red flag' escalation route for politically sensitive requests, agreed with the Press Office. I built customer feedback loops by including a one-question survey in every response. I monitored leading indicators (queue depth, time-in-triage) weekly, not lagging indicators (breach rate) monthly.

Result: On-time rate reached 96% in month five. ICO complaints fell from 14 to 2 per quarter. Customer satisfaction (where measured) rose from 58% to 81%.

Learning: Quality systems need leading indicators — by the time the breach rate rises, you are already failing.

9. Delivering at Pace (Level 4)

Situation: Following a ministerial commitment in Parliament, my team was given six weeks to publish guidance affecting 1.2 million UK businesses.

Task: Deliver legally robust, accessible guidance within the deadline with no additional staff.

Action: I structured the six weeks as three two-week sprints. Week 1-2: stakeholder mapping and draft v1, parallel-tracking legal review. Week 3-4: external consultation with five trade bodies, accessibility testing against WCAG 2.2, and Plain English Campaign review. Week 5-6: final sign-off through SCS, ministerial approval, gov.uk publication. I held a daily 15-minute standup at 09:30, eliminated non-essential meetings for the team, and personally cleared two existing commitments. When week four risk emerged (legal flagged ambiguity in one paragraph), I escalated within four hours rather than waiting for the steering group.

Result: Guidance published two days ahead of deadline. Ministerial commitment honoured. Within three months, guidance had 340,000 page views and a 4.7/5 user satisfaction score on gov.uk.

Learning: Pace requires ruthless prioritisation — saying no to good work is the price of delivering on critical work.

How sifters score your answers

Civil Service sifters score each behaviour example out of 7, against published Success Profile level descriptors. To pass sift, you typically need a minimum score of 4 across every behaviour.

Score	Description	What it looks like
7	Outstanding	Clear evidence above the required level
5-6	Strong	All level descriptors met with strong examples
4	Acceptable	Meets required level — pass mark
3	Minor concerns	One or two descriptors not evidenced
1-2	Major concerns	Generic or off-level example
0	No evidence	Answer does not address the behaviour

The Civil Service Commission's principles of fair and open competition require sifters to score against evidence in the application alone — no benefit of the doubt. If you do not write it, it does not count.

Five mistakes that fail the sift

1. Using "we" not "I" — Sifters cannot tell what you did. Replace every "we" with "I" unless genuinely collective.
2. Front-loading Situation — If your first 100 words are context, you have 150 left for evidence. That is not enough.
3. Generic verbs — "Worked on", "helped with", "was involved in". Replace with: led, designed, negotiated, escalated, decided.
4. Wrong level — A Grade 7 example showing Level 3 work fails. Check the Success Profile level descriptors before drafting.
5. No quantification — Numbers, percentages, dates, scale. "Improved process" scores 2. "Reduced cycle time from 28 to 14 days" scores 5.

Reasonable adjustments at sift and interview

Under the Equality Act 2010, the Civil Service must offer reasonable adjustments to disabled candidates at every stage. Common adjustments include:

• Extended time on online tests (typically 25% additional) and for written applications.
• Alternative formats — screen reader-compatible documents, large print, BSL interpreters at interview.
• Modified interview format — questions provided in advance, breaks between sections, panel of two instead of three.
• Disability Confident Scheme — guaranteed interview if you meet the minimum criteria and disclose a disability on application.

Request adjustments at the point of application — they are not retroactive. The recruiting manager has a legal duty to consider every reasonable request and document the decision.

Once your behaviour examples are sharp, pair them with a CV that matches the same standard. Our complete guide to the nine civil service behaviours covers level descriptors in depth, and our NHS CV examples for Bands 5 to 8a show parallel structures for healthcare applications. For broader sector inspiration, our UK CV examples by sector include public sector formats, and our 21 ATS-tested UK CV templates include sage and uk-professional formats designed for public sector applications.

FAQs

What are the 9 civil service behaviours?

The nine civil service behaviours are: Seeing the Big Picture, Changing and Improving, Making Effective Decisions, Leadership, Communicating and Influencing, Working Together, Developing Self and Others, Managing a Quality Service, and Delivering at Pace. They are defined in the Success Profiles framework and apply across all UK government departments and grades.

How do I write a civil service behaviour example?

Use the STAR+L structure: Situation (30-40 words), Task (20-30), Action (120-150), Result (30-40), Learning (10-20). Write in the first person using "I", quantify your results with specific numbers and dates, and check your example matches the Success Profile level descriptor for the grade you are applying for. Stay within 250 words per behaviour.

What is Level 4 in civil service behaviours?

Level 4 is the standard expected at Senior Executive Officer (SEO) and Grade 7. At Level 4, you should demonstrate independent decision-making, leadership of a team or workstream, and the ability to manage across teams or departments. Each behaviour has specific Level 4 descriptors published on gov.uk under the Success Profiles framework.

How long should civil service behaviour answers be?

Most Civil Service Jobs applications allow 250 words per behaviour at sift stage. Some Fast Stream and SCS roles allow 500 words. Use the full word count — short answers signal insufficient evidence. Aim for 240-249 words to maximise scoring opportunity without going over.

Can I use the same example for multiple behaviours?

You can, but it is risky. Sifters mark the strongest behaviour clearly evidenced in each example. A single example stretched across three behaviours will usually score well on one and weakly on the others. Use different examples where possible, and only reuse if the example genuinely demonstrates each behaviour at the required level.

What is the STAR method for civil service?

STAR stands for Situation, Task, Action, Result — the structure recommended by the Civil Service for behaviour examples. Best practice in 2026 extends this to STAR+L by adding Learning, which demonstrates self-reflection valued at Level 4 and above. The Action section should take 60% of your word count, as this is where most marks are awarded.

Do civil service behaviours apply to Fast Stream?

Yes. The Civil Service Fast Stream uses the same nine behaviours but assesses them differently. Sift uses online tests and a video interview rather than written examples. Behaviours are then assessed at the Fast Stream Assessment Centre through group exercises, presentations, and structured interviews. The Success Profiles framework is identical to other grades.

Key takeaways

• The nine behaviours are defined in the Success Profiles framework (gov.uk) and apply to every UK government department.
• STAR+L beats STAR — adding Learning lifts scores at Level 4 and above.
• The Action section earns 70% of marks. Spend 120-150 of your 250 words there.
• Use "I", not "we". Sifters score evidence of your individual contribution.
• Match the level descriptor for the grade — a Level 3 example fails a Grade 7 application.
• Quantify everything: percentages, dates, scale, financial impact.
• Request reasonable adjustments at the point of application — they are not retroactive.