Buying a Cylinder, Not a Lock: The EN 1303 Clause a Buyer Can Actually Use
A conformity argument is only as good as its weakest document, so en 1303 smart lock rfq clause is treated here claim by claim. An EN 1303 clause inside a smart lock request for quotation is almost always one line long, and almost always mis-scoped. EN 1303 is a standard for cylinders for locks: the durability, resistance to attack and key control of the key cylinder itself, plus corrosion classes in later editions. It is not a standard for the lock that receives the cylinder, the electronics, the escape function of a door, the radio, or the fire behaviour of an assembly. A requirement that says the smart lock shall comply with EN 1303 asks a cylinder standard to carry a product claim, and every supplier answers it differently: one sends the document for the cylinder it fits, one sends a declaration for the whole lock, one says the cylinder was bought in and the evidence sits with another company.
Direct answer. An EN 1303 smart lock RFQ clause is finished when it names seven things: the part the requirement attaches to, the document that evidences it, the object that document covers, the holder of that document, the party signing the declaration that references it, the programme point by which the chain must be complete, and the boundary stating what the requirement does not cover. One line makes a sentence; those seven fields make a clause a supplier can answer and an auditor can follow.
- What the seller can produce — supplier declarations and drawings for en 1303 smart lock rfq clause
- What only an issuer can verify — third-party certificates covering the exact scope of en-1303
- What to request — the document set that matches the SKU behind en 1303 smart lock rfq clause
- For en 1303 smart lock rfq clause, the order below is fixed and en 1303 is the reference point.
This transcript builds that clause set turn by turn, for the procurement manager who owns the request for quotation.
The conversation below is illustrative and records no real meeting, project, supplier or authority.
How the two reviewers work
Two voices appear. Procurement is the buyer writing the request for quotation and owning the evidence afterwards. Technical is a standards and hardware reviewer who reads quotations, certificates and declarations against clauses.
| Voice | Stands for | Answers well | Cannot answer |
|---|---|---|---|
| Procurement | The person issuing the request for quotation | What the programme buys, which parts are in scope, what the supplier hands over | Whether a document the supplier sent demonstrates the clause that was written |
| Technical | A reviewer who reads standards and declarations against clauses | What a clause must bind, which document proves what, where a scope boundary sits | Whether a particular door will be accepted by the approving authority |
Clauses C1 to C16 accumulate as the conversation proceeds and are collected in one table further down; Annotation blocks close each turn with the clause produced and the question behind it.
One rule governs everything that follows. A standard describes what a standard tests; it never speaks for a factory or for a part it does not cover. Conformity is always somebody's claim, evidenced by a document with a holder, a scope and a date. What can be supplied is listed in the smart door locks.
Turn 1 — The line that arrived with the template
Procurement: The request for quotation went out on our standard template, where the product requirements table carries one row per standard. The EN 1303 row reads "Key cylinder shall comply with EN 1303". Three quotations came back and the answers differ: one attached a document for the cylinder it fits, one sent a declaration for the complete lock, and one said the cylinder is bought in and the evidence sits with the cylinder maker, so it attached a scope. Which one did I actually buy?
Technical: All three are defensible readings of a thin clause, which is why they diverge. Your line contains a part and a standard and nothing else: not which cylinder, which document, who holds it, or when it must exist.
Procurement: So the problem is the clause, not the suppliers.
Technical: The problem is the clause, and behind it sits a second, more expensive one. EN 1303 covers cylinders for locks and says nothing about the lock body, the electronic locking function, the escape function, the radio or the fire behaviour of an assembly. When your line says the key cylinder shall comply with EN 1303, the second supplier read it as permission to say the product conforms, and that claim is incoherent, because the product is not a cylinder.
Procurement: Why is the precise claim worth more than the generous one?
Technical: Because the generous claim is the one that gets repeated, into a brochure, a tender file and an approval submission where somebody checks whether it holds. The narrow claim survives that check, and it tells your installation team which part of the product the file is about.
Annotation — clause C1, the object clause. The requirement attaches to a named cylinder: its function and position in the lock, its type designation, the document type that evidences it, the holder of that document, and the milestone by which it must exist.
Annotation — the question the buyer is really asking. Not whether EN 1303 is enough, but which part, which document, which holder, and by when can I show it to somebody.
Turn 2 — Which cylinder, on which door
Procurement: The product sheet shows two cylinders on one lock: a euro-profile cylinder under the handle, and a small override cylinder at the base of the keypad housing that you use when the batteries are flat. My clause says the key cylinder. That covers both, I assume?
Technical: It covers whichever one the respondent chooses to call the key cylinder, which is how one clause ends up with two answers attached to it. An override cylinder is a break-glass function: used rarely, sometimes under stress, and often the only way into a room when the electronics have failed. A cylinder that operates the latch on a door is a daily-use function, and the key control expectation for the two is not automatically the same.
Procurement: So my clause needs a schedule rather than a noun.
Technical: It needs a schedule, and each row must name the cylinder by its function and position in the lock, its type designation, and the configuration as quoted. The configuration — profile, length, cam position, finish — comes from the supplier's dated product documentation for the exact variant, so confirm each value on the dated product page for the SKU quoted and copy it into the object schedule. Getting this wrong is the classic route to a cylinder that will not fit the case; both ends of that problem appear in the Smart Lock Cylinder Measurement and Smart Cylinder vs Full Smart Lock notes.
Procurement: What about the doors?
Technical: On a retrofit the existing lock case often decides what the new lock can be, and the door population decides how many cylinders and which types you buy. The Smart Lock Door Measurement Guide and the Smart Lock Retrofit Site Survey turn a door schedule into an orderable population, and what to keep on an existing door is examined in EN 1303 When Retrofitting Smart Locks Onto Existing Doors.
Annotation — clause C2, the object schedule. One row per cylinder: function, position, type designation, profile, length, cam position, finish, and the doors using it. A noun is not a schedule.
Annotation — clause C3, the boundary of the requirement. The requirement covers the cylinders in the object schedule only, and expressly excludes the lock body, the electronic locking function, the escape function, the radio and electromagnetic behaviour, the ingress and impact rating, and the fire and smoke assembly performance of the product.
Turn 3 — The cylinder your supplier did not test
Procurement: The third supplier's answer was the most honest and the least useful: we buy the cylinder, the cylinder maker tests it, here is the scope of their document. Does that satisfy my clause?
Technical: Not yet, and it can satisfy everything once you write the chain into the clause. In most smart lock programmes the cylinder is a purchased part: somebody else designed and tested it, and the document sits with that party, who is not your counterparty and has no obligation to send you anything. Your clause cannot compel a third party to issue a document to you, but it can require your supplier to produce the chain.
Procurement: Meaning what, concretely?
Technical: Four links. The supplier identifies the cylinder type as incorporated in the lock, by type designation; provides the third-party document covering that type, with its scope; provides a signed declaration identifying the cylinder type as the one fitted and referencing that document; and states the arrangement that keeps the delivered cylinder the same type as the evidenced one. Three parties are involved: the cylinder maker holding the evidence, the lock supplier placing the product on the market, and you, who has to follow the chain when somebody asks.
Procurement: And if the cylinder maker changes the type without telling my supplier?
Technical: Then the chain is broken and you find out at goods-in, the expensive place to find out. That is why the change-notification clause must reach the cylinder type rather than the finished product, because the event that counts is usually upstream of your counterparty. Binding a part is what an EN 1303 clause does that a product-level clause cannot: parts change silently.
Evidence to demand. The third-party document for the cylinder type with its scope; the supplier's signed declaration referencing it; the type entry cross-checked against the purchase order line; and the production-control arrangement in writing.
erDiagram
RFQ ||--o{ CLAUSE : contains
CLAUSE }o--|| EVIDENCE : demands
EVIDENCE ||--|| DOCUMENT : embodied_in
DOCUMENT ||--|| CERTIFICATE : may_be
CERTIFICATE }o--|| TEST_BODY : attested_by
CERTIFICATE ||--o{ TYPE_ENTRY : covers
TYPE_ENTRY }o--|| CYLINDER : describes
CYLINDER ||--o{ LOCK : incorporated_in
LOCK ||--|| DECLARATION : declared_by
DECLARATION }o--|| CERTIFICATE : references
Procurement: That diagram is the chain I have to be able to follow at goods-in?
Technical: That is the chain. The lock touches the document only through the declaration, and the document touches your order only through the type entry. If any join is missing, the evidence is about something other than what is in the container.
Annotation — clause C4, the evidence chain. Where the cylinder is a purchased part: the type as incorporated, the third-party document with its scope, a signed declaration referencing it, and the production-control arrangement that keeps the delivered cylinder the evidenced type.
Annotation — clause C5, the declaration. The party making it, the signatory and capacity, the product, the cylinder type, the document relied upon, and the date.
Turn 4 — The four documents a supplier can send
Procurement: What am I allowed to accept? On this project I have a scope, on another a PDF of a test report, and once a photograph of a mark on a carton.
Technical: Four things, routinely confused. A test report says somebody tested a sample. A certificate says a body attests conformity, with a scope and a validity. A declaration of conformity is the manufacturer's or importer's own legal claim. Marking is the symbol printed on the product or its label. When a summary says the product has CE and nothing else, any of the four might have been meant.
| Document | What it actually says | What to check | Typical failure on a cylinder |
|---|---|---|---|
| Test report | A sample of a described product was tested against named clauses | Number, date, tester, sample description, clauses tested, whether the sample is your type | A report for a different cylinder family offered as reassurance |
| Certificate | A named body attests that a defined scope of product conforms to a defined standard | Body, number, scope wording, standards listed, issue date, validity | A number with no scope attached, so nothing can be checked |
| Declaration of conformity | The manufacturer or importer makes its own legal claim | Who signed, in what capacity, what product and cylinder type it covers, what it rests on | Signed by a party with no stated relationship to the product |
| Marking | The manufacturer declares the product is placed on the market under an applicable regime | Which regime, whether the mark is on the product or only in a document | A mark on a carton graphic, for a regime silent on cylinders |
Procurement: So for the cylinder clause, which of the four do I write into the text?
Technical: The one you are prepared to defend, named by type. For most programmes that is the third-party document for the cylinder type, with the scope, plus the supplier's signed declaration referencing it. For a direct purchase at a lower risk position, a test report on a described sample plus a signed declaration may be realistic, provided the clause says so and the gap is recorded. What you must never write is the word evidence on its own, because that is the word a buyer uses when the decision has not yet been made.
Evidence to demand. The full document rather than a summary: for a certificate, the scope; for a report, the sample description and the results. The documents worth asking for are listed in What Certifications Should I Request From a Smart Lock Supplier?, and one is read page by page in Reading a EN 1303 Test Report Page by Page: a Smart Lock Buyer Walkthrough.
Annotation — clause C6, the document type. The document is named in the clause. A summary, an extract, a bare number or a marking shown in an image does not satisfy it.
Turn 5 — The edition, and who notices it changing
Procurement: One supplier cited EN 1303 with a year attached. Another wrote EN 1303 with no year. Which do I put in the clause?
Technical: Neither as written. A year without an amendment statement is ambiguous, because amendments are issued separately from the main edition, so a document can cite the edition and still be silent on a change that counts. No year at all means the supplier's file decides, and two quotations can no longer be compared on the same basis. Write the current published edition and pin the evidence against it.
Procurement: The current edition covers more than durability, doesn't it?
Technical: Later editions of EN 1303 added corrosion classes to what the cylinder is assessed on, which is exactly why the current edition is a moving reference rather than a date. Check the published title and scope of the current edition, and route clause-level questions to the standard text itself. If you want a fixed edition for a reason — a client standard, a tender instruction, a local implementation rule — say so in the clause and carry the risk that the market has moved on.
Procurement: The complication is that the cylinder is not my supplier's product.
Technical: It is the reason the change obligation has to reach upstream. Your supplier may know nothing about a new edition until the cylinder maker says so, which may be after production starts. So the clause asks the supplier to state the edition and amendment cited, to notify you before shipment if that citation is superseded, and to say whether the document remains valid. On a long programme, name the edition that applies to your order, so the supplier can pass it up the chain.
CONFIRM-WITH-LOCAL-CERTIFICATION-BODY — whether a cylinder certificate issued against one edition of EN 1303 remains valid when a later edition or amendment is published, how the body handles re-assessment, and what the national implementation guidance says at the date of your order.
Annotation — clause C7, the edition. Conformity to the current published edition, including any amendment in force at the date of issue, with the edition and amendment cited on the document supplied.
Annotation — clause C8, the change notification. The Supplier notifies before shipment if the cited edition, the cylinder type or the production site changes, and states whether the document remains valid for the delivered cylinder.
Turn 6 — Key control is in scope, and that changes the clause
Procurement: Key control is one of the things EN 1303 covers, and it is the part I care about most. Our building runs a master key system, and the cylinders have to sit inside it without breaking the estate's key discipline.
Technical: Then the clause must ask for two different things, and buyers regularly mix them up. The first is what the standard assesses about key control on the cylinder type: how it is configured to be keyed, what controls exist over duplication and over unauthorised copying, and what the third-party document says about that configuration. The second is your own keying design: which master key hierarchy the cylinder lives in, which keys go to whom, which cylinders are keyed alike and which are keyed different, and which one is the break-glass cylinder nobody carries casually.
Procurement: So the certificate answers the first and cannot answer the second.
Technical: Correct. A cylinder document says nothing about your building's key system, and your key system says nothing about the cylinder's assessed performance. What the certificate can do is show that the cylinder type was assessed with a particular key control configuration, and the clause then requires the supplier to state that configuration and confirm it is compatible with the keying schedule you specify.
Procurement: How specific should the key control clause be?
Technical: Specific enough that two suppliers answering the same clause produce comparable answers: the key control configuration as offered, the key quantities as quoted, the master key relationship for each cylinder position, and a written statement of compatibility with the keying schedule attached to the request for quotation. Where the programme touches housing for vulnerable or sensorily impaired occupants, the access-control locking practice reference cited in that sector must be named in the clause, and its published title and edition verified locally before citing it.
CONFIRM-WITH-LOCAL-SECURITY-ADVISER — which access-control locking practice reference applies to the housing type in this programme, its published title and current edition, and what it requires of key control, cylinder selection and override arrangements.
Annotation — clause C9, key control. The key control configuration of the cylinder type offered, the key quantities as quoted, the master key relationship for each position, and compatibility with the Buyer's keying schedule.
Turn 7 — What the cylinder document is silent
Procurement: Assume I have the strongest possible cylinder evidence: a third-party document, correct scope, exact type, current edition, and a declaration that references it. What does that tell me about the lock I am buying?
Technical: It tells you about a cylinder. That is all. It is silent on the lock case, the latch and the deadbolt; on the cam engaging the lock mechanism and what the lock needs from that cam; on the motor, the gear train and the timing of the automatic locking; on the escape behaviour of the lock body; on the durability of the complete set; on the radio, the electromagnetic behaviour, the ingress and impact ratings of the assembled product; and on what the assembly does in a fire.
Procurement: Why is that commercially important? A cylinder is a cylinder.
Technical: Because a cylinder is the one part of a smart lock that has to keep working when everything else has failed. The electronics can be unpowered, the app unreachable, the network down, and the mechanical override is what gets someone into the room. For the building as a whole, the estate's master key is the fallback. So the cylinder evidence is not a minor line in the file: it is the only evidence bearing on the part that cannot be replaced without touching the door.
Procurement: Then I can say the lock conforms to EN 1303 as long as the cylinder is covered.
Technical: No, and that is the sentence to take away from this transcript. The product is not a cylinder, so a product-level claim against a cylinder standard is not a weaker claim, it is an incoherent one. The defensible formulation is narrow: this cylinder, this type, this document, this scope. If the supplier's own declaration says the product conforms to EN 1303, ask them to correct it and put the correction into the clause, so the document you hold later is coherent.
Procurement: Which raises what the lock body evidence should look like, so the two sit in one file without contradicting each other.
Technical: They sit as separate clauses with separate documents, and each carries its own boundary. A mechanically operated lock body and striking plate sit with the EN 12209 family; an electromechanically operated lock body and striking plate sit with the EN 14846 family, the closer fit for the mechanical-electrical locking function of a battery-driven lock. Multi-point locking is a different scope again, and its published title and scope should be checked before it is cited. The lock body's own clause follows the same pattern, in Writing EN 14846 Into a Smart Lock RFQ: Clause Language that Gets Real Answers.
Annotation — clause C10, the coherence clause. Any declaration in respect of the Lock identifies the cylinder as a component and references the cylinder evidence; no product-level claim against EN 1303 is made.
Turn 8 — The boundary, drawn so that it can be reused
Procurement: I want one page I can pin next to the request for quotation showing which question each standard answers, because the same file carries clauses for the lock body, the escape function, the radio and the fire doors.
Technical: Here it is. The point of the page is not decoration: it stops a clause being borrowed for a claim it cannot support, in both directions — in your tender pack, and in the supplier's marketing, which will quote your request for quotation back to you.
graph TD
REQ["What a cylinder document covers"] --> SCOPE["Durability and resistance to attack"]
REQ --> KEYC["Key control characteristics"]
REQ --> CORR["Corrosion class in later editions"]
REQ --> EXCL["What it is silent about"]
EXCL --> OUT1["The lock case, latch and deadbolt"]
EXCL --> OUT2["The electronic locking function"]
EXCL --> OUT3["The escape function of the lock body"]
EXCL --> OUT4["The radio and electromagnetic behaviour"]
EXCL --> OUT5["The ingress and impact rating"]
EXCL --> OUT6["The fire and smoke door assembly"]
NEIGH["A separate clause answers each neighbouring question"] --> LOCKBODY["EN 12209 and EN 14846 families for lock bodies"]
NEIGH --> ESCAPE["EN 179 and EN 1125 for escape devices"]
NEIGH --> RADIO["The radio and electromagnetic route for each destination market"]
NEIGH --> FIRE["The assembly route for fire and smoke doors"]
| Requirement a buyer may want | The standard or regime that answers it | What the EN 1303 clause must not be used for |
|---|---|---|
| Cylinder performance, resistance to attack, key control | EN 1303 | The lock body or the electronic locking function |
| Mechanically operated lock, latch and striking plate | The EN 12209 family | Cylinder durability or key control |
| Electromechanically operated lock body and striking plate | The EN 14846 family | Any claim about the cylinder type fitted inside it |
| Escape by lever-operated device | EN 179 | The cylinder's contribution to escape |
| Escape by panic bar | EN 1125 | The lever-operated device requirement |
| Radio and electromagnetic behaviour | The radio and electromagnetic regimes per destination market | Mechanical durability, cylinder resistance or key control |
| Ingress and impact protection of an outdoor unit | The ingress and impact rating system | Any durability or attack-resistance requirement |
| Fire and smoke door assembly performance | The assembly test route, hardware tested with the door | Standalone hardware performance |
CONFIRM-WITH-LOCAL-FIRE-ENGINEER — where an electronic lock is proposed on a fire or smoke door, the assembly requirements, the components tested with the door and the maintenance regime that apply to that opening.
Annotation — clause C11, the reliance boundary. Cylinder evidence is not evidence for lock body performance, electronic locking function, escape function, radio or electromagnetic behaviour, ingress or impact rating, or fire and smoke door assembly performance, and may not be offered as such.
The scope limits of the standard are set out in EN 1303 for Smart Locks: Scope, Tests and What the Standard Never Proves, and the neighbouring multi-point standard is compared in EN 1303 Versus EN 15685: Which One Applies to Your Smart Lock Door.
Turn 9 — Reading the answers that come back
Procurement: I now have the right questions. But suppliers reply in paragraphs and I need a way to read them that is not just about tone.
Technical: Grade the answer, not the tone, and grade it against a fixed checklist. A long reply that names the document type, the holder, the scope, the cylinder type, the production site of the cylinder and the change-notification route is a strong answer. A reply that says the product meets all applicable international standards is not an answer at all, and it should be returned on the day it arrives.
| Signal in the reply | Reading | Action |
|---|---|---|
| Third-party document with scope, type entry matching the quoted cylinder | Answerable | Check the type entry against the purchase order line |
| A declaration stating the whole product conforms to EN 1303 | Category error | Return for correction; the product is not a cylinder |
| Cylinder bought in, with the maker's scope supplied | Answerable in principle | Require the chain clauses and the declaration |
| Document whose scope names a different cylinder family | Wrong object | Re-ask using the type designation from the object schedule |
| An edition cited with no amendment statement | Ambiguous | Ask for both, using the edition clause |
| An undertaking to provide the document after the order | Not in existence at award | Make the timing binding before quotations are compared |
Procurement: Is there a way to make the judgement objective?
Technical: Set the rung you are buying at before the request for quotation goes out, and write it into the evidence schedule. The rungs run from a marketing image at the bottom, through a self-declared declaration, a test report on a sample, a third-party certificate with a scope and a number, a certificate covering the exact type you are buying, up to production-control evidence that keeps it valid after the sample passed. The ladder's value is not that the top is always necessary but that the programme must know which rung it stands on, because the recurring failure is buying near the bottom and discovering at installation that nothing above it existed. For en 1303 smart lock rfq clause, the position on this ladder is what the purchase decision turns on.
Annotation — clause C12, the rung. The Buyer is purchasing at the evidence rung stated in the evidence schedule, and a lower rung may not be substituted.
Turn 10 — Rewriting the weak cylinder clauses
Procurement: Put the clauses we drafted next to what they should have said.
Technical: Here is the rewrite set. Read the middle column first — the failure each weak clause invites — then the right-hand column.
| Weak clause | What it fails to bind | Clause as it should read |
|---|---|---|
| Smart lock shall comply with EN 1303 | Object, document, holder, date | The key cylinder incorporated in the Lock, identified in the object schedule, shall be shown to conform with the current published edition of EN 1303 by [document type] from [holder] whose scope covers that cylinder type, provided before [milestone] |
| Cylinder to EN 1303 as per sample | Which sample, which clauses, which edition | The Supplier shall provide the report issued for the cylinder type in the object schedule, showing the sample description, the clauses tested and the edition and amendment applied |
| CE certificate to be provided | Whether EN 1303 is inside the scope of that mark | The marking and its supporting declaration in force for each destination market, provided separately from the cylinder evidence, with the two confirmed consistent |
| Factory approved to EN 1303 | Who attests, for which scope, for which site | The holder of the document named with number and scope attached, and the production site of the cylinder covered stated |
| Latest edition of EN 1303 shall apply | What happens when it changes mid-order | The edition and amendment cited stated on the document, and any superseding edition notified before shipment with a statement of validity |
| Lock shall provide emergency key access | Which cylinder, which evidence, which duty | The cylinder used for mechanical override identified, with its position in the Lock, its key control configuration and the evidence covering it |
| Product shall comply with all applicable standards | Everything, which binds nothing | Each requirement evidenced by the document type named in the evidence schedule, and no requirement answered by a document produced for another |
Procurement: Several of these are ones I have sent.
Technical: Most of them are ones everybody has sent, which is why the request for quotation has to be a controlled document rather than a set of inherited table rows, and why the template behind it is worth reviewing before the next issue rather than after it. The Smart Lock Supplier Due Diligence Checklist and the Hotel Smart Lock RFQ Guide are the documents to hand to whoever maintains the template, with the international version in the Smart Lock RFQ Guide for International Buyers.
Turn 11 — Sending the clause set, and where it has to live
Procurement: How do I introduce sixteen clauses to a supplier list without it reading as an accusation?
Technical: Frame it as the basis on which quotations will be compared. Every respondent is asked the same clauses in the same form for the same document types, so the comparison is fair and the programme can move. Say that the request for quotation is being reissued this cycle with a defined evidence schedule, that it applies to all respondents equally, and that the evidence requested is what the consultant and the approving authority will need to read.
Procurement: And the sixteen clauses cover cylinders only?
Technical: Say what the set does and does not cover, because that is what lowers the temperature. Most request for quotations write one requirement line per standard and let the respondent guess which product it lands on; if your clause set says the EN 1303 clauses apply to the cylinders in the object schedule and to nothing else on the product, the supplier knows you understand the standard.
Procurement: What if a supplier objects to one clause, or offers the evidence after the order?
Technical: Ask them to state the clause and what they would propose instead, in the same structure: requirement, document, object, holder, timing, consequence. If the answer is that the evidence does not exist in a form that meets the clause, that is a finding, and it is a finding you want before you award. And if the evidence is offered only after the order, decide deliberately: either it is a condition of award, so the comparison is made on documents in hand, or it is a condition of shipment, so it is a different clause with a different consequence. Writing evidence to follow without a date and a consequence is how a programme discovers at goods-in that it bought a claim rather than a document.
Procurement: Once I award, does the clause set survive? Our contract template has a product specification annex and a quality clause, and neither knows anything about cylinders.
Technical: This is where most EN 1303 clauses die. A request for quotation is an invitation; a contract is an obligation. If the clause set does not appear in the contract, the evidence obligation expires at award. So the clauses you want to keep — the object schedule, the document type, the edition, the chain, the change notification, the consequence — are repeated in the contract, and the annex becomes the object schedule. Two must survive intact: the coherence clause, which stops an incoherent conformity claim reappearing later in the file, and the change-notification clause, which catches the upstream type change nobody told you about.
Annotation — clause C13, the evidence schedule. One row per clause: reference, document type, object, holder, date and milestone. A clause with no row is a clause nobody is working on.
Annotation — clause C14, the consequence. Failure to provide the document by the stated date entitles the Buyer to reject the quotation, remove the product from comparison, or withhold the order.
Annotation — clause C15, change of product or route. A proposed change to designation, cylinder type, production site or route requires reissue and re-satisfaction of the schedule.
Annotation — clause C16, the contract repetition. The requirements and the object schedule are annexed to the contract and repeated there.
The annotated cylinder clause sheet
Collected, the clauses below are what a request for quotation would carry. They are written to be lifted, and the bracketed fields are the ones only the programme can fill in.
| Ref | Clause as it should read | Document that must exist | Bound to |
|---|---|---|---|
| C1 | The key cylinder in the Lock shall be shown to conform with the current published edition of EN 1303 by [document type] from [holder] whose scope covers the cylinder type, provided before [milestone] | Third-party document | Supplier |
| C2 | A schedule lists each cylinder by function and position, with type designation, profile, length, cam position and finish as quoted | Object schedule, dated product page | Buyer |
| C3 | The requirement applies only to the cylinders in the object schedule and to no other part of the product | Boundary statement | Buyer |
| C4 | For a purchased-part cylinder, the Supplier identifies the type as incorporated, provides the third-party document with its scope, provides a signed declaration referencing it, and states the production-control arrangement | Type entry, document, declaration | Supplier |
| C5 | The declaration identifies the party, the signatory and capacity, the product, the cylinder type, the document relied upon and the date | Signed declaration | Supplier |
| C6 | The document type is named; a summary, extract, bare number or image does not satisfy the clause | The full document | Supplier |
| C7 | Conformity is to the current published edition including any amendment in force at the date of issue, cited on the document | Edition statement | Supplier |
| C8 | The Supplier notifies before shipment if the cited edition, the cylinder type or the production site changes, and states whether the document remains valid | Supplier notification | Supplier |
| C9 | The key control configuration, key quantities as quoted, master key relationship per position and compatibility with the Buyer's keying schedule are stated | Statement and keying schedule | Supplier |
| C10 | Any declaration identifies the cylinder as a component and references the cylinder evidence; no product-level claim against EN 1303 is made | Declaration in the required form | Supplier |
| C11 | Cylinder evidence may not be relied upon for lock body performance, electronic locking function, escape function, radio or electromagnetic behaviour, ingress or impact rating, or fire assembly performance | Boundary statement | Buyer |
| C12 | Responses are evaluated at the rung stated in the evidence schedule and a lower rung may not be substituted | Evidence schedule | Buyer |
| C13 | The evidence schedule holds one row per clause with document type, object, holder, date and due milestone | The schedule itself | Buyer |
| C14 | Failure to provide the document by the stated date entitles the Buyer to reject the quotation, remove the product from comparison, or withhold the order | Consequence clause | Buyer |
| C15 | A proposed change to designation, cylinder type, production site or route requires reissue and re-satisfaction of the schedule | Change notification | Supplier |
| C16 | The requirements and the object schedule are annexed to the contract and repeated there | Contract annex | Buyer and Supplier |
Two fields decide most of the value of the sheet: the milestone in C1 and C13 decides whether you are comparing documents or comparing promises, and the consequence in C14 makes the milestone real.
What this transcript cannot settle about a cylinder
The transcript cannot tell you whether your doors need a cylinder in that position, or which cylinders the building's existing key system can absorb. That is a question about the door schedule, the estate's keying design and the local access-control practice, and those answers do not travel between projects.
It cannot tell you which conformity route your market applies to the product, or which party in the supply chain carries the legal obligation to hold and to produce the declaration. In several markets that obligation sits with the importer rather than the factory, and elsewhere door hardware sold as a construction product runs through a route that produces a Declaration of Performance rather than only a declaration of conformity.
CONFIRM-WITH-LOCAL-LEGAL-ADVISER — which conformity route applies to the cylinder and to the lock in each market you are supplying, whether a Declaration of Performance is required in addition to a declaration of conformity, and which party carries the legal obligation to hold and to produce it.
CONFIRM-WITH-LOCAL-REGULATORY-CONSULTANT — whether the marking on the product and the cylinder evidence supplied under clauses C1 to C9 are consistent, and whether the mark needed differs from the mark already on the product for each destination market.
It also cannot tell you how much evidence is enough. That is a programme risk decision, and the ladder lets you make it explicitly and in writing.
What to take into the request for quotation
- List the cylinders, not the lock: one row per cylinder by function and position, with type and configuration from the dated product page for the exact variant quoted.
- Name the document type in the clause, find out who holds the evidence, and set the evidence rung and milestone before quotations arrive.
- State the boundary in the document, and repeat the clauses in the contract with the object schedule annexed.
- Watch the upstream events: an edition or cylinder type change reaches you through a party who is not your counterparty, so the notification obligation has to be written into the clause.
The Smart Lock Supplier Due Diligence Checklist and the Hotel Smart Lock RFQ Guide are the documents to hand to a supplier. The order samples page describes the product-side review, the certifications page the conformity documentation route, and request a quote the route where a scoped enquiry saves a round of correspondence.

