Smart Lock Glossary: Two Stage Lock Definition for B2B Buyers
This glossary entry gives B2B importers a two stage lock definition for direct use in a purchase file. It treats the term as a buyer working rule, not a universal industry standard. The clauses below settle what must be stated, what evidence must accompany it, and where the sequence is checked before handover.
Clause 01 — Put the two stage lock definition in writing
Direct answer. Clause 01. For this programme, two-stage locking means a lock that passes through at least two ordered, distinguishable locking states before reaching its specified final state. The user may perform one action or several; the definition concerns the sequence
The phrase may describe one assembly coordinating a latch, deadlatch or bolt, or several elements working as one system. It does not mean two complete locks. Clause 01A requires the supplier to identify every stage, its observable result, and the action causing the next stage.
| Element | Required wording | Commercial result |
|---|---|---|
| Scope | One assembly or coordinated elements | Fixes what is being supplied |
| Stages | Ordered states and transition action | Supports training and inspection |
| Final state | Observable condition for acceptance | Prevents subjective acceptance |
| Exceptions | Named non-normal conditions | Assigns resolution ownership |
Clause 02 — State what the sequence decides
Clause 02. A two-stage lock changes the door hardware sequence, so the definition affects preparation, access-control commissioning, operating instructions and inspection. A survey that records only the lock family and finish leaves the sequence unresolved and untested.
| Buyer decision | Working answer | Commercial consequence | Evidence required |
|---|---|---|---|
| Component scope | One assembly or coordinated elements | Sets the component schedule | Sectional drawing and hardware schedule |
| Stage transitions | Action that produces each state | Drives training and commissioning | Numbered sequence |
| Final condition | Observable result that closes the sequence | Defines acceptance | Inspection method |
| Exceptions | Defined departure from normal operation | Assigns resolution ownership | Approved exception procedure |
For access control hardware, state whether credential release operates the first stage, all stages, or a defined exception path. The supplier must confirm the interface on the dated product page for the specific SKU; a family brochure cannot settle a variant. Access rights remain an access-control design decision, not an implied property of the phrase “two-stage.”
Clause 03 — Exclude the common substitutions
Clause 03. Importers most often lose clarity by treating the phrase as a product count, security grade, or authentication rule. Add these exclusions:
- It does not mean two locks; one assembly may coordinate the ordered elements.
- It does not mean two-factor authentication; credential count is a separate access-control requirement.
- It does not prove a performance grade; specified evidence must establish any applicable grade.
- It does not describe failure behavior; release, exceptions and service override need separate clauses.
- It does not establish radio or platform compatibility; integration requirements must be stated separately.
For a smart lock, the useful distinction is simple: the sequence describes what the hardware does, while the access-control design describes who may cause each stage. Combine both in the lock specification, but do not merge their terms.
Clause 04 — Demand evidence that can settle the term
Clause 04. Require evidence at the same level as the question. A marketing sentence cannot establish the mechanics, and a drawing cannot establish the operating result. The minimum set is:
| Evidence record | Question it settles | Minimum useful content |
|---|---|---|
| Dated product-page extract | Does this SKU use the term? | Exact SKU, version and context |
| Sectional drawing | Which parts produce the stages? | Revision-controlled parts view |
| Sequence diagram | What action changes each state? | Numbered steps and observed results |
| Door preparation drawing | What site work is required? | Project-specific dimensions and interfaces |
| Inspection method | What constitutes acceptance? | Conditions, steps and pass criteria |
| Exception procedure | What happens outside the normal flow? | Trigger, authorized response and record |
The following is a record structure, not a claim about every product’s internals.
flowchart LR
A["First defined state"] --> B["Second defined state"]
B --> C["Final state"]
C --> D["Inspection record"]
Clause 05 — Put the term into RFQ and sample controls
Clause 05. In the RFQ, add a field labelled two-stage-lock. Beside it, request the working definition, stage count, user-action count, final observable state, exception behavior and inspection method. This stops a family name from leaving the importer to infer the design. The same fields belong in What an RFQ Should Contain: Plain Explanation.
At sample approval, bind the definition to the exact configuration under review. Record the drawing revision, dated product-page reference and observed sequence. How a Sample Becomes a Production Standard: Plain Explanation gives the approval context; How a Door Is Prepared for a Lock: Plain Explanation handles preparation separately. These links carry the operational depth behind this glossary clause.
Importer due diligence should establish whether every stage is named, whether the final state is observable, and whether the approved sample reproduces the same result. A supplier answer that only repeats “two-stage locking” is incomplete.
Clause 06 — Make inspection and exceptions explicit
Clause 06. Inspection should record the transition from the first defined state to the final state, including who or what initiated each transition. A generic “lock works” check does not prove the ordered sequence, and an end-state check alone does not prove how it was reached. State the test conditions, normal steps, observation points and acceptance criteria.
For exceptions, name the event, permitted response, responsible party and required record. Do not let “manual override” remain unbounded in a smart lock submittal. The procedure should say what is authorized, who may perform it and what condition must be restored afterward.
Whether a sequence is suitable for a particular door assembly or permitted use is not settled by this glossary.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the applicable local door, fire, access and egress requirements for the specific project, and obtain the required authority or client sign-off.
Clause 07 — Control handover and later changes
Clause 07. Handover should transfer the agreed sequence, not just the lock. Include the marked-up door schedule, stage diagram, operating instructions, inspection record and exception procedure. Give each line a configuration identifier. Site records should carry the references used in Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey, rather than a generic site note.
The build-up behind that decision is in retrofit smart lock vs new lock installation. That is the same question two stage lock definition has to answer here.Any later change to stage count, transition method, exception behavior or identification should trigger a documented review against the approved configuration. A revised sample or product-change notice may be required.
Deliver one working definition, one sequence diagram, one inspection method and one change-control route. Ask the supplier to return these items with the quotation and sample approval record. This gives an importer comparable quotations and gives the receiving team evidence that the installed lock matches the agreed two-stage-lock configuration.
Ask for the offer against the same requirement: request a quote.

