Civil Service Success Profiles: How to Structure Your CV & Behaviours (UK)

Civil Service Success Profiles: How Your CV and Behaviours Get You Through the Sift

Success Profiles is the Civil Service's recruitment framework, and it assesses you on up to four elements — Behaviours, Strengths, Experience and Technical skills — rather than the old competency system. To pass a sift, your application must map evidence directly to the specific behaviours named in the job advert, usually written in STAR format, while your CV provides the supporting Experience narrative. Most rejected applicants fail not because they lack ability, but because they submit generic statements that don't address the advertised behaviours at the right grade level. This guide explains each element, shows you two full example behaviour statements, and gives you a CV structure that works for Civil Service applications. For general formatting rules that apply across UK employers, our complete UK CV format guide covers length, spelling and layout conventions first.

What Are Success Profiles and Why Did They Replace Competencies?

The Civil Service moved away from the old Common Standards framework to Success Profiles so departments could hire against what a role actually demands instead of a single rigid competency list. Under the current framework, a vacancy will draw on some or all of these four elements:

• Behaviours — how you act and deliver in role. There are defined behaviours such as Communicating and Influencing, Delivering at Pace, Making Effective Decisions, Working Together, Seeing the Big Picture and Changing and Improving. The advert tells you which ones are assessed and at what grade.
• Strengths — what you naturally do well and enjoy. Assessed through quick-fire interview questions ("What gives you energy?"), rarely at sift.
• Experience — your track record: roles, achievements and context. This is where your CV matters most.
• Technical — profession-specific qualifications or knowledge, such as finance qualifications for analyst grades or policy experience for policy roles.

Every advert states which elements apply and how they'll be weighted. Read that section before writing a single line of your application — it is effectively the marking scheme. If behaviours are sifted at 250 words each, those statements carry far more weight than your CV itself.

How Does the Civil Service Sift Actually Work?

A sift panel scores your application against pre-agreed criteria, typically using a scale where a pass mark exists per criterion. Panels cannot award marks for implied ability: if a behaviour asks about leading stakeholders and you never mention leading anyone, you score zero for that evidence, however senior you are. Three practical consequences follow:

1. Everything is marked anonymously by rubric. Name-dropping impressive employers earns nothing unless the sentence demonstrates the behaviour being scored.
2. Grade level matters. The same behaviour means different things at EO, HEO, SEO and Grade 7. An HEO statement should show managing your own delivery and influencing peers; an SEO statement should show leading others and shaping direction. Borrowing a statement pitched too low caps your score even when it reads well.
3. Recent evidence wins. Panels prefer examples from roughly the last two years and your most recent roles. A brilliant 2015 example is weaker than a solid 2025 one.

This evidence-mapping discipline mirrors other structured public-sector processes — if you're applying across sectors, our NHS supporting statement guide explains the same person-specification logic in healthcare settings.

Which Behaviours Will You Be Asked For?

Most adverts select three or four behaviours from the Success Profiles framework. The most frequently assessed include:

Check the exact wording in your advert — the Civil Service publishes definitions and level descriptors for every behaviour, and panels mark against those descriptors, not against a dictionary definition of the title.

Writing Behaviour Statements in STAR Format

Nearly all behaviour statements follow STAR: Situation, Task, Action, Result. Where applicants go wrong is predictable:

• Too much Situation. Two or three sentences maximum. The panel scores your actions, not your backstory.
• "We" instead of "I". Panels can only credit what you did. Say "I drafted", "I persuaded", "I analysed" — even inside a team effort.
• No result. Close with an outcome, ideally quantified: time saved, error rates down, satisfaction improved, money protected. If a precise figure isn't available, attribute qualitatively ("feedback from stakeholders improved", "the deadline was met two days early").
• Dumping everything into Action. Action deserves roughly half your word count. Structure it as four to six deliberate steps.

Example Behaviour Statement 1: Communicating and Influencing (HEO Level)

Situation: My department needed frontline caseworkers to adopt a new digital case-management system, but early briefings had been met with resistance — staff feared the tool would slow them down during a backlog peak.

Task: As the change lead for my team of eleven caseworkers, I was responsible for securing genuine buy-in so that adoption reached the required standard before the legacy system was switched off eight weeks later.

Action: I began by listening rather than broadcasting. I ran three short drop-in sessions where staff voiced specific concerns, and I recorded the five issues raised most often. I then worked with the system trainer to redesign our team's guidance around real case scenarios staff recognised, replacing the generic national manual for local use. When two long-serving colleagues remained openly sceptical, I asked them to test the new process on live cases with me beside them, incorporating their corrections publicly so the guidance carried their endorsement. I shared a weekly one-page update showing what had changed in response to feedback, and I escalated one legitimate design flaw — a duplicated data-entry step — to the digital team, who fixed it before rollout.

Result: My team reached full adoption a week ahead of the department-wide deadline, and our error rate on migrated cases was among the lowest in the directorate. Staff survey comments specifically praised the way concerns had been listened to, and my scenario-based guidance was adopted by two neighbouring teams.

• Annotation: Roughly 240 words. Notice the shape: two sentences of situation, a task that names the applicant's responsibility, action occupying over half the statement with distinct steps, and a result with concrete outcomes plus qualitative recognition. Every sentence contains something the panel can tick against the HEO descriptor — tailoring the message, addressing resistance, and influencing beyond own authority via escalation.

Example Behaviour Statement 2: Delivering at Pace (SEO Level)

Situation: Following an unexpected ministerial announcement, my unit had five working days to produce a robust options analysis that would normally have taken six weeks, while continuing business-as-usual casework.

Task: As senior officer on the project, I had to re-plan the workload, secure analytical support from another team, and deliver an accurate submission to the deadline without cutting corners on quality assurance.

Action: I immediately broke the analysis into three separable workstreams and identified which could run in parallel. I negotiated with the economics team's lead to borrow an analyst for four days, offering our casework support in return so the ask felt reciprocal rather than extractive. Recognising that waiting for complete data would consume the whole window, I agreed with my Grade 7 that we would publish clearly-labelled provisional figures and commit to a follow-up annex — managing expectations upward rather than silently risking the deadline. I set a mid-point checkpoint on day three to catch errors early, and I personally quality-assured the final figures against source data the evening before submission. When a stakeholder challenged one assumption on day four, I arranged a same-day call rather than letting the query sit in an inbox over the weekend.

Result: The submission arrived on time and was accepted without correction requests — the only unit in the directorate to achieve this. My Grade 7 cited the work in my performance review, and the parallel-workstream approach became the unit's template for subsequent urgent pieces.

• Annotation: At SEO level the panel expects leadership of others and management upward — note the negotiation with another team's lead and the expectation-setting with the Grade 7. The result includes a benchmark comparison ("only unit") which strengthens it without inventing fake statistics. Adapt both structures freely; never copy text verbatim, since assessors recognise recycled examples and plagiarism checks exist.

How Should You Structure a CV for a Success Profiles Application?

Not every Civil Service vacancy requires a CV — many use the online application form alone — but when one is requested, treat it as your Experience evidence base. The structure that works best:

1. Header. Name, city, phone, email — in the document body, never a Word header or footer, because recruitment platforms frequently fail to extract them there.
2. Personal statement. Four lines tying your background to the specific role and department. Generic statements read as bulk-application signals to panels.
3. Key achievements. Three or four bullets that preview your strongest behaviour-aligned wins with numbers where honest.
4. Employment history. Reverse chronological. Under each role, prioritise bullets that demonstrate the advert's behaviours in action. Mirror the vocabulary of the advert — "stakeholder engagement", "options appraisal", "risk register" — wherever genuinely true.
5. Education and professional qualifications. Include any technical-element requirements explicitly (charterships, degrees, profession memberships).
6. Additional information. Volunteering, secondments or committee roles only where they evidence behaviours you haven't shown elsewhere.

Keep it to two pages, British spelling throughout, no photo and no date of birth. Because Civil Service applications often flow through platforms like Trac or departmental portals, clean single-column formatting protects your content from mangling — our ATS resume checklist walks through file-safe formatting step by step.

What About Strengths Questions?

Strengths are almost always assessed at interview, not sift, so they shouldn't reshape your CV. But prepare for them: strengths questions come fast and feel odd ("Would you say you are a perfectionist?", "When did you last change something you do regularly?"). The Civil Service wants authentic energy and enjoyment, not rehearsed competency answers. The practical preparation is self-knowledge: know which parts of work energise you, and answer quickly and honestly rather than strategically. Over-engineered strengths answers score worse than natural ones.

Common Mistakes That Fail Good Candidates at Sift

• Answering a different behaviour than the one asked. If the advert asks for Changing and Improving, a great Delivering at Pace story scores zero on that criterion.
• Pitching below grade level. Re-read the level descriptors. If the role is SEO, your statement must show you led the work, not contributed to it.
• Reusing one statement across applications unchanged. Each advert's context differs; tailor the situation and result to the hiring department's world. The same principle applies to CV tailoring generally — see how to tailor your resume to a job description for the systematic method.
• Burying the result. Panels skim. Put outcomes in the final two sentences where they land.
• Ignoring the technical element. If the role lists a required qualification, state yours verbatim — including membership numbers where relevant.

If you're unsure whether your CV survives the initial automated handling before human eyes see it, checking it against the advert's language takes minutes: our post on resume match score benchmarks explains what a strong keyword match looks like across employer types.

Key Takeaways

• Success Profiles assesses Behaviours, Strengths, Experience and Technical — the advert's "how to apply" section is your marking scheme.
• Write behaviour statements in STAR with "I" actions taking half the word count and a quantified-or-attributed result at the end.
• Pitch examples at the advertised grade, keep them recent, and tailor each application rather than recycling.
• Structure your CV around the Experience element: achievements up front, behaviour-evidencing bullets under each role, technical qualifications explicit.

Next Step: Check Your Match Before You Submit

Before investing hours in behaviour statements, make sure your CV itself speaks the advert's language. Paste the job description into JD2CV's free CV builder and match checker to see which Success Profiles keywords are missing from your document — then close the gaps honestly and submit an application built to score.