Make the Substitution Differences Visible

A supplier offers an available product while the specified one has a long lead time. The offer may deserve serious review. The leadership problem begins when the conversation carries only the attractive difference and leaves everyone else to discover the consequences later.

Start with a comparison that makes the proposed change understandable to the people responsible for deciding it. Availability belongs in that comparison. So do the unresolved questions about fit, coordination, documentation and the work already planned around the original selection.

The federal GSAM Submittals clause, 552.236-72 provides one specific reference point. It says general submittal review does not permit departures from contract requirements, and requires written identification of deviations or changes in resubmissions. Those provisions belong to their applicable contract context; they are not universal instructions for every project. Have the responsible project participants determine the requirements governing yours.

Our editorial recommendation is a short difference record beside the formal submission. Identify the originally selected item, the proposed alternative and the exact versions of the documents being compared. Explain what prompted the request. Separate a supplier's stated availability from a confirmed commitment, and attach the dated evidence each statement depends on.

A useful opening question is: What would a reviewer need to notice if the attractive lead time were removed from this proposal? This helps expose the assumptions hidden by urgency. It also gives the proposer a fair opportunity to explain the alternative clearly rather than relying on a product name or a broad claim of equivalence.

Ask the responsible technical participants which adjoining work, approvals or operating needs require review. Keep their questions in the record with a named responder. A project coordinator can assemble those questions and track responses without deciding technical suitability or treating an unanswered issue as acceptance.

Consider an illustrative equipment proposal that arrives sooner but uses a different connection arrangement. The procurement discussion records the quoted availability, while the responsible reviewers examine whether the interfaces affect other work. The proposal stays visibly unresolved until the authorized decision is recorded. This scenario illustrates coordination only; it gives no installation or design instruction.

Where a change affects several trades, make the dependencies explicit. Record who needs the decision, what information remains missing and which planned commitment depends on the answer. An email copied to a long distribution list is weaker coordination evidence than a specific question accepted by a named responder.

Use the project's established submission and authorization process. Link the actual disposition to the exact proposed version, including its stated conditions. Ask the responsible decision maker to clarify any ambiguity before the team describes the alternative as approved. A meeting recollection should not silently become the basis for an order.

After a decision, check that the people preparing the next authorized commitment can find the same record. If the supplier later changes the proposed model or its stated terms, preserve that difference and route it for review. Do not assume a decision about one proposal answers a later, changed proposal.

For an internal check, count reviewed substitution requests with a versioned comparison, named decision owner and linked disposition, divided by all substitution requests reviewed. Track unresolved requests separately. This measure describes documentation completeness; it does not establish compliance, technical acceptance or project savings.

Choose one live request before the next procurement meeting. Ask a colleague who missed the original conversation to explain what changes and who decides. If that is difficult, improve the record before the team relies on its shorthand. Any eventual schedule or cost benefit needs its own evidence.

Source note: GSAM 552.236-72, March 2019 clause text on Acquisition.gov, reviewed October 26, 2026. The comparison record, scenario, questions and internal measure are The Dig Daily Dose's editorial recommendations.

What would make The Dig Daily Dose more useful to you? Share your feedback in three optional questions.