Telecommunications (Property Access and Other Matters) Amendment Bill
About this bill
This bill is intended to reduce compliance costs for Telecommunications Development Levy payers by addressing identified issues with the liability allocation process; reduce the time taken to obtain the consent of all parties with an interest in the property a fibre connection needs to occupy; and extend the regulatory requirements relating to the Ultra-Fast Broadband programme to the extension of that programme.
Current status
Royal Assent given 18 April 2017.
Enacted as the Telecommunications (Property Access and Other Matters) Amendment Act 2017 (2017/16)
Member of Parliament responsible
Bill type
Government bill
All data
| Bill type | Government bill |
|---|---|
| Parliament | 51 |
| Ref | 146-3 |
| Introduced | 29 June 2016 |
| First reading | 5 July 2016 |
| Select Committee | Commerce Committee |
| Public submissions due | 10 November 2016 |
| Select Committee report back | 13 December 2016 |
| Second reading | 15 February 2017 |
| Committee of the whole House | 4 April 2017 |
| Third reading | 11 April 2017 |
| Royal Assent | 18 April 2017 |
| Enacted as | Telecommunications (Property Access and Other Matters) Amendment Act 2017 (2017/16) |
| Divided | No |
Where are the votes?
WhereTheyStand doesn't have any records of votes for this bill — even though they would have occurred for the bill to have advanced to its present state. You can read about why this might be the case here.
About this page
Information about this bill was last retrieved from the Parliament website on Tuesday, 01 September 2020 at 18:23 (Office of the Clerk). Licenced by the Clerk of the House of Representatives for re-use under the Creative Commons Attribution 4.0 International licence. The full licence is available here.
Records of votes are part of Parliamentary debates (Hansard) and are not covered by copyright.
This information has been scraped from the Parliament website, and its accuracy depends on the Parliament site being consistently formatted. Sometimes things change, which might result in information being interpreted incorrectly or not at all. If that's the case, you can submit a correction request.
You can view a JSON representation of this page by adding the query string json=1 to the URL.