Police CVF examples,worked board answers for every competency.

Situation

I was the response inspector. A dip sample I ran across my teams showed that on one team, roughly a third of domestic incidents over two months had safeguarding referrals that were either late or missing, including two where children were in the house. They weren't cutting corners deliberately, the referral was just falling off the end of a busy job.

Task

The easy route was to make it the sergeant's problem and move on. But the standard on my command was mine, and I hadn't made the expectation clear or checked it, so the gap was as much mine as anyone's. I decided to own it rather than escalate it or push it down.

Action

I didn't open with blame. I sat with the sergeant and was straight that the system around his officers had let this happen, and that fixing it was on me to do with him rather than something I was dropping on his desk. Before I changed anything I read the referrals in full rather than trusting the dip sample, because I wanted to know whether this was capability or load. It was load. The thin ones clustered on the busiest officers at the busiest hours, which told me it was a process problem, not a competence one. We worked out together that the referral was being left until the officer got back to the station, by which point three more jobs had stacked up and the detail had gone cold. So we moved the point at which it happened, building it into the close of the incident on the street while the account was fresh. I put a simple check in where the sergeant reviewed every domestic referral within the shift rather than relying on a monthly sample, and I retro referred the two child cases that same day rather than let them sit. I was open with my superintendent straight away, including the two involving children, rather than waiting to present it once it was tidy, because owning it meant owning it before it was fixed, not after. I tracked it myself weekly for two months and fed each officer their own figures so the standard was visibly held.

Result

Late or missing referrals on that team went from around a third to under five per cent and held there. More than the number, the sergeant started bringing me near misses early, because he'd seen me own one rather than hunt for someone to carry it. I fed the change to the other response teams before they hit the same wall.

Reflection

What I took from it was a rule I now apply. If something's gone wrong in my area, the first question is what I set up, or failed to set up, that allowed it, before I look at anyone below me. Owning it that way is also what made people honest with me.

Situation

Illegal car cruising on a retail park on my area was generating around forty calls a month, a genuine danger to the public who walked through it, and a steady stream of complaints we couldn't arrest our way out of. The meets were organised on social media and moved the moment we turned up.

Task

My own resources couldn't fix this on their own, and chasing it on a Friday night just displaced it to the next car park. The only durable answer ran through people I had no power over, so I needed to build a partnership that didn't yet exist rather than wait for one to be convened for me.

Action

I didn't start with a meeting and a list of demands. I went to see each partner first and worked out what the problem cost them in their own terms. The council cared about the antisocial behaviour figures and had a Public Spaces Protection Order power going spare. The retail park's managing agent was worried about footfall and liability, not policing. A motorsport venue twenty minutes away wanted custom on quiet weeknights. Once I understood that, I could shape something where each of them got a win they cared about rather than a favour to me. I proposed the protection order so the council got enforcement that counted for them, and I got the managing agent to fund better lighting and barriers by framing it around footfall and liability rather than crime. Rather than fight the social media side, I set up a cheap legal track night at the venue and had a youth worker and one of my PCSOs seed it through the same pages the meets were advertised on, so the alternative actually reached the drivers. When the council and the agent fell out over who paid for the barriers, I kept it moving by separating their contributions so neither felt they were carrying the other. And I did the unglamorous part myself, chairing a short fortnightly call and chasing the actions in between, because a partnership dies in the gaps between meetings rather than in them.

Result

Over the following quarter, calls from the retail park dropped from around forty a month to single figures, and they didn't simply move elsewhere, because the track night gave the genuine enthusiasts somewhere to go. The council later used the same approach on a second site. None of it would have held on enforcement alone.

Reflection

What stayed with me was that I'd gone in thinking I needed their help with my problem. The partnership only worked once I'd flipped it and made it their problem too, with something in it for each of them. That's how I come at partnership now, common interest first and my ask second.

Situation

A capable constable on my team kept letting victim updates slip until I chased him near the twenty eight day point. He wasn't lazy, far from it. His arrest and case file work was some of the best on the team, which is exactly what made the gap stand out and what made it worth getting right rather than just enforced.

Task

The easy version was to performance manage the deadline and move on. But I wanted to understand why a genuinely good officer kept dropping this one thing, because if I just set him a target I knew I'd be back here in a month having the same conversation.

Action

I asked him about it properly rather than telling him off. It turned out he saw victim updates as an administrative box, separate from the real police work, the arrests and the files. That was the actual problem, not his diary. So I didn't lead with the policy. I picked one of his own jobs, a burglary where the victim was an elderly woman living alone, and asked him what he thought she'd been doing in the three weeks she hadn't heard anything. We talked about what the silence felt like from her side. Then I made it concrete and gave him something to own. I asked him to ring two of his victims that week with no script and just tell me what came back. One of them told him she'd assumed we'd dropped the case and had stopped sleeping properly. That landed far harder than any deadline I could have set. I was still clear the standard wasn't optional, the updates had to happen, but I tied it to the person it protected rather than to the twenty eight day clock. I checked in weekly after that, not on his compliance figure but on what his victims were telling him, and when he started getting it right I told him specifically what good had looked like rather than just noting the figure had gone green, because I wanted him to know it was the quality of the contact I'd clocked, not the box.

Result

His updates stopped being late because they'd stopped being admin to him. Three months on he volunteered to write a short input for the team tutor on keeping victims in the picture, which I hadn't asked him to do. The wider point was that I'd grown the officer, not just closed the gap.

Reflection

What I took from it was that holding someone to account and developing them aren't separate things. If I'd only enforced the standard I'd have got compliance and missed the chance to change how he saw the work. That's the difference I look for now before I reach for a target.

Situation

As the chief inspector leading safeguarding I owned our response to rape and serious sexual offences, where our positive outcome rate was sitting at around three per cent. The accepted view internally was that the investigations were under strength and the teams needed performance managing.

Task

I had to decide where to put a finite improvement effort across the command. The easy and popular move was to accept that narrative and drive the investigators harder. It didn't sit right with me, and at this level the cost of acting on the wrong cause is paid by victims, so I needed to test it properly before I committed anyone.

Action

I went back to the data with sharper questions rather than accepting the headline. I asked when in the process we were losing cases, not just how many. When we mapped attrition against time, the picture changed. We weren't mainly losing cases at charge through weak files. We were losing them in the first seventy two hours, through early evidence that was never captured and first contact that left victims feeling disbelieved, so they disengaged before an investigator ever built a file. Before I took that anywhere I tested the obvious alternative, that it really was investigator quality, by pulling cases the strongest investigators had also lost, and they were dropping out at the same early stage, which killed the performance management theory. I used the national Operation Soteria findings and our own HMICFRS feedback to pressure test it too, because I didn't want a conclusion drawn only from data my own teams had produced. The uncomfortable part was that the real problem sat upstream with first response and initial contact, not with the specialist investigators being blamed. When I took it to a senior team that had publicly backed the performance line, I didn't lead with the fact they'd got it wrong. I led with the attrition curve and let them reach the upstream conclusion themselves, because a diagnosis they arrived at would hold where one I imposed wouldn't.

Result

We shifted the effort upstream, into early evidence capture and how first responders handled the initial contact, and into specialist input on day one rather than week three. Over the following year the positive outcome rate roughly doubled off that low base, and early victim disengagement fell. More than the number, the conversation across the command stopped being about blaming investigators.

Reflection

What I took from it was that being evidence led isn't accepting the first thing the evidence appears to say. The discipline is asking what question the number is actually answering. The three per cent was real, but it was measuring the end of a problem that started long before the investigators ever got the case.

Situation

On my response team, the domestic abuse risk assessments were completed back at the station at the end of the job, often several hours later. I was concerned the delay was costing us detail, and worse, that we were under grading genuine risk, because the form was being filled in from memory once the adrenaline had gone and three other jobs were waiting.

Task

I thought there was a better way, doing the assessment at the scene while it was fresh, but it was a routine the team trusted and several of the experienced officers were openly sceptical. I needed to test the idea honestly rather than sell it, because I genuinely didn't know whether it would survive a busy shift.

Action

I deliberately looked outside policing first. I spent time with an emergency department charge nurse on how they triage risk at the point of contact rather than later, and borrowed the principle that the assessment belongs at the moment of contact, not the end of the process. Then I was clear with the team that I had a hypothesis, not a decision, and that if the evidence went against me I'd drop it. I asked the two most sceptical officers to help design the trial, partly to stress test it and partly because their backing would carry the others. We agreed up front what we'd measure, the quality of risk grading on supervisory review and the time from incident to completion, and we ran it for four weeks against a comparison shift. One of the sceptics raised a real objection I hadn't seen, that completing it at scene in front of a frightened victim could feel like an interrogation, so we built a judgement call in for those cases rather than pretend the problem didn't exist. I kept the trial deliberately small and reversible, one team for four weeks, so that if it failed we lost nothing and nobody could say I'd bet the shift on a hunch. I squared the mobile device access with our information manager before we started, because I didn't want a data protection objection to sink a good idea halfway through, and I briefed the control room so they understood why those officers might be on scene a little longer.

Result

The data surprised me. The time saving I'd expected was modest. What moved sharply was the quality of the grading and the number of safeguarding referrals that followed, because officers were capturing at the door what they'd lost by the time they reached the station. We took it on across the team, two neighbouring teams picked it up, and the original sceptics were the ones who sold it to them.

Reflection

The part that stayed with me was that I'd set out to save time and the real prize turned out to be somewhere I wasn't looking. If I'd mandated it on day one I'd have got compliance and never learned that. Staying open wasn't a soft skill here, it's what made the change worth keeping.

Situation

I was a fairly new sergeant on a long established team. One of the most experienced and well liked PCs made comments about one local community that had drifted from cynicism into something I'd call discriminatory. It was treated as harmless, people laughed along, and I'd started to hear two of the probationers repeat the same lines on the radio.

Task

I had to deal with it. The difficulty was real. He was popular, he'd been in the job longer than me, and challenging him would mark me out with a team I was still earning trust from. Doing nothing would have been easier and I knew it.

Action

I chose to deal with it in a way that might actually change it rather than just be seen to react. I thought about going straight to professional standards, but that would have been the easy route for me and the wrong one for the team, so I dealt with it myself in the open and kept a note of what I'd said and when, in case it didn't land and I had to escalate later. I spoke to him on his own first and was direct. I told him plainly the comments weren't acceptable, that I could hear newer officers echoing them, and that I wasn't prepared to have it on my team. He pushed back, said it was banter and I was taking it too seriously. I didn't get drawn into whether he meant any harm, because that wasn't the point. I stayed on the effect it was having and the standard I expected. When it surfaced again a week later in the writing room, I addressed it there and then, calmly, in front of the others, so the team saw the standard was real and applied to him as much as anyone. I wasn't out to humiliate him, the aim was a changed standard and not a scalp, so I was firm and then moved on. I also had a quieter word with the two probationers about the language they'd picked up.

Result

The comments stopped. It cost me some warmth from him for a few weeks, which I'd expected and accepted. What I hadn't expected was that one of the probationers came to me afterwards and said she'd been uncomfortable for months and hadn't felt able to say so. The tone on the team shifted, and not only on this.

Reflection

The honest cost was to a working relationship I needed, and I'd still do it the same way. What I learned was narrower than I expected. It wasn't really about that one officer, it was about the probationers watching what I let go. Silence from a supervisor isn't neutral, it reads as permission, and I set the standard by what I'm willing to stand in front of.

Situation

One community on my command, largely from minority ethnic backgrounds, had confidence scores in our surveys well below the force average, with a long history behind it that included how stop and search had been used there. My teams were doing more activity in the area and getting less trust for it.

Task

I could have treated this as a visibility and messaging problem, which was the comfortable option. I was clear with myself that if I went in to defend our record I'd make it worse. The job was to genuinely understand the experience from their side and let that change what we did, not to reassure them about what we already did.

Action

I went to the community sessions personally, and I went to listen rather than to account for our performance. I was honest that this wasn't always comfortable, because some of what I heard was fair criticism of decisions my own command had made. I also went after the data rather than relying on the loudest voices in a room, looking at our complaints, our stop and search disproportionality and who we were and weren't hearing from, so I understood the pattern and not just the anecdotes. What I heard reshaped our tasking. I resisted the easy fix of a one off engagement event, because those buy a good photograph and change nothing. Instead I made a community scrutiny panel a standing fixture with real access to our data, I had body worn footage from a sample of stops reviewed with community members in the room, and I changed how and where we used the power off the back of what that surfaced. I made sure we reported back on what had actually changed and not just on what we'd heard, because accountability runs both ways. When one of my inspectors pushed back that this was second guessing his officers, I held the line and reframed it as the thing that protected them, because a stop that survives that kind of scrutiny is one no complaint can touch.

Result

Over about a year, confidence in that community rose for the first time in three years of surveys, and our disproportionality narrowed without losing the legitimate searches. The scrutiny panel became a permanent part of how the command worked rather than a one off. The change that mattered most was that my inspectors started treating community confidence as part of the job, not a soft add on.

Reflection

What I took from it was that respect at this level isn't how I treat the person in front of me, it's whether I'll let what a community tells me change decisions I'm responsible for. Listening that doesn't change anything is just a better managed complaint.

Situation

My command was under pressure on one headline figure, our sanction detection rate, which sat on the chief officer scorecard and which my own boss had publicly committed to lifting. The quickest way to move it was to push my teams towards the easy to detect, low harm offences that close quickly and count the same as anything else.

Task

The easy and more popular option was to chase the number, because it would have made my command look better in exactly the place it was being judged. But it would have pulled effort away from the high harm work that mattered most to the public and didn't move that particular metric. I had to decide which I was really there to serve.

Action

I didn't do it on rhetoric, because at that level it would have been picked apart. I had the analysts model exactly where the easy detections would come from, and it confirmed the worry, the quickest route to the target ran straight through shoplifting recoveries and cannabis warnings that close fast and count the same as a rape or a robbery. I built the case around harm rather than volume, showing what chasing the number would cost in capacity for the domestic abuse and vulnerable victim work that actually mattered to the public. I also did the honest thing and modelled what holding the line would do to my own figures, so nobody could say I hadn't seen the cost coming. I took it to my superintendent knowing it wasn't what he wanted to hear, and I was straight that I wasn't willing to buy a scorecard number at the expense of victims who'd never see that scorecard. I proposed we measure the command on something closer to public harm rather than raw detections, and I accepted my headline figure would sit below my peers' for a while. I said the same thing plainly to my own inspectors, because I wasn't going to ask them to hold a line I wouldn't defend upward myself.

Result

We held the resource on the high harm work. For two quarters my detection rate sat below the others and I had to own that in uncomfortable rooms. Over the year our outcomes for domestic abuse and repeat vulnerable victims improved materially, and the force eventually shifted to a harm based measure closer to what I'd argued for.

Reflection

What I took from it was that public service is easy to claim when it also flatters your figures. The test is whether you'll hold to it when doing the right thing makes you, for a while, look worse than the person next to you. That's the version that actually counts.