Keep a Proposed Concrete Product Substitution Separate From Approval
Availability can prompt a contractor to discuss a different product before a project starts. The fact that an alternative can be purchased does not establish that it is suitable or approved for the accepted scope. Record the proposed change, the relevant review and the final instruction without turning an availability discussion into an implied technical endorsement.
Identify the baseline and the alternative
Use the exact product references from the accepted scope and the proposed substitute. If the baseline was not finalized, make that status explicit. Explain what prompted the discussion without disclosing internal supplier costs. A similar name, package color or marketing description does not establish equivalent performance or compatibility for the actual substrate and project conditions.
Send the right questions for review
Ask the responsible provider which project requirements and manufacturer instructions must be considered. Include any relevant finish, use or adjacent-work expectation from the accepted scope. Do not invent a universal compatibility rule or direct an unqualified person to choose based on a broad online claim. The review should produce a project-specific response from the responsible party rather than a spreadsheet assumption.
Confirm the current written selection
Retain the decision, its source and any resulting scope, price or scheduling change through the existing agreement process. Label a rejected or still-pending alternative accordingly. Keep the final product and applicable care information with the project record. This preserves a clear instruction for the project without adding a new warranty, changing agreed remedies or implying that every available substitute is acceptable.
Copyable worksheet
Use one row for each field. Mark unknown information clearly and retain the original records.
| Field | Your note |
|---|---|
| Baseline selection and status | ____________________ |
| Exact proposed alternative | ____________________ |
| Reason for the proposed change | ____________________ |
| Responsible review and written response | ____________________ |
| Final approved selection and scope effect | ____________________ |
Worked example
Illustrative example: a supplier reports that an anticipated product is unavailable. The partner records an alternative as proposed, obtains the appropriate project review and communicates the resulting scope response. The owner’s current written selection is then updated through the established process. The availability notice itself is not treated as approval or proof of equivalent performance.