Most officers going for sergeant know We Support and Inspire is about leading people. They know the language — developing capability, bringing out the best in your team, creating the right environment.
What most officers don't know is that the panel isn't just watching how you manage down. The competency applies at every level — how you support a colleague who's struggling, how you help someone less experienced grow, how you contribute to the people around you operating at their best. It doesn't require a line management relationship. It requires genuine investment in another person.
This post takes one question, shows a weak answer and why it fails, then a strong answer and what changed. The scenario is sergeant level. The final section covers how the expectation shifts at inspector and chief inspector.
The Question
"Tell me about a time when you recognised that a member of your team wasn't reaching their potential. What did you do and what did you learn from it?"
Every sergeant candidate has a version of this story. The difference in score isn't the story. It's how they tell it.
The Weak Answer
"We had a young PC who'd been quite enthusiastic when they first joined the team but seemed to have lost some of that over the previous few months. The sergeant before me had flagged it in handover. We had a chat one to one and I told them I'd noticed the change and wanted to help. We talked about their development and I set them a few targets. Things did pick up after that. I suppose what I took from it is that you need to keep an eye on your team and not wait for problems to escalate."
That answer describes a supervisor who followed the process. It doesn't describe a leader who understood the person. Here's what the panel can't score from it:
It's reactive, not proactive. The officer found out from the previous sergeant, not themselves. A panel is looking for officers who notice what's happening in their team before someone else raises it.
"We" throughout. "We had a chat", "we talked", "we agreed targets" — collective language hides the individual contribution the panel is trying to assess.
No curiosity before action. The officer moved straight to setting targets without any indication they tried to understand what was actually driving the change. That's a supervision process, not a leadership decision.
The reflection is generic. "Keep an eye on your team" is something every officer knows before their first shift as a sergeant. It reveals nothing about what this experience taught this person.
The answer isn't wrong. It just won't score.
The Strong Answer
The extract below is condensed for illustration. A full board answer at sergeant level would typically run around five to six minutes. What matters here is the approach, the recognition and the quality of reflection. Not the length.
"I'd noticed over about three weeks that a PC on my team who'd previously been one of the more proactive officers had started hanging back. They were doing what was asked but not looking for work the way they had been. Nobody had flagged it to me. I picked it up myself.
Before I spoke to them I thought about what I actually knew about them as a person. I knew they'd been passed over for a secondment they'd applied for earlier in the year. I didn't know if that was connected but I wanted to find out before I assumed anything.
I asked how they were finding the role at the moment and whether there was anything they felt was getting in the way. They told me they'd started to question whether they had what it took to progress. The secondment knockback had hit them harder than they'd let on at the time.
I was honest with them about something. The shift needed them operating at their best — not because their numbers were down but because what they brought to the team had a genuine impact on how we worked as a unit. I wanted them to understand that. But I also recognised that telling someone they're needed isn't enough when their confidence has taken a hit.
Over the following month I worked with them differently. I brought them into briefings in a way I hadn't before. I gave them ownership of a task that had a visible outcome for the team and made sure the result was recognised when it landed. Three months later they put in for their sergeant's exam.
What I took from it was something I hadn't expected. I realised I'd been leading the team as a unit and had stopped seeing the individuals inside it. That was a genuine gap in how I'd been operating and it changed how I work now."
What Changed
Same scenario. Completely different score. Here's what the strong answer did that the weak one didn't:
It showed proactive recognition. The officer noticed the change themselves. They didn't wait for a handover note or a formal flag. Panels are watching for that — a leader who sees what's happening around them before being told.
It showed curiosity before judgement. Thinking about what they knew about the person before deciding how to approach the conversation is a meaningful distinction. The weak answer went straight to setting targets. The strong answer tried to understand first.
It connected the individual to something bigger. The officer told the PC directly that the team needed them and explained why. That's not a pep talk. It's an officer helping someone understand that their contribution has a real impact beyond their own performance numbers. The panel can see that.
The reflection identified a genuine blind spot. Recognising you'd been leading a team as a unit and missing the individuals inside it is a specific, personal observation. It's uncomfortable to say in a board room, which is exactly why it lands.
Notice also that the strong answer uses "I" throughout. Not "we had a conversation" or "we agreed an approach." Collective language hides the very thing the panel is scoring.
How This Shifts at Different Ranks
At inspector level the panel expects your investment in people to operate beyond your direct span of control. A single officer's development story is a sergeant answer. An inspector needs to show how they influenced their sergeants to lead differently, or how they created the conditions for a whole team to grow. The detail moves from one conversation to an environment.
At chief inspector level the panel wants to see people development as something that shapes the capability of the organisation. Not one officer's progression but how your approach to developing people had a measurable impact on the function you led.
The bones of a strong answer are the same at every rank — genuine curiosity, honest recognition, specific reflection. What changes is the scale at which it operated.
The Thing Most Officers Miss
We Support and Inspire is often answered as if it's a performance management question. It isn't. The College of Policing CVF at level 2 is asking whether you understood what someone needed and adapted because of that understanding. A PDR review and a target conversation are the baseline expectation of any supervisor. What this competency scores is what you noticed, what you asked and what changed because of it.
The officer who ran a competent supervision process scores lower than the officer who read the person, not just the problem.
If you want to know how your own We Support and Inspire answer would score, State6's AI board review gives you specific feedback against the CVF descriptors at your rank. Not generic advice but a breakdown of exactly where your answer is losing marks and why. Build the full structure using the STARR guide and use the CVF 2024 explained post to check what the panel is specifically scoring at your level.
For a complete overview of the promotion process — how the NPPF works, what the CVF requires at each rank and how to structure every question type — see the complete guide to UK police promotion boards.