The submittal is approved. Can the equipment actually arrive on time?
Connect submittal approvals, fabrication, delivery and installation so a green procurement log does not hide a late construction handoff.
The procurement log says “approved.” The superintendent asks when the equipment will arrive. Someone opens an email thread, and the answer changes.
Approval, release for fabrication and a confirmed delivery date are different events. A useful construction procurement schedule follows the whole chain, including the decisions that have to happen before a supplier can make a reliable commitment.
Here is a practical review method for a general contractor buying long-lead equipment. The example below is hypothetical, not an SP4N customer result.
#Work backward from a real installation need
Suppose an air-handling unit must be available for a planned installation. Do not start by asking whether its submittal is late. First ask what “available” means: delivered to the project, inspected, accepted, lifted into position, or ready for startup. Those dates can be weeks apart.
Write down the installation activity and its prerequisites. Check access, structural readiness, the lifting plan, power, controls, protection and storage. Then work back through transport, factory testing where applicable, fabrication release and the approved information the manufacturer needs. Have the people responsible for those steps validate the sequence.
The GAO Schedule Assessment Guide1 treats a reliable schedule as an integrated model of the work. Applying that principle here means connecting procurement milestones to the work they enable, rather than keeping delivery promises in an unrelated spreadsheet.
#Separate the dates people tend to combine
For each critical package, track these fields separately:
- Submittal issued and revision number.
- Review returned, with outstanding comments identified.
- Resubmittal required and responsible party.
- Fabrication release authorized, with evidence.
- Supplier acknowledgment of the released requirements.
- Current production and shipment commitments.
- Delivery need date and installation activity.
Add the source and date of every commitment. A vendor email from last month is weaker evidence than a current written confirmation of the released configuration. Neither proves that every upstream prerequisite is complete.
Avoid turning an optimistic supplier estimate into an unqualified contractual promise in the log. Preserve the supplier's qualification, such as “subject to approved controls drawings.” That condition may be the most important part of the update.
#Put the unresolved decision next to the delivery date
Consider an approved unit with an unresolved electrical connection. The procurement line may look green because the mechanical review is complete. The manufacturer may still be waiting to release a component.
A useful row reads: “Delivery depends on electrical confirmation; response owner identified; decision needed before release.” A weak row reads: “With vendor.” The first gives the team something to resolve. The second gives everyone somewhere to hide.
For a late package, examine alternatives without assuming they are acceptable: resequencing, temporary access, revised installation methods or a substitute. Confirm design, safety, warranty and contract implications with the responsible parties before proceeding. A faster delivery does not automatically make an alternate product suitable.
#Run a short exception review
Review packages with an unconfirmed release, changing delivery date or shrinking time between delivery and installation. Ask what changed since the last meeting, what supports the new date, and which downstream activity is affected. Keep routine packages out of the discussion unless their evidence has changed.
Track the age of unconfirmed commitments alongside overdue submittals. A log can contain very few late submittals and still carry a serious procurement problem.
#Use the review to make one decision
A useful exception review ends with an instruction someone can carry out. For the air-handling unit, that might be to obtain written confirmation of the electrical requirement by Thursday, then ask the supplier whether the confirmed requirement changes the release or shipping date. Record the owner of each step separately. The person chasing the design answer may not be the person authorized to release fabrication.
At the next review, compare the evidence with the commitment. Do not move the installation date simply to make the procurement row look comfortable. First identify what work would actually move, whether the crew can be reassigned and whether the lifting arrangement remains available. If the team chooses a different sequence, record that decision in both the procurement log and the working schedule.
Before the next meeting, pick one long-lead package and trace it from today's unresolved decision to installation. If the chain breaks, that is the next question to answer. For a broader source-record review, see how SP4N approaches project evidence.