Or Equal Substitution: How Suppliers Respond
The response begins with a fixed baseline
The or equal substitution supplier response should be a structured comparison against the approved door-set requirement, not a collection of general product claims. The supplier identifies what changes, supplies evidence for each comparison, and states the residual questions that remain. The specifier then decides whether the proposal is equal, requests a revision, or records why it is not acceptable. What can be supplied is listed in the smart door locks.
Direct answer. This distinction protects the project from a circular review. A request does not approve a substitute; a brochure does not establish equivalence; and silence does not create approval. The original requirement remains the reference point until a dated decision says otherwise. For broader guidance on the governing question
The controlled sequence for an or-equal request
The or-equal substitution process follows a dependency sequence because each stage protects the next from an incomplete answer. The supplier can begin with product evidence, but the comparison cannot be evaluated until the baseline, deviations, interface requirements, and authority-dependent questions are visible.
flowchart TD
A["Receive and log the request"] --> B["Fix the approved baseline"]
B --> C["Screen the response for completeness"]
C --> D["Map functions and interfaces"]
D --> E["Assemble named evidence"]
E --> F["Verify physical fit where needed"]
F --> G["Resolve authority dependent questions"]
G --> H["Record the comparison and decision"]
H --> I["Issue the result and update the record"]
The sequence is not a promise about timing. It states what must be established before a reliable decision can be made. A supplier that cannot answer one stage should identify the missing evidence rather than letting the answer move forward by implication.
Stage one: receive the request and identify its exact scope
The first supplier response should identify the schedule item, door number, door-set description, and the baseline product or requirement from which the request departs. It should also identify who submitted the request and the revision or issue date of the baseline being compared. Without that information, two otherwise competent reviewers can compare different products against different assumptions.
A broad request such as propose an equal product is not yet an evaluable instruction. The supplier should ask for the relevant schedule line, approved documents, door type, frame details, locking arrangement, and the specific constraint that prompted the request. Questions are appropriate here; assumptions are not. They turn an unknown into an assigned evidence request while keeping the responsibility with the party holding the missing information.
| Entry in the request log | Required content | Why it matters |
|---|---|---|
| Project and schedule reference | Project identifier, door number, schedule line | Keeps the response tied to one installed condition |
| Baseline | Approved product, drawing, schedule revision, and relevant specification text | Prevents comparison against a remembered or superseded item |
| Reason for substitution | Supply, availability, design coordination, or another stated project reason | Keeps the proposed solution connected to a defined need |
| Scope of change | Hardware, interface, finish, credential, power, or door-set implications | Reveals which dimensions and authorities may be affected |
| Response contact | Name, role, organization, and contact route | Creates a route for technical clarification |
| Record status | Draft, issued for review, revised, or decision pending | Prevents a working response from being mistaken for approval |
Stage two: screen the door hardware submittal for completeness
The second stage tests whether the supplier substitution response can be compared without another meeting. A complete response maps the proposal to the baseline; a partially complete response lists what is supplied and what remains open. The distinction matters because missing information may concern a physical interface, an operating arrangement, or a decision outside the supplier’s authority.
A product brochure can introduce the proposed item, but it cannot replace the comparison record. The door hardware submittal should identify document titles and revisions, state the scope each document addresses, and show where the evidence can be held. When the same document supports several parts of the comparison, the matrix can cross-reference it rather than repeat it.
| Completeness test | Acceptable evidence in the response | Result when absent |
|---|---|---|
| Product identity | Proposed manufacturer, model, finish, and document revision | Request a clearly identified proposal |
| Baseline identity | Approved item and comparison reference | Return for a baseline rather than judge an unknown product |
| Functional mapping | Proposed function aligned to the specified function | Do not infer equivalence from general descriptions |
| Interface mapping | Door, frame, power, control, and egress interfaces identified | Mark the interface as unverified |
| Deviations | Each departure stated explicitly | Do not treat silence as sameness |
| Evidence ownership | Named document, scope, holder, and revision | Return for traceability |
| Decision status | Supplier recommendation separated from specifier decision | Prevent an implied approval |
The Or Equal Substitution: Documents a Specifier Should Demand guide provides a useful cross-check for this screening stage. It is more efficient to identify the missing evidence when the response is received than to reconstruct the request after the proposed item is already installed.
Stage three: build a like-for-like equal-product evaluation
The core comparison is a row-by-row equal-product evaluation. The supplier does not need to prove that the proposed product is better; the response needs to show whether it satisfies the same defined requirement or identify the departures that require a decision. This avoids a common mismatch in which attractive features obscure an unresolved interface or authority question.
Each comparison row should contain the baseline requirement, the proposed response, the evidence reference, and any difference. A short narrative may accompany the matrix, but the matrix should remain the controlling part of the door hardware submittal. Where a statement depends on a document, the document title and revision belong in the same row rather than in a remote appendix.
| Comparison dimension | Baseline question | Supplier response expected |
|---|---|---|
| Intended function | What must the lock do within this door set? | Map the proposed operating function to that requirement |
| Locking arrangement | What locking points and release behavior are required? | Identify every point and relevant difference |
| Door and frame interface | What physical features are controlled by the schedule? | Provide the dimensional and configuration evidence |
| Egress role | How does the door participate in the escape route? | State the proposed arrangement for authority review |
| Credential and control interface | How is user access intended to be administered? | Describe the interface and the evidence available |
| Power and operating state | What happens under normal and interrupted supply? | State the arrangement for review against the door role |
| Signal or reporting need | Does the system need to know door or exit events? | Map line supervision or egress interface requirements |
| Finish and visual coordination | Which finish reference governs the door set? | State the finish identifier and any visible interface changes |
| Maintenance access | Can the installed item be serviced without damaging the set? | Identify access and replacement requirements |
| Documentation | Which documents establish each claim? | Provide a traceable evidence index |
A dimension that does not affect the proposed item should be marked not applicable with a short reason. A dimension that affects it but remains open should be marked pending and assigned to a party. Leaving both conditions as blank creates a false appearance that the comparison is complete.
Stage four: assemble a substitution evidence package
The substitution evidence package should make each important proposition inspectable. The supplier should name the document, state the scope it addresses, identify its revision, and say who holds the original or controlled copy. A statement such as the product complies with the requirement is not a substitute for that evidence.
The package can include a dated product page, an installation instruction, a dimensional drawing, a configuration record, an interface description, a test report, a sample record, or a project-specific letter, depending on the proposition. The document type is not prescribed by the comparison; the question is whether it actually evidences the point being claimed. If a document has a broad scope, the response should explain the portion that applies rather than presenting the whole document as if every statement were relevant.
| Evidence proposition | Question the supplier should answer | Traceability expected in the response |
|---|---|---|
| The proposed item is the one evaluated | Which model and revision does the response cover? | Product identity tied to every supporting document |
| The item fits the scheduled door set | Which dimensions and configurations are shown? | Drawing or installation instruction with scope stated |
| The operating method meets the requirement | What functional sequence is documented? | Configuration, test, or technical description identified |
| The interface works with the surrounding system | Which boundary and signals are addressed? | Interface document and project-specific assumptions listed |
| The finish matches the approved reference | Which colour reference applies? | RAL or other accepted identifier, not only a photograph |
| An authority has accepted the arrangement | Which authority made which determination? | Dated written approval or a clearly pending question |
The supplier should also identify evidence that conflicts with the proposal rather than silently omitting it. A conflict is not a failure of the process; an undisclosed conflict is. A traceable disagreement gives the specifier something to decide.
Stage five: verify the physical interface instead of relying
Physical fit is checked against the door that is on site, not against an ideal product image. The installer needs the backset, bore diameter, bolt-to-bore distance, lock case type, faceplate or strike arrangement, and any other dimensions that control the installation. These are separate facts. A response that supplies only one dimension has not completed the dimensional check.
The dimension the installer needs is the backset, stated in millimetres, while bore diameter and bolt-to-bore distance must also be stated independently in the same unit convention. The supplier should identify whether the proposed lock is mortise or rim mounted, whether multipoint operation is involved, and how the faceplate and strike match the closing edge. The comparison should follow the actual door leaf, frame, handing, swing, and door-set arrangement rather than a representative configuration.
| Physical item to verify | Information requested | Reason for the check |
|---|---|---|
| Backset | Dimension stated in millimetres | Establishes the lock body’s relationship to the door edge |
| Bore diameter | Separate dimension stated in millimetres | Establishes whether the prepared opening accepts the item |
| Bolt-to-bore distance | Separate dimension stated in millimetres | Relates the locking point to the prepared bore |
| Lock case | Mortise or rim configuration identified | Determines the installation method |
| Locking points | Multipoint arrangement identified where relevant | Establishes how the closing edge is secured |
| Faceplate and strike | Matching dimensions and configuration stated | Connects the lock case to the frame |
| Door and frame | On-site dimensions and relevant construction stated | Tests the proposal against the actual opening |
For a survey-led installation, the Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey can be used as inputs to this stage. They help separate observed door-set conditions from assumptions carried over from a schedule. Once the physical evidence is assembled, the supplier response should identify any field measurement still required.
Stage six: map the operational interfaces without changing
A proposed lock may meet the dimensional requirement and still alter how the door operates. The response must map credential administration, reporting, power arrangements, and any interface with access-control or egress systems. It should distinguish a proposed capability from a confirmed project configuration, because a general product description cannot prove compatibility with the surrounding system.
Battery backup, fail-safe or fail-secure behavior, line supervision, and the egress interface are door-set decisions rather than decorative product attributes. Fail-safe and fail-secure describe the lock’s state under an interrupted supply, and the appropriate state is determined by the role of the door. The supplier should therefore state the arrangement under review and provide supporting documentation, while the specifier confirms that the arrangement suits the door’s function.
| Operational subject | Supplier must state | Decision owner or evidence source |
|---|---|---|
| Credential administration | Intended authority, credential format, and administration method | Client access-control requirement and interface evidence |
| Door-state reporting | Whether and how open or closed status is reported | Client system requirement and configuration evidence |
| Exit-device interface | How an exit-device operation is communicated | Approved door arrangement and relevant authority evidence |
| Normal power | Power source and wiring interface relevant to the proposal | Project design information |
| Interrupted supply | Backup arrangement and resulting lock state | Door role and client operating requirement |
| Maintenance access | Route for battery change, service, and replacement | Maintenance requirement and physical installation evidence |
Where the proposal crosses organizational boundaries, the supplier should identify the dependency rather than assume that another consultant has accepted it. Or Equal Substitution: Coordination Between Architect and Supplier examines that hand-off from the coordination side; in this workflow, the supplier’s task is to expose the dependency clearly enough for coordination to occur.
Stage seven: isolate the questions that require an authority
Some proposed changes can be evaluated from technical evidence, while others require a decision by a public authority, the client’s access consultant, or the client’s counsel. A supplier should identify those questions and provide the evidence available for review. It should not convert an unanswered authority question into a supplier assertion.
The escape route and locking arrangement are part of the door set, not separate features that can be exchanged without consequence. Panic hardware and free egress remain part of the wider review, and any electronic component proposed on a fire door must be considered within the assembly rather than as an isolated product.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the applicable locking arrangement, power-loss state, and approval evidence for the escape route and building interfaces on this specific project.
CONFIRM-WITH-FIRE-AUTHORITY: Where a fire door assembly is involved, confirm which assembly evidence is relevant and how the proposed electronic component is assessed for that installation.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the operable-part, approach, and user requirements against the actual door, frame, and operating environment with the client’s access consultant.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm how the project contract assigns substitution approval, notice, cost responsibility, and remedy before the response is treated as contractually effective.
The supplier response should label these items as questions for the named decision-maker. The project record should then show whether the answer was accepted, remains pending, or resulted in a revised requirement. A dated decision is more useful than a general statement that the arrangement is acceptable.
Stage eight: use mock-up verification only for what a sample
Mock-up verification is appropriate when the remaining uncertainty concerns physical fit, interface appearance, finish, handling, or access to service areas. A mock-up or sample can provide direct evidence at the review point, but it evidences fit rather than the complete performance of the proposed lock. The approval record must distinguish what was observed from what remains supported only by documents.
A photograph shows the finish; it does not specify it. The approved reference should therefore remain the named finish identifier, while a sample can help reviewers understand how that finish appears under the project’s lighting and adjacent materials. Any visible difference between the sample and the scheduled door set should be recorded before the sample is accepted.
| Review evidence | What it can establish | What remains documentary |
|---|---|---|
| Physical mock-up | Fit, visible interface, proportions, and selected handling observations | Authority acceptance and complete operating performance |
| Controlled sample | Finish appearance and detail comparison | Fit in the actual opening without site verification |
| Site measurement | Actual door, frame, and preparation dimensions | Functional and authority evidence |
| Interface drawing | Intended connection and geometry | Installation condition until checked on site |
| Configuration record | Intended operating sequence | Whether the installed system follows that configuration |
The mock-up record should identify the sample revision, door and frame conditions represented, participants, observations, photographs if used, and unresolved items. It should end with a dated status. A sample left at an office without a record may create confidence without evidence.
Stage nine: form the recommendation and the specifier approval
Before the recommendation is written, the reviewer should test the response for identity, completeness, internal consistency, and alignment with the baseline. The Or Equal Substitution: Reviewer Checklist can serve as a final control against skipping one of those checks. The supplier’s recommendation should not reproduce the checklist in place of a comparison; it should state what the comparison found.
The specifier approval record has a clear chain. It identifies the proposal and its revision, the evidence considered, the unresolved questions, the decision, the reasons, the conditions attached to any revision, and the date. A useful decision is one of three states: approved as equal, revise and resubmit, or not approved as equal. A conditional approval should identify exactly what remains open and who must close it.
The submittal is not approved until the review is recorded and dated. Silence, receipt of a file, or a supplier statement that the product is equivalent cannot replace that record. If the review only confirms that the response is complete enough to assess, it should say that rather than implying that the product has been accepted.
Stage ten: issue the decision and close the response loop
The final supplier response should be issued as a controlled result rather than an informal acceptance. It should state the decision, identify the exact proposal and baseline revisions, summarize the reasons, and list any action assigned to the supplier or another party. The recipient list should include the people who need to update the schedule, procurement record, installation information, or downstream design.
After issue, the project file should preserve the request, the original response, the evidence index, every review round, the dated decision, and any resulting revision. The superseded proposal should be marked as superseded rather than deleted. This allows a later reader to see what was proposed, what evidence was considered, and which version moved forward.
The decision can then become the new baseline for procurement or installation only after the appropriate project process accepts it. Until that happens, the original requirement remains the reference point. Keeping both versions visible avoids a situation in which an installer receives a substituted item while the schedule still describes the approved one, or a future reviewer mistakes an unapproved draft for the decided requirement.
How to read common supplier response patterns
Even when the response is sincere, its presentation can hide unanswered questions. The reviewer should interpret the form of the answer, then decide whether it is ready for comparison. This reading does not replace the equal-product evaluation; it identifies where that evaluation can begin.
| Supplier response pattern | What it actually establishes | Specifier action |
|---|---|---|
| A general statement that the item is equal | A proposed position without a visible comparison | Request a baseline-linked matrix |
| A brochure without dimensions | Product identity or general description only | Request the physical interface evidence |
| A reference to an attachment without a title or revision | An indication that evidence may exist | Request a traceable evidence index |
| A proposed alternative with changed geometry | A real change that may affect installation | List the deviation and test it against the door set |
| A request to discuss the item in a meeting | An unresolved communication need | Send structured questions before the meeting |
| A performance description without interface evidence | A functional claim in general terms | Identify the relevant boundary and document |
| Silence on an authority question | No decision on that question | Route the question to the named authority |
| A request to proceed before review is complete | Commercial urgency, not technical acceptance | Keep the baseline active until the review is recorded |
This approach avoids the adversarial reading of a supplier’s wording. It treats each response as a data structure: some entries are complete, some are pending, and some are missing. The review can then focus on the actual gaps rather than on whether the tone sounded confident.
Decision-comparison table for common proposal scenarios
The following comparison table shows how the same supplier response may lead to different outcomes. It is a decision aid, not a default answer. The project evidence and the named authority remain controlling.
| Scenario | Evidence to weigh | Likely route | Required record |
|---|---|---|---|
| Proposed item preserves the scheduled function and physical interface | Baseline mapping, dimensional evidence, configuration record | Proceed to comparison and recommendation | Dated decision identifying both revisions |
| Proposed item changes the interface but may suit the actual door better | Site dimensions, revised schedule requirement, installer confirmation | Return the change to the project requirement before deciding | Deviation list and authorized requirement change |
| Proposed item meets the fit but changes the power-loss arrangement | Door-role evidence, operating requirement, authority input where applicable | Hold decision until the operating arrangement is accepted | Authority or client determination tied to the door |
| Proposed item offers a different credential or control method | Client access requirement, interface evidence, access-consultant review | Compare by function and control boundary | Revised mapping and dated acceptance |
| Evidence is complete for fit but incomplete for an escape route | Door-set record and authority decision | Do not approve the unresolved arrangement | Authority query, answer, and decision status |
| Supplier recommends an alternative but provides no baseline mapping | Identity of both items and revised response | Return for a structured comparison | One response revision linked to the original request |
The table keeps the decision tied to evidence. It also allows a rejected proposal to remain useful: the reasons and unresolved points can guide a revised response without restarting the whole review from an unstructured request.
Dependencies that should shape the sequence
The order of work is driven by evidence dependencies rather than by a universal calendar. A supplier may assemble documents while a door is being surveyed, but a recommendation based on assumed dimensions cannot be final until the measurements are reconciled. Likewise, a technical comparison may proceed while an authority question remains open, but the approval record must preserve that open status.
The sequence also distinguishes responsibility. The supplier supplies evidence for what it proposes. The specifier compares that evidence with the approved requirement and records the recommendation. The installer confirms field conditions that affect installation. The authority or client specialist decides questions within their remit. The client’s commercial process administers any resulting change.
This separation prevents a supplier response from carrying too much authority or a specifier from being asked to fill a supplier’s missing evidence. It also creates a practical escalation path. When a dependency is blocked, the record identifies the blocked item, the party who holds it, and the decision that cannot proceed. No numerical timing promise is necessary for that control to work.
A structured template for the supplier’s response
A supplier can use the following field order to make the answer reviewable. The Or Equal Substitution: Template Language for a Specification provides related clause language, while this sequence is intended for the response package.
- Reference: Project, door number, schedule line, request date, and response revision.
- Baseline: Approved item, drawing, specification, and schedule revisions used for comparison.
- Proposed item: Manufacturer, model, finish, configuration, and document revision.
- Statement of intent: Clarify that the proposal is offered for an equal-product evaluation.
- Comparison matrix: Baseline, proposal, evidence, and difference for each applicable dimension.
- Deviation schedule: List every physical, functional, operational, visual, or authority-related departure.
- Evidence index: Document title, revision, scope, holder, and proposition supported.
- Dimensional evidence: Backset, bore diameter, bolt-to-bore distance, case type, and faceplate or strike data.
- Interface evidence: Credential, control, power, reporting, and maintenance arrangements relevant to the door.
- Open questions: Authority-dependent items, missing evidence, and the party responsible for each response.
- Verification plan: Site check, mock-up, sample, or other proposed evidence method, with the question each method will answer.
- Supplier recommendation: State the supplier’s view while reserving the decision for the designated project reviewer.
- Response status: Submitted, revised, awaiting information, or complete for review.
The template prevents the comparison from being lost inside a product narrative. More importantly, it makes a revision traceable. Each returned package can be compared with the previous issue, allowing the reviewer to focus on what changed.
What the project file must retain
The response has lasting value only if the project can reconstruct the decision later. The retained record should include the request, baseline, evidence index, supplier response, review notes, decision, and any approved revision. It should also identify who owns the record after handover and in what form the handover occurs.
| Record component | Minimum content | Long-term purpose |
|---|---|---|
| Original request | Reason, scope, requester, and date | Shows why the substitution was considered |
| Baseline set | Approved schedule, drawings, and specification revisions | Provides the comparison reference |
| Supplier response | Product identity, matrix, deviations, and evidence index | Shows what was proposed and supported |
| Review record | Questions, comments, and response disposition | Preserves the reasoning trail |
| Decision | State, reasons, conditions, authority, and date | Establishes whether and how the proposal moved forward |
| Approved revision | Updated product, drawing, schedule, and configuration references | Connects the decision to downstream work |
| Handover record | Final documents, responsible owner, and storage location | Supports future operation, repair, and audit |
The handover should not reduce the record to a single accepted email. The owner should receive the controlled baseline, the decision, the supporting evidence, and an index showing where each file is stored. This is especially important when the client, installer, and consultant retain different parts of the project record.
The response closes when the record is usable
An effective or equal substitution supplier response gives the specifier enough evidence to make a defensible decision and gives the installer enough information to understand what changed. The supplier’s role is to expose differences, attach evidence, and identify unresolved questions. The specifier’s role is to compare, decide, and record the reasons.
For a supplier preparing an alternative smart-lock response, begin with the baseline rather than the product narrative. For a specifier sending the request, provide one controlled set of door-set requirements and state what evidence will be accepted. For either side, treat a partial response as a partial response. It is better to show an open item with an owner than to imply closure through silence.
That discipline keeps the or-equal request from becoming a catalogue substitution. It also gives the client, installer, supplier, and future project reader one common record of what was proposed, what was verified, what remained open, and which version was approved.
When the file is ready, request a quote against the written requirement.

