Compliance, state by state · ACT
ACT rideshare compliance with JollyDrivers
How far JollyDrivers goes towards the ACT's Road Transport (Public Passenger Services) Act 2001 today — transport booking service accreditation, rideshare driver accreditation, rideshare vehicle licences — and what isn't built for the ACT yet.
Checked against the legislation in force on 26 September 2026. This page explains how JollyDrivers works; it is not legal advice. The regulator has the last word.
Australian Capital Territory at a glance
- Regulator
- Access Canberra
- The booking business holds
- Transport booking service accreditation
- The driver holds
- Rideshare driver accreditation — a 'D' condition on the licence and a public vehicle driver authority card
- The vehicle needs
- A rideshare vehicle licence and registration
- Per-trip levy
- No per-trip levy
- Safety system
- Accreditation conditions under the Road Transport (Public Passenger Services) Regulation 2002
- Records and reporting
- As the accreditation conditions require
- JollyDrivers here
- National tools only National tools only — no ACT document catalogue, safety-plan templates or course yet.
The rulebook
- Road Transport (Public Passenger Services) Act 2001 (ACT) — rideshare services, rideshare drivers and rideshare vehicle licences (from s 60A), and accreditation of transport booking services.
- Road Transport (Public Passenger Services) Regulation 2002 (ACT) — the accreditation requirements and conditions.
- The regulator is Access Canberra.
JollyDrivers has not written an ACT pack yet, so this page is general. Check the detail with Access Canberra.
Every step of the way
JollyDrivers' national tools apply here as everywhere: documents with expiry dates and operator approval, one door for every booking, the eligibility check at assignment (it warns rather than refuses today, and has no ACT document types to check against yet), stage stamps on every trip, the case register, tax invoices in the operator's own Xero, and the booking's full history kept.
The booking business
A transport booking service must be accredited and comply with its accreditation conditions.
Built The booking record, event history, case register and invoicing work the same here as anywhere. Not built yet No ACT safety-plan templates. Yours to do Holding the accreditation.
Drivers
A rideshare driver needs rideshare driver accreditation: on approval the licence is endorsed with a 'D' condition and a public vehicle driver authority card is issued.
Partly built The licence and other documents can be stored with expiry dates and approved by the operator, but no ACT accreditation document type is seeded yet.
Vehicles
A rideshare vehicle needs a rideshare vehicle licence (Act s 60J) as well as registration.
Partly built Vehicles carry their own documents and a service log; no ACT vehicle document types are seeded, and a booking does not yet snapshot which vehicle did the trip.
Safety and fatigue
Built Hours counted from trips across every operator on JollyDrivers, against the driver's own cap, with history reports. Built — switched on by choice The warning when a job would pass the cap.
Incidents and complaints
Built The case register records complaints and incidents on the operator's own books. Not built yet No ACT notification test or deadline yet.
Records, fares and levies
Built Every booking is kept with its full history, and tax invoices go into the operator's own Xero. The ACT charges no per-trip levy.
Privacy
Built Operators see only their own bookings, driver documents move only by recorded consent and are encrypted at rest, and privacy requests are tracked. Not built yet No separate consent step before a medical certificate or police check is uploaded.
Where JollyDrivers falls short
- No ACT document types, safety-plan templates, course or notification guidance.
- The compliance gate warns rather than refuses, and reminders are switched off, as everywhere.
Check it yourself
Operators and drivers can see what JollyDrivers holds at /portal/compliance and /portal/driver/documents. Every change JollyDrivers ships is dated at /releases.
Every state and territory
The same duties land differently across the border. The national picture and the side-by-side table are on the compliance hub.
- QLDQueenslandBooking entity authorisation (BEA)State pack built
- NSWNew South WalesBooking service provider (BSP) authorisationState pack built
- VICVictoriaBooking service provider registrationNational tools only
- SASouth AustraliaAccreditation as a centralised booking serviceNational tools only
- WAWestern AustraliaOn-demand booking service authorisationNational tools only
- TASTasmaniaOperator accreditation under the Passenger Transport Services Act 2011National tools only
- NTNorthern TerritoryApproval as a ridesharing network or operator — check the current category with the DepartmentNational tools only
- ACTAustralian Capital TerritoryTransport booking service accreditationNational tools only
JollyDrivers is booking and back-office software. It is not an authorised booking entity, booking service provider or transport operator, and it does not hold anybody's authorisation for them: the operator does, and the operator and driver stay accountable for the duties the law gives them. Statements about the law are summaries, checked on the date above against the legislation then in force; legislation changes, and the regulator's own guidance and the in-force text are the authority. Found something out of date? Tell us at hello@jollydrivers.com.au.