Major Incident Planning and Support (MIP+S) Level 4

122 videos, 12 hours and 25 minutes

Course Content

Communications

Video 76 of 122
26 min 54 sec
English
English

Unlock This Video Now for FREE

This video is normally available to paying customers.
You may unlock this video for FREE. Enter your email address for instant access AND to receive ongoing updates and special discounts related to this topic.

Communications at Major Incidents

Aim: Enable safe, coordinated multi-agency response by sharing accurate information on scene and beyond. Poor communication can cost lives.

Why Communication Matters

  • Builds situational awareness from fragmentary, evolving information.
  • Prevents deadly assumptions and “moving the lighthouse” errors—check and verify sources.
  • Supports cross-agency coordination (police, fire, ambulance, health, local authority, site management, etc.).

Common Causes of Failure

  • Lack of information: early reports are often wrong; keep updating.
  • Lack of confirmation: clarify sound-alike words, numbers, names; challenge assumptions.
  • Lack of coordination: decisions without owners, locations, timings, or logistics plans fall through the cracks.

Methods of Communication

  • Face to face: richest signal (body language/inflection), best for command huddles.
  • Radio: know your kit (PTT, channels, battery, scan). Use voice procedure for clarity, accuracy, brevity.
  • Landlines: useful between fixed points (e.g., Command ↔ CCS); reduce radio clutter.
  • Runners: only with written messages and written replies.
  • Crowd/area tools: loud-hailer (e.g., “If you can walk, come to me”), tannoy systems, whistles (note: fire service evacuation signal).
  • Mobiles/apps: helpful but not primary in major incidents: bandwidth congestion, poor situational visibility for commanders, security issues. JESIP-type apps can help format/log SITREPs (e.g., METHANE).

Radio Networks & Interoperability

  • On-scene vs off-scene: consider Direct Mode (radio-to-radio) on scene; Trunked/Mast mode for control/remote units to protect network capacity.
  • Interoperability channels: allow commanders to speak cross-service for rapid clarification en route and on scene.

Good Practice on the Air

  • Use plain English; avoid service-specific jargon. Ask for clarification if you don’t understand.
  • Apply RSVP: steady rhythm, slow speed (dictation pace), normal volume (avoid over-modulation), clear pitch.
  • Spell clearly with the phonetic alphabet (“I spell…”). Send numbers as figures digit-by-digit.
  • Pre-warn long transmissions: “Long message, over”.
  • Use standard terms: Over (response needed), Out (no response), Roger (received), Acknowledge (confirm receipt/understanding).
  • Request repeats: “Say again all/before/after/between <keyword>”. Correct errors with “Wrong…”.
  • Prefer appointment titles on scene (“Loading, this is Silver…”) to avoid call-sign churn.

Command Responsibilities

  • Ensure critical safety information is shared sideways across agencies, not just up/down your own chain.
  • Designate a Communications Officer early (nets, modes, channel plan, backups).
  • Log decisions and rationale via control or approved apps; time-stamp messages.
  • Train regularly—voice-procedure skill-fade is real with modern “phone-like” radios.
Want a quote for your company?