25.12.2014 Views

KI Traveller's Levy Economic Impact Assessment - Kangaroo Island ...

KI Traveller's Levy Economic Impact Assessment - Kangaroo Island ...

KI Traveller's Levy Economic Impact Assessment - Kangaroo Island ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Commercial-in-Confidence<br />

<strong>KI</strong> Traveller’s <strong>Levy</strong><br />

<strong>Impact</strong> <strong>Assessment</strong><br />

APPENDIX C: KEY CONSULTATION DISCUSSION POINTS 13<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Do you think the <strong>KI</strong> circumstances warrant introduction of a modest (perhaps $5 to<br />

$10) Traveller’s <strong>Levy</strong> as a means of ensuring the <strong>Island</strong>’s infrastructure (particularly<br />

roads) is adequately maintained<br />

What impact do you think a Traveller’s <strong>Levy</strong> would have on tourism visitation and<br />

expenditure<br />

What flow-on impacts do you think would stem from the introduction of a Traveller’s<br />

<strong>Levy</strong> on <strong>KI</strong><br />

Given a significant proportion of exiting visitors identify the condition of local roads as a<br />

major drawback (reason for not returning/recommending to others), do you believe<br />

there is a likelihood that a Traveller’s <strong>Levy</strong> coupled with improved maintenance of<br />

roads may actually increase tourism activity<br />

Have other experiences (past fee/price increases or fuel levies, for example) provided<br />

indicative evidence of how tourists might respond to a <strong>Levy</strong><br />

If a Traveller’s <strong>Levy</strong> was imposed what do you see as the most effective (and costeffective)<br />

way to collect and administer it<br />

Would it be feasible to, and what issues would arise in, attaching a Traveller’s <strong>Levy</strong> to<br />

your existing pricing structure (Setting aside any legal barriers for the time being).<br />

Given your current pricing structure, would a per-vehicle or per-passenger <strong>Levy</strong> be<br />

more/less feasible to administer<br />

If residents had a clear form of identification (a resident card or unique resident number<br />

to use in bookings), how additionally onerous would it be to exclude residents from a<br />

<strong>Levy</strong><br />

If you have introduced levies (such as fuel levies) in the past, what were the costs of<br />

updating booking systems/websites, etc, to reflect the new levy<br />

What lead time do you think would be required to introduce a <strong>Levy</strong> into your booking<br />

systems<br />

Do you have any opinion as to the likely costs of collection/administration of a<br />

Traveller’s <strong>Levy</strong> Would you wish to receive a fee for its collection<br />

How do you think the introduction of a <strong>Levy</strong> would impact on the competitiveness of <strong>KI</strong><br />

as a tourism destination relative to other destinations and for economic activity<br />

generally<br />

Given road maintenance costs are a major driver behind the need to consider a <strong>Levy</strong><br />

would you consider a vehicle levy as an alternative to a per-passenger Traveller’s<br />

<strong>Levy</strong><br />

Rather than applying a levy would a better approach be for <strong>KI</strong> to receive greater State<br />

Government road funding support (or alternatively for the State to assume<br />

responsibility for some of the key roads)<br />

Are there any allowances / block grants from the State Government to <strong>KI</strong> How does<br />

State govt revenue raised from <strong>KI</strong> compare with State govt services provided to <strong>KI</strong><br />

13 Not all points of discussion were raised with all stakeholders – some were specific to certain groups.<br />

45

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!