A WA parliamentary question on notice requests a detailed breakdown of correspondence received by the Minister for Tourism's office over a 12-month period, including acknowledgment and response details. The Minister declined to answer, citing unreasonable resource allocation.

AnsweredQoN 1417Legislative Council
Asked
17 November 2009
Portfolio
Tourism

QuestionView source ↗

(1) How many pieces of correspondence relating to the Tourism portfolio, were received by the Minister’s office in the following months, -
(a) October 2008;
(b) November 2008;
(c) December 2008;
(d) January 2009;
(e) February 2009;
(f) March 2009;
(g) April 2009;
(h) May 2009;
(i) June 2009;
(j) July 2009;
(k) August 2009; and
(l) September 2009?
(2) Of those, for each of the months above, -
(a) how many have been acknowledged;
(b) how many have been responded to by the Minister;
(c) how many have been responded to by a ministerial staff member;
(d) how many have been responded to by an Agency employee; and
(e) how many are outstanding?

AnswerView source ↗

Answered
2 March 2010
Responded by
Minister for Environment representing the Minister for Tourism
Response time
105 days
(1)(a) - (1)(l)
The total number of correspondence received by my office, on matters relating to my Tourism Portfolio from 1 October 2008 - 30 September 2009 was 1480.
(2)(a) - (2)(e)
As per precedent set by the previous government's response to questions, such as LAPQ3026, which seek significant volumes of information, the member is informed that in relation to her questions above, that to develop a response would require an unreasonable allocation of Government resources to source and collate all information requested.
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