A material substitution deviation register should be a numbered decision record that compares the approved requirement with a proposed alternative and tracks evidence, affected interfaces, commercial handling, approval authority and downstream document changes. Its release question is whether an alternative may proceed, must be revised, or remains rejected without silently replacing the compliant baseline. Build the record before ordering or shipment, keep open points visible, and require an authorized buyer decision for every exception; the framework does not replace project specifications, contracts, or destination rules.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: September 1, 2026
Corrections: Send documented corrections through the HOMESEE contact page.
Editorial note: The author and reviewer are the same confirmed HOMESEE representative; this is not an independent technical review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement substitution judgment this record controls
- Minimum fields and comparison proof
- A step-by-step workflow
- A alternative authorization matrix
- Category and edge-case handling
- Governance and change control
- Buyer checklist
- HOMESEE RFQ review
- Sources
What procurement substitution judgment does a material substitution deviation register control?
A proposing vendor suggestion becomes a controlled substitution only after the deviation owner can see exactly what changes and who is authorized to accept it. The register should preserve the compliant base request, isolate the alternative, and prevent an informal approval from drifting into unrelated rooms, quantities or packages.
The core deliverable is a numbered substitution judgment record that compares the approved requirement with a proposed alternative and tracks comparison proof, affected interfaces, commercial handling, approval authority and downstream document changes. It should be readable as a substitution judgment record rather than a marketing presentation. The practical test is whether an alternative may proceed, must be revised, or remains rejected without silently replacing the compliant baseline. If the team cannot answer that question from controlled files, the deviation register is not ready, even if individual participants believe they remember the answer.
This guide describes a buyer-side control method. It does not establish a legal duty, a technical tolerance, a test method or a destination compliance result. Those come from the signed contract, project specifications, qualified designers, relevant authorities and product-specific comparison proof. HOMESEE should be evaluated only against the scope and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-controlled affected material or substitution judgment ID even when proposing vendor references change. proposing vendor model names, carton numbers and report numbers remain valuable, but they should be mapped to the stable ID rather than replacing it. That approach preserves continuity between a BOQ, a finish schedule, a sample, a drawing, an order, an inspection record and a affected scope mark.
Keep status separate from comparison proof
A status such as approved is not comparison proof by itself. Store the approving role, date, applicable scope, source document and revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, quantity or authorization. A proposing vendor declaration can identify a claim, but the deviation owner must decide what independent or destination-specific comparison proof the substitution review requires.
Minimum fields for the material substitution deviation register
Use a structured register with one row per affected material, affected scope, substitution judgment or exception at the level where the outcome can change independently. The table below is a field model, not a HOMESEE project record.
| Control field | Required treatment | alternative authorization test |
|---|---|---|
| Identity | Stable ID plus native references | Can a reviewer find the same affected material across files? |
| Basis | Approved source, revision and scope | Is the current basis distinguishable from a proposal? |
| Status | Named owner, substitution judgment and date | Is every open point visible and actionable? |
| comparison proof | Linked file and limitation | Does the comparison proof support only the claim being made? |
| Downstream action | Affected order, inspection, affected scope or receiving record | Was the substitution judgment propagated? |
Deviation id
In the deviation register, deviation ID is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Affected affected material and location
In the deviation register, affected affected material and location is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Approved baseline
In the deviation register, approved baseline is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Proposed alternative
In the deviation register, proposed alternative is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Reason for proposal
In the deviation register, reason for proposal is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
comparison proof and sample references
In the deviation register, comparison proof and sample references is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Impact assessment
In the deviation register, impact assessment is written as a comparison between the active requirement and the proposed alternative. The deviation owner avoids words such as equivalent unless an authorized project role has defined and accepted the comparison basis. Each entry names affected locations, quantities and interfaces. If the proposal changes several independent characteristics, split them so one acceptable feature cannot conceal another unresolved consequence.
Step-by-step workflow for material substitution deviation register
Run the workflow as linked gates. A later gate does not repair an undocumented earlier substitution judgment; it merely makes the missing control harder and more expensive to find. The exact approval titles and contract notices belong to the substitution review, but the sequence below gives procurement teams a reproducible starting point.
Step 1: Preserve the original requirement
preserve the original requirement. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Step 2: Describe the alternative without marketing shorthand
describe the alternative without marketing shorthand. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Step 3: Collect relevant comparison proof
collect relevant comparison proof. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Step 4: Map cost schedule and interface impacts
map cost schedule and interface impacts. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Step 5: Route to authorized reviewers
route to authorized reviewers. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Step 6: Record the substitution judgment conditions
record the substitution judgment conditions. The deviation owner keeps the compliant base offer visible while the alternative is examined. comparison proof is indexed by the characteristic it supports, and effects on drawings, interfaces, quantities, samples, inspection and packing are assigned to reviewers. The proposal remains proposed until the accountable authority records a substitution judgment. Rejection, conditional acceptance and limited-location acceptance each trigger a different downstream update.
Edge cases that need an explicit rule
Case 1: A finish looks similar but uses a different construction
If a finish looks similar but uses a different construction, the deviation owner keeps the original compliant requirement and opens a separate comparison row. The row states the proposed difference, reason, comparison proof and interface consequences without assuming equivalence. Location limits and quantity limits are explicit. The accountable authority then approves, conditions or rejects that row, and only the authorized result is propagated to samples, orders, inspections and packing instructions.
Case 2: One component is unavailable
If one component is unavailable, the deviation owner keeps the original compliant requirement and opens a separate comparison row. The row states the proposed difference, reason, comparison proof and interface consequences without assuming equivalence. Location limits and quantity limits are explicit. The accountable authority then approves, conditions or rejects that row, and only the authorized result is propagated to samples, orders, inspections and packing instructions.
Case 3: A dimension changes an interface
If a dimension changes an interface, the deviation owner keeps the original compliant requirement and opens a separate comparison row. The row states the proposed difference, reason, comparison proof and interface consequences without assuming equivalence. Location limits and quantity limits are explicit. The accountable authority then approves, conditions or rejects that row, and only the authorized result is propagated to samples, orders, inspections and packing instructions.
Case 4: An approval applies to one zone only
If an approval applies to one zone only, the deviation owner keeps the original compliant requirement and opens a separate comparison row. The row states the proposed difference, reason, comparison proof and interface consequences without assuming equivalence. Location limits and quantity limits are explicit. The accountable authority then approves, conditions or rejects that row, and only the authorized result is propagated to samples, orders, inspections and packing instructions.
Case 5: The proposal arrives after packing has begun
If the proposal arrives after packing has begun, the deviation owner keeps the original compliant requirement and opens a separate comparison row. The row states the proposed difference, reason, comparison proof and interface consequences without assuming equivalence. Location limits and quantity limits are explicit. The accountable authority then approves, conditions or rejects that row, and only the authorized result is propagated to samples, orders, inspections and packing instructions.
Related files and revision governance
For material substitution deviation register, keep the operating file connected to the container-loading comparison proof plan, proposing vendor document requirements and HOMESEE sourcing services. Plan sampling in the project inquiry form, state protection in the project references, and link final placement to the BOQ normalization guide. Before an order, reconcile the material submittal register guide. Commercial context remains in cross-category finish schedule, project-specific files go through the mixed-material AQL plan, and published export packaging specification are references rather than guaranteed outcomes.
Issue the material substitution deviation register with a revision, date, preparer and accountable approver. A change notice names the affected rows and downstream files; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the active register. Standards, photographs, declarations and sampling reports retain their own scope: none becomes a universal compliance statement merely because it is linked to the procurement file.
Practical review exercise
Reviewers should read a deviation register horizontally and vertically. Horizontally, one row must show baseline, alternative, proof, impact and substitution judgment. Vertically, the team should filter by room, affected material family, proposing vendor and revision to find accumulated effects. Several individually accepted substitutions can create a cross-category finish or interface conflict; the register should expose that combined risk before separate approvals are treated as a coordinated affected scope.
Buyer checklist for material substitution deviation register
Complete the checklist against the substitution review files, not from memory:
- A stable buyer-controlled ID exists for every affected affected material or substitution judgment.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- proposing vendor references are mapped without replacing buyer identities.
- Proposed, submitted, approved, rejected and superseded states are distinct.
- Every exception has an owner, due action and authorized substitution judgment route.
- Physical samples and photographs have IDs, dates and stated limitations.
- Quantities and units reconcile at the level needed for the alternative authorization substitution judgment.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified reviewers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for current releases.
- The final record names preparer, approver, issue date and revision.
Request a substitution-control RFQ review
To evaluate this control within a real sourcing affected scope, use the mixed-material AQL plan and upload the BOQ, current drawings, schedules, sample register and any existing material substitution deviation register. Include the destination, required-on-site context and the substitution judgment dates your project has actually approved. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined scope and organize an RFQ discussion against those files. The response should be assessed against the substitution review's technical, contractual and destination requirements. Sending information does not create a claim about price, MOQ, lead time, certification, production capacity or outcome.
Sources
- Build Procurement Hub material submittal process
- Digital NSW RACI responsibility model
- RICS New Rules of Measurement
The sources support the general control concepts identified above. Standards and public guidance must be read in their own scope and current edition. A reference here is not a declaration that a particular product, shipment, proposing vendor or HOMESEE service complies with it.