En 14637 smart lock RFQ clause: build qualification-ready RFQ clauses that separate smart-lock scope from fire-door hold-open evidence before comparing.

Posted At: Mar 11, 2026

Buying Against the Hold-Open on a Fire Door: RFQ Clause Language that Survives Comparison

Buying Against the Hold-Open on a Fire Door: RFQ Clause Language that Survives Comparison

Runbook objective: qualify the function before comparing the lock

En 14637 smart lock rfq clause is the subject of this piece, and every claim below is written so a buyer can check it. This runbook treats “buying against the hold-open” as adding or comparing smart-lock access functions at a fire or smoke door assembly where an electrically controlled hold-open arrangement may also be present. It does not treat the lock as a substitute for that arrangement. The qualification task is to state the proposed scope, supporting evidence and operating ownership before quotations are compared.

Direct answer. The one-line answer — en 14637 smart lock rfq clause is the working record for en 14637 smart lock rfq clause. en 14637 smart lock rfq clause is worthless until en-14637 is attached to it as evidence. an en 14637 smart lock rfq clause works as a two-column evidence test. en 14637 smart lock rfq clause names the documents. Each column of en 14637 smart lock rfq clause closes with a paper.

en 14637 smart lock rfq clause is used here in the narrow sense set out in en 14637 smart lock rfq clause. It is a working definition built for en 14637 smart lock rfq clause. It is not a statutory one, and it has to be read against the market and product concerned.

The en 14637 smart lock rfq clause is a document-control instruction, not a marketing label. The current edition of EN 14637 concerns electrically controlled hold-open systems for fire and smoke door assemblies. Its scope covers requirements, tests, application and maintenance, including interface expectations involving fire detection or alarm systems and mains-powered arrangements. Non-fire doors and battery-only systems are outside its own scope statement. The catalogue side of this is the smart door locks.

Confirm the published title and scope of the current edition before applying any clause. A standard describes what the standard tests; it does not establish that the site is certified. Nor can EN 14637 convert unrelated lock testing into fire-door evidence. Where fire-resistance performance is in scope, EN 1634-1 evaluates hardware as part of the door assembly rather than as a standalone lock.

The broader technical boundary appears in EN 14637 for Smart Locks: Scope, Tests and What the Standard Never Proves. Use that boundary to decide which questions belong in this RFQ and which must be referred to another standard, supplier discipline or project specialist.

Qualification tag: en-14637.

CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the applicable editions, assembly scope, evidence acceptance route and approving authority for the delivery jurisdiction.

Qualification route map: five gates from RFQ issue to release

Run each RFQ through five qualification gates. Do not let a polished response jump directly to commercial comparison because it contains a familiar standard reference. The release record must identify which function was tested, which document supports it and who owns the interfaces.

GateQualification ownerRequired release recordStop condition
Q1 ScopeProcurement ManagerDoor, function and proposed-component scope logThe offered function remains ambiguous
Q2 EvidenceCompliance reviewerDocument-type inventory tied to each claim“Certified” or “compliant” is the only evidence description
Q3 BindingTechnical reviewerExact model, variant, configuration and interface mapEvidence cannot be mapped to what is offered
Q4 ComparisonCategory ManagerLike-for-like comparison sheetDifferent functions or evidence levels are scored together
Q5 HandoffOperations representativeMaintenance, inspection and responsibility scheduleNo operating owner accepts the system obligations
flowchart TD
  A[Open qualification ticket] --> B[Freeze door and function scope]
  B --> C[Separate evidence document types]
  C --> D[Map exact variant and interfaces]
  D --> E{Evidence supports stated function?}
  E -->|Mismatch| F[Hold and request clarification]
  E -->|Confirmed| G[Compare like for like]
  G --> H[Release qualification record]
  F --> B

The operator rule is simple: a missing answer creates a status, not an assumption. Mark it CLARIFY, UNVERIFIED or NOT CLAIMED. Do not convert any of those statuses into a compliant response during table consolidation.

Q1 scope gate: freeze the assembly, function and interfaces

Request a controlled description before asking for evidence. It should identify the door assembly, intended use, existing door controls, proposed smart-lock function, power arrangement and every connection to fire detection or alarm systems. If the work is a retrofit, record what is being retained rather than assuming the existing installation has been assessed. The Smart Lock Retrofit Site Survey can support field capture, but survey data is not conformity evidence.

Ask the supplier to classify each proposed function against the published scope of the relevant current edition. Keep lock performance, hold-open control, fire-resistance performance, radio or electromagnetic compatibility, and electrical safety as separate questions. One document should not be asked to answer all of them.

Procurement questionScope to checkTreatment in the RFQ
Does the smart lock provide the proposed electromechanical locking function?Current edition of EN 14846, with its published title and scopeRequire lock-performance evidence under the standard actually claimed
Is a device an electrically powered hold-open arrangement for a swing door?Current edition of EN 1155Establish the boundary; do not treat it as the fire and smoke assembly scope
Is the device a manually powered controlled door closer?Current edition of EN 1154Keep manual closing and electrical hold-open functions separate
Is the arrangement an electrically controlled hold-open system for a fire or smoke door assembly?Current edition of EN 14637Require scope classification, interfaces, tests and maintenance evidence
Does the claim concern fire-resistance performance of the door assembly?Current edition of EN 1634-1Require assembly-bound evidence rather than a lock-only substitution

A supplier may answer “yes” to several rows, but each answer needs its own evidence trail. The table is a routing tool, not a compliance matrix. See EN 14637 When Retrofitting Smart Locks Onto Existing Doors for the retrofit decision path.

CONFIRM-WITH-LOCAL-AUTHORITY: Confirm which authority or appointed reviewer accepts the door-assembly description and the applicable standards route for this project.

Q2 evidence gate: name the document before accepting the claim

Procurement teams often receive a PDF, an image or a declaration and describe all three as a certificate. Require the supplier to name the document type before the document is assessed. The evidence then enters the comparison sheet at its actual level rather than at the level implied by marketing language.

Document typeWhat it isWhat it can supportCommon defect at RFQ stage
Marketing imageA visual product claimIdentification of a claim to investigateEvidence for en 14637 smart lock rfq clause (en 14637)
Test reportResults from testing a sampleThe method, sample and result actually reportedSample or configuration is not mapped to the offer
CertificateA body’s attestation, with stated scope and validityOnly the conformity stated within its scopeNumber, scope, validity or covered variant is missing
Self-declared DoCThe manufacturer or importer’s own dated and signed legal claimThe declaration made by that partySignature, date, responsible party or cited evidence is absent
MarkingA mark printed on a product or labelIdentification of the marking shownTreated as proof of the entire underlying claim

Use marketing image → declaration of conformity → test report on a sample → scoped third-party certificate → certificate covering the exact SKU/variant ordered → production-control evidence that keeps the certificate valid after the sample passed you are buying→audit or production-control evidence that keeps it valid after the sample passed`. A response that stops at an early rung has not demonstrated the later rungs. For en 14637 smart lock rfq clause, the position on this ladder is what the purchase decision turns on.

The rungs that decide en 14637 smart lock rfq clause are the ones issued under en 14637; a file for a different scheme does not move the position on this ladder.

For report review, use Reading an EN 14637 Test Report Page by Page: A Smart Lock Buyer Walkthrough. The operational outcome of this gate is not a broad assurance statement. It is a traceable line from each claim to one named document and one checked scope statement.

CONFIRM-WITH-LOCAL-LEGAL-REVIEW: Confirm which declarations, certificates, markings and contractual evidence statements the importer, manufacturer and delivery jurisdiction may lawfully rely upon.

Q3 drafting gate: mandatory response clauses for the fire

The fire door smart lock RFQ should separate scope, evidence and responsibility before technical or commercial comparison begins. Draft each clause as a supplier obligation with a defined response field and evidence attachment key. Replace square-bracket placeholders before issue; do not leave the commercial fallback to the supplier’s discretion.

  1. Classification of the offered scope. The Supplier shall classify every offered item against the published title and scope of the current edition of EN 14637. The response shall identify whether the item forms part of an electrically controlled hold-open system for a fire or smoke door assembly, is a separate component, or lies outside the standard’s scope. “Relevant to the project” is not an acceptable classification.

  2. Component and interface schedule. The Supplier shall provide a schedule naming the door assembly, hold-open device, smart-lock or access-control equipment, power arrangement and connection to fire detection or alarm systems. For each interface, the schedule shall identify the supplied scope, evidence offered, commissioning party and design responsibility. One component’s test result shall not be presented as covering another component.

  3. Evidence taxonomy. For every compliance claim, the Supplier shall identify the supporting document as a test report, certificate, declaration of conformity or marking. A test report shall state the sample tested and result; a certificate shall state its issuing body, verifiable number, scope and validity; a declaration shall be signed and dated; and marking evidence shall identify where the marking appears. Marketing images shall be listed separately. For en 14637 smart lock rfq clause, the position on this ladder is what the purchase decision turns on.

  4. Binding to the offered configuration. The Supplier shall map every test report and certificate to the exact offered model, variant, configuration and, where applicable, tested sample. It shall disclose material differences between the offered item and the tested sample. Evidence that cannot be mapped shall be recorded as unverified for the offered item rather than transferred from a similar product.

  5. Door-assembly boundary. Where the claim relies on fire-resistance performance, the Supplier shall provide EN 1634-1 door assembly evidence and identify the assembly boundary. The response shall not recast assembly evidence as a standalone lock fire certificate, and shall not use a lock-performance document to answer the fire-resistance question.

  6. Interface, power and maintenance. The Supplier shall describe the interface to fire detection or alarm systems, the power arrangement and the maintenance regime relevant to the current edition of EN 14637. It shall attach evidence for the behavior claimed and list any function, interface or service activity outside the evidence supplied. The RFQ shall not prescribe an operational mode unless the project design and applicable local review establish it.

  7. Certificate scope and continuing obligations. The Supplier shall state the validity period, issuing-body status and production-control evidence for each certificate relied upon. It shall identify missing renewal, surveillance or production-control information and the party responsible for closing it. A certificate shall not be treated as covering an exact offered variant unless its stated scope does so.

  8. Exceptions and incomplete information. Any limitation, unresolved interface, sample mismatch or evidence gap shall be listed against the relevant clause and marked as an exception. Procurement may return an incomplete response for clarification. Acceptance of a clarification is a separate recorded decision from acceptance of the underlying evidence.

The clause set works only when the response schedule mirrors it. A supplier should be able to point to one attachment for every claim without guessing which document controls. If that is impossible during clarification, the claim remains outside the verified comparison set.

CONFIRM-WITH-LOCAL-LEGAL-REVIEW: Review the contractual effect of each acceptance, clarification, exception and evidence-reliance mechanism before issuing the RFQ.

Q4 response gate: build a claim-to-evidence register

Require one register row for every claim. Do not collect a single bundle of PDFs and ask reviewers to infer which page supports which answer. The register should preserve the supplier’s wording, the procurement interpretation and the attachment reference in the same row.

RFQ response fieldMinimum contentProcurement checkStatus if incomplete
Scope classificationOffered item, intended function and relationship to the proposed assemblyPublished title and scope checkedCLARIFY
Component and interface scheduleSupplied items, exclusions, connections and responsible partiesNo hidden transfer of responsibilityCLARIFY
Evidence inventoryDocument type, title, date, issuer and attachment numberOne document type per rowUNVERIFIED
Test report evidenceSample, tested configuration, method and resultSample maps to the offer or difference is disclosedUNVERIFIED
Third-party certificateIssuing body, verifiable number, scope and validityScope covers the claimed function and offered variantUNVERIFIED
Declaration of conformitySignatory, date, responsible manufacturer or importer and declared scopeSigned, dated and internally consistentUNVERIFIED
MarkingProduct or label image and claimed meaningMarking is not used as a substitute for missing documentsCLARIFY
Fire assembly evidenceAssembly boundary and EN 1634-1 report or certificate where relied uponEvidence applies to the relevant door assemblyHOLD
Maintenance and service evidenceInspection regime, service tasks, records and responsible partyOperating owner accepts the obligationHOLD

Use a controlled vocabulary for the status column. COMPLETE means the stated check has passed. CLARIFY means a supplier answer is needed. UNVERIFIED means the offered claim lacks an applicable evidence link. NOT CLAIMED means the supplier has expressly excluded the claim. None of the last three statuses may be silently rewritten as COMPLETE.

For tender assembly, EN 14637 in a Smart Lock Tender Pack: The Evidence Checklist provides the supporting evidence sequence. Keep the commercial response attached to that sequence so reviewers can audit completeness without relying on narrative assurances.

Q5 comparison gate: compare equal functions at equal evidence

A like-for-like comparison starts by identifying what each supplier actually offered. Do not score a complete hold-open assembly against a lock-only package, or a certificate against a report on a different sample, as if the underlying claim were the same. Create separate comparison lanes when the functions differ, then evaluate the interface between them.

Option presentedWhat may be comparedEvidence required for that comparisonProcurement decision
Offered configuration claims the complete EN 14637 functionScope, exact configuration, interfaces, results and certificate scopeApplicable report, certificate and production-control evidence mapped to the offerEligible for the like-for-like lane when complete
Smart lock and separately scoped hold-open arrangementEach component under its own relevant standardSeparate evidence sets plus a signed interface scheduleCompare components separately before comparing the integrated offer
Test report on a sampleTested sample, method and resultExact sample identification and disclosed differences from the offerComparable only within the demonstrated test scope
Certificate with a different scopeIssuer, scope, number and validityA scope check against the claimed function and offered variantExclude from equivalence until resolved
Self-declared declaration of conformityThe claim, signatory, date and declared scopeSignature, date and supporting evidence referencesTreat as a declaration, not a third-party attestation
Marketing imageThe advertised claim onlyEvidence for en 14637 smart lock rfq clause (en 14637)No evidential comparison credit

Before calculating commercial scores, complete three checks. First, confirm that both offers perform the same procurement function. Second, confirm that the evidence reaches the same rung. Third, confirm that the exact offered variant, assembly boundary and interfaces are described consistently. A response with a genuine gap may still be commercially attractive, but it must not be presented as technically equivalent to a fully evidenced response.

Use exception language in the score sheet rather than hiding gaps in a narrative footnote. A “zero” numerical score cannot repair false equivalence. If the evidence lanes differ, retain both responses but compare cost, scope and risk against the defined procurement function.

Q6 operations gate: assign the hold-open maintenance requirements

Qualification is incomplete until an operating owner accepts the tasks that follow handover. The hold-open maintenance requirements should name what must be inspected, how faults are identified, which records are retained and who restores operation after intervention. Do not substitute a generic service promise for the maintenance information associated with the supplied evidence.

Operational activitySupplier deliverableInstaller or commissioning evidenceOperating owner acceptance
Inspection and routine checksSource of the prescribed task and the information needed to perform itCompleted inspection method and recordNamed owner accepts the schedule
Fault identificationDefined fault indications and authorised response stepsDemonstrated identification routeSupport escalation and restoration process accepted
Power and interface checksScope and limitations of the supplied arrangementCommissioning record for each stated interfaceResponsibility boundary signed
Replacement or reconfigurationCompatibility and configuration information for the offered itemUpdated configuration and evidence mappingChange-control procedure adopted
Record retentionDocumentation and register requirementsInitial handover pack deliveredLocation, owner and review route confirmed

The current edition of EN 14637 and the supplied product documentation should be the source for maintenance scope. If the supplier cannot provide a usable maintenance regime, the system remains at HOLD for operational acceptance even if the laboratory evidence has been accepted.

CONFIRM-WITH-LOCAL-AUTHORITY: Confirm local inspection, commissioning, maintenance-record and handover requirements before transferring responsibility to the operating owner.

Q7 exception gate: use hold codes that prevent silent acceptance

Create hold codes at the first failed check. They provide a consistent response across reviewers and prevent an unanswered field from becoming an implied answer during bid evaluation.

Hold codeTriggerFirst actionExit evidence
HOLD-SCOPEThe offered function or relationship to the door assembly is unclearRequest a classified scope statementSigned component and function schedule
HOLD-EVIDENCEThe document type, issuer, number, scope or date is missingAsk for the named documentComplete evidence inventory
HOLD-VARIANTThe report or certificate cannot be mapped to the offered variantRequest sample and configuration mappingTraceable variant record
HOLD-MARKINGA marking is offered as proof of the full underlying claimSeparate the marking from technical evidenceAppropriate supporting document
HOLD-ASSEMBLYThe fire-resistance claim lacks an assembly boundaryRequest EN 1634-1 evidence relevant to the assemblyIdentified assembly evidence
HOLD-INTERFACEPower, detection or alarm interfaces lack responsibility and evidenceRequest an interface scheduleAccepted interface definition
HOLD-OPERATIONInspection, maintenance and record ownership are unassignedObtain the service pack and owner acceptanceSigned operations handoff

A hold is not automatically a commercial rejection. It prevents qualification until the specified exit evidence arrives. Record whether the gap was closed, accepted as a stated limitation or left unresolved. That decision belongs to the named procurement and technical approvers, not to the bid evaluator’s spreadsheet default.

Readers comparing approaches usually start with smart lock salt spray testing. That is the same question en 14637 smart lock rfq clause has to answer here.

Clause release checklist before shortlist approval

Release the RFQ for comparison only when the qualification record passes every applicable check:

  • The published title and scope of the current edition of EN 14637 are recorded.
  • The proposed smart-lock function is separated from the hold-open function.
  • The door assembly, proposed additions and exclusions are described.
  • Every interface has a named technical and commissioning owner.
  • Test reports, certificates, declarations and markings are listed separately.
  • Each test report identifies its sample and tested configuration.
  • Each certificate states its number, scope and validity.
  • Evidence is mapped to the exact offered model and variant.
  • EN 1634-1 door assembly evidence is identified where the claim relies on fire resistance.
  • The response separates the EN 14637 hold-open system from ordinary smart-lock claims.
  • Maintenance, inspection and record responsibilities are accepted.
  • Every exception and unverified claim remains visible in the comparison.
  • The local authority or appointed reviewer has confirmed the applicable route.

Qualification handoff and supplier response request

The released package should contain the signed scope log, claim-to-evidence register, exception list, interface schedule, comparison lanes, hold-code decisions and operations acceptance. Store the current edition references and document checks with the RFQ response so a later reviewer can reproduce the qualification decision without relying on meeting notes.

This overlaps with the earlier coverage in smart lock mechanical load testing. That is the same question en 14637 smart lock rfq clause has to answer here.Ask each shortlisted supplier to return the completed clause schedule, named evidence attachments and an updated exception register against the issued RFQ version. Request explicit written confirmation where a scope, document or interface remains outside the offer. That request preserves comparison quality because the supplier must expose the limit instead of allowing procurement to infer it.

This runbook supports procurement qualification and does not replace the current published standards, project-specific fire-safety design, local authority review or legal advice. The commercial release remains conditional on the recorded evidence and operating handoff, not on the appearance of a standard number in a proposal.

CONFIRM-WITH-LOCAL-AUTHORITY: Confirm final acceptance, local documentation, commissioning and handover requirements for the delivery jurisdiction before commercial release.

Ask for the offer against the same requirement: request a quote.

Your Cart
Your experience on this site will be improved by allowing cookies Cookie Policy
Chat on WhatsApp