Trips

A trip is one truck run. It records who drives (your own driver or a subcontracted haulier), with which truck and trailer or chassis, which bookings it carries, and the stops in order. Each booking adds a pick-up stop and then a delivery stop. The trip is where dispatch happens. It gives the driver a page on the phone, with no login, for the pre-trip check, arrivals, proof of delivery (name, drawn signature, CMR number, photos) and loaded / delivered. Before the truck leaves, the trip warns about driving time, ADR, tanker capacity and time windows. It also shows what the run earns, what it costs and the margin.

Where to find it: Workspace → Logistics → Transport → Trips. The Transport menu only appears when the module Transport bookings, trips, trucks and drivers is switched on in the Warehouse settings.

Who can use it

• See trips, the board and a trip's details: anyone with any Warehouse permission.
• Plan trips, send them to the driver, record stops, cancel trips and move cards on the board: the permission Bookings, trips and their events. A role with the whole group Gate in and out, move units, fill and empty tanks has it too.
• See Revenue, Cost and Margin: the permission See prices, revenue and margins (dashboard, trips, bookings, service orders). Without it the money columns show a dash and the trip's details hide the figures.
• The driver needs no NIZU account. The trip's private link is their access, and it works only for that trip.
• Roles marked Cannot use bulk actions work one row at a time. Roles with Transport (bookings, trips, fleet) under Does not see have no access.

Where it sits in the operation

Bookings come in as client orders. The dispatcher groups one or more bookings that are To plan into a trip, chooses the driver and the equipment, and sends the trip to the driver. On the road, each stop is closed with proof of delivery. The stop can be closed by the driver on the phone, by the office, or by the gate clerk when the stop is at one of your own sites. Closing stops moves the bookings on (On the road, Delivered) and finally the trip itself (Done). Delivered bookings then go to billing.

What you see

The page header shows the number of Open trips (Planned, Sent to the driver and On the road). Below it, one card with two tabs, List and Board, and Plan a trip at the top right. Which tab opens first is set in Settings → Warehouse → Appearance → Trips open on.

The statuses

List

Filter tabs: Open (the default), Planned, Sent to the driver, On the road, Done, Cancelled and All. The table can be searched, sorted and exported to Excel.

Select several rows for a bulk action: Send them to the drivers (planned trips) or Cancel them (Planned and Sent to the driver trips only). Trips in any other status are skipped.

Board

One column per status. The open columns are sorted by planned start, in the order the trucks leave. Done and Cancelled show the last 30. Each card shows:

• the trip number and the planned start;
• a Late badge when the planned start has passed and the trip is still Planned or Sent to the driver;
• the driver and truck plate, the haulier, or No driver yet;
• the route (first stop → last stop);
• a progress bar and the count of stops done.

Done and Cancelled cards cannot be dragged. Click any card to open the trip.

Plan a trip

1. Click Plan a trip, or drag a To plan booking to Planned on the Bookings board. The form then opens with that booking ticked.
2. Under Bookings on this trip, choose one or more bookings. Only bookings that are To plan are listed, with client, route and pick-up time. Each booking adds a pick-up stop and then a delivery stop, in the order you choose them.
3. Under Who drives?, choose your own Driver, or a Haulier you subcontract to (a provider from the Providers App). Optional: the Truck and the Trailer or chassis. Only active drivers and vehicles from Fleet are listed.
4. Optional: Planned start. Empty means the first booking's pick-up time, or now when it has none.
5. Optional: Distance (km). Empty means the sum of the bookings' distances.
6. Optional: Cost: what the trip costs you (fuel, tolls and driver for your own fleet, or the haulier's price).
7. Optional: a Note. Click Plan a trip. You see "TR-3 planned with 2 booking(s).", followed by any warnings as separate messages.

Each stop takes its booking's window. Its planned time is the window's From time, or the trip's planned start when the booking has no From. When nothing is waiting, the form says No bookings waiting to be planned: create a booking first.

A trip cannot be edited after it is saved: bookings, driver, truck, cost and distance are fixed. To change them, cancel the trip while it is Planned or Sent to the driver (its bookings return to To plan) and plan again.

The trip's details

Open a trip (its number, the eye button, or a board card) to see, from top to bottom:

• The header: trip number, driver and phone (or the haulier), truck plate + trailer plate, planned start and status.
• The Before you drive result: green "All OK", red with the defective items and the driver's words, or "The driver has not done the pre-trip check yet."
• The warnings, if any (see below).
• Revenue (with a "… without a price" badge when a booking has no price), Cost, Margin with its percentage, and Distance (km).
• The Stops in order. Each shows pick-up or delivery, the place, the client, the booking, the unit or product and litres, the window, the arrival time, the done or skipped time, "POD:" with the name of who signed, the CMR number, and links to the signature and photos.
• The driver's page with its link, Copy the link, and a phone button that opens the page (while the trip is open).
• What happened: every event, newest first, with time and who did it: the user, "Driver", or the channel (for example MCP).

Buttons at the bottom: Send to the driver and Cancel the trip while Planned; only Cancel the trip while Sent to the driver.

Send a trip to the driver

1. Open the trip and click Send to the driver, or drag the card. You see "Trip sent to the driver."
2. Under The driver's page, click Copy the link and send it to the driver, for example by WhatsApp or SMS. The link is created with the trip and stays the same. It already works while the trip is Planned. Sending is how the office marks the hand-over.
3. On the phone, without logging in, the driver sees Your trip TR-3, your company name, their name and plates. Below are Before you drive and every stop with its window, the client, and the unit or product. Addresses have an Open in maps link.
4. Only the next open stop has buttons, so the driver works the stops in order:
   • I have arrived.
   • At a pick-up: Handed over by (name), a Signature drawn on the screen (Clear to redo), an optional CMR number and optional Photos taken with the camera, then Loaded.
   • At a delivery: Received by, signature, CMR number, photos, then Delivered.
   • At one of your own sites, after arriving: "Report at the gate: they will check you in or out." The driver closes nothing there; the gate does.
5. When the last stop is done the driver sees "All stops are done. Thank you, drive safely." A cancelled trip shows Cancelled. A deleted trip's link says "This link is not valid any more."

The pre-trip check

On the phone, Before you drive lists eight items: Tyres and wheels, Lights and indicators, Brakes and air, No leaks (fuel, oil, load), Coupling and fifth wheel, Documents (licence, CMR, ADR papers), ADR kit and placards (dangerous goods), and Load and unit secured, seals on. Each one is OK or Defect. Everything is OK ticks them all at once. A defect needs a short description under What is wrong (if anything), otherwise "Say what the defect is." Send the check stores it on the trip: "Check sent. Drive safely." or "Check sent with 2 defect(s): the office can see it."

The office sees the result at the top of the trip's details and in What happened as "Pre-trip check". A defect does not stop the trip: it is reported, and the dispatcher decides. The check can be sent while the trip is Planned, Sent to the driver or On the road.

Under Settings → Warehouse → Transport and EDI, Pre-trip check before the first stop makes it required. The first arrival is then refused with "Do the pre-trip check before the first stop." until a check has been sent.

Record stops from the office

When the driver cannot use the phone, or a stop is confirmed by mail or phone, close it from the trip's details. On each open stop:

• Arrived (while To do): records the arrival time. A Planned or Sent trip goes On the road.
• At an outside address, Mark as done: you are asked "Who signed for it? (name)". The office records the name only. Signature, CMR number and photos come from the driver's page.
• At one of your own sites, Gate in (delivery) or Gate out (pick-up): the gate form opens filled in with the stop's unit, truck plate and driver. When you let the unit in or out, the stop is closed at the same moment, with the note "at the gate".
• Skip: the stop will not be carried out on this trip.

A stop closed without an earlier arrival gets the closing time as its arrival time. The trucks expected at a site today also appear on that site's live yard under Expected today, with the same gate buttons.

Warnings

The trip checks itself when you plan it and each time you open it. Warnings never block. They tell the planner what to check, because the planner knows things the App does not (a second driver, a ferry, a haulier's own ADR cover).

What is not checked: driving time is an estimate from distance, not tachograph data. Payload in kg is not compared with the load. The driving-licence date is not checked on trips. When the trip goes to a haulier, the ADR checks are left to the haulier.

Revenue, cost and margin

Fill in Cost when you plan. Without it the margin equals the revenue and means nothing. For your own fleet, use your cost per km × distance plus tolls and the driver. For a haulier, use their agreed price.

Controls and exceptions

• Double taps and poor coverage. Every driver action and board move carries a one-time key. If the same form is sent twice (a resend on a weak network, a double tap), the second one is not applied, and the driver sees "This was already recorded." Simultaneous actions on the same trip are handled one after the other, so two people cannot close the same stop twice.
• Audit trail. What happened is append-only. Every plan, send, take back, start, arrival, stop done, skip, cancel and pre-trip check is kept with its time and source (web user, driver, MCP and others). Signatures and photos are stored as files on the stop.
• The truck left but nobody pressed anything. Drag the card to On the road, or record Arrived on the first stop.
• The driver forgot to press Delivered. Use Mark as done in the office with the receiver's name, and ask for a CMR photo by other means.
• A stop will not happen. Skip closes the stop but leaves its booking where it was. A skipped delivery is not delivered, not billed, and cannot go on another trip. When the move is only delayed, rather cancel and re-plan while the trip has not left.
• Wrong driver, truck or bookings. There is no edit. Cancel while Planned or Sent and plan again.

For the manager

• At dispatch time: the Planned column with Late badges shows trucks that should already have left. Open each trip with warnings before sending it.
• During the day: the On the road progress bars, and the trip's details for POD names, CMR numbers and the pre-trip results. A red pre-trip check needs a decision before the truck goes on.
• Weekly: sort the list by Margin, look at negative or thin trips, and look at trips with "without a price" bookings. Those will not be billed until priced.
• Billing: trips are not invoiced themselves. Their delivered bookings are (see Bookings and Rates). The trip's cost is for margin control only. It does not create an expense.
• AI Reports: "Transport trips (Warehouse)" gives trips, cost, km and the average hours from start to end, by driver, status, subcontracted or not, and planned start. Combine it with "Transport bookings (Warehouse)" for on-time % and agreed value.
• AI agents and Marvin: MCP tools warehouse.trips, warehouse.plan_trip, warehouse.trip_event and warehouse.trip_status plan trips and record events through the same rules. Marvin can tell a user which trucks are on the road.

Glossary

Trip

One truck run carrying one or more bookings, with its stops in order.

Stop

A pick-up or a delivery of one booking at one place, with its window and proof.

Dispatch

Handing the planned trip to the driver: Send to the driver plus the link.

Haulier

A subcontracted carrier (a provider in the Providers App) that runs the trip with its own truck and driver.

POD

Proof of delivery: the name of who received or handed over, the drawn signature, and photos.

CMR

The international road consignment note. Its number can be recorded on each stop.

Pre-trip check

The driver's walk-around inspection of the truck and trailer before driving.

ADR

European rules for carrying dangerous goods by road. They require an ADR-equipped vehicle and a driver with a valid ADR certificate.

EU 561/2006

The EU driving-time regulation: 9 h daily driving, a 45-minute break after 4.5 h. The warnings use these limits.

Time window

The From – Until period in which a stop should happen.

Margin

Revenue of the trip's bookings minus the trip's cost.

Idempotency key

A one-time code on each action, so a resent action is recognised and not applied twice.

Related screens

• Bookings: what goes on a trip.
• Fleet: drivers, trucks and trailers, ADR and licence dates.
• Units: gate in and gate out at your own sites.
• Rates: transport per load, per km, detention, and Bill a month.
• Products: hazard class and UN number that trigger the ADR checks.
• Warehouse settings: average speed, pre-trip check, fuel surcharge, numbering.
• All screens