Civil Service Behaviour Examples: STAR Structure Guide with Real Examples

Civil Service behaviour examples are the most frequently asked-about topic among UK government job applicants. Whether you are writing a 250-word example for an application form, preparing for a panel interview, or trying to understand why a previous application did not score well, the answer usually comes back to the same thing: the examples did not clearly show what you did, at the right level, with a clear outcome.

The Civil Service Success Profiles framework defines eight core behaviours. Every role advertises which three to five are being assessed. You are expected to demonstrate — in writing or verbally — how you have shown each behaviour through real experience.

Most candidates know what STAR stands for. The problem is execution. Examples that are too vague, too generic, or spend too many words setting the scene and too few on the actual actions are the most common reasons applications do not score well.

This guide covers all eight Civil Service behaviours, explains what assessors are looking for in each one, and provides full STAR example answers written to HEO and SEO level as a baseline — with notes on how to adjust for other grades.

What Are Civil Service Behaviours?

Civil Service behaviours describe the actions and activities that result in effective performance in a role. They are part of the Success Profiles framework, introduced in 2019 to give a more complete picture of what candidates can do, how they do it, and what they are motivated by.

There are eight behaviours in the current framework:

• Seeing the Big Picture
• Changing and Improving
• Making Effective Decisions
• Leading and Communicating
• Collaborating and Partnering
• Building Capability for All
• Managing a Quality Service
• Delivering at Pace

Each job advert specifies which behaviours are being assessed for that particular role. A policy advisory post might prioritise Seeing the Big Picture and Making Effective Decisions. A service delivery role will weight Managing a Quality Service and Delivering at Pace more heavily. Leadership roles typically include Leading and Communicating and Building Capability for All.

When you are asked for behaviour examples — either in written form on the application or verbally at interview — the assessor compares your answer against a level descriptor for that grade. The descriptor describes exactly what good looks like at that seniority. Your job is to give them an example that matches it.

How to Use the STAR Method for Civil Service Behaviour Examples

STAR structures your answer into four parts:

• Situation: Brief context. Where were you and what was the challenge or background?
• Task: Your specific responsibility within that situation.
• Action: What you personally did. This is where assessors find their marks.
• Result: What changed. What was the outcome of your actions?

The single most common mistake candidates make is the wrong distribution of words. In a 250-word example, most people write 80 to 100 words on Situation and Task — context the assessor does not need in detail — and leave only 100 words for Action. This inverts the scoring structure entirely.

A well-structured 250-word example should allocate roughly 30 to 40 words to Situation, 20 to 30 words to Task, 140 to 160 words to Action, and 30 to 40 words to Result. In verbal interview answers, this means two sentences of context, then the bulk of your answer on what you specifically did and why.

The Action section must describe your personal contribution. Phrases like "the team worked on" or "we decided to" do not score — assessors cannot separate your contribution from what others did. Use "I" throughout the Action section.

Grade Calibration: What Changes at Each Level

The same behaviour looks different at different grades. Before writing any example, check the grade descriptor in the job advert and ensure your example matches that scope.

At Administrative Officer and Executive Officer level, examples should show competent delivery within a defined process. You followed the right procedures, communicated clearly, and completed tasks to a good standard.

At Higher Executive Officer and Senior Executive Officer level, assessors expect independent judgement, managing complexity or ambiguity, influencing others without formal authority, and taking accountability for outcomes. The situation should involve some genuine difficulty or trade-off.

At Grade 7 and Grade 6 level, examples should show strategic scope, delivering through others, managing significant risk or uncertainty, and producing impact at programme or directorate level.

A strong HEO example would be a weak G7 example. Match the scope and judgement in your example to the grade you are applying for — not just your job title.

Behaviour 1: Seeing the Big Picture

Seeing the Big Picture is about understanding the wider context of your work — how your role connects to organisational goals, political priorities, and the external environment. Assessors want to see that you looked beyond your immediate task and used that wider understanding to make better decisions or produce better outcomes.

At higher grades, this includes horizon scanning: identifying emerging risks or opportunities before they become urgent, and connecting day-to-day delivery to longer-term objectives.

The most common weakness in Seeing the Big Picture examples is describing someone who received context rather than someone who sought it out and acted on it.

STAR Example — Seeing the Big Picture (HEO level)

I was working as policy lead in a team responsible for maintaining guidance documentation when a new government spending review was announced. My immediate brief was to update the documents against existing policy.

Rather than completing the task in isolation, I reviewed the spending review publications and cross-departmental briefings that went beyond my direct remit. I identified three sections of guidance that were likely to become outdated within six months based on the direction signalled in those documents. I wrote a short impact assessment for the programme team, consulted two colleagues in adjacent teams with specialist knowledge of the affected areas, and proposed to my Grade 7 that we flag those sections as under review rather than publishing them as final. I presented the assessment at our next team meeting and recommended a phased publication approach, setting out the risk of not doing so in terms the team could act on.

The programme team adopted the phased approach. The flagged sections were updated within three weeks of the spending review outcome rather than requiring a full redraft. My manager noted that proactive horizon scanning had saved an estimated two weeks of rework across the team.

What Weak Looks Like

"I always try to understand how my work fits into the wider priorities of the organisation." This is a claim, not evidence. It contains no situation, no specific action, and no result. It scores nothing.

Behaviour 2: Changing and Improving

Changing and Improving is about actively identifying opportunities to make things better — not waiting to be directed, but spotting where processes, outputs, or ways of working could be more effective and doing something about it. At higher grades, it also means creating a culture where your team is comfortable proposing and leading change themselves.

Assessors want to see initiative, a specific idea or intervention, and evidence that the change actually happened and made a measurable difference. Examples that describe suggesting an idea which went nowhere do not score as well as examples where you drove the change through to completion.

STAR Example — Changing and Improving (HEO level)

My team ran a monthly internal reporting process that required six colleagues to manually extract data from separate systems and compile it into a single spreadsheet. The process took around three working days each month, involved frequent manual errors, and regularly delayed the final report reaching senior leaders.

I mapped the process end to end and identified the compilation stage as the main bottleneck. I found that two of the six data sources were compatible with a reporting tool already available on our systems. I built a prototype automated extract for those two sources, tested it against three months of previous data to confirm accuracy, and documented it clearly. I then brought the remaining four colleagues together, demonstrated the approach, and worked with them to agree a consistent data format for their manual extracts that would make the final merge significantly faster. I proposed a revised schedule that moved the process two days earlier to allow more time for quality checking, and ran a short session to walk the team through the changes before the first live run.

The monthly process was reduced from three working days to one. Error rates dropped because the two automated sources removed the main causes of discrepancy. The team lead formally adopted the revised process, and it has run consistently to schedule for every reporting cycle since.

Behaviour 3: Making Effective Decisions

Making Effective Decisions is about using evidence and judgement to reach timely, proportionate decisions — including when information is incomplete, stakeholders disagree, or the stakes are significant. At SEO level and above, this behaviour carries particular weight because decisions regularly involve real consequences, limited certainty, and competing interests.

Assessors want to see not just that you reached a decision, but how you reached it: what information you gathered, what you weighed up, how you handled uncertainty or risk, and whether the outcome was proportionate.

STAR Example — Making Effective Decisions (SEO level)

I was senior responsible officer for a grant programme when a key delivery partner flagged that they were at risk of missing a milestone due to an unexpected staffing issue.

I had to decide whether to enforce the existing grant conditions — which would trigger a formal breach and potential clawback — or to agree a variation. The decision had financial, reputational, and programme implications and needed to be made quickly. I gathered information from three sources: the partner's formal notification and evidence of the staffing issue; our internal risk register to assess the downstream impact of a delay; and legal guidance on the conditions under which a variation could be agreed. I identified that the partner had a strong delivery record, the issue was genuinely exceptional rather than a pattern of underperformance, and the programme impact of a breach would be more disruptive than a short extension. I also identified that agreeing a variation without conditions could set an unhelpful precedent for the programme. I decided to agree a six-week extension on three conditions: a revised milestone plan, fortnightly check-ins during the extension, and written confirmation that the staffing issue had been resolved. I documented my reasoning in full and briefed my Grade 6 before communicating the decision to the partner.

The partner met the revised milestone on time and the programme remained on track. My manager confirmed the decision was well-reasoned and proportionate. The documentation I had produced was later used as a template for other grant variation decisions across the team.

Behaviour 4: Leading and Communicating

Leading and Communicating is about being clear, engaging, and effective when presenting information, leading others through change, or influencing stakeholders. Assessors want to see that you adapted your approach to your audience and that people responded to your leadership — not just that you delivered information or ran a process.

At HEO level, strong examples typically involve communicating something complex clearly or leading a team through something unfamiliar. At SEO and above, examples should involve more complex stakeholder environments, greater resistance to overcome, or higher-stakes communication.

STAR Example — Leading and Communicating (HEO level)

My team of fourteen was asked to move to a new digital case management system. There had been two previous failed digital projects in the directorate, and several colleagues were openly sceptical. My Grade 7 asked me to lead the communications and change management for the rollout alongside my normal workload.

I started by having informal conversations with six colleagues who had been most vocal about their concerns. I wanted to understand what had actually gone wrong before, rather than offer generic reassurance. I used what I heard to shape specific, honest communications rather than standard change management language. I ran two small group sessions: one focused on addressing the concerns of the most resistant colleagues by showing exactly how their daily tasks would be affected and what would stay the same; one for the wider team covering practical benefits and a clear timeline. I produced a one-page summary updated weekly throughout the transition and set up a brief daily check-in for the first two weeks so colleagues could surface issues before they became blockers. I also identified two colleagues who could act as informal champions and briefed them separately so they had the answers when peers came to them first.

The implementation completed on schedule. A team survey at the end of the first month showed that eleven of fourteen colleagues rated the transition as well-managed. The two colleagues who had been most resistant both became informal peer supporters for newer team members during onboarding.

Behaviour 5: Collaborating and Partnering

Collaborating and Partnering is about building productive working relationships — within your team, across your organisation, and with external stakeholders — and using those relationships to deliver things that would not have been possible alone. Assessors want to see that you proactively built or maintained a relationship, navigated a genuine challenge or disagreement, and produced a shared outcome.

At senior grades, this includes managing complex stakeholder landscapes, resolving significant conflicts, and bringing together people with genuinely different interests to reach agreement where others have not.

STAR Example — Collaborating and Partnering (SEO level)

I was responsible for coordinating a cross-departmental review of shared digital infrastructure involving three government departments with different priorities and a history of disagreement over governance. Two previous attempts over three years had failed to reach agreement.

I met individually with the senior lead from each department before any joint session. My aim was to understand their actual interests rather than their stated positions, and to identify where alignment was being obscured by process friction. I found all three departments agreed on two of the five main issues, and the remaining disagreements were partly about ownership language rather than substance. I redesigned the review structure so the two areas of agreement were confirmed in the first joint session — building momentum — and the three contested issues were taken into focused working groups with terms of reference I drafted to ensure the scope was neutral and could not be claimed by any single department. Between sessions, I kept each department's senior lead personally informed so there were no surprises in the joint meetings. When one working group reached an impasse, I arranged a separate conversation between the two leads before bringing them back to the group.

All three departments signed off on joint recommendations for the first time. Two of the three contested areas were resolved without escalation. The third required a brief Director-level escalation, but the documentation I had maintained meant it was resolved quickly. The programme director described the approach as a model for future cross-departmental work.

Behaviour 6: Building Capability for All

Building Capability for All is about developing others — not just through formal training, but through coaching, creating stretch opportunities, sharing knowledge proactively, and being inclusive in how you identify and support people's development. Assessors want evidence that you invested in a specific person or group, tailored your approach to their actual needs, and that their capability measurably improved.

The word "all" is deliberate. Strong examples often include an element of equity or inclusion — ensuring that development is accessible to everyone on the team, not just the most visible or confident individuals.

STAR Example — Building Capability for All (HEO level)

I line-managed a team of four Executive Officers, one of whom had recently been promoted from AO level and was struggling with the independence expected at the higher grade. Her work was accurate, but she was routinely seeking sign-off on decisions within her own authority, creating delays and visibly affecting her confidence.

I had a structured conversation with her to understand the root cause. She told me she was unsure whether her judgement was reliable at the new grade, having worked to clearly defined processes at AO level. I put together a three-part development plan: a weekly thirty-minute one-to-one where we reviewed one decision she had made independently — not to check the outcome, but to discuss her reasoning and reinforce what she had done well; a written list of the decision types she was explicitly authorised to make without escalation, removing ambiguity; and a buddy arrangement with an experienced EO in a different team who could answer practical questions informally. I also deliberately assigned her to lead a small piece of stakeholder analysis independently, with an explicit brief that I was available only if she encountered something outside the scope.

Over three months, the frequency of unnecessary escalations reduced significantly. By the end of that period she was operating with appropriate independence and had taken on a small project leadership role. In her mid-year review conversation, she identified increased confidence as her single biggest development during the period.

Behaviour 7: Managing a Quality Service

Managing a Quality Service is about delivering consistently to the standard users expect — and actively working to understand where you are falling short, why, and how to fix it. Assessors want to see that you took ownership of quality, not just delivery.

At HEO level, strong examples involve identifying a performance gap, understanding its root cause, and implementing a targeted improvement. At SEO and above, examples should involve setting service standards, managing others to deliver against them, and using data to drive continuous improvement across a team or function.

STAR Example — Managing a Quality Service (HEO level)

My casework team had a published service standard of fifteen working days for correspondence responses. Over a three-month period, our average response time had risen to twenty-two days and we had received a formal complaint from an external stakeholder.

I analysed our case data for the previous three months and found that 60 per cent of the delay was concentrated in two stages: initial triage and the final sign-off step. I spoke individually with three team members who worked on those stages to understand the practical causes. For triage, the categorisation criteria were ambiguous, leading to cases being reassigned multiple times. For sign-off, I was the sole authority and was not always available quickly enough. I rewrote the triage criteria in direct consultation with the colleagues who did that work day to day, so the criteria reflected what was genuinely unclear in practice rather than what looked clear on paper. I identified two colleagues at the appropriate grade to whom I formally delegated sign-off authority, after running a half-day briefing session. I introduced a weekly case-age report so the team could see at a glance which cases were approaching the target without needing me to prompt them.

Our average response time dropped from twenty-two days to thirteen days over six weeks — below the published standard. The formal complaint was resolved. The revised triage criteria were subsequently adopted by two other casework teams in the directorate.

Behaviour 8: Delivering at Pace

Delivering at Pace is about maintaining effective output under pressure — managing competing priorities, making proportionate trade-offs, and keeping momentum when the situation changes. Assessors want to see that you managed the pressure actively, not just that you worked hard.

Strong examples involve genuine complexity in the workload or timeline: competing demands, unexpected obstacles, or resource constraints. Examples that simply describe a deadline you met without explaining how you managed the pressure around it tend not to score as highly.

STAR Example — Delivering at Pace (HEO level)

Three weeks before a ministerial submission deadline, two of my six team members went on unplanned absence simultaneously. We had a complex briefing to deliver that had been scoped for the full team.

I immediately mapped all outstanding tasks against the deadline and categorised them into essential and non-essential. I identified which elements genuinely required the expertise of the absent colleagues and which could be covered by those remaining. I contacted one absent colleague and asked for a short written briefing note on the one section requiring their specialist knowledge, keeping the request minimal and specific. I restructured the remaining work into a clear daily plan shared with the team each morning so progress was visible without additional coordination overhead. On day two, I escalated to my Grade 7 — not to request resource at that stage, but to ensure they were informed of the risk early and would not be surprised later. When it became clear that one analytical section would not meet our usual quality standard in the time available, I flagged this proactively in the submission itself and proposed a follow-up note rather than waiting to be asked.

The submission was delivered on time. The follow-up note was provided three days later. My Grade 7 noted that the early escalation and transparent management of the situation had allowed them to stay appropriately informed throughout without needing to intervene directly.

Common Mistakes That Cost Marks

Writing about what the team did rather than what you did is the most common mistake. Assessors score your contribution, not your team's. Use "I" throughout the Action section. You can reference the team in Situation and Task, but every sentence in Action must describe something you personally decided, produced, or changed.

Using vague language damages scores consistently. Phrases like "I worked collaboratively," "I communicated effectively," or "I supported the team" describe outcomes without describing actions. Tell the assessor exactly what you said, decided, produced, or changed — and why you made those specific choices.

Omitting a clear result is a persistent pattern in poorly-scoring examples. Every behaviour example needs to end with something that changed: a decision made, a process improved, a person developed, a deadline met. If you cannot identify a result, the example may not be strong enough for the grade.

Choosing examples that are too junior for the grade is a problem many candidates do not spot. If you are applying at Grade 7 but your examples describe tasks an EO could carry out, the assessor will not uprank their scoring based on your job title. The scope and complexity of the example must match the level descriptor.

Going over the word limit signals poor judgement. Writing 350 words when 250 is specified does not demonstrate thoroughness — it demonstrates an inability to prioritise. Edit the Situation and Task sections ruthlessly. Every cut should come from context, not from Action.

How to Build Your Behaviour Example Bank

Before writing any application, build a bank of five to seven strong examples from your career that you can adapt across the eight behaviours.

For each example, note the situation in one sentence, the specific actions you took, the outcome, and which behaviours it could demonstrate. Many good examples are flexible: a process improvement story can show Changing and Improving, Managing a Quality Service, or Delivering at Pace depending on which aspect of the Action you foreground.

When an application asks for a specific behaviour, select the example from your bank that gives you the richest Action section for that behaviour. Edit everything else down to fit the word count — almost all cuts should come from Situation and Task.

Review each example against the level descriptor for the grade in the job advert before submitting. The descriptors tell you exactly what assessors are scoring against. If your example does not match the level, choose a different one rather than trying to reframe it.

Tools like SpecMatch can help you test your examples against job advert criteria before you submit — identifying where your evidence is thin and which requirements you have not yet covered.

FAQs

What are Civil Service behaviour examples?

Civil Service behaviour examples are written or verbal accounts of real situations from your past experience that demonstrate one of the eight behaviours in the Success Profiles framework. Each example follows the STAR structure: Situation, Task, Action, Result.

How long should a Civil Service behaviour example be?

Most application forms specify 250 words per behaviour, though some allow up to 500. Always check the advert and stay within the limit. Going over the word limit signals poor judgement about what matters, which can count against you.

What are the 8 Civil Service behaviours?

The eight behaviours in the Success Profiles framework are: Seeing the Big Picture, Changing and Improving, Making Effective Decisions, Leading and Communicating, Collaborating and Partnering, Building Capability for All, Managing a Quality Service, and Delivering at Pace.

How do I calibrate my examples to the right grade?

At EO level, demonstrate competence within defined processes. At HEO and SEO, show independent judgement, ownership of outcomes, and managing complexity. At G7 and G6, show strategic scope, delivering through others, and organisational-level impact. Match the scope and complexity of your example to the level descriptor in the job advert — not just your current job title.

What is the most important part of a Civil Service behaviour example?

The Action section. This is where assessors find every scoring mark. Situation and Task provide context. The Result demonstrates impact. But the Action — what you specifically did, how you thought about it, what judgement you exercised — is where all scoring decisions are made. It should account for at least 60 per cent of your word count.

What is the difference between Civil Service behaviours and strengths?

Behaviours are evidence-based: assessors score you against specific descriptors using past examples. Strengths are authenticity-based: assessors look for whether you genuinely enjoy an activity and whether it comes naturally to you. Many roles assess both. Our Civil Service strengths-based interview guide covers how to prepare for strengths questions differently.

Can I use the same example for more than one behaviour?

Yes, as long as you change the focus of the Action section for each behaviour. A process improvement example can show Changing and Improving, Delivering at Pace, or Managing a Quality Service depending on which aspect you foreground. Do not submit identical text for two behaviours — assessors read all examples together and repetition suggests limited range of experience.

What makes a Civil Service behaviour example score poorly?

Using "we" instead of "I," describing actions in vague terms, omitting a clear result, choosing examples too junior for the grade, and going over the word limit are the most common reasons behaviour examples score poorly.

Conclusion

Civil Service behaviour examples are won or lost in the Action section. The Situation gives context. The Result demonstrates impact. But what assessors actually score is the Action — what you specifically did, how you thought about it, and what level of judgement you exercised at the grade you are claiming.

Use the examples in this guide as benchmarks for what well-structured answers look like at HEO and SEO level. Your examples need to come from your real experience, calibrated to the grade you are applying for, and written with enough specificity that an assessor who has never met you can picture exactly what you did and why.

For the written application that surrounds these behaviour examples, understanding how to read the person specification correctly is the foundation. Our guide on what a person specification is explains how hiring panels use the document to shortlist — so you know exactly what you are being assessed against before you write a word. And if your role involves a strengths-based interview alongside the written behaviours, our Civil Service strengths-based interview guide covers the different preparation approach those questions require.