Submittal Process: How Suppliers Respond
The submittal process supplier response is the supplier’s controlled answer to a review request, not simply a brochure attached to an email. For a door-hardware consultant moving a project from awareness to evaluation, its purpose is to expose what is proposed, what evidence supports it, what remains unresolved, and who must make each decision. The package must serve three readers simultaneously: the client needs traceability, the installer needs usable door information, and the supplier needs an unambiguous record of what was submitted.
Direct answer. The one-line answer — submittal process supplier response is the working record for submittal process supplier response. submittal process supplier response is worthless until submittal-process is attached to it as evidence. A submittal process supplier response gives the specifier working documents. submittal process supplier response is the document that decides the requirement. That is what submittal process supplier response turns into.
submittal process supplier response is used here in the narrow sense set out in submittal process supplier response. It is a working definition built for submittal process supplier response. It is not a statutory one, and it has to be read against the market and product concerned.
- Frame the requirement — use a template that names the physical constraints in submittal process supplier response
- Catalogue the evidence — attach the conformity file for the SKU behind submittal-process
- Deliver it in one request — issue one complete package per door class, not one per query
- For submittal process supplier response, submittal process is what each step has to answer to.
A usable smart lock submittal therefore needs more than product claims. A supplier response log connects the request, the returned package, its revision, and the review outcome. Field evidence can also be carried by the Office Smart Lock Site Survey and the Smart Lock Retrofit Site Survey. Together, those documents should let the team evaluate the proposed lock without reconstructing the decision through repeated meetings.
The Supplier Response as a Controlled Review Object
A submittal request asks for defined information. A supplier response supplies that information in a form the reviewer can check. A separate review record then states what the reviewer decided. Keeping these three things distinct prevents an acknowledgment, a sales conversation, or a receipt email from being mistaken for approval.
This submittal-process sequence can be separated into components, each with its own owner and exit condition:
| Response component | Question it resolves | Minimum recorded output |
|---|---|---|
| Receipt and scope | What was requested, and which revision is being answered? | Named request, response revision, package owner |
| Product identity | Which exact SKU and configuration are under review? | SKU, dated product-page reference, options |
| Door-fit data | Can the proposed lock be checked against the actual door? | Relevant dimensions, hand, interfaces, door assumptions |
| Evidence | What documents support the submitted claims? | Document title, scope, holder, revision |
| Electronic interfaces | How will access, power, and door monitoring connect? | Named interfaces, requested evidence, unresolved points |
| Exceptions | Where does the proposal depart from the requested information? | Deviation schedule and explicit decision request |
| Closeout | What was approved, by whom, and under what conditions? | Dated review record and signed responsibilities |
The supplier owns the accuracy and completeness of the response package. The specifier owns the technical recommendation and records deviations. The client decides commercial and project priorities, while the relevant authority decides matters involving building control, fire behavior, or access obligations. A supplier cannot close those decisions merely by supplying a statement in its own format. The catalogue entry point for this is the smart door locks.
Receipt Control and the Supplier Response Log
The first component is administrative, but it prevents downstream confusion. The supplier response log should identify the request, the date received, the receiving channel, the supplier’s package owner, the response revision, the completeness status, the assigned reviewer, and the next recorded action. If the request has a revision number, the supplier must repeat that revision in the response. A response cannot quietly inherit the identifier of an earlier package.
Receipt acknowledgment should be limited to administrative facts: the package arrived, it is associated with the correct request, and a named person owns the next action. It should not state that the proposal is technically accepted, complies with project requirements, or is ready for purchase. Those are review conclusions, and they require a dated record.
The response log also makes revision control visible. Whenever information changes, the supplier should issue a new package revision, mark changed fields, and identify superseded pages. The reviewer then works from one defined revision rather than a folder containing a mixture of current and obsolete information. This discipline is particularly important where a product sheet, installation drawing, and interface description were issued at different times.
The Completeness Shell Before Technical Review
In a submittal process supplier response, the package shell establishes whether technical review can begin. It should contain a cover sheet, package index, stated scope, product and option identification, response-to-request matrix, drawings and data, evidence register, deviation schedule, and named contact. These items are not administrative decoration. They tell the reviewer where the answer to each question is located.
| Shell item | Reviewer test | Incomplete-response treatment |
|---|---|---|
| Cover sheet | Does it identify the request and response revision? | Return as incomplete |
| Package index | Can every attachment be located and distinguished? | Request a replacement index |
| Stated scope | Are included doors, options, and exclusions clear? | Request scope clarification |
| Response matrix | Is each request answered or expressly marked open? | List unanswered fields |
| Evidence register | Are source documents named and scoped? | Return unsupported claims for evidence |
| Deviation schedule | Are departures from the request visible? | Require an explicit exception response |
| Named owner | Is there a person accountable for the package? | Hold the package for administrative completion |
An incomplete package should come back with a precise list of missing or unusable fields. “More information required” is not enough. The recipient should identify which door, dimension, document, interface, or decision remains unresolved. This keeps the review moving without turning every omission into a new meeting.
The shell should also say what the package does not cover. A supplier may be reviewing only one lock configuration or one door type, while the request concerns a broader family. Stating that boundary early prevents an incomplete answer from being interpreted as a project-wide proposal.
Product Identity and Checkable Technical Data
The product data submittal is the working core of the response. It must identify the exact product, configuration, and dated source from which the information came. A family name or general platform description is not enough for procurement because the reviewer cannot determine which variant, option, or document revision is being considered.
The identity block should include the manufacturer’s SKU, the proposed configuration, handedness or handing where relevant, finish identifier, included components, excluded accessories, and the dated product-page reference. Where a specification depends on a model-level capability, confirm on the dated product page for the specific SKU. The supplier should also identify where the product page and submittal differ.
| Data category | What the response should carry | Failure that prevents evaluation |
|---|---|---|
| Identity | Exact SKU, configuration, option, source date | Product family name only |
| Mechanical form | Lock case, dimensions, hand, interfaces | Marketing description without dimensions |
| Finish | RAL or colour reference and surface description | Photograph without a finish identifier |
| Power | Intended supply arrangement and interface details | No response to the specified power condition |
| Credentials | Intended credential arrangement and evidence needed | Unsupported interoperability statement |
| Installation | Required conditions, clearances, and related documents | No way to compare the unit with the door |
| Limitations | Known exclusions and information still open | Exceptions concealed in general text |
The response should separate manufacturer data from project assumptions. For example, a dimension may be taken from the dated product data, while the door thickness or frame condition comes from the site record. The source of each value should remain identifiable. If a value depends on an option or a different door set, the supplier should state that dependency instead of presenting the value as unconditional.
The Door-Fit Module
A lock cannot be evaluated apart from the door set: the leaf, frame, hardware, and locks operate as one assembly. The supplier response should provide the dimensions an installer needs, in a stated unit and format, and identify which door and frame conditions the information assumes.
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, and a submittal that omits one of them cannot be checked. The response should also address the lock case arrangement: a mortise lock case sits inside the door, a rim lock has a surface-mounted case, and a multipoint arrangement operates several locking points through one gear.
| Door-fit field | Supplier responsibility | Reviewer comparison |
|---|---|---|
| Backset | State the measurement and source | Compare with the actual door edge and spindle position |
| Bore diameter | State whether the condition applies | Compare with existing or planned boring |
| Bolt-to-bore distance | Provide the relevant relationship | Check against the prepared opening |
| Faceplate | Identify form and fixing arrangement | Compare with the door edge and frame |
| Strike | Identify the counterpart | Check alignment and door-hand operation |
| Lock case | State mortise, rim, or multipoint arrangement | Compare with the door construction |
| Door condition | State thickness, hand, and relevant assumptions | Reconcile with site or survey information |
The Office Smart Lock Site Survey can establish the project-side door record, while the Smart Lock Retrofit Site Survey can capture an existing condition where the proposed lock must fit what is already installed. The supplier then has a defined basis for answering rather than guessing which condition the catalogue dimensions represent.
A mock-up or sample may evidence fit and finish under the conditions presented. It does not prove performance across the project. The review record should identify what the physical item demonstrated and what remained a documentary decision.
The Evidence Envelope
The evidence envelope answers a narrower question than the product narrative: what source supports each submitted claim? A usable reference names the document, its scope, its revision or date, and the holder of the underlying record. A generic statement that a product complies is not a reviewable evidence trail.
| Claim area | Preferred response | What the reviewer can then do |
|---|---|---|
| Mechanical data | Dated product data or drawing tied to the SKU | Compare values with the door record |
| Test evidence | Named report with tested configuration and scope | Judge whether the scope addresses the proposal |
| Installation | Published instruction set and identified revision | Check whether the assumptions match the project |
| Interface | Configuration guide or dated product-page reference | Identify what must be tested or confirmed |
| Authority decision | Written decision from the authority that owns it | Record the approving party and conditions |
| Sample or mock-up | Review record describing the conditions examined | Separate fit evidence from performance evidence |
Broader document expectations can be compared with Submittal Process: Documents a Specifier Should Demand. That article addresses the evidence set from the specifier’s side; the supplier’s responsibility here is to provide the same information with enough scope and ownership detail for a direct check.
Where an electronic lock forms part of an escape route, the response must identify the locking arrangement and the interface with panic hardware. The supplier should not imply that a component alone resolves the free-egress question.
CONFIRM-WITH-FIRE-AUTHORITY: Confirm which authority signs off on the locking arrangement for each escape-route door and what written evidence it requires.
Where a local building-control review is triggered by the proposed alteration, the response should identify the relevant decision path without predicting the outcome.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm which building-control authority applies, what it decides, and which document belongs in the project record.
Access, Power, and Door Interfaces
During the door hardware review, electronic functions should be translated into interface questions. The response should state what the proposed lock must exchange with the access system, what the controller must learn about the door, and what happens when normal power is unavailable.
Credential questions should include the intended credential arrangement, the controller relationship, configuration evidence, and whether the package is for one space or a wider system. Key-control questions should identify how the cylinders fit the client’s master key and hierarchical key-control plan, including any doors deliberately outside that system.
Line supervision tells the controller whether a door is open or closed. An egress interface tells the system that an exit device has been operated. These are different functions, and a response should not merge them into one general connectivity statement.
| Interface topic | Question for the supplier | Evidence to request |
|---|---|---|
| Credentials | Which credential arrangement is proposed? | Configuration or interface reference |
| Key control | How does the cylinder fit the key plan? | Cylinder and key-system schedule |
| Door monitoring | Which door states are reported? | Interface description tied to the SKU |
| Exit-device signal | How is operation of the exit device reported? | Named egress-interface evidence |
| Network protocol | Which protocol or interface applies to this SKU? | Dated source and configuration scope |
| Normal power | How is the lock supplied in normal operation? | Installation and power interface data |
| Power loss | Which state is intended for this door role? | Fail-safe or fail-secure decision record |
| Battery backup | How is continued operation supported? | Backup arrangement and monitoring scope |
The fail-safe or fail-secure choice belongs to the door’s role and the approved locking arrangement, not to the product by default. Battery backup should likewise be described as a project arrangement rather than an assumed product feature.
A description of a broader platform cannot stand in for SKU-level evidence.
Where operability or independent access is part of the project decision, the response should identify the proposed operable part and the evidence available for review.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm which access consultant or client authority determines the applicable operability criteria and what evidence must be recorded.
Finish and Mechanical Consistency
Finish approvals can fail late when the supplier and specifier are using different references. The response should provide the RAL or colour reference, the surface description, the components covered, and the dated source. A photograph shows the finish; it does not specify it.
The same rule applies to physical interfaces. If the response names a mortise or rim arrangement, multipoint operation, faceplate, or strike, those elements should match the mechanical data and the proposed door set. A finish sample can be approved against a written reference, but it should not silently become the reference itself.
| Interface | Response requirement | Reviewer action |
|---|---|---|
| Finish | RAL or colour reference plus surface description | Compare with the door and hardware schedule |
| Finish coverage | Identify lock, strike, and exposed components covered | Check that no visible item is omitted |
| Mock-up | Record the approved sample and reference used | Link the approval to a specific revision |
| Lock case | State form and configuration | Reconcile with the mechanical drawing |
| Faceplate and strike | Identify matching halves | Check door edge and closing geometry |
| Accessories | Identify finish and mechanical compatibility | Review as part of the complete door set |
The result should be one consistency check rather than separate decisions about colour, case, and strike that later conflict. Any unresolved item belongs in the deviation schedule.
Deviations, Substitutions, and Replacement Requests
A supplier response must say where it cannot meet the requested information or design. Silently changing a dimension, option, finish, interface, or included component creates a different proposal under the same revision number. The deviation schedule should identify the requested condition, the proposed condition, the reason supplied, the effect on the door set, and the decision required.
An or-equal is a request to substitute. The comparison belongs to the specifier, and the decision and its reasons should be recorded. A supplier may provide evidence for the proposed alternative, but it should not label that alternative approved.
| Response event | Supplier action | Reviewer decision | Required record |
|---|---|---|---|
| Information omitted | Return the missing field with an explanation | Incomplete or revise | Open item and response revision |
| Product option changed | Issue a marked deviation | Accept, reject, or request revision | Revised comparison |
| Substitution proposed | Provide like-for-like evidence | Decide whether the request is equal | Decision and reasons |
| Replacement requested | State why and identify every affected field | Compare against approved scope | Product replacement request |
| Evidence conflicts | Identify the conflicting documents and sources | Request corrected evidence | Conflict disposition |
| Authority decision pending | State what remains open and who must decide | Hold or escalate | Authority and evidence record |
A product replacement request should trigger a scoped delta rather than restart the review without control. The response should list changed and unchanged fields so the reviewer can see whether the replacement alters fit, interfaces, finish, documentation, or decisions already recorded.
Coordination between the proposing team and the manufacturer is particularly important when the request crosses disciplines. Submittal Process: Coordination Between Architect and Supplier provides the surrounding coordination view; the supplier response itself must still carry the technical delta and the requested decision.
Review Status, Signatures, and the Approval Record
A controlled response uses named statuses instead of informal labels such as “approved for now” or “subject to review.” The status tells every participant what may be relied upon and what action is required. A receipt does not approve a technical detail, and technical acceptance of one field does not approve the package.
| Status | Meaning | Next action |
|---|---|---|
| Received | Package is associated with the request | Log receipt and assign review |
| Incomplete | Required fields or documents are missing | Return a precise deficiency list |
| Under review | Package is complete enough for technical assessment | Record findings |
| Revise requested | Specific changes are required | Issue a new supplier revision |
| Approved as noted | Accepted subject to stated conditions | Record each condition and owner |
| Approved | Package accepted within its stated scope | Issue the approval record |
| Not approved | Proposal is outside the accepted scope | Record the reason and next decision |
The submittal approval record should identify the request and package revision, the reviewed door or product scope, the decisions made, unresolved conditions, the reviewer, the authority where applicable, and the date. It should also show which conditions were accepted by another participant and remain open elsewhere.
Responsibility should be visible within the record. The supplier package owner confirms the completeness and identity of what was submitted. The specifier records the technical review and recommendation. An authority records only the decision within its remit. The client can accept commercial or project conditions, but that acceptance should not rewrite a technical review that has not occurred.
The submittal is not approved until the review is recorded and dated. Until then, the package is evidence under review, not an authorization to proceed.
The Response Workflow and Its Stage Gates
The submittal process supplier response is not linear once exceptions arise. It moves through gates, and each gate has a different output: receipt, completeness, technical review, exception handling, and closeout. A revision can return the package to an earlier gate without erasing the history of what was reviewed.
flowchart TD
R[Receive named request] --> L[Log receipt and revision]
L --> C[Check package completeness]
C -->|Complete| E[Review product and door data]
C -->|Missing| X[Return incomplete response]
X --> L
E --> A[Review evidence and exceptions]
A --> D[Record decision or revision request]
D -->|Revise| L
D -->|Approve| F[Issue dated approval record]
| Stage | Required input | Output | Exit condition |
|---|---|---|---|
| Receipt | Named request and response package | Log entry | Ownership and revision confirmed |
| Completeness | Package shell and index | Status and deficiency list | All required fields are present or expressly open |
| Technical review | Identity, data, evidence, and exceptions | Findings by subject | Each proposed condition has been checked |
| Exception handling | Marked deviation or replacement request | Decision, condition, or revision request | Responsible decision maker is identified |
| Closeout | Completed findings | Dated approval record | Scope, conditions, and responsibilities are recorded |
The stage-gate model protects the schedule from false progress. A supplier cannot close a field by promising to investigate it, and a reviewer cannot approve an exception by relying on an earlier email. Each move to the next stage is visible in the record.
Exceptions That Require a Controlled Reply
Exceptions are not necessarily failures. They become failures when they are allowed to remain implicit. The supplier response should identify the condition, its source, the affected requirement, the party who can decide it, and the evidence required to close it.
| Exception | Required reply | Reviewer treatment |
|---|---|---|
| Incomplete dimensional set | Supply the missing field and its source | Keep package incomplete |
| Conflicting product revisions | State which revision governs | Review only the identified revision |
| Door data conflicts with assumptions | List each conflicting condition | Hold the fit decision |
| Evidence does not match configuration | Explain scope or provide corrected evidence | Return the affected claim |
| New configuration appears mid-review | Issue a full delta and revision | Recheck changed fields |
| Authority decision is pending | Name the authority and outstanding question | Hold the related approval |
| Sample is offered as proof | State exactly what was examined | Do not infer performance |
| Open project assumption remains | Identify owner and decision method | Record as a condition, not an approval |
A useful exception response is specific enough to close without another meeting. “Consult the factory” identifies an action but not an owner or output. “Door thickness is not stated in the current product data; the package requires the field survey value before fit can be checked” states the gap, its effect, and the next evidence.
The same discipline applies when the supplier learns new information after submission. A replacement request, correction, or additional document should identify the revision it changes and which prior conclusions remain valid.
A Working Supplier Response Template
The template should collect information in review order rather than mirror the supplier’s internal folders. It begins with identity and scope, moves through product data, door fit, interfaces, and evidence, then ends with exceptions and signatures. This order helps the specifier compare packages consistently.
| Template field | Supplier wording | Reviewer use |
|---|---|---|
| Request reference | Name the request and revision answered | Connects package to project record |
| Product identity | State exact SKU, configuration, and dated source | Establishes what is under review |
| Response scope | Identify included doors, options, and exclusions | Defines the review boundary |
| Product data | Attach dimensions, functions, finish, and interfaces | Supports technical comparison |
| Door-fit data | State source, unit, and assumptions | Checks the proposed door set |
| Evidence register | List document, scope, date, and holder | Enables direct inspection |
| Interface response | Answer power, credential, monitoring, and signal questions | Checks system relationships |
| Deviation schedule | Mark every departure or unresolved field | Prevents silent scope change |
| Product replacement request | State changes, unchanged fields, and reasons | Enables controlled delta review |
| Package owner | Name the person responsible for accuracy | Provides an escalation route |
| Review disposition | Select status and attach decision record | Closes the request visibly |
A short cover note can direct the reviewer without repeating the package. It should identify the response revision, list open items, state whether the package replaces an earlier response, and name any decision required from the specifier. It should not contain unsupported capability statements or informal approval language.
The template is a transmission control, not a substitute for technical judgment. Fields remain empty only when the reason is stated and the responsible decision maker is identified. Every open item must carry the same discipline as a completed answer.
Evaluation-Stage Decision Rules for the Consultant
At the awareness-to-evaluation stage, the consultant’s task is to decide whether the proposal is ready for deeper project evaluation, not to approve every product detail immediately. The supplier response is ready for evaluation when it is complete enough to compare, specific enough to check, and traceable enough to revise.
| Evaluation gate | Pass condition | Action if it fails |
|---|---|---|
| Identity | Exact product and source are identifiable | Return for clarification |
| Completeness | Required fields are answered or expressly open | Record an incomplete status |
| Fit | Door assumptions can be compared with project data | Hold the fit recommendation |
| Evidence | Each material claim has a named source | Request supporting evidence |
| Interfaces | Relationships and responsibilities are visible | Assign technical questions |
| Exceptions | Deviations have owners and decision paths | Record conditions or revise |
| Record | Decision, conditions, and revision can be traced | Issue no approval record |
The final recommendation can then separate what is accepted, what remains conditional, and what belongs to another authority. This avoids turning a project team’s general enthusiasm into an implied technical approval. It also preserves the ability to explain later why a supplier response was accepted within one scope but not another.
A practical assessment aid is the Submittal Process: Reviewer Checklist. Use it to verify the record independently of any verbal discussion. The supplier owns the submitted evidence; the consultant owns the quality of the review record.
Before a package advances, ask the supplier to fill the same response fields, identify every revision, and close or assign each open item. When those conditions are met, the supplier response becomes a usable project record rather than a collection of attachments. That record gives the client a defensible decision, gives the installer a clear interface, and gives the supplier an exact statement of what was accepted.
When the file is ready, request a quote against the written requirement.

