← Back to Blog
Guide

What Is a Bill of Lading (BOL)? — Trucking Paperwork Explained

What Is a Bill of Lading (BOL)? — Trucking Paperwork Explained

What Is a Bill of Lading (BOL)? — Trucking Paperwork Explained

A bill of lading, commonly called a BOL, is one of the most important documents in freight transportation. It records what a shipper tenders to a carrier, where the shipment is going, who is responsible for delivery, and what condition the cargo was in when the carrier received it.

For owner-operators, dispatchers, fleet managers, and carrier owners, understanding the bill of lading BOL trucking process helps prevent payment delays, cargo disputes, incorrect deliveries, and claims problems. A properly completed BOL also gives the driver and carrier a reliable record of the shipment moving through the transportation process.

What Is a Bill of Lading?

A bill of lading is a transportation document issued for freight accepted by a motor carrier. It generally serves three practical purposes:

  • Receipt: It confirms that the carrier received specified freight from the shipper.
  • Evidence of the transportation agreement: It documents the parties, origin, destination, cargo, and shipping instructions.
  • Delivery record: It records when and how the freight was delivered, including shortages or visible damage.

A BOL is not simply a form for collecting a signature. It can become important evidence in a freight claim, payment dispute, detention disagreement, audit, or lawsuit. The document should therefore match the actual shipment and should not be completed from assumptions or copied from a previous load.

Federal regulations address bills of lading in 49 CFR Part 373. In particular, 49 CFR 373.101 generally requires a motor carrier receiving property for transportation to issue a receipt or bill of lading, subject to the regulation’s exceptions. The regulation does not prescribe one universal BOL design, so companies commonly use shipper-created forms, carrier forms, broker forms, or electronic transportation-management documents.

A BOL is only useful when it accurately describes the freight that was actually tendered, transported, and delivered.

Who Uses the BOL?

Shipper

The shipper prepares or provides much of the shipment information. This may include the commodity description, piece count, packaging type, weight, freight class, purchase order number, and delivery instructions. The shipper should make sure the description is specific enough for the carrier to identify the freight.

Motor carrier

The carrier accepts the freight, reviews the document, transports the load, and obtains delivery acknowledgment. The carrier is responsible for recording exceptions it observes rather than signing a clean receipt when the freight or packaging has visible problems.

Driver

The driver is often the person who discovers discrepancies at pickup or delivery. Before signing, the driver should compare the freight and paperwork, document shortages or damage, and obtain signatures from the appropriate shipping or receiving employee.

Consignee

The consignee is the delivery party. Its authorized representative usually signs the BOL, confirms the quantity received, and notes visible damage or shortage. A signature without a clear exception may later be used as evidence that the shipment was delivered in apparent good condition.

What Information Belongs on a BOL?

There is no single format used for every shipment, but a complete bill of lading commonly contains the following information:

  • Shipper’s legal name and address
  • Consignee’s legal name and delivery address
  • Bill-to party, if different from the shipper or consignee
  • Carrier name and, when applicable, broker or third-party logistics information
  • Pickup and delivery dates or appointment times
  • Purchase order, load, reference, or shipment numbers
  • Commodity description
  • Number and type of handling units, such as pallets, cartons, drums, or crates
  • Weight, dimensions, and freight classification when applicable
  • Special handling instructions
  • Declared value or liability information, if applicable
  • Hazardous materials information when the shipment is regulated
  • Shipper and carrier signatures
  • Delivery signature, date, time, and exceptions

The description should be practical and accurate. “Freight” or “parts” may be too vague to resolve a claim. A better description identifies the product, packaging, quantity, and any distinguishing information without creating a conflict with the shipper’s commercial documents.

How to Complete a BOL at Pickup

1. Compare the document with the freight

The driver should verify the number of pallets, cartons, or other units against the BOL. The driver should also inspect packaging for visible damage and confirm that the freight appears to be the commodity described. Drivers should not be expected to open sealed cartons, but they should record obvious discrepancies.

2. Record exceptions before leaving

If the shipment is short, damaged, wet, crushed, improperly packaged, or different from the paperwork, the driver should write a clear exception on the BOL before signing. Examples include “one pallet visibly crushed,” “three cartons short,” or “shrink wrap torn; contents exposed.” A vague note such as “damaged” is less useful than a specific description.

The shipper may ask the driver to sign a clean BOL and report the problem separately. That can create unnecessary risk. If there is a visible exception, it should be documented on the pickup record and supported with photographs when permitted.

3. Confirm special instructions

Instructions involving temperature, seal numbers, loading order, appointment requirements, or product handling should be reviewed before departure. A seal number should be written on the paperwork when a trailer is sealed. A driver should not break a seal without authorization unless safety, law, or an emergency requires it.

How to Handle Delivery Signatures and Exceptions

At delivery, the consignee should count the freight and inspect visible condition before signing. The carrier should request the consignee’s name, signature, date, and time. Electronic proof of delivery can be acceptable and is increasingly common, but the record should remain readable, retrievable, and linked to the correct shipment.

If there is damage or shortage, the consignee should identify it directly on the delivery record. The driver should not argue about fault or promise payment. The driver’s role is to preserve an accurate record. Photographs, seal information, pallet counts, and written observations can help the carrier investigate later.

A signed BOL does not eliminate every possible cargo claim. Under 49 CFR Part 370, motor carriers must have procedures for receiving, acknowledging, investigating, and processing claims for loss or damage to cargo. The Carmack Amendment and the carrier’s applicable tariff or contract may also affect liability and claim handling. The BOL is important evidence, but it is not the only evidence considered.

Electronic BOLs and Document Management

Many carriers now use electronic bills of lading, mobile document uploads, scanned PDFs, and electronic proof-of-delivery systems. Digital records reduce lost paperwork, but only if the carrier maintains a dependable process.

A usable electronic BOL system should:

  • Connect the document to the correct load and customer
  • Capture all pages, including continuation sheets
  • Preserve signatures, timestamps, and delivery exceptions
  • Allow authorized personnel to retrieve records quickly
  • Prevent accidental replacement of the original document
  • Back up records and control user access

Carriers should also confirm document-retention requirements in their contracts, customer instructions, and applicable regulations. A BOL should not be deleted simply because the invoice was paid. It may be needed later for a claim, audit, rate dispute, or customer review.

VAU0 LLC’s all-in-one platform can help carriers connect load information, document uploads, dispatch activity, and compliance workflows in one place. For a small carrier, keeping the BOL attached to the correct load can be just as important as obtaining the document itself.

BOL Requirements for Hazardous Materials

Hazardous materials require additional care. A BOL or shipping paper for regulated hazardous material must contain the information required by the Hazardous Materials Regulations, including the basic description in the required sequence, proper shipping name, hazard class or division, identification number, and packing group when applicable. These requirements are found primarily in 49 CFR Part 172, Subpart C.

Motor carriers and drivers must also follow shipping-paper and accessibility requirements during transportation. For example, 49 CFR 177.817 addresses shipping papers for hazardous materials carried by highway. The driver should verify that the shipping paper is complete, available as required, and consistent with the packages and placards.

A generic commodity description is not sufficient for hazardous material. If the shipment information appears incomplete or inconsistent, the driver should stop the loading or dispatch process and obtain correction from qualified shipping personnel before transportation begins.

Common BOL Mistakes That Create Problems

  • Signing without counting: A driver should not assume the pallet count is correct.
  • Using vague descriptions: Broad terms make claims and invoice review more difficult.
  • Failing to record visible damage: A clean signature can undermine the carrier’s position later.
  • Confusing the BOL with the rate confirmation: The BOL describes the freight and movement; the rate confirmation documents agreed compensation and operating instructions.
  • Ignoring seal discrepancies: A seal that does not match pickup documentation should be recorded and reported.
  • Uploading incomplete pages: Missing pages may remove the only evidence of quantity or exceptions.
  • Alterations should be clear, attributable, and accepted by the relevant parties.

BOL, Rate Confirmation, POD, and Freight Invoice

These documents are related but not interchangeable. The rate confirmation establishes the transportation rate and service terms. The BOL identifies the freight and records pickup and delivery conditions. The proof of delivery, or POD, confirms that delivery occurred and may include the signed BOL. The freight invoice requests payment and may reference all of these documents.

Before invoicing, the carrier should compare the signed BOL, rate confirmation, accessorial documentation, and POD. Detention, layover, lumper, rework, or shortage charges generally require supporting records. VAU0’s TMS and Rate Con AI features can help organize load documents and review rate-related details before billing, reducing avoidable paperwork gaps.

Practical BOL Checklist for Carriers

  • Confirm shipper, consignee, and delivery addresses.
  • Match piece count, pallet count, weight, and commodity description.
  • Check seal numbers and special handling instructions.
  • Inspect visible packaging and cargo condition.
  • Write specific exceptions before signing.
  • Obtain pickup and delivery signatures from authorized personnel.
  • Photograph damage, shortages, seals, and unusual conditions when appropriate.
  • Upload the complete signed document to the correct load.
  • Compare the BOL with the rate confirmation before invoicing.
  • Retain the record according to applicable requirements and company policy.

For carriers managing multiple drivers, a consistent BOL workflow should be part of driver onboarding and dispatch training. VAU0 LLC’s driver onboarding, compliance management, dispatching, and document tools can support that workflow while keeping paperwork connected to the load.

Practical takeaway: Treat every bill of lading as an operational and legal record, not just a delivery form. Verify the freight, document exceptions immediately, preserve the signed record, and reconcile it with the rate confirmation before billing. That discipline protects the carrier’s revenue and creates a clearer record when a shipment dispute occurs.

← Back to Blog For Carriers →
Why We Built VAU0 Instead of Buying Another TMS | VAU0 Blog
Our Story

Why we built VAU0 instead of buying another TMS

In 2022, we were running a small fleet and spending approximately $400 per truck per month on software. TMS license, ELD subscription, e-sign service, separate accounting integration. Four different logins. Four different monthly invoices. Four different support teams to call when something didn't work.

None of it talked to each other without manual data entry.

The software evaluation that changed everything

We spent three months evaluating every major TMS and fleet management system on the market. AscendTMS, McLeod, Motive, EZLogz, KeepTruckin, TruckingOffice, Axon. We signed up for demos, trials, and in two cases, paid for actual subscriptions to test them properly.

What we found was consistent across almost all of them: the software was built by people who had never dispatched a truck. You could tell immediately. The terminology was slightly wrong. The workflows assumed steps that no real dispatcher would take. The ELD and TMS were always separate systems that "integrated" — meaning they sometimes shared data, if you configured things correctly, and the configuration broke whenever either vendor pushed an update.

"The best way to evaluate trucking software is to use it under real pressure. Not in a demo. Not in a test environment. On a real load, with a real deadline, when a broker is calling every 30 minutes for an update."

The specific things that were broken

Without naming specific vendors: one major TMS required five screen transitions to update a load status. Not five clicks — five full page navigations. On a mobile browser from a truck stop, that meant 45 seconds to tell a broker the truck was loaded. Another system had beautiful analytics dashboards but couldn't tell you, in real time, how many hours of drive time your driver had remaining without navigating to a separate compliance module.

The ELD market was worse. Most ELD systems were designed to satisfy FMCSA's technical requirements — which they did — while making the user experience as painful as possible. Drivers hated them. When drivers hate their tools, they find workarounds. Workarounds create compliance risk.

The moment we decided to build

The decision was made on a Tuesday afternoon when our dispatcher spent 40 minutes re-entering data from a rate confirmation PDF that our ELD had already captured in a different system. The information existed. It was digital. It lived in three different places that didn't talk to each other, and a human was manually transferring it between systems.

That's not a technology problem. That's a lack of ambition problem. Nobody had decided to solve it because the existing systems were profitable enough without solving it.

What we decided to build instead

One platform. ELD and TMS as the same system, not integrations. AI that reads rate confirmation PDFs so dispatchers don't have to. A dispatcher — eventually an AI dispatcher — that covers nights and weekends so loads don't get missed. E-sign built in, not bolted on.

And priced at zero through 2026, because the goal was to prove the product worked before asking carriers to pay for it.

Two years in: did it work?

The Rate Con AI has a 95%+ accuracy rate on standard broker formats. ERETH ELD passed FMCSA's technical certification. Our AI dispatchers book real loads for real carriers after hours. The carrier dashboard still occasionally has a minor bug — we fix them the same day they're reported.

Would we have been better off just using an existing system and focusing on freight? Financially, in the short term, probably yes. But we would have kept paying $400 per truck per month for software that we knew was mediocre. And we would have missed the opportunity to build something that actually works the way the industry needs it to work.

We don't regret it.

← Back to Blog Next: Our first AI broker call →