Long-lead reporting should connect release, submittal, approval, fabrication, delivery, substitution, installation, testing, and schedule consequence.

Start with the item that can control the project

Identify the equipment, assembly, material, or service; the specification and drawing reference; responsible trade; procurement lead; required-on-site date; installation window; area or system served; predecessor work; startup, inspection, and testing needs; and the project milestone that depends on it. A generic “long-lead list” is not enough if it cannot explain why one delayed item matters to enclosure, permanent power, elevators, life safety, turnover, or another controlling sequence.

The register should distinguish an early warning from an established constraint. Design development, incomplete selections, allowance scope, owner-furnished equipment, utility-furnished components, imported material, custom fabrication, seasonal demand, constrained manufacturing, specialty labor, permits, and required agency or professional reviews can create different paths. Record the source and date of each reported duration rather than turning a vendor estimate into a fixed fact.

Build the complete procurement sequence backward

Begin with the date the installed system must be ready for the work that follows. Work backward through testing or commissioning, startup, installation, delivery, site readiness, shipping, fabrication, approved-for-fabrication documents, technical review, resubmittal allowance, release, commercial agreement, final selection, and any design or owner decision needed before the submittal can be completed. Include mockups, samples, utility coordination, delegated design, engineering calculations, authority review, and factory testing where they control release.

USACE scheduling guidance uses a connected submit, approve, procure, fabricate, and deliver sequence for long-lead activities. A lender’s project does not inherit that contract requirement automatically, but the sequence is a useful test: if the schedule shows only delivery, it may hide the review, decision, and manufacturing steps that determine whether delivery is achievable. Float and recovery options should be evaluated against the connected path, not a single promise date.

Require evidence for each reported state

A procurement log may say planned, released, bought, approved, in fabrication, shipped, delivered, or complete. Define what each state means and what record supports it. Depending on the item, evidence may include a subcontract or purchase order, approved manufacturer and model, submittal transmittal, reviewed shop drawings, approved deviations, deposit or invoice, fabrication confirmation, factory-test result, shipping record, bill of lading, delivery ticket, photographs, receiving inspection, stored-material record, installation observation, startup report, test, or commissioning issue disposition.

Commercial commitment and technical release are not the same. A purchase order can preserve price or manufacturing capacity while design information remains open; an approved submittal can still lack a released purchase order; a fabrication report can omit the component that actually controls shipment. The monitor should state the evidence reviewed, information reported by others, material gaps, and the date of the status rather than converting partial documentation into a broader assurance.

Treat substitutions as controlled changes

A substitution may alter capacity, dimensions, weight, support, power, controls, connections, clearances, accessibility, acoustics, fire or smoke performance, envelope continuity, finish, maintenance, warranty, spare parts, commissioning, approvals, or expected life. The request should identify the specified basis, proposed product, reason, technical comparison, affected drawings and specifications, design-professional response, owner or authority decisions, cost and time effect, procurement advantage, interfaces, and required follow-up.

An RFI or submittal should not quietly rewrite design intent. AIA construction-administration guidance distinguishes substitutions from ordinary RFIs and submittals because an accepted substitution may require a change to the contract documents. The exact approval path follows the project agreements. For monitoring, the practical control is to keep the item pending until the technical, contractual, budget, schedule, permit, and lender-required decisions are visible and the current construction documents reflect the accepted result.

Connect procurement to the draw and remaining cost

A deposit, stored-material request, fabrication payment, or early purchase can legitimately precede installation, but each has a different evidence and risk profile. Read the current request against loan eligibility, contract terms, title and payment evidence where required, identification to the project, insurance, storage, protection, prior funding, delivery, installation, and the amount still needed to complete the item. Do not fund the same value as deposit, stored material, delivered material, and installed work without a controlled reconciliation.

Cost exposure can arise from escalation, cancellation, restocking, expediting, premium freight, storage, redesign, temporary service, out-of-sequence work, remobilization, testing, or extension of general conditions. Approved and pending substitutions should appear in the change, contingency, buyout, schedule, and remaining-cost record. A less expensive unit price does not establish a project saving if coordination or delay moves cost somewhere else.

Escalate the consequence and follow through acceptance

When the current forecast no longer supports the need date, define the affected milestone, available float, downstream work, operating or occupancy consequence, current evidence, responsible decision, and date by which action is needed. Recovery may involve accelerated review, alternate sourcing, resequencing, partial release, temporary equipment, early enabling work, premium logistics, a qualified substitution, or a revised completion plan. State which option is proposed, approved, funded, and incorporated into the schedule.

Close the procurement item only when the required scope reaches its agreed endpoint. Delivery is not installation; installation is not startup; startup is not testing; testing is not authority, owner, or commissioning acceptance. Preserve remaining punch work, training, documentation, warranty, spares, controls integration, seasonal work, and open technical issues so the procurement register does not declare success while the system still cannot support completion.

Primary sources

Sources and technical references.

Source review current as of September 2, 2026.