Or Equal Substitution in New Construction
An or equal substitution new construction request is not a request to find a similar lock. It is a request to change a controlled part of the door set after the design team has established what that door must do. The reviewer must determine whether the proposed item is equal in fit, function, operation and evidence while preserving the decisions already made for the door leaf, frame, opening, egress route, access system and installation. This handbook turns that decision into clauses, review gates and records that a supplier, installer and specifier can use without relying on a meeting or informal email approval. It is especially useful when a new construction lock submittal is issued against a coordinated project baseline rather than a stand-alone product catalogue.
Direct answer. The short answer is that or equal substitution new construction is not one decision. It is a sequence. This article takes or equal substitution new construction from or equal substitution new construction through or-equal-substitution to the record you keep. An or equal substitution new construction is a resource for whoever writes the requirement. or equal substitution new construction turns a request for or equal substitution new construction into something a supplier can price.
The term or equal substitution new construction carries one meaning throughout this article. It is the one given in or equal substitution new construction. That is a working definition of or equal substitution new construction, and the buyer still has to check it against the dated product page.
- Put the requirement in writing — use a template that names the physical constraints in or equal substitution new construction
- Set out the documents — attach the conformity file for the SKU behind or-equal-substitution
- Send one complete request — issue one complete package per door class, not one per query
- In or equal substitution new construction, this sequence is what or equal substitution is checked against.
The controlled path from baseline to release
New construction gives the team an opportunity to reject incomplete requests before doors, frames and wiring are coordinated around the wrong information. Every substitution file should produce five controlled records: the approved baseline, the request, the completed comparison, the decision and the revised release package. The build options sit in the smart door locks.
flowchart TD
A[Baseline recorded] --> B[Request received]
B --> C{Comparison package complete}
C -->|No| D[Information required]
D --> B
C -->|Yes| E[Technical and authority review]
E --> F{Equal and approved}
F -->|No| G[Rejected or revised]
F -->|Yes| H[Decision recorded and release updated]
| Record | Owner | Minimum content |
|---|---|---|
| Baseline | Specifier | Door set, specified lock, dependencies and controlling documents |
| Request | Supplier | Proposed item, affected doors and every declared difference |
| Comparison | Review team | Fit, function, evidence, authority questions and unresolved items |
| Decision | Specifier | Status, reasons, conditions, reviewer and date |
| Release | Project team | Revised schedule, drawings, procurement and installation records |
The request does not become a baseline change merely because it has been received, and the submittal is not approved until the review is recorded and dated.
Clause A — Establish the controlled baseline
Baseline clause: “The project documents shall identify the specified door set and applicable lock as the substitution baseline. Every proposed change shall be compared against that approved baseline. An approved change shall update the baseline before affected procurement, fabrication or installation proceeds.”
The baseline is the door set, not merely the lock: door leaf, frame, hardware, locks, handing, opening dimensions, finish, locking arrangement, credential behavior, power dependencies, communications dependencies and installation requirements. A change that works with one door but not with the coordinated door set has not demonstrated equality.
Record the baseline in a schedule that identifies each door or door group and links to the applicable drawings and submittals. A site survey can help reconcile catalogue assumptions with the actual opening, but the Office Smart Lock Site Survey should inform the record rather than replace the approved project documents.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm how the project documents establish the baseline, amend it and allocate responsibility for changes.
Clause B — Define what “or equal” means
Equality clause: “A proposed substitute may be approved as or equal only where a recorded comparison demonstrates no reduction in the specified functions and no unapproved change to the door-set design. Every material difference shall be listed, including dimensional, operational, credential, finish, power, communications, installation and maintenance differences.”
The or equal substitution clause must distinguish sameness from equivalence. A different manufacturer, internal construction or supporting technology may still be acceptable, but only when the differences are visible and the resulting performance and installation remain suitable for the same door role. Appearance, catalogue similarity or procurement convenience cannot establish equality by themselves.
Require the requester to identify both differences and unchanged functions. An empty difference schedule is not proof that the products are equal; it may only reveal that the comparison was never performed.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm the contractual effect of the approved definition of equality and the treatment of unlisted differences.
Clause C — Name the decision authority before requests arrive
Decision clause: “The specifier shall issue the technical or-equal decision after consultation with the installer, supplier and other affected reviewers. Authorities with jurisdiction over a particular consequence shall decide that consequence, and the client’s contract team shall address any separate commercial effect.”
The decision belongs to the specifier, but the supporting roles must be explicit. A supplier cannot approve its own request, and an installer cannot waive a design requirement by confirming that a sample appears to fit.
| Decision | Accountable role | Required consultation | Recorded output |
|---|---|---|---|
| Technical equivalence | Specifier | Supplier and installer | Comparison decision with reasons |
| Door and frame fit | Specifier | Installer and frame supplier | Dimensioned fit finding |
| Egress, fire and access consequences | Relevant project authority or consultant | Specifier and supplier | Written confirmation within its scope |
| Contract and commercial effect | Client’s contract team | Specifier and counsel | Contractual disposition |
| Procurement and release | Project manager | Specifier and purchasing | Revised release package |
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm which authority decides any building-code consequence and what written evidence the project must retain.
Clause D — Require a complete request before review
Request clause: “No substitute shall enter technical review until the request identifies the proposed item, the affected door sets, every known difference, the supporting evidence and the project stage at which the change is requested.”
The request package should contain:
- A unique request reference and issue date.
- The affected door, door group and baseline submittal references.
- The proposed manufacturer, item and SKU.
- A dated source for every dimensional and capability statement.
- A side-by-side comparison with the baseline.
- A complete difference schedule supported by evidence.
- Installation, power, communications and commissioning impacts.
- A clear statement of the decision requested.
This prevents a product brochure from being mistaken for a complete new construction lock submittal. The Or Equal Substitution: Reviewer Checklist can support a second-pass completeness check without replacing the project-specific comparison record.
If any item is missing, return the request with the missing evidence identified. “Under review” should describe work that can proceed; it should not conceal an incomplete package.
Clause E — Compare the door geometry, not just the lock
Dimensional clause: “The proposed substitute shall be dimensionally mapped to the coordinated door and frame. Required dimensions shall be shown on dated drawings and shall distinguish the backset, bore diameter, bolt-to-bore distance, case type, faceplate and strike arrangement.”
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 dimensions, and a submittal that omits one cannot be checked. Mortise and rim cases describe different installation arrangements; multipoint equipment changes the number and location of locking points; and the faceplate and strike must be matched as two parts of the closing edge.
The dimension the installer needs is the actual backset, stated in millimetres on a dated drawing. Bore locations, fixing positions, door thickness, frame depth and strike alignment should be shown on the same coordinated set. For any proposed SKU, confirm on the dated product page for the specific SKU and request a dimensioned drawing that can be overlaid on the door schedule.
Clause F — Run a recorded functional-equivalence test
Functional clause: “Approval shall be based on a line-by-line comparison covering physical fit, locking operation, door role, credential operation, electronics, finish, installation and maintenance. An unresolved comparison row shall prevent unconditional approval.”
The resulting technical equivalence review should be a matrix rather than an opinion. A door hardware substitution is not equal merely because it offers a similar function in a sales presentation.
| Test | Equal when | Evidence required | Not-equal signal |
|---|---|---|---|
| Physical fit | Every dimension maps to the coordinated door and frame | Dated drawings and installation instructions | Missing dimension or unresolved clearance |
| Locking geometry | Case, bolt, faceplate and strike arrangement match the door’s function | Configuration drawing and fit sample | New drilling, different strike or unresolved bolt path |
| Door role | The proposed arrangement performs the approved function for that door | Approved door-set description and authority input where applicable | Changed door role or unconfirmed operating sequence |
| Credential operation | Users, overrides, schedules, event records and administrative workflows remain equivalent for the intended use | Interface and workflow evidence | Missing administrative or audit function |
| Electronics and power | Power source, battery backup, power-loss state and dependencies match the design intent | System diagram and dated product evidence | Unassessed failure behavior or new infrastructure requirement |
| Finish | The finish is specified by its colour reference and accepted against the coordinated palette | Dated finish schedule and sample record | Photograph offered without a colour reference |
| Installation and service | Fixing, wiring, configuration and replacement arrangements are workable for the project | Installer package and maintenance procedure | Unresolved installer or service constraint |
The power-loss state must follow the door’s role and approved design; it is not inherited automatically from a product description. The line supervision and egress interface also need to be mapped to the proposed system rather than assumed from the baseline.
Clause G — Require evidence with a named scope
Evidence clause: “A capability claim shall be supported by a document that identifies the item, the tested or stated scope, the issuer or holder, the issue date and any limitations. Unsourced statements shall not be used to establish equality.”
Acceptable evidence may include a dated product-page extract, dimensioned drawing, installation instruction, test or evaluation report, interface document, configuration record and signed sample report. Each document must answer a specific comparison question rather than merely describe the manufacturer.
CONFIRM-PER-SUPPLIER: Confirm every capability, holding and limitation claimed for the proposed item on evidence issued for the specific SKU.
The Or Equal Substitution: Documents a Specifier Should Demand provides a useful document-by-document checklist. Keep each source in the request register so a reviewer can see whether the evidence applies to the proposed SKU, the actual door and the intended operating arrangement.
Clause H — Route project-specific consequences to the deciding
Authority clause: “Technical equality shall not waive any project requirement concerning egress, fire-door treatment, accessibility or building control. Where a proposed change affects such a requirement, the question and the deciding authority shall be recorded before approval.”
Ask what the proposed change affects and which authority decides that effect. The technical comparison may identify the question, but it cannot create the authority’s answer.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the project location, applicable approval route and any building-code consequence with the authority that decides it.
CONFIRM-WITH-FIRE-AUTHORITY: Confirm the treatment of any door assembly that includes fire-rated elements with the authority that decides it.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the operable-part, force, motion and approach requirements for the installed door with the consultant who decides them for this project.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm whether the project documents require separate client, designer or authority acceptance for an approved technical substitution.
Record the authority’s response in its applicable scope. Do not convert a project-specific confirmation into a blanket claim about the product.
Clause I — Use samples to verify fit, not to imply performance
Sample clause: “A mock-up or sample may support dimensional, operational and finish review. The sample record shall state what was inspected and shall not be used as evidence of untested installation, system or project performance.”
| Sample evidence | What it can verify | What remains unverified |
|---|---|---|
| Installed dimensional check | Case, bolt, faceplate and strike relationship on the sample door | Conditions not represented by that sample |
| Operational demonstration | Handing, movement and visible interface arrangement | Long-term operation and system-wide behavior |
| Finish comparison | Visual match against an approved physical reference | The complete specification of the delivered finish |
| Interface review | Visible controller, reader and exit-device arrangement | Coverage, power behavior and downstream integration |
A photograph shows the finish; it does not specify it. Record the applicable RAL or colour reference, finish designation and approved sample. A physical example evidences fit, not performance, and cannot replace the remaining document review.
Clause J — Preserve the substitution decision record
Record clause: “Each request shall receive one recorded status, the reviewer’s findings, the reasons for the status, any conditions and the date of issue. The decision record shall become part of the project submittal register.”
Use a controlled status set:
- Request received.
- Information required.
- Under technical review.
- Approved as equal.
- Approved with conditions.
- Rejected.
- Withdrawn.
The substitution decision record should identify the request, baseline, proposed item, reviewer, comparison package, authority correspondence, outcome and required follow-up. Keep rejected requests in the register because they explain why the baseline remained in force or why the request was returned for revision.
Use a central or-equal-substitution request register so superseded drawings, emails and conditional notes cannot compete with the formal decision. The submittal is not approved until the review is recorded and dated.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm whether silence, correspondence or a purchase order can alter the formal approval status under the project documents.
Clause K — State the effect of rejection and conditional approval
Consequences clause: “An unapproved or conditionally approved substitute shall not proceed as an unconditional baseline. The project team shall identify any affected design, procurement, installation, commissioning or operational activity before work continues.”
A rejection closes the request as submitted; it does not prevent a revised request. A conditional approval identifies what must happen before the condition is discharged. For example, an approval may require corrected dimensional drawings, a revised wiring diagram, an accepted sample or a written authority response.
Record the effect of the request on each affected workstream without assigning an unverified commercial consequence. The Or Equal Substitution: Cost and Risk Consequences covers that evaluation separately; the clause handbook should ensure that the decision and its consequences remain linked.
CONFIRM-WITH-CLIENT-COUNSEL: Confirm which party bears the contract and cost effect of a rejected, revised or conditional request.
Clause L — Or equal substitution new construction
Change-stage clause: “A substitution request shall identify the project stage, the work affected and the interfaces already coordinated. Information required by an earlier stage shall not be deferred to a later stage without written acceptance of the resulting change.”
A request raised before frame closure can affect opening coordination, concealed fixing and service routes. A request raised after lock ordering can affect procurement and installation documents. A request raised after installation belongs within the project’s construction-change process rather than an informal equality decision.
The requester should identify whether the change affects the frame, door leaf, handing, finish, reader position, wiring route, network design, controller schedule or installation sequence. The Smart Lock Retrofit Site Survey offers useful site-record disciplines, while Or Equal Substitution in Retrofit Projects addresses the distinct decision path for completed installations.
Clause M — Release the approved change as a new baseline
Release clause: “An approved substitution shall replace the affected baseline information throughout the schedule, procurement documents, shop drawings, installation instructions, system records and handover package before the affected work proceeds.”
The release update should identify:
- The revised door and lock schedule entries.
- The baseline product record for every affected door.
- The accepted comparison and decision record.
- Procurement references and approved ordering information.
- Dimensioned installation drawings.
- Power, communications and interface documents.
- Credential and access-control configuration records.
- Installer and commissioning instructions.
- The as-built record to be completed at handover.
At handover, name the person or party receiving the records and the format in which they will be held. The project file should show what was installed, which documents govern it and where unresolved conditions were transferred. An approval that remains only in a supplier email is not a complete release.
Illustrative review of a coordinated new-build door
Consider an illustrative new construction door set coordinated around a mortise lock. A supplier requests a surface-mounted multipoint alternative and states that it can retain the intended credential role and system connection. The request includes a sample, a configuration diagram and a general product drawing.
The sample confirms that the faceplate and strike can be arranged on that sample door. It does not establish performance on the project door, and it cannot resolve the power-loss arrangement. The dimensional package also leaves the bolt-to-bore relationship and some fixing locations unstated. The credential comparison lists the user and override functions but does not show how administrative changes and event records will be handled.
The specifier returns the request as information required. The reasons are specific: missing dimensional mapping, incomplete functional comparison and unresolved project-specific operating questions. No procurement release follows that status. The supplier later supplies coordinated drawings, revised system information and the required project reviews. Only then does the specifier record approval, with reasons, and release the change for schedule and document updates.
Readers comparing approaches usually start with smart lock mass production after sample approval. That is the same question or equal substitution new construction has to answer here.This example shows why an apparently equal product description is insufficient. The decision depends on evidence matched to the actual door, the intended use and the point in the construction programme.
Pre-release substitution approval matrix
Before releasing a request, the substitution approval matrix should answer each question with evidence and an identifiable owner.
| Gate | Pass condition | Hold if unresolved |
|---|---|---|
| Baseline | Affected door set and governing documents are identified | Comparison target is ambiguous |
| Request | Proposed item, differences and requested decision are stated | Package is promotional or incomplete |
| Fit | Required dimensions map to the door and frame | Any required dimension is absent |
| Function | Comparison covers every operational test | A test has no evidence |
| Authority | Relevant project questions have written responses | Required review remains open |
| Decision | Status, reasons, conditions and date are recorded | Approval exists only in correspondence |
| Release | Schedules, drawings and instructions use the approved item | Released documents still show the old baseline |
A disciplined or equal substitution new construction process gives the client, installer and supplier a common record. Ask a prospective supplier for a dated product-page extract, dimensioned drawings, a completed comparison matrix, an evidence index and a sample protocol before the review starts. That preparation makes the technical decision faster while leaving the installer, specifier and downstream handover teams with a package they can actually use.
Put the answer on paper and request a quote against that document.

