The GDN: Your Digital Proof of Custody Handover

What a Goods Delivery Note is

A Goods Delivery Note — commonly abbreviated as GDN — is the document that records the transfer of physical goods from one custodian to another. In maritime operations, the GDN typically documents the handover of parcels from the ship agent to the vessel (or from the vessel to the agent for outbound cargo). It lists every item delivered, its description, quantity, condition at handover, and the identities of the parties involved.

The GDN is not a commercial document like an invoice or a bill of lading. It is an operational record — proof that a specific set of goods changed custody at a specific time, in a specific condition, witnessed by identified individuals. In the context of ship agency, it serves as the definitive record of what was delivered to or from the vessel during a port call.

This document matters because it is the primary evidence in any dispute about cargo custody. When a P&I club investigates a damage claim, when a customs authority audits a bonded goods transfer, or when a shipowner questions whether all ordered spare parts were actually delivered, the GDN is the document that answers the question.

Why the GDN matters for maritime operations

Every parcel that moves between shore and ship passes through multiple hands: the supplier or courier, the receiving terminal, the warehouse, the staging area, the launch or vehicle to the vessel, and finally the vessel's crew. At each transition, custody responsibility shifts. The GDN captures the most critical of these transitions — the formal handover between the agent and the vessel.

Without a reliable GDN, the ship agent has no proof of delivery. The captain may deny receiving certain items. The shipowner may claim that goods were damaged before they reached the vessel. The customs authority may question whether bonded goods were properly transferred. In each case, the agent bears the burden of proof, and the GDN is the instrument that carries it.

The GDN as a legal instrument

In many jurisdictions, the GDN has legal standing as evidence of custody transfer. Insurance claims, customs disputes, and commercial arbitrations all reference the GDN as a primary source document. Its legal weight depends on its completeness, accuracy, and verifiability — which is precisely where paper GDNs fall short.

The problems with paper GDNs

Paper-based GDNs have been the industry standard for decades. The process is familiar: the agent prepares a delivery list, prints it, has it signed at the point of handover, and files the signed copy. This process has four systemic weaknesses that become apparent during disputes.

Loss and deterioration

Paper documents get lost. They are misfiled, damaged by water (an occupational hazard in port environments), or discarded during office reorganizations. A GDN from a port call six months ago may simply not exist when a claim investigator requests it. For the agent, this is equivalent to having no proof of delivery at all.

Incomplete signatures

The value of a GDN depends on it being signed by the receiving party. In practice, captains are occupied during port calls and GDN signing is often deferred, delegated to a junior officer, or completed with a cursory initial rather than a full signature. An unsigned or partially signed GDN has significantly reduced evidentiary value.

No integrity verification

A paper GDN can be altered after signing. Items can be added to the list, condition notes can be changed, and quantities can be modified. While forensic analysis can sometimes detect alterations, the practical reality is that paper GDNs have no built-in mechanism to prove they have not been tampered with since the moment of signing.

Missing context

A paper GDN is a snapshot. It records what was delivered but not the full custody history leading up to the delivery. It does not show when the goods were received at the terminal, how long they were in the warehouse, who handled them at each stage, or what condition they were in at prior custody transitions. When a dispute arises, this missing context forces the agent to reconstruct the timeline from other sources — emails, warehouse logs, operator memory — which are incomplete and unreliable.

How a digital GDN works

A digital GDN is not a scanned copy of a paper form. It is a structured document generated automatically from the parcel custody data, enriched with the full timeline of events and secured with cryptographic integrity verification.

Automatic generation from custody data

In a digital custody system, the GDN is generated from the actual parcel records — not typed separately. Every item on the GDN corresponds to a parcel in the system with a complete event history. The descriptions, quantities, and condition notes are pulled directly from the custody chain, eliminating transcription errors and ensuring the GDN accurately reflects the operational reality.

A digital GDN can be generated from the moment a parcel reaches “Received” status, not only after staging or delivery. This means agents can produce a preliminary delivery note as soon as goods arrive at the terminal, updating it as the parcels progress through the custody lifecycle.

Custody chain timeline

Unlike a paper GDN that records only the handover moment, a digital GDN includes the full custody timeline for each parcel. When was it received at the terminal? Who received it? When was it moved to the warehouse? Which zone was it stored in? When was it staged for delivery? Who loaded it? When did the captain confirm receipt? Every event is listed with a precise timestamp and the identity of the operator who performed it.

This timeline is not supplementary information. It is evidence. When a claim investigator reviews the GDN, they can see the complete chain of custody from receipt to delivery, with no gaps and no ambiguity about who had responsibility at each stage.

Integrity hash

A digital GDN includes a cryptographic integrity hash — a unique fingerprint generated from the document's contents at the moment of creation. If any data in the GDN is modified after generation — an item added, a condition note changed, a quantity altered — the hash will no longer match, and the tampering is immediately detectable.

This is the digital equivalent of a tamper-evident seal. Any party with access to the verification mechanism can independently confirm that the GDN they are viewing is identical to the one that was generated at the time of the custody event. This level of integrity verification is impossible with paper documents.

Captain digital signature

The digital GDN captures the captain's confirmation as an authenticated, timestamped event tied to their identity. Unlike a handwritten signature that can be disputed or attributed to someone else, the digital confirmation is linked to the captain's authenticated session and recorded in the immutable audit trail.

How SeaPillar generates and verifies GDNs

SeaPillar generates the GDN directly from the parcel custody chain. When a parcel reaches Received status, a GDN can be produced that includes all items at that stage or beyond. The document includes the full event timeline, per-parcel condition notes, photographic evidence where attached, and the captain's confirmation status.

Each GDN carries an integrity hash that can be verified through the platform. When an insurer, customs authority, or shipowner receives a SeaPillar GDN, they can confirm its authenticity and verify that no data has been altered since generation. The GDN is available as a printable document for parties who require a physical copy, with the integrity hash printed as a verifiable code.

For ship agents, this means the GDN is no longer a document they have to prepare, chase signatures for, and hope they can find months later. It is generated automatically from the data they are already capturing as part of normal operations, secured with cryptographic verification, and available instantly whenever it is needed. The custody record speaks for itself.