The EU Low Voltage Directive in a Smart Lock Tender Pack: The Evidence Checklist
Use this eu lvd smart lock tender evidence schedule during qualification, before commercial evaluation. It turns the EU Low Voltage Directive into a line-by-line response: what was supplied, which route may apply, what document supports each point, and who owns any gap. The same structure can index a smart lock tender pack, a gateway schedule and an adaptor schedule without treating them as one product. Keep it in the bid file rather than a general supplier questionnaire.
Direct answer. In brief, this article covers eu lvd smart lock tender evidence from eu lvd smart lock tender evidence to eu-lvd. It states what to confirm about eu lvd smart lock tender evidence on the dated product page where a figure is involved. An eu lvd smart lock tender evidence turns conformity language into requests a buyer can send. eu lvd smart lock tender evidence is where those eu lvd smart lock tender evidence requests get written down.
On eu lvd smart lock tender evidence, this article uses eu lvd smart lock tender evidence as the definition. It treats eu lvd smart lock tender evidence as a working definition specific to this market and product, rather than a general one.
- What is in the supplier file — supplier declarations and drawings for eu lvd smart lock tender evidence
- What needs certification — third-party certificates covering the exact scope of eu-lvd
- What to obtain — the document set that matches the SKU behind eu lvd smart lock tender evidence
- eu lvd smart lock tender evidence runs this sequence, and eu lvd is the record it produces.
CONFIRM-WITH-LOCAL-EU-LVD-SCOPE: Confirm the current legal scope, destination-market route and tender-specific instructions with the relevant competent authority or a qualified conformity adviser before release.
1. Bid sheet control: define the exact supplied item
Start with one row per offered configuration rather than one row per product family. A lock, gateway, bridge, charging dock and external power supply may require different evidence. Record the model, supply boundary and power arrangement without relying on a family name or compliance badge. A published treatment of the same step is Smart Lock Procurement Budget Checklist. The build options sit in the smart door locks.
| Bid field | Required entry | Qualifier to record |
|---|---|---|
| Offered item | Commercial line and product description | Lock, gateway, adaptor or complete supplied assembly |
| Model identity | Manufacturer model and exact SKU | Hardware and configuration revision |
| Supply boundary | Parts included with the tendered item | Exclude separately supplied accessories |
| Power source | Battery, external supply or mains interface | Identify every external power component |
| Destination and use | Intended market and operating environment | State whether the item is battery-only or externally powered |
| Evidence owner | Person responsible for closing each field | Use CONFIRM-PER-SUPPLIER until validated |
Freeze the bid-sheet version after supplier response. A change to the SKU, power supply, supplied components or documented construction should reopen the affected evidence fields.
CONFIRM-WITH-LOCAL-EU-LVD-SCOPE: Confirm which authority or conformity adviser should validate the route for each exact offered configuration.
2. Allocate the scope by supplied item and function
The central question is not whether the tender concerns a smart lock. It is which supplied item, voltage source and function are under assessment. The LVD 2014/35/EU electrical-safety route concerns mains-connected equipment and adaptors; a battery lock and a mains-powered smart lock gateway must not be bundled simply because they work together.
| Assessment lane | Question for the bidder | Evidence to request | Inference to prohibit |
|---|---|---|---|
| Electrical safety | Does the supplied configuration include a mains interface or external adaptor? | Applicable electrical-safety report and route-specific documents | Treating a battery-only product statement as gateway evidence |
| Mechanical and electromechanical function | Which locking performance standard was applied to the sampled configuration? | Report with model and test scope | Using lock-performance evidence as electrical-safety evidence |
| EMC and radio | Is a wireless function or radio module included in the offered item? | Evidence from the applicable EMC and radio route | Using an LVD document to answer radio questions |
| Fire-door application | Is the lock intended for use in a tested fire- or smoke-door assembly? | Evidence tied to the assembly and configuration | Treating a standalone lock file as assembly evidence |
| Construction-product route | Is the hardware being supplied in a capacity covered by the construction-products route? | Route-specific declaration and supporting evidence | Substituting an electrical-safety declaration |
EN 14846 is the closer fit than EN 12209 for the mechanical-electrical locking function of a battery-driven smart lock. EN 12209 addresses mechanically operated locks and latches. Neither designation answers the electrical-safety question for an external adaptor or gateway.
Use The EU Low Voltage Directive for Smart Locks: Scope, Tests and What the Standard Never Proves to structure the scope narrative. Where a construction-product route may overlap, use The EU Low Voltage Directive Versus the EU Construction Products Regulation: Which One Applies to Your Smart Lock Door as a separate comparison.
CONFIRM-WITH-LOCAL-EU-LVD-SCOPE: Confirm the current LVD, EMC, radio and construction-product routes separately for the exact supplied configuration and destination.
3. Keep the four evidence objects separate
The phrase “the supplier has CE” is not a usable tender response. It may refer to a label, a declaration, a report or a certificate with a defined scope. Require the bidder to name the evidence object and provide it in a traceable form.
| Evidence object | What the document actually is | Information to capture | What it cannot replace |
|---|---|---|---|
| Test report | Evidence that someone tested a sample | Laboratory, report identifier, sample description, standard title and edition, clauses tested, results and issue date | A certificate, declaration or marking |
| Certificate | A body’s attestation within a stated scope | Issuer, certificate number, holder, covered models, scope, issue date and validity information | Evidence that the tendered configuration matches the tested sample |
| Declaration of conformity | The manufacturer’s or importer’s own legal claim | Legal actor, product identifier, signed declaration, date, signatory, applicable route and referenced standards | Independent test evidence or production-control records |
| Marking | A mark printed on the product or label | Mark location, product photograph, packaging image and model identification | The report, certificate or declaration behind it |
A test report, a third-party certificate with scope and number, a signed LVD declaration of conformity and an applicable marking may form one evidence set. They remain four distinct objects with four different functions.
CONFIRM-WITH-LOCAL-EU-MARKING: Confirm which declaration, marking and market-access requirements apply to each supplied item in the destination market.
4. Apply the evidence-quality ladder
Use this eu lvd smart lock tender evidence acceptance matrix to grade what has actually been supplied. The rungs describe evidence quality; they are not interchangeable labels for compliance.
| Rung | Evidence available | Qualification interpretation | Procurement action |
|---|---|---|---|
| 1 | marketing image | No auditable support | Evidence for eu lvd smart lock tender evidence (eu lvd) |
| 2 | self-declared DoC | Legal claim with limited independent support | Validate identity, signature, date and scope |
| 3 | test report on a sample | Technical evidence for the tested sample | Map the sample to the offered SKU |
| 4 | third-party certificate with scope and number | Independent attestation within a defined scope | Verify scope, holder, validity and model coverage |
| 5 | certificate for the exact SKU/variant being purchased | Evidence tied to the offered configuration | Reconcile every model and option |
| 6 | production-control records that hold the approval open after the sample passed | Support for keeping the approved build under control | Define monitoring and change-control duties |
The recurring failure is accepting a document at rung 2 or 3 and discovering during installation that no evidence chain exists for the exact configuration at rung 5. A high-quality report becomes weak evidence when the sample, options or power supply differ from the tendered item.
CONFIRM-WITH-LOCAL-EU-LVD-SCOPE: Confirm the evidence needed at qualification and the status of any declaration offered by the supplier.
5. Review the report, certificate, declaration and marking
Reviewing the files in sequence prevents a strong-looking certificate from hiding an unidentified sample or an unsigned declaration.
Start with the electrical safety test report
Request the complete electrical safety test report, including its cover pages, sample description, photographs, test tables and annexes. Record the report number, laboratory, issue date, model designation, standard title, edition, clauses and results. The sample description must expose the power arrangement and any options that could affect the test. Clause-level interpretation should be checked against the published standard text.
Then examine the certificate
If a third-party certificate is offered, verify the issuer, certificate number, legal holder, scope, issue date and validity information. Compare every model identifier with the offered SKU. A family name on the cover is not enough when the certificate schedule lists a restricted model, variant or component set.
Review the signed declaration next
Check the LVD declaration of conformity for the legal manufacturer or importer, product identity, signing authority, signature and date. Reconcile its product identifier and referenced standards with the report and certificate. Keep the signed declaration in the tender record rather than treating an unsigned portal image as the final evidence object.
Capture the marking last
Record the location of the CE, UKCA, RCM, KC or G-Mark relevant to the item and destination, as confirmed for that route. Use clear photographs and model labels. The marking is a traceability record; it does not reveal whether the underlying report covered the supplied configuration.
For a page-by-page review, use Reading an EU Low Voltage Directive Test Report Page by Page: A Smart Lock Buyer Walkthrough.
CONFIRM-WITH-LOCAL-EU-LVD-DOCUMENTS: Confirm the required document set, document validity and destination-specific marking for each item.
6. Bind every claim to the exact SKU and controlled build
Evidence must follow the configuration offered for award. Create a model-to-document map showing which test report, certificate, declaration and marking file applies to each SKU. Include the external power supply where it forms part of the supplied scope.
| Linkage field | Question to answer | Acceptable support | Qualification failure |
|---|---|---|---|
| Model identity | Is the full model code visible? | Purchase order, datasheet and label cross-reference | Supplier family name only |
| Configuration | Do options match the tested configuration? | Configuration schedule or controlled variant list | Silent assumption that all options are equivalent |
| Power arrangement | Is the external supply the assessed item? | Separate schedule and document map | Lock evidence reused for the adaptor |
| Production build | Are changes controlled after assessment? | Production-control or audit evidence | Evidence limited to an unidentified sample |
| Change notice | How will the bidder notify the buyer of changes? | Written commitment and contact route | No traceable change process |
Rung 5 of the evidence ladder requires exact SKU or variant coverage. Rung 6 adds evidence that the assessed build remains connected to production. Record the status as CONFIRM-PER-SUPPLIER until both the document mapping and the build-control check are complete.
Readers comparing approaches usually start with when should you choose smart lock oem instead of odm. That is the same question eu lvd smart lock tender evidence has to answer here.CONFIRM-WITH-LOCAL-EU-LVD-VARIANTS: Confirm whether any proposed variant or production change requires fresh evidence for the offered configuration.
7. Turn the checklist into RFQ clauses
A useful requirement tells the bidder what to state, which evidence to provide and how exceptions will be handled. It should not ask one broad question about the entire lock programme.
For each offered SKU and each externally powered item, state the applicable regulatory route and provide an evidence schedule identifying the test report, certificate where used, signed declaration of conformity, marking evidence, model-to-document mapping and production-control evidence. Identify every excluded item, unresolved gap, sample limitation and proposed alternative separately.
| RFQ line | Required bidder response | Conditional evidence | Disposition if absent |
|---|---|---|---|
| Scope statement | Name the item, function and power source | Route-specific explanation | Hold for clarification |
| Standard identification | Give the published title and edition | Published text reference | Request correction |
| Test report | Give the report number and sample description | Complete report and annexes | Do not infer coverage |
| Certificate | Give number, scope, holder and covered models | Verification channel | Treat as unresolved |
| Declaration | Supply the signed and dated document | Legal-actor explanation | Do not rely on an unsigned copy |
| Marking | Identify the relevant marking and location | Clear product photographs | Record as absent |
| Variants | Map all offered options to evidence | Controlled variant schedule | Exclude unsupported options |
| Exceptions | List every gap and proposed mitigation | Alternative or supplementary evidence | Escalate before qualification |
Require a written response against every line rather than a single compliance tick. The smart lock tender pack should preserve the supplier’s words, document references and exceptions alongside the procurement decision.
For clause design focused on an electrical component, use The Electrical Safety Route in a Smart Lock RFQ: What a Mains-Powered Part Changes.
CONFIRM-WITH-LOCAL-EU-LVD-RFQ: Confirm the final RFQ wording and documentary requirements with the relevant authority and legal adviser before issue.
8. Map adjacent standards without scope leakage
A smart-lock programme can involve several standards, but each answers a different question. Build a scope map that prevents a mechanical lock report, an EMC document or a fire-door assembly record from standing in for electrical-safety evidence.
| Question | Reference family to check | Evidence sought | Boundary |
|---|---|---|---|
| Electrical safety of powered hardware | LVD route and the published scope of relevant electrical-safety standards such as IEC 62368-1 where applicable | Route-specific report and conformity documents | Does not establish lock performance |
| Electromechanical locking function | EN 14846 | Report tied to the lock configuration | Does not answer radio, EMC or adaptor questions |
| Mechanical locking performance | EN 12209 for mechanically operated locks and latches | Report for the assessed hardware | Does not cover electronically driven locking |
| Fire-door suitability | EN 1634-1 for tested door and shutter assemblies | Evidence tied to the assembly | No standalone lock fire-certificate concept |
| EMC and radio | Current RED and EMC routes | Separate technical evidence | Does not replace electrical-safety evidence |
| Battery and transport | IEC 62133 series and UN 38.3 as applicable to cells and transport | Cell, battery or transport documentation | Does not qualify the installed lock |
Use the current edition of each standard and check the published title and scope. A standard describes what was tested; it does not establish the conformity status of a site, installation or unlisted variant.
CONFIRM-WITH-LOCAL-EU-ROUTES: Confirm the published title, scope and edition of every standard and regulation entered in the compliance map.
9. Control gaps, exceptions and proposed substitutions
Treat an unresolved gap as a qualification issue with an owner. Do not convert it into an implied pass through procurement language such as “equivalent,” “latest version available” or “certificate to follow.”
| Observed gap | Permitted qualification treatment | Shortcut to prohibit | Owner |
|---|---|---|---|
| Only a marketing image | Evidence for eu lvd smart lock tender evidence (eu lvd) | Assuming a report exists | Supplier |
| Report sample differs from the SKU | Seek a documented rationale or replacement evidence | Treating model similarity as identity | Engineering and supplier |
| marketing image | Hold or propose an identified alternative | Widening the scope verbally | Compliance owner |
| Declaration lacks a signature or date | Hold for the signed record | Accepting an unsigned draft | Legal manufacturer or importer |
| Substitution proposed | Open a new evidence-review line | Inheriting the original evidence automatically | Procurement and engineering |
Maintain an exception register with the affected SKU, missing field, requested document, accountable party, qualification consequence and closure status. Any conditional acceptance should identify the document or decision required before the condition can close.
CONFIRM-WITH-LOCAL-EU-LVD-EXCEPTIONS: Confirm any exclusion, exception or conditional treatment with the relevant authority and legal adviser.
10. Run the qualification gate
Use a staged gate so that incomplete scope decisions cannot be hidden by apparently strong documents.
flowchart TD
A[Define supplied item] --> B[Record power source and voltage]
B --> C[Allocate evidence route by item]
C --> D[Collect four evidence objects]
D --> E[Match exact SKU and scope]
E --> F{All qualification fields closed}
F -- Yes --> G[Approve evidence status]
F -- No --> H[Assign gap owner and closure action]
This overlaps with the earlier coverage in when should you choose smart lock odm instead of oem. That is the same question eu lvd smart lock tender evidence has to answer here.The scope and evidence matrix should move from configuration freeze, through route allocation and document review, to exact-SKU matching. A file should pass only when the gate has a named reviewer, a dated record and a supported decision.
| Gate | Pass condition | Stop condition | Required record |
|---|---|---|---|
| Configuration | SKU, power source and supply boundary are fixed | Parts or options remain undefined | Approved bid-sheet row |
| Scope | Every item has an allocated route or documented exclusion | Two routes are being treated as interchangeable | Scope confirmation |
| Documents | Report, certificate if used, declaration and marking are identified | Supplier uses an undifferentiated compliance statement | Evidence index |
| Model mapping | Each document is tied to the offered configuration | Sample or model differences remain unexplained | Model-to-document map |
| Qualification | Decision, conditions and owner are recorded | Evidence remains at an unsupported rung | Signed gate record |
Keep CONFIRM-PER-SUPPLIER visible on any line that has not passed all five gates.
CONFIRM-WITH-LOCAL-EU-LVD-GATE: Confirm the qualification decision with the authority or qualified conformity professional responsible for the tender.
11. Apply the tender committee decision matrix
Present the committee with evidence states rather than compliance adjectives. The decision matrix below is a commercial qualification tool, not a substitute for the route-specific confirmation required for the supplied item.
| Evidence state | Qualification decision | Reason | Tender action |
|---|---|---|---|
| Exact configuration supported through report, certificate where used, declaration, marking and production control | Pass subject to change control | Evidence chain reaches the controlled offered build | Include evidence conditions in the schedule |
| Technical documents match, but production-control evidence is absent | Conditional hold | The assessment-to-production link is incomplete | Require the missing control evidence |
| Only a test report on a sample is available | Hold | Sample coverage is not yet tied to the tendered SKU | Request model mapping or replacement evidence |
| Only a signed self-declared DoC is available | Hold and escalate | Legal claim has not been supported by the requested evidence chain | Request the route-specific documents |
| Certificate scope excludes the offered model | Do not qualify that line | The evidence object does not cover the item | Offer an identified alternative or exclude the line |
| Supplier confirms that no electrical-safety route applies after scope review | Exclude from that scope with a written rationale | The route decision is resolved rather than merely undocumented | Update the scope schedule |
| Exception or substitution remains open | Defer the line | The qualification condition has no closure evidence | Assign owner and closure requirement |
Record the decision for each bid line separately. A strong gateway package must not compensate for an unsupported lock, adaptor or supplied variant.
CONFIRM-WITH-LOCAL-EU-LVD-DECISION: Confirm the final treatment of each qualification decision, especially exclusions and conditional acceptance.
12. Assemble, index and hand over the evidence pack
Use this EU Low Voltage Directive evidence checklist as the cover sheet for the tender evidence. The index should let a reviewer move from the commercial item to the scope decision and then through every supporting document without relying on email history.
| Index tab | Mandatory contents | Control rule |
|---|---|---|
| Scope and configuration | Bid rows, power sources, supplied items and route decisions | Match the approved tender schedule |
| Model map | SKU, document identifiers and coverage notes | No unexplained variants |
| Technical evidence | Complete reports and supporting annexes | Record edition, sample and issue date |
| Attestation evidence | Certificates and signed declarations where used | Record scope, number, holder and validity |
| Marking evidence | Photographs and model identification | Keep destination and item visible |
| Control and exceptions | Production-control records, deviations and closure evidence | Preserve ownership and status |
| Approval | Reviewer decision, conditions and confirmation record | Date and authorise the final state |
Hand the completed pack to the contract and installation teams with a short change-control note. Identify the documents that cannot be varied without reopening qualification, the route questions that remain local confirmations and the contact responsible for evidence updates.
The commercial ready state is a traceable chain from each tendered SKU to its scope statement, test report, certificate where used, signed declaration, marking evidence and production-control record. That chain is more useful than a statement that the product “has CE,” and it gives procurement a defensible basis for qualification.
CONFIRM-WITH-LOCAL-EU-LVD-PACK: Confirm the final evidence index, declaration route and destination-specific requirements before releasing the tender pack.
Close the loop with requesting a quote.

