Delivery Trips: Run the Trip, Record the Proof and Close the Day
Steps 5 and 6 of Installation Scheduling Workflow: the driver runs the trip, and you close the day. You are here after Step 4, with the van loaded and the trip at Ready To Ship.
Today’s van at GS-KV-01 carries three stops: the 75-inch display for wall-mounting, the split-unit air conditioner and the six laptops for a reseller.
Before you cancel anything at the end of the day: Cancel Trip cancels every job on it, so move the stops that are still going out to another trip first. Cancel a single job from the Job Sales Order / Job Sales Invoice / Job Delivery Order listing it belongs to, not from the combined Delivery Job listing (Step 6 says why).
Step 5: The driver runs the trip
Delivery And Installation Driver (on the driver’s phone)
The outcome: every job completed, with the recipient’s name, IC number and the quantity delivered per item recorded against it. Those are the proof of delivery the office can rely on. The driver also signs and photographs on the screen, but from the web applet neither the signature nor the photos can be viewed in the back office afterwards — see What the office can see afterwards on the driver applet page.
Set the trip to Start Trip when the van leaves — this applies Out For Delivery to every job on it in one action.
The driver opens the Delivery And Installation Driver applet, which offers only their own trips. Its home screen is a trip calendar, and in the web applet that calendar cannot list or open trips today (see the driver page’s Troubleshooting); this guide does not cover the Android app. A trip, once opened, shows the stops in the order you set. Each job card has the address as a map link and the contact as a tap-to-call number.
At each stop the driver taps Start Job, does the work, then Confirm Delivery and fills in the proof of delivery: quantity delivered per item, the recipient’s name and IC number, a signature on the screen, photographs, remarks, and any cash collected. Completing the job also empties any recipient phone number or job-level reason the office had typed on the job, so keep those in the job’s remarks. Short or refused items get a reason in the failure dialog — in the Remarks box for now, because its Failure Reason dropdown is empty (see Step 0).
What the driver cannot do, deliberately: start or complete a trip, set a custom status, back-date an event, or see any job that is not on one of their trips. All of that stays with you.
Step 6: Close the day
Delivery Installation > Trips > (your trip) > Complete Trip
The outcome: every sales document marked as delivered, and a record of what did not go to plan.
Complete Trip sets every job on it to Complete, writes the completion event on each, and re-stamps the source documents and shipments — which, for a job built from an invoice or an order, leaves the document reading what it read since Add to Trip (Step 3). The trip and the jobs are the record of completion; the Delivery Job Line Report is the day’s proof.
When a stop fails — nobody home, access refused — cancel that job from the listing it came from. Cancelling puts the quantity back into the pick-pack queue, which is exactly what you want: the invoice becomes deliverable again, its line turns back to Partially Delivered, and you can put it on tomorrow’s trip.
Cancel Trip cancels every job on it. If you are calling a trip off but three of its five stops are going out on another van, move those jobs to the other trip first, then cancel. There is no undo, and re-creating jobs means going back to the source listings.
Cancel a job from the Job Sales Order / Job Sales Invoice / Job Delivery Order listing it belongs to. The Cancel Job button on the combined Delivery Job listing only handles shipment-sourced jobs and will refuse a document-sourced one with SHIPMENT LINK TABLE NOT FOUND.
What success looks like for this part
Every job on the trip reads Complete or Cancelled, and nothing is still Out For Delivery. Each completed job carries the recipient’s name, IC number and the quantity delivered per item; each cancelled job’s quantity is back in the pick-pack queue of the listing it came from, ready for tomorrow’s trip. The Delivery Job Line Report for today lists one line per thing delivered. The whole day’s five-minute check is on the front page.
Common mistakes in this part
Cancelling a trip to fix one bad stop. Every job on it goes. Move the good ones first.
Cancelling a job from the wrong listing. Document-sourced jobs are cancelled from their own listing. The error message is not obvious about why.
Treating a completed job as proof the customer is happy. BigLedger records that goods arrived and were signed for. Whether the air conditioner actually works is between your installer and the customer, and if you need that recorded, it belongs in the job remarks — the photographs cannot be viewed from the back office (Step 5), and there is no commissioning record to fill in.
Assuming a cancelled job stays cancelled. In current builds a job cancelled with Cancel Job can still be completed afterwards, because the guard compares against a different spelling of the status than the button writes. Treat the job event history as the true record, and do not rely on the guard.
The rest of the guide’s mistakes are on the front page and on Plan and load the trip.
Related documentation
- Installation Scheduling Workflow — the setup and Step 1
- Plan and load the trip — Steps 2 to 4
- Delivery Installation applet — the full dispatch reference, including every endpoint and setting
- Delivery And Installation Driver — what the driver sees and what they can do
- Goods Delivery Note (Internal) — the paper the customer signs