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 last carton is on the dock. The tally sheet is not totaled yet. The air around you still smells like diesel and corrugated cardboard, and the driver is leaning against their cab door scrolling on their phone, waiting for you to sign off so they can pull out of the bay. You’re still holding the golf pencil you tucked behind your ear at the start of the unload, smudges of graphite on the cuff of your work glove.
What the paper says: piece count just finished
Every mark on the document corresponds to a detail you observed as the liftgate lowered each skid to the dock. The pre-printed line items list expected SKUs, quantities, and the purchase order number tied to the shipment, and you’ve scrawled your actual count next to each line, crossing out the pre-printed number only after you confirmed it twice by counting cartons on the corresponding skid. A small, circled asterisk next to skid 3 marks the carton with the crushed corner you spotted as soon as it came off the truck, and the scribble next to skid 7 notes that half the shrink wrap was torn off when it was stacked in the trailer, so some cartons shifted during transit. You didn’t write any of these notes from memory; you jotted each one down the second you noticed the detail, so the record is as accurate as possible in the moment.
Entries you leave alone
You leave the pre-printed expected counts fully visible, no blacking them out or scribbling over them so hard they’re unreadable, because that context matters for anyone reviewing the document later. You leave the driver’s initial pre-unload signature intact, even if they mentioned they thought a skid was missing when they picked up the load from the origin facility, because that comment is not part of your physical count on the dock today. You leave the pre-printed carrier routing information exactly as it is, even if you know the driver took a different route to get to your facility, because that detail is not relevant to the piece count you just finished. Any changes you make to the document are limited to the actual count lines and damage notes that tie directly to what you can see in front of you on the dock right now.
The ten-minute check: piece count just finished
This quick, structured review ensures you don’t miss critical details before the driver leaves the property, and follows these clear steps:
- First, cross-reference every hand-written count next to each skid number against the count logged in your handheld device for that same skid. If there’s a discrepancy, walk back to the skid stacked by the bay door and count the top layer, then multiply by the number of layers to confirm, adjusting the count on the document only if you find a math error in your initial scribble.
- Second, verify every notation about damage is paired with a quick photo timestamp you took as you unloaded the skid, so you can reference the image later if needed. If you forgot to take a photo of the crushed carton on skid 3, snap it now before the driver pulls away, and jot the photo’s file reference number next to the damage note. You can cross-reference the timestamp with the entry you logged in Dock Tally if you need to confirm the unload window later.
- Third, add up all the individual skid counts twice, to make sure your final total matches. If the first sum is 412 and the second is 413, add them a third time before writing the final total at the bottom of the page. Illustrative example: if you received 127 more cartons than the pre-printed expected count, you write that number in the “overage” line in the margin, with a small note that the extra cartons are all the same SKU listed for skid 5, no mixed stock.
- Fourth, sign your full name and employee ID number in the designated recipient signature line, and mark the date and exact time you finished the count, down to the minute, so there’s no confusion about when the load was officially accepted on the dock.
- Fifth, ask the driver to sign next to your signature, and give them the carbon copy of the document they’re required to carry for their route logs.
Where the page goes: piece count just finished
After the driver climbs back into their cab and pulls out of the bay, you don’t tuck the original document into your back pocket where it can get crumpled or stained with grease from your lunch pail, or leave it on the edge of the dock where it can blow into the parking lot or get soaked by a sudden mid-shift rain shower. You first slide the original copy into the waterproof clear sleeve hanging by bay 4, the spot designated for all incoming load documentation from that day, so it stays with the other delivery records from your shift, sorted by the time each truck arrived. At the end of your shift, when you’re doing your final walkthrough before clocking out, you drop the entire sleeve of documents into the labeled tray by the shipping office door, where the admin team pulls each page the next morning to log the received counts into the central inventory system. You keep a small, folded black and white photocopy of the page in the inner pocket of your work bag for the next 30 days, just in case you get pulled aside to answer questions about the load, so you don’t have to hunt through the office’s filing cabinets to find your original notes.
Assumptions you do not make
You don’t assume the 127-cartoon overage means the origin shipping facility intentionally sent extra stock to cover a previous shortage, you only note that you received more than the pre-printed expected count, no guesswork about the reason for the discrepancy. You don’t assume the crushed carton on skid 3 is full of damaged goods, or that the contents are unharmed, you only note that the outer carton has a 6-inch gash along the bottom edge, no speculation about the state of the inventory inside until the warehouse team opens the carton for formal inspection. You don’t assume the driver is responsible for the damage, or that the damage happened during loading at the origin facility, you only log what you see when the carton comes off the liftgate, no assigning blame anywhere on the document. You don’t assume the inventory team will see your margin notes about the overage without a follow up, but you don’t add extra, unprompted notes to the document that aren’t tied directly to the count you just finished, to avoid cluttering the record with irrelevant context. You don’t assume the pre-printed expected count is wrong even if it doesn’t match what you received, you just log your actual count and let the back-office teams reconcile the difference between the two numbers.
When you next pull this document
When you pull this document back out, whether it’s a week later when the inventory team asks about the overage on purchase order 4729, or a month later when the origin shipping facility reaches out about a missing batch of cartons, you first confirm the signature and timestamp at the bottom are yours, so you know you’re referencing the right load, not a different delivery from the same day. You cross-reference your handwritten notes with the photos you took during the unload, to jog your memory about the crushed carton on skid 3 and the torn shrink wrap on skid 7, so you can speak to exactly what you observed that day, not what you think you might have seen. You only reference the marks you made on the page during the ten-minute check right after the unload, not any details you think you remember about the load that aren’t written down, because memory fades far faster than graphite on paper. If there’s a question about how you arrived at your final count, you walk through the process of adding up the individual skid totals twice, and explain any margin notes you wrote next to the overage line, no guessing about details you didn’t log at the time. You don’t add new notes to the original document after the fact, any additional context you share is written on a separate, clearly dated note attached to the original page, so the timeline of observations stays clear for anyone who references the file later.