UL 294 Versus UL 1034: Which One Applies to Your Smart Lock Door
Procurement managers often receive a smart lock described as “UL listed” and then try to decide whether that covers the whole access-control system, the lock at one doorway, or neither. The question behind ul 294 versus ul 1034 applicability is more precise: what is being supplied, and which published standard scope contains that unit?
Direct answer.ul 294 versus ul 1034 applicability is taken here as ul 294 versus ul 1034 applicability, deliberately narrowly. It is a working definition of ul 294 versus ul 1034 applicability. It is specific to this market and product
UL 294 is normally described as covering access-control system units, while UL 1034 covers power locks, meaning electrically controlled locks for door openings. A project can require evidence from both routes without either standard certifying the installed site. This guide gives procurement managers a practical way to separate product scope, evidence and installation acceptance before approving a SKU.
CONFIRM-WITH-LOCAL-AUTHORITY: Verify the current editions, local adoption, project specification and any requirement imposed by the authority having jurisdiction for the specified installation.
The applicability answer at a glance
The fastest way to avoid a misplaced evidence request is to identify the object under purchase before discussing the standard number. If the relevant unit is an access-control system unit, investigate the current edition of UL 294. If it is an electrically controlled lock for a door opening, investigate the current edition of UL 1034. If one smart-lock product contains both functions, keep two evidence questions open until the supplier documents the product boundary. Before the next supplier meeting, read Glass Door Smart Lock Price Guide. What the specification covers is in the smart door locks.
| Qualification question | Evidence route to investigate | What this does not settle |
|---|---|---|
| Is the supplied unit within access-control system unit scope? | Current UL 294 published title and scope | Whether the complete installed access-control system is accepted |
| Does the supplied unit electrically control a door opening? | Current UL 1034 published title and scope | Whether a separate controller or reader is in scope |
| Does one product contain both functions? | Separate scope and evidence analyses | Whether one document covers both functions |
| Is the opening subject to fire or egress requirements? | Project-specific code and assembly evidence | Whether UL 294 or UL 1034 alone establishes compliance |
| Is the offered evidence tied to the ordered configuration? | Exact SKU, variant and accessory review | Whether the evidence remains valid after a configuration change |
The practical distinction is between relevance and obligation. One standard may be relevant to a supplied unit even when no local rule or project specification requires evidence under it. Conversely, a product brochure carrying a familiar mark does not establish which standard was evaluated. Product scope verification must therefore precede any request for certificates, declarations or markings.
Use the current edition of the published standard whenever a clause, test or product-scope decision drives acceptance. Do not rely on an undated secondary summary to define what a unit contains or excludes.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm whether either standard is referenced for this project and whether the authority having jurisdiction accepts the proposed evidence format.
Draw the product and system boundary first
“Smart lock” is a commercial description, not a standards classification. Before comparing scopes, freeze a product boundary that identifies whether the offer includes a lock body, credential reader, controller, communications module, power supply, door contacts, request-to-exit interface or other access-control equipment.
A useful boundary record names the exact model, hardware revision, firmware release, bundled accessories and the functions assigned to each component. It also records what remains outside the supplier’s package and must be supplied by another contractor. This prevents a cabinet-level controller, a standalone lock and an integrated device from appearing equivalent merely because each has an electronic credential interface.
flowchart TD
A[Record the exact product boundary] --> B{Access control unit in scope}
B -->|Yes| C[Investigate current UL 294 scope]
B -->|No| D{Electrically controlled door lock in scope}
D -->|Yes| E[Investigate current UL 1034 scope]
D -->|No| F[Check another published standard]
C --> G[Request evidence for the exact SKU]
E --> G
F --> G
G --> H[Confirm local project requirements]
Ask the supplier to complete this boundary record:
| Boundary item | Procurement record |
|---|---|
| Exact commercial model and revision | Unambiguous identifier matching the proposed order |
| Electronic and mechanical functions | Components and functions included in the package |
| Controller and reader relationship | Which functions operate locally and which operate centrally |
| Power arrangement | Components included in the assessed configuration |
| Accessories | Interfaces, housings, cables and ancillary devices supplied |
| Installation dependencies | Equipment required but not supplied |
| Site assumptions | Door, opening, environment and system conditions used for the offer |
The UL 294 access control question and the UL 1034 power locks question can then be asked against defined objects. Without this record, a supplier may interpret “smart lock” as the complete access-control product or as only the electromechanical locking device. You may then receive power lock evidence when the contract expects access-control-system evidence, or the reverse.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm whether the authority having jurisdiction treats the proposed device as one unit, several units or part of a larger access-control system.
What UL 294 addresses in a smart-lock project
The current edition of UL 294 addresses access-control system units and organizes performance into classes labelled Line Supervision, Endurance, Security and Standby. The class names are useful for identifying the published performance category associated with an evaluated unit, but they do not transform a component into an approved site design.
Start with the current edition’s published title and scope. Determine whether the unit being purchased performs the access-control functions covered by that scope, and whether any required assessment is performed on the combined unit or on an individual component. If the offer consists of several separately supplied units, document which unit carries the evidence and where it sits in the operating arrangement.
The wider limits are set out in UL 294 for Smart Locks: Scope, Tests and What the Standard Never Proves. That distinction is essential when a smart lock combines mechanical locking, radio communication, access decisions and system-level functions. A supplier cannot use a report about one function to answer every question about the complete offer.
Class language also needs context. Decoding UL 294 Class and Grade Numbers for Door Hardware explains why a copied class or grade label is not enough without the complete test-report entry and evaluated configuration. In your records, keep the class, evaluated model, report and certificate identifiers together rather than reducing them to one label.
A sound UL 294 evidence request identifies the unit, its functions, its configuration and the current published scope. It also states whether the supplier is offering a test report, an issued certificate, a declaration of conformity or product marking. Those documents perform different functions and should never be substituted for one another.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm whether the project specification references UL 294, which edition and class it expects, and whether it requires system-level or unit-level evidence.
What UL 1034 addresses in a smart-lock project
The current edition of UL 1034 covers power locks, described as electrically controlled locks for door openings, and addresses lock-level electrical safety and performance. That makes it the closer route to investigate when the purchase object is the mechanism that controls the door lock, rather than the access-control unit that makes and manages a credential decision.
The UL 1034 power locks route should therefore be tied to the exact electrically controlled lock and its operating configuration. Record the model, mechanical interface, electronic control arrangement, supplied parts and any project-defined options. A family name that includes several lock bodies, finishes or control options is not enough to show that the evidence covers the ordered configuration.
UL 1034 evidence does not by itself answer whether a centralized controller, credential reader, line-supervision arrangement or system endurance belongs within the relevant access-control scope. Conversely, UL 294 evidence about an access-control unit does not replace evidence for an electrically controlled door lock simply because both devices ship under one brand.
If the proposed device contains a local lock motor, credential reader and controller in one housing, ask the supplier to state which functions were evaluated under which published scope. Do not infer the answer from the enclosure, mobile application or claim that the product is “smart.” Use the current edition’s published title and scope, then tie any supporting document to the exact model and variant.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm whether UL 1034 is referenced for the project and whether the authority having jurisdiction expects evidence for the lock, the complete device or the installed opening.
Side-by-side comparison for the procurement file
The two standards answer related questions at different levels. The table below is a decision-comparison tool, not a statement that either standard is mandatory at a particular site.
| Decision factor | UL 294 route | UL 1034 route | Procurement implication |
|---|---|---|---|
| Primary object | Access-control system unit | Power lock for a door opening | Define the purchased unit before choosing the evidence path |
| Scope emphasis | System-unit access-control performance | Lock-level electrical safety and performance | Ask each supplier to map its product to the current published scope |
| Performance labels | Line Supervision, Endurance, Security and Standby classes | Use only classifications shown in the current published scope | Preserve the complete entry and test conditions |
| Evidence granularity | The assessed unit and its configuration | The assessed lock and its configuration | A family-level document may not cover the ordered variant |
| Relationship between routes | May address the control side | May address the door-opening lock side | An integrated product can create two separate evidence questions |
| Fire-door assembly | Does not replace assembly-specific evidence | Does not replace assembly-specific evidence | Keep the opening and its installed hardware in a separate review |
| Site acceptance | Not established by the standard alone | Not established by the standard alone | Obtain local project acceptance separately |
| Configuration control | Record assessed options | Record assessed options | Freeze the approved SKU before purchase |
The ul 294 versus ul 1034 applicability record should show the selected route, rejected route and reason. “Rejected” does not mean “failed.” It may mean that the product is outside the scope, that another buyer holds the relevant evidence, or that the project does not reference that route.
For a project spanning many doors, maintain both the project-level system map and the product-level evidence register. The system map shows how components relate; the register shows what evidence each supplier has actually provided. Do not ask every lock supplier to reproduce an entire access-control system file if the controller and credentials sit under a separate contract.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm the evidence level required by the contract and the authority having jurisdiction; do not infer site acceptance from either product standard.
Five project patterns and the correct routing question
1. Standalone battery-powered smart lock
For a single door, begin with the mechanical and electrical functions of the lock itself. Ask whether the current UL 1034 scope contains that product and whether power lock evidence exists for the exact model. Then ask whether the lock is also an access-control system unit within the current UL 294 scope, or merely a device controlled by another unit.
A local credential capability does not automatically resolve the second question. The supplier must explain the product boundary and the assessed functions. If the lock is only one element of a separately controlled access-control installation, keep the lock evidence and the controller evidence in separate folders.
2. Central controller with an electrically controlled lock
The controller and the lock are separate evidence objects. The UL 294 route may be relevant to the controller or other access-control unit; the UL 1034 route may be relevant to the electrically controlled lock. Ask each supplier to document which unit they are offering rather than requesting both documents under the same model number.
The project file should identify the interface between the units, but that interface does not transform one component’s evidence into evidence for the other. A technical description of communication, supervision or fail-safe behavior is not a substitute for the applicable published scope.
3. Integrated reader, controller and lock device
An integrated housing can still contain distinct assessed functions. Request a written scope map for the current editions of both standards. The map should identify which assembly was evaluated for access-control performance and which assembly was evaluated as a power lock, if applicable.
Do not accept “the product is UL 294” or “the product is UL 1034” without the evaluated model, report, certificate or declaration that supports the statement. If the supplier cannot connect the claim to a named document, record the claim as unverified and keep it out of the approved evidence checklist.
4. Retrofit onto an existing controlled opening
A retrofit creates two boundaries: the new product and the existing access-control installation. The new lock may need product-level evidence, while the retained controller and system may have their own evidence history. Existing equipment does not transfer evidence to the replacement lock, and the replacement lock does not automatically establish the status of the retained system.
For installation-specific issues, use UL 294 When Retrofitting Smart Locks Onto Existing Doors as a companion guide. Record door condition, retained components, changed interfaces, power arrangement and commissioning responsibility before deciding which documentation must be refreshed.
5. Fire-rated or life-safety-related opening
Treat the opening as an assembly question in addition to the product questions. The applicable fire, egress and access-control evidence must be identified for that installation; neither UL 294 nor UL 1034 alone should be recorded as proving the complete opening’s status.
Ask the local authority or project fire-safety professional which evidence must cover the installed door, frame, hardware and interfaces. Keep that answer separate from the supplier’s product file so that a component report is not mistaken for assembly acceptance.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm fire-door, egress and access-control requirements for each opening with the authority having jurisdiction and the project’s qualified life-safety professionals.
Separate the four documents behind a conformity claim
A request for “UL certification” is too vague because it leaves the supplier free to answer with any of four different document types.
| Document | What it represents | Minimum details to capture | Common procurement mistake |
|---|---|---|---|
| Test report | A sample or evaluated configuration was tested | Laboratory, report number, date, model and tested configuration | Treating the report as current approval for every later production unit |
| Certificate | A body attests conformity within a defined scope | Certificate number, scope, holder, model coverage and validity | Ignoring exclusions, options or a different standard edition |
| Declaration of conformity | The manufacturer or importer makes its own legal claim | Signed party, date, applicable legislation, model and referenced evidence | Accepting a declaration without checking its referenced documents |
| Marking | A mark or label appears on a product or package | Marking image, authorised model, placement and supporting record | Treating a label photograph as proof of the underlying evidence |
CONFIRM-PER-SUPPLIER: All certification status must be confirmed against the named report, certificate, declaration or marking supplied for the exact SKU and variant.
The evidence-quality ladder for ul 294 versus ul 1034 applicability runs: marketing image → declaration of conformity → test report on a sample → scoped third-party certificate → certificate covering the exact SKU/variant ordered → audit trail proving the approval still stands after the sample passed.
The rungs that decide ul 294 versus ul 1034 applicability are the ones issued under ul 294; a file for a different scheme does not move the position on this ladder.
The commercial failure often occurs when purchasing stops at the second or third rung and installation later reveals that the exact SKU, variant or production process was never covered. A stronger power lock evidence request asks how the supplier maintains the connection between the evaluated sample and the units being shipped.
Use Reading a UL 294 Test Report Page by Page: A Smart Lock Buyer Walkthrough for the report side of that review. Three Ways UL 294 Evidence Disappoints Smart Lock Buyers covers common gaps between a supplier’s headline claim and the purchasing file.
Inspect scope, configuration and certificate coverage
Ask the supplier for a one-page applicability statement for each offered unit. The statement should identify the current edition considered, the published scope relied upon, the evaluated model, applicable options and the evidence offered. A standard number without those details is a lead, not an approval record.
Check the following fields:
| Field | Question for the supplier | File action |
|---|---|---|
| Product identity | Which exact model and revision were evaluated? | Match to the purchase requisition |
| Product role | Is the unit the access-control unit, the power lock, or both? | Record the product boundary |
| Configuration | Which hardware, firmware, interface and accessories were included? | Flag every proposed difference |
| Standard edition | Which edition appears on the report or certificate? | Compare with the project requirement |
| Scope reference | What wording in the published scope supports the claim? | Attach the dated source |
| Classification | What class, rating or other designation appears in the evidence? | Preserve the full entry |
| Certificate number | Is there an issued certificate with a verifiable number? | Verify against the issuing body’s record |
| Holder and scope | Does the certificate cover this manufacturer, model and configuration? | Reject family-only assumptions |
| Validity | What validity or status information is shown? | Record the check date |
| Production continuity | What controls connect the evaluated sample to production units? | Request supporting records |
This product scope verification prevents two common errors. First, a certificate for one model does not automatically cover a differently equipped variant. Second, a document can discuss the right standard while still excluding the particular product or function being sold.
Do not ask the laboratory to interpret a supplier’s commercial package. Ask the certificate issuer to confirm certificate scope when necessary, and ask the supplier to explain how the evaluated configuration maps to the purchase order. The person who signed the declaration remains responsible for that declaration even when a third-party report is attached.
When the evidence will enter a tender or pre-award pack, use UL 294 in a Smart Lock Tender Pack: The Evidence Checklist as a completeness model and add the corresponding UL 1034 records for the lock being purchased.
Write an RFQ clause that requires an answer
A weak clause asks whether the product is “UL 294 and UL 1034 approved.” That wording assumes both routes apply, gives no scope record and treats approval as a product-wide state. Instead, require a product-by-product response.
Use the following procurement language:
For each offered model, provide a written applicability statement identifying the product boundary, functional description, current published standard edition considered, exact model and variant evaluated, and the evidence available under each potentially applicable route. Attach the named test report, issued certificate, declaration of conformity or marking relied upon, together with its identifier, date, scope and configuration. Where a route does not apply, state the scope-based reason and identify which supplied component, if any, is covered instead.
Add these mandatory attachments to the response schedule:
- A line-by-line model and revision list.
- The current published title and scope used for the determination.
- A product-function map showing the reader, controller, lock, interfaces and accessories.
- Every report, certificate and declaration offered for the exact configuration.
- Any excluded models, options or accessory combinations.
- The process for keeping evidence aligned with production and configuration changes.
- A named contact authorized to resolve scope questions.
UL 294 Covers the System, Not the Lock: Writing the Clause So a Supplier Answers provides a focused drafting pattern for the access-control side. Also clarify responsibility for obtaining evidence rather than treating it as an invisible factory task; Who Pays for UL 294 Evidence in a Smart Lock OEM Programme separates ownership, timing and quotation assumptions.
Smart lock compliance improves when the RFQ asks for the same fields from every bidder. It also makes later comparison meaningful: two suppliers may occupy different product boundaries, but their answers should still reveal whether each has completed product scope verification.
Keep product evidence separate from site acceptance
A standard describes what it tests. It does not approve a particular doorway, installation, configuration or building. Product evidence can support qualification, while site acceptance depends on the project’s applicable requirements, installation records and the authority having jurisdiction.
Keep these project records in separate sections:
- Product file: model, revision, evidence, scope and configuration.
- System file: controller, readers, interfaces, power, communications and operating arrangements.
- Opening file: door, frame, locking hardware, exits, fire provisions and installed accessories.
- Commissioning file: as-installed settings, tests, exceptions and responsible signatories.
- Local-acceptance file: correspondence and decisions from the relevant review body.
The project file should not say “site certified” merely because a component carries a mark or report. Use more precise wording: “Supplier supplied the named evidence for the listed model and configuration.” If a certificate has a defined scope, preserve that scope in the index. If a project review issues an acceptance record, file that record separately with its issuer, scope and date.
Ask the authority having jurisdiction which standard edition and evidence route it expects for this opening. If no reference exists, record that answer as received rather than inferring silence from an unquoted specification. If multiple authorities are involved, maintain each response under its own reference.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm whether project acceptance requires a particular document, who may issue or sign it, which opening records must accompany it and whether changes require renewed review.
Seven errors that distort the applicability decision
Treating “UL” as one blanket claim. A familiar abbreviation does not reveal the standard, scope, model or evidence type. Require the named document.
Using one standard for the entire project. A system-unit route does not replace lock-level evidence, and lock evidence does not replace access-control-system evidence.
Calling a test report a certificate. A report records testing. A certificate is a separate attestation with its own scope, number and validity information.
Accepting family-level coverage. Confirm that the exact SKU, revision and relevant options appear within the evidence, not merely the same product family.
Ignoring the standard edition. The current edition and the dated project requirement must be compared before clause-level conclusions are recorded.
Quoting a class without the assessment record. A class label detached from the report, tested configuration and certificate scope is incomplete evidence.
Assuming local adoption from product literature. Local requirements must come from the relevant authority and project documents, not from a supplier brochure.
These are evidence-control failures, not merely drafting problems. Each one can leave a procurement file with a persuasive phrase but no traceable answer. The corrective action is simple: preserve the claim, identify the document that supports it and verify the document’s coverage.
For more failure patterns, review Three Ways UL 294 Evidence Disappoints Smart Lock Buyers alongside the project’s own evidence index. The object of the review is to find missing records before purchase, not to search for a substitute claim after a shortfall appears.
A ten-gate qualification workflow
The workflow below turns the standards comparison into a sequence that can be assigned across procurement, engineering, quality and installation teams.
| Gate | Owner | Required decision | Output |
|---|---|---|---|
| 1. Boundary | Product lead | Define each supplied unit and function | Signed product map |
| 2. Configuration | Engineering | Freeze model, revision, firmware and accessories | Configuration baseline |
| 3. Scope | Compliance | Read current published titles and scopes | Preliminary applicability map |
| 4. Route | Procurement | Select UL 294, UL 1034 or both evidence questions | Route decision record |
| 5. Evidence | Supplier | Submit reports, certificates, declarations and marking records | Supplier evidence index |
| 6. Coverage | Quality | Match evidence to exact SKU and configuration | Coverage comparison |
| 7. Local check | Project lead | Confirm project and authority requirements | Written local-response record |
| 8. Installation | Integrator | Match installed equipment to approved baseline | As-built configuration record |
| 9. Change control | Program manager | Review substitutions and firmware changes | Impact decision |
| 10. Release | Procurement | Approve the evidence package for order | Signed qualification file |
Use the project reference ul-294 on every evidence request, supplier folder and purchase-order attachment so the standards analysis is easy to retrieve. For projects with no North American reference, retain the reference as an internal search tag rather than presenting it as a local requirement.
Gate three should occur before asking suppliers for expensive or time-consuming records. If the current published scope does not contain the supplied unit, record that finding and move to the correct published standard or evidence route. If the scope is potentially relevant, ask for the exact document. This sequence reduces wasted requests without weakening the acceptance file.
Readers comparing approaches usually start with smart locks for conference rooms. That is the same question ul 294 versus ul 1034 applicability has to answer here.Do not release a SKU for purchase while a requested document remains unresolved, unless the commercial decision explicitly records who accepted the gap and why. An unresolved exception should never be hidden inside a general note such as “certificates pending.”
This overlaps with the earlier coverage in smart locks for office storage rooms. That is the same question ul 294 versus ul 1034 applicability has to answer here.
The one-page smart-lock applicability decision note
Close each qualification with a short record that another procurement manager can understand without the original email chain. It should contain:
- Exact product model, revision and door-opening application.
- Product functions and component boundary.
- Current UL 294 scope conclusion, with supporting document or a not-applicable reason.
- Current UL 1034 scope conclusion, with supporting document or a not-applicable reason.
- Names and numbers of all reports, certificates and declarations.
- Declaration-of-conformity signer and date where supplied.
- Product marking identified from the physical label, if relevant.
- Configuration differences and excluded options.
- Local project requirement and the authority’s written response.
- Open exceptions, owners and approval dates.
- Evidence-freshness and production-control notes.
- Approved configuration baseline for the purchase order.
The note should avoid unsupported phrases such as “the whole system is UL certified” or “the site is UL 1034 approved.” Write what the evidence actually covers. If an access control certification claim is made, resolve it to the named certificate or report. If power lock evidence is supplied, identify the lock model and assessed configuration. If neither route applies, preserve the scope analysis that explains why.
Before releasing the order, ask the supplier to return the completed applicability note, exact evidence attachments and a signed statement of any proposed configuration change. This turns the standards question into a controlled commercial deliverable: the buyer receives an answer tied to the ordered hardware, while the installer and authority retain their separate acceptance responsibilities.
Put the answer on paper and request a quote against that document.

