The wrong truck was checked in. How should the shipment record change?
Key Takeaways
When the wrong truck is checked in for a load, the shipment record should be corrected so that each load shows the truck, carrier, times, and documents that actually belong to it, while the original wrong entry stays in the history with the reason for the change. An AI logistics coordinator can find the mix-up, move each event to the right load, update the BOL and the carrier, and save every correction with change history.
- A wrong check-in happens when a truck is logged against a load it is not there to carry.
- It often happens when two trucks from the same carrier, or two loads for the same customer, arrive close together.
- If it is caught before loading, the fix is a record correction. If freight was loaded on the wrong truck, the fix is larger.
- Arrival, check-in, and departure times must move to the correct load, or detention and tracking will be wrong.
- The BOL, the PRO number, and the carrier's own records must match the truck that actually took the freight.
- The original wrong entry should not be deleted. It should be marked as corrected, with who changed it and why.
- Wilson, by Cartage, is an AI logistics coordinator that tracks each load, compares site records with carrier records, and keeps every correction in the shipment record with change history.
How does the wrong truck get checked in?
The wrong truck gets checked in when the gate or dock matches a truck to a load using incomplete information, such as the carrier name alone, a similar load number, or the customer name. An AI logistics coordinator should know the common causes, because the cause shows where the record needs to change.
Common causes
| Cause | What happens |
|---|---|
| Two trucks from the same carrier | Gate assigns the first truck to the first load on the list |
| Similar load or pickup numbers | Clerk types 44812 instead of 44821 |
| Two loads for the same customer | Truck matched by customer name, not load number |
| Driver gives the wrong number | Driver reads a number from another load's paperwork |
| Carrier swapped trucks | Carrier sent a different truck than it told the shipper |
| Drop trailer confusion | Wrong trailer hooked from the yard |
Two loads for the same customer
When two loads go to the same customer on the same day, a clerk may check in either truck for either load. If the loads have different freight or delivery addresses, the swap matters. If they are identical, it may not change the freight, but it still changes the record, the BOL, and the invoice. The record should be fixed either way.
Why it matters
A wrong check-in can cause the wrong freight to go on a truck, a truck to wait for freight that is not for it, or a load to look picked up when it is not. Even if the freight goes on the right truck in the end, the record may show the wrong times for both loads. That affects tracking, customer updates, and detention review. Detention is a fee a carrier bills when its truck waits too long at a dock.
LTL pickups
For less-than-truckload pickups, several carriers may come to the same dock in one afternoon. Less-than-truckload, or LTL, is freight that shares a trailer with other shippers' freight. Freight staged for one carrier can be handed to another. The BOL and PRO number are the main checks. The dock should confirm the carrier name on the BOL matches the driver's company before loading each pallet.
Caught early or caught late
If the mix-up is caught before loading, the fix is mostly a record correction. If freight was loaded on the wrong truck, the fix may mean unloading, reloading, or changing where the truck goes. If the truck has already left, the fix may involve the carrier redirecting it. The earlier the mix-up is found, the cheaper it is.
Drop trailers
On drop-trailer pickups, the carrier leaves an empty trailer and later picks up the loaded one. If the wrong trailer is hooked, the wrong freight leaves. Trailer numbers and seal numbers are the main protection. A seal is a numbered tag that shows the trailer was not opened in transit. The BOL should record both.
Delivery sites can mix up trucks too
The same thing happens at delivery. A receiver may check in a truck against the wrong purchase order, unload it at the wrong door, or sign a delivery receipt for the wrong load. The shipper may then get a proof of delivery that does not match. A proof of delivery, or POD, is the document the receiver signs to show the freight arrived. The same correction rules apply.
Tracking can hide the swap
When two trucks are swapped, carrier tracking may show each truck moving normally. The tracking for Load 5101 may actually be following the truck carrying Load 5102. The customer for 5101 may get updates about a truck that is going somewhere else. Only a check of truck details against the load reveals the problem.
Hypothetical example: two trucks, one carrier
This example is hypothetical and does not describe a real customer. Two trucks from the same carrier arrive 10 minutes apart for Loads 5101 and 5102. The gate checks in the first truck for Load 5101, but that truck was dispatched for Load 5102. Both trucks wait at doors for the wrong freight. The warehouse notices when the driver's paperwork does not match the pick list. The AI logistics coordinator swaps the check-in records, and both loads are loaded correctly.
How should the mix-up be detected?
The mix-up should be detected by comparing the truck's details at check-in, such as the carrier, trailer number, driver name, and the load number on the driver's dispatch, with what the carrier confirmed for each load. An AI logistics coordinator should run that comparison when the check-in is recorded and flag any mismatch before loading starts.
What to compare at check-in
| Check-in detail | Compare with | Mismatch means |
|---|---|---|
| Carrier name | Carrier booked for the load | Wrong carrier or wrong load |
| Load or pickup number on the driver's dispatch | Load number checked in | Possible swap |
| Trailer number | Trailer the carrier confirmed, if known | Different truck sent |
| Driver name or phone | Driver the carrier assigned, if known | Possible swap |
| Equipment type | Equipment booked | Wrong truck or wrong load |
The detection workflow
| Step | Trigger | What the AI logistics coordinator does | When a person steps in |
|---|---|---|---|
| 1. Read check-in | Site records a check-in | Reads carrier, trailer, driver, and load number | Never |
| 2. Compare | Check-in read | Compares with the carrier's confirmation for that load | Never |
| 3. Flag | Details do not match | Alerts the warehouse before loading | Warehouse confirms with the driver |
| 4. Confirm | Warehouse checks | Asks the carrier which load the truck is for | When the carrier's answer differs from the driver's |
| 5. Correct | Correct load confirmed | Moves the check-in to the right load | Never for simple swaps |
| 6. Record | Correction made | Saves the original entry, the change, and the reason | Never |
Flag before loading, not after
The value of the comparison is in its timing. A mismatch caught at check-in costs a few minutes. The same mismatch caught after loading may cost hours. The AI logistics coordinator should run the comparison as soon as the check-in is recorded and send the alert to the dock lead who will assign the door.
Ask the carrier for truck details in advance
The best protection is to know which truck is coming before it arrives. Many carriers can share the trailer number, driver name, or truck number when they dispatch. The AI logistics coordinator can request these details and add them to the booking, so the gate has something specific to match.
Equipment as a quick check
Equipment type is a fast check. If the load needs a 53-foot dry van and a flatbed checks in, something is wrong. If the load needs a reefer and a dry van arrives, the truck is either wrong or the carrier sent the wrong equipment. A reefer is a refrigerated trailer. Either way, the mismatch should be resolved before loading.
The driver's paperwork is the key
The driver usually has a dispatch sheet or app screen showing the load number. Asking the driver to show it at check-in, and matching it to the load, catches most swaps. A check-in by carrier name alone is the main source of mix-ups.
When the carrier swapped trucks on purpose
Sometimes the carrier changes which truck covers which load after dispatch, for good reasons, and forgets to tell the shipper. The gate then sees a truck that does not match the details on file. The fix is to confirm with the carrier and update the booking, not to turn the truck away. The record should show that the carrier made the change and when it told the shipper.
Check-ins on paper
At sites that check trucks in on paper, the gate list may not be connected to any system. The AI logistics coordinator may only see the check-in later, when the site sends its log. The comparison still helps, but it may catch a swap after loading rather than before. Sites with frequent swaps may benefit from a simple digital check-in.
Hypothetical example: caught by the trailer number
This example is hypothetical and does not describe a real customer. A carrier confirms trailer 53-2219 for Load 6630. At check-in, the gate logs trailer 53-4471 for Load 6630. The AI logistics coordinator flags the mismatch. The warehouse asks the driver, who is there for Load 6631. The check-in is moved to Load 6631 before any freight is loaded.
How should the shipment record be corrected?
The shipment record should be corrected by moving each event to the load it belongs to, updating the truck and carrier details, keeping the original wrong entry marked as corrected, and noting who made the change and why. An AI logistics coordinator should make these corrections for both loads involved, because a swap always affects two records.
What to correct on each load
| Record | What to change |
|---|---|
| Arrival time | Move to the correct load |
| Check-in time and door | Move to the correct load |
| Trailer, truck, and driver | Update to the truck that served the load |
| Loading start and finish | Move to the correct load |
| Departure time | Move to the correct load |
| Signed BOL | Attach to the correct load; reissue if wrong |
| Status | Reset to match what really happened on each load |
A bill of lading, or BOL, is the shipping document that lists the freight and serves as the carrier's receipt for it.
Keep the original entry
The wrong entry should stay in the record, marked as corrected. If someone later asks why Load 5101 shows a check-in at 9:00 a.m. that was moved, the history shows the original entry, the corrected one, the reason, and who made the change. Deleting the wrong entry removes the evidence of what happened.
Who may correct the record
Only named roles should be able to move events between loads, such as the load owner or the AI logistics coordinator acting under set rules. Corrections by anyone else should be reviewed. This keeps the history trustworthy, especially when detention or claims may depend on it.
Fix both loads together
A swap affects two loads. Fixing only one leaves the other wrong. The correction should be done as one change across both records, so neither load is left with missing or duplicated events.
Recalculate dependent information
Once times move, other information may change: delivery estimates, detention start times, and customer updates. The AI logistics coordinator should recalculate these for both loads after the correction and tell the load owner if a delivery promise is now at risk.
Notify the carrier of the correction
The carrier's records should match the shipper's. If the carrier's system has Truck A on Load 5101 and the shipper has corrected it to Load 5102, the carrier needs to update its records too. Otherwise, the carrier's invoice, tracking, and POD may all point to the wrong load. A short written message with both loads and both trucks is enough.
Customer updates may need correcting
If the customer already received a pickup notice based on the wrong check-in, it may need a corrected update. The customer should hear the right pickup time and carrier details, so its receiving plans are based on the truck that is really coming.
Hypothetical example: times swapped
This example is hypothetical and does not describe a real customer. After a swap is corrected, Load 5101's record shows arrival at 9:10 a.m. and departure at 10:20 a.m., and Load 5102's shows arrival at 9:00 a.m. and departure at 11:45 a.m. Before the fix, Load 5102 looked like it had waited only 70 minutes. After the fix, it shows 2 hours 45 minutes, which may matter if the carrier bills detention.
What if the freight was loaded on the wrong truck?
If freight was loaded on the wrong truck, the team must decide quickly whether to unload and reload, redirect the truck to the right destination, or let it go and send the right freight later, and then update the BOL, the carrier's records, and the customer. An AI logistics coordinator should bring the load owner the options and handle the updates once a decision is made.
Options when freight is on the wrong truck
| Situation | Usual option |
|---|---|
| Truck still at the dock | Unload and reload on the correct truck |
| Truck left; same carrier; nearby destination | Ask the carrier to redirect, if the price is agreed |
| Truck left; different destinations far apart | Recall the truck or reship |
| Freight for the wrong customer delivered | Arrange return and send the right freight |
Documents must follow the freight
The BOL must list the freight that is actually on the truck. If the wrong freight was loaded, the BOL signed by the driver may now be wrong. A new BOL may be needed, and the carrier must update its records, including the PRO number. A PRO number is a tracking number a carrier gives to a shipment. Pallet labels and packing slips may need to change too.
Price and charges
A redirect or a second trip may cost more. The carrier should confirm any new charge in writing before the change. The rate confirmation, which is the document that states the agreed price and terms for one load, may need to be updated. Who pays depends on who caused the mix-up.
Decide fast, then document
When freight is on the wrong truck, speed matters more than perfect records in the first minutes. The load owner should decide what to do, and the AI logistics coordinator should handle the documents and messages right after. Every decision and change should still be saved, but saving should not delay the fix.
Tell the customers
If either customer's delivery changes, the customer should hear about it before the delivery window passes. The message should say what is coming, when, and what happens to any wrong freight that arrives. A customer that receives the wrong freight should be told not to accept it, where possible.
Claims and damage
If freight was moved between trucks, unloaded, or reloaded, the risk of damage rises. The dock should check the freight and note any damage before the second loading. If damage is found later, the record of the swap helps decide who is responsible.
Hypothetical example: caught after departure
This example is hypothetical and does not describe a real customer. A warehouse discovers 30 minutes after departure that Load 7201's freight went on the truck for Load 7202. Both loads go to customers in the same city. The AI logistics coordinator asks the carrier to swap the delivery addresses for the two trucks. The carrier confirms at no extra charge. The coordinator updates both BOLs, both carrier records, and both customers' delivery notices.
How can teams prevent wrong check-ins?
Teams can prevent wrong check-ins by matching trucks at the gate by load number and trailer number, not by carrier name, by getting truck details from carriers before arrival, and by checking the driver's paperwork against the pick list before loading. An AI logistics coordinator can supply the gate with the details it needs and flag mismatches as they happen.
Prevention steps
| Step | Who | Effect |
|---|---|---|
| Ask carriers for trailer and driver details at dispatch | AI logistics coordinator | Gate has specific details to match |
| Check in by load number and trailer number | Gate staff | Fewer swaps between trucks from one carrier |
| Match driver paperwork to the pick list before loading | Dock lead | Catches swaps before freight moves |
| Record trailer and seal numbers on the BOL | Dock lead | Proof of what left on which trailer |
| Review mix-ups monthly | Logistics manager | Finds sites or carriers that need changes |
Put the pickup number on the tender
Many swaps start because the driver does not have the pickup number, or has the wrong one. Every tender should include the pickup number, the customer reference, and the site's check-in instructions. A tender is the offer of a load to a carrier. When the driver arrives with the right number, the gate can match it exactly.
Use distinct pickup numbers
Similar pickup numbers invite typing errors. Some teams use pickup numbers with a check digit or a different format for each site. Others add the customer name and destination to the gate list, so the clerk can confirm with the driver.
Watch busy times
Swaps happen most when several trucks arrive close together, especially from the same carrier. During busy windows, an extra check at the gate or the dock is worth the time.
Train new gate staff
Many mix-ups happen when new or temporary staff work the gate. A short checklist, such as "match load number, trailer number, and carrier; ask the driver to show the dispatch," helps new staff avoid the most common errors.
Measure the mix-ups
The team should count wrong check-ins, how they were caught, and what they cost. A falling count shows the prevention steps are working. A site with many mix-ups may need a better gate process.
Teams handling documents that may belong to the wrong load can read how to check whether a delivery receipt reached the right load. Teams building a full pickup routine can start with the freight pickup guide.
Where does Wilson fit when the wrong truck is checked in?
Wilson, by Cartage, is an AI logistics coordinator that books loads with the customer's approved carriers, tracks each load, and compares site records with carrier records for every stop. Wilson tracks each load using the best source available: carrier API, GPS or ELD data where it exists, the carrier's website by PRO number, and email or phone where configured. An ELD, or electronic logging device, records a truck's driving time and can share location.
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.
How Wilson handles a wrong check-in
Wilson compares the truck details in the site's check-in with the carrier's confirmation for each load and flags mismatches. When a swap is confirmed, Wilson moves each event to the right load, updates the BOL and carrier records, and recalculates delivery estimates. Wilson works with carriers through email, API, EDI where the carrier supports it, and phone calls where configured, and it notifies internal teams through Slack, Microsoft Teams, email, or SMS.
Payment
When the carrier invoice arrives, Wilson audits and reconciles it against what was booked, using the corrected times and any agreed change. 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 Wilson does not do
Wilson does not move freight between trucks or decide whether to unload a truck. It flags the mismatch, corrects the records once the right load is confirmed, and brings decisions about freight, charges, and customers to the person who owns the load.
What Cartage asks in discovery
Cartage asks how trucks are checked in at each site, whether carriers share truck details in advance, how often trucks from the same carrier arrive together, and who corrects records today. These answers shape the check-in comparison an AI logistics coordinator runs.
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 correction is saved in the shipment record with change history.
This article is part of our complete guide to driver arrival and detention records.
FAQs
How should the shipment record change when the wrong truck was checked in?
Move each event to the load it belongs to, update the truck details, and keep the original entry marked as corrected. An AI logistics coordinator fixes both loads together.
How can a wrong check-in be detected?
By comparing the truck's carrier, trailer, and load number at check-in with the carrier's confirmation. An AI logistics coordinator flags mismatches before loading.
What if freight was loaded on the wrong truck?
Unload and reload, redirect, or reship, then update the BOL, carrier records, and customers. An AI logistics coordinator brings the options to the load owner.
How can wrong check-ins be prevented?
Check in by load and trailer number, get truck details in advance, and match driver paperwork to the pick list. An AI logistics coordinator supplies the details.
Should the wrong check-in entry be deleted?
No. It should stay in the record, marked as corrected, with who changed it and why. An AI logistics coordinator saves the full history.
Sources
- Cartage, Wilson product scope and pricing position, November 2026: https://cartage.ai
Ask Cartage to show how an AI logistics coordinator catches a wrong check-in and corrects the shipment record without losing the history: talk to the Cartage team.