Learn STANCE: The Presentation Framework for Promotion Boards
Why most officers present at the wrong level, and how a six-step structure changes what the panel hears.
Section 1 — The structure problem nobody talks about
Most officers preparing for a promotion board presentation spend their time on content. What data to reference. How much to rehearse the words. Very few spend time on structure. And that's the gap the panel sees.
Strong officers fall short not because they lack experience, but because the structure of what they say doesn't let the panel see it. Walk into any leadership programme and one of the first principles you encounter is BLUF: Bottom Line Up Front. It originated in the US Army and spread to every professional environment where clarity under pressure matters. State your recommendation before you build the case for it. Give the listener the destination before the journey.
The Pyramid Principle, developed by McKinsey consultant Barbara Minto, formalised the same idea. Lead with your conclusion. Support it with arguments. Support each argument with evidence. Structure flows from the top down, not from the ground up. Most officers do the opposite. They build the case first and arrive at the conclusion at the end. By the time they get there, the panel is already forming a view about whether the answer ever had a direction.
The primacy-recency effect compounds this. Memory holds the first things and the last things most clearly. The middle is where it fades. A presentation that buries its conclusion after three minutes of context is handing the panel its weakest material at exactly the moments when memory is strongest.
Most presentations fail for the same structural reasons before content becomes relevant. Part 1 of our presentations series covers the habits that cost marks before an officer reaches the substance.
Section 2 — What STANCE stands for
Six steps. Each doing a specific job. Built on the same principles that underpin structured communication in every high-stakes professional environment.
S
Situation
State the problem. Not the full context, not the history, not the background reading. The specific, named problem your presentation addresses. Two sentences at most.
T
Take a position
Your recommendation, stated in the second step. Not built to. Not arrived at. Stated. If you can't state a clear recommendation here you haven't finished thinking yet.
A
Assessment
Your evidence. This is the analysis that supports the position you've already taken, not analysis that leads to it. Named sources, specific data, force context, inspection findings.
N
Navigate the options
The alternatives you considered and discarded, and why. Find the strongest counter-argument. Engage with it honestly. Then explain why your recommendation still holds.
C
Cost and risk
What this takes. Resourcing, dependencies, risks and mitigations. Panels aren't just assessing whether your recommendation is right. They're assessing whether you understand what it costs to deliver it.
E
End with impact
One sentence. The outcome you're committing to and how you'll know it's working. Not a summary. A close that tells the panel what success looks like and that you own it.
Section 3 — Each section in detail
S
Situation
60–80 words · State the problem. Two sentences at most.
The panel doesn't need the journey. They need to know what the journey is about. Your Situation is not background reading, not a history of the issue, not an explanation of why it matters. It is the specific, named problem your presentation addresses, with one or two pieces of hard evidence that prove it exists. If you find yourself explaining causes, context, or history in this section, you've already drifted into Assessment.
Weak
"Sickness absence has been an issue across the force for some time and there are a number of contributing factors that have been identified through various reviews and staff surveys over recent years."
Strong
"Sickness absence across the command unit has risen eighteen percent over the last twelve months, with the highest concentration in two response teams. The HMICFRS 2023 State of Policing report identified workforce fatigue as a systemic issue across the service."
Common mistake
Opening with context instead of the problem. The panel should know exactly what you're presenting about by the end of your second sentence. If you're still setting the scene at thirty seconds, you've lost the structure before you've started.
T
Take a position
60–80 words · State your recommendation before any evidence.
This is the Minto Pyramid Principle in practice. Lead with your conclusion. Let everything that follows be in support of it. Most officers present at length before telling the panel what they think. STANCE inverts that. If you cannot state a clear recommendation at this point, you haven't finished thinking yet. The panel should hear your decision in the second step, not after three minutes of evidence.
Weak
"Having looked at the data and spoken to supervisors, I think there are several things the force could consider in terms of addressing the sickness issue, including wellbeing support, supervisor training and potentially a referral pathway."
Strong
"My recommendation is a structured twelve-week supervisor-led wellbeing intervention, starting with the two highest-absence response teams, rather than a force-wide programme or a referral-only model."
Common mistake
Hedging the recommendation. 'I would consider', 'it might be worth looking at', 'one option could be' — these all signal to the panel that you haven't made a decision. State the recommendation as something already decided, then build the case for it.
A
Assessment
300–400 words · The evidence that proves your recommendation is right.
Assessment is the largest section and it has a specific discipline: you're building the case for a decision you've already stated, not conducting an open-ended review. Named sources, specific data, force context, inspection findings. The panel should hear an officer who knows the evidence landscape and has applied it to the specific problem they're presenting on. Vague references to 'various studies' or 'force data suggests' score poorly. Name the source. Name the finding. Connect it to your recommendation.
Weak
"The evidence shows that sickness absence is a problem in many forces and there are research findings that support supervisor-led approaches to wellbeing. The force data also indicates that there are issues in some teams."
Strong
"The HMICFRS 2023 State of Policing report identifies workforce fatigue as a systemic issue across policing. The National Police Health and Wellbeing Strategy 2024 to 2026 specifically identifies supervisor-led early intervention as the most effective approach to short-term absence. Our force performance data shows that the two teams with the highest absence rates have also had the highest supervisor-to-officer ratio change in the last eighteen months."
Common mistake
Treating Assessment as an opportunity to re-examine the question rather than build the case. If your evidence section makes the recommendation sound uncertain, you've undermined Take a Position rather than supported it.
N
Navigate the options
200–280 words · The alternatives you considered and discarded, and why.
This section does two things. It shows the panel you didn't arrive at your recommendation without thinking it through. And it anticipates the questions they'll ask, because experienced panels will probe exactly why you chose this option over the others. The discipline here is to take the strongest competing argument seriously. Don't present the weakest alternatives and dismiss them easily. Find the genuine counter-argument. Engage with it honestly. Then explain why your recommendation still holds.
Weak
"I considered just sending people to occupational health but I don't think that would work on its own. I also thought about a force-wide programme but that might be too expensive."
Strong
"The main alternative I considered was a structured referral pathway to occupational health. The reason I discarded it is that the force data shows officers in high-absence teams are the least likely to self-refer, and a referral model without earlier supervisory contact consistently underperforms in comparable forces. A force-wide programme was the other option. I rejected it because concentrating intervention on the two teams with the highest absence means the resource goes where the evidence says it's needed, rather than being diluted across the force before it has demonstrated impact."
Common mistake
Choosing weak alternatives that are obviously wrong. The panel will test whether you've genuinely engaged with the strongest competing option. A Navigate section that dismisses easy targets doesn't show strategic judgment.
C
Cost and Risk
250–300 words · What this takes. Resourcing, dependencies, risks and mitigations.
Panels aren't just assessing whether your recommendation is right. They're assessing whether you understand what it costs to deliver it. An answer with no Cost and Risk section sounds like an officer who hasn't led anything at scale. At sergeant level this is your team and the time it needs. At inspector level this is your command and the functions it draws on. At chief inspector level this is force-level resource and the wider environment. Name the real costs, name the real risks, and state a specific mitigation for each.
Weak
"This would require some supervisor time and there might be some resistance from staff initially. I would manage this through good communication."
Strong
"The resource cost is supervisor time: approximately four hours per week across the twelve-week intervention period, plus designation of a sergeant as the lead coordinator. The budget implication is minimal as this draws on existing capacity rather than additional headcount. The primary risk is that supervisors experience this as additional burden rather than as core leadership work. I'd manage that risk through how I brief it: the intervention is positioned as supervision, not a welfare programme. The second risk is inconsistent delivery across the two teams if the lead sergeant doesn't have sufficient oversight from me. I'd mitigate that through fortnightly review meetings at inspector tier."
Common mistake
Treating this section as a risk register without naming the strategic and inspection dimensions. At chief inspector level, the panel expects you to name what continued underperformance would mean for the force's relationship with the inspectorate and for public confidence. If your Cost and Risk reads like a logistics section, it won't score at that rank.
E
End with Impact
30–50 words · One sentence. The outcome you're committing to and how you'll know it's working.
The primacy-recency effect is as powerful at the close as it is at the opening. The last thing the panel hears is the thing they carry into scoring. End with Impact is not a summary of what you've said. It's a forward-looking commitment: a specific outcome, a measurable standard, and personal ownership. One sentence. If you find yourself summarising your earlier sections, you've written the wrong close.
Weak
"In conclusion, I think the approach I've outlined will make a real difference to the team and I'm committed to making it work."
Strong
"Sickness absence in the two affected teams will reduce by at least six percentage points within sixteen weeks, measured through monthly workforce reporting, and I will hold the lead sergeant accountable for delivery at our fortnightly governance meetings."
Common mistake
Summarising instead of committing. The panel has already heard your analysis. What they need at the close is a specific outcome, a timeframe, and the clear signal that you own delivery of it personally.
Section 4 — STANCE in practice: a worked example
Scenario: sickness absence across the command unit has risen eighteen percent over twelve months. You've been asked to present your approach as a new Chief Inspector.
Without STANCE
"Sickness has been an issue across the force for some time. There are various factors including workload, leadership and personal circumstances. I would look at the data, speak to sergeants, consider what support is available and put together a plan to address the most significant causes."
With STANCE
"The situation is an eighteen percent rise in sickness absence across the command unit over twelve months, concentrated in two response teams. My recommendation is a structured twelve-week supervisor-led wellbeing intervention, starting with those two teams, rather than a force-wide programme or a referral-only model. The evidence supports this: the HMICFRS State of Policing 2024 to 2025 identifies workforce fatigue as a systemic issue, and the National Police Health and Wellbeing Strategy 2024 to 2026 specifically points to supervisor-led early intervention as the most effective approach. The alternative I considered was a structured referral to occupational health. I discarded it because the data shows officers in high-absence teams are the least likely to self-refer, and a referral model without supervisory contact first consistently underperforms. The cost is supervisor time: four hours per week across the intervention period, plus coordination from a sergeant I'll designate as the lead. The risk is that supervisors feel this is additional burden rather than core leadership work. I'll manage that through how I brief it. The outcome I'm committing to is a measurable reduction in short-term absence by week sixteen, reviewed at week eight with the sergeants running it."
Same scenario. The first version tells the panel you would look at things. The second tells them what you've already decided, why, what it costs and what you're accountable for.
Both sources cited in the STANCE version above are publicly available. HMICFRS State of Policing reports are published annually and freely accessible. The National Police Health and Wellbeing Strategy is maintained by Oscar Kilo, the national police wellbeing service. Naming verifiable sources in your Assessment is what turns an opinion into evidence.
Section 5 — Rank calibration within STANCE
The framework applies at every rank. What changes is the scope of each step. The most common error is calibrating STANCE at the rank below the one you're applying for. A chief inspector presenting a command unit solution to a force-level problem. An inspector presenting a team outcome to a command question.
Sergeant
SituationA team-level problem, named, with evidence it exists in your shift or team.
Take a positionA decision about how your team will address it, already made and stated.
AssessmentWhat you know about your officers, your shift pattern, your local context.
Navigate the optionsThe alternatives a sergeant with your team could realistically have chosen.
Cost and RiskYour team's capacity, their time, and the supervisory dependencies.
End with ImpactA team-level outcome owned through your direct management of the shift.
Watch out: If your presentation doesn't mention your responsibility for the people delivering it, you're presenting at constable level.
Inspector
SituationA command-level problem, connecting to force priorities and the operational picture.
Take a positionA decision about how your command will address it, at a level that requires inspector authority.
AssessmentForce priorities, the HMICFRS inspection picture, what the evidence says at command level.
Navigate the optionsAlternatives that a command-level officer could credibly have pursued.
Cost and RiskYour command's capacity and the functions it draws on, including sergeant-tier delivery.
End with ImpactA command-level outcome you own through your sergeants.
Watch out: If your presentation is entirely about what you'll do personally rather than what your command will deliver, you're presenting at sergeant level.
Chief Inspector
SituationA force-level or portfolio problem connected to the strategic environment.
Take a positionA decision that operates at force level and requires chief inspector authority to implement.
AssessmentNational policing priorities, the HMICFRS inspection architecture, public confidence data, and the statutory landscape.
Navigate the optionsAlternatives that force-level leadership could have credibly chosen, rejected with strategic reasoning.
Cost and RiskForce-level resource, multi-function dependencies, inspection risk, and reputational exposure.
End with ImpactA strategic outcome the force can be held to, with a governance mechanism that sits at your level.
Watch out: If your End with Impact sounds like something you'd say to your own team rather than to a Chief Superintendent, rewrite it upward.
A ten-minute presentation at 120 words per minute is roughly 1,200 spoken words. The targets below are calibrated for that window. Most officers overrun because they spend too long on Assessment and don't leave enough time for Navigate, Cost and Risk, and End with Impact. The last three sections are where the panel scores your strategic thinking, not your knowledge of the evidence.
Situation
60–80 words · ~0:40 spoken
Two sentences. The problem and the evidence it exists. Nothing else.
Take a position
60–80 words · ~0:40 spoken
The recommendation, already decided. No hedging. No preview of the evidence.
Assessment
300–400 words · ~2:30–3:20 spoken
The biggest section. Named sources, specific data, direct connection to your recommendation.
Navigate the options
200–280 words · ~1:40–2:20 spoken
At least two credible alternatives, each rejected with a clear reason.
Cost and Risk
250–300 words · ~2:00–2:30 spoken
Real costs, real risks, specific mitigations. Named at the right rank level.
End with Impact
30–50 words · ~0:20 spoken
One sentence. Outcome, measure, personal ownership. No summary.
Ten minutes feels long until you present it out loud. The most common failure is running over time on Assessment and collapsing Navigate and Cost and Risk into two sentences each. Practise with a timer. The sections you rush are the sections the panel scores most carefully.
Section 7 — Common failure modes
Building to the recommendation
The most common structural failure at inspector and chief inspector boards. The officer opens with context, builds through options, and arrives at their recommendation in the last quarter of the presentation. Nothing in that structure is wrong, but the panel has been waiting three minutes to find out what the officer actually thinks. By the time the recommendation lands, it feels like the conclusion of a report rather than the decision of a leader.
Rank calibration failure
The scope of each STANCE section should match the rank being applied for. A chief inspector presenting a command unit solution to a force-level problem. An inspector presenting a team outcome to a command question. STANCE doesn't fix that by itself, but it creates the discipline to ask at every step: is this answer pitched at the level I'm applying for, or the level I'm leaving?
Weak or absent alternatives in Navigate
Presenting alternatives that are obviously wrong and dismissing them easily. The panel expects you to have genuinely engaged with the strongest counter-argument. If your Navigate section reads as a formality rather than a genuine evaluation of competing options, it won't score. Find the argument a reasonable senior officer could actually defend, and then explain precisely why it fails.
Cost and Risk as a logistics list
Naming costs and risks without naming the strategic and inspection dimensions. At chief inspector level, the panel expects you to know what continued underperformance would mean for the force's inspection rating and for public confidence. A Cost and Risk section that reads like a project plan without any strategic or reputational dimension scores at inspector level, not chief inspector.
A closing summary instead of a commitment
Ending with a restatement of what you've already said. End with Impact is a forward-looking commitment: a specific outcome, a measurable standard, and personal ownership. The last thing the panel hears is the thing they carry into scoring. A summary close wastes the strongest memory slot in the entire presentation.
Vague evidence in Assessment
References to 'force data', 'research shows', 'various studies suggest' score poorly because they're unverifiable and signal that the officer doesn't know the evidence well enough to name it. Assessment requires named sources, specific data, and a direct connection between the evidence and the recommendation already stated in Take a Position.
Section 8 — STANCE, PEEL, and STARR: which one applies
State6 uses three frameworks. Each is built for a different question type. Using the wrong one for the question being asked costs marks, because the structure doesn't match what the panel is listening for.
"Tell me about a time when..." / "Give me an example of..." / "When have you..."
Your answer draws on past experience and needs to show individual action, outcome and reflection. The panel is assessing whether you've already demonstrated the behaviour at the level required.
"How would you handle..." / "What would you do if..." / "What is your view on..."
Your answer takes a position on a hypothetical, grounds it in evidence, engages with the tension and commits to action. PEEL is a spoken answer to a single question.
STANCE — Presentation tasks
A structured scenario briefed in advance or set out in writing, requiring a recommendation and an accountable close.
STANCE is for presentations. The difference from PEEL is scope and formality. PEEL is one spoken answer. STANCE is a structured presentation with a beginning, a body and a close. If you've been given a topic and told you have ten minutes, STANCE applies.
If you're preparing for forward facing questions alongside your presentation, how to structure a forward facing question covers why PEEL and STARR aren't interchangeable and what panels are actually listening for.
If you're unsure which applies, listen to how the question is framed. A presentation task will typically be briefed in advance or set out in writing. You'll have time to structure it. That's when STANCE applies.
Section 9 — Ready to build?
The STANCE Presentation Builder is inside State6. Enter your topic, generate a rank-calibrated Presentation Model with prompts for each section, and write your own answer section by section. Each section has a coach button that gives you structured feedback on what's working and what needs improving, timed across three rounds to match how a real board would hear it.
STANCE and the voiced AI Mock Board are both on the Gold plan, so you can build your presentation and then deliver it out loud to a scoring panel.
STANCE is a skill, not a script. The structure becomes second nature through repetition. The goal isn't to sound like you're using a framework. It's to sound like a confident, decisive leader who has clearly thought through the problem before they walked into the room.