Fire Scene StudioFire Scene Studio
Exercise complete — open the debrief

Exercise · level 1 · seed 184040019

The Willows — Rear Bedroom Fire

T+10min
Venting fireOffensive

Frames · Fire Scene Engine

Selected view · T+10 minutes is loading…

Loading…

T+10 min

Well alight — flames from the opening and making up; dark smoke, heavy, hot.

Timeline
T+10 / 10Resolution

Doctrine-referenced debrief · not an assessment

[1]

Incident Commander — Command Performance Review

SFJ Awards Level 3 Award in Initial Incident Command in Fire and Rescue ServicesOfqual Ref: 610/0183/1 · Unit 6033 · 65h TQT

Competent operational command meeting UK FRS standards, with sound dynamic risk assessment and structured execution across core incident phases.

Doctrine Score82/100
competent
Situational Awarenesscompetent
70%
  • No explicit Level 3 anticipation recorded. Look ahead: verbalise predicted fire spread and future resource needs before escalation occurs.
  • Limited Level 2 understanding evident. Translate observations into operational meaning (e.g. what dark pulsing smoke signifies for entry safety).
  • Level 1 Perception active (1 situational observations recorded).
  • All identified critical hazards had corresponding mitigating actions recorded.
Decision Makingexemplary
90%
  • Orders judged on their effect: 2 given — 2 sound, 0 wrong for the conditions, 0 not scored.
  • Decision controls and cues are not captured from typed orders and are not scored.
Interpersonal Communicationexemplary
90%
  • Rapid, prompt acknowledgement to Mrs Jones.
  • Response provided, but did not explicitly repeat back critical operational specifics.
  • Rapid, prompt acknowledgement to Mrs Stephens.
  • Response provided, but did not explicitly repeat back critical operational specifics.
  • Rapid, prompt acknowledgement to Fire Control.
  • Response provided, but did not explicitly repeat back critical operational specifics.
  • Rapid, prompt acknowledgement to Fire Control.
  • Response provided, but did not explicitly repeat back critical operational specifics.
  • Rapid, prompt acknowledgement to Fire Control.
  • Response provided, but did not explicitly repeat back critical operational specifics.
  • Rapid, prompt acknowledgement to Command Support.
  • Response provided, but did not explicitly repeat back critical operational specifics.
Teamwork & Coordinationcompetent
75%
  • Sector commanders coordinated appropriately.
Leadership & Command Presencecompetent
75%
  • Maintained clear command presence and tactical leadership.
Personal Resilienceexemplary
90%
  • Active monitoring intervals maintained without decision stagnation.
  • Maintained safe span of control (0 sectors).

Key Strengths

  • Handled all dynamic roleplay injects and operational messages effectively.

Development & Learning Opportunities

  • Safety warning: No scene access control point (SACP) established to log personnel entering the inner cordon.
  • Operational briefing was unstructured — adopt the standard IIMARCH framework (Information, Intent, Method, Risk).

The incident got away — but there’s plenty to take forward.

Developmental reflection — not an assessment

What went well

  • Good call — monitor at T+0 (“Carry out a 360 of the building”).
  • Good call — monitor at T+5 (“Establish an inner cordon at the front”).
  • Every judged decision (2) matched the conditions.

What to develop

  • Ended by the assessor with the fire NOT under control.
  • Property partially saved (damage 11).

Key decision points

  • T+00 [monitor · good] “Carry out a 360 of the building”
  • T+05 [monitor · good] “Establish an inner cordon at the front”

Learning points

  • Incident states: Venting fire (T+0).
  • Send an early METHANE / informative message to set the incident picture.
  • Gather information early — speak to the witness, check the ORI, ask Fire Control and the BA crews — and act on what you learn.

Discuss this with the training mentor

Mentor grounded in published UK FRS principles — developmental discussion, not assessment. It cites its sources or reframes as a question.

Incident report

Practice — not a real IRS submission