Direct answer
Each shipment needs its own checklist of the documents it requires, with an owner for every item, a required-by date and an automatic chase when something is late. Documents that live in inboxes and shared folders are found only when someone remembers to look. Documents attached to a shipment record, with a status per document, show at a glance what is missing and who is holding it up.
This guide describes the process. It does not claim customs filing, electronic document exchange or EDI; those are separate integrations scoped per project only where an API exists.
Define document sets by shipment type
Do not build one giant checklist. A checklist should be generated from the shipment's type, so people only see what applies. Start by listing, for each type of shipment you handle, which documents are normally needed and who supplies each one.
- Split by mode (sea, air, road) and direction (import, export) where the document sets genuinely differ
- Mark each document as always required, conditional or optional, and record the condition (for example, only for certain goods or destinations)
- Record who normally supplies it: the client, the supplier, the carrier or your own team
- Confirm the real requirements with your own compliance contacts. This workflow tracks documents; it does not decide what the law requires
Set required-by dates, not just required lists
A document that arrives after the cut-off is as bad as one that never arrives. Give each item a required-by date derived from a shipment milestone: for example, a number of days before departure or before the vessel or flight cut-off. Store the rule, not a hand-typed date, so that when the shipment date moves, every deadline moves with it.
Sort the working view by the nearest deadline across all shipments. That single list is what the person responsible opens each morning.
Collection and chasing
Collection fails when chasing depends on someone's memory. Decide the sequence in advance and let the system run it.
- A request goes to the responsible party when the shipment is confirmed, listing exactly what is needed and by when
- Reminders follow at set points before the deadline, with a clear escalation to a named person on your side if the deadline passes
- Replies and uploads attach to the right shipment automatically or through a one-step filing action
- Late items surface on the working view, not only in the sender's inbox
- Every chase is logged, so you can see what was asked and when
Related pattern
Collecting documents from clients follows the same logic as any document request. See [client document collection automation](/client-document-collection-automation/) for the general pattern.
Version control
Shipping documents change: an invoice is corrected, a packing list is reissued, a booking is amended. The failure mode is that two versions circulate and the wrong one is used. Keep every version, mark exactly one as current, and record who uploaded it and when. Superseded versions stay visible for audit but are clearly labelled. Name files consistently, or better, let the system set names from the shipment reference and document type, so nobody has to guess.
Approvals
Some documents need review before they are released or relied on. Decide which ones, and by whom: an internal check of a client's commercial invoice against the booking, a manager sign-off on a document going to a third party, a client confirmation of a draft. Each review should have a status (waiting, approved, changes requested), a named reviewer and a recorded decision. A document that is present but unapproved should look different from one that is complete.
Client visibility
Clients want to know what you still need from them, and what you already have. A simple client-facing list of requested, received and outstanding documents removes a lot of email. That can be a periodic summary email at first, or a view inside a customer portal later; see the freight forwarder customer portal for that step. Whichever channel you use, show the client only their own shipments and only the documents meant for them. Internal notes and cost documents stay internal.
Design the exceptions
Most of the pain lives in exceptions, so decide them before go-live:
- A document arrives for a shipment that does not exist yet, or with a reference nobody recognises
- A required document is genuinely not applicable this time: allow a recorded waiver with a reason and a name
- A shipment is split, merged or rerouted and its document set changes
- A document is received but unreadable or incomplete
- The responsible person is away: who receives the chase instead
What to build first
A small start works: a shipment record, a checklist generated from shipment type, a status per document, a required-by rule and a daily overdue view. Add automatic chasing next, then client visibility. Where you already run RFQs and quotes in the same tool, keep the shipment record continuous from the request; see the freight RFQ management workflow. If today's tracking sits in spreadsheets and inboxes, the logistics software development page describes how we scope custom shipment and document tooling, and AI operations for logistics covers where automation can assist. The exact scope is agreed per project.
Questions
Do you track customs filings or exchange e-documents?+
No such capability is claimed here. This workflow tracks which documents you have, who owes what and by when. Integrations to external systems are scoped per project only where an API exists.
Can this run in a spreadsheet?+
For a small volume, a disciplined sheet can hold a checklist. It gets fragile once several people update it, deadlines depend on moving dates and clients need visibility, which is when a purpose-built tool pays back.
Who should own each document?+
One named party per item, usually whoever supplies it, plus one internal person who chases it. Shared ownership is how items get lost.
How do we handle a corrected document?+
Upload it as a new version, mark it current and keep the old one visible but labelled as superseded, with who and when recorded.
Should clients see the checklist?+
Yes for their own shipments, showing what is received and what is outstanding. Keep internal notes and cost documents out of that view.