No more paper dockets. No more missing delivery records.
The delivery record that connects the job to the invoice
In haulage, a docket is the delivery record that confirms a job was completed — what was delivered, where, when, and who received it. In bulk haulage, it is often a scale ticket showing the weight of material delivered, a site sign-off from the receiving party, or a combination of both. The docket is the evidence that the work was done and the basis on which the invoice is issued.
Without a docket, you have a driver's word that the delivery happened. That is often good enough for the invoice, until a client disputes a charge. At that point, the paper docket — if it can be found — is the only evidence you have. If it is lost, the dispute is harder. If it is illegible, it may as well be lost. If it was for the wrong job, it actively makes things worse.
Digital dockets in HaulageOps are the direct replacement: the same information, captured on the driver's mobile device at the delivery site, stored in Azure, attached to the job record, and visible in the client portal — without any of the delays or risks that come with paper.
Paper workflow
Handwritten at site → stored in cab → arrives at depot days later → admin files it.
- Lost in cab
- Arrives three days late
- Illegible handwriting
- Wrong job reference
Digital workflow
Photo + signature captured in app at site → instant upload to Azure → attached to job record.
- Zero handling time
- Available in admin panel immediately
- Visible in client portal
- Cannot be lost
Why paper dockets cause invoice delays even when the job runs perfectly
Lost or late dockets
The docket leaves the delivery site in the driver's cab. It might arrive at the office the same day. It might arrive Friday. It might never arrive — left in a jacket pocket, dropped at the depot, or handed to the wrong person. Every missing docket is a job that cannot be invoiced until someone tracks it down. In a fleet running 50+ jobs per week, docket chasing becomes a standing administrative burden.
Wrong job, wrong reference
A paper docket associated with the wrong job number causes the wrong invoice to be generated or delays both invoices while the error is investigated. When dockets are manually sorted and filed, matching errors are common. A driver picks up two dockets from two different clients on the same day. The paperwork gets mixed. Admin applies both to the wrong jobs. The error surfaces when the client queries the invoice.
Illegible or incomplete
Handwritten dockets completed in a vehicle cab, in the rain, by a driver who has already run three loads that morning are not always clearly written. Illegible weight readings, missing reference numbers, and incomplete signatures cause admin to go back to the driver for clarification — adding more days to the process. A photograph is always legible. A captured signature is always complete.
No client visibility
The client's copy of the docket, if they receive one at all, is whatever the receiving site keeper kept. They cannot log in anywhere to see their delivery records. They call your admin team for a copy. Admin finds the docket, scans it, and emails it. For high-volume clients this becomes a regular request that consumes time on both sides.
No audit trail
A paper docket in a filing cabinet is not an audit trail. There is no record of when it arrived, who handled it, or whether the version filed matches what was originally captured at the delivery site. If a dispute goes to mediation or legal process, a paper docket offers limited evidential weight compared to a timestamped digital record with GPS location, signature capture, and a documented chain of custody in Azure storage.
Invoice delay is the consequence
Every docket problem — lost, late, illegible, mismatched — adds time between the job completing and the invoice being sent. In bulk haulage where margins are tight and job volumes are high, invoice delay accumulates into a material cash flow gap. The docket problem is not a paperwork inconvenience — it is a working capital issue.
Captured at the site. Stored in Azure. Attached to the job before the truck moves.
When a driver completes a delivery in the HaulageOps driver app, the POD capture workflow begins automatically. The driver does not need to navigate to a separate section or look up a job reference — they are already in the correct job in the app.
Delivery photograph
Timestamped and geotagged using the phone's location services. Uploads to Azure Blob Storage and attaches to the job record.
Customer signature
The receiving party signs directly on the driver's phone screen. Drawn on the device, not photographed from paper — stored as part of the POD record.
Document upload
Scale ticket, weighbridge docket, site entry record — photographed and uploaded through the same workflow, attached to the job in Azure Blob Storage.
Offline operation
No connectivity at the site? All three captures queue locally and upload automatically when signal returns — no action from the driver, nothing lost.
Delivery address shown. "Mark Delivered" button active.
Three options: Take Photo, Collect Signature, Upload Document.
Customer name field plus blank drawing area on the device.
"POD captured — 3 items attached" with upload status. Offline indicator when no signal.
Offline mode indicator visible when signal is unavailable — captures queue and upload automatically.
The docket is already there when you need it — in every portal that needs it
Admin & Dispatch Panel
The moment a docket is captured and synced, it is visible in the admin panel against the job record. Dispatchers and billing admin can see the POD status on every job without asking the driver. When it is time to generate an invoice, the docket is already attached — there is no chase, no wait, no manual filing step between delivery and billing.
- POD status visible on the job record immediately after sync
- All three capture types — photo, signature, document — accessible from the job
- Download or view in browser — no separate file access required
- Available for invoice generation without any manual step
Client Portal
Your clients have access to their own delivery records through the client portal. When a docket is captured against one of their jobs, it becomes visible in their portal alongside the job detail and — once generated — the invoice. Clients do not need to call your office for a copy of the docket. They see it the same day the delivery was made.
- Client sees their own dockets in self-service portal
- POD linked to the job record and the invoice
- Delivery photograph, signature, and any uploaded documents all accessible
- Reduces inbound queries from clients requesting POD copies
JOB-1844 — Apex Civil
Driver: L. Chen · Status: Delivered · Completed 14:35
POD — 3 items attached
Delivery photograph
Captured 14:32 · GPS -33.87, 151.21
Customer signature
Signed by J. Marshall · 14:33
Scale Ticket — uploaded by driver
Captured 14:31 · 23.4 t gross
POD present and complete — invoice can be generated directly from the job record, no manual step between delivery and billing.
What changes when you stop relying on paper dockets
| Scenario | Paper Docket | HaulageOps Digital Docket |
|---|---|---|
| Docket captured | Handwritten at delivery site, stored in cab. | Photographed and signed on driver's phone at delivery site. Uploaded to Azure. |
| Docket arrives at office | When the driver returns. Sometimes days later. Sometimes never. | Attached to job record the moment the driver uploads — before they leave the site. |
| Docket matched to the correct job | Manually matched by admin. Errors possible, especially at high volume. | Automatically attached to the active job in the driver app — no manual matching. |
| Client wants a copy | Admin finds the paper copy, scans it, emails the client. | Client logs into their portal and views it themselves — no admin involvement. |
| Docket lost | Invoice delayed. Ask the driver. Hope the site has a copy. Chase for days. | Cannot be lost — it is in Azure Blob Storage, attached to the job record. |
| No signal at delivery site | Paper docket is unaffected — but still has all the usual problems above. | Driver app works offline. Captures queue locally, upload on reconnect. Nothing lost. |
| Docket used to generate invoice | Admin retrieves paper docket, reads details, enters into billing system. | POD already attached to job record. Invoice generated directly from job — no re-entry. |
| Dispute about delivery | Locate the paper docket. Hope it is legible. Hope it was correctly filed. | Timestamped photo, signature, and document in Azure. Complete chain of evidence available instantly. |
Digital dockets — common questions.
What if the driver has no mobile signal at the delivery site?
The driver app is offline-capable. If there is no connectivity at the delivery site — which is common at quarries, on construction sites with temporary facilities, or in rural locations — the app continues to operate normally. Photographs, signatures, and document uploads are captured and stored locally on the device. When the driver returns to an area with signal, the app uploads everything automatically without any action from the driver. The job record in the admin panel and client portal updates as soon as the sync completes.
Can my clients see their own digital dockets?
Yes. Clients who have a client portal login can see the dockets for their own jobs. The delivery photograph, signature capture, and any uploaded documents are visible in the portal alongside the job detail and invoice. Clients cannot see dockets for other clients' jobs, and they cannot see your other operational data. Access is scoped strictly to their own records.
How are the photographs stored? Can I download them?
All photographs, signature images, and uploaded documents are stored in Azure Blob Storage. They can be viewed directly from the job record in the admin panel or client portal. Download is available from the admin panel for admin and billing users. The files are stored with timestamps and job references — there is no manual filing or folder organisation required on your end.
Does the driver need to be on the correct job in the app for the docket to attach correctly?
Yes. The POD capture is initiated from within the active job in the driver app, so the docket automatically attaches to that job. The driver cannot accidentally attach a docket to the wrong job by going through the normal capture workflow. If a driver is managing multiple jobs, they work through each job sequentially and capture POD against each one separately.
What if a subcontractor's driver is completing the delivery — does this work the same way?
Yes. When a job is delegated to a subcontractor, their driver uses the same driver app and the same POD capture workflow. The docket is captured and stored in Azure in the same way, and it attaches to the job record in your admin panel — not in the subcontractor's portal only. Your client sees the docket in their portal regardless of whether the delivery was made by your driver or the sub's driver.
Is digital POD acceptable as evidence in a payment dispute?
HaulageOps generates a timestamped record that includes delivery photograph, customer signature, GPS location data, and the chain of custody in Azure storage. Whether this meets the evidentiary standard for a specific dispute depends on the jurisdiction and the nature of the dispute. What it provides — compared to a paper docket — is a more complete, tamper-evident, and immediately accessible record. We recommend discussing your specific evidence requirements with your legal or commercial advisors.
Digital dockets connect to these features and solutions
Driver App
The iOS and Android app drivers use to receive jobs, update status, capture POD, and log breaks — offline-capable with Firebase push notifications.
Driver App detailProof of Delivery
The full POD workflow — how photograph, signature, and document capture combine to create a complete delivery record for invoicing and dispute resolution.
Proof of DeliveryJob to Invoice
How the digital docket connects directly to invoice generation — the rate is already attached, the POD is already present, and the invoice builds from the completed job record.
Job to InvoiceDocument Management
Azure Blob Storage for all operational documents: dockets, licences, permits, contracts, and insurance records — stored against the relevant record in the system.
Document Management