Delivery Note Template for Hauliers and Container Operators
Build a delivery note template that speeds up invoicing for hauliers and container operators. Includes required fields, container moves, and TMS integration
The truck has arrived, the goods are on the customer's site, and the driver believes the job is finished. Then the receiver disputes the quantity, the signature is missing, or the only paperwork is a blurred photograph with no job reference. Operations starts calling the driver, finance holds the invoice, and a completed movement turns into an avoidable query.
A delivery note template should prevent that chain of events. For hauliers and container operators, it's not merely a printable list of goods. It's the control record that connects the order, the physical handover, the proof of delivery, the exception, and the invoice. A long-established delivery note records what was sent, including descriptions, quantities, size, and weight, and accompanies the shipment through loading and final delivery workflows, as explained in this delivery note overview for logistics teams. Modern electronic POD records now sit alongside signed paper forms in the same proof-of-delivery framework.
Table of Contents
Why the Right Delivery Note Template Speeds Up Haulier Invoicing
A familiar failure starts at the customer's gate. The driver obtains a signature, but the receiver later says that one pallet was missing. The signed sheet doesn't show the order number, the delivered quantity is indistinguishable from the planned quantity, and nobody recorded whether the packaging was intact. The invoice desk has a completed journey, but not a defensible delivery record.
A structured delivery note changes the handover. Before departure, it carries the job number, customer, collection and delivery addresses, goods description, planned quantity, pallet count, weight, and reference to the order. At the destination, the driver records the actual quantity, arrival time, receiver identity, signature, and any reservation. That distinction matters because a delivery can be complete, partial, refused, or attempted. Treating every outcome as “delivered” creates billing and customer-service problems.
Make every field answer a billing question
The useful test is simple. If a field doesn't help someone answer what moved, where it went, when it arrived, who accepted it, or what went wrong, it probably shouldn't delay the driver.
A good note lets the transport management system match the physical handover to the correct job. It gives accounts payable a usable attachment for invoice approval. It gives operations a clear exception to investigate instead of a vague message saying “customer queried delivery.” Guidance on proof-of-delivery records and payment delays identifies disputed or missing delivery documentation as a major cause of late settlement, and defines POD performance around completed deliveries supported by signed paper or electronic records.
The practical handoff should be:
- Dispatch: Generate the note from the job and prefill known details.
- Delivery: Capture quantities, condition, time, receiver, signature, and reservations.
- Operations: Sync the completed record back to the job.
- Finance: Release or query the invoice based on POD status.
Teams reviewing their wider shipping processes can also use Arete Global Shipping Services as a practical logistics resource. For a deeper look at the billing handoff itself, see this guide to speeding up transport invoicing.
Required Fields Every Delivery Note Template Must Carry
Build the form around traceability, not just driver convenience. A driver needs a note that can be completed quickly, while operations and finance need enough structured information to identify the job months later.
Start with identifiers and movement details
The header should contain a unique delivery note number, issue date, job or order reference, customer account, supplier, carrier, and vehicle registration. These identifiers connect the document to the TMS record, the customer's order, and the eventual invoice. Sequential or controlled numbering also makes missing records easier to detect.
The route section should show the collection party, delivery party, full addresses, scheduled timing, and actual arrival or departure times. Don't rely on a customer name alone. Sites with multiple warehouses, gates, or operating companies need a precise location reference.
The load description must be specific enough for a receiver to confirm it. Record the goods, package type, planned quantity, delivered quantity, pallet or unit count, weight, seal number, and any consignment reference. For restricted goods, include the relevant hazard information and handling instructions rather than forcing the driver to consult a separate document at the gate.
Make acceptance and exceptions separate
The handover area should identify the driver, receiver, receiving company or role, signature, date, and time. A signature without a clear statement of what was accepted has limited value. The template should show planned and delivered quantities separately, then provide a visible reservation field for shortages, damage, packaging problems, waiting time, access restrictions, or refusal.
Include delivery status options such as:
- Delivered in full: The receiver confirms the stated goods and condition.
- Partially delivered: The delivered quantity and undelivered balance are recorded.
- Attempted delivery: The reason, arrival time, and next action are captured.
- Refused delivery: The receiver's reason and return instruction are documented.
- Returned goods: The return quantity, condition, and receiving party are entered.
Add space for photographs and attachments. Practical template guidance recommends a unique number, supplier and recipient identifiers, itemized descriptions and quantities, and a signature area, while also warning against vague descriptions, missing addresses, and uncontrolled numbering in delivery note template instructions.
| Field group |
Fields to include |
Operational purpose |
| Control identifiers |
Delivery note number, issue date, job number, order reference |
Links the handover to the TMS, customer order, and invoice |
| Parties |
Supplier, carrier, customer, collection party, receiver |
Establishes who arranged, transported, and accepted the movement |
| Route and timing |
Collection address, delivery address, scheduled time, actual times |
Supports traceability, service review, and waiting-time queries |
| Load |
Description, package type, planned quantity, delivered quantity, weight |
Enables order matching and discrepancy review |
| Vehicle and security |
Registration, driver, seal or consignment references |
Connects the document to the equipment and shipment |
| Acceptance |
Receiver name, role, signature, date, time |
Records who accepted the goods and when |
| Reservations |
Damage, shortage, refusal, access issue, waiting time |
Captures exceptions at the point of handover |
| Evidence |
Photos, attachments, return details, delivery status |
Strengthens POD review and invoice decisions |
Adapting the Template for Container Moves and Port Work
A general haulage note follows goods. A container-move note must follow an equipment identity and a chain of port events. The job number and parties still matter, but they aren't enough once a movement passes through a terminal, quay, depot, and customer gate.
The container section should carry the container number, ISO size and type, seal number, vessel and voyage, bill of lading reference, terminal, berth or stack information, and release or booking reference. State the movement type clearly, such as port to depot, depot to customer, customer to port, or intermodal transfer. The next expected event should be visible, because a driver completing a port delivery may be handing the unit into a depot rather than completing the customer's overall transport obligation.
Stack the port fields onto the base template
For a laden export, add verified gross mass, cargo description, and the shipping documents required for the movement. For an import, capture discharge reference, availability status, terminal-out time, inspection requirements, and whether stripping is expected. Gate-in and gate-out timestamps should identify the terminal, depot, or customer receiving the container.
The condition section deserves more attention than it receives in standard templates. Capture photographs of the container on arrival, including doors, floor, roof, sides, and seal condition. Record dents, rust, holes, contamination, and previous damage in the reservations area. If a seal is replaced, record the old and new numbers and who authorised the change.
| General haulage note |
Container-move note |
| Goods description and quantity |
Container number, size, and type |
| Customer delivery address |
Terminal, depot, quay, or gate identity |
| Receiver signature |
Gate-in or gate-out confirmation |
| Package or pallet condition |
Container structure, doors, floor, roof, and seal condition |
| Order reference |
Booking, release, vessel, voyage, and bill of lading references |
| Delivery status |
Availability, inspection, stripping, empty return, or repair status |
Empty returns also need a meaningful outcome. “Returned” doesn't distinguish a clean release from a depot hold or repair condition. Container operators comparing risk arrangements can compare logistics insurance quotes online, while teams reviewing the operating model should understand what drayage means in trucking. The delivery note won't replace interchange documentation, but it should carry the references that let people reconcile the two records.
Legal Weight, Retention Rules, and Evidence Strength
A signed delivery note can help establish that a handover occurred, but it doesn't automatically settle every liability question. Its strength depends on what the receiver signed, whether exceptions were recorded at the time, and whether the document can be connected to the correct consignment.
A clean POD with a named receiver, signature, date, time, quantity, and condition is stronger than a signature on a blank or generic sheet. A note with a written reservation can protect the haulier from being treated as responsible for a visible shortage or damage that the receiver acknowledged at delivery. An unsigned copy reconstructed from driver messages or vehicle logs may support an investigation, but it's weaker evidence of acceptance.
Retain the record that explains the invoice
The delivery note should be archived with the job and invoice, using the delivery note number as the common reference. Accounts teams may need to produce proof of receipt long after the vehicle has left the site, so scanning a paper note immediately or syncing an electronic record at completion is more reliable than leaving photographs in a driver's phone.
For container work, the delivery note also needs to sit beside the relevant interchange receipt, terminal record, or other equipment handover document. The note can show what happened during the road movement, but it shouldn't be presented as a substitute for the CMR or bill of lading where those documents allocate transport or cargo liability.
Practical rule: A delivery note proves the handover you recorded. It doesn't repair a missing exception, replace a contract document, or establish facts that nobody captured at the gate.
| Capture state |
Chargeback defence |
Audit trail |
Liability proof |
| Signed, complete, clean POD |
Strong for recorded quantity and acceptance |
Clear link to job and invoice |
Supports handover, not every contractual liability |
| Signed with written reservations |
Stronger where the exception is specific |
Shows when and where the dispute arose |
Helps allocate visible damage or shortage questions |
| Unsigned note with complete delivery data |
Limited, depends on supporting records |
Useful if linked to driver and job records |
Shows operational activity, not clear acceptance |
| Reconstructed copy from logs |
Weakest for acceptance disputes |
Can support an internal investigation |
Doesn't independently prove condition or receiver approval |
Driver Capture Best Practices at the Point of Handover
The driver shouldn't have to improvise the evidence sequence. A short, consistent capture routine produces better records than a long form with optional fields that drivers skip under pressure.
Use the following order at the delivery point:
- Approach: Confirm the correct site, job reference, container number, or consignment.
- Park: Record arrival and, where relevant, the waiting or access condition.
- Verify: Match the container or pallet count to the delivery note and check the seal reference.
- Inspect: Look for visible damage, shortage, packaging failure, or signs of tampering.
- Hand over: Give the receiver the goods or equipment and confirm the actual delivered quantity.
- Capture: Record reservations, take photographs, obtain the signature, and close the status.
The driver application should prompt for the information that's easy to miss. It should require confirmation of the container number or pallet count, check the seal against the consignment, attach the timestamp and location, and keep the damage or shortage field visible before the signature screen appears.
Specific reservations beat vague comments
“Damage” doesn't tell the claims team enough. “Two cartons crushed on the top layer, outer packaging split” gives operations a usable starting point. For a container, “dent on right door, seal intact, photograph attached” is far more useful than “container damaged.”
A practical photo sequence should include:
- Arrival condition: Show the load or container as it appeared before unloading.
- Security condition: Capture the seal, doors, or relevant securing arrangement.
- Completion evidence: Photograph the signed note or final handover screen.
The driver shouldn't close the job until the system shows signed or refused. If the receiver won't sign, the driver should record the refusal, name the reason where available, capture supporting evidence, and notify dispatch before leaving. A refusal is an operational outcome. Hiding it as a completed delivery creates a larger problem for billing and dispute handling.
Connecting the Note to Your TMS, POD, and Invoicing Workflow
The delivery note works best as a state change, not a file that someone uploads. The TMS creates the job, the note carries the order data to the driver, the driver captures the handover, and the completed record returns as proof of delivery.
The closed loop should look like this:
- TMS job creation: Operations enters the customer, route, goods, references, and chargeable services.
- Delivery note generation: The system creates a prefilled note linked to the job.
- Driver capture: The driver confirms the movement, records exceptions, adds evidence, and obtains signature or refusal.
- POD completion: The note syncs back with status, timestamps, photographs, and receiver details.
- Invoice trigger: Finance releases a clean completed job or routes a disputed record into a query queue.
Remove the handoffs that create rekeying
The common failures are predictable. Someone manually types a POD reference into an accounting system, an exception flag prevents invoice generation without telling anyone why, or container interchange data remains in a separate port platform with no shared reference. Each gap forces a planner, administrator, or finance clerk to reconcile records by hand.
A useful workflow has two invoice outcomes:
- Clean completion: The POD is signed or otherwise accepted, required evidence is present, and the invoice can move forward.
- Exception completion: The system records the job as delivered with a query reason, then holds or adjusts the invoice according to the agreed process.
That distinction is better than an all-or-nothing rule. A partial delivery may still support a legitimate invoice for the completed work, while a missing seal record or disputed damage may require review.
This short video provides a visual introduction to connected transport workflows:
Measure the loop using days from delivery to invoice and POD query rate as a percentage of jobs. Those measures expose whether the template is helping cash collection or producing more documents. Teams evaluating ways to accelerate invoicing in haulage should also consider whether the note is linked to the invoice automatically. Where paper and mixed formats remain, AI document extraction for transport records can reduce rekeying, provided the extracted fields are validated against the job.
Habits That Keep Your Delivery Note Template Working Long Term
A well-designed template fails if drivers use old carbon-copy books, planners omit the job reference, or finance accepts incomplete photographs. Long-term performance comes from a small operating discipline that people repeat on every movement.
Audit the fields that affect disputes
Review disputed jobs regularly and ask which missing field caused the query. If shortages keep appearing without delivered quantities, make that field prominent. If container damage is being reported without photographs, change the capture sequence rather than adding another paragraph of instructions.
A quarterly field audit should include:
- Dispute comparison: Check recent queries against the fields captured on the note.
- Template ownership: Give one named person responsibility for revisions and approval.
- Version control: Date each change and remove obsolete versions from driver devices.
- Driver refreshers: Train against the exception categories appearing in the TMS.
- Evidence checks: Confirm that photographs, signatures, refusals, and reservations remain retrievable.
Keep the form lean enough to use
More fields don't automatically produce better evidence. A driver who must scroll through irrelevant questions is more likely to skip the important ones. Keep fields tied to billing, proof of handover, liability, or operational control, and make conditional fields appear only when the movement requires them.
Adoption matters more than decoration: A plain template completed consistently is more valuable than a sophisticated form that drivers bypass.
For next week, dispatch teams can adopt a short list of firm rules. Require a photo and a signature or written reservation before closing a delivery. Require a GPS-tagged timestamp on every electronic capture. Retire legacy books once the replacement workflow has been tested. Review the main dispute causes every month, then change the template only when the evidence shows a real gap.
Logivo provides transport management workflows for hauliers and container operators, including job planning, driver briefing, digital delivery note and POD capture, attachments, timestamps, and invoice linkage. Visit Logivo to see how a connected workflow can turn the delivery note from a loose document into a controlled billing record, then assess it against your current TMS and invoice process.