How to answer the 'tell me about a time when' questions every promotion board asks — and why most candidates answer them wrong.
Section 1 — Why boards use STARR: the science behind the structure
STARR is not a presentation trick. It is a structured behavioural interview framework, and its use in police promotion boards is grounded in forty years of occupational psychology research. Meta-analyses of structured competency-based interviews consistently show they are among the most valid predictors of job performance available — significantly more accurate than unstructured interviews, application forms, or even many psychometric assessments.
The underlying principle is straightforward: the best predictor of how you will perform in the next rank is how you have already performed in similar situations. When a panel asks 'tell me about a time when you took ownership of a difficult problem', they are not looking for a story. They are looking for evidence — specific, verifiable, first-person evidence — that you have already demonstrated the behaviour required at the rank you are targeting.
This is why 'what would you do' answers score poorly in a STARR question. Hypotheticals describe your intentions. STARR answers describe your proven behaviour. The panel is assessing whether you have already done the job at the level required — not whether you understand what good looks like in theory.
Each question targets one or more of the six CVF competencies. Your answer must demonstrate the specific Level 2 descriptors the panel is assessing. Knowing the five letters of STARR is the starting point, not the destination. The candidates who score highest are those who understand exactly which competency is being assessed, select an example that genuinely evidences it at the right level, and deliver it in a way that makes the panel's job easy.
Section 2 — STARR vs STAR: why the fifth element matters
If you have been in policing for any length of time you know STAR. Every promotion process for the last twenty years was built around it. The upgraded model — STARR — adds a fifth component: Reflection. This was not a cosmetic change.
The CVF competency framework explicitly expects officers at sergeant level and above to demonstrate self-awareness, learning orientation, and a commitment to continuous professional development. A STAR answer tells the panel what you did. A STARR answer tells the panel what you did and what kind of leader you are becoming. The Reflection component is where that distinction is made.
STAR answers
Describe what happened
Prove you can act at that level
Score at the competency level
STARR answers
Describe what happened
Prove you can act at that level
Score at the competency level
Show what you learned from it
Demonstrate self-awareness and growth
At Inspector level and above, a missing or weak Reflection is a significant scoring liability — not a minor omission. Build your Reflection first. If you cannot articulate a specific change in your practice, your answer is not ready.
Section 3 — The five components in detail
S — Situation
Set the scene briefly. The panel needs context — not a story.
Without context the panel cannot assess whether your actions were appropriate. But spend too long on context and you have used up your time before describing what you actually did. A strong Situation is two to three sentences and takes no more than 10–15% of your total answer time. Treat it like a briefing note, not a narrative.
Weak
"So this was about two years ago, I think it was a late shift, and there'd been a few jobs already that evening, and the Sergeant was off sick, so I was..."
Strong
"About eighteen months ago, I was acting Sergeant on a late shift when we received a high-priority missing person report — a fourteen-year-old girl with significant mental health vulnerabilities who had left a care setting in distress."
Common mistake
Treating Situation like the whole story. If you are spending more than sixty seconds setting the scene, you have the proportions wrong and the panel will notice.
T — Task
State your specific accountability. What were YOU responsible for?
Promotion boards assess your individual capability, not your team's. The Task component makes your personal responsibility explicit. Without it the panel cannot tell whether you led, supported, or simply happened to be present. After your Situation, explicitly signal your role: 'As acting Sergeant, my responsibility was...' or 'I was personally accountable for...'
Weak
"We had to deal with it."
Strong
"As acting Sergeant, I was responsible for coordinating the immediate response — deciding deployment, liaising with the care home, and making the call on whether this met the critical incident threshold."
Common mistake
Conflating Task with Situation. They are separate. Situation is what happened; Task is what you personally owned. Candidates who blur the two often produce answers where the panel cannot identify the individual's accountability.
A — Action
Describe what YOU did. First person. Specific. The biggest section.
This is where the competency is actually demonstrated. Everything before Action is setup; everything after is consequence. Action is where the panel scores you, and it should take 45–55% of your total answer time. Use 'I' throughout. 'We' is the single most common reason strong candidates score amber instead of green. Every sentence should show a decision, a communication, or a specific behaviour — not a generalisation.
Weak
"We did all the usual things — searches, family contact, the normal missing person procedures."
Strong
"I graded this as a critical incident based on the vulnerability profile. I briefed the team, tasked the student officers on a localised search paired with an experienced colleague, and personally took the lead on intelligence gathering by challenging the care home's initial account, which I suspected was incomplete."
Common mistake
Collective voice. Watch for 'we decided', 'the team did', 'we all agreed'. Replace every instance with 'I decided', 'I directed', 'I ensured'. If you genuinely shared a decision, say 'I discussed with X and we agreed — and I took responsibility for implementing it.'
R — Result
State what happened. Quantify where you can. Never skip this.
Without a Result the answer is structurally incomplete. A strong Action with no Result is like a case file with no conclusion. The Result is also where you demonstrate impact: numbers, feedback, and observable changes carry far more weight than 'things improved'. If the outcome was mixed or negative, say so — panels respect honesty, and a strong Reflection can turn a difficult outcome into your strongest answer.
Weak
"We found her eventually and it was a good outcome."
Strong
"The girl was located safe within ninety minutes. The DI later commended the early escalation decision. The vulnerability flagging process I subsequently developed with the care home has since reduced search times across three further incidents."
Common mistake
Rushing the Result because you have run out of time. If this happens consistently when you practise, you are spending too long on Situation or Action. Use a stopwatch and reverse-engineer your proportions.
R — Reflection
State what you learned and how it changed your practice.
This is the component that separates STARR from STAR, and it is not optional at sergeant level or above. The College of Policing's CVF expects candidates to demonstrate self-awareness, learning orientation, and commitment to improvement. A genuine Reflection answers three questions: what did I learn about myself or my practice? How did this change my approach? What do I now do differently as a result? It should be specific, not generic — 'I learned teamwork is important' scores nothing.
Weak
"I learned a lot from this experience and I would definitely handle it the same way again."
Strong
"What I took from this was that I had been too willing to accept initial reports at face value. I now routinely challenge partner agencies' opening accounts, and I have built a 'challenge question' prompt into my student officers' initial enquiry briefings."
Common mistake
Treating Reflection as a closing pleasantry. It should contain genuine insight into your development. If you cannot say what specifically changed in your practice as a result of this experience, your Reflection is not finished.
Section 4 — Rank calibration: what good looks like at each level
Panels use rank-calibrated rubrics. An answer that would score green at Sergeant level may score amber or red at Inspector level — not because the example is weak, but because it demonstrates the wrong level of thinking. Understanding what each rank expects is as important as knowing the STARR structure itself.
PC to Sergeant
Shift from individual execution to first-line supervision
Taking direct accountability for your team's output, not just your own
Making decisions that balance operational demands against individual welfare
Developing constables through coaching and feedback, not just directing them
Managing risk within your team and shift — not escalating everything upwards
Enforcing standards consistently and fairly, including with officers you like
Watch out: If your answer is entirely about your own actions with no supervisory dimension — no developing others, no managing team risk, no accountability for others' performance — you are answering at constable level.
Sergeant to Inspector
Shift from supervising individuals to leading multiple teams
Managing competing demands across several sergeants and their teams
Taking ownership of problems that sit outside your direct line management
Thinking about force-level implications, not just shift-level outcomes
Building systems and processes that scale, not just solving individual problems
Developing your sergeants to develop their own teams — developing the developers
Watch out: If your answer describes excellent people management with no strategic or organisational dimension — no systems thinking, no cross-departmental collaboration, no force-level impact — you are answering at sergeant level.
Inspector to Chief Inspector
Shift from tactical leadership to organisational change and command
Driving force-wide improvements, not just departmental ones
Managing significant operational commands with reputational and legal risk
Influencing and persuading at senior leadership level
Building capability and resilience across multiple functions
Owning accountability for complex, long-horizon outcomes
Watch out: If your answer lacks organisational scope and senior stakeholder management, you are demonstrating inspector capability, not Chief Inspector.
Section 5 — Building your evidence bank
Walking into a promotion board without a prepared evidence bank is like sitting an exam without revising. You need eight to ten strong examples, mapped to the CVF competencies, tested out loud, and ready to be adapted to the question asked.
1. Map to the CVF
Write one example for each of the six CVF competencies at Level 2. For your target rank, read the Level 2 descriptor carefully. Your example must demonstrate the specific behaviours listed — not the Level 1 behaviours you are already comfortable with.
2. Write them out in full
Do not rely on mental notes. Write each example as a complete STARR answer in longhand. The act of writing forces clarity and surfaces gaps. If you cannot write it, you cannot say it under pressure.
3. Test the flex
A strong example should be able to evidence more than one competency. After writing an example for 'We Take Ownership', ask: does this also demonstrate 'We Analyse Critically'? 'We Collaborate'? Panels may ask the same question with a different competency framing — your example needs to flex without breaking.
4. Say them out loud
Reading silently is not the same skill as speaking under pressure. Record yourself on your phone. Listen back. Notice where you slip into 'we', where you rush, where you lose specificity. Three rounds of spoken practice reveals more than ten rounds of silent reading.
5. Stress-test with probe questions
For each example, ask yourself: what would the panel probe? Prepare answers for 'why did you do it that way?', 'what would you do differently?', and 'what happened after?' If those answers are not ready, your example is not ready.
One strong example, properly prepared, can answer three or four different questions. One weak example, delivered confidently, will not fool a trained panel.
Section 6 — Worked example: PC to Sergeant
Sergeant Level — We Take Ownership (CVF Level 2) — ~450 words — 3 to 4 minutes
Question:"Tell me about a time when you took ownership of a high-risk situation. What did you do and what was the outcome?"
Situation
About eighteen months ago, I was acting Sergeant on a late shift when we received a high-priority missing person report. A fourteen-year-old girl with significant mental health vulnerabilities and a recent history of self-harm had left a local care home following an altercation with staff. She had not been seen for over two hours, it was approaching dusk in November, and I had only four response officers available, including two still in tutorship.
Task
As acting Sergeant, I was personally responsible for coordinating the response and owning the risk assessment. That included deployment decisions, the critical incident threshold decision, managing a concurrent high-risk domestic, and keeping the care home briefed. This was mine to lead, not to escalate and wait.
Action
My first decision was to formally grade it as a critical incident. The vulnerability profile and environmental factors were clear. Waiting for further developments would have been a failure of my responsibility. I briefed the team concisely, paired the student officers with an experienced colleague for a localised search, and took the intelligence strand personally.
I rang the care home manager directly and challenged the initial account, which felt thin. By probing, I discovered she had a history of visiting a friend in a neighbouring force, detail entirely missing from the initial report. Rather than wait for the Duty Inspector, I took ownership of the cross-border communication myself: I contacted the neighbouring force duty Inspector, explained the risk profile, and secured their agreement to deploy a unit immediately.
When the separate Grade 1 domestic call escalated, I did not distract the search team. I triaged it personally by contacting the victim to assess immediate safety, managing the delay until a unit was free. Throughout, I gave the care home a thirty-minute update cycle to prevent their calls overwhelming control.
Result
The girl was located safe at her friend's address ninety minutes after the report. The DI subsequently commended the early escalation decision. I recognised the care home's intelligence handover as a systemic gap and met their management the following week. We developed a vulnerability flagging protocol that is now standard in three subsequent missing person responses.
Reflection
What I took from this was that I had previously been too ready to accept initial reports without challenge. The detail that found her was available from the start. I had to push for it. I now routinely teach my student officers to treat the opening account as a first draft, not a final briefing. Professionally challenging partner agencies is a skill I have since made explicit in my development conversations.
~450 words. Situation 12% / Task 10% / Action 52% / Result 16% / Reflection 10%. Note: no use of 'we' in Action; every decision is owned in first person; Reflection identifies a specific change in practice, not a generic lesson.
Section 7 — Worked example: Sergeant to Inspector
Inspector Level — We Take Ownership (CVF Level 2) — ~580 words — 4 to 5 minutes
Question:"Tell me about a time when you took ownership of a difficult organisational problem. What did you do, what was the outcome, and what did you learn?"
Note the shift in scope: "organisational problem" signals the panel wants Inspector-level thinking — cross-departmental complexity, force-level risk, systemic solution.
Situation
Shortly after my promotion to Inspector, I identified a significant risk in how the volume crime team was handling digital media evidence. CCTV and mobile device material was being seized but not processed within our disclosure timescales. The backlog had reached approximately eighty unprocessed items, some over six months old, and cases were actively collapsing at court. The legal exposure under CPIA was serious, victim satisfaction scores in our BCU were falling, and no one had taken ownership of resolving it.
Task
Digital forensics sat within a centralised force function, outside my direct line management. I was not formally responsible for resolving this. I chose to own it anyway, because the failure of that process was preventing my team from delivering justice for victims. My specific accountability was to identify the root cause, build a business case for change, influence the relevant DI and senior stakeholders, and implement a solution that would hold.
Action
I started with data. Over two weeks I personally audited the backlog, categorising items by age and case impact. I identified three specific cases where violent defendants had avoided prosecution solely because of our disclosure failure. I produced a one-page summary that turned an anecdotal complaint into an undeniable business case. Data wins arguments that opinions do not.
I then met the DI responsible for digital forensics. I was deliberate about my approach: I framed the backlog as a shared organisational risk, not a performance failure on their part. That framing mattered. Accusatory conversations create defensiveness; collaborative ones create solutions. I proposed a triage protocol under which my team would take on a first-pass review of lower-risk digital media, developed jointly with the forensics unit to preserve evidential integrity.
I managed resistance from the forensics team by arranging a targeted masterclass for my officers, building confidence on both sides. I identified four Digital Champions within my team, personally oversaw their training, and created a weekly performance dashboard tracking the backlog that went directly to the Detective Superintendent. That accountability loop made the improvement visible and protected the change from being quietly de-prioritised.
Result
Within ten weeks the backlog was below twenty items. Processing time for new submissions dropped from six months to six weeks. The Detective Superintendent cited this work explicitly in the quarterly performance review. No further cases in my department collapsed for disclosure reasons in the following twelve months. The triage protocol has since been adopted as a pilot across two other districts.
Reflection
Two things. First, data wins arguments that opinions do not. I would not have secured buy-in without the one-page summary. Second, and more importantly, ownership at Inspector level is not the same as ownership at Sergeant level. It is not about being formally responsible. It is about deciding to own a problem because it affects your team's ability to do their job, even when you could legitimately leave it to someone else. That distinction is now something I actively develop in my Sergeants.
~580 words. Note the inspector-level markers: cross-departmental problem, force-level risk, systemic solution, senior stakeholder management, developing others. The Reflection contains two specific insights, not one generic lesson.
The problem usually isn't your examples. It's the rank they're calibrated to. This guide shows you the difference, mapped to the STARR sections you already use.
✓Five traps, one per STARR section — Situation, Task, Action, Result, Reflection
✓Sergeant vs inspector answers side by side, so you can see exactly where the mark is lost
✓A fill-in worksheet to draft your own answer, scored against We Take Ownership
Landscape PDF. Free. No login required.
No spam. One email with your download link. Unsubscribe any time.
Section 8 — Handling probe questions
Modern promotion panels will almost always follow your STARR answer with probe questions. These are not designed to trip you up. They are designed to verify your example is genuinely yours, test the depth of your thinking, and give you the opportunity to demonstrate competency the panel may not have seen clearly in your initial answer. Candidates who prepare for probes consistently outperform those who prepare only their opening answer.
Detail probes
"What exactly did you say to the officer?" / "Walk me through your decision step by step."
Stay concrete. If you genuinely cannot recall the exact words, say so — but describe the intent and tone clearly. Panels probe detail to verify the example is real and genuinely yours.
Consequence probes
"What happened as a result of that?" / "How did the team respond?"
Use the opportunity to strengthen your Result. If your initial answer was light on outcomes, a consequence probe is your chance to add the impact you glossed over.
Reasoning probes
"Why did you choose that approach?" / "What did you consider and reject?"
This is rank calibration in real time. The panel wants to see the quality of your decision-making, not just the decision. Explain your reasoning explicitly: what you weighed, what risks you considered, what alternatives you discounted and why.
Self-awareness probes
"What would you do differently?" / "What was the hardest part for you personally?"
Do not be defensive. These are not trick questions. Panels actively reward candidates who can acknowledge difficulty, error, or limitation with honesty. The strongest answers to self-awareness probes say something specific, not generic.
Depth and scope probes
"How many people were affected?" / "Did this have any force-level implications?"
If you are going for Inspector, the panel may probe to check whether you can think beyond your immediate team. Have your answer ready for the wider context, even if you did not lead at that level.
If you are genuinely unsure
'Let me think about that for a moment' is a confident response. 'I cannot recall exactly, but what I do know is' is better than an invented detail. Panels probe to verify personal ownership, not to catch you out on facts. Honesty about what you do not remember is far better than fabrication, which collapses immediately under a follow-up.
Section 9 — Common failure modes
The 'we' trap
The most common reason strong candidates score amber instead of green. 'We decided', 'the team did', 'we all agreed' — none of these tell the panel what you, personally, contributed. Replace every instance of 'we' with a specific I-statement. If a decision was genuinely shared, own your part of it explicitly.
Skipping or rushing the Result
Candidates run out of time and drop the Result to a single sentence. If this happens in practice, your proportions are wrong — too much time is going on Situation. Practise with a stopwatch and cut your scene-setting until the Result has room to breathe.
A cosmetic Reflection
'I learned a lot' or 'I would do the same again' scores nothing. Reflection must answer: what specifically changed in your practice? At Inspector level and above, a weak Reflection is a significant scoring liability. Build it first — then work backwards to the rest of the answer.
Wrong rank voice
Constable-level thinking in a Sergeant answer. Sergeant-level thinking in an Inspector answer. Panels assess against rank-specific descriptors. If your answer is entirely about your own actions and outcomes with no reference to supervising others, developing people, or managing risk at a team level, you are almost certainly answering at the rank below. Read the CVF Level 2 descriptors before your board.
Vague outcomes
'Things improved' does not score. 'Sickness absence fell from twelve to eight percent over three months, and the exit interview data showed a measurable improvement in team satisfaction' does. Quantify wherever you honestly can. If you have no numbers, use observable behaviour: 'The officer in question voluntarily requested the development course', 'Three team members referenced the change in their appraisals.'
Over-rehearsed delivery
Memorised answers collapse under probe questions. Panels know within sixty seconds whether a candidate is recalling a script or speaking from experience. Prepare your examples thoroughly, but practise speaking them from bullet points — not word-for-word. The answer should feel recalled, not recited.
Borrowing other people's examples
Panels probe specifically to verify personal accountability. 'I was involved in that' is not the same as 'I made that decision'. If you use a team example, be rigorous about what your individual contribution was. Borrowed examples without genuine personal ownership fall apart under one or two probe questions.
Missing the CVF connection
Your answer must demonstrate the competency being assessed, not just tell an interesting story. Before you practise, identify which CVF competency the question targets and which Level 2 descriptor your answer evidences. If you cannot make that connection explicitly, the panel will have to infer it — and they may not infer correctly.
Section 10 — Timing and proportions
Sergeant target: 350 to 500 words (3 to 4 minutes). Inspector target: 450 to 600 words (4 to 5 minutes).
Situation
10 to 15%
Brief scene-setting. If you are over sixty seconds, cut it.
Task
10 to 15%
Your specific accountability. One or two sentences.
Action
45 to 55%
The scoring section. Every sentence should evidence a decision or behaviour.
Result
15%
Outcome and impact. Quantify where you can. Never skip this.
Reflection
10 to 15%
Specific change in practice. Build this first — if it is weak, the whole answer is weaker.
5 minutes feels long until you practise it out loud. The most common failure mode is rushing. Slow down. Pause between sections. A confident pause is a marker of rank, not hesitation.
Section 11 — STARR or PEEL? A decision rule
Use STARR when the question contains...
"Tell me about a time when..."
"Give me an example of..."
"Describe a situation where you..."
"When have you..."
Use PEEL when the question contains...
"How would you handle..."
"What would you do if..."
"What is your view on..."
"How should the police approach..."
If a question is ambiguous, default to PEEL for Inspector and above. You can always anchor a PEEL answer with a specific past example in your Evidence section — that strengthens it rather than contradicting the structure.
Section 12 — Ready to practise?
The STARR Builder lives inside State6. It lets you structure an answer, then read it back out loud with a timer. Notice where you slip into 'we', where you rush past the Result, where the Reflection is generic. Three rounds of spoken, timed practice will do more for your board performance than any amount of silent reading.
STARR is a skill, not a script. The structure becomes second nature through repetition. The goal is not to sound like you are using a framework — it is to sound like a confident, self-aware leader who happens to be very good at telling their own story.