UK Civil Service applications work nothing like a normal job application, and that is the single biggest reason capable people get rejected. The Civil Service hires through a structured framework called Success Profiles, scores your written answers against published criteria, and often sifts on those answers before anyone reads your CV. Once you understand how it is marked, the process becomes much more winnable. This guide explains Success Profiles, behaviour statements, the STAR method as the Civil Service expects it, and the mistakes that cost good candidates a sift.
How Civil Service hiring actually works
Applications are assessed against Success Profiles, which can draw on five elements: Behaviours, Strengths, Experience, Ability and Technical. Any given advert tells you which elements apply and lists the specific behaviours being assessed — for example "Making Effective Decisions", "Communicating and Influencing", or "Delivering at Pace". These behaviour names are not decoration: each has a published definition at your grade, and your written answers are scored against it.
Many roles sift on a statement of suitability or individual behaviour statements first. If your written answers do not score, your CV never gets read. Treat the written answers as the application, not an add-on to it.
Read the behaviour at your grade
The Civil Service publishes what each behaviour looks like at every grade, from administrative grades up to senior levels. A behaviour like "Leadership" means something very different at EO than at Grade 7. Before you write a word, find the behaviour descriptor for the advertised grade and note the specific things it asks for — those are the points your example must hit. Writing a strong example that demonstrates the wrong level is a common, avoidable miss.
STAR — the way the Civil Service marks it
Behaviour answers are written in STAR: Situation, Task, Action, Result. The grading reality most people miss is that Action carries most of the marks. Assessors want to see what you personally did, step by step.
- Situation (about 10%). One or two sentences of context. Where, when, what was at stake. No more.
- Task (about 10%). What specifically you needed to achieve, and your responsibility in it.
- Action (about 60%). The detailed, first-person account — "I did", not "we did". Each step should map to a point in the behaviour descriptor.
- Result (about 20%). The outcome, quantified where possible, and ideally what you learned or how it scaled.
This mirrors how the wider UK public sector marks competency answers — the same ratio we cover in our competency-based interview guide.
Write to the word count, in the first person
- Use "I", not "we". Group achievements score nothing if the assessor cannot see your individual contribution. Even in team work, spell out your part.
- Respect the word limit. Behaviour statements usually have a strict limit (often around 250 words each). Going over is penalised or cut off; coming in far under wastes scoring opportunity.
- One strong example per behaviour. A single, well-chosen example demonstrated in depth beats three shallow ones.
- Mirror the descriptor's language. If the behaviour asks you to "identify the main issues" and "take ownership", show exactly those actions and, where natural, use those words.
A worked mini-example (Making Effective Decisions)
Situation/Task: "Our team faced conflicting data on which of two suppliers to renew, with a deadline in three days. I was responsible for the recommendation."
Action: "I gathered the cost and performance data from both contracts, identified that the apparent saving from Supplier B excluded delivery penalties, and consulted the operational lead to confirm the real-world impact. I weighed the financial saving against reliability, documented the assumptions, and set out a clear recommendation with the risks of each option."
Result: "We renewed with Supplier A; on-time delivery held at 98% and we avoided an estimated £12k in penalties the cheaper option would have incurred."
Notice the Action does the heavy lifting and every step shows a decision being made on evidence — exactly what the behaviour asks for.
Mistakes that cost a sift
- Writing about the team, not yourself. The most common failure. Assessors score your individual actions.
- Ignoring the grade descriptor. Demonstrating the behaviour at the wrong level reads as a near-miss and scores low.
- Thin Action, padded Situation. If half your answer is context, you have spent your words in the low-scoring section.
- No measurable result. "It went well" is not a result. Quantify or describe a concrete outcome.
- Reusing one example for everything. Choose a distinct, best-fit example for each behaviour.
Once your written answers are strong, make sure the CV behind them is clean and parser-safe — see our ATS-friendly CV guide — and choose a clear layout from our UK CV templates.
FAQ
- What are Success Profiles?
- Success Profiles is the framework the UK Civil Service uses to assess candidates, drawing on up to five elements: Behaviours, Strengths, Experience, Ability and Technical. Each advert states which elements apply and names the specific behaviours being assessed, each of which has a published definition at the advertised grade that your answers are scored against.
- How do I write a Civil Service behaviour statement?
- Use STAR — Situation, Task, Action, Result — and spend most of your words on the Action, written in the first person. Read the behaviour descriptor for the advertised grade first, choose one strong example that hits its points, mirror its language where natural, and finish with a measurable result, all within the word limit.
- Why is the Action section so important?
- Because assessors are scoring what you personally did against the behaviour descriptor, and the Action is where that evidence lives. It typically carries the majority of the marks, so a thin Action — even with strong context and outcome — scores poorly. Keep Situation and Task brief and detail your steps as "I did".
- Does my CV get read in a Civil Service application?
- Often not at the first stage. Many roles sift on your written behaviour statements or statement of suitability before any CV is read, so if those answers do not score you are rejected regardless of your CV. Treat the written answers as the application itself.
- How long should each behaviour answer be?
- Up to the stated word limit, which is commonly around 250 words per behaviour. Going over is penalised or truncated, and coming in well under wastes scoring opportunity, so write a full, detailed answer that lands inside the limit.
Atlas helps you prepare structured, evidence-led applications — including STAR behaviour answers and a parser-safe CV — across every UK sector, public and private. Create a free account to build your next application with a head start.