| Core Definition | On-Board Date The date on which cargo is physically loaded onto the named vessel for an ocean shipment. It should not be confused with the booking date, cargo-receipt date, or document-issue date. | Establishes the actual departure milestone used to calculate transit expectations, estimated arrival, and shipment-performance metrics. | An incorrect definition can create inconsistent records across the purchase order, transport document, commercial invoice, customs entry, and payment file. | Define OBD in the purchase contract, logistics instructions, and transport-management system. Record the time zone and the relevant vessel or voyage. | Common ocean-shipping documentation practice; the governing contract should control where definitions differ. |
| Actual Versus Planned OBD | Planned OBD is the intended loading date. Actual OBD is the date supported by the carrier’s transport document or verified loading event. | The difference between planned and actual OBD reveals rolled cargo, port congestion, missed cut-offs, or late handover. | Payment and compliance teams should use the actual shipment date when a contract or documentary requirement refers to shipment. | Keep both dates as separate fields. Do not overwrite the planned date with the actual date. | Standard logistics milestone-control practice. |
| Incoterm and Risk Transfer | Under sea terms such as FOB, CFR, and CIF, delivery and risk transfer are linked to loading on board the vessel. Under FCA, risk generally transfers when goods are handed to the carrier at the agreed place. | The correct milestone identifies when transport risk changes and who is responsible for the next movement or incident. | The OBD event may support the seller’s delivery obligation under sea terms, but it does not automatically determine ownership, title, or payment entitlement. | Match the selected Incoterm with the named place, transport mode, insurance responsibility, and documentary requirements. | Incoterms® 2020 rules. |
| Documentary Payment Deadline | A documentary credit may specify a latest shipment date. The transport document must show shipment within the period required by the credit. | A vessel loaded after the permitted date can trigger document discrepancies even if the goods arrive within the expected delivery window. | Under UCP 600, a presentation generally must be made no later than 21 calendar days after shipment and in all cases no later than the credit’s expiry date, unless the credit states otherwise. | Compare actual OBD with the latest shipment date before document presentation. Check whether the credit requires an on-board notation, shipment date, or another transport-document statement. | UCP 600, including Articles 14(c) and 20. |
| Export-Control Timing | Export declarations, licenses, screening, and supporting records must be completed within the deadlines imposed by the export jurisdiction and transport mode. | Missing or late export clearance can prevent cargo from being loaded, causing the actual OBD to move beyond the planned date. | Incorrect shipment information can create customs holds, penalties, seizure risk, or delays in issuing proof of export. | Validate exporter, consignee, commodity classification, customs value, origin, license requirements, and filing status before the cargo cut-off. | Applicable national export-control and customs regulations. |
| Import and Customs Planning | OBD is the departure milestone used to estimate arrival, port availability, import-filing windows, and document readiness. | A changed OBD can alter the expected arrival date, free-time planning, inland transport booking, warehouse labor, and inventory availability. | Import declarations and safety or security filings may require accurate transport details before arrival; incorrect timing can increase inspection or storage exposure. | Recalculate estimated arrival after every OBD change and notify the importer, customs broker, inland carrier, and receiving facility. | Destination-country customs and cargo-security requirements. |
| Carrier Document Evidence | Evidence may include an on-board notation, a transport document with a shipment date, a verified electronic milestone, or other carrier-issued confirmation. | Reliable evidence improves visibility and supports accurate exception management when vessel schedules change. | Banks, auditors, customs authorities, and contractual counterparties may rely on transport-document wording rather than an internal system timestamp. | Reconcile the internal OBD with the final transport document and retain the document version used for payment or customs purposes. | Transport-document and audit-control practice. |
| Time Zone and Calendar | OBD should be recorded with the local date of the relevant loading event and the applicable time zone. Contractual deadlines may use a different location or time standard. | A late-night loading event can fall on different calendar dates in the port, seller, buyer, and bank locations. | Time-zone ambiguity can cause an apparent late shipment, late document presentation, or inconsistent regulatory record. | Store the local event timestamp, UTC equivalent, port location, and source document. State the deadline time zone in the contract or documentary credit. | International data-governance and contract-administration practice. |
| Exception and Delay Management | An OBD exception occurs when actual loading differs from the agreed window, latest shipment date, or required compliance milestone. | Early escalation allows rebooking, alternative routing, revised delivery appointments, and inventory replanning. | A delay may require an amendment, waiver, documentary-credit approval, customs update, or revised contractual notice. | Set automated alerts for missed cut-offs, planned-to-actual variance, latest shipment dates, and missing transport evidence. | Supply-chain exception-management practice. |
| Data-Quality KPI | Useful measures include planned-versus-actual OBD variance, percentage of shipments with verified OBD, documentation discrepancy rate, and on-time shipment rate. | These indicators distinguish schedule reliability from downstream port, customs, or inland-delivery delays. | High data completeness supports auditability, payment processing, customs reporting, and dispute resolution. | Review the metrics by lane, port, transport mode, and month. Keep operational performance data separate from customer or supplier identity data. | General logistics-performance measurement practice. |