Proof of Delivery Template: Record Receipt, Condition and Exceptions

A proof of delivery template records the transfer of a defined shipment at a defined time. A useful record identifies what was handed over, to whom, where, in what visible condition and with which exceptions, without turning a signature into a claim about facts nobody checked.

Use the governing contract, carrier process, customer instructions, privacy rules and applicable law to define what evidence is required. This template is an operational starting point, not legal advice.

Define what the acknowledgment proves

State the event being acknowledged: delivery attempt, package handoff, count verification, visible-condition review or another defined milestone. These are not interchangeable. A recipient may confirm receipt without opening every package or validating every item.

Define who can acknowledge delivery and which alternatives are permitted, such as an authorized receiving role, controlled unattended delivery or carrier exception code. Avoid language that makes the recipient certify concealed condition, technical conformity or commercial acceptance unless the applicable process genuinely requires and supports it.

Name the carrier record owner and the customer-side owner for exceptions. Set escalation triggers for missing identity, count mismatch, damage, refusal, wrong location or unavailable recipient.

Define whether the proof of delivery is the original record, a customer copy or a status message derived from another system. Keep these forms distinguishable. A notification that says “delivered” should point to the underlying acknowledgment and should not contain broader claims than that evidence supports.

Copy this proof of delivery template

PROOF OF DELIVERY RECORD

SHIPMENT
Delivery / shipment / order reference:
Sender / carrier / service:
Delivery location:
Vehicle or route reference, if required:

HANDOFF
Arrival / handoff date and time:
Package, pallet or item count:
Seal or handling-unit references, if applicable:
Visible condition at handoff:
Recipient name or approved identifier:
Recipient role / organization:
Acknowledgment method:

EXCEPTIONS
Shortage / overage / damage / refusal / access issue:
Affected package or item identifiers:
Factual notes and evidence references:
Immediate action / notification / owner:

RECORD CONTROL
Carrier representative or system record:
Recipient acknowledgment:
Correction history:
Storage link / access / retention class:

Collect only the identity information required by the process. Do not use a generic form as a reason to capture unnecessary personal data.

Match the record to the shipment

Use stable shipment, order and delivery references. Confirm the destination and package or pallet identifiers against the current transport record. If a shipment is split, consolidated or partially delivered, show which handling units are covered by this acknowledgment.

Where a route includes cross-docking, collection points or multiple custodians, record the specific handoff represented by each acknowledgment. Do not merge intermediate transfer and final customer delivery into one status. Link related records in sequence so an investigator can follow custody without assuming that every participant inspected the same scope or condition.

Record carrier, service, vehicle or route data only where needed for traceability. The delivery record should connect back to the authorized dispatch evidence without duplicating every commercial document.

The delivery exception report template provides a fuller structure when the shipment, destination or physical count does not agree. Preserve the original observation before correcting downstream systems.

Record time, place and recipient appropriately

Capture arrival, attempted-delivery and handoff times separately when they matter. Use the system’s controlled timezone and timestamp conventions. A generated timestamp may show when a form was submitted rather than when custody changed, so label the source.

Identify the location precisely enough to support the transaction without exposing unnecessary security detail. For recipient identity, follow contractual and privacy requirements. A role, employee identifier or other controlled method may be more appropriate than an unrestricted image of personal identification.

If the person lacks authority or identity cannot be confirmed under the approved method, record the limitation and follow the exception route. Do not pressure someone to sign a statement they cannot verify.

Where language, accessibility or device limitations affect acknowledgment, follow the approved alternative process and preserve what assistance was provided. Do not ask a driver or recipient to improvise a substitute signature on behalf of another person unless the governing process explicitly permits it.

Count handling units and note visible condition

Record the unit actually checked: pallets, cartons, parcels or serialized items. “One delivery” does not reveal whether all expected packages arrived. Reconcile the count to the shipping record and state when packages were not individually accessible.

If seals are part of the process, record the identifier and visible status before opening or transfer. A matching seal supports continuity only within the limits of the approved control; it does not establish item condition or quantity by itself.

Describe visible condition factually. Note crushed corners, torn wrap, wet packaging, broken seals or other direct observations with affected identifiers. Avoid diagnosing concealed product damage from exterior appearance alone.

Use photographs when authorized and useful, but frame them to avoid unrelated people, addresses, access controls and private interiors. Record who captured the image and when. A photograph supplements, rather than replaces, a clear written exception.

Handle partial, refused and unattended deliveries

For partial delivery, list accepted and missing handling units, the recipient’s acknowledgment scope and the next action. Do not issue one unqualified “delivered” status for goods that remain with the carrier.

If the recipient accepts some packages with reservation, capture the reservation in clear factual language and identify the affected units. Provide the required copy or notice through the approved channel. Avoid forcing a binary accepted or refused choice when the actual event is qualified receipt, but do not invent a local status that downstream billing or claims systems cannot interpret.

If delivery is refused, record the stated reason as reported, shipment condition, time, location and instructions received. Preserve the goods under the carrier’s approved process and notify the responsible owner. Do not infer customer intent beyond the available facts.

For unattended delivery, use only approved locations, evidence and notice methods. A doorstep image does not automatically establish recipient possession or eliminate later investigation.

Document exceptions without changing the facts

Create an exception record for count differences, visible damage, seal problems, incorrect location, access failure, refusal or disputed identity. Identify affected items, immediate containment, evidence, notifications and ownership.

Keep original entries and corrections traceable. If a package count was entered incorrectly, preserve the initial record, corrected value, reason, author and time. Never alter a signed record silently to make it agree with a transport system.

The inventory discrepancy report template can support the receiving-side investigation when delivered quantity and expected stock diverge. The proof of delivery establishes the handoff record, not the root cause.

Connect delivery to receiving and service records

The receiving process should reconcile the acknowledged shipment to expected goods, inspect according to applicable procedures and post authorized transactions. Keep concealed damage, quality inspection and commercial acceptance as separate decisions where the process distinguishes them.

Record when the receiving check occurs later than carrier handoff and which custody controls apply in between. This distinction helps reviewers assess later-discovered shortages or damage without assuming that the proof of delivery alone identifies when an issue arose.

Use a field service report template when delivery is part of a visit that also includes installation, testing or customer instruction. A delivery signature should not be repurposed as technical acceptance of work.

For installed equipment, the installation completion report template provides a more appropriate record of scope, tests, exceptions and handback. Link related records instead of asking one signature to cover incompatible purposes.

Protect electronic evidence and privacy

Electronic proof of delivery should preserve identity method, timestamps, record version, access and correction history under the applicable system. Restrict who can edit or delete completed acknowledgments. Retain records according to contractual and organizational requirements.

Test offline synchronization and duplicate handling where mobile devices are used. A delayed upload should retain the original event time and distinguish it from synchronization time. Review failed or conflicting uploads rather than accepting whichever copy appears last.

Signatures, addresses, location data and images may be personal or security-sensitive. Collect the minimum necessary, provide required notice and limit access. Avoid sending unrestricted copies through informal messaging channels.

For authorized delivery reviews with visible, consented capture, Kuno can organize discussion into draft notes and follow-ups for human verification. It does not validate signatures, determine liability or resolve contractual disputes. Explore Kuno

Review disputes and improve the process

When a delivery is disputed, gather the original dispatch, transport, location, count, condition and acknowledgment records. Preserve uncertainty and ask the authorized operational, commercial, insurer or legal roles to interpret the evidence. Do not state that one scan conclusively proves liability.

Build an event timeline using source timestamps and label their origins. Distinguish planned delivery, vehicle arrival, scan, handoff, upload, notification and later inspection. Check for timezone or offline-device differences before deciding that records conflict. Keep hypotheses separate from established facts and record which additional evidence has been requested, who owns the review and when the next decision is due.

Review recurring failed deliveries, missing packages, unclear signatures, late uploads and damage reports. Separate master-data, packing, carrier, receiving and system causes before assigning actions. Use the client status report template pattern when stakeholders need a concise separation of facts, current effect and next decisions.

Final QA should let an authorized reviewer identify the shipment, handoff event, acknowledgment scope and visible exceptions. The record is strongest when it says precisely what was and was not verified.

Keep delivery follow-ups reviewable without overstating the evidence. Kuno supports authorized capture and draft action notes; logistics, customer and commercial owners verify facts and decide outcomes. See Kuno

FAQ