Question regarding the implementation of recommendation 62 from a 2006 report on Fire and Emergency Services Legislation, specifically concerning the individuality of emergency service entities' badging. The answer confirms existing practices support the recommendation.

AnsweredQoN 765Legislative Assembly
Asked
5 May 2009
Portfolio
Emergency Services

QuestionView source ↗

I refer to the report of the Community Development and Justice Standing Committee’s Report on the Inquiry into Fire and Emergency Services Legislation (Report No. 3), 2006
and, in particular, to recommendation No. 62 which provided that despite recommendation 60, the Fire and Emergency Services Authority (FESA) should ensure the individuality of emergency services entities (including badging reflective of their unit and locality) in its business practices. Therefore I ask
(a) what steps are being taken to ensure that this recommendation is put into operation;
(b) is there a current FESA policy on badging; and
(c) if so, what is it?

AnswerView source ↗

Answered
9 June 2009
Responded by
Minister for Emergency Services
Response time
35 days
(a) The identities of all services remain as intended in terms of recommendation 62, in badging and business practices. Ongoing Uniform and Protective Clothing reviews and subsequent decisions have supported this.
(b-c) Whilst there is no current policy on this subject each service retains its unique badge including the Fire and Rescue Service (Career and Volunteer); State Emergency Service; Volunteer Emergency Service; Volunteer Fire Service; Volunteer Marine Rescue Services; FESA Units and Bush Fire Brigades.  FESA Managers have appropriate badging related to their service role.
Notice: This document is created or edited using unregistered or evaluation copy of rtLib valid for testing or development purposes only. To use it for productive or any other purposes please register it. You may purchase the license on
http://www.rtlib.com

Explore WA Government Data

Search the full archive in the free dashboard, or query programmatically via API.

Explore more