The BOL records what was tendered: shipper and consignee, piece and pallet count, weight, description and NMFC class for LTL, special instructions, and any freight-charge terms (prepaid, collect, or third-party).
A “straight” BOL is non-negotiable — the freight is delivered to the named consignee and title does not move with the document. A negotiable (“order”) BOL is a title document; whoever holds the original endorsed copy controls the goods, which matters in letter-of-credit and international trade.
The BOL signed at delivery, with any exception noted, becomes the proof of delivery and the starting point for any claim.
Example
At pickup, the shipper hands the driver a straight BOL for 18 pallets, 22,400 pounds, prepaid, with a note that the consignee requires an appointment. The driver checks the count, signs, and keeps a copy. At delivery the receiver signs the same BOL noting two pallets shrink-wrap torn — that annotation is now the record for any damage claim.
Why it matters
The BOL is the anchor document for the whole load. Count discrepancies, class disputes, freight-charge terms, and claims all trace back to what it says and how it was signed.
How teams use this term
In a carrier operation, Bill of Lading (BOL) belongs in the conversation about load closeout, billing readiness, and evidence management. The useful question is not only what the term means, but which record or decision it changes. A dispatcher may see it while planning a load, a driver may create evidence for it in the field, and accounting may need the same context before a customer invoice or carrier settlement can be finalized. Keeping the term attached to the related workflow prevents a definition from becoming disconnected vocabulary.
When reviewing Bill of Lading (BOL), ask who owns the next action, what evidence supports the record, and what date or threshold makes the situation change. The answer can vary by equipment, lane, authority, customer routing guide, or contract. A small carrier should document the assumption it used rather than treating a general explanation as a universal rule. The related terms on this page are intended to help a team move from the definition to the operational decision.
A practical review starts with the example above, then compares it with the carrier's own settlement, dispatch, document, or compliance records. If the term affects a regulated filing, payment obligation, or customer requirement, verify the current primary source before acting. Trailflow can provide workflow context, but the carrier remains responsible for the policies, records, and professional advice that apply to its operation.
In Trailflow, this shows up in document capture.