Last updated: April 14, 2026
Key Facts
- A material control layer tracks the physical material itself — not the transaction, not the shelf, not the project
- It enforces six states: Ordered, Received, Stored, Allocated, Installed, Reconciled
- Every state change is an immutable event on a ledger
- It sits between procurement, field ops, and financial systems
- Contractors typically recover $400K–$700K in working capital in year one
The gap in construction technology
Construction contractors have ERPs. They have project management tools. They have accounting systems and sometimes inventory apps. But there's a gap between all of these — the physical material itself.
ERPs track dollars. They know you spent $45,000 on conduit last month. They don't know where that conduit is right now.
Project management tools track tasks. They know the electrical rough-in is 60% complete. They don't know whether the material for the remaining 40% is in the yard, on a truck, or hasn't been ordered.
Inventory apps track shelves. They know Bay 4 has 200 feet of 1-inch EMT. They don't know if it's already allocated to Job 2847 or if the count is even accurate because someone moved it yesterday.
A material control layer fills this gap. It tracks the physical material through its entire lifecycle — from the moment it's ordered to the moment it's installed and reconciled. Every state change is an immutable event. When the system says material is somewhere, it's because someone put it there and nobody has moved it since.
The six material states
The core concept is deceptively simple. Every piece of material exists in one of six states:
1. Ordered
A purchase order has been created. Material is expected but hasn't arrived. The system knows what's coming, when it should arrive, and which job it's intended for.
2. Received
Someone physically received the material — at the yard, the job site, or the shop. It's been logged, categorized, and entered the ledger. From this moment, the system knows it exists. The key distinction: receiving is a physical event, not a PO matching exercise.
3. Stored
The material has been assigned to a location — a yard bay, a shelf, a truck, a gang box. The system knows its physical address. Purchasing can see it. Project managers can see it. If it moves, the system knows.
4. Allocated
A project manager has claimed the material for a specific job. It's spoken for. No one else can grab it without an explicit transfer. This is where double-ordering dies — because allocation is enforced, not aspirational.
5. Installed
The material has been installed or consumed. It exits active inventory. The job gets credited. The system adjusts. No phantom stock lingering in counts, inflating what you think you have.
6. Reconciled
The financial loop closes. What was ordered matches what was received, installed, and (if applicable) returned. Variances are surfaced. The ledger balances. This is where most contractors lose track — and where the real money is recovered.
Why this is different from an ERP
An ERP is designed around financial transactions. It answers: "How much did we spend?" A material control layer answers: "Where is the material, and what state is it in?"
These are fundamentally different questions, and they require fundamentally different data models. An ERP stores transactions. A material control layer stores state transitions — immutable events that form a complete audit trail for every piece of material.
You don't replace your ERP with a material control layer. You supplement it. The ERP still tracks your dollars. The material control layer tracks your physical reality. When they agree, you have confidence. When they don't, you know exactly where to look.
Why this is different from an inventory app
Inventory apps are designed for warehouses — static locations with stable stock. Construction material moves. It goes from the distributor to the yard, from the yard to the truck, from the truck to the job site, from one job to another.
In a warehouse, movement is the exception. In construction, movement is the norm. A material control layer treats movement as a first-class event — every transfer has a timestamp, a reason, and a complete audit trail. Nothing disappears between locations.
Why this is different from Procore
Procore is a project management platform. It manages schedules, documents, RFIs, submittals, and workflows. It's excellent at what it does, and RunBlu integrates with it.
But Procore doesn't track material state. It doesn't enforce material lifecycle transitions. It doesn't prevent double-ordering by showing what's already in the yard. These are different problems that require a dedicated system.
Think of it this way: Procore manages the project. RunBlu manages what goes into the project.
The financial impact
The average specialty trade contractor loses 15–30% of material value annually to a combination of over-purchasing, waste, theft, and reconciliation gaps. On a $10M revenue company with $4M in material spend, that's $600K–$1.2M walking out the door every year.
Most of this isn't malicious. It's systemic. When you don't know what you have, you buy more. When you can't trust counts, you build in buffer. When material moves and no one tracks it, it disappears. When reconciliation happens months after the fact (if it happens at all), discrepancies get written off.
A material control layer makes the data trustworthy. Enforced state transitions mean the system can't lie. When you trust the data, you stop over-purchasing. When you track movement, nothing disappears. When you reconcile in real-time, variances are caught immediately.
Contractors using RunBlu typically recover $400K–$700K in working capital in year one. The average ROI is 13x+. Not because the software does something magical — but because trustworthy data eliminates the waste that comes from operating blind.
Who needs a material control layer?
If you're a specialty trade contractor or general contractor in the $5M–$50M revenue range, and you deal with physical material across multiple locations (yards, trucks, job sites), you need a material control layer.
Specifically, if you recognize any of these patterns:
- Your purchasing team over-orders because they don't trust inventory counts
- Material regularly "disappears" between the yard and the job site
- Project managers hoard material because they're afraid it won't be there when they need it
- You reconcile material months after jobs close — if you reconcile at all
- You've tried spreadsheets, and they're always out of date
- You've tried inventory apps, and they can't handle the movement
Then you're operating without a material control layer. And you're losing money because of it.
What to do next
If you want to understand how much material value your company is currently losing, start with a Bleed Audit. It's a free diagnostic that quantifies your material bleed — the delta between what you purchase and what you can account for.
If you want to see how RunBlu works in practice, book a walkthrough. We'll show you the ledger, the state machine, and the real-time visibility that makes material control possible.