Signed, photographed and stored before the driver leaves the site.
Proof of delivery is the evidence that connects the job to the invoice — and protects you in a dispute
In bulk haulage, proof of delivery serves four distinct purposes. Understanding each one clarifies why a timestamped digital record is meaningfully better than a paper signature on a docket that ends up in a filing cabinet.
Dispute resolution
When a client claims a delivery did not happen, was short, or was at the wrong location, the POD is your primary evidence. A photograph of the delivered material at the correct address, timestamped and geotagged, is a substantially stronger record than a paper docket that you are relying on someone to have kept. A customer signature captured digitally is harder to dispute than a handwritten mark on a form that may have been processed days later.
Invoice evidence
Before you send an invoice for a delivery, you need confidence that the delivery was completed as specified. Digital POD gives your billing team that confidence without requiring them to call the driver or locate a paper docket. The invoice follows immediately from the completed job record because the evidence is already attached.
Client satisfaction
Large clients managing multiple sites and multiple haulage suppliers will ask for delivery records. Being able to give a client self-service access to their POD — through the client portal, without a phone call or email — is a material operational advantage over operators who have to dig through a filing cabinet for a copy.
Compliance and audit readiness
An audit trail of delivery records — what was delivered, when, where, and who confirmed receipt — is relevant to Chain of Responsibility compliance and to any contractual obligation to demonstrate delivery performance. A complete, timestamped digital record supports audit readiness in a way that paper filing cannot.
JOB-1844 — Apex Civil
Driver: L. Chen · Status: Delivered · Completed 14:23
Delivery photograph
Timestamp overlay "14:23 Monday" — tap to expand
AttachedCustomer signature
J. Williams — Site Supervisor · drawn on screen
AttachedScale ticket
PDF thumbnail · upload timestamp · tap to open
AttachedFinance team sees this view before generating the invoice — POD present, rate confirmed, ready to bill.
POD is captured before the truck moves:
- Photograph taken at the delivery point
- Signature collected from the receiving party
- Any document uploaded while still on site
- All three attached to the job record immediately
Three capture types — all on the driver's phone, all attached to the job
Delivery photograph
The driver uses the phone camera within the HaulageOps driver app to take a photograph at the point of delivery. This typically shows the delivered material at the delivery address — the aggregate tipped at the correct stockpile, the spoil deposited at the designated area, the materials placed at the site entrance. The photograph is timestamped with the time of capture and geotagged using the device's location services. It uploads to Azure Blob Storage and attaches directly to the job record in the admin panel and client portal.
Customer signature
The receiving party — a site supervisor, a weighbridge operator, a site manager — signs directly on the driver's phone screen within the driver app. This is a digital signature capture: the person draws their signature using their finger on the touchscreen, not a handwritten mark photographed from paper. Their name is entered alongside the signature. The signature image is stored in Azure and attached to the job record as part of the POD. It is visible in the admin panel and in the client's portal.
Document upload
Where a physical document exists at the delivery site — a scale ticket from the weighbridge, a site delivery receipt, a permit check record — the driver photographs it within the driver app and uploads it as a document attachment. The document is stored in Azure Blob Storage, named with the job reference and upload timestamp, and attached to the job record alongside the delivery photograph and signature. It becomes part of the complete POD record for that delivery.
How POD flows from delivery site to admin panel to client portal
Driver marks job delivered
In the driver app, the driver navigates to the active job and marks it as Delivered. This triggers the POD capture workflow within the same screen — the driver does not need to navigate elsewhere or remember a separate step.
Photograph captured
The driver takes a photograph of the delivery using the in-app camera. The timestamp and GPS coordinates are recorded automatically. The photograph is compressed appropriately for mobile upload without losing the visual detail needed for dispute purposes.
Signature collected
The driver hands the phone to the receiving party, who enters their name and signs on the screen. The signature is captured as a vector drawing — not a photograph of a handwritten signature — and stored as part of the POD record. The driver takes the phone back when complete.
Document uploaded (if required)
If a scale ticket or delivery receipt exists on paper, the driver photographs it through the document upload function and submits it. The document attaches to the same job POD record as the photograph and signature.
Upload to Azure
All three captures upload to Azure Blob Storage. If the site has no connectivity, the uploads queue locally and complete automatically when signal is available. The driver does not need to take any action — the sync is handled by the app.
Available instantly across portals
Once uploaded, the POD is visible in the admin panel against the job record, and in the client portal for that client's jobs. Finance sees the POD before generating the invoice. The client can view and download their delivery records without contacting your team.
The complete chain — job, POD, invoice, payment
POD is not a standalone feature — it is the link between the completed job and the invoice that can be issued without dispute. In HaulageOps, the chain is connected throughout:
- Job created with rate attached — at dispatch, not at invoice time
- Driver completes delivery — status updates to Delivered in real time
- POD captured at site — photo, signature, document all attached to job
- Finance reviews job record — POD visible, rate confirmed, ready to invoice
- Invoice generated from completed job — no re-entry, no reconstruction
- Invoice syncs to Xero via OAuth2 — automatically, on cron or real-time webhook
- Client sees invoice in their portal — with POD evidence already alongside it
- Payment received in Xero — webhook updates invoice status in HaulageOps
At no step in this chain does someone need to retrieve a paper document, call a driver, or cross-reference a separate spreadsheet. The POD is the piece that connects the operational record to the billing record — and in HaulageOps, it is captured at the point where it actually happens.
Rate attached at creation
Photo + signature + document
Generated from job + POD
Synced, payment status
Invoice + POD visible
One record links all five — no broken links, no separate systems, no manual re-entry.
What the comparison actually looks like in practice
| Situation | Paper signature / manual process | HaulageOps digital POD |
|---|---|---|
| POD captured | Driver collects paper signature on docket at delivery. Docket stays in the cab. | Driver captures photo + signature + document in app. Uploaded to Azure before leaving site. |
| POD available to admin | When driver returns. Could be same day, could be days later. | Immediately after upload — in some cases before the driver has left the delivery site. |
| POD available to client | Client calls requesting copy. Admin scans and emails. May take several days. | Client views their POD in their self-service portal — no contact with your team required. |
| No mobile signal at site | Paper docket unaffected by signal — but carries all the usual handling risks. | Driver app works offline. Captures queue and upload automatically on reconnect. |
| Client disputes delivery | Retrieve paper docket from filing. Hope it is legible. Hope it is the right one. | Timestamped photograph, named signature, and GPS record retrieved instantly from Azure. |
| Finance generates invoice | Waits for docket. Re-enters job details. Attaches scanned docket manually. | POD already attached. Invoice generated from job record. Nothing to re-enter. |
| Audit or compliance review | Pull physical files. Records may be incomplete or misfiled. | Full delivery record retrievable by job, date, client, or driver — complete chain of custody in Azure. |
Proof of delivery — common questions.
What format are the delivery photographs stored in?
Delivery photographs are captured via the phone camera within the driver app and stored in Azure Blob Storage as image files (JPEG). They are timestamped at the point of capture, geotagged where location services are available, and attached to the job record by reference. They can be viewed directly from the admin panel or client portal and downloaded by authorised admin users.
Can the client download their POD from the portal?
Clients can view their delivery photographs, signature records, and uploaded documents in the client portal. The ability to download individual files depends on your portal configuration. The client portal provides self-service visibility — the primary outcome is that clients stop contacting your admin team for POD copies because they can see the records directly.
What if the receiving party refuses to sign?
If a customer declines to sign at the delivery site, the driver can complete the POD workflow with the delivery photograph and document upload without a signature. The absence of a signature is noted rather than forcing an incomplete record. The delivery photograph and timestamp still constitute a record of delivery. If signature refusal is a regular occurrence for a particular client site, this is a commercial relationship issue that your team would need to address separately.
How is storage handled — is there a limit on how many POD records we can keep?
POD records are stored in Azure Blob Storage as part of your HaulageOps subscription. There is no manual file management required on your end — the system handles storage against the relevant job records. For specific questions about storage limits at your expected job volume, contact us when discussing your subscription configuration.
Does POD capture work when the driver is using subcontractor capacity?
Yes. When a job is delegated to a subcontractor and the sub's driver completes the delivery, the POD capture workflow operates the same way in the driver app. The captures upload to Azure and attach to the job record in your admin panel, where your dispatch and finance teams can see them. Your client's portal also shows the POD regardless of whether your driver or a subcontractor's driver made the delivery.
Does the app require the driver to capture all three POD elements, or are some optional?
The required elements of POD capture can be configured to match your operational requirements. In practice, the photograph is the most universally captured element. Signature capture depends on whether the delivery site has an authorised person available to sign. Document upload applies when a physical document exists at the site. The system allows the driver to complete POD with the elements that are available at that delivery point rather than blocking completion when a signature is not obtainable.
Is the digital signature capture legally equivalent to a paper signature?
The legal standing of electronic signatures varies by jurisdiction and context. HaulageOps captures a named digital signature — drawn on screen by the receiving party — alongside a timestamped photograph and GPS record. This creates a stronger evidentiary record than a paper signature on a docket processed days later. For specific legal questions about your jurisdiction and contract requirements, consult your commercial or legal advisors.
POD connects to these features and solutions
Driver App
The iOS and Android app used by drivers to receive jobs, update status, and capture POD — offline-capable, with Firebase push notifications for job alerts.
Driver App detailDigital Dockets
Digital dockets as the broader delivery record concept — what they replace, how the capture workflow works, and how they attach to jobs for immediate availability.
Digital DocketsJob to Invoice
The full billing workflow — how the POD-confirmed completed job record becomes an invoice and syncs to Xero without re-entry at any step.
Job to InvoiceClient Portal
How clients access their own jobs, POD records, invoices, and rate cards through a dedicated self-service portal — reducing inbound queries to your admin team.
Client Portal