Licensing Register
Operators, vehicles and drivers with their licence class, conditions, validity dates and history. The register is the source, not a copy of one.
Regulator Console
The whole licensed fleet on one screen
A single view of every vehicle, driver, operator and trip under your licence, with the record behind each one and the tools to act when something is wrong.
Most authorities regulate on a delay
Licensing sits in one system, complaints in another, and operational data arrives as a monthly spreadsheet from the operators themselves. By the time a pattern is visible, the quarter it belongs to has closed.
- Licence, vehicle and driver records held in separate systems
- Operational data supplied by the operators being regulated
- Complaints investigated without access to the trip record
- Expiring credentials found during audits rather than before
- No way to measure service obligations as they are being met or missed
What the console gives an authority
Licensing, live operations, compliance and reporting in one place, drawing on the same record the dispatch engine writes.
Credential Monitoring
Insurance, roadworthiness, medical and background check expiry tracked automatically. A vehicle with a lapsed credential stops receiving work.
Live Jurisdiction View
Active vehicles, open jobs, waiting passengers and coverage by zone, shown as they happen rather than reported afterwards.
Service Obligation Tracking
Response times, accessible vehicle availability and zonal coverage measured against the targets in the licence, per operator.
Complaint and Case Handling
A complaint opens against the actual trip record: the driver, vehicle, route, fare and allocation decision are attached automatically.
Enforcement Actions
Warnings, suspensions, conditions and penalties issued from the console, applied to the operating record immediately and logged against the officer who issued them.
Policy Publishing
Fare tables, zone definitions and allocation rules are published from here and take effect across every connected operator at a stated time.
Reporting and Disclosure
Board, ministerial and public reporting generated from the operating record, with the underlying data exportable in full.
Regulating on evidence rather than submissions
The console reads the same record the dispatch engine writes, so the authority is not dependent on operators self-reporting their own performance. Where an operator disputes a figure, both parties are looking at the same underlying trips.
Single recordNo self-reportingFull audit trailOfficer attribution
Governance
Built around how an authority actually has to work
Procurement, audit and legal teams ask the same questions of every system a regulator buys. These are the answers.
- Role-based access, separating licensing, enforcement and analyst duties
- Every action attributed to a named officer with a timestamp
- Records retained to the schedule your legislation sets, not ours
- Full export of the operating record at any time, in open formats
- Hosted inside your jurisdiction, in a sovereign cloud or on-premise
- Read-only access for auditors without granting enforcement rights
- Change history on every policy, fare table and rule version
- Personal data handled under the authority's own governance policy
Works with
The rest of the platform
Bring your licensing conditions
The most useful demonstration is the one run against your own regulations. Send them ahead and we will configure the console before we meet.