Educational overview only. Prudent Guardian (www.inspirecodingedu.com) is not an insurance company, broker, law firm, or registered investment adviser, and does not provide personalized insurance, investment, tax, medical, or legal advice. Verify details with licensed professionals and official issuers.
The words say short. The number of pieces is empty. You’re hunched over the edge of the dock, rain spotting the edge of the freight document where the carrier driver scrawled their signature 12 minutes ago before stepping back into their cab to warm up. The forklift idles 10 feet away, its operator waiting for your sign to move the pallets of corrugated tubing back into the overstock bay instead of staging them for the afternoon delivery run. You squint at the line item again, making sure you didn’t miss a faint digit smudged under the wet spot on the paper.
What This Pre-Bill of Lading Exception Note States
This is the pre-BOL you generated 48 hours ago when you scheduled the less-than-truckload pickup for the 16 pallets of custom extruded tubing bound for the regional distribution center in Des Moines. The form is pre-formatted to auto-populate the exception field with “SHORT” when the scanned pallet count at pickup is lower than the scheduled count listed on the original order, but the driver’s handheld scanner glitched mid-scan when they ran it over the top pallet’s barcode, so no number populated in the corresponding piece count field right below the exception flag. You know the carrier’s internal routing system auto-flags unpopulated exception fields for manual follow-up within 72 hours, so leaving this blank would delay the shipment’s processing at the first cross-dock hub, even if the count is actually correct. Illustrative example: A similar blank piece count exception on a shipment last month led to a 37-hour processing delay at the Des Moines hub, which pushed the final delivery to the industrial construction end customer back two full business days, triggering a series of check-in calls from their project manager that took 3 hours of your work week to resolve. You don’t want to repeat that process, so you take the extra 5 minutes now to resolve the blank field before the driver leaves the lot. You can cross-check the count against the log you entered in Dock Tally earlier this morning when you moved the pallets into the staging lane, to confirm you didn’t miscount during your initial walkthrough.
Side-by-Side Pallet Count Comparison You Complete On The Spot
You run this comparison immediately, no need to wait for the carrier’s support line to pick up, since you have physical access to all the pallets right now. Follow these steps to resolve the blank count before the driver departs:
- Walk the full length of the dock staging lane where the shipment is stacked, counting each wrapped pallet individually, marking a small tick on the blank edge of the pre-BOL for every unit you pass. Make sure to count partial pallets as full pieces for this log, since the carrier’s system counts each palletized unit as one piece regardless of how many individual tubing lengths are wrapped on it.
- Cross-reference that total with the printed scheduled count listed two lines above the blank exception field, verifying that you did not miss any pallets staged in the overhang of the bay door or tucked behind the empty pallet stack near the forklift charging station. If the counts don’t match, separate the missing SKUs and note their part numbers on the back of the pre-BOL before moving to the next step.
- Jot the verified total in the blank piece count field in blue ink, so it is distinct from the pre-printed black text and the red “SHORT” exception flag, then add a 2-word note next to it that reads “SCANNER GLITCH” to explain the discrepancy between the flagged exception and the actual matching count. Do not cross out or mark over the pre-printed “SHORT” flag, as altering pre-populated exception codes creates confusion in the carrier’s tracking system and can lead to the form being rejected entirely when it is processed at the hub.
- Flag down the driver before they pull out of the dock lot, have them initial next to your handwritten count and note to confirm they witnessed the physical count and agree the scanner failed to log the correct number of pieces. If they push back on signing, point to the empty count field and explain that leaving it blank will delay the shipment’s processing, which will also impact their delivery timeline for the rest of their route that day.
Once the driver adds their initials, you make a quick photo of the page with your work phone and email it to your operations lead, so they have a digital copy on hand if the carrier reaches out with questions before the shipment is delivered. You don’t send a copy to the carrier directly, since their system will pull the scanned version of the pre-BOL when the driver scans it into their handheld once they’re back on the road, and your handwritten notes will be visible in that scan. You give the forklift operator the all-clear to load the pallets onto the truck, then tuck the physical copy of the pre-BOL under your arm to file once the truck pulls away.
When You Pull This Exact Page Out Again Next Week
When you stand up right now, you file this signed pre-BOL exception note in the top slot of the locked filing bin next to the dock door, the slot reserved for pending LTL shipments that require post-delivery follow-up. You’ll leave it there until the Des Moines distribution center sends their delivery confirmation email, which typically lands in your inbox 6 business days after pickup. When you pull this exact page out then, you’ll first cross-reference the count listed on the delivery confirmation with the handwritten count you added today, to make sure no pallets were lost or misrouted in transit. If the counts match exactly, you’ll add the delivery confirmation number to the bottom of the page and move it to the closed shipment file for the month, where it will be stored for 18 months per your company’s record retention policy. If there is a discrepancy between the count you logged and the count the distribution center received, you’ll use the page as supporting documentation when you reach out to the carrier’s routing team to locate any missing units, since it has both your verified count at pickup and the driver’s signed confirmation of that count. You won’t need to track down extra proof of the shipment’s contents, because the pre-BOL already lists the part numbers and total weight of each pallet, which matches the weight log the driver collected when they pulled onto the scale at the edge of your lot before arrival. You’ll also be able to pull the photo you took of the page today from your email archive if the physical copy gets misplaced before you follow up, though you keep the locked filing bin organized enough that misplaced forms are rare. If the shipment is delivered on time with the correct count, you’ll note that on the page as well, so you can reference it if a similar scanner glitch happens with a future shipment, to show your team how quick adjustments at pickup prevent lengthy delays down the line. You’ll also add a small check mark to the corner of the page to indicate no follow-up was needed, so you can quickly sort through closed files at the end of the quarter when you run shipment accuracy reports for the operations leadership team.