Submittal Process in New Construction
The submittal process new construction teams use should convert a design intention into a recorded decision that the installer can execute. This handbook defines that process clause by clause for a door-hardware consultant or specifier managing electronic access hardware.
Direct answer. In short, submittal process new construction is the subject of this piece. submittal process new construction is where the work on submittal process new construction sits. submittal-process is what has to be evidenced before anyone signs. A submittal process new construction is a resource for whoever writes the requirement. submittal process new construction turns a request for submittal process new construction into something a supplier can price.
submittal process new construction is used here in the narrow sense set out in submittal process new construction. It is a working definition built for submittal process new construction. It is not a statutory one, and it has to be read against the market and product concerned.
- State the requirement — use a template that names the physical constraints in submittal process new construction
- Compile the documents — attach the conformity file for the SKU behind submittal-process
- Submit once, complete — issue one complete package per door class, not one per query
- For submittal process new construction, submittal process is what each step has to answer to.
A submittal has two connected parts: the package submitted for review and the review record returned with a decision. The package may contain drawings, schedules, product information and supporting evidence. The review record identifies the reviewed revision, unresolved conditions and the person or role that made the decision. Without that record, the submission remains open regardless of how complete the package looks.
Clause 01 — Establish the review object before the package arrives
A review must have a defined object. Identify the project, the affected door sets, the design revision, the contract package and the person responsible for the technical decision. If those references are missing, the recipient cannot know whether a comment applies to one opening, a repeated door type or the entire building. The earlier published note on this is Smart Lock Market for New Construction. Specifications at this level come off the smart door locks.
Use three separate outcomes. Received means the package entered the review queue. Reviewed means assigned reviewers returned findings. Approved means the decision maker accepted the named revision for its stated scope. These labels prevent an acknowledgement of receipt from being mistaken for technical acceptance.
| Decision or deliverable | Prepared or confirmed by | Accountable decision maker | Required record |
|---|---|---|---|
| Door schedule and design basis | Design team | Project specifier | Issued design revision |
| Door-set fit information | Supplier, installer and door-set team | Door-hardware specifier | Marked-up submittal |
| Product and integration evidence | Supplier | Technical reviewer | Evidence register |
| Egress, fire and access decisions | Relevant authority or consultant | Authority named by the project | Dated approval or response |
| Submittal disposition | Review coordinator | Project specifier | Recorded review decision |
The responsibility table is a working allocation, not a replacement for the contract. Adapt the names to the project structure, but do not leave the decision owner blank. The coordination role is examined more fully in Submittal Process: Coordination Between Architect and Supplier.
flowchart TD
A[Design basis issued] --> B[Submittal received]
B --> C{Intake complete}
C -->|No| D[Return as incomplete]
C -->|Yes| E[Technical review]
E --> F{Authority items resolved}
F -->|No| G[Hold with named action]
F -->|Yes| H[Decision recorded]
H --> I[Approved revision released]
Clause 02 — Identify the door set before evaluating the lock
The reviewer must be able to connect the proposed lock to the door that will be installed. A brochure, family photograph or catalogue dimension may provide context, but it cannot establish fit for the project door. The new construction lock submittal should therefore begin with door-set fit information tied to a drawing and schedule reference.
For each opening, require the door mark, door type, opening direction and handing. Record the leaf thickness and the dimensional relationships needed to prepare the door. These include backset, bore diameter, bolt-to-bore distance and the faceplate and strike arrangement. Where multipoint hardware is proposed, identify the locking points and how they are operated. The lock case may be mortise or rim mounted, and the submitted information must make that distinction clear.
| Required item | Review question | Failure prevented |
|---|---|---|
| Door mark and opening reference | Does the information match the issued door schedule? | Review of the wrong door type |
| Backset | Is the distance from the door edge to the spindle or cylinder centre stated? | Bore prepared in the wrong location |
| Bore diameter | Is the required bore identified separately from the backset? | Unprepared or incorrectly prepared door |
| Bolt-to-bore distance | Is the relationship between bolt and bore shown? | Incorrect bolt engagement |
| Faceplate and strike | Are both closing-edge components identified as a matched arrangement? | Door that closes but cannot be secured as intended |
| Leaf thickness and construction | Are the preparation assumptions stated for the actual door? | Surface-mounted or concealed parts that do not fit |
| Finish reference | Is the finish identified by its reference rather than a photograph? | Delivered finish that cannot be checked objectively |
Backset, bore diameter and bolt-to-bore distance are separate dimensions. Do not allow a product brochure to substitute for them. The dimension the installer needs is the project-specific dimension, stated in the format shown on the approved fabrication information.
The supplier may provide a product template, but the installer or door-set team must confirm which project dimensions apply. Where the construction information is still developing, label the affected value as an assumption and state what evidence will close it. A photograph shows the finish; it does not specify it. Use the applicable colour reference and identify the door and component to which it applies.
Clause 03 — Require a package that can be reviewed without a call
| Package part | Minimum content | Reviewer can test |
|---|---|---|
| Cover and transmittal | Project, door marks, submission purpose, revision and requested decision | Whether the package has a defined review object |
| Door and lock drawings | Plan, elevation and detail views tied to the door schedule | Whether the proposed arrangement matches the design |
| Dimensional schedule | Backset, bore, bolt-to-bore, leaf thickness and faceplate information | Whether the installer can prepare the actual door |
| Product information | Configuration, finishes, interfaces and components offered for the project | Whether the proposed item corresponds to the submitted doors |
| Evidence register | Document title, revision, scope, issuer and project reference | Whether each claim is traceable |
| Installation information | Preparation, wiring or power requirements, setup and handover requirements | Whether the information can be coordinated |
| Exceptions and assumptions | Unresolved values, dependencies and actions | Whether anything is being mistaken for approved fact |
| Approval block | Review disposition, conditions, reviewer role and date | Whether the review is complete |
The document set can be developed with the framework in Submittal Process: Documents a Specifier Should Demand. The focus here is sequence: a later document should not be used to introduce a change that belongs in the earlier design record.
Clause 04 — Convert capability statements into evidence requests
A submittal should not ask the reviewer to infer compliance from marketing language. Every capability or holding claim should point to a document that states its scope, revision and owner. The evidence register is the control that makes this possible.
Use a consistent row for each claim: the statement made, the evidence supplied, the project element affected and the reviewer’s disposition. A capability statement remains provisional until the supplier confirms it for the exact project configuration.
CONFIRM-PER-SUPPLIER
| Claim type | Evidence the reviewer should request | Acceptance test |
|---|---|---|
| Product configuration | Dated product information or project-specific schedule | Does it identify the proposed configuration? |
| Installation requirement | Preparation or wiring drawing | Can the door and electrical teams work from it? |
| Functional behavior | Test record, procedure or technical description tied to the claim | Does the evidence cover the condition being relied upon? |
| Interface dependency | Interface statement and responsibility matrix | Are the parties and limits clear? |
| Finish | Dated finish reference or approved sample record | Can the delivered finish be compared objectively? |
| Authority-related matter | Authority response or approval record | Has the named decision maker issued it? |
“Complies” is not a document. A useful evidence request names the document, the revision, the scope and the holder. If the evidence is a third-party report, identify its stated subject and limits without implying that it covers every project condition. If the statement depends on a product page, confirm on the dated product page for the specific SKU.
Clause 05 — Control the review sequence and stop incomplete reviews
At intake, check the index against the minimum package. Reject a package as incomplete when a required document is missing, the door mark is absent, the revision cannot be identified or the requested decision is unclear. State the missing items in the return record and identify who must supply them.
| Review gate | Core question | Output |
|---|---|---|
| Intake | Is the package complete enough to review without reconstruction? | Accepted for review or returned as incomplete |
| Door-set review | Can the proposed arrangement be checked against the actual door? | Fit comments and unresolved dimensions |
| Evidence review | Does every relied-upon claim have traceable evidence? | Accepted evidence or further request |
| Coordination review | Are interfaces, power routes and responsibilities assigned? | Coordination actions and owners |
| Authority review | Has the relevant decision maker answered the project-specific question? | Dated authority record |
| Final disposition | Which named revision is approved, subject to conditions or returned? | Controlled review record |
Return incomplete packages as a distinct status. Do not mix missing information with technical rejection; the supplier needs to know whether the problem is administrative or substantive. Common examples of this failure pattern are discussed in Common Submittal Process Errors that Delay a Project.
Clause 06 — Keep product choice separate from design decisions
| Design decision | Supplier responsibility | Specifier responsibility |
|---|---|---|
| Door and frame arrangement | Explain product preparation and fit | Define the project door set |
| Locking arrangement for each opening | State the behavior of the proposed configuration | Establish the required arrangement |
| Escape-route operation | Describe how the proposed interface is intended to work | Obtain the required authority decision |
| Credential and access model | State the proposed method and dependencies | Define project access intent |
| Finish | Provide the available reference and limitations | Establish the approved project finish |
| Service and maintenance path | Explain the physical access required | Ensure coordination with the design |
Fail-safe and fail-secure behavior is decided by the role of the door, not by the product family. A submittal should state the required power-loss state, the proposed response and the authority or client decision supporting it. It should not allow the installer to infer that state from a product name.
Clause 07 — Make revision history part of the decision
Revision control must show what changed, why it changed and which prior comments the change closes. Assign a new revision to the package whenever a reviewed drawing, schedule, product configuration or evidence register changes. Do not overwrite the submitted issue or leave comments on an uncontrolled redline.
Use a revision table that identifies the affected door, the changed item, the reason, the originator and the affected review comments. A consolidated drawing alone does not replace this record when separate documents carry different revision dates.
| Revision event | Required record | Result |
|---|---|---|
| Initial package | Transmittal, issue date and full index | Baseline for review |
| Comment response | Response matrix tied to comment numbers | Evidence that the issue was addressed |
| Design revision | Revised drawing and schedule references | New review baseline where affected |
| Supplier resubmittal | Revised package and superseded-item list | Clearer re-review scope |
| Clarification | Question, response and affected item | Avoids unnecessary full resubmittal |
| Partial approval | Explicitly identified door marks or sheets | Prevents unapproved scope being released |
A revision should state which items remain unchanged. This reduces repeated checking while preserving responsibility. Where a change was caused by site information, request the project record that supports it. Where it was caused by a product constraint, record the constraint and the design response.
The commercial effect of a revision can be evaluated separately from the technical decision. Submittal Process: Cost and Risk Consequences provides that comparison, but the submittal record should still remain factual: no unsupported figures, assumptions or claims should be introduced as if they were settled.
Clause 08 — Bind approval to coordinated construction information
Link every coordination item to a responsible party and a closure record. The item is not closed merely because a drawing includes a note. The receiving team should confirm that it can meet the requirement or record the change it needs.
| Coordination item | Information in the submittal | Coordinating party | Closure evidence |
|---|---|---|---|
| Door preparation | Preparation drawing and dimensional schedule | Installer and door-set team | Confirmed fabrication information |
| Frame and strike | Faceplate and strike arrangement | Door and frame team | Approved detail |
| Power and wiring | Route, connection point and dependency | Electrical team | Coordinated drawing |
| Access-control interface | Controller, reader or exit-device relationship | Security or controls team | Interface responsibility record |
| Network position | Device location and coverage dependency | Network designer | Coverage or connection plan |
| Door schedule | Final mark and hardware relationship | Design team | Issued schedule revision |
Where the design remains incomplete, identify the hold point. For example, a door schedule may reserve a lock position while the final frame detail remains open. This reservation is not product approval. Record it as an assumption and state the event that will trigger review of the affected lock submittal.
Clause 09 — Preserve the authority decisions that the project
| Project question | Evidence to request | Decision record |
|---|---|---|
| Is the locking arrangement acceptable at this escape door? | Response from the authority responsible for the project location | Dated approval or conditions |
| Does an electronic component affect the fire-door assembly decision? | Response from the fire authority | Assembly-specific decision |
| Is the operable approach suitable for the intended users? | Response from the access consultant or client’s designated reviewer | Approved operating arrangement |
| Which evidence must accompany the installed assembly? | Project instruction from building control | Handover evidence list |
CONFIRM-WITH-LOCAL-BUILDING-CONTROL
CONFIRM-WITH-FIRE-AUTHORITY
CONFIRM-WITH-LOCAL-ACCESS-CONSULTANT
The questions must identify the door and its intended function. A response for one opening cannot be transferred to another merely because both are escape doors. The fire authority may ask about the assembly as a whole, while building control may ask about a different part of the project. Confirm which authority signs off and for which scope.
The required evidence must travel with the approved revision. If a condition changes the lock, frame, exit device or surrounding construction, route the affected package back through review. Do not treat a permission granted for one assembly as blanket permission for the project.
Clause 10 — Record assumptions before they become hidden facts
| Entry type | Example form | Required follow-up |
|---|---|---|
| Verified project fact | Door mark and dimension confirmed from the issued fabrication record | Retain the source reference |
| Supplier statement | Capability described for a named configuration | Confirm the statement for the proposed SKU and project scope |
| Design assumption | Temporary coordination value pending an updated door detail | Name the designer and required issue |
| Open decision | Locking arrangement awaiting the relevant authority | Name the decision maker and required record |
| Client assumption | Expected service condition supplied by the client | Preserve as the client’s stated assumption |
Do not convert a supplier value into a project requirement without checking the source. Do not convert a temporary design value into a verified dimension because it appears in an approved drawing. Keep the client’s assumptions distinct from supplier information, particularly when they concern service life, operating conditions or future changes.
The submittal should identify which assumption could change the selected product, the installation or the approval. A low-impact clarification can be closed in the next package. A value that changes door preparation, authority review or the product configuration requires a formal resubmittal.
Clause 11 — Issue conditional approval without losing the condition
| Disposition | Meaning | Release rule |
|---|---|---|
| Approved | The named revision is accepted for the listed scope | Release the approved revision |
| Approved subject to closure | The decision is positive but named evidence remains outstanding | Release only if the contract permits; close the condition before installation |
| Revise and resubmit | Material information or evidence requires a new review | Hold the affected scope |
| Not approved | The proposal does not meet the stated requirement | Resolve the identified issue before resubmittal |
| Incomplete | The package cannot enter technical review | Supply the listed items |
A submittal approval record must identify the reviewed revision, the affected doors, the disposition, each condition, the responsible owner and the date. When all conditions close, issue a final or unconditional approval record rather than relying on a collection of email confirmations.
Conditions should be verifiable. “Confirm dimensions” is weak because it does not say who confirms them or what evidence closes the item. “Installer to issue the approved fabrication dimension for door marks identified in the submittal schedule” identifies an output and an owner.
Clause 12 — Transfer the approved record at handover
The submittal record must survive into construction and handover. The project team should receive the approved revision, not the latest file found in a supplier folder or mailbox. The door schedule, fabrication information, approved product configuration and outstanding conditions must be linked by revision.
| Handover record | Responsible party | Form at handover |
|---|---|---|
| Approved submittal register | Specifier or document controller | Controlled schedule with revisions |
| Final door and hardware schedule | Design team | Issued project drawing and schedule |
| Fabrication and preparation information | Installer or door-set team | Approved shop or fabrication record |
| Authority decisions | Responding authority or project coordinator | Dated response or certificate in the project record |
| Configuration and setup record | Supplier or commissioning team | Project-specific completion record |
| As-built changes | Design and construction team | Updated drawing and schedule |
| Open-item disposition | Project decision maker | Closure record or approved carry-forward |
The owner of the record after handover should be stated in the project’s document-control arrangements. A client may retain the design record, while the contractor may retain installation records and the supplier may retain its approved configuration record. The project needs an index that shows where each item is held without making unsupported claims about who owns every underlying file.
Final approval does not freeze the project. A later door-material or frame change can affect preparation. A hardware substitution can affect evidence. Record the change against the affected door and route it through the same review logic. The handover index should distinguish the original approved basis from later approved changes.
Reviewer worksheet — twelve questions before disposition
| Reviewer question | Evidence checked | Result |
|---|---|---|
| Are the project, doors and requested decision identified? | Transmittal and schedule | Pass or return |
| Is the package revision controlled? | Revision register | Pass or return |
| Can the lock be checked against the actual door? | Dimensioned drawings | Pass or comment |
| Are backset, bore and bolt-to-bore treated as separate dimensions? | Preparation schedule | Pass or comment |
| Does every relied-upon claim point to evidence? | Evidence register | Pass or request |
| Are configuration, finish and interfaces tied to the proposed SKU? | Product information | Pass or request |
| Have unresolved assumptions been labelled? | Exceptions schedule | Pass or return |
| Have the relevant authorities answered their project questions? | Dated authority records | Pass or hold |
| Are construction dependencies assigned to coordinating parties? | Coordination matrix | Pass or action |
| Are revision changes tied to previous comments? | Revision history | Pass or return |
| Is every approval condition measurable and owned? | Disposition record | Pass or hold |
| Is the final record suitable for procurement and handover? | Controlled register | Release or retain |
For a more compact working format, compare this worksheet with Submittal Process: Reviewer Checklist. The reviewer should still record the actual evidence examined. A tick without a document reference does not provide a useful audit trail.
A practical review record contains six elements: package identifier, affected door marks, revision reviewed, findings, disposition and date. Keep commentary in a linked response matrix. When the decision is approval, state whether it covers the package as submitted or only named conditions.
Model clause language — a usable starting point
Electronic access hardware submittal: Submit each proposed lock under a numbered transmittal identifying the project, affected door marks, design revision and requested decision. Include door-set drawings and dimensional information; product and configuration information; evidence for each relied-upon capability; installation and interface requirements; finish references; and a schedule of assumptions and open items. The reviewer shall return one of the following recorded dispositions: approved, approved subject to closure, revise and resubmit, not approved or incomplete. A submission is not approved until the decision is recorded against the reviewed revision. Approval applies only to the listed scope. Changes to the door, frame, locking arrangement, product configuration or relevant authority decision require resubmittal of the affected items.
This clause language can be coordinated with Submittal Process: Template Language for a Specification. Avoid broad phrases that grant approval “in principle”. Define the affected scope, the review object and the point at which a decision becomes final.
The opening requirement should also name the evidence holder and the required revision. If the contract gives another party the final decision, state that relationship instead of creating an inconsistent approval route. For escape doors, frame the authority question without predetermining its answer.
Readers comparing approaches usually start with what documents should you request from a smart lock supplier. That is the same question submittal process new construction has to answer here.CONFIRM-WITH-LOCAL-BUILDING-CONTROL
Closing the submittal with a decision others can execute
A successful new construction submittal leaves no uncertainty about what was reviewed, which door set it covers or who accepted it. The package connects the product to the actual door, the claims to named evidence and the unresolved matters to accountable owners. The returned record then converts the discussion into a controlled instruction.
This overlaps with the earlier coverage in smart lock rfq guide for international buyers. That is the same question submittal process new construction has to answer here.If the answer is not yet ready, return the package with a precise status rather than a general request for clarification. If it is ready, approve only the identified revision and scope. Record the evidence, retain the conditions and route any later change back into the process.
For suppliers and project teams, the practical next step is to select one representative door set and test the package against the twelve-question worksheet. That exercise reveals which dimensions, documents, decisions and responsibilities are missing before the same gap reaches the full schedule. It also creates a reusable project record for installation, handover and later change control.
Ask for the offer against the same requirement: request a quote.

