The Act’s operation turns on a handful of statutory concepts set out in the definitions (s 3) and the “relevant information” schedule (s 4). Understanding those concepts determines the boundaries of obligations and the channels through which compliance and enforcement proceed.

Applicable premises

• “Applicable premises” are premises intended, designed or used for overnight accommodation and that fall in the listed planning zones under a planning scheme (General Residential, Inner Residential, Low Density Residential, Rural Living, Environmental Living, Village, or Activity Area 1.0 Inner City Residential (Wapping)), or are prescribed or within a prescribed class (s 3(1), definition “applicable premises”). The definition expressly excludes premises that are “excluded premises” (s 3).

Excluded premises

• “Excluded premises” are hotels, motels or caravan parks (if constructed or renovated for that use), and those prescribed by regulation or in a prescribed class (s 3, definition “excluded premises”). That carve‑out channels the Act to non‑commercial short stay uses accommodated in residential zoning rather than a hotel/motel regulatory environment.

Booking platform and booking platform provider

• “Booking platform” is a system consisting of a software application and one or more websites that display multiple short stay premises and enable short stay booking service arrangements to be made (s 3, definition “booking platform”). The law describes a functional system of display plus transactional capability.
• “Booking platform provider” is a person who, on payment of a fee or other consideration by an owner/occupier or their agent, enables by means of a booking platform short stay customer arrangements to be made (s 3, definition “booking platform provider”). The focus is on the provider‑host commercial relationship: the provider receives consideration from the host (or agent) to enable customer arrangements.

Short stay premises, providers and arrangements

• “Short stay premises” are applicable premises for which an owner/occupier or their agent enters into, or seeks to enter into, a short stay booking service arrangement with a booking platform provider (s 3, definition “short stay premises”).
• “Short stay premises provider” includes owners or occupiers, and owners/occupiers whose agent seeks/enters into a short stay booking service arrangement (s 3).
• “Short stay booking service arrangement” is the contract under which the platform displays the premises for a fee (or other consideration) and makes arrangements between the provider and a customer (s 3).

Relevant information and required information

• The “relevant information” is the set of items defined at s 4: permit status (or statement that a permit is not required or that s 12 of LUPAA applies), address and number of bedrooms used for short stay, permit number if a permit exists, and whether the premises comprise all or part of the provider’s primary residence (s 4(a)-(d)).
• The “required information” for reporting to the Director is the information supplied by the provider or agent that is, or purports to be, the relevant information, together with the “relevant listing period” for which the information was displayed on the platform (s 7(2)).

Transition and timing

• A “transition period” runs from commencement to six months later (s 3). During this period s 5 and s 6 offences are not committed (s 5(3); s 6(4)). Arrangements in place before the end of the transition are taken, for the purposes of some obligations, to have been entered into the day after the transition ends (s 5(4); s 6(5)).

Use and confidentiality

• The Director may provide information to planning authorities, State Service officers/employees and contracted persons for “required purposes” , ensuring compliance with LUPAA and the Building Act 2016, analysis/consideration/determination of housing/short stay policy, other prescribed purposes, and report preparation (s 8(1)-(3)). The Act restricts making available or publishing the Director’s data in an identifying form (s 8(4)).

Regulation and administration

• The Governor may make regulations, including prescribing the form for information delivered to the Director (s 9(1)-(2)), and may authorise matters to be regulated by the Director or Minister (s 9(5)). Administration is assigned to the Minister for Planning and the Department of Justice until an Administrative Arrangements order changes that (s 10).

These concepts distribute roles and data flows. The Act treats the platform as the choke point for collection and reporting, defines a standardised dataset (s 4), and establishes a public aggregator (the Director) with a legally limited set of uses (s 7-8). The definitions are precise about the kinds of premises and platforms covered; their particular wording creates edge cases (for example platforms that do not charge owners, single‑listing services, off‑platform arrangements and prescribed classes) that affect the law’s reach and compliance choices.

The Act allocates duties and data flows across a small number of clearly identified actors and indirectly affects other public bodies that receive and use the data. Who pays, who decides and who changes behaviour are central to understanding the distribution of costs and the likely operational responses.

Primary affected parties

• Booking platform providers: Platforms that operate a software application and websites that display multiple short stay premises and enable short stay customer arrangements, and that receive a fee or other consideration from an owner/occupier or their agent, are directly regulated as booking platform providers (s 3, definitions “booking platform” and “booking platform provider”). They must not accept listings unless they have been provided the relevant information (s 5(1)), must display permit status and permit number (s 5(2)), must collect and file the provider’s information and the listing period, and must report that information quarterly to the Director (s 7(1)-(2)). They face fines for non‑compliance (s 5(1)-(2); s 7(1)).

• Short stay premises providers (hosts and owners/occupiers): Owners or occupiers who enter into, or seek to enter into, a short stay booking service arrangement are obliged to provide the relevant information to the platform or agent (s 6(1)). If they employ an agent, they must provide the agent with the information and instruct the agent to provide it to the platform (s 6(2)). It is an offence for a provider to give false or misleading information in a material particular (s 6(3)). Hosts therefore bear the compliance cost of obtaining and supplying permit documents, confirming zoning/permit status, indicating bedroom counts and primary residence status.

• Agents acting on behalf of hosts: Agents who enter into short stay booking service arrangements are implicated indirectly because principals must ensure agents have the information and are instructed to provide it (s 6(2)). Agents receiving provider information will be the vehicle through which platforms receive the relevant information; principals remain liable for failing to supply or for false information (s 6(2)-(3)).

Secondary and public sector recipients

• Director of Building Control: The Director is the central public recipient of the quarterly dataset (s 7(1)). The Director may provide that information to planning authorities and authorised State Service officers, employees or contracted persons for required purposes (s 8(1)-(3)). The Director also exercises practical control over how the data may be accessed and used, subject to the Act’s confidentiality limitation (s 8(4)).

• Planning authorities and State Service officers/employees: Planning authorities are explicitly named as permitted recipients for the required purposes, principally to assist compliance with the Land Use Planning and Approvals Act 1993 and the Building Act 2016, and for policy analysis (s 8(1)-(3)).

• Minister and Departmental administration: Until an Administrative Arrangements order changes responsibility, administration is assigned to the Minister for Planning and the Department of Justice, who therefore set operational priorities and resourcing for enforcement and data usage (s 10).

Indirectly affected parties and market effects

• Customers (guests): The Act requires platforms to display permit status and permit number where relevant (s 5(2)), so consumers will receive additional information about regulatory compliance of listings. That may affect demand patterns and consumer trust but the statute does not regulate pricing or consumer dispute resolution.

• Property owners not using platforms: The specific definition of “booking platform” and “booking platform provider” narrows the regulated channels to multi‑listing transactional platforms that receive consideration from hosts. Private off‑platform transactions and advertising via other electronic addresses not operated by the platform may fall outside the Act if not captured by the definitions. That creates a potential incentive for some providers to transact off‑platform to avoid reporting.

• Hotels, motels and caravan parks: These are excluded premises if constructed or renovated for that use (s 3, “excluded premises”), therefore the Act does not apply to their listings in the way it applies to residential short stay listings.

• Regulators and local government: Planning authorities will gain new data for compliance and enforcement. That creates resource implications for local authorities who may need to act on identified non‑compliance. The Act contemplates the Director providing data to contractors or persons acting pursuant to contracts with the Crown or planning authorities (s 8(1)), broadening the set of public‑facing actors with access to the dataset, subject to confidentiality constraints (s 8(4)).

Who pays and who decides

• Platforms will generally pay the compliance costs of system changes to collect, display and report the required information, and may pass those costs to hosts through higher fees or listing conditions. Hosts will pay the administrative cost of obtaining and providing the permit documentation and confirming primary residence status. The Director and planning authorities will incur costs associated with receiving, storing, analysing and enforcing based on the data, although the Act centralises collection to a single public office (s 7).

In short, the Act places compliance obligations primarily on booking platform providers and hosts, centralises data with the Director of Building Control for planning and policy use, and leaves hotels/motels/caravan parks outside the regime. The definitions create operational boundaries that will shape compliance choices and market responses.

The Act sets out explicit duties for booking platform providers, short stay premises providers (and their agents), and the Director of Building Control, and it defines limited rights concerning data use. The obligations operative on each actor are precise and trigger penalties for non‑performance.

Duties of booking platform providers

• Take no short stay booking service arrangement unless the short stay premises provider (or the agent) has provided, or purported to provide, the relevant information (s 5(1)). The statutory language “provided, or purported to provide” acknowledges receipt as the trigger rather than verification; it is an act‑based receipt duty.
• Ensure that public displays of listing information on their booking platform include the information in s 4(a) and s 4(c), that is, statements about permit status and the permit number where a permit exists (s 5(2)). The platform must feature this information in customer‑facing listings.
• Provide, within 30 days after the end of each financial quarter, the required information to the Director of Building Control for each short stay premises displayed during the quarter (s 7(1)). The required information includes the information provided by the host (or agent) and the relevant listing period (s 7(2)).
• Maintain compliance through the transition period rules: they are not guilty of offences under ss 5(1)-(2) for pre‑transition non‑compliance, and pre‑transition arrangements remaining in force after the transition are treated as entered into the day after the transition for compliance purposes (s 5(3)-(4)).

Duties of short stay premises providers (owners/occupiers)

• Do not enter into a short stay booking service arrangement unless the provider, or an agent, has provided to the booking platform provider the relevant information (s 6(1)). This is a precondition to entering the arrangement.
• If using an agent, provide the agent with the relevant information and instruct the agent to supply the information to the booking platform provider (s 6(2)). The principal remains specifically responsible for ensuring the agent has and passes on the information.
• Do not provide information that purports to be the relevant information if it is false or misleading in a material particular (s 6(3)). The statute makes material falsity by the host an offence.

Duties applicable to agents

• The principal must supply the agent with the relevant information and instruct the agent to provide it to the platform (s 6(2)). The Act makes the principal’s provision and instruction mandatory; it does not, in the text provided, impose separate statutory duties on agents besides being the actor who “enters into” agreements on behalf of owners (s 3, definition “short stay premises provider”).

Duties of the Director of Building Control and permitted users

• Receive the quarterly datasets from platforms (s 7(1)), and provide the data to planning authorities, State Service officers and employees or persons acting under contract with the Crown for required purposes (s 8(1)-(3)). The Director is required to limit use to the listed permitted purposes (s 8(2)).
• Not make publicly available or otherwise publish the data in a form that enables identification of individual premises or owners/occupiers (s 8(4)).

Rights and limits on use

• The Act gives planning authorities and authorised State Service officers an express right to receive the data and to use it for ensuring compliance with LUPAA and the Building Act 2016 and for housing policy analysis (s 8(1)-(3)). These are statutory rights to access the Director’s dataset for defined purposes.
• Conversely, the Act limits release and publication: persons who receive the data are under a statutory prohibition on making it available to others not authorised by s 8(2) and on publishing it in an identifying form (s 8(4)).

Regulation‑making and administrative rights

• The Governor may make regulations to specify form, timing and other operational requirements and may authorise the Director or Minister to determine matters from time to time (s 9(1)-(6)). This gives the executive branch delegated authority to refine reporting formats and operational detail.

Interaction with transition arrangements

• Parties have temporary reprieve during the six‑month transition period (s 3, definition and s 5(3); s 6(4)). Pre‑existing arrangements are accorded a specific legal fiction for post‑transition compliance (s 5(4); s 6(5)).

Verification and evidentiary posture

• The Act’s wording places the initial onus on receipt rather than external verification (booking platforms must ensure they have been provided the information or purported information (s 5(1))). However, the Act criminalises hosts who provide materially false or misleading information (s 6(3)). There is no express statutory duty on platforms to verify authenticity beyond receipt in the text supplied.

Taken together, the duties impose discrete regulatory steps: collection (host/agent), display (platform), and reporting (platform to Director). Rights are mainly limited to public authorities to use the dataset for planning and enforcement; public release of identifiable data is prohibited, preserving some confidentiality while enabling targeted regulatory action.

The Act attaches financial penalties to the principal offences and constrains use and disclosure of the collected data. Enforcement responsibility is concentrated in the Director and planning authorities, but the Act also provides for delegated detail by regulation.

Statutory penalties

• Booking platform breach of entry/collection obligations (s 5(1)): offence with a maximum fine not exceeding 100 penalty units, and for continuing offences an additional fine not exceeding 10 penalty units per day during which the offence continues (s 5(1)). The same penalty structure applies to the display obligation in s 5(2) (s 5(2) penalty).
• Short stay premises provider breach of provision obligations (s 6(1)-(2)): offence with a maximum fine not exceeding 50 penalty units (s 6(1)-(2) penalty).
• Materially false or misleading information provided by a short stay premises provider (s 6(3)): fine not exceeding 50 penalty units (s 6(3) penalty).
• Failure by platform to provide required information to the Director quarterly (s 7(1)): fine not exceeding 50 penalty units (s 7(1) penalty).
• Unauthorised disclosure or publication of information provided to the Director (s 8(4)): fine not exceeding 50 penalty units (s 8(4) penalty).

Operational enforcement architecture

• The Act designates the Director of Building Control as the recipient of platform reports and the source of data to planning authorities and authorised persons (s 7(1); s 8(1)). The Director’s role implies operational responsibility for receiving reports and directing them to planning authorities when required.
• Planning authorities and State Service officers are authorised to use the data only for the “required purposes” (s 8(2)-(3)). This frames enforcement as a coordinated exercise between the Director and planning authorities working under the statute’s purposes: assisting compliance with LUPAA and the Building Act 2016 and conducting housing policy analysis (s 8(3)(a)-(b)).

Continuing offences and time framing

• For booking platform offences under s 5, the Act contemplates continuing liability and daily fines for ongoing breaches (s 5(1)-(2)). The quarterly reporting cycle creates a recurring compliance obligation with discrete deadlines (s 7(1) , within 30 days after the end of each financial quarter).

Transition period relief

• During the transition period (six months after commencement), persons do not commit offences under s 5(1)-(2) or s 6 provisions if they fail to comply (s 5(3); s 6(4)). Pre‑existing arrangements are treated as entered the day after the transition for the purposes of those obligations (s 5(4); s 6(5)). The transition period delays enforcement to allow system and process changes.

Regulatory delegated offences

• The regulations may create additional offences and specify fines up to 50 penalty units (s 9(4)). This allows the executive to add offences that operationalise the statute and to set penalties for regulation breaches.

Evidence and prosecution considerations (inferred from statutory structure)

• The Act creates offence elements focused on acts and omissions (e.g., entering into an arrangement without receiving the relevant information; providing materially false information). Proof will therefore rely on documentary evidence of receipt, the content of information transmitted to platforms, platform displays, and the quarterly reports provided to the Director. The Act’s requirement that platforms forward the provider’s supplied information to the Director (s 7(2)(a)) produces an evidentiary trail for investigation and enforcement.

Use limits as an enforcement control

• The statutory restriction on use and publication of the Director’s data (s 8(4)) creates an enforcement offence for unauthorised disclosure by persons in possession of the data. That re‑allocates enforcement risk from public publication to controlled administrative use, while still enabling enforcement actions based on the data.

Resourcing and compliance risk

• Enforcement depends on the Director and planning authorities acting on the reported data. The statute centralises reporting but does not in the provided text allocate enforcement budgets or staff; those will be matters for administration under s 10 and regulation. The effectiveness of the penalty regime therefore depends on institutional resourcing to investigate, prosecute and act on non‑compliance.

In sum, the Act couples collection and display obligations with financial penalties and centralised reporting; enforcement capability will hinge on the Director and planning authorities operationalising the statutory powers and on delegated regulation to fill procedural gaps.

The Act is explicitly designed to operate alongside and to assist enforcement of several existing legal regimes; it references and derives meaning from other statutes. The interaction is both substantive , definitions and permit concepts rely on those statutes , and administrative , the Act supplies data to agencies enforcing the other laws.

Land Use Planning and Approvals Act 1993 (LUPAA)

• The Act depends on LUPAA in multiple ways. The definition of “applicable premises” relies on planning scheme zones defined under LUPAA (s 3, “applicable premises” list of zones). “Relevant permit” is a permit granted under LUPAA authorising the premises to be made available for short stay purposes (s 3, definition “relevant permit”). The “relevant information” requirement expressly includes a statement that either there is a relevant permit, that a permit is not required, or that the use is one to which s 12 of LUPAA applies (s 4(a)(i)-(iii)). The Act therefore uses LUPAA as the substantive standard for whether short stay use is authorised and, implicitly, how planning permission interacts with short stay activities.

Building Act 2016

• The Act references the Director of Building Control by adopting the definition from the Building Act 2016 (s 3, definition “Director of Building Control”). The Director is the statutory recipient of the platform reports (s 7(1)) and may provide the information to planning authorities and persons acting under contract for required purposes including ensuring compliance with the Building Act (s 8(3)(a)). The Building Act therefore is among the enforcement targets for which the dataset may be used.

Residential Tenancy Act 1997

• The Act excludes tenancy agreements from its coverage: “short stay customer arrangement” does not include a tenancy agreement or an arrangement where a person will use premises as primary residence (s 3, definition “short stay customer arrangement”). The definition of “tenancy agreement” refers to the Residential Tenancy Act 1997 (s 3). This frames the Act as aimed at transient short stays rather than longer‑term tenancies protected under the Residential Tenancy Act.

Administrative Arrangements Act 1990

• Administration of this Act is assigned to the Minister for Planning and the Department of Justice until an Administrative Arrangements order is made under s 4 of the Administrative Arrangements Act 1990 (s 10). That provision provides a temporary allocation of responsibility and indicates that the administrative custodian could change by order.

Interaction effects and operational dependencies

• Enforcement of LUPAA and the Building Act will be aided by the data flow mandated here (s 8(3)(a)). Planning authorities will be able to cross‑check listings against permits and planning rules based on the permit number and address data (s 4(b)-(c); s 7(2)). The Act does not itself re‑classify land uses or create planning permissions; it provides a reporting mechanism to identify potential non‑compliance with existing planning and building rules, deferring substantive enforcement to the existing regimes.

• The Act’s exclusion of tenancy agreements and of premises constructed as hotels/motels/caravan parks creates jurisdictional limits that prevent overlap with those specialised regulatory frameworks; it therefore complements rather than supplants those statutes (s 3 definitions).

Regulatory gap filling and delegated powers

• The regulations power (s 9) can identify further prescribed premises or classes (s 3 definitions allow prescription of classes of applicable or excluded premises) and can specify the form of information to the Director (s 9(2)). That allows the executive to harmonise the dataset with existing forms and permit numbering systems used under LUPAA and the Building Act.

Privacy, data protection and release constraints

• While the Act permits sharing with planning authorities and certain State officers for defined purposes (s 8(1)-(3)), it prohibits making available or publishing the data in an identifying form (s 8(4)). That creates a statutory data protection constraint that will need to be reconciled with other obligations on agencies to disclose information under freedom of information or similar laws. The Act, however, does not in the provided text override FOI or other disclosure laws; it simply imposes a statutory offence for unauthorised release by persons handling the Director’s dataset (s 8(4)).

Evidential and procedural cross‑use

• Because the platform must send the provider’s original supplied information to the Director (s 7(2)(a)), planning authorities will receive an evidential chain that shows what the host claimed on the platform and the listed permit identifier where applicable. That dovetails with LUPAA and Building Act processes for determining permit validity and alleged unauthorised use.

In sum, the Act is deliberately designed to feed data into the planning and building regulatory ecosystem, relying on LUPAA and the Building Act for substantive regulation and enforcement while carving out tenancy law and hotel regulatory regimes. The regulations power allows further alignment; practical interaction will depend on later regulations and administrative coordination under s 10.

The text provided is the Act as enacted, with a commencement clause and a defined transition period. The Act’s internal provisions do not record any subsequent amendments or historical variations within the supplied document.

Key timing provisions in the Act itself

• Commencement: This Act commences on the day it receives Royal Assent (s 2). There is no staged commencement schedule in the supplied text beyond the commencement date.
• Transition period: The Act defines a six‑month “transition period” beginning on commencement and ending six months later (s 3, definition “transition period”). During the transition period, specified offences in ss 5 and 6 are not committed (s 5(3); s 6(4)), and pre‑existing arrangements are treated as entered into the day after the transition for compliance purposes (s 5(4); s 6(5)).

Regulatory amendment pathway

• The Act provides for the Governor to make regulations (s 9), including forms for reporting, differential application, and additional offences and penalties. This gives the executive branch an authorised pathway for operational amendment and detail without primary legislation. The regulations may also provide savings and transitional matters (s 9(6)(a)-(b)) and may transfer matters to the Minister or Director to determine from time to time (s 9(5)). As a result, much of the practical evolution of the regime will likely occur by regulation rather than by amending the principal Act.

Administration until Administrative Arrangements change

• Administration is allocated to the Minister for Planning and the Department of Justice pending any order under the Administrative Arrangements Act 1990 (s 10). That administrative assignment may change by order, without primary amendment.

Absence of recorded amendments or case notes in the supplied text

• The supplied text contains no schedule of amendments, amending acts, or indications of repeal or saving beyond what is already in the grammar of the statute. No amendment history is recorded in the text supplied.

For practitioners needing a formal historical record (statutory amendments, subordinate instrument changes, or commencement variations) the next step is to consult the official legislative database or parliamentary records to obtain consolidated versions and subordinate instruments made under s 9. The Act itself anticipates that regulations will specify or vary procedural matters and create delegated detail (s 9(2), s 9(5)), so the practical operation will likely become clearer through subordinate instruments and administrative guidance rather than through primary Act amendment.

The supplied Act text contains no references to litigation, court decisions, or judicial interpretations. There are no schedules, transitional judicial orders, or declaratory provisions tied to any case law in the document provided.

Implications for legal uncertainty

• Because there is no litigation history set out in the provided text, the statutory phrases remain untested in the courts as far as the supplied material shows. Key interpretive points that could give rise to litigation include: the meaning and scope of “booking platform provider” (the Act ties the definition to receipt of consideration from an owner or agent and to a platform displaying multiple premises); the boundary between “applicable premises” and “excluded premises” where regulations may prescribe additional classes; the meaning of “material particular” in the offence for false or misleading information (s 6(3)); and the limits of the Director’s permitted disclosure (s 8(4)).

Administrative and regulatory litigation pathways

• If disputes arise, likely avenues of legal challenge would include judicial review of administrative decision‑making by the Director or planning authorities acting on the dataset, and civil enforcement or crime prosecutions for alleged contraventions (s 5, s 6, s 7, s 8). Challenges could also arise under privacy, administrative law, or statutory interpretation principles where the Director or a planning authority seeks to use the data beyond the “required purposes” identified in s 8(3).

Precaution for practitioners

• In the absence of any judicial construction, careful contract drafting, clear record keeping, and conservative compliance approaches will reduce exposure to enforcement or litigation risk. Platforms and hosts should document receipt and display of the relevant information, maintain copies of permits and the dates of listing, and implement data governance consistent with s 8(4)’s prohibition on identifiable publication.

If and when case law develops, it will likely focus on the Act’s definitions, the factual matrix for “material particular” falsity, verification duties for platforms, and the permissible scope of the Director’s data use. For now, litigation history is blank in the text provided; operational clarity will emerge primarily from regulations and administrative guidance rather than from court precedent initially.

The Act’s text creates a number of operationally significant edge cases and potential pitfalls that practitioners should be aware of. These are mechanistic effects of the statutory language rather than policy judgments; they affect who is regulated, what must be collected, what may be published and how enforcement will proceed.

1. Definitions create narrow but consequential coverage boundaries

• “Booking platform provider” requires that the provider receives a fee or other consideration from the owner/occupier or agent (s 3). Platforms that never take fees from hosts but instead earn revenue from customers or advertisers may fall outside this definition depending on whether their business model constitutes “other consideration.” The precise classification of consideration is therefore material.
• “Booking platform” requires the display to the public of multiple short stay premises (s 3). Single‑listing software or directories that list a single property might not meet this threshold; practitioners should not assume every online listing falls within the statute.
• “Short stay booking service arrangement” excludes arrangements made by means of another website or electronic address that is not operated or maintained by the booking platform provider (s 3). Hosts choosing to transact using social media, private messaging or non‑platform channels may avoid the platform obligations, though they remain subject to planning and building laws.

2. “Provided, or purported to provide” imprecision

• The booking platform’s duty to accept listings only if the host has “provided, or purported to provide” the relevant information (s 5(1)) uses language that treats receipt as the legal trigger. That limits the platform’s statutory duty to collection rather than verification. Platforms could face enforcement exposure for accepting listings without receipt, but the host carries criminal liability for providing false information (s 6(3)). Platforms therefore have an incentive to require documentation, but the Act does not itself require authentication.

3. Display obligations only require certain items

• Platforms must display s 4(a) and (c) (permit status and permit number where applicable) publicly (s 5(2)). The address and bedroom count (s 4(b)) and primary residence status (s 4(d)) are part of the “relevant information” (s 4) and must be provided to the platform by the host (s 6(1)), but s 5(2) does not explicitly require public display of all those fields. Platforms must therefore store them and report them to the Director (s 7(2)) but may not have to display them to customers unless regulations change that.

4. Reporting vs public disclosure distinction

• Platforms must report the host‑supplied information and the listing period to the Director each quarter (s 7(1)-(2)). The Act forbids making the Director’s data available in an identifying form to parties not authorised by s 8(2) and forbids publication in an identifying form (s 8(4)). That protects hosts from public exposure via the Director’s dataset, but it does not prevent platforms themselves from publishing identifying information on their own websites (the Act requires only certain display elements and does not restrict platforms from displaying other identifying data).

5. Transition period mechanics

• No offence is committed under ss 5 or 6 for failures occurring before the end of the six‑month transition period (s 5(3); s 6(4)). However, arrangements entered into before the transition that remain in force after the transition are taken to have been entered the day after the transition is over for purposes of ss 5 and 6 (s 5(4); s 6(5)). That legal fiction can create a compliance trap if platforms or hosts fail to update records: pre‑existing listings may be retrospectively treated as fresh for compliance, imposing immediate obligations after the transition.

6. Authority to prescribe classes and forms

• Regulations may prescribe classes of premises as applicable or excluded, and may specify forms for reporting (s 3 definitions; s 9(2)). The absence of prescribed forms at commencement (until regulations are made) creates uncertainty about the required format for quarterly data; platforms should monitor the regulations for prescribed schemas. s 9(5) allows the Director or Minister to determine matters from time to time, so administrative determinations may create operational expectations beyond the Act.

7. Agents and principal liability

• Principals must provide information to agents and instruct them to pass it to the platform (s 6(2)). The principal remains liable for failing to provide or for false information (s 6(3)), so hosts cannot avoid responsibility by delegating. However, the Act does not impose a separate offence on agents for acting on false information in the text supplied; enforcement priorities may therefore focus on hosts and platforms.

8. Potential for off‑platform substitution

• Because the Act applies to specified “booking platform providers,” hosts may attempt to avoid obligations by advertising and transacting outside regulated platforms (private bookings, social media, direct websites not operated by a platform provider). The statutory coverage depends on the definitions (s 3) and any prescribed classes under regulation, so such substitution is a foreseeable compliance strategy.

9. Ambiguity about “material particular”

• The offence in s 6(3) criminalises providing information that “purports to be the relevant information” if it is “false or misleading in a material particular.” The Act does not define “material particular,” leaving scope for prosecutorial and judicial interpretation about what errors are material versus trivial (e.g., number of rooms versus deliberate claim of a permit).

10. Data governance and confidentiality

• The Act prohibits publication of the Director’s dataset in an identifying form (s 8(4)) but does not prevent analysis and aggregated reporting (s 8(3)(b)-(d)). Platforms passing raw host data to the Director must therefore anticipate the Director’s data management arrangements and ensure they meet data protection obligations, even though the Act restricts certain public disclosures.

Practitioners need to map these “gotchas” against their business models and operational flows: platforms should audit whether they fall within the definition, hosts should check permit status and bedroom counts, and local authorities should plan for the administrative load of acting on the incoming data. The regulatory and administrative detail that follows in regulations and administrative guidance will be critical to resolving several of these edge cases.

Compliance requires coordinated steps across hosts, agents, booking platforms and the Director’s office. The Act defines what must be done, and the regulations (once made) will set forms and possibly additional steps. The following checklist is a source‑grounded operational roadmap mapped to specific provisions.

For booking platform providers

1. Legal classification check

   • Confirm whether the platform fits the statutory definition of “booking platform” and whether the business model meets “booking platform provider” (s 3). Key questions: do you display multiple short stay premises publicly, do you enable customer arrangements by means of your platform, and do you receive a fee or other consideration from owners/occupiers or their agents?

2. Intake controls and contractual terms

   • Implement mandatory data fields in host intake/host dashboards to capture the “relevant information” (s 4): permit status or statement that permit not required or that LUPAA s 12 applies (s 4(a)), address and number of bedrooms used for short stay (s 4(b)), permit number where relevant (s 4(c)), and whether premises are all or part of the host’s primary residence (s 4(d)).
   • Contractually require hosts/agents to provide the relevant information before acceptance, and retain evidence of receipt (s 5(1); s 6(1)-(2)).

3. Public display

   • Ensure listing pages display at least s 4(a) and s 4(c) (permit status statement and permit number where relevant) as required by s 5(2). Consider design elements that make this information visible to customers.

4. Verification and risk management

   • Decide on a verification policy. The statute creates an offence for hosts providing materially false information (s 6(3)), but the platform’s statutory trigger is receipt (s 5(1)). For risk reduction, require upload of permit documents, implement automated validation where possible, and maintain records of receipt and timestamps.

5. Quarterly reporting pipeline

   • Establish data export processes to transmit the “required information” to the Director within 30 days after the end of each financial quarter (s 7(1)). The required information comprises the information provided by the host/agent as the relevant information and the relevant listing period (s 7(2)). Implement record retention to support audits and prosecutions.

6. Privacy and data handling

   • Align internal data governance with s 8(4): while the Director controls publication constraints, platforms must manage host data responsibly and be prepared to provide the Director’s dataset in whatever prescribed form the regulations may specify (s 9(2)). Anticipate regulatory data format requirements and secure transmission channels.

7. Transition period planning

   • Use the six‑month transition to upgrade systems and processes (s 3 definition; s 5(3)). Identify listings entered before the end of the transition and ensure they meet the condition that they will be treated as entered the day after transition for compliance (s 5(4)).

For short stay premises providers (hosts) and agents

1. Determine applicability

   • Confirm whether premises are “applicable premises” (s 3) by reference to planning zone, and whether premises are “excluded premises” (s 3). If a relevant permit is required under LUPAA, obtain and retain it.

2. Collect and supply the relevant information

   • Before entering into a short stay booking service arrangement with a platform, provide the platform (or an agent) with the full set of relevant information (s 4), and if using an agent, provide the agent with the information and instruct the agent to provide it to the platform (s 6(1)-(2)). Keep copies of the permit and of the instruction to the agent to demonstrate compliance.

3. Avoid materially false statements

   • Ensure all information provided is accurate. The Act penalises material falsity (s 6(3)). Implement internal checks on bedroom counts and primary residence status, and maintain dated records or copies of permit documents.

4. Consider off‑platform options and risks

   • Recognise that private transactions off major platforms may fall outside the Act’s scope depending on definitions (s 3). However, LUPAA and the Building Act still apply , the Act does not absolve hosts from substantive planning or building law compliance.

For the Director of Building Control and planning authorities

1. Prepare to receive datasets

   • Put in place secure submission channels and database structures to accept required information within the statutory timetable (s 7(1)). Anticipate that the regulations may specify form and schema (s 9(2)).

2. Define internal processes for permitted use

   • Establish policies and procedures for using the data only for the “required purposes” listed at s 8(3): ensuring compliance with LUPAA and the Building Act, housing policy analysis, other prescribed purposes, and report preparation. Document access controls consistent with s 8(4).

3. Inter‑agency workflows

   • Coordinate with planning authorities and authorised contractors on how data will be triaged and acted upon. The Act allows the Director to provide the data to planning authorities and authorised persons for required purposes (s 8(1)).

Cross‑cutting steps and practical checklist

• Monitor regulations: s 9(2) empowers regulations to prescribe the form of reports; stay attuned to subordinate instruments.
• Record keeping: maintain dated copies of all documents supplied and received, including permits and intake forms, to establish compliance and defend against allegations of false information.
• Update terms of service: platforms should update host terms and agent agreements to reflect the statutory obligations and to allocate responsibilities for providing accurate information.
• Staff training: ensure customer support and listing moderation staff understand the information fields required and the statutory deadlines for quarterly reporting.
• Technical readiness: build a reporting export that includes the host‑supplied information and the listing period and that meets security and retention policies aligned with the Director’s requirements.
• Transition deadline calendar: set internal milestones to complete system changes within the six‑month transition period (s 3 definition), and reconcile lists of pre‑transition arrangements that will be treated as entered the day after the transition ends (s 5(4); s 6(5)).

Regulatory anticipations

• The Act vests the Governor with regulation‑making power and allows the Director or Minister to make determinations under delegated authority (s 9). Practitioners should plan for additional compliance elements to be specified by regulation and for operational guidance from the administering department (s 10).

Careful adherence to intake, display, reporting and record‑keeping obligations will materially reduce enforcement risk under the Act. The key operational dependencies are capturing the s 4 fields accurately at listing intake, displaying s 4(a) and (c) on listing pages, reporting the dataset quarterly to the Director (s 7), and protecting the data from unauthorised public disclosure consistent with s 8(4).