Procurement Log

Definition

A procurement log is a controlled register that tracks every item of material, equipment, and subcontracted work required to deliver the project. Each row records the item, specification, responsible engineer, required-on-site (ROS) date, procurement lead time, current status, and price. In construction the procurement log is one of the three foundation registers alongside the schedule and the cost report; in complex IT programmes an equivalent vendor log tracks third-party components, licences, and lead-time-critical hardware.

Purpose

Late materials are the single most common cause of avoidable schedule slip. A procurement log exists to make lead time visible early enough to act. When a 22-week valve is missed in the log until week 18, no amount of expediting rescues the schedule. When it is captured in month one, the sequence can be adjusted, an alternative sourced, or the design revised.

Key Columns

• Item ID and description
• Specification / drawing reference
• Required-on-site (ROS) date driven by the schedule
• Lead time (design, procurement, fabrication, transit)
• Order-by date (ROS − total lead time − safety margin)
• Responsible engineer / package owner
• Status (specified, tendered, awarded, on order, in fabrication, delivered)
• Value (budget, committed, forecast)
• Risks and notes

Real-World Construction Example

A 400 MW gas turbine project maintained a procurement log of 1,850 line items. Twenty items dominated the schedule — the turbine itself, the generator, the HRSG, the main transformer — with lead times ranging from 40 to 78 weeks. The log flagged an emerging issue in month four: the main transformer manufacturer had extended lead time from 52 to 68 weeks due to global grain-oriented electrical steel shortages. Because the log was reviewed weekly with the design team, the project team resequenced pre-commissioning to allow the transformer to arrive later, avoided a 16-week critical-path hit, and — critically — did not discover the problem in month twelve when the response options would have been half as many.

Real-World IT / Agile Example

A data platform migration required 47 third-party components — hardware appliances, security certificates, software licences, and consultant contracts. The programme kept a vendor log that mirrored a construction procurement log in every respect. During iteration three, the log showed the HSM (hardware security module) as "in negotiation" 21 weeks before its ROS date — with a documented lead time of 26 weeks. The programme escalated procurement to executive attention, closed the contract in three weeks instead of the usual eight, and preserved the go-live date. Without the log surfacing the number, the HSM would have been noticed at week 24 and the go-live would have slipped by four months.

Best Practices

• Start the log at concept design, not at construction mobilisation. Long-lead items are lost in the design phase.
• Every row has one named owner. Shared ownership is no ownership.
• Review weekly at project level and monthly at steering committee level.
• Link every item to the schedule activity that depends on it — the ROS date is not a wish, it is a calculation from the critical path.
• Track a "float against ROS" figure. When it approaches zero, escalate.

Common Mistakes

• Starting the log after tender award; long-lead items are already at risk.
• Recording nominal lead times from catalogues instead of confirmed vendor lead times.
• Ignoring transit, customs, and site-handling time; a 20-week factory lead time can become 26 weeks door-to-crate.
• Treating the log as an administrative artefact rather than a working tool; ownership drifts and updates stop.
• No linkage to the schedule — the log lives on someone's laptop, the schedule lives in P6, and neither updates the other.

Expert Tips

• Highlight the top 20 items. A modern project has thousands of items; the top 20 by lead time drive 80% of risk. Track them on a one-page dashboard.
• Confirm lead times in writing. Vendor phone estimates are optimistic. Confirmed lead time letters are the only durable data.
• Include design and approval durations. "Lead time" starts when the last approved drawing exists, not when the PO is raised.
• Publish the order-by date, not just the lead time. The order-by date creates urgency; the lead time is abstract.
• Reconcile against the schedule monthly. A quiet drift between the two is normal and dangerous.

Practical Lessons Learned

• Every mega-project post-mortem in the last two decades that traced schedule slip to root cause found late procurement decisions in the top three drivers.
• The projects that finish on time invest disproportionately in procurement log discipline during the first six months.
• The single best mechanism for reducing late-material risk is a weekly procurement stand-up with design, procurement, and construction in one room.

Key Takeaways

• The procurement log makes lead time visible early enough to act.
• Start at design, not at mobilisation.
• Every row has one named owner and a linked schedule activity.
• Order-by date is the operational number; lead time alone is not enough.
• Weekly cross-discipline review is the discipline that actually works.

Related Encyclopedia Entries

• Critical Path Method
• Risk Register
• Dependency Mapping
• Schedule Compression

Related Research Articles, Case Studies & Tools

• Procurement Log Template
• Project Controls Academy: Procurement
• Long-lead equipment case studies
• Procurement lead time and schedule risk