Every trip your fleet runs, on one screen — who drove what, for whom, and whether it is paid.
Dispatchers think in trips, not time slots. The board lists each trip as a row: date, customer, container number, driver, vehicle, advance paid, amount settled, proof-of-delivery status, and a notes field for everything that does not fit elsewhere. Newest trips on top; nothing is more than one scroll away.
Filter by date range, customer, driver, vehicle or trip status. A dispatcher answering "where is container TGHU 482910?" types the number and gets the trip, the driver and the current status — no scrolling through a month of rows.
The add-trip form asks for what dispatch actually knows at booking time: customer, pickup and delivery points, container, vehicle and driver. The rest — costs, POD, settlement — fills in as the trip happens. A trip can be created before a driver is assigned and claimed later.
You rarely start from an empty board. Import a week's dispatch plan from Excel: the importer maps your columns to Haulva's fields and shows every row before anything is saved, so a typo in a container number gets caught at import time, not at the port. Export works the same way — the full filtered ledger to Excel for the accountant, the customer, or your own archive.
Each trip carries its own costs: fuel, tolls, port fees, driver advance. The cost-allocation tool splits shared costs across the trips of a day or a vehicle, so month-end no longer means rebuilding the numbers from receipts. Finance reads the same rows dispatch wrote — there is no second spreadsheet to reconcile.
| Capability | Office (web) | Driver app |
|---|---|---|
| Trip ledger, filters, search | Yes | Driver sees only their own trips |
| Add and edit trips | Yes | Drivers update status, not trip details |
| Excel import and export | Yes | Not available |
| Cost allocation per trip | Yes | Not available |
| POD photo upload | Yes | Yes — taken at delivery |
Log in as ops / ops123 and run the board the way a dispatcher does.