Submittal Process: Documents a Specifier Should Demand
The submittal process documents to demand should begin with a definition because “send us the documentation” gives the supplier, consultant, installer and client different starting points. A smart lock submittal checklist is useful only when it identifies the package being sent, the review record created, the exceptions raised and the owner of each open decision.
Direct answer. Short version — submittal process documents to demand is treated here as submittal process documents to demand first. submittal-process comes second. The evidence for submittal process documents to demand is named in the sections below. A submittal process documents to demand is a resource for whoever writes the requirement. submittal process documents to demand turns a request for submittal process documents to demand into something a supplier can price.
On submittal process documents to demand, this article uses submittal process documents to demand as the definition. It treats submittal process documents to demand as a working definition specific to this market and product, rather than a general one.
- Write the requirement — use a template that names the physical constraints in submittal process documents to demand
- 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
- Treat this as the submittal process documents to demand sequence, with submittal process as the reference.
This clause handbook treats the submittal as a controlled record rather than a brochure attached to an email. It gives a door hardware specifier language for deciding what evidence to request, what a reviewer may infer from it, and what must be referred to the client or a named authority. The submittal is not approved until the review is recorded and dated; a transmitted file is only an offer for review.
Clause 1 — Name the package, the review, and the result
Write the opening clause so that a supplier knows what to assemble, a reviewer knows what to return and the client knows what record will survive later questions. The request must distinguish the submitted package from the review record. It must also distinguish acceptance of a document for coordination from approval of the proposed door set. The build options sit in the smart door locks.
Use a numbered package index containing these layers:
- Transmittal and document index.
- Product identity and configuration.
- Technical and dimensional information.
- Operational and control information.
- Supporting evidence and authority decisions.
- Exceptions, deviations and revision history.
| Package layer | Required content | Control test |
|---|---|---|
| Transmittal | Package index, issue date, preparer and purpose of issue | Every later page can be traced to one issue |
| Identity | Configured product identifier, options and document revisions | The proposed configuration is unambiguous |
| Technical | Drawings, dimensions, interfaces and operating logic | The installer can check the scheduled door set |
| Evidence | Named source, document scope, result and holder | A reviewer can locate the underlying evidence |
| Exceptions | Departures from the specification, open decisions and owners | No unresolved item is hidden in general correspondence |
| Revisions | Change list, affected clauses and superseded material | The current package can be reconstructed |
A brochure may support one layer, but it cannot replace the package. The clause should also require a statement that the supplier has checked the index for completeness. That statement remains attributable to the supplier and does not transfer the specifier’s review responsibility to the sender.
Clause 2 — Bind every page to one product configuration
The product identity page should state the exact configured product identifier, the applicable physical variants, finish, control components and any other options that change the submitted information. It should identify the issuer, issue date and document revision, and it should list the product pages on which each identifier applies. A family name alone is insufficient when the proposed product can be configured in more than one way.
A door hardware submittal should use the same identifier in the transmittal, technical sheets, drawings, operating documents and test evidence. Any change to that identifier should invalidate references tied to the former configuration. This prevents a drawing for one variant from being combined with instructions, dimensions or approval records for another.
Product capability remains a supplier assertion until the dated evidence supports it. Require the supplier to identify the source of each claim and the configuration to which it applies rather than asking the reviewer to infer capability from a feature list or brand family.
CONFIRM-PER-SUPPLIER
Clause 3 — Make dimensional verification impossible to misread
Start with the dimensions of the door actually scheduled and surveyed. 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; omitting either makes the lock case impossible to check against the door preparation. A mortise lock has its case inside the door, while a rim lock is surface-mounted. A multipoint lock operates several locking points through one gear. The faceplate and strike are matching parts of the closing edge and must be reviewed as a pair.
| Required field | Review question |
|---|---|
| Door leaf thickness and construction | Is the proposed case suitable for the scheduled door? |
| Backset | Does the centre position match the door edge? |
| Bore diameter and bolt-to-bore distance | Can both dimensions be checked independently? |
| Spindle or cylinder centre | Does its position align with the specified operating layout? |
| Faceplate and strike | Are they matched to the same door edge and handing? |
| Handing and handing conversion method | Is the installed orientation defined? |
| Installation tolerances | Which variations are the installer expected to resolve? |
The product data submittal should carry a dimensioned drawing and a field schedule rather than a catalogue image. Dimensional verification should compare the proposed information with both the door-hardware schedule and the current site record. A dimension valid for one door set is not evidence for another door set with a different thickness, frame or edge condition.
Survey disciplines should also remain separate from catalogue selection. The field procedure in Office Smart Lock Site Survey can inform an office door set, while Smart Lock Retrofit Site Survey addresses the uncertainties of an existing opening. The supplier still owns the product-specific preparation information; the survey records what the installer found.
Clause 4 — State the door set’s locking arrangement
The submitted documents must describe the locking arrangement as part of the complete door set: the door leaf, frame, hardware and locks are one assembly, not unrelated product selections. The request should identify the egress route, any panic hardware and the intended locking sequence. It should also state whether free egress is to be maintained under the project’s approved arrangement.
A product description cannot decide the treatment of an escape door. The supplier should document the available interfaces and states, while the project’s named authority determines the arrangement that applies to that door. Where accessibility, fire behavior or building-control consequences arise, the evidence must come from the authority responsible for the decision rather than from a catalogue statement.
CONFIRM-WITH-FIRE-AUTHORITY
CONFIRM-WITH-LOCAL-ACCESS-CONSULTANT
| Decision point | Evidence to demand | Decision holder |
|---|---|---|
| Escape-route arrangement | Authority’s dated response tied to the proposed door set | Fire authority identified by the project |
| Accessible operation | Review of the operable part, motion and approach for the installed condition | Access consultant or other named project authority |
| Door identification and control interface | Configuration schedule and interface description | Client’s security and operations representatives |
| Paired-door sequence | Coordination record identifying each leaf and active state | Door-hardware consultant with installer confirmation |
Fail-safe and fail-secure describe the intended state on power loss, but the state is decided by the door’s role rather than by the lock alone. Battery backup is the arrangement intended to keep the door operable when the mains supply fails; the submittal should describe its arrangement without leaving the final choice to a product label. Line supervision reports door-open or door-closed states, while an egress interface tells a controller that an exit device has been operated. Those definitions should appear in the submitted control narrative.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
Clause 5 — Demand the operating logic, not a feature list
A feature list says what a system may advertise. An operating record says what happens when a credential is presented, a schedule changes, a controller is unavailable or staff need an override. Request a short functional narrative for each door type, supported by configuration sheets or interface diagrams. This turns the product data submittal into something the client, operator and installer can test against the same intended behavior.
| Function | Evidence requested | Reviewer test |
|---|---|---|
| Credential decision | Role, credential type and associated access rule | Can each rule be traced to a space and authorized holder? |
| Key control | Master key and hierarchical key relationships | Are exceptional holders and exclusions recorded? |
| Scheduling | Effective periods, exceptions and time source | Is behavior defined when time or connectivity changes? |
| Audit trail | Events retained, event description and retrieval method | Can the record distinguish access from door status? |
| Manual operation | Authorized method and effect on the controlled state | Is the operational consequence stated? |
| Power loss | Door state and available local operation | Does the state match the approved door role? |
| Network loss | Local behavior and later synchronization | Is the temporary state defined rather than assumed? |
| Configuration change | Authorization, version and rollback method | Can the installed configuration be reconstructed? |
The request should prohibit inferred behavior. If a document uses “optional,” “compatible” or “available,” the supplier should identify the configuration, dependency and resulting limitation. This is particularly important when the project mixes credential-based operation with a key-control plan.
CONFIRM-PER-SUPPLIER
Clause 6 — Require evidence with a named source and bounded scope
The word “complies” is not evidence. A useful evidence record names the document or decision, identifies its issuer, states its scope, records the result and identifies who holds the underlying material. It also links that material to the exact product configuration and door position affected by the review.
| Evidence class | Required identity | Limit on reliance |
|---|---|---|
| Dimensional drawing | Drawing number, revision, date and configuration | Establishes the stated geometry only |
| Installation instruction | Publication revision and applicable variant | Does not replace site verification |
| Test or inspection report | Issuer, test reference, sample scope and result | Applies only to the tested sample and conditions |
| Third-party declaration | Issuer, document title, revision and declared scope | Does not extend to an untested variant or option |
| Authority decision | Authority, project, door reference, date and conditions | Governs only the approved project scope |
| Mock-up or sample record | Item, finish, preparation and review participants | Evidences fit and finish, not performance |
| Configuration record | Software, hardware and controlled option references | Identifies the submitted state, not future changes |
Where a standard or regulation is named, the submittal should state what that source governs and what it does not answer for this door. The relevant project authority should confirm the scope. Do not turn a general evidence reference into a product-wide claim.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
The evidence discipline in Submittal Process: A Smart Lock Specifier Guide can support this review, but the clause should still identify the specific document being relied upon for each clause. The guide may explain a decision; the submittal record must contain the evidence used to make it.
Clause 7 — Capture installation, finish and maintenance evidence
The installation package should show where the lock, reader, strike, wiring route, power source and any interface components belong in the door set. It should also show the information needed for later service: access to batteries, configuration controls, cable routes and replacement operations. A drawing that establishes fit but conceals how the unit will be maintained is incomplete.
Finish requires its own identifier. Specify the RAL or colour reference and the applicable hardware or component rather than relying on a photograph. A photograph shows the finish; it does not specify it. Where the door leaf, frame or hardware finish may change, the record should identify which approved references remain controlling.
A physical mock-up or sample is useful for checking fit, finish and preparation, but it evidences fit, not performance. The review record should say who examined it, which door details it represented and what was observed. It must not be used as a substitute for dimensional documents, authority decisions or operating evidence.
Handover documentation should later identify the installed configuration, accepted finishes, test records, configuration backups, operating instructions and outstanding limitations. These records should pass from the project file to the party responsible for the installation rather than disappearing into individual correspondence.
Clause 8 — Assign review rights and use a dated approval record
Each participant should receive only the authority needed to review its part of the package. The supplier assembles and revises the submission. The specifier checks it against the scheduled intent, document completeness and internal evidence. The installer confirms preparation and interface assumptions. The client decides project intent and accepted deviations. The relevant authority decides any fire, building-control or accessibility question within its scope.
| Disposition | Meaning | Required record |
|---|---|---|
| Returned incomplete | Required content is missing or cannot be checked | Clause references, missing items and request for resubmission |
| Revise and resubmit | The approach may remain possible but the evidence needs correction | Owner, required change and affected clauses |
| Accepted for coordination | A document may be used in coordination without implying final approval | Scope of coordination and unresolved decisions |
| Approved as noted | Accepted subject to stated notes or conditions | Notes, responsible parties and evidence of closure |
| Rejected | The proposed item or method is not accepted for the project | Reason, decision maker and required next path |
The review record should identify the reviewer, date, package revision, disposition and any notes. A later change to the package creates a new review record rather than silently altering the earlier decision. An approval obtained for one configuration does not migrate automatically to another.
CONFIRM-WITH-FIRE-AUTHORITY
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
The operational checks can be separated from this record through Submittal Process: Reviewer Checklist. That checklist is useful only when its result is written into the approval record with the package revision it reviewed.
Clause 9 — Return incomplete packages without inventing a decision
An incomplete package should be returned with a status of “returned incomplete,” not rejected on the assumption that the proposed solution is wrong. The notice should identify the clause, the missing field or evidence, the reason it prevents review, the party able to supply it and the content expected in the replacement package.
A product brochure without dimensions, for example, cannot support dimensional verification. A statement that a document “complies” cannot identify its scope. An undated authority response cannot establish which decision was issued for the current door set. Each gap needs a specific correction rather than a general request for clarification.
If the same issue repeatedly returns, the specifier should consider whether the request itself is ambiguous. Template wording should distinguish required content from optional supporting material. Submittal Process: Template Language for a Specification is relevant when the clause must distinguish a mandatory field from guidance.
Clause 10 — Control revisions and substitutions
Revision control should begin with a document index that shows the current revision of every page. Each reissue needs a dated transmittal and a change list identifying the affected clauses. The package should mark superseded sheets and withdrawn evidence rather than leaving them available for accidental use.
A change to dimensions, finish, operating logic, interfaces, authority conditions or evidence scope requires an impact review. The reviewer should ask which dependent conclusions remain valid, not merely whether the changed page received a new revision number. Product identity, drawings, evidence and the approval record must remain linked to the same configuration.
An or-equal request should follow the same comparison and decision discipline. The requester supplies the proposed item and supporting evidence; the specifier records whether the substitute is accepted and why. Acceptance of an alternative does not transfer the decision for fire behavior, accessibility, building control or another authority-controlled question to the reviewer.
Clause 11 — Compare the decision rather than the brochure
This submittal process documents to demand decision map prevents a reviewer from treating every page as equally decisive. The question is not whether the package contains a glossy sheet. The question is whether the named document answers the outstanding issue for the scheduled door set and current revision.
| Decision | Evidence that resolves it | Accept only when | Refer when unresolved |
|---|---|---|---|
| Product identity | Configuration and option schedule | Every referenced page matches one identifier | Supplier identifies an ambiguous or changed configuration |
| Dimensional fit | Dimensioned preparation information | All critical dimensions are stated and compatible | Surveyed door data conflicts or is absent |
| Locking arrangement | Door-set description and authority decision | Arrangement and conditions match the approved door | Authority has not issued or renewed the decision |
| Operational behavior | Functional narrative and configuration record | Required behavior is explicit and testable | Behavior is inferred from a feature list |
| Evidence scope | Named source with bounded scope | Document, issuer, revision and applicability are clear | Evidence concerns a different variant or condition |
| Finish | RAL or colour reference and applicable component | Finish is objectively identified | Only an image or general description is supplied |
| Revision status | Dated transmittal and change list | Current and superseded material are distinguishable | Changed content has not been impact-reviewed |
| Approval | Dated review and final disposition | Decision covers the current package revision | Status is only a verbal comment or email acknowledgement |
A package passes when the evidence chain is closed for the issues that affect the decision. It does not pass merely because each document has been viewed. The reviewer should be able to move from the approval record to the dimension, authority decision, evidence source and configuration that support it.
Clause 12 — Move the package through a visible decision path
The review workflow should make incompleteness visible without treating it as rejection. Every return should identify the route back into the process and the checks that must be repeated.
flowchart TD
A[Indexed submittal received] --> B{Identity and scope complete}
B -- No --> C[Return incomplete package]
B -- Yes --> D{Door geometry verified}
D -- No --> C
D -- Yes --> E{Evidence attached}
E -- No --> F[Refer decision to named authority]
E -- Yes --> G[Record dated review]
F --> G
G --> H{Final disposition selected}
H -- Revise and resubmit --> C
H -- Approved as noted --> I[Issue revision controlled record]
A corrected package re-enters at the affected gate. The reviewer should not reopen unrelated approvals simply because a page reference changed, but any change that affects a prior conclusion must be reviewed again. The final record should show the route taken, not just the destination.
Clause 13 — Issue a compact index that can be completed
The issue-ready request can be reduced to a compact index supported by this handbook. Each line should point to the detailed clause rather than repeat it:
- State the exact configured product and option scope.
- Identify every drawing, instruction and evidence document by revision.
- Supply the dimensions required for dimensional verification.
- Describe the complete door set and its locking arrangement.
- Explain normal operation, exception modes and audit information.
- State power-loss, backup and interface behavior for the proposed configuration.
- Name each evidence source, its scope and its holder.
- Attach the applicable authority decisions with project and door references.
- List finish, mock-up and maintenance information separately.
- Submit the transmittal, exception list and revision history together.
Before issue, ask a colleague to use only the index and submitted package. If that reviewer cannot answer a scheduled decision, the index or package needs another layer. The test reveals whether the request works without relying on a remembered meeting or an informal explanation.
Reusable language for the specification can be separated from the package evidence. Submittal Process: Template Language for a Specification helps with clause construction, while the index remains the control that shows what was actually submitted.
Handover record: convert the decision into usable project
The approval record becomes one input to the project handover package. The record owner should assemble the final approved revision, authority decisions, installation configuration, finish record, commissioning evidence and outstanding conditions under the project’s document system. The as-built record should identify what was installed where the approved submittal differs from the proposal.
Any client assumption about installation life belongs in the client’s own model as an identified assumption, using the information the client supplied. A supplier-provided figure should not silently become the client’s planning basis. Where the installer encounters a condition that prevents the submitted preparation, the variance should be recorded and reviewed rather than corrected informally.
Readers comparing approaches usually start with smart lock supplier checklist for first time buyers. That is the same question submittal process documents to demand has to answer here.The final request to a prospective supplier is straightforward: return one indexed package, one revision-controlled evidence set and one decision record. A specifier can then approve the current door set with confidence, explain what evidence supported the decision and show which later change requires a fresh review.
The quote request is where the decision turns into a number: request a quote.

