Or Equal Substitution Versus Procurement Priorities
This bid and specification sheet defines how an or-equal request is screened when commercial urgency is present. It separates technical equality from procurement preference so the or equal substitution versus procurement question is answered in writing, by named roles, with evidence tied to the actual door set. Use it as a bid appendix, substitution request form, and decision record rather than as a general invitation to replace a specified product.
Direct answer. The one-line answer — or equal substitution versus procurement is the working record for or equal substitution versus procurement. or equal substitution versus procurement is worthless until or-equal-substitution is attached to it as evidence. An or equal substitution versus procurement is a tool pack for the specifying side. or equal substitution versus procurement names the artefact the RFQ must produce for or equal substitution versus procurement.
1. Document Control and Scope
Complete this sheet for each proposed substitute. It covers the specified product, the proposed replacement, and the door set affected by the request. It does not authorize changes to unrelated doors or establish approval for work not yet reviewed. The commercial end of this decision is the smart door locks.
| Document field | Entry |
|---|---|
| Project | [Project name and location] |
| Door hardware schedule | [Schedule, sheet, and revision] |
| Door set reference | [Door number and opening description] |
| Specified baseline | [Manufacturer, product, and revision] |
| Proposed substitute | [Manufacturer, exact SKU, and revision] |
| Requestor | [Name, organization, and contact] |
| Procurement priority | [Operational or commercial reason for the request] |
| Review authority | [Named specifier and required approvers] |
| Submission status | [Draft, under review, returned, or recorded] |
| Review date | [Date of recorded determination] |
Attach this sheet to the product submittal rather than keeping it in a separate email thread. The request is not approved until the review and its reasons are recorded and dated.
2. Instructions Embedded in the Bid
Issue the following instructions to every bidder permitted to propose a substitute:
- Identify the proposal. Name the manufacturer, exact product, SKU or model revision, finish, and supplied components. A family name or catalogue image does not identify the item offered.
- Identify the baseline. Cite the specified product and schedule revision. Mark every dimensional, functional, interface, and documentation difference from that baseline.
- Submit the comparison. Complete the technical criteria and the substitution approval matrix rather than attaching a general brochure.
- Attach dated evidence. Provide the document, scope, issuer, revision, and result needed to check each material claim.
- Separate the procurement priority. State whether availability, standardization, commercial fit, documentation burden, or another reason is driving the request. Do not present that reason as proof of technical equality.
- Accept the review sequence. A request does not alter the approved door hardware schedule or release an order until the authorized determination is recorded.
This separation gives procurement a usable comparison while preserving the specifier's responsibility for the technical finding.
3. Decision Route from Request to Recorded Outcome
flowchart TD
A[Request logged] --> B[Baseline and door set identified]
B --> C[Technical equality review]
C --> D{Required gates passed}
D -->|Yes| E[Procurement priority review]
D -->|No| F[Revision or decline]
E --> G[Authorized decision recorded]
F --> H[Resubmittal or closure]
The route begins by fixing the baseline. Without the approved product, schedule revision, and affected opening, reviewers can compare different scopes and still reach different conclusions.
The specifier owns the technical equality determination within the assigned project scope. Procurement then checks whether the reason for pursuing the substitute creates a commercial or operational advantage among technically equal options. A failed mandatory gate returns the request for correction or a formal deviation decision; it does not move forward merely because procurement considers the substitute preferable.
4. Minimum Substitution Bid Package
Require the package below with every request. The bidder should mark an item as unavailable only when its proposed design genuinely does not provide the requested function, and should attach the supporting evidence in the same place.
| Package item | Required response |
|---|---|
| Product identification | Exact maker, SKU, revision, finish, and supplied components |
| Baseline identification | Approved product, schedule entry, and drawing reference |
| Difference statement | Every material change from the baseline |
| Technical data | Dated product information for the proposed SKU |
| Door-fit information | Dimensions and installation requirements for the actual door set |
| Access and egress interface | Proposed arrangement and supporting evidence |
| Systems interface | Power, network, credential, monitoring, and controller interfaces relevant to the project |
| Operations information | Service access, maintenance, configuration, and handover requirements |
| Evidence index | Document name, issuer, scope, revision, and attachment reference |
| Procurement statement | Reason for preference and the commercial effect of the change |
| Declaration | Confirmation that the response identifies all known deviations |
A product brochure can introduce the proposed item, but it cannot complete this package. The reviewer must be able to trace each important comparison from the request to dated evidence.
5. Technical Equality Criteria
The or equal substitution criteria assess whether the proposed product can perform the same project role as the baseline. Equality does not mean identical appearance or internal construction. It means that the proposed item meets the functional, dimensional, safety, interface, operational, and documentation requirements applicable to that door set.
| Comparison dimension | Pass question | Evidence expected | Failure signal |
|---|---|---|---|
| Intended function | Does the proposal perform the function assigned to this opening? | Project-specific comparison and dated product data | Purpose or operating arrangement is changed |
| Door-set fit | Can the item be coordinated with the actual leaf, frame, and hardware? | Dimensioned drawing and installation instructions | Key dimensions are omitted or conflict |
| Egress and access | Is the locking arrangement compatible with the approved access and exit strategy? | Authority determination or relevant project evidence | Review depends on an assumption |
| System interfaces | Can required power, network, credential, and monitoring connections operate as intended? | Interface definition and test or commissioning evidence | Compatibility is inferred from a brand or family |
| Operations and service | Can maintenance, configuration, and handover be performed on this installation? | Operations and service information | Required access is obstructed or unsupported |
| Finish and appearance | Does the proposed finish have an identified reference and an agreed sample? | Colour reference and recorded sample review | A photograph is used as the finish specification |
| Documentation | Can the installation, testing, and handover be completed from supplied records? | Defined document package | Critical record depends on a phone call |
| Approved baseline alignment | Are all differences stated and dispositioned? | Signed difference schedule | A material difference is omitted |
Procurement preference is not another technical criterion. If a preferred item fails one of these dimensions, the appropriate result is revision, escalation, or a properly authorized deviation—not a finding that the items are equal.
6. Door-Set Fit and Dimensional Gate
The comparison must use the door on site, not a generic catalogue door. Backset is the distance from the door edge to the centre of the spindle or cylinder. Bore diameter and bolt-to-bore distance are separate measurements, and a submittal that omits either cannot be checked against the opening.
The door set includes the door leaf, frame, hardware, and locks as one assembly. Record whether the proposed lock is intended for a mortise, rim, or multipoint arrangement and compare the faceplate and strike as a matched pair. A change in the lock case, the closing edge, the frame, or an adjacent pull or exit device may alter the installation even when the product family appears familiar.
A photograph shows the finish; it does not specify it. Likewise, a catalogue drawing may establish a general arrangement, but it does not establish fit at the project opening. Obtain the dimensioned information for the proposed SKU and reconcile it against the survey, shop drawing, and approved door hardware schedule.
For field coordination, use Office Smart Lock Site Survey for office openings and Smart Lock Retrofit Site Survey where existing conditions control the work. Each survey identifies information to collect; neither approves a substitute.
CONFIRM-PER-SUPPLIER — Obtain and retain the dated dimensional package for the exact proposed SKU and reconcile it with the door set identified on site.
7. Egress, Fire and Access-Control Gate
Ask whether the proposed change affects the egress route, panic hardware, free egress, locking arrangement, or the relationship between an access-control device and an exit device. The relevant question is not whether the product can be installed, but whether the complete opening retains the arrangement reviewed for that door.
For an opening in a fire-rated assembly, request evidence that addresses the assembly and any electronic component as an installed combination. Do not infer assembly performance from the lock's individual information sheet.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL — Confirm which local building-control authority decides the applicable requirement for this project and obtain the written decision needed for the affected opening.
CONFIRM-WITH-FIRE-AUTHORITY — Confirm with the fire authority having jurisdiction which assembly evidence it requires and which part of the door set it will review.
CONFIRM-WITH-ACCESS-CONSULTANT — Confirm the required exit arrangement and the interface between locking, access control, panic hardware, and the approved egress route.
Record each response as the authority's name, scope, document reference, and date. Keep the determination with the submittal so the approval record can be reconstructed later.
8. Evidence Standard for a Smart Lock Submittal
A smart lock submittal is complete only when another reviewer can test its conclusions without contacting the supplier. Each material statement should point to a named document with a defined scope. For SKU-specific capabilities, obtain the dated product page for the exact item and retain the revision or retrieval record used.
The minimum evidence index should contain:
- the product identification sheet for the exact SKU;
- dimensioned door and installation drawings;
- interface and configuration information;
- relevant test or inspection reports;
- authority decisions or approvals where they apply;
- operating, maintenance, and handover instructions; and
- a difference schedule identifying every departure from the baseline.
Evidence must state what it covers. A report for a different size, configuration, door type, or product revision cannot be extended by implication. Ask the supplier to identify missing evidence rather than marking it not applicable.
Use Or Equal Substitution: Documents a Specifier Should Demand to structure the document request, then apply Or Equal Substitution: Reviewer Checklist before issuing the decision.
CONFIRM-PER-SUPPLIER — Confirm every capability, holding, interface, and dimensional claim against dated evidence for the exact proposed SKU.
9. Procurement Priority Review
The phrase or equal substitution versus procurement describes a sequence: technical equality is established first, and procurement preference is then used to choose among acceptable options. The procurement priority review should state the operational or commercial reason for the request without allowing that reason to waive a mandatory technical gate.
| Procurement priority | Question for the procurement reviewer | Treatment in the substitution decision |
|---|---|---|
| Availability and continuity | What supply uncertainty is the request intended to reduce? | Considered after technical equality is established |
| Standardization | Does the proposal align with an already approved product or design? | Supports preference if the door-set effects are documented |
| Commercial effect | How does the proposal change the commercial terms under evaluation? | Recorded separately from technical compliance |
| Documentation burden | Which records can the supplier actually provide? | An evidentiary issue, not an automatic equality finding |
| Supplier responsiveness | Can the supplier resolve missing information within the project process? | Determines whether review can continue |
| Delivery and packaging | Will grouping or logistics affect other project requirements? | Routed for coordination and documented |
| Client preference | Who requested the change, and what operational need was stated? | Identifies the basis for an authorized deviation if necessary |
Procurement may rank technically equal options, recommend a preferred alternative, or identify a commercial constraint that should be visible to the client. It cannot convert a dimensional mismatch, unresolved egress question, or unsupported interface into equality.
Where the preferred proposal fails a mandatory criterion, record the mismatch and route it for revision, a different proposal, or a deviation decision by the authority empowered to accept that change. Do not describe the result as an or-equal approval.
Readers comparing approaches usually start with smart lock manufacturer china buyer. That is the same question or equal substitution versus procurement has to answer here.
10. Substitution Approval Matrix
The substitution approval matrix converts the comparison into a reviewable decision. Each gate names the evidence to inspect, the person responsible for the finding, and the action required if the gate does not pass.
| Gate | Pass condition | Reviewer | Result if not satisfied |
|---|---|---|---|
| Identity and baseline | Exact products and controlled schedule references are identified | Specifier | Return for clarification |
| Technical function | The proposed item satisfies the function assigned to the opening | Specifier | Revise or escalate |
| Door-set fit | Required dimensions and interfaces reconcile with the actual opening | Specifier with installer input | Revise or reject |
| Egress, fire and access | Applicable authority decisions and project evidence support the arrangement | Named project reviewers and relevant authorities | Hold pending evidence |
| Systems interfaces | Required power, network, credential, and monitoring interfaces are defined | Systems designer or responsible reviewer | Revise or reject |
| Operations and service | Installation, maintenance, configuration, and handover remain workable | Specifier with operations input | Add conditions or reject |
| Evidence completeness | Every material claim is traceable to a dated, scoped document | Specifier | Return as incomplete |
| Procurement priority | The reason for preference is stated and separated from equality | Procurement reviewer | Escalate to decision authority |
Enter one result for each gate: pass, revise, escalate, or decline. Attach the evidence reference, reviewer name, and date. A blank cell is not an implied pass.
11. Authority and Signature Route
Name the people and organizations that will act at each stage before the request enters review. A role title alone is insufficient if the project has not identified who holds it.
| Role | Responsibility in the decision |
|---|---|
| Specifier | Compares the proposal with the baseline and records the technical equality finding and reasons |
| Supplier | Supplies exact-SKU data, drawings, declarations of difference, and requested evidence |
| Installer or fabricator | Confirms whether the proposed arrangement can be installed on the actual door set |
| Access consultant | Reviews the access and egress interface within the assigned scope |
| Building-control or fire authority | Decides the applicable requirement within its jurisdiction |
| Procurement reviewer | Confirms commercial conditions and records the procurement priority |
| Client or design authority | Accepts or rejects a deviation when the project procedure assigns that decision to the client |
| Contract administrator | Records the final determination, conditions, and schedule action |
The technical finding and the commercial finding should remain visible as separate entries. If the two conflict, route the unresolved difference to the named authority rather than letting the commercial reviewer close the technical gate.
CONFIRM-WITH-LOCAL-CLIENT-COUNSEL — Confirm the contract-administration clause, decision authority, notice method, and effect of any deviation with the client's counsel and named contract administrator.
12. Clause Set for Issue
Use the following drafting pattern with the bid package. Review it against the contract and local project procedure before issue; the language below is a worksheet, not a substitute for project-specific terms.
- Or-equal request. A request to substitute shall identify the proposed product, the specified baseline, the affected door set, all known differences, and the person or organization making the request.
- Equality determination. The or equal substitution criteria shall include intended function, door-set fit, applicable egress and access evidence, relevant interfaces, operability, service access, finish reference, and required documentation. The technical finding shall identify the reviewer, reasons, and dated evidence.
- Separate procurement priority. A procurement priority may guide selection among technically equal proposals but shall not be used to waive a failed technical criterion. Any proposed deviation shall follow the route stated in the bid documents.
- Evidence requirement. The requester shall provide dated evidence with a defined scope for every material claim. Evidence issued for another SKU, configuration, door type, or project shall not be treated as evidence for the proposed item without written justification.
- Recorded outcome. The determination shall state pass, revise, escalate, or decline; list conditions and required evidence; identify the decision maker; and be dated. The submittal is not approved until the review is recorded.
- Schedule and handover effect. An accepted substitute shall be entered into the controlled door hardware schedule and handover record. Informal supplier correspondence alone shall not modify the approved project information.
For alternative wording, compare Or Equal Substitution: Template Language for a Specification. For the wider hand-off sequence, use Or Equal Substitution: A Smart Lock Specifier Guide.
CONFIRM-WITH-LOCAL-CLIENT-COUNSEL — Confirm the clause wording, contractual effect, approval route, and record-retention requirement with the client's counsel and contract administrator before issue.
13. Supplier Substitution Response Form
Require the requester to complete this form in addition to the technical submittal. Use one form per proposed product and door set.
| Response field | Supplier entry |
|---|---|
| Proposed manufacturer and product | [Entry] |
| Exact SKU or model revision | [Entry] |
| Baseline product and revision | [Entry] |
| Affected opening | [Door number and description] |
| Drawing or schedule reference | [Entry] |
| Principal reason for request | [Entry] |
| Procurement priority category | [Entry] |
| Material differences | [Entry or attached schedule] |
| Evidence attachments | [Document titles and references] |
| Installation or handover effect | [Entry] |
| Requested decision | [Accept, accept with conditions, revise, escalate, or decline] |
The response must then answer the following questions without relying on a conversation:
- Which specified requirements does the proposal meet without change?
- Which requirements change, and how?
- What dated evidence establishes each material claim?
- What field measurements must be confirmed before acceptance?
- Does the proposal alter the egress, fire, access, power, network, credential, monitoring, maintenance, or finish requirements?
- What condition would have to be completed before procurement treats the item as acceptable?
- Which document will carry the decision into the door hardware schedule and handover package?
End with a declaration that the response identifies the proposed item and all known differences. Require a named signatory and date, while keeping this declaration separate from the technical approval.
14. Disposition, Revision and Final Record
The outcome must describe what happens next. Use the matrix result to select the disposition, then attach the reasons and any conditions.
| Disposition | Use when | Required record |
|---|---|---|
| Accepted as equal | Every mandatory gate passes and the evidence is complete | Technical finding, procurement review, approver, and date |
| Accepted with conditions | Non-critical corrections or documents must be completed before acceptance | Each condition, owner, due point in the project process, and closure evidence |
| Returned for revision | Evidence, dimensions, interfaces, or clarifications are incomplete | Deficiency list and resubmittal reference |
| Escalated as a deviation | A required change falls outside the accepted technical finding | Decision route, authority, reasons, and resulting project action |
| Declined | The proposal cannot meet a mandatory project requirement | Failed gate, evidence, notification route, and date |
The record should include the baseline, proposed SKU, requestor, drawings, comparison matrix, evidence index, procurement priority, technical reasons, decision, conditions, approver names, and dates. Keep returned revisions with the original request so the review trail remains intact.
After acceptance, update the controlled door hardware schedule and the handover package. Do not leave the final record only in an email, a supplier proposal, or a meeting note.
15. Bid Issue Checklist and Handover
Issue the package only when these items are complete:
- The specified baseline and current door hardware schedule are identified.
- Every affected door set has a reference and field-data source.
- The technical equality criteria are included in the bidder instructions.
- The substitution approval matrix has named reviewers.
- Evidence requirements name the document, scope, SKU, and revision.
- Procurement priority is separated from the technical test.
- The path for an unresolved or material deviation is stated.
- The supplier response form is attached to the submittal template.
- The contract administrator and record holder are identified.
- The route into the schedule, installation information, and handover record is defined.
A complete bid makes the review path visible before the first request arrives. Procurement sees which priority it may pursue, the specifier sees what must be proved, suppliers see the evidence required, and the client sees exactly who may authorize a departure from the stated baseline. The result is a recorded decision that can be carried into installation without reconstructing the argument later.
Ask for the offer against the same requirement: request a quote.

