Compliance, state by state · NT

Northern Territory ridesharing compliance with JollyDrivers

How far JollyDrivers goes towards the Northern Territory's Commercial Passenger (Road) Transport Act 1991 today — ridesharing networks, drivers and vehicles, and the per-trip passenger services levy — and what isn't built for the Territory 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.

Northern Territory at a glance

Regulator: Department of Logistics and Infrastructure — Commercial Passenger Vehicles
The booking business holds: Approval as a ridesharing network or operator — check the current category with the Department
The driver holds: Driver approval for commercial passenger work under the Act
The vehicle needs: Approval to use the vehicle for ridesharing, and registration
Per-trip levy: A per-trip passenger services levy, lodged online by operators and ridesharing networks
Safety system: Conditions under the Act and Regulations, and work health and safety law
Records and reporting: Levy returns lodged online; other records as the Department requires
JollyDrivers here: National tools only National tools only — no Territory document catalogue, safety-plan templates, course or levy line yet.

The rulebook

Commercial Passenger (Road) Transport Act 1991 (NT) and the Commercial Passenger (Road) Transport Regulations 1992 (NT) — commercial passenger vehicles, including ridesharing.
The regulator is the Department of Logistics and Infrastructure's Commercial Passenger Vehicles team, which also runs the per-trip levy.

JollyDrivers has not written a Territory pack yet, so this page is general. Check the detail with the Department.

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 Territory 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

Ridesharing networks and operators must be approved under the Act, and lodge and pay the per-trip levy.

Built The booking record, event history, case register and invoicing work the same here as anywhere. Not built yet No Territory safety-plan templates. Yours to do Holding the approval.

Drivers

Partly built The licence and other documents can be stored with expiry dates and approved by the operator, but no Territory driver document type is seeded yet.

Vehicles

A vehicle must be approved before it is used for ridesharing.

Partly built Vehicles carry their own documents and a service log; no Territory 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 Territory notification test or deadline yet.

Records, fares and levies

A passenger services levy is payable on each commercial passenger vehicle trip, including ridesharing, and is lodged and paid online. The Department's bulletin sets the current amount.

Built Every booking is kept with its full history, and tax invoices go into the operator's own Xero. Not built yet No Territory levy line and no levy return.

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 Territory document types, safety-plan templates, course, levy line 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.

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.