Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Follow the standard message process (previously published in Operations)

Control Measure Knowledge

Note: This legacy control measure was previously published in the Operational Guidance for Operations, and will be replaced by Fire Control Guidance for Incident management.

 

Fire and rescue services should consider the use of standard message templates to ensure communications between the fire control room and the incident ground are brief. Employing a suite of standard messages will also lead to consistent reporting of incident specific details, which are understood by all and which will assist fire control room operators in recording such data accurately.

This approach should be used for all methods of transmitting information, including radios and telephones. Mobile data terminals linked to mobilising systems can send status messages in text format, but they should also use standard templates to reduce any confusion as to the type and nature of a message.

The call sign or incident commander’s name should precede any message; this will assist fire control personnel to accurately identify the log to be annotated with information.

Additional messages that are passed between incident ground and the fire control room should follow predetermined content and structure.

Messages or information exchanged with other agencies should follow the guidance provided in the JESIP publication, Joint Doctrine: the interoperability framework.

Fire control personnel should be mindful that mobilisation messages may influence the behaviour of responding personnel. In particular the messages may affect a driver’s perception of urgency and therefore their driving behaviour. Using standard messages may avoid or minimise this happening.

It may be necessary to provide responding personnel while driving to the incident with:

  • Further relevant information
  • Changes to the incident that may influence the urgency of attendance
  • Changes to access routes

Strategic Actions

Tactical Actions