Delivery Proof Record Template for Freight

What A Delivery Proof Record Should Establish

A delivery proof record is the operational note that connects a freight movement to the moment a receiving party takes possession or records a variance. It is more useful than a single delivered status because it shows which shipment arrived, where it arrived, when the handoff occurred, what was counted, what condition was visible and what still needs a decision. This guide is for importers, forwarders, suppliers and warehouse teams that need a repeatable receiving record.

The Federal Maritime Commission describes ocean transportation intermediaries as parties that arrange or facilitate transportation services. That boundary is useful here: a provider can report an arranged handoff and its evidence, while the receiving team confirms the physical result. Keep both roles visible so a transport update is not mistaken for acceptance of every warehouse task. Use the record to define the handoff, not to promise a universal delivery outcome.

• Shipment reference, delivery boundary and receiving location.
• Actual handoff time, time zone and accepting contact.
• Expected quantity, observed quantity, condition and open action.

Build A Stable Header Before The Handoff

Put the stable identifiers at the top of the template so a later reviewer can match the record to the shipment file. Include the internal shipment reference, supplier or origin label, receiving company or site, delivery boundary, planned appointment reference, record version, prepared time and reporting time zone. Use a controlled contact name or team mailbox rather than copying private phone numbers into every distribution list.

Write the service boundary in plain language. For example, state whether the record covers a carrier handoff at a warehouse, a provider's delivery to a site, or a receiving team's internal put-away step. The International Chamber of Commerce publishes Incoterms rules as a shared vocabulary for commercial tasks, costs and risks, but a named term does not replace the practical boundary in this particular record.

• Keep one reference unchanged from dispatch through receiving.
• State the location, appointment, version time and time zone.
• Describe what this record confirms and what it does not cover.

Record Expected, Observed And Pending Quantities

Use separate fields for the quantity expected from the shipping record, the quantity physically observed at receiving and the quantity still being checked. List cartons, pallets, crates or loose pieces in the same unit language used in the packing record. If a pallet contains mixed cartons, show both the pallet count and the carton count instead of collapsing them into a single total that another team cannot reconcile.

Ask the receiving contact to confirm whether the count was made before unloading, during unloading or after the freight was moved into a storage area. The timing changes what the observation proves. If one package is inaccessible or a count is based on a carrier message, mark the field pending and assign the next check. Never fill a missing quantity with the planned number simply to close the form.

Describe Visible Condition Without Guessing Cause

Condition notes should describe what a person could see at the handoff: intact or broken wrapping, a wet carton, a crushed corner, an open closure, a missing label or a visible count difference. Add the affected package or pallet reference and the location in the receiving area. If an image is useful, connect it to the same shipment reference and record version so it does not become an orphaned camera file.

Avoid declaring who caused a condition from a delivery image alone. Write the visible fact, the time it was observed and the immediate action, such as isolating the package, asking for a second count or notifying the provider. Incoterms can allocate commercial tasks and risks, but the receiving note should remain an operational observation and send responsibility questions to the agreed review process.

• Name the affected unit and the exact visible condition.
• Pair close detail with enough context to identify the handoff.
• Separate what is visible from what still needs investigation.

Use A Handoff Decision Table

The table below keeps the record decision-ready without turning it into a claim form. Choose the smallest next action that resolves the open field or protects the receiving plan. If a variance could change a later warehouse appointment or delivery scope, name the decision owner before the record is distributed more widely.

The International Maritime Organization's maritime framework is a useful reminder that a receiving record sits inside a chain of connected handoffs. Show the next operational step, not only the moment a vehicle reaches the gate. The downstream action may be a second count, a controlled move to inspection, a revised appointment or a provider update.

Capture The Receiving Contact And Evidence Location

The receiving contact should be a real operational owner, not only the name of the person who forwarded the delivery message. Record the person or team, local time, site or dock reference, appointment number when relevant and the location of the signed note, scan or image set. If a system generates the proof, keep the system reference and the human reviewer who checked it.

Use the same evidence location in the status update, warehouse record and provider handoff. A linked file should tell a later reviewer which version is authoritative and whether it is an original, a crop or a derivative. Protect unrelated private information in images and documents, and grant access only to the teams that need the record for the shipment decision.

• Name the accepting contact, team and local handoff time.
• Store the signed note, scan or image index beside the record.
• Label the authoritative copy and any controlled derivative.

Close Exceptions And Preserve The Change History

An exception is closed when the physical fact, owner and next action are recorded, not when the message thread becomes quiet. Add the original observation, the action taken, the decision time and the final result. If a second count changes the quantity, keep both values and explain why the final value superseded the first. This makes the record useful for the next delivery and for internal process review.

When a provider, warehouse or supplier changes a material fact, issue a new record version rather than editing the sent copy. Show the changed field, the reason for the change, the person who approved it and the next handoff affected. The connected-handoff view from the International Maritime Organization is a practical reminder that one receiving change can affect storage, onward transport or an appointment.

• Keep the first observation beside the resolved result.
• Record changed field, reason, approver and affected handoff.
• Close only when the final owner and evidence are visible.

Conclusion: Make Delivery Proof Easy To Reconcile

A delivery proof record template works when it gives every reader the same factual handoff: shipment reference, boundary, location, actual time, expected and observed quantity, visible condition, receiving contact, evidence and next action. Keep planned and actual fields separate, use neutral language, and preserve a clear version history when something changes. That structure reduces repeated questions without claiming that a single delivery message proves every downstream task is complete.

Before requesting a quote or confirming the next movement, share the route, package data, receiving point, appointment needs and the evidence your team expects. Punctual Logistics can help align door-to-door, warehousing and delivery scope around one practical record. The final proof should make the next decision easier, whether the result is accepted, pending or escalated.

• Lead with the handoff facts a later reviewer must reconcile.
• Give every variance an owner, due time and evidence reference.
• Use the completed record to improve the next freight plan.

Frequently asked questions