Skip to content
Capability — Inside Shipment Management

Freight Document Management: Generated, Controlled, and Versioned

Freight document management controls how shipment documents are created, released, amended, and versioned so every party works from the right copy. Zavin generates 19 branded freight documents from live shipment data, limits who can release a customer copy, keeps a version history for every issued bill, and checks a document is current before it is sent.

Document Control is part of Zavin's Shipment Management module. Zavin is the AI operating system for freight forwarders.

Last updated: October 2026

Zavin

Ops copilot

ZVN-84291 · SHA→LAX

Copilot

On file ZVN-84291

Docs · EDI · Track live
Flag any BL discrepancies on shipments due this week.
2 found — BL-2904 missing fields. MBL-3012 consignee mismatch on ZVN-84291.
Draft correction ready. Ops alerted — 4h before vessel cutoff.

Correction draft on MBL-3012 · resolution window 4h before cutoff

19
Freight document types generated from shipment data
Every issue
Saved as a bill of lading version snapshot
Field-level
Access control across every object, branch, and country
< 14 days
To go live — no migration

The Cost of Sending the Wrong Version

A consignee name is corrected and the house bill is amended. A week later, someone replies to an old thread and attaches the original PDF. The consignee presents the wrong document, cargo release stalls at destination, and the team spends a day on calls and a letter of indemnity.

When documents are typed by hand and stored as email attachments, the wrong version is only a matter of time. Zavin makes the shipment the single source for every document and checks the version at the moment of sending.

When documents are typed by hand and stored as email attachments, the wrong version is only a matter of time.

Freight Document Management From One Source of Truth

Zavin generates branded documents straight from the shipment record, so the consignee on the arrival notice is the consignee on the house bill. The document list only offers types that fit the shipment's mode and direction.

  • House and master bills of lading.
  • Delivery orders and letters of indemnity.
  • Arrival notices, pre-alerts, and proof of delivery.
  • Booking requests, booking confirmations, shipping instructions, and letters of instruction.
  • Container load plans and cargo receipts.
  • CMR and CIM consignment notes, VGM declarations, and manifests.

Release Permissions and a Document Register

In Zavin, drafts stay internal until someone with release permission releases them. Internal working copies and customer-facing copies are kept apart, and every document passes the same release check however it was produced — generated by a coordinator, drafted or sent by Zavin Autopilot.

Each shipment carries a register that shows, at a glance, which documents are required, received, in draft, approved, rejected, released, or out of date, and which are internal or external. Superseded documents are marked stale, so nobody mistakes last week's copy for today's.

Bills of Lading With a Full History

Every house bill moves through a clear lifecycle, and Zavin saves a snapshot of it each time it is issued:

1

Draft — built from the shipment and checked internally.

2

Ready — complete and waiting to be issued.

3

Issued — released to the customer, with a version snapshot saved.

4

Amended — reopened with a written reason, unlocking only the fields that should change.

5

Cancelled — withdrawn, with the history kept.

Bill of Lading Amendments Straight From Email

When a customer emails “the consignee should read…”, Zavin turns the request into an amendment for review instead of leaving it buried in a thread. Once approved, the amendment opens with the customer's own wording, and your team re-issues the bill.

Files carry readable version names, such as “HBL - v2.pdf,” so a customer can tell which copy they hold. Zavin recognises duplicate uploads by their content, not their filename, so the same PDF sent three times is filed once.

Once approved, the amendment opens with the customer's own wording, and your team re-issues the bill.

Current Copies for Customers, Versioned Quotes for Sales

When a customer asks for their house bill or proof of delivery, Zavin drafts the reply with the current issued copy attached, then checks again at the moment of sending that it is still the latest version.

When a document is replaced, open tasks for the old copy close on their own and the new copy gets its own task, so the team never works the same document twice.

Amending a quote creates a new version with a new PDF and a cover email. Accepted prices are frozen, and every price change is logged with who made it and why, so the quote the customer accepted is always the quote on file.

One House Bill, Start to Finish

A coordinator generates the house bill for a 20-foot container from Mundra to Antwerp straight from the shipment. It sits as a draft, visible only inside the company, until someone with release permission issues it — and Zavin saves version one.

Two days later the shipper emails that the notify party is wrong. Zavin opens an amendment for review with the shipper's wording. Once approved, the coordinator unlocks only the notify party field, gives a reason, and re-issues. Version two is saved, version one is marked stale, and the old copy's open tasks close on their own.

When the consignee's broker asks for the bill a week later, the reply Zavin drafts attaches version two, and the check at the moment of sending confirms it is still the latest.

FAQs

Document Control: Common Questions

How freight forwarders evaluate this module. Still have questions?

Next port · your operation

Your Freight Business.
Running Itself.

Zavin handles the emails, quotes, documents, and follow-ups. Your team handles the customers, the relationships, and the growth. See it working on your own shipments.

Freight forwarders & NVOCCs · No migration · No IT project · Transparent pricing