Writing the Fire Door Assembly Into a Smart Lock RFQ: Clause Language that Gets Real Answers
An nfpa 80 smart lock rfq clause earns its place when it tells bidders exactly what evidence must follow a proposed lock into a fire-door opening. The clause should not treat a product page, test report, or site approval as interchangeable. It should identify the door and hardware boundary, define the criteria register, separate document types, and assign responsibility for each interface. This approach turns a broad request for a compliant smart lock into an answerable procurement qualification package.
Direct answer. Condensed to the essential point, nfpa 80 smart lock rfq clause turns a request into a decision record. nfpa 80 smart lock rfq clause and nfpa-80 are the two parts of nfpa 80 smart lock rfq clause most often skipped. A nfpa 80 smart lock rfq clause separates what a supplier can show from what only a body can confirm. nfpa 80 smart lock rfq clause is where the two columns start. Each nfpa 80 smart lock rfq clause claim names its document.
The phrase nfpa 80 smart lock rfq clause is anchored in nfpa 80 smart lock rfq clause. For the rest of this article it denotes the conditions and evidence that nfpa 80 smart lock rfq clause sets out below. Nothing wider than that.
- What the maker can evidence — supplier declarations and drawings for nfpa 80 smart lock rfq clause
- What a third party must attest — third-party certificates covering the exact scope of nfpa-80
- What to ask for — the document set that matches the SKU behind nfpa 80 smart lock rfq clause
- Treat this as the nfpa 80 smart lock rfq clause sequence, with nfpa 80 as the reference.
Name the opening before naming the lock
The first line of the smart lock RFQ should identify the opening, its intended function, and the components included in the proposed assembly. A lock model alone leaves too much unanswered. The reader cannot tell which door construction, frame, closer, latch, strike, hold-open arrangement, access-control equipment, power source, or existing hardware will interact with the proposed device. The catalogue entry point for this is the smart door locks.
The clause should distinguish components supplied with the lock from components that remain on the project. That boundary controls who investigates compatibility, supplies interface information, performs the work, and retains the supporting record.
Clause 1.1 — Defined assembly. The requirement applies to opening [opening identifier] and the complete set of permanently installed door, frame, fire-door hardware, electrified access-control, power, communications, and monitoring components that the bidder proposes to use. The bidder shall identify every included component, every excluded component, and the party responsible for each excluded interface. No component shall be treated as included solely because it is referenced in another project document.
| Boundary item | Information required by the RFQ | Required bidder response |
|---|---|---|
| Door and frame | Opening identifier, project criteria, construction type, condition | Proposed configuration and unresolved field conditions |
| Fire-door hardware | Existing and proposed latches, strikes, hinges, closer, hold-open arrangement and related controls | Compatibility statement, evidence reference and responsible installer |
| Electrified access-control layer | Lock, controller, power supply, credential device, monitoring and exit interfaces | Complete bill of functions with model and variant references |
| Power and communications | Source, routing, backup arrangement and connection points | Interface schedule and named responsibility for each service |
| Installation and maintenance records | Required instructions, inspections, testing and record retention | Document owner, submission point and proposed record location |
A simple qualification workflow prevents bidders from answering different questions:
flowchart TD
A[Define opening boundary] --> B[Identify included hardware]
B --> C[Map criteria to components]
C --> D[Request evidence by document type]
D --> E[Assign interface duties]
E --> F[Record open exceptions]
F --> G[Release qualification package]
The diagram is not a compliance decision tree. It is a drafting control that shows where a response can become incomplete. If a bidder cannot identify the boundary, the missing information cannot be evaluated.
CONFIRM-WITH-LOCAL-ASSEMBLY-OWNER: Confirm the named opening, its project criteria, and which components belong to the assembly before the RFQ is issued.
Build a criteria register instead of stacking standards
A fire-door smart-lock requirement can draw on several standards, but each standard answers a different question. The RFQ should present these scopes separately. This prevents a response to one question from being used as apparent evidence for another.
The clause should cite the current edition of NFPA 80 and route clause-level requirements to the published standard text. If the project has adopted a particular edition, addendum, interpretation, or authority decision, state that separately. Do not imply that a general reference to the current edition settles which requirements apply to a particular opening.
| Criterion | Scope to identify in the RFQ | Question it can answer |
|---|---|---|
| Current edition of NFPA 80 | Installation and maintenance rules for fire-door hardware | What project rules apply to the complete opening and its hardware? |
| ANSI/BHMA A156.25 | Electrified locking devices whose electrical function is not covered elsewhere | What lock-level cycling, operation, strength and environmental evidence is relevant? |
| UL 1034 | Electrically controlled locks for door openings | What lock-level electrical safety and performance evidence is relevant? |
| NFPA 101 | Egress and locking arrangements for occupancies | What project criteria govern the intended egress arrangement? |
| ADA / ANSI A117.1 | Accessible operation, including operable-part and force requirements | What accessibility criteria apply to the proposed operating method? |
These are scope prompts, not a direction to combine every row into one product claim. The published title, edition and project applicability must be checked before the RFQ relies on a criterion.
Clause 2.1 — Criteria register. The RFQ shall cite the current edition of NFPA 80 separately from any project-adopted edition. Each bidder response shall identify the published designation, edition, scope relied upon, project criterion, and evidence document for every criterion claimed applicable. A response concerning one criterion shall not be used as evidence for another criterion unless the bidder explains the documented relationship and the receiving authority accepts it in writing.
This approach also improves clarification. A bidder can say that one report addresses lock performance while another document addresses installation instructions or the project’s fire-door criteria. The reviewer can then request the missing item without rejecting an otherwise responsive submission.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the governing authority, project-adopted editions, and any approval path that applies to the specified opening before issuing the criteria register.
Separate the four evidence documents
Procurement teams often receive a folder containing a brochure, a declaration, a test report and a product label, then treat the folder as one approval. A fire-door hardware RFQ should name the document type it expects. The same product can generate very different evidence depending on what was tested, who issued the document and what variant it covered.
| Document type | What it establishes | Information the RFQ should request |
|---|---|---|
| Test report | Someone tested a defined sample against stated requirements | Laboratory, report number, issue date, sample identification, tested standard and edition, results |
| Certificate | A named body attests conformity within a defined scope | Issuer, certificate number, scope, covered product or variant, issue and validity information |
| Declaration of conformity | The manufacturer or importer makes its own legal claim | Declarant, date, signature, exact product identification, applicable legislation or standard and supporting references |
| Product or label marking | A regulatory or market-access mark appears on the product or label | Exact mark, location, model coverage and the document that explains the marking |
A certificate is not the same as a test report. A declaration is not the same as a third-party certificate. Marking is not an assembly approval. Use The evidence-quality ladder for nfpa 80 smart lock rfq clause runs:
| Evidence rung | Procurement treatment |
|---|---|
| marketing image | Evidence for nfpa 80 smart lock rfq clause (nfpa 80) |
| declaration of conformity | Accept only where the project explicitly permits self-declaration and the declaration meets the required fields |
| test report on a sample | Review sample identity, test scope and whether the proposed configuration matches |
| scoped third-party certificate | Verify the named scope, validity information and covered variant |
| certificate covering the exact SKU or variant | Match every commercial identifier and configuration option before acceptance |
| ongoing production-control evidence that survives the sample test | Request where continued production consistency or ongoing certificate validity matters to the buyer |
Clause 3.1 — Document schedule. Evidence shall be submitted by document type. For every claimed conformity, the bidder shall identify the supporting document, issuer, number where applicable, issue date, tested or certified sample, covered product and variant, published criteria, scope, and any limitation. A product-page image, declaration, certificate, test report and product marking shall be listed separately and shall not be substituted for one another.
This schedule creates a useful early warning. If a report names a sample configuration that differs from the offered lock, the question can be resolved before installation. If a certificate covers a family but excludes the proposed option, that boundary must be visible. If evidence has no number, date or named issuer, the buyer can request more information without implying that the document is valid for the complete opening.
CONFIRM-WITH-LOCAL-SUPPLIER-EVIDENCE: Confirm that every document relied upon has a named issuer, scope, date, and model or assembly coverage relevant to the purchase.
Map evidence to the exact offered configuration
The strongest report cannot answer for a different door, hardware set or commercial variant. The RFQ therefore needs an identity matrix that connects the offered product to the evidence. This is particularly important when a supplier offers several finishes, electrical options, control boards, lever sets, strike arrangements, radio configurations or mounting variants.
Avoid transcribing specifications from memory or from an undated catalogue. Any dimension, electrical rating, reading range, cycle figure, power characteristic or battery-life statement used for selection should be checked against the dated product page for the specific SKU. The clause can require that check without turning a product-page value into independent conformity evidence.
| Identity field | Required detail | Evidence linkage |
|---|---|---|
| Commercial model and variant | Full offered identifier, option set and finish | Match to every report, certificate and declaration |
| Hardware revision | Lock body, control, latch, strike and mounting revisions where applicable | Explain any difference from the tested or certified sample |
| Door interface | Door thickness, handing, stile condition, frame and hardware arrangement | Identify the field verification and installation record |
| Electrical and control configuration | Power source, input requirements, control inputs and monitoring connections | Link to applicable lock-level and project interface evidence |
| Certificate or marking coverage | Exact identifiers listed in the document | Record any exclusions, family relationships or unresolved differences |
Clause 4.1 — Configuration and evidence map. The bidder shall complete an identity matrix that maps the exact offered model, variant and hardware revisions to the documents submitted. Every difference between the offered configuration and the sample, product or family named in an evidence document shall be listed. Unmapped differences shall be treated as open exceptions and shall not be answered by a general statement that the product is certified or approved.
The limits of a product standard and the limits of an assembly claim are different. NFPA 80 for Smart Locks: Scope, Tests and What the Standard Never Proves provides a useful scope check, while Reading an NFPA 80 Test Report Page by Page: A Smart Lock Buyer Walkthrough helps reviewers match the report’s sample, criteria and results. Neither document should be asked to perform the role of an opening-specific approval.
CONFIRM-WITH-LOCAL-SUPPLIER-DOCUMENT-OWNER: Confirm the exact offered variant and that the referenced evidence identifies the same or a demonstrably equivalent configuration before the response is accepted.
Give every interface an owner and evidence request
The lock is only one part of an electrified opening. A useful clause asks how the proposed device fits the project’s door-control, power, monitoring and access-control arrangements. It should request drawings and responsibility statements rather than assume that a product-level document resolves an interface.
The interface schedule should cover normal operation and the project-defined abnormal conditions. Depending on the opening, those conditions may include egress, fire-protection signalling, loss of power, loss of communications, door position, forced-door status and manual operation. The RFQ should ask the bidder and other responsible parties to identify which scenarios apply, how each component behaves, and who approves the sequence.
| Interface | Evidence to request | Responsibility statement required |
|---|---|---|
| Mechanical fit and latching | Door, frame, latch, strike, closer and hardware interaction information | Party responsible for field verification, preparation and installation |
| Electrical supply | Input, distribution, protection, backup and connection details | Party supplying, routing, commissioning and documenting power |
| Fire-door control sequence | Project-specific sequence diagram and approved procedure | Party responsible for integration, verification and operating instructions |
| Access-control interface | Controller, credential device, monitoring and control signals | Party responsible for configuration, testing and event handling |
| Maintenance and inspection | Instruction set, check points, record form and escalation route | Party responsible for performing and retaining the records |
Clause 5.1 — Interface schedule. The bidder shall submit a project-specific interface schedule naming each interacting component, its function, physical or logical connection, power source where relevant, operating sequence, verification method, required record and responsible party. The schedule shall address normal operation, egress where applicable, project-defined signalling conditions, loss of power and loss of communications. The interface schedule shall supplement and shall not replace product evidence.
Ask for the document that establishes each interface rather than accepting a supplier assertion that the equipment is compatible. Drawings, configuration records, test results and operating instructions may answer different parts. The clause should also state who owns the final integrated result. That avoids a gap where each supplier has supplied its own evidence but no party has accepted the complete interface.
CONFIRM-WITH-LOCAL-FIRE-DOOR-INTEGRATOR: Confirm which party designs, tests, approves, installs and maintains each project-specific interface before a response is treated as complete.
Make retrofit conditions part of the response
An nfpa 80 smart lock rfq clause should distinguish a new opening from a retrofit proposal. Existing doors can contain concealed conditions, incomplete records, prior modifications and hardware arrangements that cannot be understood from a catalogue selection. A field survey is not a substitute for project approval, but it is the proper place to identify what must be verified.
Clause 6.1 — Existing-opening qualification. For a retrofit, the bidder shall identify the existing opening, available records, observed door and hardware conditions, proposed removals or additions, field measurements, concealed-condition assumptions, resulting configuration and each party responsible for verification. Any condition that cannot be confirmed before pricing shall be listed as an explicit exclusion or clarification item.
| Qualification item | New opening | Retrofit opening |
|---|---|---|
| Opening identity | Project drawing and component schedule | Project drawing, physical identifier and available installation record |
| Field condition | Manufacturer or contractor data, subject to project verification | Recorded survey conditions and identified unknowns |
| Interface evidence | Proposed component and connection data | Existing-to-proposed interface and modification details |
| Final record | Installation, configuration and acceptance documents | Updated records reflecting what was actually installed |
| Open exceptions | Unresolved design or supply items | Unknown concealed conditions and change-dependent items |
The Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey provide useful field checklists for separating observed facts from assumptions. For deeper design consequences, NFPA 80 When Retrofitting Smart Locks Onto Existing Doors examines the retrofit-specific decisions that a fire-door hardware RFQ should expose.
A fire-door hardware RFQ should not hide the condition survey inside a general installation scope. The bidder needs to know which observations are required for the offer, which are required before installation, and which changes could reopen the technical response.
CONFIRM-WITH-LOCAL-RETROFIT-OWNER: Confirm field conditions, modification limits and approval requirements for the actual opening before accepting a retrofit proposal.
Require a structured bidder response matrix
Procurement qualification is easier when every bidder answers the same questions in the same order. A blanket yes or no to “comply with NFPA 80” creates ambiguity because it may refer to a test report, a product scope, installation instructions or an opening approval. The response matrix should make the basis of every answer visible.
Clause 7.1 — Mandatory response matrix. Each bidder shall complete every row of the conformity evidence schedule. A statement of compliance shall identify the precise document, section or record relied upon. Where the bidder cannot provide the requested evidence, the response shall state the gap, its effect on the proposed scope, the proposed resolution and the party responsible. Blank cells, unqualified statements of compliance and deferred attachments shall not constitute a complete response.
| Reference | Mandatory bidder question | Required attachment | Answer quality check |
|---|---|---|---|
| R1 | Which opening and components are included? | Annotated assembly description | Every boundary item is named |
| R2 | Which criteria and editions are relied upon? | Criteria register | Scope matches the cited document |
| R3 | Which document supports each claim? | Evidence index | Type, issuer, number and date are present |
| R4 | Which exact variant was tested or covered? | Identity matrix | Offered configuration matches the evidence |
| R5 | How does the lock interface with project systems? | Interface schedule | Every interface has an owner |
| R6 | How will installation and verification be documented? | Procedure and record plan | Required records and holders are named |
| R7 | Which project approvals or decisions remain open? | Approval register | Authority and evidence need are identified |
| R8 | What assumptions, exclusions and deviations apply? | Exception schedule | Each item has a disposition request |
Include the matrix in the RFQ rather than asking bidders to reconstruct it from narrative answers. It also creates a better clarification process. The buyer can ask for one missing attachment, update one row and preserve a clear audit trail. A bidder may then quote the matrix during design development without relying on an informal email summary.
For procurement qualification, the objective is not to create a large folder. It is to establish that each requested claim has a traceable answer and each unresolved issue has an owner.
CONFIRM-WITH-LOCAL-BID-CLARIFICATION-OWNER: Confirm who may issue and accept written clarifications, deviations and release decisions for this procurement.
Give deviations and commercial terms separate schedules
A technically acceptable alternative should not be rejected merely because it differs from the proposed configuration, but it should not be treated as equivalent without evidence. The RFQ needs an exception process that records the proposed change, its effect on the opening, the evidence needed to evaluate it and the party that will accept it.
Clause 8.1 — Exceptions and deviations. Any departure from the stated opening, component schedule, evidence assumption, interface allocation or response requirement shall be listed in an exception schedule. The schedule shall identify the affected criterion, proposed alternative, supporting evidence, unresolved risk and requested disposition. No alternative shall be treated as accepted unless the party with written authority accepts it for the identified opening.
| Schedule | Purpose | Rule for the bidder |
|---|---|---|
| Conformity evidence schedule | Maps criteria, documents, samples and covered configurations | Every claimed conformity receives a documentary reference |
| Technical submittal schedule | Tracks drawings, procedures, interfaces, exceptions and approvals | A submittal is identified by opening, revision, date and owner |
| Commercial response schedule | Carries separate commercial terms and bidder qualifications | It does not replace or qualify the technical evidence schedule |
Keep the schedules operationally distinct. A commercial commitment can describe what a bidder will supply or price, but it cannot convert a missing test report into evidence or make a technical assumption binding. Conversely, a technical matrix should remain usable even if the project changes the commercial package.
The exception schedule should be read at the same stage as the response matrix. Closing a commercial line while leaving an unresolved fire-door hardware interface can give a misleading impression of readiness. Conversely, documenting a manageable field verification does not automatically make the assembly acceptable; the authorised reviewer still has to decide.
CONFIRM-WITH-LOCAL-ACCEPTANCE-OWNER: Confirm who has authority to accept a proposed alternative and what evidence must accompany that acceptance.
Apply an opening-specific release gate
Before the RFQ is issued, test the clause against a hypothetical response. Ask reviewers to point to the evidence that supports each answer. If two reviewers interpret the same row differently, the wording needs revision. The release checklist below turns that test into a repeatable quality-control step.
| Release check | Pass condition |
|---|---|
| Assembly boundary | Each opening, component and excluded interface is identified |
| Criteria register | Each cited standard has a defined scope, edition route and applicability question |
| Document separation | Test report, certificate, declaration and marking are requested separately |
| Configuration mapping | Offered models, variants and revisions connect to named evidence |
| Interface ownership | Every physical, electrical, control and maintenance interface has an owner |
| Retrofit treatment | Field observations, assumptions and change-dependent items are visible |
| Exception control | Every deviation names the evidence and approval needed |
| Response control | The bidder must complete the same matrix and schedule structure |
Clause 9.1 — Procurement qualification release. The RFQ shall not be released until the assembly boundary, criteria register, evidence-document schedule, configuration map, interface responsibility schedule and exception process have been reviewed for the identified project. Each review shall record the reviewer, project opening, applicable project documents, unresolved qualification items and the party responsible for closure. Release of the RFQ confirms that the procurement is answerable; it does not establish approval of a future product or installation.
This is the distinction that makes assembly-level approval usable. The RFQ controls the quality of the answer, while the opening-specific evidence and authorized acceptance control the decision about the proposed configuration. NFPA 80 in a Smart Lock Tender Pack: The Evidence Checklist can be used to translate the response matrix into a tender submittal register without mixing the two purposes.
Readers comparing approaches usually start with the digital smart lock price. That is the same question nfpa 80 smart lock rfq clause has to answer here.Release the RFQ when a bidder can trace every technical answer to named evidence, every evidence item to the offered configuration, and every open issue to a responsible decision-maker. That structure gives procurement a defensible qualification package and gives suppliers a clear route to respond without guessing which document, assembly boundary or approval the buyer means.
CONFIRM-WITH-LOCAL-FINAL-REVIEW: Confirm the final opening-specific approval record and the edition of every cited criterion before procurement qualification release.
The requirement is ready for request a quote once it is written down.

