En 1303 smart lock scope limits: A practical EN 1303 scope and evidence runbook helps procurement qualify smart-lock cylinder claims without overstating.

게시일: 11월 21, 2025

EN 1303 for Smart Locks: Scope, Tests and What the Standard Never Proves

EN 1303 for Smart Locks: Scope, Tests and What the Standard Never Proves

Procurement often receives a folder labelled “EN 1303 evidence” and treats it as approval of a complete smart lock. The en 1303 smart lock scope limits are clearer when the buyer separates three objects: the cylinder, the complete lock, and the product presented for purchase. EN 1303 is a standard for cylinders for locks, with coverage centred on durability, security, key control, resistance to picking and drilling, and corrosion classes in later editions. It is not a complete smart-lock approval system.

Direct answer. Short version — en 1303 smart lock scope limits is treated here as en 1303 smart lock scope limits first. en-1303 comes second. The evidence for en 1303 smart lock scope limits is named in the sections below. an en 1303 smart lock scope limits is the conformity record. One en 1303 smart lock scope limits claim sits with the manufacturer. Another needs an accredited laboratory. en 1303 smart lock scope limits settles which is which.

On en 1303 smart lock scope limits, this article uses en 1303 smart lock scope limits as the definition. It treats en 1303 smart lock scope limits as a working definition specific to this market and product, rather than a general one.

This Ops Runbook is a qualification workflow, not a test report or certificate. It tells a Procurement Manager what to collect, where the evidence must point, which adjacent standards must answer the remaining questions, and when to hold approval. The output is a traceable scope decision for an exact SKU, not a substitute for supplier evidence or a local compliance decision.

1. Runbook control and release rule — en 1303

Run the procedure for every smart-lock SKU, market, and mechanical configuration. Reopen it when the cylinder, lock body, supplier, evidence document, or destination changes.

Control fieldRunbook instruction
Accountable roleProcurement Manager
TriggerNew SKU, supplier change, cylinder change, tender, or evidence renewal
Required inputArchitecture, exact SKU, destination, supplier evidence, and claimed scope
Controlled outputCylinder-scope decision with evidence references and unresolved questions
Stop conditionMissing scope, unmatched test object, expired evidence, or unresolved safety question
Internal referenceen-1303

A released decision must identify what the evidence supports and what remains outside it. Silence about an excluded function is not acceptance of that function. What can be supplied is listed in the smart door locks.

2. Build the product and door record

Do not classify the purchase from the words “smart lock” on a quotation. Obtain the product architecture before selecting a standard. The mechanical cylinder may be a separate component, may be integrated into the lock, or may be absent.

Intake fieldEvidence to request
Exact product identifierOrdering code, variant, colour, and production revision
Lock architectureMechanical, electromechanical, or mechatronic configuration
Cylinder presencePresent, absent, removable, or integrated
Cylinder constructionProfile, key interface, and manufacturer assignment
Mechanical functionLatch, bolt, deadbolt, or multi-point engagement
Test objectThe individual cylinder, lock set, or complete assembly evaluated
InstallationNew door, retrofit, frame change, or replacement project
DestinationCountry, project type, and intended use
EvidenceReport, certificate, declaration, and supporting correspondence
Change historySupplier, component, software, and manufacturing revisions

Use the Office Smart Lock Site Survey to record physical requirements before evaluating claims. For an existing opening, the Smart Lock Retrofit Site Survey helps separate door constraints from cylinder evidence.

3. Apply the EN 1303 scope gate

Check the published title and scope of the current edition of EN 1303 for every project. Edition changes matter, and the supplied product description is not a substitute for the standard text.

Purchase configurationQuestion for the buyerRunbook action
Mechanical cylinder bought separatelyIs the cylinder itself the product being qualified?Continue through the EN 1303 evidence gates
Cylinder integrated in an electromechanical lockWhich physical object was tested?Evaluate cylinder evidence separately from lock-body evidence
Electronic lock without a lock cylinderIs any cylinder-based claim being made?Record EN 1303 as not applicable to that claim
Mechatronic cylinderDoes the construction involve machine-assisted cylinder operation?Check the published title and scope of EN 15684
Multi-point locking productDoes the claim concern a multi-point lock rather than one cylinder?Check the published title and scope of EN 15685
Handle or knob purchaseIs the claimed object door furniture?Route to EN 1906
Complete fire-door assemblyIs resistance claimed for the assembled door?Route to the assembly and installation requirements
Radio gateway or controllerIs the claim about wireless or electrical performance?Route to the relevant radio, EMC, or electrical-safety regime

A candidate cylinder inside a smart lock is not automatically outside EN 1303. Equally, EN 1303 evidence for that cylinder does not automatically cover the smart lock around it. The test report must identify the object and the configuration tested.

4. Mark the boundary between cylinder and lock claims

EN 1303 scope and applicability should be recorded as a boundary, not as a general security endorsement. The following are the en 1303 smart lock scope limits that matter most during qualification.

Buyer questionEN 1303 relevanceEvidence still required elsewhere
Durability of the cylinderWithin the standard’s cylinder-performance scopeDoor-cycle context and complete-lock operation
Key-control featuresRelevant to the cylinderKey-system governance and site procedures
Resistance to picking and drillingRelevant to the cylinderThreat assessment and installation security
Corrosion classificationRelevant in later editions, subject to the current scopeSite environment and material compatibility
Electromechanical locking functionOutside the cylinder’s core scopeEN 14846 or another applicable electromechanical lock standard
Radio, EMC, and electrical safetyOutside the cylinder scopeThe applicable product-specific regime
Fire and smoke performanceOutside the cylinder scopeDoor-assembly and national fire requirements
Emergency escape operationOutside the cylinder scopeEgress hardware and local life-safety review
Access-control data and cyber controlsOutside the cylinder scopeSystem, privacy, and security documentation

Use the standard to support a narrowly defined cylinder claim. Do not use it to answer whether a complete smart lock is suitable for a fire door, connected access-control system, or specific electronic-control requirement.

Read the scope as a two-way control. On one side, the purchased object must contain the cylinder that was actually evaluated. On the other, the claim being approved must remain limited to properties the cylinder test addresses. A complete lock may contain an in-scope cylinder, but that fact does not transfer every cylinder result to the lock body, electronic controller, credential reader, motor, strike, door interface, or connected system. Procurement should therefore record the physical component behind each proposed claim rather than one approval label for the entire quotation.

For every cylinder property proposed for release, create a traceable row with four fields: the physical test object, the standard or test reference identified in the evidence, the result actually stated, and the limitation carried forward. If the evidence does not identify one of these fields, send the item back as incomplete rather than filling the gap with a marketing description. The row should also identify whether the result belongs to the sample only or is supported by a certificate covering current production. This keeps the evidence-quality ladder visible in the decision rather than reducing a complex evidence set to one “passed” label.

Consider a quoted complete smart lock with a removable cylinder and an electronic controller. A report may show that a cylinder was tested for a property such as durability, key control, or attack resistance. The permitted conclusion is limited to the identified cylinder in the identified test configuration. It does not establish the durability of the complete lock, the ability of the controller to retract a bolt, radio performance, fire resistance, escape operation, access-control interoperability, or compliance of the mark shown on the enclosure. Those questions need their own route. Conversely, failure to find EN 1303 evidence does not disprove the cylinder; it means the cylinder claim is not yet supported by the required evidence. This symmetrical treatment prevents both overclaim and false rejection.

At sign-off, state the accepted conclusion in component-level language and list the excluded questions separately. That wording gives engineering, compliance, and the supplier a precise basis for correction without implying that the complete quotation has been approved by implication.

Before any approval meeting, build a claim-to-evidence matrix. Give each proposed statement its own row, with separate columns for physical object, property evaluated, evidence document, covered configuration, issuer, date or validity, and permitted procurement wording. Do not create one row saying “the smart lock passes EN 1303.” That wording combines the cylinder with the surrounding lock and may also hide an electronic or installation claim. Record any certification status as CONFIRM-PER-SUPPLIER, then link it to the named report, issued certificate with verifiable number and scope, or signed and dated declaration that supports it. If a phrase such as “high-security smart lock” cannot be tied to one object, tested property, and stated result, rewrite it as an unresolved requirement. This preserves the standard’s narrow conclusion without turning a missing record into a presumed pass.

5. Separate the four documents before trusting any claim

A supplier saying that a product has “CE” or other market evidence may be referring to several different things. Procurement must identify the document type before assessing whether it covers the exact purchase.

DocumentWhat it representsMinimum identification detailsWhat it does not prove
Test reportSomeone tested a sampleIssuer, sample description, standard edition, tested properties, results, and dateOngoing conformity of every later production unit
CertificateA body attests conformity within a defined scopeIssuing body, verifiable number, scope, validity period, and covered referencesCoverage outside the stated scope or variant
Declaration of conformityThe manufacturer or importer makes its own legal claimLegal manufacturer or responsible party, applicable framework, signature, and dateIndependent testing or coverage of an unreferenced SKU
MarkingA market mark appears on a product or labelExact location, model coverage, and supporting technical documentationTest results, certificate validity, or complete product compliance

A self-declared DoC is a declaration of conformity. It is not interchangeable with a third-party conformity certificate, although the applicable route determines which evidence is expected.

Treat Applied to en 1303 smart lock scope limits, the acceptance order runs:

  • Marketing image: a visual claim and a starting point only.
  • Self-declared DoC: the supplier’s own dated and signed claim.
  • Test report on a sample: evidence tied to the sample that was tested.
  • Third-party certificate with scope and number: an attributable attestation with boundaries.
  • Certificate covering the exact SKU or variant: evidence connected to the purchased configuration.
  • Audit or production-control evidence: evidence that the basis remains valid after the sample passed. For en 1303 smart lock scope limits, the position on this ladder is what the purchase decision turns on.

For a page-by-page evidence review, use Reading an EN 1303 Test Report Page by Page: A Smart Lock Buyer Walkthrough. For clause wording, see Buying a Cylinder, Not a Lock: The EN 1303 Clause a Buyer Can Actually Use.

6. Execute the eight-gate qualification procedure

Work through the gates in order. A later favourable document cannot repair a failed earlier gate unless the gap is explicitly closed and recorded.

GateProcurement actionRecordFail signal
1. Freeze the claimWrite the exact statement the supplier wants to supportClaim register“The smart lock is approved” without a defined object
2. Confirm applicabilityCheck the current published title and scopeStandard-reference noteThe product or test object lies outside the scope
3. Classify evidenceLabel each item as report, certificate, declaration, or markingEvidence indexSupplier mixes all four into one claim
4. Match the variantCompare model, revision, cylinder, and configurationVariant cross-referenceEvidence names only a generic family
5. Check validityReview dates, issuing body, scope, and report conditionsCurrency checkCertificate validity has ended or the sample differs
6. Route exclusionsSend unresolved questions to adjacent standards or specialistsRouting logCylinder evidence is used for electronics or fire performance
7. Review the marketObtain destination-specific advice and supporting recordsLocal-review recordMarket-access responsibility remains unassigned
8. Release or holdSelect one controlled outcome and assign actionsSigned decision recordApproval exists without traceable evidence

If gate 4 cannot be closed, keep the supplier request open. A precise request for a variant cross-reference, dated product record, or replacement report is more useful than accepting a plausible family match.

Keep the gate record even when the answer is “not applicable.” A documented not-applicable decision prevents the file from acquiring an orphan certificate that is later reused for a different claim. At gate 2, record the published title, edition, scope statement, and date checked. At gate 4, document how the ordering code, cylinder, and mechanical revision map to the test object. At gate 5, preserve the issuer, report or certificate number where one exists, validity dates, and any restrictions on use. A blank or verbal assurance is not a passed gate. If the supplier sends a replacement document later, link it to the failed gate, record why the earlier evidence was insufficient, and re-run the downstream gates affected by the change. This preserves an auditable sequence from claim to release.

7. Route unanswered questions to the right standard

Never combine the questions answered by a cylinder-performance standard, an electromechanical lock standard, a fire-door test, and a radio regime. Use the table as a routing map, then verify the published title and scope of the current edition.

Unanswered questionApplicable family or routeBoundary to preserve
Mechanical lock durability and functionEN 12209Does not cover electronically driven locking
Electromechanical lock and striking-plate performanceEN 14846Closer fit for a battery-driven smart lock’s mechanical-electrical function
Machine-assisted cylinder operationEN 15684Check the published title and scope for the current edition
Multi-point lockingEN 15685Do not apply automatically to a single-point product
Handle and knob furnitureEN 1906Does not test the lock mechanism
Emergency escape hardwareEN 179 or EN 1125Egress function is separate from cylinder performance
Fire-door assembly resistanceEN 1634-1 and applicable EN 14637 routesHardware is evaluated within the relevant assembly
Radio and EMC performanceApplicable EU RED, EMC, or LVD routeA battery lock, gateway, and adaptor may have different routes
Ingress, impact, batteries, and transportIEC 60529, EN 62262, IEC 62133, and UN 38.3 as applicableEach addresses a different physical or transport question
flowchart TD
    A[Receive SKU and claim] --> B{Physical cylinder in scope}
    B -->|No| C[Record EN 1303 as not applicable]
    B -->|Yes| D[Check published title and scope]
    D --> E[Map test object to exact SKU]
    E --> F[Review report certificate or declaration]
    F --> G{Exact variant covered}
    G -->|No| H[Hold and request scoped evidence]
    G -->|Yes| I[Route adjacent questions]
    I --> J[Complete local market review]

For the adjacent-standard decision, EN 1303 Versus EN 15685: Which One Applies to Your Smart Lock Door provides a focused comparison. For an existing opening, also review EN 1303 When Retrofitting Smart Locks Onto Existing Doors.

CONFIRM-WITH-LOCAL-MARKET-ACCESS-AND-RADIO-REVIEW

8. Lock the evidence to the exact purchased variant

A family name, project family, or visual similarity is not a variant cross-reference. The evidence file must connect the document to the exact ordering code and any changed mechanical component.

Control questionAcceptable supporting recordUnacceptable shortcut
Which SKU was tested?Model and revision stated in the report or controlled mappingA family brochure
Which cylinder was fitted?Cylinder designation and configuration“High-security cylinder” without identification
Which lock body surrounded it?Complete test-object descriptionA photograph of the marketed product
What changed after testing?Supplier change note or dated product-page recordSilence
Which specifications drive the purchase?Dated specification for the exact SKUA catalogue page for a similar model

Any lock dimension, read distance, cycle count, battery-life statement, or environmental rating used in the purchase decision must be confirmed on the dated product page for the specific SKU. EN 1303 evidence cannot repair a missing product-page datum.

9. Separate technical qualification from market access

Ask the supplier to identify the destination, responsible economic operator, applicable framework, and evidence for every mark shown. Ask which authority signs off, what document sits behind the mark, and whether the document covers the exact variant.

  • Marking: If CE, UKCA, RCM, KC, or G-Mark appears, request the underlying technical file and scope. The mark alone is not a test report.
  • Radio: Identify the radio module and its authorisation route; confirm on the product page and supporting market-access file which requirements apply.
  • Electrical safety: Determine whether the lock is battery powered and whether a gateway, charger, or adaptor falls into a different electrical-safety route.
  • Construction products: Ask which declaration route the complete hardware and its construction-product status require; do not substitute a cylinder declaration for an assembly-level record.
  • Fire and egress: Identify the door assembly, approved hardware configuration, maintenance responsibility, and local approval route.
  • Batteries and transport: Ask for the cell identification and applicable battery and transport evidence, including the UN 38.3 question when a forwarder requests it.
  • Data: Identify who controls credentials and event logs, where data is stored, and which privacy and security terms govern access.

CONFIRM-WITH-LOCAL-MARKET-ACCESS-REVIEWCONFIRM-WITH-LOCAL-FIRE-AND-EGRESS-REVIEWCONFIRM-WITH-LOCAL-TRANSPORT-AND-BATTERY-REVIEW

Legal-firewall note: this runbook supports procurement qualification and is not legal advice, a certificate, or a declaration of conformity. The market-access route, responsible party, and approving authority must be established for the destination and exact product.

CONFIRM-WITH-LOCAL-LEGAL-AND-CONFORMITY-REVIEW

10. Issue one of four controlled decisions

The decision must describe the accepted scope, not make a general statement about the complete smart lock.

DecisionUse whenProcurement actionRequired wording
Accepted for cylinder claimScope, variant, and current evidence alignProceed to adjacent and market checks“Accepted only for the stated cylinder claim”
Accepted with conditionsA bounded gap remains and the owner and date are recordedTrack the condition before release“Accepted subject to the listed evidence action”
HoldEvidence does not connect to the SKU or a safety question remains openDo not approve the claim“Hold pending scoped evidence”
Not applicableNo in-scope cylinder or the claimed function belongs elsewhereRoute to the correct evidence“EN 1303 is not the evidence basis for this claim”

Use “accepted with conditions” only when the missing item is bounded, owned, and capable of being closed before commercial release. Do not use it to carry an unknown standard scope, an unmatched SKU, or an unresolved fire or egress question. Those conditions require a hold because they change what the buyer is actually accepting. When conditions are closed, attach the new evidence to the original decision and identify which gate it closes; do not replace the history with a fresh approval record. A release decision remains limited to the stated cylinder claim and the exact purchased variant. Any change to the cylinder, lock body, supplier, evidence holder, or destination returns the file to the applicability and variant gates.

A supplier may hold a valid report while the exact SKU remains unmatched. That is a hold, not a pass. Likewise, a family certificate with a narrow scope cannot become an exact-variant pass without evidence from the issuer or an otherwise controlled supplier mapping.

11. Handle common evidence failures

Failure patternImmediate responseResolution evidence
Generic family report onlyHold the exact-variant claimReport or mapping tied to the SKU
Expired certificateStop relying on it for releaseCurrent certificate or other route supported by the standard
Different cylinder inside the lockReopen the scope gateRevised architecture and matching evidence
Supplier substituted a componentSuspend the previous decisionChange notice and qualification of the new variant
Standard edition changedRecheck clause and test referencesCurrent published scope and supporting evidence
Marking supplied without paperworkRemove it from the approval basisUnderlying declaration and technical records

Record each resolution as a controlled change. Do not overwrite the failed evidence or imply that a visual match closes a document gap.

12. Assign sign-off and hand over the supplier request

RoleSign-off responsibility
Procurement ManagerScope decision, open actions, and commercial release
Mechanical or product engineerArchitecture and test-object match
Supplier quality contactEvidence provenance and variant traceability
Compliance or legal reviewerDestination-specific market route
Project or tender leadRequired documents and project conditions

The supplier request should contain the exact SKU, architecture, claimed scope, current published title and scope, named test report, applicable certificate or signed declaration, variant cross-reference, adjacent evidence, and market-access records. EN 1303 in a Smart Lock Tender Pack: The Evidence Checklist can support the tender handoff.

Readers comparing approaches usually start with smart locks for conference rooms. That is the same question en 1303 smart lock scope limits has to answer here.Before approval, ask each shortlisted supplier to return the evidence package against the exact SKU and identify which questions remain outside EN 1303. Then record the narrow claim that can be accepted, route the remaining questions to their proper owners, and hold any unresolved safety or variant gap.

Close the loop with requesting a quote.

장바구니
쿠키를 허용하면 이 사이트에서의 이용 경험이 개선됩니다. 쿠키 정책
Chat on WhatsApp