Product substitutions: documenting equivalent performance
Admin · 22 October 2026
Illustrative image. Photo by Daniel McCullough on Unsplash. Unsplash License.
A proposed substitute can offer useful advantages in availability, cost or delivery. It also changes the information the project needs to review. A supplier’s description of an item as equivalent should begin an assessment, not complete it. The project needs to establish which requirements matter, what evidence supports the alternative and what consequences follow for the complete arrangement.
For buyers and design managers, the task is to coordinate a decision that competent specialists can support and authorised people can make. Technical equivalence, commercial acceptance and permission to proceed may be separate matters. A clear substitution record connects them without implying that one email or product comparison completes every required step.
Identify the approved basis
State the current product, specification and relevant design references. Explain what the existing choice is intended to provide. If the original basis is unclear, resolve that question before comparing alternatives. The project cannot reliably assess equivalence against an ambiguous requirement or an outdated product description.
Identify who owns the requirement and which specialists must review the proposal. A client may decide an operational preference while a designer assesses technical suitability. The buyer should know whose response is required and what authority it represents. Avoid treating general agreement in a meeting as evidence that all relevant responsibilities have been addressed.
Explain the reason for substitution
Record the trigger, such as changed availability, a supplier suggestion or an identified delivery issue. State the consequence of retaining the current choice. This gives decision makers a practical comparison and helps them understand the urgency. An early alternative can be explored differently from a late proposal affecting work already manufactured.
Keep the claimed benefit separate from the evidence. A shorter lead time may be indicative rather than committed, and a lower price may exclude associated work. Identify those conditions before presenting the proposal as an established saving or programme improvement. The appropriate reviewers should assess the complete consequence.
Build a requirement-by-requirement comparison
Ask the relevant designers to identify the characteristics and evidence that matter to the actual application. Record the proposed item against those requirements, with references to supporting information. The comparison should make gaps visible rather than simply place two marketing datasheets side by side and ask reviewers to infer suitability.
Different requirements may need different evidence. Appropriate technical specialists should determine what is adequate and whether any further assessment is necessary. A familiar product category or similar appearance does not establish identical performance. The record should explain what has been reviewed and the limits of the conclusion.
Assess the complete arrangement
Examine interfaces, associated components and installation requirements through the relevant specialists. A substitute may meet one headline characteristic while changing another part of the solution. Identify the affected drawings, schedules and package boundaries. The assessment should consider what the project would actually build and operate.
Consider a hypothetical equipment substitution with a similar capacity description. The relevant teams may still need to review dimensions, connections, supporting arrangements and maintenance access. The buyer should not infer equivalence from the capacity alone. The decision requires a coordinated account of the complete proposed use and its supporting evidence.
Check the product information
Identify the exact product and variant in the proposal, together with current source documents. Government construction products guidance for Great Britain provides a starting point for relevant regulatory questions. Applicable requirements depend on the market, product and project and need appropriate current advice.
Do not treat market documentation or a marking as a universal statement that the substitute fits the intended application. Review the scope and conditions of evidence with competent specialists. Where the supplier’s information is ambiguous, obtain clarification and retain it with the comparison. An unresolved gap should not be converted into a green status simply to finish the register.
Include operation and maintenance
Ask the receiving organisation what consequences matter to its use of the asset. A different consumable, servicing arrangement or replacement route may be important even where the construction team sees little difference. Obtain the relevant technical and operational review rather than assume the operator will accept a changed support requirement.
Where a supplier claims lower ongoing cost, ask for the basis and assumptions. Appropriate advisers should assess the comparison. Avoid reporting a future saving without a supported calculation and clear scope. If the evidence is insufficient, record the uncertainty and consider whether it affects the decision or requires further investigation.
Review time and commercial consequences
Identify design work, procurement changes and delivery effects associated with the proposal. The alternative’s purchase price may be only one part of the project consequence. Ask the relevant planner and commercial reviewers to assess the actual arrangements and distinguish internal estimates from agreed adjustments.
Record commitments already made. A late substitute may require changes to orders or completed work. The project should understand those consequences before authorising the proposal. Programme urgency should lead to a focused, timely assessment rather than an unsupported assumption that every outstanding review can follow after installation.
Use the correct decision process
The APM change control overview provides general context for evaluating changes to an approved baseline. The project’s actual appointments, procurement and contractual procedures determine the formal steps. Record who approves the requirement change, who instructs work and who agrees the commercial position.
Make conditions explicit. Approval to investigate or develop a proposal should not be communicated as unrestricted approval to procure or install. Identify the evidence and decisions still required, with owners and dates. This gives the supplier and site team a clear account of what they may rely on.
Implement the accepted selection
Update the relevant controlled information and communicate the decision to affected parties. The order, drawings and schedules should describe the same accepted arrangement. A substitution register is not a replacement for those updates. Assign the actions and verify completion through the project’s established process.
Keep the original comparison and supporting evidence traceable. If the proposal changes again during detailed development, assess whether the decision still applies. Do not let a broad early acceptance become authority for later variations that the reviewers have not considered.
Reconcile the delivered position
Agree the records needed to connect the accepted substitute to the material or equipment actually supplied and installed. Relevant technical and quality teams should define the evidence. The handover information should reflect the delivered arrangement, including any changed operating or maintenance requirements.
Review the outcome after the package. Identify whether the anticipated benefit occurred and which parts of the assessment needed improvement. A credible equivalence process produces a traceable, qualified decision about a specific application. It allows useful alternatives while preserving the requirements the client and design team intended the project to meet.
Prevent approval drift
An alternative can evolve as suppliers answer questions or refine their proposal. Keep a clear reference to the version assessed at each decision point. If a consequential feature changes afterwards, ask whether the approval still applies and obtain the appropriate review. A general statement that an alternative is accepted should not become a blanket authorisation for later variants that the decision maker has never seen.
At the final review, reconcile the comparison with the offer and proposed order. Check whether the stated benefits still hold and whether qualifications introduced during clarification have been addressed. This is a focused confirmation of the current position, not a repetition of every earlier discussion. Name the person responsible and retain the evidence. It helps the buyer commit to the actual reviewed proposal and gives the delivery team a coherent account of the change it is expected to implement.
