What a bill of lading proves, and why your yard count needs one

A bill of lading is the carrier's receipt for what left the supplier's yard and what they're contractually on the hook to hand you at the gate. It's a shipping document with legal weight behind it, signed by the driver and, ideally, by whoever receives the load on your end. A packing slip isn't that. A delivery ticket isn't that either. Treating the three as interchangeable is how a project controls team ends up in a dispute over a count nobody can back up.
What's on a bill of lading
A proper BOL lists the shipper, the consignee, the carrier, a description of the freight, the quantity or weight, and the terms of the shipment. For construction material, that quantity line is the whole point: forty joints of 12-inch pipe, eleven precast box culverts, eighteen rebar bundles at a stated tonnage. The driver signs it at pickup. Whoever signs for it at your gate is attesting that what arrived matches what's written down, or noting the exception if it doesn't.
That signature at receipt is what makes a BOL function as proof of delivery for laydown yard material. Without it, you've got a document describing what was supposed to show up, with nobody confirming whether it matched what landed.
Bill of lading vs. delivery ticket
A delivery ticket is usually generated by the supplier's dispatch system and handed over at drop-off, sometimes as a courtesy, sometimes because the driver's in a hurry and it's faster than digging out the BOL. It can list quantities. It often doesn't get a careful count-and-sign at the gate the way a BOL is supposed to. Some suppliers use the terms loosely enough that a ticket called a "delivery ticket" and one called a "BOL" are functionally the same piece of paper, and some don't. That inconsistency is exactly why it matters which one you're filing against an invoice.
If a dispute ever goes past your desk, a signed BOL carries more weight than a ticket nobody checked against the load. A project controls team that files tickets without confirming they were signed at receipt is building a paper trail that looks complete and isn't.
Why your yard count has to tie back to it
The BOL tells you what was supposed to land on a given day. It doesn't tell you what's still sitting in the yard three weeks later, what got used, what got moved to another laydown area on site, or what quietly walked off. That's a separate problem, and it's the one most project controls teams solve with a clipboard: someone walks the yard, counts what they can see, eyeballs the stockpile volumes, and tries to reconcile that against a stack of BOLs and an invoice that doesn't always match either.
The gap shows up in predictable places. A supplier bills for sixty joints across three deliveries, but nobody re-counted the pile after each one landed, so the running total is really just three BOL numbers added together on faith. A rebar bundle count comes up short and nobody can say whether it was never delivered, delivered and misplaced, or delivered and already tied into formwork before anyone recounted. An aggregate stockpile looks smaller than last week's estimate, but "looks smaller" isn't a number you can put in a reconciliation report next to an invoice line.
None of that is a document problem. It's a counting problem. The BOL answers what left the supplier. Your yard count is supposed to answer what's on site right now, and a hand tally against a guessed pile volume is a thin thing to put next to a signed shipping document when the numbers don't line up.
A weekly, counted record of the yard closes that gap from the other side. A drone flight over the laydown yard produces unit counts for pipe joints, precast, and rebar bundles, plus measured volumes for the stockpiles. That's the number you put next to the BOL and the invoice when you're reconciling.
Next time the invoice and the BOL don't match the pile in front of you, it helps to have a yard count you can stand behind.