Material readiness is the state in which every component a construction work package needs, from tagged equipment down to the last anchor bolt, has been received on site, verified, and allocated to that package before a crew starts work. On projects run under advanced work packaging, readiness is not a warehouse headcount or a gut feel. It is measured per Construction Work Package (CWP) through a Procurement Work Package (PWP), tracked against a Required-on-Site (ROS) date, and complete only at 100% receipt with the purchase order closed. Drawings issued but material missing means the package is not ready.
Why readiness is measured by package
Traditional delivery works in the wrong direction. Engineering issues drawings in design-office order, procurement buys as requisitions appear, and the field improvises around whatever arrives. The waste lands on the crew: fitters re-sequenced around a missing spool, supervisors walking the laydown yard instead of the workface.
AWP inverts the flow. The path of construction is agreed first, and engineering and procurement then deliver complete packages in exactly that order, finish-to-start, package by package. In that model, a warehouse full of material tells you almost nothing. The only question that matters is narrower: for this specific CWP, with this planned start date, is every line of material on site and allocated? Material readiness is how you answer that question with data instead of a walkdown.
The PWP: material readiness made visible
The instrument that makes readiness measurable is the Procurement Work Package. A PWP is not a physical deliverable and not a binder of requisitions. It is a data object, living in the procurement database, the material management system and the Level 3 schedule, that identifies all materials required to support one CWP and that CWP's ROS date.
That one object does a lot of work. It aligns procurement with construction priorities. It exposes the impact of engineering release dates on material availability. It drives expediting priority. It captures field-purchased MTO items such as supports, tubing and anchor bolts. It clarifies who owns which material (owner, engineering contractor, constructor or subcontractor, per the Material Responsibility Matrix). And it lets the project forecast construction readiness instead of discovering it at the workface.
Progress on a PWP is deliberately blunt: percent complete equals components received on site divided by total components required. The PWP starts when its first purchase order issues and finishes at 100% receipt. Without maintained PWPs, the Level 3 schedule is incomplete and material deliveries drift out of alignment with the path of construction, quietly, until a crew finds out the hard way.
The finish-to-start chain: EWP, then PWP, then CWP
Readiness only means something inside a package structure with real relationships. The chain is finish-to-start per package: the Engineering Work Package (EWP) finishes, the PWP completes, the CWP starts. The relationships are strictly one-to-one. Each CWP in the agreed sequence determines the scope, boundaries and need dates of its EWP and its PWP, and those boundaries are identical across all three.
Sequence matters at setup too. The PWP list is developed from the approved CWP list that comes out of the path of construction, and the PWP list comes before the purchase orders, with only long-lead items excepted. Deriving PWPs afterward from whatever PO groupings procurement happened to create is the classic failure mode: construction packages drive procurement packages, not the reverse. For how the CWP list itself gets built, see what advanced work packaging is.
Where the quantities come from
A readiness percentage is only as honest as its denominator, so it matters where the material quantities originate. Bills of material are generated from the 3D model, not from the procurement system. The procurement system can only reflect what has already been bought; the model is the design truth, supplemented for non-modeled scope through supplementary MTO development.
The material take-off itself has two layers. The Primary MTO carries the engineered, tagged design quantities. The Secondary MTO expands every standard detail, support, fastener, hookup component and consumable into individual digital rows, whether the item is modeled or not. That last clause is the one projects fight over, and it is worth holding the line: a quantity buried in a note on a standard detail is invisible to procurement, to warehousing and to the IWP. An individual digital row can be bought, expedited, received, kitted and verified.
One PO line, one CWP
The allocation rule that holds the whole system together is small enough to fit on a sticky note. A PWP may span multiple purchase orders, and one purchase order may serve many packages, but every PO line item supports exactly one CWP. Even on economy-of-scale common POs, the maximum granularity of line allocation is the CWP: keep the price break, split the lines.
The payoff is comparability. Once each line maps to a CWP, supplier forecast and actual delivery performance can be compared directly to CWP ROS dates, expediting can be prioritized by the ROS dates that actually matter, and a short shipment shows exactly which package it starves. Lump three packages' valves onto one line and a partial shipment becomes invisible: a single line has a single delivery status, so nobody can say which CWP is affected until the crates are opened. Worse, the CWP start gate of 100% material becomes unverifiable, because every package can claim the same valves.
| Traditional material tracking | Material readiness by package |
|---|---|
| Progress reported as bulk receipt percentages | Components received per CWP over components required |
| PO lines grouped by supplier convenience | Every PO line allocated to exactly one CWP |
| Expediting chases the loudest voice | Expediting prioritized by CWP ROS dates |
| Shortages surface at the workface | Shortages visible per package, ahead of the ROS date |
| The warehouse knows what is on site | The project knows which packages can start |
What "complete" actually means
The Definition of Complete for a PWP is fixed: 100% of components received on site and the purchase order closed. Confirmed delivery dates do not complete a PWP. 95% receipt does not. "Enough material for the first IWP" does not. The credit is binary on purpose: a PWP is 100% received or it is not, the same way a document is IFC in the document management system or it is not. Binary, package-level credit cannot be gamed, which is what makes a package skyline a forecast you can commit crews against.
The same rule has a sizing consequence that surprises people. Material is associated, released and verified at CWP level, so an oversized CWP means its entire material scope must be complete before clean execution can start. Splitting scope sensibly is part of managing material exposure, not just a scheduling preference; IWPs downstream cannot rescue a CWP whose material gate is too big to close.
Fabricated material is inside the system
Fabricated steel and pipe follow the same logic through the shop. Fabricators plan by Fabrication PWP (FPWP), mapped one-to-one to CWPs, so the shop sequences to feed construction rather than shop convenience or drawing arrival order. Trim and bolts ship with the first load for a CWP. Piece marks are unique project-wide, and weld IDs distinguish shop welds from field welds before fabrication starts, so QC and the packaging data agree without a side log.
Modules extend the doctrine rather than escaping it: the module yard is the site, relocated. Same packages, same data requirements, with ship-loose material visible through model attributes and itemized packing lists instead of a spreadsheet nobody at site can query.
Where readiness meets the crew
All of this exists to serve workface planning. CWPs dissect into constraint-free Installation Work Packages, and material is one of the constraints verified before an IWP releases to a crew; bag-and-tag kits are the field operation that puts a package's material in the crew's hands. An EWP issued for construction without its material is not executable work. Crews follow complete packages: drawings, and material, and no open constraints. For more on that handoff, read how workface planning fits into advanced work packaging.
Failure modes to watch for
A few patterns account for most material readiness grief:
- PWPs derived from POs. If the readiness ledger is built from procurement's groupings instead of the CWP list, it measures buying activity, not construction readiness.
- Lumped bulk lines. One line serving several packages makes short shipments invisible against ROS dates and the 100% material gate unverifiable.
- Secondary MTO pushed to field takeoff. The count drifts silently every time the standard detail revises, and the drift lands on an unbudgeted materials team.
- Confusing a plan with a condition. A confirmed delivery date is a forecast. Readiness is receipt.
- Oversized CWPs. The bigger the package, the bigger the material scope that must be 100% complete before it can start clean.
Material readiness is, in the end, a data discipline: one PWP per CWP, one CWP per PO line, quantities from the model, and a completion rule nobody can argue with. Get those four things right and the question "can this package start?" stops being a meeting and becomes a query.