Submittal Process: A Smart Lock Specifier Guide
Use this submittal process specifier guide as a standards decision tree for evaluating electronic lock packages without turning every question into a meeting. A submittal is more than a brochure and more than a request for approval. It is an ordered package of product evidence, installation information, project decisions, exceptions, and signatures. Its purpose is to let a future reader understand what was proposed, what was checked, who accepted it, and which revision remains valid.
Direct answer. In brief, this article covers submittal process specifier guide from submittal process specifier guide to submittal-process. It states what to confirm about submittal process specifier guide on the dated product page where a figure is involved. A submittal process specifier guide supplies the template, the evidence list and the deciding questions. submittal process specifier guide is where the submittal process specifier guide pack is applied.
This article defines submittal process specifier guide through submittal process specifier guide. The definition of submittal process specifier guide is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.
- Write the requirement — use a template that names the physical constraints in submittal process specifier guide
- List the evidence — attach the conformity file for the SKU behind submittal-process
- Send it once — issue one complete package per door class, not one per query
- submittal process specifier guide runs this sequence, and submittal process is the record it produces.
The tree works because each branch has an identifiable pass condition. Identity comes before technical comparison. Dimensional information comes before a claim that the product fits. Project-specific authority decisions come before the package is treated as complete. A changed condition returns the package to the relevant branch rather than allowing an informal assumption to carry forward.
A completed review produces two connected records. The first is the package received from the supplier. The second is the dated disposition returned by the reviewer. Neither record replaces the other: the package shows what was offered, while the review record shows what the project team accepted, rejected, or held pending further evidence.
Branch 1: Establish the Package Before Reviewing the Product
Begin with the project request, not the product literature. The transmittal should identify the door or door set, the intended function, the supplier, the exact product identifier, the package revision, and the person requesting review. Without that information, the reviewer cannot determine whether the material answers the requirement or is merely relevant to a different door.
The smart lock submittal requirements should create a common sequence for every submission. That sequence turns the door hardware submittal into an auditable package rather than a collection of attachments. It also gives the supplier a place to show which document supports each answer.
| Package position | Required item | Responsible party | Result if absent |
|---|---|---|---|
| 1 | Transmittal record and requested review | Supplier | The reviewer cannot identify the request or its project context |
| 2 | Exact product identity and dated revision | Supplier | Comparison may proceed against the wrong item |
| 3 | Product data sheet and supporting drawings | Supplier | Functional and dimensional claims cannot be traced |
| 4 | Installation and door-interface information | Supplier | The installer cannot compare the product with the actual opening |
| 5 | Evidence register with document scope and holder | Supplier and relevant reviewers | “Complies” statements remain unsupported |
| 6 | Exception, substitution, or clarification request | Requesting party | A departure from the specified requirement can remain hidden |
Sequence the package in this order, but allow the sections to be cross-referenced. A dimensional drawing can support the product data sheet, and a test report can support a written capability statement. The cover sequence should still make clear which item is controlling when the attachments appear to disagree.
Assign preparation and acceptance separately. The supplier signs that the package accurately identifies what is offered and includes the documents listed. The reviewer signs the check against the stated criteria. Where a decision belongs to another authority, that party records the decision in its own process; the reviewer records only the reference and status of that decision. Every commercial claim here has to be checked against the smart door locks.
Branch 2: Follow the Decision Tree Instead of the Document Pile
A technical package often arrives in the order the supplier assembled it. The review should follow the order in which decisions depend on one another. That sequence prevents a persuasive function description from obscuring a missing dimension and prevents a dimensional promise from bypassing an unresolved access decision.
flowchart TD
A["Receive the package"] --> B["Check exact product and revision"]
B -->|Complete| C["Check required document set"]
B -->|Missing identity| X["Return incomplete package"]
C -->|Incomplete| X
C -->|Complete| D["Check door fit dimensions"]
D -->|Missing| Y["Hold for dimensional evidence"]
D -->|Complete| E["Check operating and authority branches"]
E -->|Authority pending| Z["Hold for named decision"]
E -->|No authority branch| F["Evaluate criteria and exceptions"]
Z -->|Decision received| F
F -->|Criteria met| G["Record review and approval"]
F -->|Exception open| W["Record revision request"]
Each branch has a different decision owner. The supplier prepares the evidence. The specifier checks it against the project criteria and the written exceptions. The installer or site team confirms the door conditions that the review depends on. A building-control, fire, or access authority decides matters assigned to that authority.
| Decision branch | Pass condition | Return condition | Decision owner |
|---|---|---|---|
| Product identity | Exact item and controlling revision are named | Product family or undated literature is presented | Specifier |
| Door fit | Dimensional information maps to the actual door set | Required dimensions cannot be checked | Specifier with installer input |
| Operating arrangement | Intended function, interfaces, and power behavior are documented | Evidence does not answer the stated use | Specifier |
| Authority branch | Named decision is recorded for the applicable project issue | Review remains pending | Authority identified in the project criteria |
| Exception | Comparison criteria and reasons are recorded | Request is unsupported or outside the permitted change route | Specifier |
| Final disposition | Outstanding items are closed and the review is dated | A blank approval field or open condition remains | Reviewer |
This structure also creates a useful evidence request. Instead of asking the supplier to “send more information,” the reviewer can identify the branch, the missing document, the affected statement, and the person who must respond.
Branch 3: Make the Product Identity Traceable
The product identity branch asks a narrow question: can another reader determine exactly which item is being reviewed? A brand, product family, photograph, or general brochure is not enough. The package must connect the manufacturer’s identifier, the exact model or SKU, the document revision, and the dates of the material being supplied.
The product data sheet should be the controlling summary for the offered item. Confirm on the dated product page for the specific SKU before relying on a dimension, power statement, credential option, interface, or other model-level capability. A statement valid for one variant cannot be transferred to another variant merely because the family name is the same.
Traceability should continue beneath the headline product name. Each installation drawing, test report, instruction document, and finish reference should identify the item to which it applies. If an attachment covers a range of products, mark the relevant variant and explain which lines apply to this submission.
A capability statement remains conditional until the supplier identifies the document that supports it, the scope of that document, and where the controlled copy is held.
CONFIRM-PER-SUPPLIER
Do not accept a general statement that an item “complies.” Ask for the named document, its applicable scope, and the holder of the record. The reviewer then records whether that evidence answers the project question. The supplier’s role is to provide the evidence; the reviewer’s role is to assess its relevance.
If the product identity changes during review, stop the current technical review. Issue a revised package index, identify every document that changed, and state whether the dimensional, functional, or authority branches need to be reopened. A revised photograph alone does not justify resetting the entire review, but a changed product identifier may.
Branch 4: Verify Fit Against the Door
The dimensional branch exists because a lock is never evaluated as an isolated object. It is evaluated as part of a door set containing the leaf, frame, hardware, locks, egress route, and locking arrangement. The installer must be able to transfer the submittal information to the door that is actually on site.
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; a submittal that omits either one cannot be checked. Mortise and rim products describe different case arrangements, while multipoint hardware operates several locking points through one gear. Faceplate and strike form the matching halves at the closing edge.
The dimension the installer needs is the backset, stated in the format used on the project drawing, with its unit and tolerance where applicable. The same rule applies to every other dimension: state the measurement, its datum, and the drawing or field-check source. Do not expect the reviewer to infer missing information from a scaled photograph.
| Check | Evidence needed | Review question |
|---|---|---|
| Case arrangement | Marked installation drawing | Is the offered arrangement suitable for the door construction being reviewed? |
| Backset | Dimensioned drawing | Can the installer locate the spindle or cylinder relative to the door edge? |
| Bore diameter | Dimensioned drawing | Is the opening shown separately from bolt-to-bore distance? |
| Bolt-to-bore distance | Dimensioned drawing | Can the installer verify the offset rather than estimate it? |
| Faceplate and strike | Matched detail | Do the two closing-edge components correspond to the stated door thickness and arrangement? |
| Door interface | Field information and drawing | Does the package reflect the current leaf, frame, hardware, and locking arrangement? |
An Office Smart Lock Site Survey should be used to capture the conditions against which the submittal is checked. For an existing opening, the Smart Lock Retrofit Site Survey should distinguish a documented condition from an assumption made during review.
The Submittal Process: Common Submittal Process Errors that Delay a Project provides a useful companion when a package appears complete but contains dimensions that cannot be reconciled with the door set.
Branch 5: Test the Intended Operating Arrangement
After identity and fit are established, the reviewer can test whether the offered product answers the operating requirement. Record the intended users, credential process, event information, scheduling needs, manual operation, and interface dependencies. Describe the requirement rather than relying on a catalogue phrase such as “commercial access” or “connected lock.”
The evidence should connect each requested function to the operating context. If access records are required, identify where those records are produced and retained. If the door must report its open or closed state, identify the interface and the intended signal. If the project uses an existing controller or credential system, request the compatibility evidence without assuming that a family-level statement applies to the selected SKU.
The evidence request should identify the exact integration point, because a general connectivity statement does not demonstrate that the proposed configuration matches the project system.
Where access provisions affect an installed operable part, request the project’s acceptance criteria and the person responsible for the decision.
CONFIRM-WITH-ACCESS-CONSULTANT
The submittal should not silently convert an accessibility question into a product claim. It should show what the project requires, how that requirement was checked, and which evidence or decision record closes the question. This keeps product facts, project criteria, and authority judgments visibly separate.
Branch 6: Route Egress, Fire, and Building Decisions
Some branches cannot be closed by the supplier because the decision belongs to a named project authority. Egress and panic hardware affect the locking arrangement on an escape route. Ask which authority approved the proposed combination, what document records that decision, and whether the decision applies to the exact door and project conditions.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
A fire-door assembly must be considered as an assembly. When an electronic component is proposed, request the evidence and acceptance route for that combination rather than applying the result from one component to the complete door.
CONFIRM-WITH-FIRE-AUTHORITY
Accessibility, fire behavior, and other local building requirements should appear as project-specific questions. The package should identify the applicable criterion, the authority or reviewer who makes the determination, and the document that will carry that determination.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
Do not convert these branches into broad statements that a product is permitted for a use. The reviewer’s task is to identify the missing decision and keep the package on hold until the named authority records the outcome. An authority reference without a scope, project link, or recorded decision is still an open item.
Keep the authority decision separate from the supplier’s product evidence. This separation allows the record to show whether a statement came from the supplier, the project team, a consultant, or a regulator. It also makes later revision easier because the affected branch can be reopened without discarding unrelated approvals.
Branch 7: Resolve Power-Loss and Interface Dependencies
The power branch asks what happens when the normal supply is interrupted and how the door reports or interfaces with other systems. Identify the intended supply arrangement, the role of battery backup, the expected state on power loss, and the restoration sequence. The submittal should define fail-safe or fail-secure behavior according to the door’s role; the product description should not decide that project requirement by implication.
Line supervision and egress interface questions belong in the same review. Line supervision describes how a controller learns that a door is open or closed. An egress interface describes how the system is told that an exit device has been operated. The package should identify each signal’s source, destination, and intended response.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
Where a power-loss decision affects an escape route, ask the relevant authority to confirm the project requirement and the evidence needed for that door.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
The reviewer should not infer automatic restoration, manual release, or reporting behavior from a general product statement. Those answers need evidence for the exact configuration. This is particularly important when the installed door combines an electronic lock, frame, exit device, detection device, and controller.
Branch 8: Return an Explicit Decision When the Package
Not every incomplete package should receive the same response. A missing product identifier is an administrative defect. Missing dimensional information prevents technical evaluation. A pending authority decision creates a hold, even if the remaining package is technically strong. An exception that does not meet the stated comparison criteria needs a revision request.
Use a decision key so that “returned,” “held,” “approved,” and “approved subject to comment” cannot be confused. This avoids a common failure mode in which a request for clarification is later treated as approval.
| Disposition | Trigger | Required action | Status after issue |
|---|---|---|---|
| Return incomplete | Required identity or document is absent | Identify the missing branch item and responsible party | No technical disposition |
| Hold | A named project decision or dimension is still pending | Record the owner, required evidence, and affected package statement | Pending, not approved |
| Request revision | An exception or changed item has not passed the stated criteria | Record the reason and the information needed for reconsideration | Revised package required |
| Accept | All applicable branches pass and no condition remains open | Sign and date the review against the identified package revision | Approved for that revision only |
The evidence request attached to a return should be specific enough for the supplier to answer without restarting the review. Reference the branch, document, drawing, and statement that caused the hold. Do not rewrite the whole package when one controlled item can close the gap.
When the request changes the basis of the specified item, use a recorded substitution route rather than silently replacing the original product. The Submittal Process: Template Language for a Specification can help keep the proposed change separate from the original requirement.
Branch 9: Record Each Signature Against a Defined Scope
The approval workflow needs a record that shows what each signatory accepted. The supplier’s signature confirms the package contents. The specifier’s signature confirms the documented technical review. The installer or site representative confirms the dimensional and interface basis. Any authority decision remains in the record produced by that authority.
A role signature should include the person’s name, organization or party, date, package revision, and the scope of the review. A reviewer should not sign a statement covering documents that were not supplied. If several branches have different dispositions, the record must distinguish acceptance of one branch from a hold on another.
| Review record field | Required content | Reason it is retained |
|---|---|---|
| Package identity | Supplier, exact product, revision, and attachment index | Connects the decision to the material reviewed |
| Review scope | Branches examined and project conditions used | Prevents a general approval from being read broadly |
| Findings | Accepted items, open items, and evidence references | Shows how each branch was resolved |
| Exceptions | Comparison criteria, reasons, and decision | Creates an auditable substitution record |
| Signatures | Role, named person, scope, and date | Establishes responsibility for preparation and review |
| Distribution | Recipients and controlled-copy location | Ensures installers and suppliers use the same revision |
| Handover destination | Record owner and storage location | Preserves the approved baseline after issue |
The submittal review record should use controlled language. The submittal is not approved until the review is recorded and dated. If the product, drawing, evidence register, or project condition changes, create a new review entry rather than editing the earlier decision without an audit trail.
The Submittal Process: Reviewer Checklist provides a practical companion for checking that every review record field has an owner and a source.
Branch 10: Apply the Same Evidence Test to Every Claim
A product claim becomes reviewable when the package identifies what supports it. “Complies” is the starting point for a question, not the end of the evidence. Ask for the document title, issuer or author, scope, date or revision where applicable, and holder of the controlled copy.
The same test applies across branches, but the comparison changes with the claim. A dimensional claim is checked against the door set. A functional claim is checked against the operating requirement. An authority-dependent claim is checked against the named decision record. A capability claim is checked against the exact SKU and dated source.
| Claim type | Minimum supporting evidence | Review test |
|---|---|---|
| Product identity | Exact identifier and dated product information | Is the offered item the item under review? |
| Installation fit | Marked drawing and field correspondence | Can the installer transfer the information to the actual door? |
| Operating function | Dated source for the exact SKU and configuration | Does the source answer the stated requirement? |
| Authority outcome | Named decision scoped to the project condition | Did the authority with jurisdiction make the decision? |
| Exception | Comparison criteria, reasons, and recorded disposition | Can another reviewer reach the same result from the record? |
The Submittal Process: Documents a Specifier Should Demand separates document ownership by branch. Use it to tighten an evidence request without expanding the review into unrelated project material.
Keep unsupported statements in the package, but mark them clearly as unverified. Their presence does not stop the reviewer from checking the supported branches; however, no dependent decision should pass on an unverified statement alone.
Branch 11: Transfer the Decision Into the Handover Record
A submittal review is not complete merely because it has been returned to the project team. The approved package index, the review record, the selected product information, the accepted drawings, and all conditions must have a defined destination. That destination may be the project document repository, the handover archive, or another controlled location named by the client.
State who owns the record after handover and who may retrieve it. The installer should receive the exact approved revision rather than the supplier’s latest generic file. A later change to the door, frame, finish, access arrangement, or power design may require the relevant branch to be reopened.
At handover, check that the as-built record identifies what was actually installed and explains any authorized departure from the reviewed package. Where a departure lacks authority, leave it visibly unresolved in the handover record rather than allowing it to disappear into an informal note.
The handover package should also identify where operating instructions, interface details, and client-controlled information are held. The review record explains why the installation was accepted; the handover record explains what was delivered and how future parties should interpret it.
Branch 12: Record Life-Cycle Assumptions as Assumptions
The final branch asks what the client assumes about the life of the installation. Record maintenance access, power expectations, replacement activities, credential administration, and update responsibilities as project assumptions. Attribute each figure or duration to the client or other party that supplied it.
Do not replace a client assumption with a supplier estimate without identifying the new source. If the supplier has supplied information that informs the assumption, preserve its source and date while retaining the client’s decision. This prevents an informative document from silently becoming the owner’s approved requirement.
The same discipline applies to unresolved operational needs. State what the current package establishes, what remains an assumption, who will test it, and where the result will be recorded. A future reader should be able to distinguish a verified condition from a planning assumption without reconstructing the meeting history.
Branch 13: Convert the Branches into a Repeatable Worksheet
This submittal process specifier guide becomes useful in practice when the decision path is built into the project’s review form. Each line should point to an attachment or a recorded project decision. A blank line remains open; it is not treated as evidence by default.
Use the following sequence for each product review:
- Identify the supplier, exact product, package revision, door, and requesting party.
- List every attachment and the product revision to which it applies.
- Compare the dimensional information with the documented door set.
- Test each operating requirement against a named, dated source.
- Route project-dependent decisions to the named authority.
- Record every exception with its comparison criteria and reasons.
- Choose the disposition: return incomplete, hold, request revision, or accept.
- Obtain the applicable signatures and enter the review date.
- Name the record owner, controlled-copy location, and handover recipient.
- State which change would reopen each branch.
Review the worksheet with the supplier, installer, and project decision-maker before the formal package is issued. This short coordination step catches missing information while the correction is still local. It also establishes who will answer each branch rather than leaving the reviewer to route the entire package around the project.
After circulation, compare the returned package with the worksheet. Any additional attachment should have a purpose in the index. Any withdrawn statement should remain visible in the revision history. The worksheet then becomes the front sheet for the submittal review record and remains the map used when a later change is assessed.
Branch 14: Make Ownership Visible Across the Project
The tree works when the reviewer, supplier, installer, client representative, and project authority each have a defined role. The supplier supplies evidence. The specifier evaluates it against the requirement. The installer confirms the door interface. The client records project decisions. Authorities decide only the questions assigned to them.
Use one package index, one review status, and one controlled revision across those roles. When an item changes, identify the affected branch and reopen only what depends on it. That keeps the process proportionate while preserving a clear history of the decision.
Readers comparing approaches usually start with how much does a smart lock cost. That is the same question submittal process specifier guide has to answer here.The final commercial handoff is the controlled package: a dated product identity, current evidence, verified dimensions, recorded project decisions, signed dispositions, and a named owner for the approved record. When a prospective supplier responds to that package, ask for a document against every open branch rather than a new general presentation. The result is a submittal that can move from specification to procurement without losing the information that made it approvable.
Close the loop with requesting a quote.

