Your first incident in ten minutes

One real call, replayed against the radio audio, before the coffee gets cold. An address, the apparatus that went, and ten minutes.

Your first incident in ten minutes — recording pending

You do not need audio to build a replay. You need an address, the apparatus that went, and ten minutes.

Steps

New incident. Type the address. The building footprint is fetched for you where coverage exists; otherwise trace it in four clicks.
Guided setup, or skip it. The wizard asks what went on the call: mutual aid, audio source, CAD paste, photos. Every answer lands where the panels would have put it.
Place the first engine. Drag it to where it stopped. Unlock, rotate, lock.
Draw the attack line. Hold and drag from the pump panel to the front door. The line projects onto the floor plan on its own once one exists.
Press Record, then Play. Every placement is timestamped. Without audio the clock is a stopwatch; with audio the replay tracks the radio.
Watch it back on the TV. Theater mode hides the panels. Escape brings them back.

Adding the radio audio later

County audio for Monroe County is on OpenMHz. Radio → Import from OpenMHz pulls the talkgroup for the call's window; your admin can set the county system once so it is prefilled. Transcription and event detection run after upload and are labelled as AI drafts until someone checks them against the recording.

What this does not do

training, pre-planning, and after-action review only — never live-incident reliance. Not a CAD or dispatch system; nothing here dispatches or tracks a unit in real time.
replay reconstructs what was **logged**, not a simulation — nothing is interpolated or inferred except vehicle motion between two recorded points. Personnel positions are hard cuts by design; the app will not invent a path a firefighter did not take.
transcription is imperfect on poor radio audio and is meant to be corrected by a human — the corrections are the product, not an afterthought. Detected events are suggestions on a timeline, never a finding. No AI-vendor names in customer copy.

Your first incident in ten minutes

One real call, replayed against the radio audio, before the coffee gets cold. An address, the apparatus that went, and ten minutes.

Your first incident in ten minutes — recording pending

You do not need audio to build a replay. You need an address, the apparatus that went, and ten minutes.

Steps

New incident. Type the address. The building footprint is fetched for you where coverage exists; otherwise trace it in four clicks.
Guided setup, or skip it. The wizard asks what went on the call: mutual aid, audio source, CAD paste, photos. Every answer lands where the panels would have put it.
Place the first engine. Drag it to where it stopped. Unlock, rotate, lock.
Draw the attack line. Hold and drag from the pump panel to the front door. The line projects onto the floor plan on its own once one exists.
Press Record, then Play. Every placement is timestamped. Without audio the clock is a stopwatch; with audio the replay tracks the radio.
Watch it back on the TV. Theater mode hides the panels. Escape brings them back.

Adding the radio audio later

What this does not do

training, pre-planning, and after-action review only — never live-incident reliance. Not a CAD or dispatch system; nothing here dispatches or tracks a unit in real time.
replay reconstructs what was **logged**, not a simulation — nothing is interpolated or inferred except vehicle motion between two recorded points. Personnel positions are hard cuts by design; the app will not invent a path a firefighter did not take.
transcription is imperfect on poor radio audio and is meant to be corrected by a human — the corrections are the product, not an afterthought. Detected events are suggestions on a timeline, never a finding. No AI-vendor names in customer copy.