Question regarding compliance with Freedom of Information Act 1992, section 96(1) for agencies within the Minister's portfolio. Reveals varying levels of compliance and currency of Information Statements across different departments.

AnsweredQoN 5554Legislative Assembly
Asked
29 June 2016
Portfolio
Emergency Services; Fisheries; Corrective Services; Veterans

QuestionView source ↗

For every department and agency in the Minister’s portfolio of responsibilities, does the agency have an Information Statement consistent with section 96 (1) of the Freedom of Information Act 1992 : (a) if yes to (1), what was the date of publication of the Information Statement. If no, why not?

AnswerView source ↗

Answered
16 August 2016
Responded by
Minister for Emergency Services; Fisheries; Corrective Services; Veterans
Response time
48 days
The Department of Fire and Emergency Services (DFES) advises:
(1) Yes.
(1)(a) 31 October 2013.
The Department of Fisheries (DOF) advises:
(1) Yes.
(1)(a) 18 July 2016.
The Department of Corrective Services (DCS) advises:
(1) Whilst the Department of Corrective Services (the Department) has an Information Statement, it has not been re-published in the last 12 months in accordance with section 96 (1) of the Freedom of Information Act 1992.
The Information Statement was incorporated into the Department of Corrective Services Handbook that was last published in April 2013. The Department advises that its Information Statement will be incorporated into its 2015-2016 Annual Report.
The State Emergency Management Committee (SEMC) Secretariat advises:
(1) No.  As a sub-department of the Department of Fire and Emergency Services (DFES), compliance with section 96 (1) of the Freedom of Information Act 1992 is undertaken by DFES.
Veterans advises:
(1) DPC has an Information Statement which was published on 23/1/12, when the Department's FOI unit was established. The statement was recently updated on 2/2/16.

Explore WA Government Data

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

Explore more