En 1125 smart lock RFQ clause: how to write EN 1125 clauses into a smart lock RFQ so suppliers answer with named test reports, certificate scopes and dated.

نُشر في: فبراير 15, 2024

Panic Bars and Smart Locks: An EN 1125 Clause that Survives Scrutiny

Panic Bars and Smart Locks: An EN 1125 Clause that Survives Scrutiny

A smart lock RFQ that says "EN 1125 compliant" is a clause that has already failed, and it failed at the moment of writing. The sentence gives the supplier no way to answer that ends in a document, and it gives the buyer no way to check what came back. What arrives is usually a catalogue page, or a certificate whose scope nobody read, issued for a variant the buyer is not buying.

Direct answer. The short answer is that en 1125 smart lock rfq clause is not one decision. It is a sequence. This article takes en 1125 smart lock rfq clause from en 1125 smart lock rfq clause through en-1125 to the record you keep. an en 1125 smart lock rfq clause separates what a supplier can show from what only a body can confirm. en 1125 smart lock rfq clause is where the two columns start. Each en 1125 smart lock rfq clause claim names its document.

  • What the supplier can show — supplier declarations and drawings for en 1125 smart lock rfq clause
  • What only a body can confirm — third-party certificates covering the exact scope of en-1125
  • What to request — the document set that matches the SKU behind en 1125 smart lock rfq clause
  • For en 1125 smart lock rfq clause, en 1125 is what each step has to answer to.

EN 1125 is a standard for emergency escape devices operated by a horizontally actuated panic bar. Put that fact at the centre of a clause set and most of the drafting problems resolve themselves, because the standard answers one question only: how a panic device behaves, and whether the hardware on the escape side of a door releases it. Everything else a smart lock does — the credential, the event log, the radio, the motorised latch, the powered strike — belongs to a different question and a different document.

The answer this article works towards is that an EN 1125 clause is not a standard reference, it is a named obligation on a named document. A working clause set does four things before it says "EN 1125" at all: it decides which question the clause is allowed to ask, it names the type of evidence that will satisfy the clause, it binds that evidence to the exact variant offered, and it fixes the edition, the response format and the consequence when the evidence is missing. What follows is the drafting sequence, the clause language, and the calendar that carries a clause set from a blank annex to an award.

The Blank Page Problem: Why Most EN 1125 RFQ Lines Fail

The failure is rarely a supplier being evasive. It is that the clause never asked a question that can be answered with a document. "Supplier shall provide evidence of compliance" is not a request a supplier can answer precisely, so the response arrives as a folder, and the buyer must guess which page in the folder answers which line.

Three failure modes account for almost every disappointing EN 1125 response in a smart lock programme.

The first is the scoping failure, where the clause asks a product standard to answer a door question. EN 1125 describes a device and its behaviour under test conditions. It does not accept a building, an opening or a policy, and it does not approve a door assembly. A clause that treats it as if it does will receive evidence about a device and no evidence about the door. The build options sit in the smart door locks.

The second is the evidence-type failure, where one word covers four different documents. A supplier can reply "compliant" and mean a self-signed declaration, a report for a sample taken years ago, a certificate with a scope that lists someone else's product, or a marking printed on a label. These are not equivalent, and the clause has to say which one it will accept.

The third is the variant-binding failure, where the answer is real and true but applies to a different object than the one on the order. A house range often carries one certificate across several finishes, sizes and power configurations. The clause that does not list the variant attributes leaves the buyer unable to tell whether the answer covers the unit that will actually be fitted.

Clause as usually writtenThe answer it usually invitesWhat stays unestablished
"Lock shall be EN 1125 compliant."A catalogue line, or a certificate for hardware the buyer is not buyingWhich device, which variant, which document
"Panic device shall conform to EN 1125."A self-signed declaration of conformityWhether any third party tested or certified the device
"Supplier to provide evidence of compliance."A folder of unrelated certificatesWhich document answers which clause
"All escape hardware shall meet applicable EN standards."A list of standard designations on a brochureWhich standard, applied to which element
"Lock shall be approved for panic exit use."An approval claim with no issuer namedWhether an approval exists and who issued it
"Escape from the venue shall be possible at all times."A policy sentence echoed backAny physical requirement at all

The repair is the same in all three cases. Replace the adjective with an obligation, replace the obligation with a named document, and tie the named document to a named variant.

Step One: Decide What Question the Clause Is Allowed to Ask

Before a word of clause language is drafted, the procurement manager settles one internal question: which of several separate questions is this line of the RFQ allowed to ask? A single door opening can generate four or five of them, and each has a different answer route. A smart lock on a bedroom door in a serviced residence generates almost none, which is why EN 1125 clauses sometimes appear in RFQs where they have nothing to do with the product being quoted.

The first question is what physically provides the escape function on the escape side of the door. If the answer is a horizontally actuated panic bar, the device falls within the territory EN 1125 describes, and the published title and scope of the current edition should be checked before the designation is used in the contract. If the answer is a lever-operated device, the relevant route is EN 179, and the two designations answer different questions and must not be used interchangeably. If the answer is neither, because the escape function is provided by a fixed push plate or by policy alone, then no product clause belongs on that line at all.

The second question concerns the lock body and what it does. An electromechanically operated lock is asked about under EN 14846, with EN 12209 as the reference for mechanically operated locks, latches and locking plates. Those are different routes again, and neither of them answers for the panic hardware.

The third question is about the door set. Where a door carries a fire or smoke rating, the question is how the assembly performs, and hardware is tested as part of the assembly rather than as a free-standing product — the EN 1634-1 family is the route that treats hardware this way. The fourth question is about the radio, emissions, immunity and any mains-powered accessory the smart lock brings with it, which is governed by a market-access regime rather than by a door-hardware standard.

The question in plain wordsWhat answers itWhere the clause may cite itWhat it cannot be used for
Does the panic hardware on the escape side release the door as the standard's test conditions describe?EN 1125, for a device operated by a horizontally actuated panic barThe escape device, as a named product lineAnswering for a lever-operated device
Does the escape device work from a lever instead of a horizontal bar?EN 179, once the published title and scope of the current edition are checkedOnly where the door schedule shows a lever-operated deviceStanding in for EN 1125 on a panic-bar door
How does the lock body latch, unlock and survive cycling?EN 14846 for an electromechanically operated lock, EN 12209 as the mechanically operated referenceThe lock body, on its own lineAnswering for the escape hardware
Does the door set hold its rating with this hardware fitted?Assembly fire testing such as EN 1634-1The door assembly, as an assemblySupporting a standalone hardware claim
Does the device close the door as designed?EN 1154 for user-powered closing devicesThe closer, on its own lineAnswering for the lock or the escape device
Does the radio and any power supply conform?The radio, EMC and electrical-safety route for the destination marketThe radio module and any mains adapterAnswering for mechanical performance
Who may open the door from inside during an alarm or a power loss?The door schedule, the fire strategy and the egress policyProject documentsAnswering for any product standard

The graph below is the same triage drawn as the routing a clause actually follows. Each clause lands on one question, each question lands on one route, and only the first of those three links is something a supplier can answer with paperwork.

graph LR
  C1["Escape element on the door"] --> Q1["Which escape device route applies"]
  Q1 --> A1["EN 1125 for a panic bar"]
  Q1 --> A2["EN 179 for a lever device"]
  C2["Lock body and latching"] --> Q2["How the lock performs"]
  Q2 --> A3["EN 14846 for an electric lock"]
  C3["Door on a fire route"] --> Q3["How the assembly performs"]
  Q3 --> A4["Assembly test on the door set"]
  C4["Radio and power supply"] --> Q4["Does the radio conform"]
  Q4 --> A5["Radio and EMC route"]

The neighbour designations in this cluster each have their own scope argument, and the drafting decision here depends on those arguments rather than replacing them. The scope boundary of EN 1125 itself is set out in EN 1125 for Smart Locks: Scope, Tests and What the Standard Never Proves, and the choice between EN 1125 and EN 1154 for a given door is handled in EN 1125 Versus EN 1154: Which One Applies to Your Smart Lock Door. The rule of thumb that carries this section is simple: a clause may cite a standard only for the question that standard was written to answer.

Step Two: Fix the Door Before You Fix the Clause

The subject of every EN 1125 clause is an opening. That means the door schedule has to be settled before the clause language is settled, and the ordering is worth arguing for in an RFP because it is the stage most often compressed. A clause drafted against an opening nobody has inspected is a clause that will be re-drafted later, usually under time pressure, usually at the point where several suppliers have already priced the line.

Seven attributes need a recorded answer per opening, and each one changes what the clause can say.

Attribute to recordWhy the clause depends on itWhere the answer comes from
Opening number and door typeEstablishes which clause line appliesThe door schedule issued by the client or consultant
Escape element present on the escape sideDecides whether EN 1125 is even in scopeSurvey of the existing door
Which side the escape element is fittedDetermines the push direction and the operating element the standard addressesSurvey and drawings
Whether the opening carries a fire or smoke ratingMoves the question from the device to the assemblyThe fire strategy and the door schedule
New build or retrofitChanges who owns the door and whether the hardware is being added to an existing leafProject definition
Leaf thickness and frame depthDetermines whether the offered hardware fits the openingDoor measurement survey
Which RFQ package owns the escape hardwareDecides which supplier is even in a position to answer the clausePackage split between smart lock and door hardware

That last row is the one that saves the most trouble. In many commercial buildings the panic hardware sits in the door-hardware package while the smart lock sits in the access-control package. When that is the case, an EN 1125 clause placed in the smart lock RFQ invites a lock supplier to claim conformity with hardware it neither sells nor installs. The correct move is to move the clause to the package that owns the device, and to write in the smart lock RFQ only the interface requirement — the position of the lock relative to the escape hardware, and the fact that the escape function must remain operable while the door is secured.

Retrofit adds a second layer. Adding a panic device to an existing leaf is a change to the door, not only to the hardware on it, and the readings that follow from that change are set out in EN 1125 When Retrofitting Smart Locks Onto Existing Doors. For the clause set itself, the practical consequence is that the survey data in the table above becomes a mandatory annex, and that the RFQ must state which survey data the supplier is expected to work from. Getting the opening dimensions right at this stage is what the Smart Lock Door Measurement Guide exists to support.

CONFIRM-WITH-LOCAL-BUILDING-APPROVER: whether escape hardware on each opening is accepted as part of a door assembly, which body signs that acceptance, and what evidence format that body reads, for the jurisdiction in which the doors are installed.

Step Three: Name the Evidence Type in the Clause

This is the step that changes the quality of the responses, and it costs one table. Four documents get confused in this sector often enough that a clause that does not disambiguate them will receive whichever one the supplier finds most convenient.

Evidence typeWhat it actually isWhat it establishesWhat it cannot establishThe verb that requests it
Test reportA document recording that a sample was tested against the standardThat testing happened, under which edition, on which sample, with which resultsThat production continues to conform"Provide the test report"
CertificateA body attesting conformity, carrying a scope, usually a number, a date of issue and an expiryThat a named body stands behind a defined scopeThat the scope covers the variant being bought"Provide the certificate number, scope and issuing body"
Declaration of conformityThe manufacturer's or importer's own legal claim of conformityThat a legal party has taken responsibility for the claimThat any third party verified anything"Provide the signed and dated declaration"
MarkingA mark printed on the product or its labelWhich regime the product is presented under in the market it enteredConformity with any particular standard"Provide a photograph of the marking and name the regime"

Two habits make this section work in practice. The first is to use one verb per document type and never to let two verbs stand for the same thing — "provide" for a report, "quote" for the identifying data of a certificate, "state" for a fact about the product, and "attach" for a document that has to be seen. The second is to write the no-substitution rule explicitly, so that a marking cannot quietly discharge a clause written to require a certificate, and so that a certificate covering a different variant cannot discharge a clause written to require this one.

Underneath the four document types sits a longer ladder, and a clause set can move a response up or down it. The common commercial failure is buying at the second or third rung and discovering at installation that nothing exists at the fifth.

RungWhat the evidence looks likeWhat the clause must add to move up one rung
1A marketing image or a catalogue statementEvidence for en 1125 smart lock rfq clause (en 1125)
2marketing imageAsk for the test report that supports the declaration
3declaration of conformityAsk for the certificate covering the same scope
4test report on a sampleAsk for confirmation that the offered variant is inside that scope
5scoped third-party certificateAsk for the production-control evidence that keeps it valid
6certificate covering the exact SKU or variantAsk for the inspection routine and its frequency

The pattern to notice is that each rung costs the supplier one more piece of paperwork. A clause set that names the documents it needs is therefore doing two things at once: it is setting the evidence floor, and it is setting the price the supplier must charge to clear it. The wider question of who pays for conformity evidence in a private-label programme is handled in Who Pays for EN 1125 Evidence in a Smart Lock OEM Programme.

Step Four: Bind the Standard to the Exact Variant

Binding is the step that converts a technically correct answer into a usable one. A certificate may cover a product range. A report may cover a specific sample with a specific configuration. The buyer needs to know where the offered configuration sits inside that range, and the clause needs to make the supplier say so rather than leaving it to be inferred from a catalogue.

The mechanism is to list the variant attributes that the evidence is sensitive to, and to require the supplier to state any offered variant that the documents do not cover. The second half of that requirement carries as much weight as the first: a supplier that discloses a gap at quotation stage is a supplier negotiating a scope, while a supplier that stays silent is a supplier whose gap appears at handover.

Variant attributeTypical effect on the evidenceClause language that closes the gap
Housing finish and colourMay fall outside a certified range"Each document shall state the finishes to which it applies"
Size or dimensional variantMay constitute a different product in the eyes of the issuing body"State the dimensional variants covered, and identify any offered variant not covered"
Power sourceA battery device and a mains-fed device may sit under different arrangements"State the power source configuration covered by the documents"
Fixing and door thickness variantChanges the physical assembly that was tested"State the leaf thickness and fixing configurations within scope"
Component or supplier changeMay suspend the arrangement behind the certificate"State whether the manufacturer of the device has changed since the date of issue"
Production siteCertificates may be tied to a named site"State the manufacturing site to which the certificate relates"

The wording that works has one property in common: it asks for a list rather than a yes. "Is the device covered?" is answered yes or no, and a supplier answering no has lost nothing by being vague. "Which variants are covered?" is answered with a list, and the list is the evidence.

Two related habits complete the binding. One is to require the document set to be issued in a form the buyer can verify, which usually means the original-language document rather than a translation, or a translation that keeps the identifiers legible. The other is to require the supplier to name a contact point for verification, so that a buyer who has doubts about a scope can ask without restarting the whole procurement.

Step Five: Write the Edition Line and the Scope Line

Standards move. Editions are revised, amendments are published, and a document issued against a superseded edition may still be the document that covers the product while no longer being the edition a new tender wants to reference. The clause therefore has to state which edition it means, and the safest formulation names the edition in force at the date of the response rather than a date the buyer cannot verify.

A workable edition line reads: "Documents shall relate to the edition of EN 1125, and any published amendment, in force on the date of the Supplier's response. The Supplier shall state the edition and amendment relied on, and shall note any difference between that edition and the edition stated on the certificate."

The second sentence is the one that earns its place, because it converts a latent discrepancy into a disclosed one.

The scope line does the same job for the certificate. A certificate states what it covers, and the clause should require the supplier to quote that scope and to state the position of the offered device within it. Three outcomes are possible and all three are acceptable at quotation stage: the device sits inside the listed scope, the device sits inside a wider scope that the certificate names but the buyer must check, or the device sits outside it. Only the third is a problem, and it is a problem that becomes visible only if the clause asks.

Clause-level questions belong to the published standard text rather than to an RFQ document, and the classification markings that appear on reports and certificates are decoded in Decoding EN 1125 Class and Grade Numbers for Door Hardware. Writing a paraphrase of a clause into an RFQ is how a contract acquires an obligation that neither party intends, because the paraphrase will not match the published wording.

CONFIRM-WITH-LOCAL-STANDARD-ACCESS: which edition and amendment of the relevant designation is the contract to reference, and which body or publisher holds the definitive text for the jurisdiction of the project.

Step Six: Write the Production-Control Clause

A certificate is a statement about a sample and a standing arrangement. The sample passed on the date it was tested. What keeps the statement true afterwards is production control: the routine by which units made after the test are checked against the same requirements, and the audit that confirms the routine is running.

The clause for this is short and it is frequently omitted:

"The Supplier shall provide the evidence by which conformity is maintained for production after the date of the test, including the production-control inspection routine applied to the device and the frequency at which it is carried out, and shall state the body or scheme under which that routine is defined."

Written in this form, the clause distinguishes a product that was once tested from a product that is controlled. A supplier with a real production-control routine answers in a paragraph. A supplier without one answers with a paragraph about quality management systems, and the buyer learns something useful in the exchange.

This clause is also the one that separates a management-system certificate from product evidence. A quality management system certificate proves that the organisation runs a documented process. It proves nothing about any specific device and it cannot discharge a clause written to require product conformity. The distinction is worth making explicitly in the response format, because otherwise it is the easiest possible substitute to offer.

Step Seven: Write the Response Format Clause

A response format is what makes the difference between a document pile and an answer. The clause below is the one that prevents the pile, and it costs a single annex.

"The Supplier shall complete one row of the Annex B response matrix for each device type and each evidence type listed in Clause 7.2. Where a document is not available, the Supplier shall state the gap in the same row rather than omitting the row."

The matrix itself is short, and every column earns its place by preventing a specific ambiguity.

ColumnWhy it is in the matrix
Device type and offered variantMakes the binding explicit and stops rows being read against the wrong product
Evidence typeConfirms which rung of the ladder is being offered for that row
Document title and identifierThe name and number a buyer can check against an issuing body
Issuing body or declaring partySeparates a third-party attestation from a self-declaration
Edition or standard revision referencedReveals a mismatch with the edition the clause asked for
Date of issue and expiryShows whether the document is live and how long it will stay live
Variants covered, or scope quoted verbatimMakes the scope check possible without opening the file
Location in the attached dossierRemoves the hunt; a document that cannot be located is not evidence
Language of the original documentDetermines whether the text is verifiable as issued
Named verification contactGives the buyer a route for a question that the file did not answer

The clause also needs a rule about attachments, because the alternative to a matrix is always a folder. "Attach all relevant certificates" produces a folder, and folders invite the buyer to credit the wrong page to the wrong requirement. "Attach the documents listed in the matrix, and nothing else" produces a set that can be indexed against the clauses.

The matrix also creates the audit trail. When the contract is signed, the matrix is the record of what was promised on the day, which document was offered, and which gaps were declared. That record is what a later conversation about a non-conforming unit starts from.

The Clause Set: Draft Language That Can Be Adapted

The following is a working skeleton for a smart lock RFQ that includes panic hardware. It is written to be adapted rather than pasted unchanged: the clause numbers will differ by contract form, the jurisdiction will change the reference to the applicable market regime, and the annexes have to be filled with the openings from the door survey.

CLAUSE 7.1  SCOPE OF THE ESCAPE HARDWARE REQUIREMENT
The escape function on the openings listed in Annex A shall be provided by a
horizontally actuated panic bar on the escape side. The Supplier shall state
for each opening type whether the escape device is within the scope of the
goods offered, is supplied by others, or is absent, and shall identify any
opening where the goods offered perform no part of the escape function.

CLAUSE 7.2  CONFORMITY EVIDENCE FOR THE ESCAPE DEVICE
For each escape device type in Annex A the Supplier shall provide the
following, and shall not substitute one for another:
 (a) the test report issued against the escape device, identifying the
     standard, the edition or amendment and the sample tested;
 (b) the third-party certificate covering the escape device, quoting the
     issuing body, the certificate number, the scope of certification, the
     date of issue and the date of expiry;
 (c) the declaration of conformity issued by the manufacturer of the
     device, signed and dated;
 (d) a photograph of the marking applied to the device or its label, and the
     market regime under which that marking is applied.

CLAUSE 7.3  VARIANT BINDING
Each document supplied under Clause 7.2 shall state the product designation,
finish, dimensional variant, fixing configuration and power source to which
it applies. The Supplier shall list every variant of the offered device that
is not covered by the documents supplied.

CLAUSE 7.4  EDITION AND AMENDMENT
The documents shall relate to the edition of the standard and any published
amendment in force on the date of the Supplier's response. The Supplier shall
state the edition and amendment relied on, and shall note any difference
between that edition and the edition stated on the certificate.

CLAUSE 7.5  PRODUCTION CONTROL
The Supplier shall provide the evidence by which conformity is maintained for
production after the date of the test, including the production-control
inspection routine applied to the device, the frequency at which it is
carried out, and the body or scheme under which it is defined.

CLAUSE 7.6  RESPONSE FORMAT
The Supplier shall complete one row of the Annex B response matrix for each
device type and each evidence type in Clause 7.2. A row shall be completed
with the gap stated where a document is unavailable, rather than omitted.

CLAUSE 7.7  NO SUBSTITUTION
A marking, a declaration of conformity, a catalogue entry, an image, a
management-system certificate, or a document covering a different variant, a
different standard or a different scope shall not satisfy Clause 7.2 unless
it is the document named in that clause.

CLAUSE 7.8  EVIDENCE GAPS
Where a document named in Clause 7.2 cannot be provided, the Supplier shall
state the gap in writing, identify the device types affected, and set out the
alternative conformity route it proposes together with the evidence that
supports that route.

CLAUSE 7.9  SCOPE SEPARATION
Conformity evidence supplied under Clause 7.2 relates to the escape device
only. It shall not be relied upon as evidence of conformity of the lock body,
of any radio module, of any power supply, or of the door assembly.

CLAUSE 7.10  VERIFICATION
The Supplier shall provide the issuing body's contact details and shall
authorise the buyer to verify the scope and validity of any certificate
supplied, in writing, within a reasonable period of the request.

CLAUSE 7.11  CHANGE NOTIFICATION
The Supplier shall notify the buyer in writing of any change to the
manufacturing site, to the production-control routine, to the device
configuration or to the certificate status, within a stated period of that
change, and shall state the effect of the change on the documents supplied.

CLAUSE 7.12  SEPARATE REQUIREMENTS
Nothing in this Clause 7 relieves the Supplier of the separate requirements
of this RFQ relating to the lock body, to any radio equipment, to any
electrical safety, to the door assembly, to the credential system, or to the
data-handling obligations attaching to door event logs.

Three adaptation notes. First, the jurisdiction clause belongs in the RFQ as a separate line, naming the market regime that applies to the goods and the obligations it carries; that is a legal determination and is not made here.

CONFIRM-WITH-LOCAL-MARKET-REGIME-ADVISER: which market regime applies to the goods and to any accessory supplied with them, which obligations that regime carries, and which route in the destination market places the relevant duties on the importer rather than on the manufacturer.

Second, the reference to the escape device and the reference to the lock body must stay in separate clauses, because merging them is what allows one certificate to appear to cover an entire smart lock. Third, the gap clause is not a concession and should not be negotiated away — it is the clause that lets a supplier be honest without losing the bid, and an RFQ without it will get a confident answer instead.

The Clause Calendar: Nine Stages From Door Survey to Award

The clause set is not a document that is written once. It moves through a sequence with different owners, different inputs and different outputs at each stage, and the sequence is what stops a well-drafted clause from being quietly diluted by a later schedule, a later price sheet or a later clarification answer.

timeline
    title EN 1125 clause set build calendar
    section Preparation
        Door survey : Escape element recorded for every opening
        Question mapping : Each question assigned to one route
        Package decision : Escape hardware assigned to its RFQ package
    section Drafting
        Evidence naming : Document type written into every clause
        Variant binding : Offered variants listed against documents
        Edition line : Edition and amendment fixed
        Production control : Control routine clause added
        Response format : Annex matrix drafted
    section Issue and award
        Issue : Clause set and matrix sent to suppliers
        Clarification : Gaps declared in writing
        Evaluation : Documents checked against the matrix
        Award re-check : Scope re-read before the award
StageOwnerInputOutputWhere it lands in the RFQ
Door surveyClient, consultant or the buyer's site teamDoor schedule and drawingsEscape element recorded per openingAnnex A
Question mappingProcurement managerAnnex A and the scope tableOne route per questionClause 7.1 and the standard schedule
Package decisionProcurement manager with the package leadRoute mapA decision on which RFQ owns the escape hardwarePackage split, before issue
Evidence namingProcurement managerRoute mapOne named document per requirementClause 7.2
Variant bindingProcurement manager with the supplier's technical contactOffered variant listVariant attributes tied to each documentClauses 7.3 and 7.4
Production controlProcurement managerSupplier's routine descriptionControl clause and the audit referenceClause 7.5
Response formatProcurement managerEvidence listThe matrix templateAnnex B
Issue and clarificationProcurement managerClauses and annexesIssued RFQ, then a written clarification recordIssued document set
Evaluation and award re-checkEvaluation panelResponsesA traceable award decisionEvaluation record

Two features of this calendar are worth defending. The clarification round is a written round with a deadline and a written record, which stops an informal email from quietly becoming the contractual answer on a scope question. The award re-check is a reading of the scope back against the awarded documents, because the variant list tends to drift during negotiation, and the last version of that list is the one that has to match the purchase order.

Six Clause Traps and Their Repairs

The traps below are the ones that recur across programmes. Each is a wording choice with a predictable consequence.

TrapWhy it failsRepaired wording
"All products shall comply with EN 1125."Applies a device standard to a range that includes goods with no escape function, and to the lock body"The escape devices listed in Annex A shall comply with EN 1125. This clause does not apply to the lock body."
"Evidence of EN 1125 conformity to be provided prior to order."Puts the burden after the order, when the variant is fixed and the money has moved"Documents listed in Clause 7.2 shall be provided with the quotation, indexed by the Annex B matrix."
"Certificate shall cover the product."A certificate covering a range satisfies the sentence without covering the variant"The certificate scope shall be quoted in full, and the offered variant shall be identified within that scope."
"Any equivalent certification accepted."Invites the cheapest available substitute, including a management-system certificate"Equivalent evidence may be accepted only where it is a document of the same type, issued for the same scope, and named in the response matrix."
"Supplier to confirm compliance."Puts the verification duty on the buyer after the award"The Supplier shall state, per row of the matrix, the document that evidences compliance, or the gap."
"Compliance to be maintained throughout the contract."Creates an open-ended obligation without naming the evidence that maintains it"Conformity shall be maintained by the production-control routine described in Clause 7.5, and any change notified under Clause 7.11."

The trap that appears most often is the first one, and it is worth naming precisely: EN 1125 is applied to a product range rather than to an escape device. Once a clause says "all products shall comply", a supplier can answer it with a single device certificate and let the buyer infer that the rest of the range is covered. Nothing in the response contradicts that inference, and the inference is wrong.

How to Evaluate the Responses Without Reopening the RFQ

Evaluation works as a sequence of checks applied to each response, in a fixed order, so that the panel is reading the same things in the same sequence. The order matters because each check can end the review early.

The first check is the named-document check: does the matrix row point at a document that exists in the dossier, and is that document the type the clause named? A row that points at nothing, or at a document of the wrong type, fails here. The second is the variant check: does the document, or the scope it quotes, place the offered variant inside its coverage? The third is the scope check: does the scope of the certificate cover the device type offered, and not only a related product? The fourth is the edition check: does the edition referenced match what the clause asked for, and if it does not, has the difference been disclosed? The fifth is the production-control check: is there a routine described that keeps the claim true after the sample passed? The sixth is the gap check: has every missing document been declared in writing rather than left as a silence?

A response that clears four of the six is not a failure, and the useful response is to turn the two open checks into written conditions rather than into a conversation that resets the timeline. A disclosed gap with an alternative route is a negotiation. An undisclosed gap discovered after the award is a dispute, and it lands on the buyer, because the buyer chose the supplier without knowing there was a gap.

The evidence that arrives is read as a document, not as a claim, and the reading technique for a report page by page is set out in Reading a EN 1125 Test Report Page by Page: a Smart Lock Buyer Walkthrough. The three recurring ways that this stage goes wrong are collected in Three Ways EN 1125 Evidence Disappoints Smart Lock Buyers, and the tender-facing version of the same checklist is EN 1125 in a Smart Lock Tender Pack: the Evidence Checklist.

Where the Clause Set Meets the Rest of the RFQ

An EN 1125 clause set is one part of a larger instrument, and the parts have to agree with each other. The clause in this article cannot contradict the technical specification, the door schedule, the price sheet or the sample approval procedure.

Against the technical specification, the rule is that a standard reference in the specification is a reference to a requirement, while a standard reference in the clause set is a request for evidence. The two belong in different documents for a reason: one tells the supplier what to build, the other tells the supplier what to prove. The wider drafting of the technical side is covered in Smart Lock OEM Technical Specification.

Against the door schedule, the rule is that Annex A and the door schedule must be the same list. A clause set that covers openings the schedule does not contain will produce responses about hardware that is not installed, and a schedule that contains openings the clause set omits will produce a building with escape devices that nobody asked anyone to document. This is the point at which Smart Lock RFQ Guide for International Buyers is worth reading alongside, because the schedule, the specification and the evidence annex have to move as one package.

Against the rest of the compliance evidence, the rule is that each market-access regime has its own line and its own documents, and that a line for one regime never discharges another. A radio-equipment question and a panic-hardware question are answered by different bodies and different files. The general question of what to request from a supplier, and how hard to verify it, is handled in What Certifications Should I Request From a Smart Lock Supplier?, and the broader programme-level checklist is Smart Lock Procurement Checklist for B2B Buyers.

One obligation sits outside the product file entirely and needs its own line in the RFQ. Where a smart lock produces a record of who opened which door and when, that record is personal data, and the retention period, the hosting location, the processor arrangements and the deletion terms are contractual questions rather than product questions.

CONFIRM-WITH-LOCAL-DATA-PROTECTION-REVIEW: which data-protection regime applies to the door event logs the goods generate, how long those records may be retained, where they may be hosted, and which party acts as processor for the installation.

Sending the RFQ: What You Ask

The clause set is finished when three things are true. The Annex A list matches the door schedule opening for opening. Every clause names a document rather than an aspiration. And the response matrix is attached, because a request for evidence without a format for answering it returns a folder.

Once the RFQ is issued, the work continues in the clarification round, and it continues with the discipline of writing. The record of what a supplier declared about its own evidence, on the day they declared it, is the document that settles the question when one is raised later. Two habits preserve that record: require every clarification to be given in writing against the clause number it addresses, and keep the matrix version that was issued with the RFQ alongside the matrix version that came back.

The final step is the award re-check, which is a reading rather than a meeting. Before the purchase order is raised, the scope quoted in the awarded documents is compared against the variant list on the order, and any documented gap is carried into the order as a written condition with a named owner and a date. A gap that is written down is a condition. A gap that is carried in silence becomes a dispute, usually at handover, usually with the calendar already against the project.

Where a programme needs samples before the clause set is finalised, the sample is worth ordering against the same variant list that the clause set binds to, so that the physical unit and the documentary evidence describe the same object. Model-level facts — dimensions, cycle behaviour, reading performance, power characteristics — are confirmed on the dated product page for the specific SKU rather than assumed. If a clause set is ready to be reviewed against a real variant list, the request can go through Request a Quote, and physical units can be ordered through Order Samples.

عربة التسوق الخاصة بك
سيتم تحسين تجربتك على هذا الموقع من خلال السماح بملفات تعريف الارتباط سياسة ملفات تعريف الارتباط
Chat on WhatsApp