Audio
Speed:

Theory Map and Assessor Q&A Reference

Candidate: David Agyei. Assessment: 18 June 2026, 14:00. AM2 Q&A AM1 Professional Discussion

How to use: Section 1 gives you the quick lookup table of theories by decision area, then a detail card for each. Section 2 gives you the eight questions most likely to expose a gap, with a Pass-level answer and a Distinction-level answer for each. Read the distinction answer. Practise saying it out loud before Wednesday.
› Section 1: Theory Map A–Z by decision area

When the assessor asks "which models or frameworks underpinned your approach?", use this table. Name the theory, say where you used it, then evaluate it (the evaluation is what moves Pass to Distinction).

Decision Area Theory / Framework to Name Where it appears Assessment
Change management Lewin's unfreeze/change/refreeze model to diagnose Phase 1 failure; Kotter's "creating urgency" for Phase 2 coalition building Proposal Section 9 closing observation; Root Cause analysis AM1 + AM2
Coaching practice GROW model (Goal, Reality, Options, Will); non-directive, person-centred approach; systemic coaching CPD Coaching Testimonials 2025; West Midlands Coaching Pool; ELD K4.2, S4.2 AM1
Financial analysis Proxy costing with transparent assumption labelling; ADASS/PSSRU as published public sector benchmarks Cost Avoidance v0.1; Proposal Section 6 AM2
Leadership approach Situational Leadership (Hersey and Blanchard): directing vs coaching based on stakeholder readiness Jim Ford engagement; provider management; coaching testimonials; ELD K4.1 AM1 + AM2
Options appraisal Cost-benefit analysis with do-nothing as explicit baseline (Green Book principle) Proposal Section 8: three alternatives evaluated and rejected AM2
Project management Agile/Scrum: empirical process control (inspect and adapt, sprint cadence) Slide 3 decision; Proposal Section 3; 12-week sprint plan AM2
Stakeholder management Mendelow's Power/Interest Matrix FFP stakeholder mapping; SWANN partner engagement; ELD K6.1 AM1 + AM2
› Theory Detail Cards A–Z by framework name

Each card gives you the justification for choosing the theory, its limitations in your context (this is the distinction bit), and a sentence you can say out loud.

2. Agile/Scrum: Empirical Process Control
Decision area: Project management. Used in: SWANN Phase 2 delivery design.
Why you chose it

Phase 1 used a linear, waterfall approach. Requirements changed partway through and the project could not adapt. Stakeholder confidence in the PMO's delivery ability was affected. Agile's inspect-and-adapt cadence allowed SWANN Phase 2 to deliver visible, incremental outputs at each sprint, which maintained stakeholder confidence during the council's financial emergency. Short sprint cycles also meant that if requirements changed again, the cost of change was contained.

How you used it
  • 12-week sprint framework with defined deliverables per sprint.
  • Now/Next/Later roadmap as a visual tool to communicate progress and intent without committing to a locked-in Gantt.
  • Sprint reviews to show incremental progress to SWANN partnership at each monthly meeting.
  • Requirements workshop on 2 June: user stories confirmed collaboratively, not imposed.
Limitation (say this for Distinction)
Public sector procurement and governance cycles do not naturally align with sprint cadence. The SWANN portal required engagement with the council's digital team, which operates on its own change management process and approval timeline. I had to adapt rather than implement pure Scrum: the sprint framework was used for planning and visibility, but I could not control the velocity of dependencies sitting outside my team. The Agile literature assumes team authority that did not exist in a cross-functional, multi-agency context.
Say this out loud

"I chose an agile sprint approach because Phase 1's waterfall failure showed that stakeholder confidence needed visible, incremental delivery. I adapted Scrum principles to fit council procurement constraints rather than implementing it in a pure form."

5. Cost-Benefit Analysis with Do-Nothing Baseline
Decision area: Options appraisal. Used in: Proposal Section 8.
Why you chose it

Green Book best practice requires genuine options comparison including a do-nothing baseline. Without a do-nothing option, a recommendation reads as a foregone conclusion rather than a justified choice. Including three genuine alternatives and evaluating each against explicit criteria makes the recommendation defensible under scrutiny from commissioners, senior leaders, or an assessor.

How you used it
  • Option 0: do nothing. Baseline against which all other options are measured.
  • Option 1: standalone referral form. Lower cost, lower functionality. Rejected on data tracking grounds.
  • Option 2: external system integration. Higher capability, higher risk. Rejected on procurement timeline and dependency grounds.
  • Option 3 (recommended): Dynamics 365 portal. Builds on existing council infrastructure. Preserves data tracking integrity. Proportionate to Phase 2 scope.
Limitation (say this for Distinction)
The options appraisal is based on cost, risk, and strategic alignment. It does not include a full sensitivity analysis of what happens if the Dynamics 365 portal takes longer than anticipated to build, which is a real risk given the council's digital team's existing workload. A more rigorous Green Book appraisal would have weighted each option against a wider range of criteria and included a risk-adjusted cost estimate. I made a pragmatic judgment that this level of analysis was proportionate to a Phase 2 project at this scale, but I recognise it is not the same as a full HMT-level options appraisal.
Say this out loud

"I structured the options appraisal with an explicit do-nothing baseline, following Green Book principles, so the recommendation is justified against alternatives rather than presented as the only option. I would acknowledge it is a proportionate rather than exhaustive appraisal at this project scale."

7. GROW Model and Non-Directive Coaching
Decision area: Coaching practice. Used in: West Midlands Coaching Pool; Claire Allen sickness absence project; day-to-day team coaching.
Why you chose it

A non-directive, person-centred approach enables the coachee to discover their own solutions rather than receiving direction. This is both more sustainable (the coachee owns the outcome) and more appropriate in coaching relationships where the coach is not the line manager and does not have the full context of the coachee's situation. GROW (Goal, Reality, Options, Will) provides a structured conversation framework that keeps the session purposeful without prescribing the answer.

How you used it
  • 15 coachees via the West Midlands Public Sector Coaching Pool over 5+ years.
  • Outcomes: 2 returned to work following burnout; 6 received promotions. All referenced in client evaluations seen by Shanda Reid.
  • Claire Allen: GROW principles applied within an operational work context (sickness absence process mapping) rather than a formal coaching session. This is coaching embedded in practice, not just in designated sessions.
  • CPD: systemic coaching, wellbeing coaching, and career transitions modules completed. Demonstrated by ongoing learning, not just initial qualification.
Limitation (say this for Distinction)
Non-directive coaching works when the coachee has sufficient experience and self-awareness to generate their own solutions with facilitated reflection. In cases where a coachee is new to a role or facing a crisis, a purely non-directive approach can feel unsupportive. I have had to shift between non-directive coaching and more directive mentoring based on readiness. Shanda Reid's coachees who returned from burnout required a more scaffolded approach early in the process before non-directive techniques became productive. Knowing when to shift mode is the skill; the framework is the starting point.
Say this out loud

"I use the GROW model as a framework but the core principle is non-directive: the coachee owns the solution. The skill is knowing when to shift from non-directive to more directive support based on readiness, which is a judgement call the model doesn't make for you."

6. Lewin and Kotter: Change Management Models
Decision area: Understanding Phase 1 failure and designing Phase 2. Used in: Proposal Section 9; Root Cause analysis.
Why you chose it

The proposal's closing observation states: "governance structures built retrospectively under pressure; should not happen again." This is a systemic diagnosis of why Phase 1 failed. Lewin's unfreeze/change/refreeze model provides the explanatory framework: Phase 1 changed the technology (the "change" stage) without ever completing the "unfreeze" stage. Stakeholder buy-in was assumed rather than built. Kotter's model of building a guiding coalition and creating visible short-term wins informed the Phase 2 design.

How you used it
  • Lewin: Phase 1 diagnosis. Technology was changed but working practices and professional referrer buy-in were never unfrozen first. Phase 2 opens with a requirements workshop and partnership presentation precisely to unfreeze before building.
  • Kotter step 1 (create urgency): financial case (£390k cost avoidance) presented to create the "burning platform" for action.
  • Kotter step 3 (build a guiding coalition): SWANN partnership, Director, AD, Lisa Middleton as Commissioner all engaged before any technical build began.
  • Kotter step 6 (generate short-term wins): sprint framework designed to deliver visible outputs at each stage, not a single final deliverable.
Limitation (say this for Distinction)
Both Lewin and Kotter assume a degree of organisational control that a project lead without line authority does not have. I could create urgency and build a coalition but I could not unfreeze the organisation's working practices unilaterally. Professional referrer resistance from Jim Ford required individual relational work that sits outside both models. Real change in a multi-agency, cross-boundary context is messier than either framework suggests. I used them as diagnostic lenses rather than prescriptive processes.
Say this out loud

"I drew on Lewin's model to diagnose why Phase 1 failed. The technology was changed but the working practices were never unfrozen first. Phase 2 corrects that sequence. Kotter's coalition-building informed how I structured the partnership engagement before any technical build began."

1. Mendelow's Power/Interest Matrix
Decision area: Stakeholder management. Used in: FFP As-Is Meetings project and SWANN Phase 2.
Why you chose it

The FFP project involved stakeholders ranging from a Director of Children's Services down to operational staff, with no single reporting line connecting them. Mendelow gave a structured basis for deciding how to allocate engagement effort and what level of information each stakeholder needed. Director Shaw required detailed briefing; operational staff required simple takeaways from the analysis.

How you used it
  • Director David Shaw (high power, high interest): managed closely; briefed with full report and infographic; asked for Director-level commitment on meeting review.
  • AD Natasha Moody (high power, developing interest): kept satisfied; responded to her anomaly query constructively before wider release.
  • HWBB/Louisa Jones (medium power, high interest): kept informed; methodology shared for cross-organisational adoption.
  • Operational staff (lower power, high interest locally): minimal data, clear summary output; anonymised below Service Manager level to protect trust.
Limitation (say this for Distinction)
Mendelow maps power and interest but does not capture emotional investment in the status quo. Jim Ford's concern about Phase 1 was not a matter of low power or low interest. It was a matter of prior experience and professional reputation. I had to supplement the matrix with trust-building conversations before presenting the Phase 2 design, because the matrix alone would have classified him incorrectly and triggered a transactional engagement that would not have worked.
Say this out loud

"I used Mendelow's power/interest matrix to structure my stakeholder approach, but I found it had to be supplemented with relational trust-building because power and interest alone don't capture emotional investment in the status quo."

3. Proxy Costing with Transparent Assumption Labelling
Decision area: Financial analysis. Used in: Cost Avoidance Framework v0.1.
Why you chose it

No internal unit cost data existed for escalations from early help to statutory social care within Shropshire Council. ADASS (Association of Directors of Adult Social Services) and PSSRU (Personal Social Services Research Unit) produce published, peer-reviewed unit cost benchmarks used by HMT-approved analysts across the public sector. Using them as proxies gave the financial case a credible and replicable basis without waiting for internal data that did not exist.

How you used it
  • All proxy assumptions explicitly labelled [ASSUMPTION: PROXY] in the document. Not hidden.
  • Three scenarios modelled: 5%, 10%, 20% reduction in escalations.
  • £390k illustrative figure based on 20% reduction scenario. Not presented as a financial commitment.
  • Five outstanding questions sent to Lisa Middleton for confirmation: total contract value, performance metrics, referral volume targets, unit cost data, Phase 1 outcomes data.
Limitation (say this for Distinction)
The £390k figure is illustrative only. ADASS/PSSRU proxies are national averages; Shropshire unit costs may be higher or lower depending on contract structures I do not yet have access to. The point of Phase 2 is precisely to build the data infrastructure that replaces these proxies with actuals. The financial case is not a forecast; it is a demonstration of what becomes possible once the measurement framework exists. That is why Recommendation 3 (building the measurement framework in parallel) is as important as the portal build itself.
Say this out loud

"The £390k is illustrative, using ADASS/PSSRU proxies because internal unit cost data doesn't exist yet. Every assumption is labelled. The purpose of Phase 2 is to build the infrastructure that replaces proxies with actuals. That's why the measurement framework recommendation matters as much as the portal."

4. Situational Leadership (Hersey and Blanchard)
Decision area: Leadership approach. Used across: SWANN, FFP, coaching practice.
Why you chose it

Different stakeholders had different readiness levels for change. Jim Ford (experienced, resistant) needed a different approach to Charlotte Saywell (capable, willing). Applying the same leadership style to every participant would have been counterproductive. Situational leadership gave a structured basis for adjusting approach deliberately rather than reactively.

How you used it
  • Directing: Jim Ford, who had seen Phase 1 fail and needed clear rationale before engagement, not open-ended consultation.
  • Coaching: providers whose systems were technically incompatible with the original design. Worked through options with them rather than imposing a solution.
  • Delegating: Charlotte Saywell, who coordinated the FFP data collection across 73 staff with minimal oversight once briefed.
  • Supporting: Shanda Reid's coachees, where scaffolding was provided but direction was withheld to build ownership.
Limitation (say this for Distinction)
Situational leadership assumes the leader can accurately assess readiness and has sufficient authority to adjust their style accordingly. In a cross-functional project without line authority over most participants, applying situational leadership required influence rather than direction. I could not instruct Jim Ford; I had to earn his engagement. The model is helpful for diagnosing what approach is needed but does not tell you how to execute that approach when you have no formal authority. That gap is where the trust-building work and Mendelow's stakeholder analysis became necessary supplements.
Say this out loud

"I applied situational leadership to adjust my approach by stakeholder. Directing with Jim Ford who needed clarity on rationale, coaching with providers to adapt their processes, delegating to Charlotte Saywell. The challenge was doing this without line authority, which meant influence had to substitute for direction."

› Section 2: Eight Dangerous Questions A–Z by question topic

These are the questions most likely to be asked and most likely to cost marks if answered at Pass level. For each one: the Pass answer is what most candidates say. The Distinction answer is what you should say. The evidence anchor tells you which file to reference if needed.

Question 8
"How did you decide to deprioritise the Children's EHM Mapping workstream and what was the cost of that decision?"
AM2 Q&A
Pass-level answer (do not stop here)
"I made a pragmatic decision to focus on SWANN Phase 2 given the capacity constraints and EPA deadline."
Distinction-level answer
"The deprioritisation was a deliberate resource allocation decision, not a reactive one. At the point where SWANN Phase 2 and the EHM Mapping workstream were competing for the same capacity, I assessed them against three criteria: strategic urgency (SWANN Phase 2 was directly linked to the financial recovery mandate; EHM Mapping was valuable but not time-critical), stakeholder dependency (SWANN had an active partnership with scheduled meetings and commitments; EHM Mapping had no external accountability structure), and reversibility (EHM Mapping could be picked up after Phase 2 without significant rework; pausing SWANN mid-sprint would have broken the cadence and damaged stakeholder confidence). The cost of deprioritisation is that EHM Mapping evidence remains incomplete, which limits the As-Is picture across the broader system. I was explicit about this in the presentation. The risk I accepted is that EHM Mapping may become urgent before I have capacity to return to it. The mitigation is that the As-Is Meetings Mapping methodology I developed for FFP is transferable and could be applied by another team member to EHM with appropriate briefing."
Evidence anchor

Presentation Slide 2 (managing self and workstream prioritisation); ELD B3.3, K5.1; SWANN updates.

Question 1
"How does your project connect to Shropshire Council's wider strategic priorities?"
AM2 Q&A
Pass-level answer (do not stop here)
"The SWANN Phase 2 project supports the council's early intervention agenda and helps reduce escalations to statutory services."
Distinction-level answer
"Shropshire Council is managing a £121 million financial emergency declared in 2024. The MHCLG has issued an improvement notice and the council faces external scrutiny. The single largest cost pressure in children's services is escalation from early help to statutory social care. SWANN Phase 2 directly addresses that pressure by building the data infrastructure needed to measure cost avoidance on escalations. Phase 1 failed to create that infrastructure. The £390k illustrative saving figure is not a financial commitment; it is a demonstration of what becomes measurable once Phase 2 is complete. The connection to the Shropshire Plan 2022 to 2025 outcomes framework is explicit in the proposal's strategic context section. This project exists because the financial recovery mandate requires evidence-based early intervention investment, and that evidence currently cannot be generated."
Evidence anchor

Proposal Section 1 (strategic context); Cost Avoidance v0.1; ELD Golden Thread statement; ELD K1.3, S4.1.

Question 6
"Tell me about a time you had to challenge upwards, and what happened as a result."
AM1 Professional Discussion
Pass-level answer (do not stop here)
"I presented findings to senior stakeholders and they responded positively."
Distinction-level answer
"The clearest example is the FFP As-Is Meetings Mapping project. I identified £770k to £851k in annual meeting costs across Children's Services, equivalent to 12.5 to 14 full-time equivalent social workers. I presented those findings to the Director of Children's Services, David Shaw, alongside his Assistant Director Natasha Moody and Programme Manager Charlotte Saywell. Presenting sensitive capacity and cost data about senior leaders' own meeting behaviour to the Director who attends those meetings is an inherently uncomfortable position for someone at my grade. I managed it by framing the findings as a system-level analysis, anonymising data below Service Manager level, and focusing on the structural causes rather than individual behaviour. Director Shaw's response was that he was going to review his own meeting attendance and whether those meetings were the best way to achieve their intended aim. That is a Director-level behavioural commitment secured without any formal authority over his diary. The HWBB also adopted the methodology cross-organisationally. Charlotte Saywell described it as one of the PMO's strongest pieces of work. The reflection: I could have softened the findings to avoid the conversation. I did not. That was a deliberate choice grounded in the same principle as the transparent cost avoidance model: presenting complete information, even when it is uncomfortable, is more professional than managing the discomfort by omitting it."
Evidence anchor

Evidence 9 (FFP Comms Update email chain); ELD K6.1, S6.1, B1.3, B4.2; Charlotte Saywell testimony.

Question 5
"There were 31 outstanding referrals with no service level agreement as of your submission. What is happening to those people and what decisions did you make about escalation?"
AM2 Q&A
Pass-level answer (do not stop here)
"The 31 referrals are being managed and Phase 2 will address the SLA gap once the portal is built."
Distinction-level answer
"The 31 outstanding referrals represent a live operational risk that I flagged at the 27 May SWANN partnership meeting and documented in the RAID log. As of 2 June 2026, 13 referrals remained outstanding for Shropshire Mental Health, pending decryption and forwarding by Kate Hobbs; the root cause was a mailbox encryption issue that blocked Customer Services from accessing referrals, now resolved via a new Swan mailbox. The Live Well Shropshire referrals had been cleared. The absence of an SLA is a governance gap inherited from Phase 1, confirmed by both Kate and Jim at the 2 June meeting. My decision on escalation was to bring this explicitly to the partnership rather than manage it operationally without visibility, because these are families who have already sought support once and a second failure to respond would have both a human cost and a reputational risk for the council. The Phase 2 digital portal directly addresses the root cause: referrals currently arrive through inconsistent channels with no tracking mechanism. Once the portal is live, response times become measurable and accountable. The interim position is: Kate Hobbs unencrypting and forwarding outstanding cases; providers sending confirmation emails to the CSCDuty mailbox; advisors including addresses in the further information field as a workaround pending a form fix."
Evidence anchor

SWANN updates 3 June file; RAID log; Success Outcomes v0.1; ELD B1.3.

Before Wednesday: 10 June confirmed these 13 were not dependent on Customer Services (referrals forwarded; Shropshire Mental Health responding to residents). Call Kate Hobbs on 17 June to confirm whether all 13 are now resolved and note the final count for your opening remarks on 18 June.
Question 2
"What is the basis for your £390,000 cost avoidance figure and how confident are you in it?"
AM2 Q&A
Pass-level answer (do not stop here)
"It is an estimate based on national benchmarks and I acknowledge it needs to be confirmed with actual data."
Distinction-level answer
"The figure is explicitly illustrative. It uses ADASS and PSSRU unit cost benchmarks, which are the standard published sources for social care proxy costing in the UK. Every assumption in the model is labelled [ASSUMPTION: PROXY] rather than presented as confirmed fact. The reason I proceeded with proxies is that internal unit cost data does not exist within Shropshire Council's current recording systems. That is part of the problem Phase 2 is designed to solve. Five specific questions have been sent to Lisa Middleton for confirmation: total contract value, performance metrics, referral volume targets, unit cost data, and Phase 1 outcomes data. The illustrative calculation in the submitted presentation runs as follows: 200 referrals per year once the electronic form is live (estimated), multiplied by a 20% deflection rate (NHS England social prescribing evidence, lower end), gives 40 escalations avoided. 40 x £750 assessment cost = £30,000 assessment avoidance; 40 x 60% progression to care packages (NHS Digital eligible rate) = 24 care packages avoided x £15,000 per year (ADASS conservative figure) = £360,000 care package avoidance. Total: £390,000. All inputs labelled as estimates or proxies in the presentation. None of the five questions have been answered as of the assessment date; a meeting with Lisa Middleton is scheduled for 23 June to work through them. The proxy model therefore stands as the basis for the cost avoidance figure on 18 June. The intellectual design of the model is sound; the figures will be replaced with actuals once Phase 2's measurement framework is operational. This transparency is itself a methodological choice: I would rather present a clearly labelled proxy than an unreferenced figure that cannot be reproduced or challenged."
Evidence anchor

Cost Avoidance v0.1 (Evidence: supporting evidence folder); Proposal Section 6; ELD K1.3, B4.2.

Status as of 15 June: Meeting with Lisa scheduled for 23 June (post-EPA). None of the five questions answered as of the assessment. Be ready to state this clearly: the proxy model is the basis for the figure on 18 June; the meeting on 23 June is the next step to replace proxies with actuals.
Question 7
"What would you do differently if you were starting Phase 2 again?"
AM2 Q&A
Pass-level answer (do not stop here)
"I would have confirmed the strategic owner earlier and made sure the financial data was in place before submission."
Distinction-level answer
"Three things. First, I would have built structured financial confirmation milestones into the project plan from week one rather than discovering at the point of cost avoidance modelling that the five key data points from the commissioner had not been collected. I underestimated how long organisational data requests take when the person being asked has competing priorities and no formal obligation to respond to your timeline. Second, I would have escalated the strategic owner confirmation earlier. I built a target date into the ToR but did not build a governance escalation trigger if that date was missed. That is a planning gap, not just an execution gap. Third, I would have been more deliberate about documenting the learning from Phase 1 formally at the outset. The root cause analysis exists but was produced informally. A formal post-implementation review of Phase 1, signed off by the SWANN partnership, would have created a shared narrative about failure that would have made it easier to build the Phase 2 coalition. The current situation is that Phase 1's failures are understood by me but not formally acknowledged by the organisation."
Evidence anchor

Cost Avoidance v0.1 (five outstanding questions); SWANN ToR (TBC field); Root Cause analysis; ELD S8.1, K8.1.

Question 4
"Which management models or theories informed your approach to this project, and where specifically did you apply them?"
AM1 + AM2
Pass-level answer (do not stop here)
"I used stakeholder management techniques and project management tools such as RAID logs and sprint planning."
Distinction-level answer
"I drew on several frameworks deliberately. For stakeholder management I used Mendelow's power/interest matrix, which structured my engagement decisions across a diverse stakeholder landscape with no single reporting line. For project management I applied agile sprint principles from the Scrum framework, specifically the empirical process control concept of inspect and adapt, which I chose because Phase 1's waterfall failure showed that requirements would change. For leadership I applied situational leadership, adjusting between directing and coaching depending on each stakeholder's readiness. For the change management diagnosis I used Lewin's unfreeze/change/refreeze model, which explains why Phase 1 failed: the technology changed but the working practices and stakeholder buy-in were never unfrozen first. For the options appraisal I used cost-benefit analysis with a do-nothing baseline, consistent with HMT Green Book principles. I did not apply these models in isolation or as textbook prescriptions. Each one had limitations in a multi-agency public sector context, and I combined them rather than relying on any single framework."
Evidence anchor

ELD Theory Map table (Quick Reference section); Proposal Sections 3, 6, 8, 9; all Group 1 and Group 2 KSBs.

Question 3
"Your Terms of Reference show the Strategic Owner as TBC with a target confirmation date of 30 May 2026. Who is the strategic owner and when was it confirmed?"
AM2 Q&A
Pass-level answer (do not stop here)
"The strategic owner was listed as TBC at the point of the ToR but has since been confirmed."
Distinction-level answer
"The TBC reflects a deliberate governance decision rather than an oversight. At the time the ToR was drafted, two senior leaders were in scope for the role and the final confirmation was pending a meeting on [insert date]. The strategic owner role remains formally TBC as of the assessment date, documented as a live RAID risk with a target date of 30 May. Lisa Middleton as Commissioning Officer holds the senior programme accountability; the naming gap is a governance design issue, not an accountability vacuum. The lesson from Phase 1 is precisely that governance gaps left unresolved early become blockers later. I flagged this as a live risk in the RAID log and built a target confirmation date into the ToR rather than leaving it as an open item. If the strategic owner question is still being resolved, the mitigation is Lisa Middleton as Commissioning Officer is the effective strategic owner; a follow-up meeting is scheduled for 23 June to formalise the confirmation and close the RAID risk. This reflects the same principle as the financial analysis: being transparent about what is not yet confirmed is more defensible than presenting incomplete information as settled."
Evidence anchor

SWANN SPoR ToR v1.0; RAID log (8 risks, 2 issues); ELD B1.3, B4.2.

Before Wednesday: Strategic owner is still formally TBC as of 15 June. Your mitigation narrative is set: RAID-logged risk, Lisa Middleton as effective senior accountability, follow-up meeting on 23 June. Be ready to state this clearly and without apology if asked.
› Section 3: What Moves Pass to Distinction

These are the specific verbal behaviours that separate a Distinction performance from a Merit or Pass in a live assessment. Read before Wednesday. Say them out loud.

If an assessor asks about...Pass answer does thisDistinction answer does this
A decision you made Describes what the decision was and the rationale Names the criteria used to make the decision, describes the alternatives rejected, and identifies what was accepted as the cost of the chosen option
A framework or model Names the framework and describes how it was used Names the framework, describes how it was used, and then critiques its limitation in this specific context
A gap or weakness Acknowledges the gap honestly Acknowledges the gap, explains why it was accepted, describes the mitigation in place, and identifies what the residual risk is
A piece of evidence Describes what the document shows Tells the story behind the document: the context, the action taken, the outcome, and what was learned from it
Stakeholder challenge Describes who the stakeholder was and what the challenge involved Describes the power dynamic, the emotional component, the approach taken, why that approach rather than another, the outcome, and what would be done differently next time
Your development Identifies a learning or development need Identifies the learning, describes how practice changed as a result, and provides external evidence that the change was observable (e.g. Steve Humphrey's quote, coaching testimonial outcomes)
The single most important distinction behaviour: After every answer, add one sentence that evaluates rather than describes. "What this showed me was..." or "The limitation of that approach was..." or "If I were doing this again, the thing I would change is..." These sentences are what distinguish a reflective practitioner from a competent practitioner.