The working question
Which unconfirmed step can still move the installation date?
Ask what “ordered” actually establishes
A purchase order can establish scope and price while leaving the delivery question open. A supplier may still need the required disposition of its proposed equipment submittal, a coordinated drawing, an initial payment, or written permission to begin fabrication. The useful procurement record identifies the event that starts the lead time, rather than treating every ordered item as equally secure.
Begin with one defined package and its installation need. State what must be available at the workface, including receiving and preparation time. A truck arriving at the gate is different from material being checked, accepted for the intended use, and available to the installation team. Record those boundaries before calculating a release date.
This article addresses the chain between commitment and readiness for a scheduled activity. The allowance guide addresses cost-state reconciliation. Neither an order value nor an allowance balance proves that a supplier has accepted the required delivery sequence.
Build a short, testable date chain
Identify the release event
Begin with the current specified equipment and drawing revision, reflecting requirements already developed by the design team and vetted with the owner. The general contractor checks the proposed product and coordination information through its required submittal before the designated design and owner reviews. Track that review and its conditions instead of reopening an established equipment selection. Missing design information needs clarification; an alternative product needs the prescribed substitution review and any required change authorization.
Write the supplier’s stated start condition in plain language: for example, an acknowledged fabrication release after the designated submittal is returned. Link the dated source that establishes that condition. Keep “purchase order issued,” “release sent,” and “release acknowledged” as separate observations when their dates differ.
Once the required design-submittal approval and other release conditions are met, the subcontractor should order promptly enough to protect the vendor-confirmed lead time. Plan the corresponding payment requirements early: the owner can fund eligible stored material through the agreed monthly progress process before site delivery. Obtain the contract’s required storage and payment approvals, material identification, title or other security for the owner, applicable insurance and waivers, and delivery arrangements. Merely ordering an item or approving its submittal does not make it eligible.
Work backward from the installation need
List receiving or preparation time, transportation time, and fabrication time separately. State whether each duration uses calendar days or an actual working calendar. A compact date chain is useful for an initial review, but it must not silently substitute seven-day arithmetic for the supplier’s production calendar, holidays, or capacity restrictions.
Retain the supplier’s current forecast
The latest acceptable release date is a planning calculation. Keep the general contractor’s estimate separate from a confirmed commitment. Ask the entity controlling each milestone to validate it: the manufacturer confirms fabrication and shipment readiness, the carrier confirms transport, and the receiving or installation team confirms its own availability. Where a subcontractor or vendor depends on its own supplier, the general contractor enables that supplier’s confirmation through the responsible trade partner rather than making the promise on its behalf.
Record the confirming entity and representative, confirmation date, scope, conditions, supporting evidence, and current specification, drawing, and submittal revisions. A conditional confirmation stays conditional. The general contractor retains responsibility for coordinating and reconciling the overall sequence; vendor confirmation does not replace required design or owner review. Give missing confirmations a responsible party and deadline. “Expedite” alone identifies neither.
Check delivery and purchase requirements together
Confirm the quoted scope, delivery location, receiving conditions, and interfaces with adjoining work. Record an alternative as an option until the responsible parties accept its specification, cost, time, and approval requirements. A proposed substitute can shorten one duration while creating a new review or installation constraint.
Worked example: three days beyond the need
Fictional teaching example · elapsed calendar days
A fictional office project needs a control cabinet ready for installation on December 14, 2026. The example assumes two days for receiving and preparation, four days in transit, and twenty-eight days from fabrication release to shipment. Each duration is an elapsed date offset at the same time of day; the example has no holidays or working-calendar restrictions.
Working backward gives December 12 for receipt, December 8 for shipment, and November 10 for release. At the October 26 reporting cutoff, the forecast release is November 13. Adding twenty-eight, four, and two days gives December 11 shipment, December 15 receipt, and December 17 readiness: three calendar days after the installation need.
These dates are the fictional general contractor’s planning estimates, not confirmed vendor commitments. The cabinet manufacturer must validate fabrication and shipment readiness, the carrier its transport allowance, and the receiving and installation parties their preparation time. If the manufacturer relies on another vendor, obtain that vendor’s confirmation of its own milestone too. Until those dated, scope-specific confirmations and their conditions are recorded, the arithmetic remains a scenario.
| Milestone | Latest date that fits | Current forecast |
|---|---|---|
| Fabrication release | November 10 | November 13 |
| Shipment | December 8 | December 11 |
| Receipt | December 12 | December 15 |
| Installation readiness | December 14 | December 17 |
The cabinet is already defined in the fictional specification, and the order has been issued. The contractor must confirm the current submittal revision and required design and owner review disposition, then obtain the supplier’s fabrication-release acknowledgement. Those records, rather than a repeated equipment-selection decision, determine whether an earlier release is supportable. Test the resulting dates in the actual schedule; the example does not establish a three-day delay to overall project completion.
A second, fictional October 28 record forecasts release on November 11. Its readiness date is December 15, still one day late. The earlier record remains in the worked CSV; the new forecast does not erase the first report or prove that the improvement occurred.
Use the procurement record
The blank CSV provides one empty working row. The worked file contains two dated observations of the same fictional package. Enter the package identifier, revision, cutoff date, scope, commitment state, duration basis, needed date, and current forecast. Keep the identifier stable across revisions. Use only the latest applicable observation when summarizing current packages; do not count historical rows as additional orders.
Complete the requirement-document and revision fields, design and owner review roles, required review reference, actual disposition and evidence reference, and contractor currentness check. Use the unresolved-requirement field to identify a gap and its next action. These entries carry the existing project basis into the record; filling them does not grant review approval or authorize a change.
Record the entity controlling the milestone, its scope, confirmation status and date, evidence and conditions, and the contractor’s separate forecast and coordination action. Check that the confirmation still covers the current revision. Unconfirmed values remain planning estimates.
Calculate the latest release and forecast dates in your reviewed scheduling or spreadsheet process, then record the results in the CSV. It does not calculate dates, validate a calendar, or warn about a missed milestone. A blank forecast means unknown; do not replace it with the need date to make the row appear complete.
Use the evidence reference to locate an authorized source in the project’s existing records. The public example uses invented references. Keep actual supplier terms, contacts, and confidential pricing in the appropriate private system. Before issuing a report, confirm that the referenced acknowledgement still covers the same configuration and delivery conditions.
Include the specification section, drawing revision, submittal identifier and revision, review disposition, and required reviewing roles in that referenced record. If a specification is unavailable, state the documented purchase or design basis and assign the gap for professional clarification before treating fabrication release as ready.
Companion tool · Version 1.1
Procurement milestone record
A blank record and a separate fictional worked CSV. The files contain plain data, with no formulas, macros, automated checks, or account connection. Read the article before adapting the fields.
Download blank CSVDecide what the next review must resolve
Read the chain from both directions. Can the installation team explain the needed date, and can the supplier support the forecast? Check that receiving time has not been counted twice or omitted. If several packages share a transport or receiving constraint, review that shared capacity rather than declaring each row independently achievable.
Close the item only when the required evidence is present and the downstream schedule has been reconciled. Preserve changes in forecast and assumptions as dated observations. This method supports a focused procurement discussion; it does not verify supplier capacity, authorize a substitution, or certify that the project milestone will be met.
Release edition · 2026-10-21 · Companion file version 1.1-review. All scenario dates and references are fictional.
Sources, method & limitations
The explanation, field structure, and fictional scenario are original teaching material. The cited primary guidance provides context; it does not endorse this resource or make its records an official approval process.
- GAO Schedule Assessment Guide, GAO-16-89G (2015)
Background on integrated schedules, dependencies, baseline comparisons, and the connection between time and cost. The date examples and review records here are original teaching devices, not a GAO assessment. - GAO Cost Estimating and Assessment Guide, GAO-20-195G (2020)
Background on defining estimate scope, documenting assumptions, and updating estimates with actual information. The examples do not reproduce a government cost model. - Caltrans Construction Manual, section 5-1: Project Records and Reports (November 2024)
Background on retaining organized project records. These CSV fields and examples are independently authored, not copied Caltrans forms or a mandated filing structure. - AIA Contract Documents: what is a submittal in construction?
Background on required submittals and their review against project requirements. The project’s own contract determines the responsible roles and procedures; a submittal disposition does not itself replace a required contract modification. - AIA Contract Documents: payment for materials stored offsite
Explains A201–2017 section 9.3.2 as one contractual approach: advance owner approval for offsite storage and payment, an agreed location, protection of the owner’s interest, and applicable insurance and transport arrangements. The executed project contract governs eligibility. - AIA Contract Documents: payment applications and stored-material reconciliation
Describes required payment support and moving stored value to completed work as incorporation occurs without charging for the same material twice. Use the project’s actual payment rules and applicable waiver requirements.
Apply the actual project requirements and obtain the relevant professional review. This guide does not establish contractual entitlement, certify technical performance, or replace authorized acceptance. No actual client record or project outcome is represented by the fictional examples.
Release edition · October 21, 2026. Source notes identify the references used in preparation. Report an error or review our correction policy.