Materials

Why sites lose materials they already own

Three failures, and they compound.

The first is the re-order loop. Stock arrives, goes into a laydown, and becomes invisible — so when the next requisition is raised, nobody checks, because there is nothing to check. The material is ordered again. And at closeout the project discovers it owns a great deal of cable it never needed, purchased twice, now worth its scrap value. A requisition that does not interrogate stock first is not a requisition. It is a habit.

The second is theft, and the mechanism is exactly the sentence at the top of this page: you cannot miss what you never logged. Unrecorded stock cannot go missing, in the strict sense that its absence produces no signal anywhere. Construction site theft is estimated in the hundreds of millions to around a billion dollars a year in the US alone, with under a quarter of it ever recovered — a figure we set out in full on the delivery-notes page. But the estimate is not the interesting part. The interesting part is that a site with no inventory record cannot even participate in the statistic, because it will never know.

And the third is waste, which is the quietest. Material waste runs above ten per cent of purchased quantity on a typical project — the figure sits on our material-procurement page — and site studies routinely find actual wastage at roughly double the allowance carried in the estimate. But waste is only measurable if consumption is attributed to something. Issue material against an activity and the overrun is visible. Issue it as “some rebar for level three” and the overrun is simply the way things are.

What site inventory actually requires

• Issue-to-site discipline — against a work order and a location, never against a vibe. “Some rebar for level three” is not an issue record. It is a story about rebar. Material drawn against a specific activity and location is what makes consumption per activity computable, and consumption per activity is the only thing that makes waste measurable. Without it, every overrun is invisible and therefore normal — and a site where waste is normal will not reduce it, because it has never seen it.

• The requisition must interrogate stock first. This is a one-line control and it closes the whole re-order loop. Before a purchase requisition goes out, the system checks what is already in the laydown — and, ideally, in the laydowns of the other projects. The alternative is a portfolio quietly buying, twice, materials it is simultaneously writing off as dead stock somewhere else.

• Secure storage tiers by pilferability, because not everything walks equally. Copper, cable and power tools disappear. Aggregate does not. Treating both to the same storage regime means over-securing the sand and under-securing the thing that is actually worth stealing — which is how a site ends up with an impressively locked compound and no cable in it.

• Storage conditions can void an acceptance you already have. This is the one that catches people. Cement ages, so FIFO is not housekeeping, it is compliance. Waterproofing membrane left in UV degrades. Rebar in ground contact contaminates. Material that passed its inspection on arrival can fail on the day it is installed — and the inspection record that said it was acceptable will still be sitting there, correct and useless, describing a condition that no longer exists.

• Reorder points come from arithmetic, not from instinct. Consumption rate multiplied by replenishment lead time, plus a buffer. Set the alert on that, and it fires when it should. Set it on a low-stock feeling, and it fires when somebody notices — which is generally after the front has stopped.

• Owner-furnished materials carry the same discipline and more exposure. You did not buy them, and you are holding them. Custody, insurance, condition on receipt, and a record of exactly what arrived — because when an owner-furnished item is damaged or missing, the conversation about who is responsible will be reconstructed entirely from documents, and the party without documents will lose it.

How the shrinkage conversation should go

Received, minus issued, minus what is physically on the shelf, equals shrinkage. It is arithmetic, and it is the only honest starting point.

Which means the count has to happen. Cycle-count by ABC frequency — the high-value, high-pilferability classes often, the aggregate rarely — rather than one enormous annual count that nobody believes and everybody dreads.

And when the number comes out non-zero, investigate it rather than absorbing it. A shrinkage figure that is quietly written off each month is not a control; it is a subscription.

How Zepth runs site inventory

Per-project stock with a full movement audit trail — received, reserved, issued, returned — and issue-to-site workflows that draw material against an activity and a location rather than against a name and a nod.

Low-stock alerts computed from consumption and lead time. Reservations against work fronts, so the material that is spoken for is visibly spoken for. And the whole record joins to the delivery notes that brought the material in and the inspections that accepted it — which is what turns three separate systems into one answerable question.