Hon. Ken Travers questions the Minister for Transport regarding the printing and release of the Western Australian Bicycle Network Plan 2014-2031, specifically discrepancies in previous answers about its printing history. The Minister acknowledges an error in previous advice.

AnsweredQoN 1135Legislative Council
Asked
15 October 2014
Portfolio
Transport

QuestionView source ↗

BICYCLE
NETWORK PLAN — PUBLICATION
1135. Hon KEN TRAVERS to the
parliamentary secretary representing the Minister for Transport:
I refer to question without notice 323 in relation to the ''Western
Australian Bicycle Network Plan 2014–2031'', and the answer
received.
(1) On or before 28 February 2014, had the department ordered
the printing of any version of the plan?
(2) If yes to (1) —
(a) on what date was the plan
printed;
(b) how many copies of the plan
were printed;
(c) what was the total cost of the
printing, inclusive of GST; and
(d) was the plan distributed to
the public; and, if not, why not?
(3) If the
department ordered the printing of the plan on or before 28 February 2014 that
was different from the plan subsequently released to the public on Saturday, 29
March 2014, can the parliamentary secretary explain —
(a) why the answer to (3) in
question without notice 323 was ''No''; and
(b) why the answer to (4) in
question without notice 323 was ''Not applicable''?

AnswerView source ↗

I thank the honourable member for some
notice of the question.
(1) Yes.
(2) On 26
November 2013, 100 copies of the ''Western Australian Bicycle Network
Plan'' were printed at a cost of $2 398, ready for the launch on a date
to be determined by the government. The plan was subsequently updated to
include the new Minister for Transport's details, due to the change in
minister.
(3) The
Department of Transport apologises for its error in providing incorrect advice
to the parliamentary secretary. The only difference was the update to include
the new Minister for Transport's details.

Explore WA Government Data

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

Explore more