Submittal process new construction: A clause-based guide to preparing, reviewing, revising and approving smart-lock submittals for new construction projects.

Publicat la: nov. 19, 2025

Submittal Process in New Construction

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 deliverablePrepared or confirmed byAccountable decision makerRequired record
Door schedule and design basisDesign teamProject specifierIssued design revision
Door-set fit informationSupplier, installer and door-set teamDoor-hardware specifierMarked-up submittal
Product and integration evidenceSupplierTechnical reviewerEvidence register
Egress, fire and access decisionsRelevant authority or consultantAuthority named by the projectDated approval or response
Submittal dispositionReview coordinatorProject specifierRecorded 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 itemReview questionFailure prevented
Door mark and opening referenceDoes the information match the issued door schedule?Review of the wrong door type
BacksetIs the distance from the door edge to the spindle or cylinder centre stated?Bore prepared in the wrong location
Bore diameterIs the required bore identified separately from the backset?Unprepared or incorrectly prepared door
Bolt-to-bore distanceIs the relationship between bolt and bore shown?Incorrect bolt engagement
Faceplate and strikeAre both closing-edge components identified as a matched arrangement?Door that closes but cannot be secured as intended
Leaf thickness and constructionAre the preparation assumptions stated for the actual door?Surface-mounted or concealed parts that do not fit
Finish referenceIs 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 partMinimum contentReviewer can test
Cover and transmittalProject, door marks, submission purpose, revision and requested decisionWhether the package has a defined review object
Door and lock drawingsPlan, elevation and detail views tied to the door scheduleWhether the proposed arrangement matches the design
Dimensional scheduleBackset, bore, bolt-to-bore, leaf thickness and faceplate informationWhether the installer can prepare the actual door
Product informationConfiguration, finishes, interfaces and components offered for the projectWhether the proposed item corresponds to the submitted doors
Evidence registerDocument title, revision, scope, issuer and project referenceWhether each claim is traceable
Installation informationPreparation, wiring or power requirements, setup and handover requirementsWhether the information can be coordinated
Exceptions and assumptionsUnresolved values, dependencies and actionsWhether anything is being mistaken for approved fact
Approval blockReview disposition, conditions, reviewer role and dateWhether 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 typeEvidence the reviewer should requestAcceptance test
Product configurationDated product information or project-specific scheduleDoes it identify the proposed configuration?
Installation requirementPreparation or wiring drawingCan the door and electrical teams work from it?
Functional behaviorTest record, procedure or technical description tied to the claimDoes the evidence cover the condition being relied upon?
Interface dependencyInterface statement and responsibility matrixAre the parties and limits clear?
FinishDated finish reference or approved sample recordCan the delivered finish be compared objectively?
Authority-related matterAuthority response or approval recordHas 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 gateCore questionOutput
IntakeIs the package complete enough to review without reconstruction?Accepted for review or returned as incomplete
Door-set reviewCan the proposed arrangement be checked against the actual door?Fit comments and unresolved dimensions
Evidence reviewDoes every relied-upon claim have traceable evidence?Accepted evidence or further request
Coordination reviewAre interfaces, power routes and responsibilities assigned?Coordination actions and owners
Authority reviewHas the relevant decision maker answered the project-specific question?Dated authority record
Final dispositionWhich 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 decisionSupplier responsibilitySpecifier responsibility
Door and frame arrangementExplain product preparation and fitDefine the project door set
Locking arrangement for each openingState the behavior of the proposed configurationEstablish the required arrangement
Escape-route operationDescribe how the proposed interface is intended to workObtain the required authority decision
Credential and access modelState the proposed method and dependenciesDefine project access intent
FinishProvide the available reference and limitationsEstablish the approved project finish
Service and maintenance pathExplain the physical access requiredEnsure 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 eventRequired recordResult
Initial packageTransmittal, issue date and full indexBaseline for review
Comment responseResponse matrix tied to comment numbersEvidence that the issue was addressed
Design revisionRevised drawing and schedule referencesNew review baseline where affected
Supplier resubmittalRevised package and superseded-item listClearer re-review scope
ClarificationQuestion, response and affected itemAvoids unnecessary full resubmittal
Partial approvalExplicitly identified door marks or sheetsPrevents 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 itemInformation in the submittalCoordinating partyClosure evidence
Door preparationPreparation drawing and dimensional scheduleInstaller and door-set teamConfirmed fabrication information
Frame and strikeFaceplate and strike arrangementDoor and frame teamApproved detail
Power and wiringRoute, connection point and dependencyElectrical teamCoordinated drawing
Access-control interfaceController, reader or exit-device relationshipSecurity or controls teamInterface responsibility record
Network positionDevice location and coverage dependencyNetwork designerCoverage or connection plan
Door scheduleFinal mark and hardware relationshipDesign teamIssued 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 questionEvidence to requestDecision record
Is the locking arrangement acceptable at this escape door?Response from the authority responsible for the project locationDated approval or conditions
Does an electronic component affect the fire-door assembly decision?Response from the fire authorityAssembly-specific decision
Is the operable approach suitable for the intended users?Response from the access consultant or client’s designated reviewerApproved operating arrangement
Which evidence must accompany the installed assembly?Project instruction from building controlHandover 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 typeExample formRequired follow-up
Verified project factDoor mark and dimension confirmed from the issued fabrication recordRetain the source reference
Supplier statementCapability described for a named configurationConfirm the statement for the proposed SKU and project scope
Design assumptionTemporary coordination value pending an updated door detailName the designer and required issue
Open decisionLocking arrangement awaiting the relevant authorityName the decision maker and required record
Client assumptionExpected service condition supplied by the clientPreserve 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

DispositionMeaningRelease rule
ApprovedThe named revision is accepted for the listed scopeRelease the approved revision
Approved subject to closureThe decision is positive but named evidence remains outstandingRelease only if the contract permits; close the condition before installation
Revise and resubmitMaterial information or evidence requires a new reviewHold the affected scope
Not approvedThe proposal does not meet the stated requirementResolve the identified issue before resubmittal
IncompleteThe package cannot enter technical reviewSupply 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 recordResponsible partyForm at handover
Approved submittal registerSpecifier or document controllerControlled schedule with revisions
Final door and hardware scheduleDesign teamIssued project drawing and schedule
Fabrication and preparation informationInstaller or door-set teamApproved shop or fabrication record
Authority decisionsResponding authority or project coordinatorDated response or certificate in the project record
Configuration and setup recordSupplier or commissioning teamProject-specific completion record
As-built changesDesign and construction teamUpdated drawing and schedule
Open-item dispositionProject decision makerClosure 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 questionEvidence checkedResult
Are the project, doors and requested decision identified?Transmittal and schedulePass or return
Is the package revision controlled?Revision registerPass or return
Can the lock be checked against the actual door?Dimensioned drawingsPass or comment
Are backset, bore and bolt-to-bore treated as separate dimensions?Preparation schedulePass or comment
Does every relied-upon claim point to evidence?Evidence registerPass or request
Are configuration, finish and interfaces tied to the proposed SKU?Product informationPass or request
Have unresolved assumptions been labelled?Exceptions schedulePass or return
Have the relevant authorities answered their project questions?Dated authority recordsPass or hold
Are construction dependencies assigned to coordinating parties?Coordination matrixPass or action
Are revision changes tied to previous comments?Revision historyPass or return
Is every approval condition measurable and owned?Disposition recordPass or hold
Is the final record suitable for procurement and handover?Controlled registerRelease 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.

Coșul dumneavoastră
Experiența dumneavoastră pe acest site va fi îmbunătățită dacă permiteți utilizarea cookie-urilor. Politica privind cookie-urile
Chat on WhatsApp