Transport (Compliance and Miscellaneous) (Vehicle Sharing Schemes) Regulations 2026

The Regulations develop a tightly specified regulatory model for shared personal mobility devices in the “category A” class. Key legal concepts and definitions are taken from or cross-referenced to existing transport and road safety statutes and instruments: terms such as alcohol interlock condition, behaviour change program and driver licence are defined by the Road Safety Act 1986 and are imported by reference in reg 4. The Road Rules are expressly incorporated as a source document (reg 4 and reg 6(2)).

Category A standards. Regulation 5 prescribes the standards and requirements in Part 2 as the “category A standards” for the Act’s definition of that term (reg 5). That makes the Part 2 rules the baseline technical and operational regime that approved category A scheme operators must meet.

Equipment and conspicuity. Reg 6(1)(a)-(f) requires minimum physical equipment: at least one effective brake, a bell/horn, white front and red rear lighting with minimum visibility distances (200 metres), a red reflector visible at 50 metres under low beam, a helmet lock, and the vehicle must be able to stand upright by itself. Reg 6(1)(j)-(l) mandates on-vehicle identification that includes a unique visible ID number visible at five metres, clear identification of the approved operator, and contact information including a telephone number.

Helmet regime. The Regulations combine hardware, detection and software lockouts. Reg 6(1)(g)-(h) requires helmet-detection ability and a prohibition on making the vehicle available for hire unless an approved bicycle helmet is attached. Reg 6(1)(m)(ii) and (iii) then require software/hardware features that prevent hire unless a helmet is attached, and that prevent the vehicle from being ridden unless the helmet is detached or the operator can verify the hirer is wearing their own helmet. That establishes a two-stage control: attachment to permit hire, detachment/verification to permit riding.

Telematics and active interventions. Reg 6(1)(m)(v)-(vi) requires geolocation capabilities that allow alerts, actions or restrictions based on location and prescribes a graduated set of interventions when a vehicle is detected outside the municipal district where it may be hired: audio alert, slow the vehicle, stop the vehicle and prevent ending the hiring. For metropolitan Melbourne reg 6(4) adds footpath detection and similar graduated interventions, plus the ability to determine post-hire parking location and to prevent ending hire outside a specified area (reg 6(4)(a)-(d) and reg 9).

Safety standards for electric scooters. Reg 6(3) requires electric scooters to comply with at least one of several named standards (AS/NZS 60335.2.114:2023, BS EN 17128:2020, ANSI/CAN/UL 2272:2016 or 2024), and batteries must meet one of two UL standards (ANSI/CAN/UL/ULC 2271:2018 or 2023). The Explanatory Details provide the incorporated matter table listing the applied standards (Endnotes, Table of Applied, Adopted or Incorporated Matter).

Behavioural gatekeeping. Reg 7 imposes cognitive reaction testing at set hours with software-enforced lockouts; reg 8 requires explicit drug and alcohol messaging before hire and a software confirmation that the hirer has read the material and is fit to ride. These provisions make the hiring software the locus for behavioural compliance before access is granted.

Maintenance and insurance. Reg 10 requires a maintenance plan for inspection, servicing and maintenance of operational capability. Reg 11 requires the scheme to include operator insurance (minimum A$20m) and rider insurance for riders aged 16 and over (minimum A$1m), with the rider cover required irrespective of whether the rider is found guilty of offences under the Road Safety Act or the Road Rules.

Spatial and administrative framework. Several provisions reference external administrative instruments. Reg 6(1)(m)(vi) speaks of municipal districts where a vehicle “may be hired in accordance with an authorising agreement”; metropolitan Melbourne is defined by reference to the Planning and Environment Act 1987 (reg 4). The Regulations therefore sit alongside authorising agreements and the Act’s approval processes rather than replacing them.

In short, the main concepts are: (1) defined category A standards applying to vehicles and operators; (2) a combined hardware/software approach to ensure helmet use, visibility and geofencing; (3) software-based pre-hire behavioural controls; (4) mandated electrical/battery safety standards for scooters; and (5) minimum insurance and maintenance obligations. Each of these concepts is stated as a legal requirement in the text (see regs 5-11).

The primary legal addressee is the “approved category A scheme operator”. The Regulations repeatedly use that term (for example regs 6(1)(k), 6(1)(m)(iv), 6(1)(m)(vi) and reg 9) and place technical, operational and insurance obligations on the operator. The operator will therefore be the entity that purchases, configures and maintains vehicles, develops and maintains the hiring software, procures the mandated insurance, and ensures compliance with the lighting, detection and telematics requirements.

Riders are affected directly by behavioural controls. The Regulations change access and riding conditions for users by requiring helmet presence to permit hire (reg 6(1)(g)-(h)), restricting riding unless the helmet is detached or verified (reg 6(1)(m)(iii)), imposing a cognitive reaction test during certain hours with potential lockouts (reg 7), and requiring riders to confirm they have read drug and alcohol messaging and that they are fit to ride before the hire is permitted (reg 8). Riders aged 16 and older benefit (or receive cover) under the mandatory rider insurance the scheme must include (reg 11(1)(b)). The Regulations do not specify minimum rider age; they do, however, limit the rider insurance application to riders at least 16 years of age (reg 11(1)(b)).

Suppliers and manufacturers are indirectly affected through the technical standards. Operators sourcing electric scooters must ensure devices comply with one of the listed standards for electrical systems and batteries (reg 6(3) and endnotes). This will affect procurement specifications, product testing and certification documentation that manufacturers and importers must supply to operators.

Local government and planning authorities are implicated because the Regulations use municipal districts and define metropolitan Melbourne by reference to the Planning and Environment Act 1987 (reg 4 and reg 6(1)(m)(vi)). The authorising agreements referenced in reg 6(1)(m)(vi) will determine the municipal districts in which vehicles may be hired; those agreements and any local conditions will influence where operator geofencing and no-end-hire zones must be configured.

Insurance markets and underwriters are affected through the minimum limits imposed on operator and rider cover (reg 11(2)-(3)). Operators will need to obtain and maintain the required policies and produce evidence of cover as part of compliance with the scheme requirements.

Regulators and enforcement agencies under the Act will have to develop audit, inspection and compliance procedures to verify that operators meet equipment, software, maintenance and insurance requirements. The Regulations do not specify the enforcement modalities; regulation 2 notes the Regulations were made under sections 207O and 256 of the Act, so enforcement will operate alongside existing enforcement powers under the Act and any authorising agreements.

Finally, smaller or new entrant operators face specific commercial impacts. The Regulations create a set of upfront and ongoing obligations,hardware meeting visibility and electrical standards, helmet systems and locks, geofencing and braking intervention capabilities, cognitive-testing and messaging software, maintenance regimes and high-limit insurance,that will affect cost structures and operational models. The Regulations will therefore influence market entry decisions and competitive positioning for providers of shared bicycles and electric scooters.

Duties placed on approved category A scheme operators

• Ensure each vehicle has required safety equipment and markings. Reg 6(1)(a)-(f) and (j)-(l) require at least one effective brake, a bell or horn, white front and red rear lights that are permanently or automatically activated in low light and visible at least 200 metres, a rear red reflector visible at least 50 metres under low-beam, a helmet lock, the ability to detect an approved bicycle helmet attached to the vehicle, and a unique identification number visible for 5 metres. Operators must display clear identification and contact information on each vehicle (reg 6(1)(k)-(l)).
• Ensure helmet controls operate. Operators must ensure vehicles are only made available for hire when an approved helmet is attached (reg 6(1)(g)-(h)) and implement technological measures that prevent hiring unless a helmet is attached and prevent riding unless the helmet has been detached or the operator verifies the hirer is wearing their own approved helmet (reg 6(1)(m)(ii)-(iii)).
• Provide software features for rider interaction and enforcement. Operators must provide audio alerts or instructions, fall-over detection and alerts, geolocation-based alerts, actions and restrictions, and graduated measures if vehicles are outside authorised municipal districts (audio alert, slow, stop, prevent end-hire) (reg 6(1)(m)(i), (iv)-(vi); reg 6(4)(a)-(c) for metropolitan Melbourne).
• Implement cognitive reaction testing in the hiring application and apply lockout periods after failures, including a minimum four hour lockout after two failed attempts (reg 7).
• Present drug and alcohol messaging and require hirer confirmation of understanding and fitness to ride before hiring (reg 8).
• Adopt a maintenance plan describing inspection and servicing schedules and how operational capabilities are maintained (reg 10).
• Maintain insurance. The scheme must include operator liability insurance of at least A$20,000,000 (reg 11(2)) and rider liability insurance of at least A$1,000,000 for riders aged 16 and above, with the rider cover to apply irrespective of whether the rider is found guilty of relevant offences (reg 11(1)(b)-(3)).

Rights and administrative positions

• The Regulations identify the operator as the decision-maker for several functions. For example, reg 6(1)(m)(iii)(B) allows the operator to “verify” a hirer’s own helmet, which places a right or discretion on the operator to decide what verification method to use and whether verification has succeeded. The Regulations do not prescribe the verification mechanism.
• The operator has the right and duty to configure geofencing and to use the vehicle’s technological features to prevent hires ending outside specified areas (reg 6(1)(m)(vi)(D) and reg 6(4)(d)). Operators decide the boundaries consistent with authorising agreements referenced in the Regulations.
• The Regulations do not confer any express private right on riders beyond the compulsory rider insurance requirement in reg 11(1)(b). That provision requires the scheme to include rider insurance irrespective of guilt for relevant offences; this is framed as a scheme obligation and therefore creates an entitlement for insured riders, subject to policy terms and applicable insurance law.

Operational consequences for behaviour and operation

• Hiring access depends on software-mediated checks. Reg 7 and reg 8 make hire conditional on passing cognitive tests at certain times and confirming drug/alcohol messaging content. Reg 6(1)(m)(ii)-(iii) conditions hire and riding on helmet presence/detachment or operator verification. Thus, the software is an access gatekeeper; operators must design onboarding, identity and helmet-verification flows to effect those duties.
• Vehicles must be capable of being slowed and stopped remotely under the prescribed conditions (reg 6(1)(m)(vi)(A)-(C) and reg 6(4)(b)-(c) for metropolitan Melbourne). Operators therefore have a duty to implement reliable remote control and fail-safe measures consistent with safety and the minimum functionality the Regulations require.

What the Regulations do not specify

• The Regulations do not set out specific enforcement mechanisms or penalties within their text. They are made under ss 207O and 256 of the Act (reg 2), so compliance oversight, penalties and revocation or suspension of approvals are matters that will arise under the Act or in authorising agreements. The Regulations do not specify the procedures for submission or approval of maintenance plans, the form or evidentiary standard for demonstrating insurance cover, nor minimum standards for helmet locks or helmet verification systems beyond the functional descriptions in reg 6.

In summary, the Regulations impose detailed operational, technical and insurance duties on approved category A scheme operators, give operators the practical discretion to implement verification, geofencing and intervention systems, and vest the hiring software with gatekeeping functions. The Regulations create entitlements for riders in the form of mandatory insurance cover for those aged 16 and above, but do not specify enforcement pathways or precise verification technologies.

The Regulations themselves do not include express penalty clauses or a standalone enforcement scheme within their text. They are made under sections 207O and 256 of the Transport (Compliance and Miscellaneous) Act 1983 (reg 2), and the objective in reg 1 describes the Regulations as prescribing matters for the purposes of Part VIA of that Act. Enforcement, penalties, approvals and compliance measures therefore fall to be located within the Act, Part VIA, and any authorising agreements that govern where and how category A vehicles may be hired. The Regulations define substantive duties but leave the Act and authorising agreements to provide enforcement mechanisms.

What the Regulations require for verification and evidence

• Insurance: reg 11 requires minimum insurance limits , A$20,000,000 operator liability and A$1,000,000 rider liability (reg 11(2)-(3)) , and reg 11(1) requires the scheme include these insurances. In practice, demonstrating compliance will require the operator to hold the policies and be able to produce certificates of currency and policy documents to the regulator. The Regulations do not prescribe the documentation format or the frequency of renewal verification.
• Maintenance plan: reg 10 requires a maintenance plan setting out inspection and servicing routines and how operational capabilities are maintained. Regulators will need such plans to be submitted, accepted and audited. The Regulations do not set mandatory contents beyond the functional requirement; the regulator will need to determine what suffices.
• Software logs and telematics: the operational requirements for helmet detection, cognitive tests, geofencing, fall detection, parking determination and graduated interventions imply a need for data and logging to evidence compliance (reg 6(1)(g), (m)(i), (iv)-(vi), reg 7, reg 9). The Regulations do not stipulate retention periods or log formats; enforcement would therefore require regulators to define acceptable evidentiary standards in practice.
• Authorising agreements and municipal districts: several intervention rules depend on municipal district limits and authorising agreements (reg 6(1)(m)(vi)). Enforcement of location-based restrictions will therefore require coordination between regulators and the bodies that negotiate and approve authorising agreements.

Practical enforcement challenges and implementation risk

• Verifying functional features. Many obligations are functional rather than prescriptive. For example, reg 6(1)(m)(iv) requires detection of a fallen vehicle and provision of an alert to the operator but does not specify detection thresholds or alerting standards. Regulators will need technical assessment protocols to judge whether a vehicle’s fall-detection system meets the standard.
• Remote intervention safety and liability. The Regulations require the ability to slow and stop vehicles remotely (reg 6(1)(m)(vi)(B)-(C) and reg 6(4)(b)-(c)). Enforcers will need to consider safety implications of remote immobilisation and how to verify that operators have appropriate fail-safes and testing regimes. If a vehicle is slowed or stopped remotely and causes harm, determining causation and liability will implicate operator compliance and broader liability frameworks.
• Insurance versus prosecutorial outcomes. Reg 11(1)(b) requires rider insurance irrespective of whether the rider is found guilty of offences under the Road Safety Act, its regulations or the Road Rules. This creates a prospective insurance entitlement for injured third parties or injury claims by riders, but enforcement of the Regulations to ensure policies provide cover on the stated basis will require regulators to inspect policy wordings and claims-handling practices.
• Evidence collection and privacy. The Regulations create a data footprint (helmet-detection events, geolocation, cognitive test outcomes, fall events, parking status), but do not address data-sharing, privacy protections, retention or access rights. Enforcement will therefore require regulators to request and handle personal and telematics data, which raises administrative and legal workload.

Enforcement instruments likely to be used

• Compliance audits and documentation requests for policy certificates, maintenance plans and vehicle test reports.
• Vehicle inspections and functional tests to assess lighting visibility, reflector performance, helmet locks and the operation of technological interventions.
• Review of software behaviour and logs to test that cognitive test lockouts, helmet verification, messaging confirmations and geofence interventions operate as required.
• Actions under the Act and authorising agreements, including potential suspension or revocation of approvals, monetary penalties or orders to remediate if the operator is non-compliant. The Regulations themselves do not set these measures, so enforcement actions must be taken under the Act or agreements.

In short, the Regulations create a framework of functional obligations and minimum insurance limits but do not specify enforcement mechanisms or penalties within the text. Effective enforcement will require regulators to create technical standards, evidence protocols, audit practices and coordination with the approval regime under the Act and with authorising agreements that define municipal districts and other local conditions.

The Regulations are explicitly tied to a set of existing statutes and instruments, and they incorporate external technical standards by reference. Practical compliance requires operators and advisers to read the Regulations alongside these materials.

References to the Act and Part VIA. The Regulations are made under ss 207O and 256 of the Transport (Compliance and Miscellaneous) Act 1983 (reg 2) and explicitly prescribe matters for the purposes of Part VIA of the Act (reg 1). The Regulations therefore operate as subordinate legislation implementing Part VIA’s object and approval structures. The Act will set out authorisation, approval and enforcement mechanisms; the Regulations supply the technical and operational standards those authorised schemes must meet.

Road Safety Act 1986 and consequential criminal/regulatory provisions. The Regulations repeatedly reference the Road Safety Act 1986. Definitions such as alcohol interlock condition, behaviour change program and driver licence are imported from that Act (reg 4). Reg 6(2) requires electric scooters to display information about section 49 of the Road Safety Act 1986 (Offences involving alcohol or other drugs). Reg 8 requires the hiring software to inform hirers that the Road Safety Act’s drink- and drug-driving provisions apply to riders of electric scooters on roads or road-related areas and to outline potential consequences under s 49, including cancellation of driver licences, fines, behaviour change programs and alcohol interlock requirements. That cross-reference embeds criminal and administrative outcomes under the Road Safety Act into the pre-hire messaging regime required of operators.

Road Rules. The Regulations import the Road Rules by reference (reg 4) and require display of certain Road Rules provisions on electric scooters (reg 6(2)(b)). Reg 8 references specific Road Rules offences that may interact with hiring behaviour and enforcement of traffic rules by police. Operators must therefore ensure their user information and sanctioning messages align with the Road Rules and relevant offences.

Planning and Environment Act 1987 and municipal boundaries. The definition of metropolitan Melbourne is taken from the Planning and Environment Act 1987 (reg 4), and several location-based requirements depend on municipal district boundaries and authorising agreements (reg 6(1)(m)(vi)). Authorising agreements will therefore govern where a vehicle may be hired, and those agreements interact with the Regulations’ geofencing and intervention rules.

Subordinate Legislation Act 1994. The Explanatory Details state the Regulations will sunset 10 years after making under s 5 of the Subordinate Legislation Act 1994 (Endnotes). That imposes a statutory review/expiry horizon for regulators and operators to consider.

Incorporated technical standards. Reg 6(3) requires electric scooters to comply with a list of named technical standards for electrical systems and batteries. The Explanatory Details include a table of the applied, adopted or incorporated matter that names the standards and confirms that “the whole” of each listed standard is incorporated by reference (Endnotes, Table of Applied, Adopted or Incorporated Matter). Operators and suppliers must read and apply those incorporated standards when procuring and certifying scooters and batteries.

Insurance law and policy. Reg 11 requires minimum insurance limits for operator and rider liabilities. Those obligations will interact with general insurance law, policy terms, exclusions, indemnities and the law of subrogation. Notably, reg 11(1)(b) requires rider insurance irrespective of whether the rider is found guilty of relevant offences; that framing may affect insurers’ positions on exclusions for unlawful conduct and subrogation against riders but the Regulations do not alter general insurance law , they simply make the policy requirement for the scheme.

Data protection and privacy regimes. While the Regulations require extensive telematics (helmet detection, geolocation, fall detection, cognitive testing), they do not address data protection, retention, disclosure or privacy safeguards. Those aspects will therefore interact with general privacy laws and any sectoral guidance on personal data handling, and with the regulatory need to access logs and telematics for enforcement.

In sum, the Regulations are operationally entwined with the Transport (Compliance and Miscellaneous) Act 1983 authorisation regime, the Road Safety Act and Road Rules for legal offences and consequences, incorporated technical standards for electrical and battery safety, local planning definitions for mapping metropolitan Melbourne, insurance law for minimum cover, and data protection regimes for handling telematics and user data. Compliance therefore requires an integrated review of these interacting instruments.

There are no amendments to the Transport (Compliance and Miscellaneous) (Vehicle Sharing Schemes) Regulations 2026 recorded in the endnotes. The Regulations were made on 17 February 2026 by the Governor in Council under sections 207O and 256 of the Transport (Compliance and Miscellaneous) Act 1983 and commenced on 18 February 2026 (Endnotes, General information).

Key dates and lifecycle

• Made by Governor in Council: 17 February 2026 (Endnotes).
• Commencement: 18 February 2026 (reg 3).
• Sunset: The Explanatory Details note the Regulations will sunset 10 years after the day of making, i.e. 17 February 2036, under section 5 of the Subordinate Legislation Act 1994 (Endnotes).

Incorporated standards and their versioning

• Reg 6(3) incorporates specific technical standards by reference and the Explanatory Details list the exact editions and publication dates that are incorporated, for example AS/NZS 60335.2.114:2023 (published 1 December 2023), BS EN 17128:2020 (published 31 October 2020), ANSI/CAN/UL 2272:2016 and 2024, and ANSI/CAN/UL/ULC 2271:2018 and 2023 for batteries (Endnotes, Table of Applied, Adopted or Incorporated Matter). The incorporated-matter table indicates “the whole” of each named standard is applied. Consequently, operators and suppliers must comply with the specific versions listed until and unless later amendments to the Regulations update the incorporations.

No amendments recorded to date

• The endnotes explicitly state there are no amendments made to the Regulations by statutory rules, subordinate instruments or Acts (Endnotes, Table of Amendments). That means the current text and attached incorporated standards remain the legal requirements as at the Version noted (Version No. 001, as at 18 February 2026).

Implications for future amendment

• Because the Regulations are subordinate legislation and include incorporated external standards, any change to those incorporated standards or operational experience may prompt amendments to the Regulations. The sunset after ten years means a legislated date for statutory review or remaking absent renewal.

For users and advisers, the amendment history is brief and clean: the instrument is newly made, contains incorporated technical standards with specific editions listed in the Explanatory Details, and bears a ten year automatic sunset under the Subordinate Legislation Act 1994.

The Regulations’ endnotes and explanatory material record no judicial decisions, appeals or litigation concerning the Transport (Compliance and Miscellaneous) (Vehicle Sharing Schemes) Regulations 2026. The Explanatory Details include statutory and interpretive material and a table of incorporated standards, but there is no recorded litigation history in the instrument’s Endnotes.

Operationally, litigation may in future arise under several possible heads given the content of the Regulations, but such prospects are not recorded in the source. The text itself does not mention any cases or judicial treatment. Any dispute about interpretation, enforcement, the adequacy of technical measures (for example, whether a helmet-detection method or a remote stopping procedure meets the Regulations), or insurance coverage decisions would be litigable in future; however, the Regulations do not provide historical litigation to cite.

Accordingly, at present:

• There are no cases named in or attached to these Regulations.
• No administrative determinations or tribunal decisions about compliance, approvals, or enforcement under these Regulations are recorded in the Explanatory Details or Endnotes.
• Future litigation lines to watch (noting the Regulations only) include disputes about functional compliance (helmet verification, telematics), accidents involving remote intervention, insurance coverage disputes given the “irrespective of guilt” rider insurance provision, and challenges concerning authorising agreements and municipal boundaries. These are potential litigation vectors implied by the Regulations’ content but are not present as existing legal authorities in the source.

For practitioners, this means there is no binding judicial interpretation of the instrument available. Advisers must therefore rely on the Regulations’ plain text and coordinate with regulators about compliance expectations until administrative guidance or case law develops.

The Regulations contain several drafting and operational features that create compliance traps or ambiguities operators and advisers should note. The following are items that commonly produce implementation risk and require careful attention to the Regulations’ exact language.

Helmet logic and sequencing (reg 6(1)(g)-(h), (m)(ii)-(iii))

• The Regulations require that a vehicle be able to detect an approved bicycle helmet attached to the vehicle and that a vehicle is only made available for hire when such a helmet is attached (reg 6(1)(g)-(h)). Separately, the Regulations require technological features that prevent the vehicle from being ridden unless an approved bicycle helmet is detached from it or the operator verifies that the hirer is wearing their own approved helmet (reg 6(1)(m)(iii)). Operators must therefore implement two linked but distinct states: (1) helmet attached to permit hire; and (2) helmet detached or verified to permit riding. The text does not prescribe how verification of a rider-supplied helmet is to be performed. The phrase “able to verify” (reg 6(1)(m)(iii)(B)) is functionally open-ended and therefore a source of compliance ambiguity: photographic confirmation, video, biometric overlay, or operator visual confirmation may be possible verification methods but none is mandated. Operators must therefore document and justify their verification method and be prepared to show it to regulators.

Helmet lock specification and approved helmet definition (reg 6(1)(f), (g); reg 4)

• The Regulations require a helmet lock and the ability to detect approved bicycle helmets (reg 6(1)(f)-(g)). The Regulations do not define a standard for helmet locks nor state what constitutes an “approved bicycle helmet” beyond importing the meaning from the Road Rules (reg 4). That raises questions about acceptable helmet interfaces, detection mechanisms (mechanical, RFID, optical), and interoperability of third party helmets.

Remote slowing and stoppage functions (reg 6(1)(m)(vi); reg 6(4)(b)-(c))

• The Regulations require hardware/software capable of gradually and successively playing an audio alert, slowing the vehicle, stopping the vehicle and preventing a rider from ending a hire when outside the municipal district in which it may be hired (reg 6(1)(m)(vi)(A)-(D)). The Regulations impose the same graduated controls for footpath detection in metropolitan Melbourne (reg 6(4)(a)-(c)). The requirements impose a duty to implement remote control of propulsion and possibly regenerative braking or motor cut. The Regulations do not specify safe deceleration profiles, emergency-release mechanisms, or operator responsibilities when remote immobilisation causes a hazard. That creates potential safety and liability issues if vehicles stop in traffic or create fall risks.

Preventing end of hire outside specified areas (reg 6(1)(m)(vi)(D); reg 6(4)(d))

• The ability to prevent a rider from ending the hiring of the vehicle outside a specific area is required (reg 6(1)(m)(vi)(D) and reg 6(4)(d) for metropolitan Melbourne). That can strand riders if the system does not permit a manual override or if the operator cannot respond in real time. The Regulations do not prescribe procedures for assisting stranded riders or for handling exceptions.

Cognitive test lockouts and service availability (reg 7)

• Reg 7 requires a cognitive reaction test before 5 a.m. or after specified evening hours, and an enforced minimum four hour lockout after a second failed test. Operators must integrate this into their user flows; but the lockout periods could deny access to critical trips for some users. The Regulations do not require appeal or review mechanisms for erroneous test failures, nor do they prescribe reasonable accommodation for accessibility needs.

Insurance phrasing and rider cover irrespective of guilt (reg 11(1)(b))

• Reg 11(1)(b) requires the scheme include insurance for any liability of a rider aged at least 16 in respect of injury or damage arising from use of the vehicle, “irrespective of whether or not the rider is found guilty of an offence” under the Road Safety Act, its regulations, or the Road Rules. This is an unusual framing from an underwriting perspective: it constrains the operator to supply rider insurance that responds even where the rider is criminally culpable. Operators must ensure policy wordings do not contain exclusions that would defeat that statutory requirement and must confirm insurer willingness to offer such cover. The Regulations do not require the rider to be named in a policy as an insured; they require the scheme to include such insurance, so the design of cover and claims process is a careful drafting point.

Interoperability with incorporated standards (reg 6(3); Endnotes)

• Electric scooters must comply with one of a number of listed standards (AS/NZS, BS EN, ANSI/CAN/UL), and batteries must meet specified UL standards (reg 6(3), Endnotes). Supply chain mismatches between a scooter’s certification and the particular standard listed may render equipment non-compliant. The Explanatory Details expressly identify the versions incorporated. Operators sourcing older or non-listed-conforming models may need retrofit or replacement plans.

Lack of specified enforcement and evidence procedures

• The Regulations set many functional requirements but do not specify audit frequencies, documentation formats, or log-retention periods. Regulators will need to set administrative expectations; meanwhile operators must maintain comprehensive records (maintenance, logs of helmet detection, cognitive test outcomes, geofence events and fall notifications) to demonstrate compliance when regulators ask. The absence of specified standards for evidence creates uncertainty and administrative burden.

Municipal district / authorising agreement dependency (reg 6(1)(m)(vi))

• The graduated interventions apply where the vehicle is detected outside the municipal district “in which it may be hired in accordance with an authorising agreement” (reg 6(1)(m)(vi)). That places emphasis on the authorising agreement to define permissible hiring geography. Operators must align geofencing rules in their software to the spatial terms of their authorising agreements, which may vary across jurisdictions.

Data protection and privacy not addressed

• The Regulations demand telematics and behavioural logs without addressing data governance. Operators must develop privacy-compliant logging, retention and disclosure practices in line with privacy law to enable regulators to inspect compliance records.

Each of the above points is grounded in the Regulations’ text and highlights drafting or operational features that create ambiguity or discrete compliance burdens that operators and advisers should directly address.

Compliance requires coordinated actions across procurement, software design, operations, maintenance, insurance, and regulatory liaison. Below is a structured compliance checklist tied to the Regulations’ provisions and practical steps an approved category A scheme operator should take.

1. Legal and administrative alignment

• Confirm authorisations and scope of operation under Part VIA of the Act and any authorising agreements. Map the municipal districts and any no-ride/no-end-hire areas that apply under authorising agreements, because multiple Regulation obligations (reg 6(1)(m)(vi) and reg 6(4)(d)) depend on those boundaries.
• Prepare documented policies and point-of-contact details to provide to regulators on request, including the operator’s identity that must appear on vehicles (reg 6(1)(k)-(l)).

2. Vehicle procurement and equipment compliance

• Specify procurement contracts and supplier warranties requiring compliance with the incorporated electrical and battery standards listed in reg 6(3) and the incorporated-matter table in the Explanatory Details. Obtain and retain test reports and certificates demonstrating conformance to the named versions of AS/NZS 60335.2.114:2023, BS EN 17128:2020, ANSI/CAN/UL 2272 (2016 or 2024), and ANSI/CAN/UL/ULC 2271 battery standards (Endnotes).
• Ensure vehicles have the physical equipment required: at least one effective brake, bell/horn, white front light and red rear light meeting the “visible for at least 200 metres” criterion when activated (reg 6(1)(a), (c)-(d)); ensure a rear red reflector visible for at least 50 metres under low-beam (reg 6(1)(e)); and a stable self-standing capability (reg 6(1)(i)).
• Fit and certify helmet locks and helmet-detection systems. Document the detection technology, its reliability testing, and how it interfaces with the hiring application (reg 6(1)(f)-(g)).

3. Software design and user flows

• Implement helmet-check logic: prevent hire unless a helmet is detected attached (reg 6(1)(g)-(h) and reg 6(1)(m)(ii)), and prevent riding unless the helmet has been detached or operator verification of a hirer-supplied helmet occurs (reg 6(1)(m)(iii)). Make the business logic explicit and produce test evidence that the logic behaves as required.
• Build cognitive reaction tests into the hiring app with the timing and lockout rules in reg 7. Ensure the app: (a) runs the test at the specified hours, (b) prevents hire unless the user passes, (c) provides the mandated fail messaging on first fail (reg 7(2)(b)(i)-(iii)), and (d) enforces a minimum four hour lockout on a second fail (reg 7(2)(c)).
• Integrate drug and alcohol messaging required by reg 8(a) and prevent hire unless the user confirms they have read and understood the information and that they are fit to ride (reg 8(b)(i)-(ii)). The content must list the potential consequences named in reg 8(a)(ii)(A)-(E).
• Log all relevant events: helmet attach/detach events, verification outcomes, cognitive test attempts and results, messaging confirmations, geofence entry/exit, audio alerts and remote slowing/stopping events, fall detection events and alerts to the operator, and end-hire attempts (reg 6(1)(m), reg 7, reg 8, reg 9).

4. Telematics, geofencing and interventions

• Implement robust geofencing tied to municipal district boundaries in authorising agreements. Ensure software triggers the graduated interventions in reg 6(1)(m)(vi) in sequence: audio alert, slow, stop, prevent end-hire. For metropolitan Melbourne, implement the footpath-detection features in reg 6(4)(a)-(c) and the parking determination requirement (reg 6(4)(c) and reg 9).
• Design and test remote slow/stop functions with documented safe deceleration profiles and emergency override procedures. Maintain a failsafe plan if vehicles are immobilised in traffic or present a hazard to the rider or other road users.

5. Maintenance plan and operational capability

• Draft and maintain a maintenance plan satisfying reg 10. The plan should cover inspection intervals, servicing checks, battery management and replacement schedules, software update protocols, fall-detection and remote-control testing, and procedures for returning non-compliant vehicles to service.
• Keep records of inspections, remediations and component replacements. Ensure maintenance staff are trained in the technical standards listed in reg 6(3) where relevant.

6. Insurance procurement and policy management

• Obtain operator liability insurance with a minimum limit of A$20,000,000 as required by reg 11(2).
• Obtain rider liability insurance covering riders aged at least 16 for at least A$1,000,000 as required by reg 11(1)(b)-(3). Ensure policy wordings explicitly provide cover “irrespective of whether or not the rider is found guilty of an offence” under the Road Safety Act, its regulations, or the Road Rules, or otherwise document how the scheme satisfies the statutory requirement. Discuss subrogation and exclusions with insurers and legal advisers to confirm compliance with reg 11.
• Maintain certificates of currency and make them readily available for inspection by regulators.

7. Documentation and evidence for regulators

• Prepare a compliance pack including: maintenance plan, vehicle technical compliance certificates and test reports for lighting, reflectors and electrical/battery standards, software functional specifications and logs demonstrating cognitive tests and helmet-verification workflows, geofencing maps tied to authorising agreements, remote intervention test outcomes, and insurance certificates. The Regulations do not prescribe formats, so provide comprehensive, time-stamped and verifiable records.
• Implement log-retention and data access protocols aligned with privacy obligations and regulators’ likely evidentiary requests.

8. User communications and operations

• Ensure each vehicle displays the required information: unique visible ID number (visible at 5 metres) and operator contact information including a telephone number (reg 6(1)(j)-(l)). For electric scooters, ensure display of the Road Safety Act s 49 notice and the specified Road Rules (reg 6(2)(a)-(b)).
• Train customer support and field staff to respond to situations where the remote system prevents riding or ending of hire. Establish rapid-response processes for stranded riders and for safety-critical interventions.

9. Risk management and testing

• Test fall-detection functions and audit false positive/negative rates. Test the remote slow/stop features under controlled conditions and document safe operating procedures.
• Conduct user-experience testing on cognitive tests to minimise false failures and to account for accessibility requirements. Maintain escalation processes for false positive cognitive failures.

10. Privacy, data protection and legal compliance

• While the Regulations do not specify data-handling rules, implement privacy-by-design measures for telematics, helmet verification media, cognitive test data, and user confirmations. Prepare privacy notices aligned with applicable privacy law and be ready to provide records to regulators in line with lawful disclosure requirements.

Operational timeline and monitoring

• Map compliance milestones against vehicle deployment. For example: certify vehicle fleets to listed standards before first hire; test and log helmet-detection and remote-control functionality; confirm insurance arrangements; and submit any licence, authorisation or evidence required by the regulator or authorising agreement.

By following these steps and producing auditable documentation tied to the Regulations’ specific provisions (citing regs 6-11 as the compliance endpoints), operators can construct a defensible compliance posture. Where the Regulations leave technical or evidentiary specifics open, document design choices, testing protocols and risk assessments to show regulators a reasoned compliance approach.