Trips

A trip is one journey a driver makes: an ordered list of stops, optionally starting from an origin, with a driver, a vehicle and a schedule attached. It is the unit you plan, dispatch, watch and close out, and it is what the driver app shows when someone taps Start.

This page covers the trip list and the trip page. Building a route is covered separately in the trip wizard and stops and sequencing.

Every trip gets a generated number of the form TRIP-20260310-0001 — the date it was created plus a counter for that day. You can also record your own reference number, which is searchable alongside the trip number.

Beyond that, a trip carries:

• A type and a priority. Type comes from a tenant-configurable list (delivery, pickup, transfer, return, service, inspection, emergency, other by default). Priority is low, normal, high or critical.
• An origin, or none. With no origin the trip starts wherever the assigned driver is, and the route is measured from the first stop instead.
• A driver, an optional second driver, and a vehicle. All three can be left empty at draft stage and filled in later.
• A schedule. Scheduled start and end, plus planned distance and estimated duration, which the route builder fills in for you unless you override them.
• Its stops, tasks, cargo and documents, each on its own tab of the trip page.
• Costs and revenue, recorded per trip and rolled up into the trip report.

The trips page opens on a table, with a view switcher in the header for a board and a calendar. All three read the same filters, so switching view never changes which trips you are looking at — only how they are drawn.

Above the table sits a status strip: one cell per status, each a single-click filter, with the total clearing it again. Below that, a filter bar with quick views for Today, This week, Active and All, and filters for status, scheduled window, driver, vehicle, priority, type and origin. Search matches the trip number, the reference number and the notes.

The table shows trip number, status, driver, vehicle, origin, scheduled start and priority by default. Around a dozen more columns — type, category, stop progress, actual times, distances, weight, tags — are available from the column manager and remembered per user. Driver, vehicle and origin columns are deliberately not sortable: the server can only sort them by internal id, which would order the rows arbitrarily rather than by name.

A trip has exactly one status, and the moves between them are fixed. There is no free-form status field: every change is a transition the server validates, records as an event on the trip, and may refuse.

Open a trip and the header offers only the actions its current status permits. Anything destructive asks for confirmation, and several ask for a reason that is stored on the trip rather than discarded.

• Draft: Schedule, Edit, or Delete — deleting a draft needs no reason.
• Scheduled: Assign, Edit, or Cancel with a reason.
• Assigned: Edit, or Cancel with a reason.
• En route: Pause with a reason (driver break, vehicle issue, weather, dispatch hold, other), Complete, or Fail with a reason.
• Paused: Resume, or Cancel with a reason.

There is deliberately no Start button on an assigned trip. Starting is the driver's action, and whether it happens by tapping Start or automatically on departure from the origin is a tenant setting, not a per-trip choice.

Assigning runs a conflict check — the same driver or vehicle already booked, maintenance windows, hours-of-service. Conflicts are recorded on the trip and shown to you, but they never block: an operator overriding a warning is a real and legitimate case. What does block is a missing driver, and a vehicle that is not active when the trip starts, which can be forced through only with a reason.

The header carries the trip number, its status badge, the origin and stop count, planned distance and duration, a progress stepper and a PDF report. Everything else lives on tabs:

• Overview — the trip at a glance, with recent events.
• Stops — the route, editable while the trip is not in a final state.
• Tasks — every task across every stop, with proof status. See tasks.
• Events — the full audit trail of state changes and system actions.
• Locations — the GPS breadcrumb the driver app reported.
• Documents and Cargo — files and consignments.
• Exceptions — late arrivals, SLA breaches and deviations that were flagged.
• Route comparison — the planned route against what actually happened.

The PDF report bundles costs, revenue, internal notes and contact details, so it is restricted to admins even though drivers can open the trip itself.

Select rows in the table and a bar appears with three actions: cancel, export to CSV, and assign a driver. Each one is applied per trip rather than as a single transaction, so a partial result is possible and is reported as one — for example "7 cancelled, 2 failed". The trips that succeeded are cleared from the selection; the ones that failed stay selected so you can look at them and retry.

A separate export control in the page header exports the current filter rather than the current selection, which is usually what you want for reporting.