Everything you need, written for the person doing the job
Each role has its own guide: what you are responsible for, the workflows you will run, and exactly what you can and cannot do. Read the concepts below once, then jump to your role.
See how it works
17 charts and flow diagrams: architecture, role hierarchy, the data model and every operational workflow.
Open the diagramsTry it as any role
Eight demo accounts, all sharing one password, on a database loaded with a working operation.
Open demo accountsFind your role
From employee and driver through dispatcher, manager, control room, finance, vendor and administrator.
Jump to the guidesKey concepts
Nine words the rest of the product assumes you know. They map one to one onto the screens.
- Site
- An office or delivery centre you run transport for. Shifts, routes and reporting all hang off a site.
- Shift
- A transport window — for example “Evening Drop 20:00”. A shift has a direction (pickup into the office, or drop home), a start and end time, a pickup tolerance window, and the days it runs on.
- Pickup point
- A geofenced boarding location with an area label. The area is what groups passengers together when routes are generated, so name areas consistently.
- Transport request
- One employee's demand for one shift on one date. Raised by the employee, by the transport desk, or generated from the roster. Requests inside the cut-off window need approval.
- Route
- A planned sequence of stops for one shift on one date, with a vendor, vehicle and driver allocated. A route is a plan — it can be edited freely until it is published.
- Trip
- What actually runs. Publishing a route creates the trip, builds the passenger manifest and notifies everyone. From then on the trip moves through its lifecycle and cannot be edited as a plan.
- Manifest
- The passenger list on a trip, in stop order, each with an attendance state: scheduled, boarded, dropped or no-show.
- Protected category
- A flag on an employee profile that applies your night-drop safety rule to them — typically meaning they must not be the last drop during night hours.
- Transport policy
- The single place every operating rule lives: cut-offs, capacity buffer, night window, compliance blocking, delay and no-show thresholds, GPS staleness, quiet hours and retention. Change it in Administration and it applies immediately.
- Authorised override
- When a safety or capacity rule blocks publication, a user with override permission can proceed by giving a written reason. The override and the reason are recorded against their name.
How a trip progresses
A trip only moves through valid stages, so the record cannot be tampered with by accident.
Guides by role
Pick the one that matches your job.
Employee
Book your cab, know when it arrives, get help if you need it.
Read the guideDriver
See today's trips, run the manifest, report problems.
Read the guideDispatcher
Watch the operation run and fix what breaks.
Read the guideHR / Transport Manager
Turn tomorrow's demand into published, safe, allocated routes.
Read the guideControl Room
Answer the safety alerts. Nothing else competes for your attention.
Read the guideFinance
Pay for the trips that actually ran, at the rate you agreed.
Read the guideVendor
Accept the work, keep your fleet compliant, get paid.
Read the guideTenant Admin
Configure how the product behaves for your organisation.
Read the guideCommon questions
The things people actually get stuck on.