Yard report, updated weekly

What a yard report is and why it's not your delivery log

Close-up of stacked steel reinforcing bars in a material yard.

If you run project controls on a laydown yard, you already have a daily delivery log. Every truck that rolls through the gate gets logged: ticket number, material, quantity, timestamp, maybe a signature. It's a good record of what arrived. It is not a record of what's there now.

That gap is where a yard report comes in, and it's the thing most project controls teams are missing without quite realizing it.

The delivery log answers one question

A daily delivery log tells you what came through the gate on a given day. It's built from paperwork: bills of lading, supplier tickets, receiving signatures. It's chronological, it's transaction-based, and it's only as good as whoever wrote down the numbers at the gate.

What it doesn't tell you is what's left. Material gets pulled for installation, shifted between laydown areas, double-counted across two tickets, or quietly consumed faster than the schedule says it should be. None of that shows up in a delivery log, because a delivery log only records the moment of arrival. It has no opinion about Tuesday's pile versus Thursday's pile.

The yard report answers a different question

A yard report is a snapshot of what's physically sitting in the yard at a point in time. Not what was shipped, not what was invoiced: what's there, counted or measured, as of this week. Pipe joints get counted. Rebar bundles get counted. Precast units get counted. Aggregate and sand stockpiles get measured for volume, because you can't count a pile of crushed stone the way you count a stack of pipe.

That distinction between counting discrete stock and measuring loose material is most of what makes a yard report useful. A clipboard tally can get you a rough count of joints if someone walks the rows carefully enough. It almost never gets you an honest pile volume. Most of the "we paid for 400 tons, there's clearly not 400 tons here" conversations trace back to someone eyeballing a stockpile and writing down a guess.

Why the difference matters when you're reconciling against invoices

The delivery log says what was shipped. The invoice says what was billed. The yard report says what's physically there. When all three agree, reconciliation is boring, which is the goal. When they don't agree, the yard report is what tells you where to look.

Material delivered and installed shows up as a normal gap in the count, nothing to chase. Material delivered, logged, and never installed but also missing from the yard count is a real problem. And every so often the invoice quantity never matched what came off the truck in the first place, which the delivery log alone won't catch either.

Without a yard report, a project controls team is trying to reconcile two documents against each other, delivery log and invoice, with no independent check on physical stock. You're trusting the paperwork to catch errors in the paperwork. A weekly stock record breaks that loop by giving you a third number that didn't come from a supplier or a hauler.

A delivery log without a yard report is half the picture

Most yards running a straight delivery log and no independent stock check find out about a shortage or an overbilled stockpile weeks after it happened, usually during a progress payment dispute when it's expensive to sort out. A weekly yard report catches the gap closer to when it opened, while there's still a chance to ask the right question before the invoice gets paid.

Material Tracking turns a weekly drone flight over the yard into that counted, measured record, pipe joints and precast counted, rebar bundles counted, aggregate stockpiles measured for volume, so project controls has a yard report to set next to the delivery log and the invoice instead of a guess and a clipboard.

If your reconciliation process is still built on a hand tally and hope, it might be time to see what a weekly yard report looks like for your site.

Start a pilot

← Back to the blog