EN 1303 in a Smart Lock Tender Pack: The Evidence Checklist
This article separates what can be shown from what has to be confirmed, and en 1303 smart lock tender evidence is where that line is drawn. Three tender packs land on the same desk in the same week for the same smart-lock programme. One is a folder of PDFs named by document type. One is a single certificate whose scope line the panel cannot parse. One is a printed specification sheet with a market mark printed in the corner and a line that reads "EN 1303". The panel will score them against each other, so the first thing to fix is not the products. It is the shape of the packs.
Direct answer. Short version — en 1303 smart lock tender evidence is treated here as en 1303 smart lock tender evidence first. en-1303 comes second. The evidence for en 1303 smart lock tender evidence is named in the sections below. an en 1303 smart lock tender evidence turns conformity language into requests a buyer can send. en 1303 smart lock tender evidence is where those en 1303 smart lock tender evidence requests get written down.
- What comes from the factory — supplier declarations and drawings for en 1303 smart lock tender evidence
- What needs an external body — third-party certificates covering the exact scope of en-1303
- What to order — the document set that matches the SKU behind en 1303 smart lock tender evidence
- For en 1303 smart lock tender evidence, the order below is fixed and en 1303 is the reference point.
The discipline behind en 1303 smart lock tender evidence is straightforward: rebuild the pack as a question-indexed document set where every line names one tested object, one document type and one scope the panel may accept. A designation is a question, not an answer. The pack exists so that the panel can see which question each document actually answers, and what it leaves unanswered.
EN 1303 is a standard for cylinders for locks. It describes what it tests: durability, security, key control, resistance to picking and drilling, and corrosion classes in later editions. It says nothing about the lock body, the motor, the radio module or the building. Nothing in this guide is a conformity assessment, a legal opinion, or a statement that any product holds any designation.
Why three supplier packs can look identical and mean different
The common tender failure is not a missing document. It is a document whose type nobody stated, so the panel cannot tell what it is allowed to support.
| Wording in the pack | What it may actually be | Question to put in the request | Acceptable substitute for the panel |
|---|---|---|---|
| "We have EN 1303" | A test report on a sample, a family certificate, or a sales statement | Which document type, and which object did it cover | A named document with its type stated |
| "Fully CE marked" | A mark printed on a label, a declaration, or a self-declared route | Which of the four document types sits behind the mark | The declaration with signature and date, plus its technical basis |
| "Tested to the standard" | A report written against an edition that has since changed | Which edition was the report written against | The current edition and a scope note |
| "High-security cylinder" | A marketing descriptor with no tied result | Which property, on which object, with what result | The stated result and the document that carries it |
Keep four labels apart throughout: the test report, the certificate, the declaration of conformity and the marking. Each carries a different weight, and each has a different expiry logic. The evidence-quality ladder runs from a marketing image, through a self-declared declaration, a test report on a sample and a third-party certificate with a scope and a number, to a certificate covering the exact variant being bought, and finally to audit or production-control evidence that keeps the basis alive after the sample passed. Buying at the second rung and discovering at installation that nothing exists at the fifth is the recurring commercial failure, and it starts in the pack. The build options sit in the smart door locks. For en 1303 smart lock tender evidence, the position on this ladder is what the purchase decision turns on.
The pack index: seven tabs and the question behind each
A tender pack should be an index of questions, not an index of suppliers. The same seven tabs apply to every supplier so that the panel compares answers in the same order.
| Tab | Question the tab answers | Typical contents | Owner | Pass marker |
|---|---|---|---|---|
| 1 | Which cylinder, in which lock, is being bought | Identity sheet and revision history | Supplier | Ordering code, cylinder and lock body all named |
| 2 | Does the current published scope reach this object | Applicability note with edition and date checked | Buyer or compliance | Published title, edition and scope sentence recorded |
| 3 | What evidence exists and what does each item prove | Evidence register with four document labels | Supplier and buyer | One row per document with type and scope stated |
| 4 | Does the tested sample match the ordered variant | Variant cross-reference and change notes | Supplier | Every difference explained or evidence re-opened |
| 5 | Which questions this pack cannot answer | Exclusion register with routes | Buyer | Each excluded question has an owner elsewhere |
| 6 | Which market route applies to the destination | Market-access file and responsible party | Importer or supplier | Framework, signatory and documents identified |
| 7 | What remains open and who closes it | Open-items sheet | Buyer | Each item has evidence required, owner and tab |
erDiagram
TENDER_PACK ||--o{ PACK_TAB : holds
PACK_TAB ||--o{ EVIDENCE_ITEM : lists
EVIDENCE_ITEM }o--|| CLAIM : supports
EVIDENCE_ITEM }o--|| DECISION_RECORD : feeds
DECISION_RECORD ||--o{ OPEN_ITEM : raises
TENDER_PACK {
string pack_reference
string sku_code
string destination_market
string pack_state
}
PACK_TAB {
string tab_number
string tab_purpose
string tab_owner
string tab_state
}
EVIDENCE_ITEM {
string document_type
string issuer
string reference_number
string issue_date
}
CLAIM {
string claim_text
string tested_object
string stated_result
}
DECISION_RECORD {
string decision_code
string scope_accepted
string approver_role
string record_date
}
OPEN_ITEM {
string item_text
string owner_role
string closing_evidence
}
Tab 1: the identity sheet names the cylinder, not the brand
A cylinder result belongs to a cylinder. The identity sheet is what ties a document to something the buyer can actually order, and it is the tab most often left thin.
| Field | What to record | Why the panel needs it |
|---|---|---|
| Ordering code and variant | The exact string on the quotation, including finish and revision | Most failures trace back to a pack written for a family |
| Cylinder presence | Present, removable, integrated or absent | A standard written for cylinders for locks has nothing to say about a product with no cylinder |
| Cylinder type and interface | Profile, key interface, and who assigns the key system | Key-control statements only make sense against an interface |
| Lock body around it | Mortise, rim, multi-point or retrofit kit | A cylinder result does not travel into the body |
| Test object wording | The words the report uses for what was tested | The only way to compare a document with an order |
| Destination and project type | Country, building type, intended use | Drives the market-access file and the installation context |
| Change history | Supplier, component and revision changes since testing | Decides whether tab 4 can stay closed |
Where the smart lock is an electromechanical product, the mechanical and electrical locking function belongs to a different document family, and EN 14846 is the closer fit for that question than a cylinder standard. A working record of that boundary is available in EN 1303 for Smart Locks: Scope, Tests and What the Standard Never Proves.
Tab 2: the applicability note is written as a scope question
The note is one paragraph, and it answers four things: the published title of EN 1303 as it stands now, the edition relied on, the date and the name of the person who checked, and the scope sentence quoted from the published text. Editions change, so a note that says "to EN 1303" without a checked date is a gap, not a scope statement.
Write the note so the reader can audit it. Something like this: the current edition of EN 1303 carries the published title X; the supplier's claim concerns the cylinder described as Y; the published scope reads Z; Y sits inside Z on the strength of the description in tab 1.
Three errors make the note useless. Treating the designation as a product approval, extending a cylinder scope to the complete lock, and assuming the edition cited inside a report is the edition in force today. Where the claim touches a neighbouring designation, write the check rather than the conclusion: for machine-assisted cylinder operation, check the published title and scope of the current edition of EN 15684; for multi-point locking, check the published title and scope of the current edition of EN 15685; for the electromechanical locking function itself, check EN 14846.
CONFIRM-WITH-LOCAL-CONFORMITY-ASSESSMENT
For the case where two designations are both plausible, EN 1303 Versus EN 15685: Which One Applies to Your Smart Lock Door works through the choice rather than the paperwork.
Tab 3: the evidence register carries four labels and one
One row per document. No exceptions, and no document left out because it looked unimportant. The register is the table the panel reads twice.
| Document type | Identity fields that must appear | What it can support | What it cannot support |
|---|---|---|---|
| Test report | Issuer, sample description, edition, tested properties, results, date | A stated result on the named sample | Conformity of later production units |
| Certificate | Issuing body, verifiable number, scope, validity period | Conformity within the stated scope and window | Anything outside the scope, or a variant it does not name |
| Declaration of conformity | Legal manufacturer or responsible party, framework, signature, date | The declared party's own legal claim | Independent testing, or a SKU the declaration does not reference |
| Marking | Exact location on product or label, and the document behind it | Which mark was applied, and where | Test results, certificate validity or complete product compliance |
| Audit or production-control record | Scope of the control, who performed it, period covered | That the basis continues after the sample passed | A new product configuration that was never sampled |
Give the register these columns so nothing is implied: row number, document type, issuer, reference number, issue date and validity, object covered, edition referenced, result actually stated, permitted wording, and the tab where the item is used. Then write the permitted wording in full, because that sentence is what travels into the evaluation summary.
Two working habits keep this tab honest. Record the sample result as a sample result, and state certification status as CONFIRM-PER-SUPPLIER until a named report, an issued certificate with a verifiable number and scope, or a signed and dated declaration is attached. For the line-by-line reading of a report, use Reading an EN 1303 Test Report Page by Page: A Smart Lock Buyer Walkthrough. For clause language that survives comparison, use Buying a Cylinder, Not a Lock: The EN 1303 Clause a Buyer Can Actually Use.
Tab 4: the variant cross-reference survives a supplier change
A cross-reference is a controlled mapping, not a visual resemblance. It states the ordering code, the cylinder fitted inside it, the lock body, the configuration in which the sample was tested, and every difference the buyer knows about.
| Change since the sample was tested | Evidence action | Tabs to reopen |
|---|---|---|
| Cylinder supplier or construction changed | Change note, plus confirmation that the fitted cylinder is the tested cylinder | 3 and 4 |
| Lock body or mechanism changed | Variant cross-reference or new evidence for the changed body | 3, 4 and 5 |
| Firmware or credential side changed | Separate electronics evidence; the cylinder tab stays as it is | 5 |
| Standard edition changed | Re-check the scope note and any classification reference | 2 |
| Destination market changed | New market-access file for the new destination | 6 |
| Supplier or evidence holder changed | Provenance and the record of who holds the evidence | 3 and 7 |
Any dimension, read distance, cycle count, battery-life statement or environmental rating that carries weight in the purchase decision must be confirmed on the dated product page for the specific SKU. No standards document repairs a missing product-page datum, and no cross-reference should be used to carry one.
Tab 5: the exclusion register names what this pack cannot answer
The most expensive line in a tender pack is the one that answers a question nobody asked the document. Keep the excluded questions in the pack, in writing, so that nobody later mistakes silence for coverage.
| Question a buyer may ask | Where that question belongs | Note for the panel |
|---|---|---|
| Mechanical lock durability and function of the body | EN 12209 family | Not electronically driven locking |
| Electromechanical locking performance of the lock | EN 14846 family | Closer fit for a battery-driven product |
| Multi-point locking of the door | EN 15685 route | Check the published title and scope |
| Handle and knob furniture | EN 1906 family | Furniture, not the mechanism |
| Emergency escape operation | EN 179 or EN 1125 | Egress function is its own question |
| Fire and smoke performance | EN 1634-1 assembly route and the EN 14637 family | Hardware is assessed inside the door assembly |
| Radio and electromagnetic compatibility | The applicable radio and EMC regime | A battery lock, a gateway and an adaptor may sit in different routes |
| Electrical safety of mains-powered parts | The applicable low-voltage and safety route | Confirm which item is in scope |
| Ingress and mechanical impact | IEC 60529 and EN 62262 codes | Ask for the tested item, not the marketing phrase |
| Battery cells and transport | IEC 62133 and UN 38.3 evidence | A forwarder asks for this before it accepts the shipment |
| Event logs, credentials and hosting | Data-protection and security documentation | Logs that identify who opened what are personal data |
CONFIRM-WITH-LOCAL-MARKET-ACCESS-AND-ELECTROMAGNETIC-COMPATIBILITY-REVIEW
Tab 6: the market-access file states who signs and for where
This tab is where destination obligations are recorded, and it is where the buyer most often discovers that a mark on the enclosure was never tied to a document the buyer can rely on.
Ask for: the destination country, the responsible economic operator placing the product on that market, the framework the supplier believes applies, the document behind every mark shown, the signatory of the declaration, whether the hardware is placed as a construction product, the radio authorisation route for the fitted module, the route that covers any charger or adaptor, and the identity of the party that controls credentials and event logs. Where a registration scheme places the obligation on the importer rather than the factory, that allocation belongs in the file, because it changes who has to act before shipment.
Marks that may appear include CE, UKCA, RCM, KC and G-Mark. The presence of a mark is a fact about the label, not evidence of what was tested. Ask for the document behind it.
CONFIRM-WITH-LOCAL-MARKET-ACCESS-REVIEWCONFIRM-WITH-LOCAL-LEGAL-AND-CONFORMITY-REVIEW
Acceptance practice differs by market, and the same pack can be read differently in different places. EN 1303 in the United Kingdom Purchasing Practice: What Buyers Are Asked to Produce covers one of those readings.
Tab 7: the open-items sheet is what carries the pack forward
Open items are normal. A tender pack that pretends nothing is open is a pack that has been tidied for presentation. The sheet is what makes the tidying honest.
| Column | Entry rule |
|---|---|
| Item | The unresolved question in one line, phrased as a question |
| Why it is open | The document gap or scope gap that created it |
| Evidence that closes it | The specific document, mapping or statement that would settle it |
| Owner | Named role inside or outside the buying team |
| Tab to reopen | Where the answer goes when it arrives |
Give every item an owner and a closing evidence. An item with no owner is not open, it is unassigned, and it should be counted as an unanswered question in the evaluation summary. When the supplier returns a replacement document, attach it to the item it closes and note why the earlier document was insufficient, rather than starting a fresh history.
The acceptance test: what each tab must show before it passes
| Tab | Passes only when | Fails when |
|---|---|---|
| 1 | Ordering code, cylinder and lock body are named and consistent | The pack describes a family or a photograph |
| 2 | Published title, edition, scope sentence and date of check are recorded | The note says "to EN 1303" with no edition |
| 3 | Every document is typed, dated, referenced and tied to an object | Several document types are merged into one claim |
| 4 | Every known difference is explained or the evidence is re-opened | The sample is matched by appearance |
| 5 | Each excluded question has a named route and an owner | A cylinder document is used for radio, fire or egress questions |
| 6 | Framework, signatory and documents are identified for the destination | A mark appears with nothing behind it |
| 7 | Every open item has an owner and a closing evidence | A verbal assurance closes a line |
Apply the test tab by tab. A later satisfactory document cannot repair a failed earlier tab unless the gap is closed explicitly and recorded, and a verbal assurance is not a passed tab. Where a tab cannot close, the request stays open. A precise request for a variant cross-reference or a dated product record is more useful to both sides than a plausible family match.
Reject reasons that come back again and again
| Reason the pack is sent back | What it looks like | The request that fixes it |
|---|---|---|
| No document types stated | Files named by supplier reference only | Ask for each item labelled as report, certificate, declaration or marking |
| Family-level evidence only | A certificate whose scope names a range of models | Ask for the cross-reference that names the ordering code |
| Wrong edition referenced | A report written against a superseded edition | Ask which edition applies now and what changed |
| Object never described | Results listed without stating the tested object | Ask for the object description in the report's own words |
| Expired or undated evidence | A certificate with no window, or a document with no date | Ask for the current version and its validity |
| An excluded question answered anyway | Cylinder durability used for radio or fire performance | Ask the question to be routed to the right family |
| Product data mixed with standards evidence | Specifications presented as conformity | Ask for the source of each figure on the dated product page |
Record each return as a controlled change with a reason code, so the panel can see which suppliers resolve requests and which ones restate their marketing. The deeper failure patterns behind these returns are examined in Three Ways EN 1303 Evidence Disappoints Smart Lock Buyers.
Reading order for the panel and the decision record
The panel reads tabs 1, 2, 3 and 4 before any commercial discussion, because a claim that cannot be tied to an object cannot be scored. Tab 5 is read before the exclusions are closed, tab 6 before any market conclusion is drafted, and tab 7 last, because it is the record of what is still moving.
| Decision | When it applies | What the record states | What follows |
|---|---|---|---|
| Released for the cylinder claim | Scope, variant and current evidence align | The accepted scope, the document relied on and the object it covers | Market-access and installation review continue |
| Released with conditions | A bounded gap remains with an owner and a closing evidence | The condition, the owner and the tab to reopen | Condition tracked to closure before commercial release |
| Held | Evidence does not reach the ordered variant, or a safety question is open | The missing item in precise terms | The request stays open; no acceptance is recorded |
| Out of scope for this claim | The questioned function belongs to another family | Which family answers it and who owns that question | The question is routed, and EN 1303 is not the basis |
Where classification or grade numbers appear in a supplier's material, the notation has to be decoded before it can be compared, and Decoding EN 1303 Class and Grade Numbers for Door Hardware sets out how those numbers behave. Where the panel needs to know who carries the cost and the custody of each piece of evidence, Who Pays for EN 1303 Evidence in a Smart Lock OEM Programme covers the ownership question. The supplier-side view of the same pack is set out in Smart Lock RFQ Guide for International Buyers.
What the pack may not contain
A tender pack is a controlled document set, so it also has a short list of things that must not appear in it.
- No claim that a product holds a certification, in any market-access wording, unless the file carries the document behind it.
- No promised delivery, service-life, failure-rate or warranty figure used as a substitute for evidence.
- No product specification presented as a conformity result.
- No document used to answer a question outside its scope.
- No unqualified conformity wording on a product page or in a marketing image.
- No undated, unnumbered or unattributed evidence. For en 1303 smart lock tender evidence, the position on this ladder is what the purchase decision turns on.
The pack supports procurement qualification. It is not legal advice, not a conformity assessment, and not a conclusion about any installation or building. The market-access route, the responsible party and the approving authority are established for the destination and the exact product.
CONFIRM-WITH-LOCAL-CONFORMITY-ASSESSMENT
Returning the pack to the supplier
Send the request as a line-by-line list against the seven tabs, so that a response can be answered in the same order. For each missing item, name the document type you need, the object it must cover, the edition or framework it should reference, and the date or reference that would identify it. Say which items block the evaluation and which ones only need to close before release, because those two categories are handled differently and mixing them slows the whole file.
Keep the outcome short. The supplier receives a pack they can complete; the buyer receives a decision record that states the accepted scope, the open items and the owners. If a manufacturer is preparing the same set for a customer-facing programme, the wider document set is described in What Documents Should You Request From a Smart Lock Supplier?, and the supplier-side checks sit in Smart Lock Factory Audit Checklist for International Buyers.
A tender pack earns its place when it makes the evidence comparable. Index it by question, label every document, tie each result to an object, write the questions the pack cannot answer, and record the decision in the same words you would use in the contract. That is the whole of en 1303 smart lock tender evidence: a cylinder standard used to answer cylinder questions, with every other question sent where it belongs.
If you want the equivalent pack prepared for a specific smart-lock programme, send the door and product details through our quote request, or ask for sample units and review the enclosure, the model marking and the documentation set together before the tender opens.

