Coordinate drawings, specification notes and the material reference.
Illustrative specification workspace. Blank records and samples do not establish product approval or acceptance criteria.Ask for a structured comparison covering product, geometry, interfaces, appearance, documents and project impacts.
Define the comparison baseline
Identify the current specified product and document revision before describing an alternate. A comparison without a stable baseline can overlook a recently changed profile or finish requirement. Ask the proposer to list each difference explicitly, including items they consider minor. Keep supplier availability and price information separate from technical comparison so a schedule benefit does not conceal an unresolved interface. The submission should identify who is proposing the change and which portions of the work would use it, including any already ordered material.
Trace the consequences
Review product identity, dimensions, drying description, grade terminology, finish system and accessory compatibility against the existing package. Request updated drawings, instructions and samples where the difference affects those records. If a rating or certification is required, obtain evidence applicable to the proposed product and configuration rather than accepting a broad family claim. Ask the responsible parties to identify effects on layout, support design, installation sequence, maintenance and warranty conditions. This workflow organizes questions; it does not calculate structural equivalence or establish compliance by matching a few descriptive fields.
Record a bounded decision
The authorized reviewer should state the disposition and any conditions in the project's established process. Record which locations and product revisions the decision covers. If an alternate is accepted, update the purchase identity, register, relevant details and closeout requirements together. Keep the original comparison so a later reader understands why the selection changed. An unanswered difference remains open even when the replacement is commercially attractive. The completeness checklist can confirm that a comparison and response are recorded, while final suitability and release remain with the people assigned that authority.
Compare the proposed change against the actual requirement
A substitution request should identify the specified item, the proposed alternative and the reason for the change. Begin with the project requirements, not a general assertion that the materials are equivalent. Two products can serve a similar use while differing in profile, coverage, fastening, appearance, treatment or required documentation.
Ask the proposer to mark every changed field. Keep unchanged fields visible too, because that makes the comparison reproducible. A product sheet alone rarely explains which requirements it is intended to satisfy or which details elsewhere in the project must change.
Follow the consequences beyond the board
Scroll sideways to read all columns. Keyboard: focus the table and use the arrow keys.
| Changed field | Related items to review |
|---|---|
| Overall section | Trim, adjacent levels and dimensional coordination |
| Installed coverage | Layout, quantities, edge pieces and openings |
| Mating profile | Adjacent boards and replacement compatibility |
| Fastening system | Hardware, support, exposure and installation method |
| Finish or surface | Appearance sample, preparation and care instructions |
| Product evidence | Reports, scope, limitations and traceability |
For example, a proposed profile with different coverage can change the final edge condition even when the nominal width sounds the same. A different hidden-fastener interface may require more than swapping a clip. Record the affected drawing and schedule references so the reviewer can assess the complete change rather than only the material line.
Distinguish equivalence from an accepted difference
Sometimes an alternative satisfies the original requirements without changing the design. Sometimes the owner or design team elects to accept a different outcome. Those are different decisions. Do not label a deliberate change in appearance, maintenance or geometry as identical performance merely because it has been accepted.
Where evidence is missing, keep the review pending and identify the exact document or confirmation needed. Where a documented requirement is not met, record the conflict. A lower price or shorter proposed lead time does not resolve a technical mismatch by itself.
Update the package after the decision
An accepted substitution should appear in the product schedule, relevant details, quantity basis, sample record and closeout requirements. Attach the conditions of acceptance. Leaving the old drawing in circulation while accepting the new product by email creates two competing instructions.
Retain the original proposal and the review response with their dates. If the alternative changes again at delivery, treat that as another reviewable change rather than assuming the earlier acceptance covers the whole product family. The review record should identify the actual supplied configuration.
Keep the website's draft in its proper role
The specification workspace can organize the comparison and expose missing fields. It does not exercise the project's contractual approval authority. Assign the review to the responsible parties and carry their decision into the issued documents. Revision control and the submittal register help keep that decision attached to the work.
Evidence & scope
Original planning guidance. References support their stated technical scope; examples and workflows do not establish product approval.