Here's a hard truth: 80% of Civil Service sift failures come from the same five mistakes. Not lack of experience. Not poor qualifications. Just preventable errors in how candidates structure their STAR examples.
The frustrating part? Most people don't know they're making these mistakes until they get the rejection email. The panel won't tell you what went wrong. The feedback will be vague: "Your examples didn't sufficiently demonstrate the required competencies."
This guide shows you exactly what those fatal flaws look like—and how to fix them in under 10 minutes.
Red Flag #1: Vague Action Section
"We decided to implement a new system. We held meetings with stakeholders and we agreed on a timeline. We then rolled out the changes and we saw positive results."
Why this fails: The panel is recruiting YOU, not your team. When you write "we decided," the assessor has no idea what YOUR contribution was. Were you the leader? A participant? Someone who just attended meetings?
The Civil Service Success Profiles framework explicitly requires evidence of individual contribution. Generic team actions don't count.
"I proposed implementing a new system after identifying gaps in the current process. I convened stakeholders from three directorates, securing their buy-in by demonstrating how the change would reduce their administrative burden by 30%. I then led the rollout, personally training 40 staff members and establishing a feedback mechanism to address issues quickly."
Notice the difference? Every sentence starts with "I" and describes a specific action YOU took. This is what panels need to see.
Scan your draft. Count the word "I" and the word "we." If "we" appears more than "I," you're in trouble. Aim for a 5:1 ratio minimum (five "I" statements for every "we").
Red Flag #2: Missing Numbers and Evidence
"As a result of my actions, the team's efficiency improved significantly. Staff morale increased and we received positive feedback from senior management."
Why this fails: "Significantly" is meaningless. "Positive feedback" is unverifiable. The panel will assume you're exaggerating or that the impact was minimal.
Without numbers, your example is forgettable. Panels review 50+ applications. Vague results blend together. Specific numbers stick.
"My actions reduced processing time from 12 days to 7 days—a 42% improvement. Staff survey scores increased from 62% to 81% satisfaction. The Permanent Secretary cited the project as an example of best practice in the departmental quarterly review."
What if you don't have exact numbers? Use credible estimates:
- "Approximately 200 service users benefited"
- "Reduced complaints by an estimated 60%"
- "Saved roughly 15 staff hours per week"
Honest estimates beat vague claims every time.
1. Quantified outcomes: "Reduced costs by £45,000"
2. Timeline evidence: "Delivered 3 weeks ahead of schedule"
3. Recognition: "Shortlisted for departmental innovation award"
Red Flag #3: Too Much Set-Up, Not Enough Action
"In 2019, following the machinery of government changes, our department underwent a significant restructure. The Policy Development team, which had previously sat within Strategy Division under the oversight of the Director General for Operations, was merged with the Implementation unit. This created challenges because the two teams had different working cultures, used different IT systems, and reported to different Ministers. There was also uncertainty about budget allocations and line management reporting structures..."
[Word count: 0/250 used, and they haven't even reached their actions yet]
Why this fails: The panel doesn't care about your organisational history. They care about what YOU did. If you spend 60% of your word count setting the scene, you'll run out of space for the Action section—which is worth 60% of the marks.
"During a departmental restructure that merged two teams with different working cultures, I was tasked with..."
[25 words used. 225 left for Task, Action, and Result]
That's it. One sentence is enough. The panel can infer the complexity. They need to see how YOU navigated it.
Rule of thumb: Your Situation section should be 10% of your total word count. For a 250-word example, that's 25 words maximum. For 500 words, 50 words.
Red Flag #4: Telling Instead of Showing
"I demonstrated strong leadership by motivating the team. I showed excellent communication skills throughout. I displayed resilience when facing setbacks and proved my ability to work under pressure."
Why this fails: These are labels, not evidence. Saying "I demonstrated leadership" doesn't prove you can lead. It's like saying "I'm funny" instead of telling a joke—if you have to say it, it probably isn't true.
Panels are trained to ignore self-assessment. They only mark observable behaviours and actions.
Instead of "I demonstrated leadership":
→ "I chaired weekly steering group meetings, delegated tasks according to team strengths, and provided 1-to-1 coaching to two junior colleagues struggling with the workload."
Instead of "I showed communication skills":
→ "I translated complex technical requirements into plain English for ministerial briefings, adapting my style for different audiences from Grade 7 to SCS level."
Instead of "I displayed resilience":
→ "When the project was paused due to budget cuts, I reprioritised deliverables, secured interim funding from another budget line, and maintained team morale through transparent communication about constraints."
See the pattern? Describe WHAT you did. Let the panel infer the competency.
Ban these phrases from your examples:
❌ "I demonstrated..."
❌ "I showed..."
❌ "I displayed..."
❌ "I proved..."
❌ "This showed my ability to..."
If you're tempted to use them, you're telling instead of showing. Describe the action instead.
Red Flag #5: Passive Voice Overload
"It was decided that a new approach was needed. A working group was established and meetings were held. Recommendations were made and these were implemented. Improvements were seen across multiple metrics."
Why this fails: Passive voice hides who did what. "It was decided" could mean you decided, your manager decided, or the team collectively decided. The panel can't score what they can't attribute to you.
Passive voice also makes you sound less confident and less senior. It's the language of someone who observes rather than acts.
"I decided a new approach was needed. I established a working group and chaired fortnightly meetings. I developed recommendations and secured Senior Leadership Team approval. I led implementation, resulting in improvements across multiple metrics."
Every sentence has a clear subject (I) and action (decided, established, developed). This is the language of accountability and leadership.
How to spot passive voice: If you can add "by zombies" to the end of the sentence and it still makes grammatical sense, it's passive voice.
- "The decision was made [by zombies]" ← Passive
- "I made the decision [by zombies]" ← Doesn't work. Active voice. Keep it.
The 5-Minute Red Flag Check
Before submitting your application, run this quick diagnostic:
Step 1: Open your example in Word or Google Docs.
Step 2: Use Find & Replace to highlight these words in different colours:
- Highlight "I" in green — Should appear 8-12 times in a 250-word example
- Highlight "we" in red — Should appear 0-2 times maximum
- Highlight "was" in yellow — More than 3 instances suggests passive voice
Step 3: Check your Result section. Do you have at least ONE number? If not, add one.
Step 4: Read only your Action sentences. Can you see WHAT you did and HOW you did it? Or just generic claims?
Step 5: Count words in your Situation section. More than 30 words? Cut it.
This takes 5 minutes and will catch 90% of fatal flaws.
What Good Looks Like: A Comparison
Example with 5 Red Flags:
(95 words)
Same Example with Red Flags Fixed:
I conducted a comparative analysis of systems used by HMRC, DWP, and BEIS, interviewing their HR Directors to understand implementation challenges. Using this research, I built a business case demonstrating potential efficiency gains of 20%.
I presented to the Senior Leadership Team, securing £80,000 budget approval. I then chaired a cross-directorate implementation group, personally training 45 line managers on the new system and creating user guides for 200+ staff.
The system launched on schedule. Within 3 months, staff satisfaction scores increased from 58% to 76%, and the time spent on performance reviews decreased by 35%. The Permanent Secretary cited it as an exemplar project in her quarterly stakeholder update."
(157 words)
Notice how the second version:
- ✅ Starts with "I" in most sentences (personal accountability)
- ✅ Includes specific numbers (£80,000, 45 managers, 35% reduction)
- ✅ Minimal background (one sentence)
- ✅ Describes actions, doesn't claim competencies
- ✅ Uses active voice throughout
Common Questions
"What if my role genuinely was collaborative and I didn't do everything alone?"
That's fine—and common in the Civil Service. But reframe it: "I led a collaborative approach" or "I facilitated cross-team working." You can acknowledge teamwork whilst still highlighting YOUR specific contribution.
"What if I don't have access to the numbers anymore?"
Use credible estimates: "approximately," "roughly," "around," "estimated." The panel knows you're not making Excel pivot tables for your application. Ballpark figures based on memory are acceptable.
"Can I use 'we' at all?"
Yes, sparingly. "We achieved the target" as a result sentence is fine. "We decided to" as an action sentence is not. The test: Does the sentence describe YOUR action (I) or the outcome of your action (we/the team)?
Your Action Plan
Here's what to do right now:
- Open your most recent Civil Service application
- Read your behaviour examples looking ONLY for these 5 red flags
- Fix them one at a time using the rewrites above as templates
- Run the 5-minute diagnostic check
- Save the improved version for future applications
These fixes work. They're based on how panels actually mark examples, not theory. Apply them systematically and you'll transform mediocre examples into ones that score.