The BOL is missing and the truck is coming. Who gets notified?
Key Takeaways
When the bill of lading is missing and the truck is coming, the load owner should be notified first, then the person who can create the BOL, then the warehouse, and the carrier only if the pickup may be delayed. An AI logistics coordinator can detect the missing BOL early, send each notice with the facts, and track the fix until the document is ready.
- A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
- A missing BOL is a timing problem. The earlier it is found, the fewer people need to be involved.
- Notifications should go to people who can act, not to everyone on the load.
- Each notice should say what is missing, when the truck arrives, and what the reader needs to do.
- The carrier should be told only when the pickup may be late or the driver needs to wait.
- The decision to hold or release the truck should belong to one named person.
- Wilson, by Cartage, is an AI logistics coordinator that prepares bills of lading from the booked load, checks that each one is ready before pickup, and notifies the right people when it is not.
Who should be notified when the BOL is missing before pickup?
The load owner should be notified first, because that person can decide what happens next. Then the person who creates the BOL, then the warehouse, and the carrier only if the pickup may change. An AI logistics coordinator should send each notice in that order, with the facts each person needs.
The table below shows who needs to know and why.
| Who | Why they need to know | What they should do |
|---|---|---|
| Load owner | Owns the decision for the load | Decide whether to fix, delay, or release |
| BOL creator | Can produce the document | Create or correct the BOL |
| Warehouse | Will hand the BOL to the driver | Hold the freight until the BOL is ready |
| Customer service | May need to tell the customer | Update the customer if delivery may slip |
| Carrier | Sends the driver | Adjust the arrival if the pickup moves |
Why not notify everyone at once
A message to a large group often gets no action. Everyone assumes someone else will handle it. A missing BOL needs one person to decide and one person to create the document. Other people only need to know if the plan changes. Sending the right message to the right person is faster than a group alert.
Who is the load owner?
The load owner is the person responsible for the shipment from booking to delivery. In some teams, that is a logistics coordinator. In others, it is a shipping lead or a customer service rep. The owner should be named in the shipment record, so the notice does not go to the wrong person.
Who creates the BOL?
In many companies, the BOL is created from the order system when the order is released to the warehouse. In others, a coordinator creates it in a carrier portal. Sometimes the carrier creates it. The notice should go to whoever does this for this load, not to a general shipping inbox.
Back-ups when the owner is out
Every notification plan needs a back-up. If the load owner is on vacation, in a meeting, or off shift, the notice should go to a named back-up after a short wait. The back-up should have the same view of the load and the same authority to decide. Without a back-up, a missing BOL at 6 a.m. can sit until the owner logs in, while the driver is already on the road.
Shift changes at the warehouse
Many warehouses run more than one shift. A BOL problem found by the day shift may not be known to the night shift that loads the truck. The notice to the warehouse should go to the shift that will be at the dock when the driver arrives, not only to the person who noticed the problem. The shipment record should show which shift was told.
When to tell the customer
The customer only needs to hear about a missing BOL if the delivery may be late. If the BOL can be fixed before the truck arrives, the customer never needs to know. Telling customers about internal paperwork issues creates worry without helping them plan.
Why does a BOL go missing before pickup?
A BOL usually goes missing because an upstream step did not happen: the order was not released, the data was incomplete, the carrier changed, or the document was created but never reached the dock. An AI logistics coordinator should find the cause, because the cause tells the team who can fix it fastest.
Common causes
| Cause | What happened | Who can fix it |
|---|---|---|
| Order not released | The order system never sent the order to shipping | Customer service or order management |
| Missing data | Weight, count, or address is blank | Warehouse or customer service |
| Carrier changed | The BOL was printed for the first carrier and voided | Logistics coordinator |
| Carrier form required | The carrier needs its own BOL and it was not created | Logistics coordinator |
| Document not delivered | The BOL exists but never reached the dock | Warehouse or shipping clerk |
| Split shipment | One order became two loads and only one BOL exists | Logistics coordinator and warehouse |
Orders that are booked before they are ready
Some loads are booked before the order is fully picked or packed. That is often the right choice, because carriers need notice. But it means the BOL may be created late. The load owner should know which loads are booked ahead of order readiness, so they can check those BOLs first.
Data that arrives late
The BOL needs the piece count, weight, and freight description. If the warehouse has not finished picking, these numbers may not exist yet. A BOL created with estimates may need to be updated later. A BOL that waits for final numbers may not exist when the truck arrives. The team should decide which approach fits each lane.
Documents that exist but are in the wrong place
Sometimes the BOL exists, but in an email, a printer queue, or a folder the dock does not use. The fix here is not a new document but a better handoff. The notice should ask the BOL creator to send it to the dock, not to create it again.
Carrier-issued BOLs and portals
Some carriers want the shipper to create the BOL in the carrier's portal, so the carrier can assign a PRO number in advance. A PRO number is a tracking number a carrier gives to a shipment. If the coordinator forgets this step, the dock has the company's own BOL but not the carrier's. The driver may accept the company's BOL, or may not. The notice should name the carrier's rule, so the fix is clear.
Changes in the order after release
An order can change after it is released: a line is canceled, a quantity changes, or the ship-to address is updated. Some order systems void the BOL when the order changes and wait for someone to create a new one. Others leave the old BOL in place. Either way, the dock may end up with no valid BOL. The check should look for these changes, not only for a missing file.
Hypothetical example: a split shipment
This example is hypothetical and does not describe a real customer. A manufacturer splits a large order into two truckloads because the product does not fit on one trailer. The first BOL was created with the full order. The second truck is booked for the next morning, but no BOL exists for it. The day before pickup, the AI logistics coordinator finds that the second load has no BOL. It notifies the load owner and the shipping clerk. The clerk creates a BOL for the second load and corrects the first one to show only its own pallets.
When should the missing BOL be detected?
A missing BOL should be detected the day before pickup at the latest, and ideally when the load is booked. An AI logistics coordinator should check every load at set times before pickup, so a missing BOL becomes a routine task, not an emergency at the dock.
Detection checkpoints
| Checkpoint | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| At booking | Load booked | Checks whether a BOL exists or is scheduled | When the order is not yet released |
| Day before pickup | Pickup within 24 hours | Confirms the BOL exists and matches the load | When it is still missing |
| Morning of pickup | Pickup within a few hours | Confirms the BOL reached the dock | When the dock does not have it |
| Truck arriving | Carrier shares an arrival time | Alerts the load owner if the BOL is still missing | Owner decides to hold or release |
The cost of late detection
When the missing BOL is found at the dock, everyone is under pressure. The driver may wait. The carrier may bill detention, which is a fee a carrier bills when its truck waits too long at a dock. The warehouse may hand over a handwritten BOL with errors. The driver may leave without the load, and the carrier may bill a truck ordered not used fee, or TONU. All of these cost more than an early check.
How early is early enough?
The answer depends on how long it takes to create a BOL. If the order system creates it in minutes, a check the morning of pickup may be enough. If the BOL needs data from the warehouse, the day before is better. If the carrier requires its own form and the portal is slow, the check should happen at booking. The team should set the timing by lane or carrier.
Appointments add pressure
When the pickup has a fixed appointment, a missing BOL is more urgent. The carrier may have planned the driver's day around that time. If the BOL is not ready, the driver may lose the slot and the next pickup too. The detection check for appointment loads should happen earlier than for open pickup windows, so there is more time to fix the document.
Live loads and drop trailers
On a live load, the driver waits at the dock while the freight is loaded. A missing BOL delays the driver directly. On a drop trailer, the carrier leaves an empty trailer and picks up the loaded one later. A missing BOL may not delay the driver, but the trailer cannot leave without it. The urgency is different, and so is the notification plan.
Measure how often the BOL is missing
The team should track how many loads reach the day before pickup without a BOL, and why. A rising number usually points to one cause: orders released late, missing weights, or carrier changes. Fixing that cause reduces the number of notices, which is better than sending faster ones. The AI logistics coordinator can report these counts on request from the loads it handles.
Hypothetical example: a check at booking
This example is hypothetical and does not describe a real customer. A distributor books an LTL load with a carrier that requires its own BOL form. At booking, the AI logistics coordinator sees that no carrier BOL has been created. It sends the coordinator a reminder with the carrier's portal link and the order details. The coordinator creates the BOL that afternoon, two days before pickup.
What should each notification say?
Each notification should say what is missing, which load it belongs to, when the truck is expected, what the reader needs to do, and by when. An AI logistics coordinator should write a different message for each reader, because each one has a different job.
Message templates
| Reader | What the message should include |
|---|---|
| Load owner | Load number, pickup time, what is missing, likely cause, options |
| BOL creator | Load number, order number, data needed, deadline |
| Warehouse | Load number, dock time, whether to hold the freight |
| Carrier | Load number, new expected ready time, whether the driver should wait |
| Customer service | Load number, delivery risk, whether to tell the customer |
A good message to the load owner
A good message might say: "Load 4410, pickup today at 2 p.m. with Carrier B. No BOL found. The order was released at 9 a.m. but the weight is blank. Options: ask the warehouse for the weight and create the BOL, or move pickup to tomorrow. Please choose by noon." The owner can act in one step.
A good message to the warehouse
The warehouse needs to know whether to keep loading, hold the freight, or move it to another door. A good message might say: "Load 4410, Door 6, pickup at 2 p.m. BOL is not ready yet. Keep the freight staged. Do not release it to the driver until the new BOL arrives, expected by 1:30 p.m." The dock lead knows exactly what to do and what to wait for.
A good message to the carrier
If the pickup may be late, the carrier needs a clear time. A good message might say: "Load 4410 will be ready at 3:30 p.m. instead of 2 p.m. Please adjust the driver's arrival or confirm the driver can wait." The carrier should not get a vague note that "there is a document issue."
Use the channel each person reads
The best message fails if it goes to an inbox nobody checks. Warehouse leads may read a text message faster than an email. Coordinators may live in Slack or Microsoft Teams. Carriers often answer email or a phone call. The notification plan should use the channel each person actually reads during the shift, and the shipment record should show which channel was used.
Escalate if nobody answers
If the BOL creator does not answer within the deadline, the notice should go up one level, to a supervisor or the load owner. The escalation should include the first message and the time it was sent. That way, the supervisor does not need to ask what happened before acting.
Avoid duplicate messages
If several people are notified, they should not receive the same message with different instructions. One shipment record should show who was told what and when. That way, when someone asks "did anyone tell the carrier?", the answer is clear.
Keep messages short
Each notice should fit on a phone screen. Long messages with history and attachments get skimmed. The first two lines should carry the load number, the problem, and the action needed. Details can follow below or in the shipment record.
Follow up until the BOL exists
A notification is not the end. The AI logistics coordinator should check again before the deadline. If the BOL still does not exist, it should remind the creator and update the load owner. The task closes only when the BOL is at the dock.
Who decides whether to hold or release the truck?
The load owner should decide whether to hold the truck, delay the pickup, or let the driver leave, based on rules set in advance. An AI logistics coordinator should present the options with their costs and timing, and record the decision with the load.
Decision rules
| Situation | Usual decision | Why |
|---|---|---|
| BOL ready within the driver's free time | Hold the driver | No extra cost |
| BOL ready after free time, delivery still on time | Hold if detention is cheaper than a new pickup | Cost comparison |
| BOL cannot be ready today | Reschedule pickup | Avoid long detention |
| BOL missing and delivery is critical | Escalate to a manager | Customer impact |
| Driver cannot wait | Reschedule and confirm TONU terms | Avoid surprise charges |
Free time is the time a carrier allows at a dock before detention starts. Detention is very common: in a September 2024 study, the American Transportation Research Institute (ATRI) found it affected 39.3% of truck stops in 2023. A missing BOL is one of the avoidable reasons a driver waits.
Weigh the customer impact
Cost is not the only factor. If the load feeds a customer's production line, a one-day delay may cost far more than a few hours of detention. If the customer has flexible receiving, a reschedule may be the better choice. The load owner should know which customers and orders are critical, so the decision rules can reflect that. The AI logistics coordinator can show this information next to the cost options.
Never release freight without a BOL
The freight should not leave without a BOL. The BOL is the carrier's receipt and the shipper's proof of what was tendered. A handwritten BOL is better than none, but it should include the required fields and be replaced in the record with the correct version afterward.
Know the carrier's terms before deciding
The right decision depends on the carrier's terms. How much free time does the rate confirmation allow? What is the detention rate per hour? What does a TONU cost, and when does it apply? A rate confirmation is the document that states the agreed price and terms for one load. If these terms are on file, the load owner can compare costs in minutes. If they are not, the owner is guessing.
Record the decision
Whatever the owner decides, the shipment record should show the decision, the time, the reason, and who made it. If the carrier later bills detention or TONU, the record shows why the delay happened and whether it was approved.
Hypothetical example: a held driver
This example is hypothetical and does not describe a real customer. A driver arrives at 2 p.m. for a truckload with two hours of free time. The BOL is missing because the address was blank. The AI logistics coordinator tells the load owner that customer service can fix the address in 30 minutes. The owner decides to hold the driver. The BOL is ready at 2:40 p.m., the truck leaves at 3:10 p.m., and no detention applies.
Where does Wilson fit when a BOL is missing before pickup?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers and prepares the documents each load needs, such as bills of lading, rate confirmations, packing slips, and pallet labels. Wilson checks that each BOL exists and matches the load before pickup, and notifies the right people when it does not.
Wilson replaces the TMS for freight execution and connects to the company's ERP. A TMS, or transportation management system, is software used to plan, book, and track freight. An ERP, or enterprise resource planning system, is the company's main business system for orders, inventory, and accounting. Wilson works from the connection or data flow the company already has, such as an ERP feed, a scheduled file drop, a spreadsheet, email, or API.
How Wilson finds a missing BOL
Wilson checks each booked load against its document list at set times before pickup. If the BOL does not exist, does not match the load, or has not reached the dock, Wilson flags it to the load owner. Because Wilson prepares BOLs from the booked load, many gaps are closed before anyone needs a notice.
How Wilson notifies
Wilson notifies internal teams through Slack, Microsoft Teams, email, or SMS, and works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured. EDI, or electronic data interchange, is a standard format some carriers use to exchange documents between systems. Each notice names the load, what is missing, and what the reader needs to do.
Carriers, approvals, and payment
Wilson tenders the customer's approved carriers first, and the customer approves each new carrier before Wilson uses it. If a delay leads to a detention or TONU charge, Wilson checks it against the recorded times and the terms when the invoice arrives. Customers use the Wilson Wallet to pay their carriers. Payments above approval limits or outside the rules wait for a person. Wilson has no subscription or platform fee; its pricing is a percentage of the freight payments coordinated through the Wallet. Pricing scales down as volume grows, and Enterprise pricing is custom.
What Cartage asks in discovery
Cartage asks where BOLs are created, which carriers require their own forms, who owns each load, and what the team does today when a driver arrives without a BOL. These answers shape the checkpoints and the notification plan an AI logistics coordinator follows.
Where teams start
Wilson starts with assisted execution. Approval limits are set by the customer, and routine actions can run automatically within those rules as reliability is proven. Timing depends on scope: most teams start on a few lanes and expand from there. Every notice and decision is saved in the shipment record with change history.
Teams preparing documents earlier can read how to request missing bills of lading before pickup. Teams building a full pickup routine can start with the freight pickup guide.
This article is part of our complete guide to bills of lading from booking to delivery.
FAQs
Who should be notified when the BOL is missing?
The load owner first, then the person who creates the BOL, then the warehouse. An AI logistics coordinator tells the carrier only if the pickup may be delayed.
When should a missing BOL be detected?
At booking if possible, and no later than the day before pickup. An AI logistics coordinator checks every load at set times so the gap is found early.
Should the truck wait for a missing BOL?
It depends on how long the fix takes and the cost of waiting. An AI logistics coordinator shows the load owner the options, and the owner decides.
Can freight leave without a BOL?
It should not. The BOL is the carrier's receipt. An AI logistics coordinator should make sure a correct BOL exists before the freight is released.
What should a missing-BOL notice include?
The load number, the pickup time, what is missing, the likely cause, what the reader must do, and the deadline. An AI logistics coordinator writes a different message for each reader.
Sources
- American Transportation Research Institute, "New Research Documents Substantial Financial and Safety Impacts from Truck Driver Detention," September 2024: https://truckingresearch.org/2024/09/new-research-documents-substantial-financial-and-safety-impacts-from-truck-driver-detention/
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator detects a missing bill of lading before pickup and notifies the right people in time: talk to the Cartage team.