UL 325 Compliance: What Architects Need in the Spec Set
- Door Automation Systems
- 7 days ago
- 11 min read
UL 325 appears in more specifications than it is understood in. It gets written into Division 08 sections, requested by building departments, referenced by insurers, and cited in submittals, usually as three characters and a number with no accompanying detail about what compliance actually requires or what documentation proves it.
That vagueness is survivable right up until it is not. A specification that says "operator shall be UL 325 compliant" and nothing else has not settled anything. It has not established what the certification actually covers, whether the installed assembly still matches it, or what the contractor hands the inspector at closeout.
This guide covers what the standard governs, the two distinctions that cause most of the confusion, and what belongs in the documentation set before a project reaches permitting.
Requirements vary by jurisdiction, occupancy, and application, so treat what follows as preparation for the conversation with your authority having jurisdiction rather than a substitute for it.
What UL 325 actually covers
The full title of the standard is Door, Drapery, Gate, Louver, and Window Operators and Systems, and the current version is binational: ANSI/CAN/UL 325, applying in both the United States and Canada. It governs the operator, meaning the motor, control electronics, and the safety devices supplied with it.
Editions matter more than most specifications acknowledge. A certification is issued against a specific edition with specific revisions, so a document citing an edition from a few years back is not automatically stale, but it does tell you which version of the requirements the product was measured against. Ask which edition, and record it in the submittal.
Its core concern is entrapment. An automated door is a powered mechanism moving a heavy object through a space people occupy, and the standard exists because that combination has injured people. Compliance testing addresses several areas:
Entrapment protection. The system has to detect an obstruction and respond by stopping, reversing, or both. Protection is classified by method, and different classifications suit different applications.
Force limitation. The operator cannot exert unlimited force. Testing establishes the maximum force the system may apply during a closing cycle and how quickly it must respond to resistance.
Emergency operation. The door must be operable when power is not available. Manual release provisions have to function without tools and without specialized knowledge, because the person who needs them is likely a member of the public.
Electrical safety. Grounding, insulation, wiring, and fault conditions. Detailed further below.
Endurance. Cycle testing that verifies safety features continue functioning after sustained use rather than only when the unit is new.
Electromagnetic compatibility. Tested against the IEC 61000-4 series, covering electrostatic discharge, radiated radio-frequency field immunity, electrical fast transient and burst, surge, conducted disturbances induced by RF fields, voltage dips and short interruptions, and harmonics at the AC power port. In practice this is what keeps a door from behaving unpredictably in a building that also contains commercial radio equipment, large motors, or unstable power.
Electrical safety. Residual voltage, kinetic energy, leakage current measured both initially and following humidity conditioning, input current, normal temperature rise, and dielectric voltage withstand.
The UL 325 specifications overview in our technical library sets out the specific test standards and results.
Did You Know? UL 325 covers gates, louvers, and window operators alongside doors. A project with automated shading or operable louvers may have UL 325 obligations in scopes the door specification never touches.
The two distinctions that cause most of the trouble
UL 325 certifies a product. It does not certify an installation.
This is the single most consequential thing to understand about the standard, and it is where specifications most often fail.
An operator carries a certification because a specific configuration of motor, control board, and safety devices was submitted for testing and passed. The certification describes that configuration. It is a statement about equipment, made under laboratory conditions.
What it does not do is guarantee that the equipment ends up installed the way it was tested. A certified operator can be installed with sensors mounted incorrectly, force settings adjusted past their tested limits, safety devices bypassed during commissioning and never restored, or paired with hardware the certification does not cover. The product remains certified. The installation is not compliant.
Building inspectors know this. An inspector who finds an operator whose photo eyes are misaligned will not be reassured by a certification document, because the document describes a configuration that no longer exists on site.
Certification is equipment-specific
The certifying document is an Authorization to Mark, and it describes the equipment it covers rather than blessing a manufacturer wholesale.
That has a direct consequence for specifications. Language requiring "UL 325 certified operators" and nothing further has not established that the equipment eventually delivered is what the certification describes. On a project where the operator is value-engineered late or a substitution lands at submittal, what arrives may not be what the document covers.
Ask the supplier to confirm that the certification documentation covers the equipment being supplied for your project. A supplier who knows their product will answer that in a sentence.
UL is not the only certifier
UL 325 is a standard. Underwriters Laboratories wrote it, but UL is not the only body that certifies against it. Intertek, TÜV, CSA, and other Nationally Recognized Testing Laboratories all issue certifications to UL standards, and their marks carry equal weight.
This matters twice over. In the specification, writing "UL listed" is narrower than most architects intend and can technically exclude an operator certified by another NRTL to the same standard.
The accurate phrasing is that the operator shall be certified to ANSI/CAN/UL 325 by a Nationally Recognized Testing Laboratory, which states the requirement without naming a certifier.
And in the paperwork, if you are expecting a UL mark and the documentation shows an ETL mark from Intertek, nothing is wrong. Different laboratory, same standard.
Quick Tip: Write both requirements into the specification. Require that the operator be certified to ANSI/CAN/UL 325 and that it be installed and commissioned in accordance with that certification, with commissioning documentation submitted at closeout. One sentence closes the most common compliance gap on the project.
Where UL 325 shows up in a project
Phase | What is needed | Who asks |
Design development | Confirmation the specified equipment is certified for the intended application | Architect, owner |
Construction documents | Specification language covering certification, entrapment protection, and installation | Architect |
Permitting | Certification documentation for the specified operator | Building department |
Submittals | Product data, shop drawings, safety device schedule | Architect, GC |
Rough inspection | Verification of dedicated circuits, backup power provisions, sensor rough-in | Inspector |
Commissioning | Force testing results, sensor verification, safety feature testing | Contractor, AHJ |
Final inspection | Certification documents plus commissioning records | Inspector |
Closeout | Complete package for owner, insurer, and facility records | Owner, insurer |
The pattern worth noticing is that certification documentation is requested at multiple points by different parties, and it is almost never a single document. The UL 325 safety certification documentation is the starting point, not the complete answer.
What belongs in the specification
Generic language produces generic compliance. These items give the specification teeth.
Name the standard and the certifier requirement. State that the operator shall be certified to ANSI/CAN/UL 325 by a Nationally Recognized Testing Laboratory, and require certification documentation covering the equipment supplied. "Compliant with applicable safety standards" establishes nothing, and "UL listed" is narrower than you mean.
State the entrapment protection requirement explicitly. Protection methods vary in how they detect obstruction and how they respond. The right choice depends on the door type, the traffic, and whether the application is residential or public. This decision belongs to the design team rather than the installer, and leaving it unstated means it gets made in the field.
Require installation in accordance with the certification. Covered above, and worth the sentence.
Require commissioning documentation at closeout. Force testing results, sensor verification, and safety feature testing, delivered as a record rather than as a verbal confirmation.
Address emergency operation directly. Specify manual release provisions and, where the project requires continued operation during outage, backup power. Backup battery systems are a specification item, not an accessory.
Coordinate with fire alarm and egress requirements. Automated doors on an egress path have obligations that go beyond UL 325, and the coordination has to happen during design rather than at inspection.
Specify the manual override hardware. Brake clutch assemblies provide controlled stopping and emergency manual override, and their specification affects whether the door is operable when the power is not.
For a broader checklist of what to resolve before an automated door specification goes out, our guide to the questions architects should ask about automated door systems covers the technical questions that most often surface too late.
Standards that travel alongside UL 325
UL 325 rarely operates alone. Depending on the application, several other standards apply, and a specification that names only UL 325 may leave gaps.
ANSI/BHMA A156 series governs power operated pedestrian doors. Different documents within the series address full power operation, low energy operation, and power assist, and the distinction matters because low energy doors face different requirements from full power doors. Which applies depends on how the door is activated and how fast it moves.
ADA and accessibility standards address clear width, opening force, and control reach ranges. These are separate from UL 325 and can drive different design decisions. Our guide to automated doorways in luxury homes covers accessibility considerations in residential applications, and commercial automatic doors addresses the higher-traffic requirements.
The International Building Code and its local amendments determine what your specific jurisdiction requires. Amendments vary, and the authority having jurisdiction has the final word regardless of what the base code says.
Fire and life safety requirements apply wherever an automated door sits on an egress path, and they can override normal operating behavior entirely.
Did You Know? A building department can require documentation the base code does not mention. Local amendments and individual AHJ practice vary considerably, which is why the documentation package is worth assembling early rather than in response to a request.
Where compliance breaks down
Five failure patterns account for most of the problems, and all five are avoidable at the specification stage.
Documentation requested at the worst possible moment. An inspector asks for certification at final inspection, nobody has it assembled, and occupancy waits while the contractor chases the manufacturer. Collect the package at submittal.
Safety devices adjusted or bypassed during commissioning. A door that is not closing reliably gets its force settings raised, or a sensor triggering falsely gets disconnected. Both fixes work. Both void compliance. Both are commonly still in place at final inspection.
Entrapment protection unspecified and chosen by default. When the specification is silent, the installer selects, and the selection reflects what is convenient rather than what the application requires.
Retrofit assumed to inherit compliance. Adding an operator to an existing door does not make the assembly compliant. The existing hardware, frame, and structure all have to suit powered operation, and the operator certification does not cover what it was attached to.
Custom configurations outside the certification. A certification covers a tested configuration. Unusual mounting, non-standard hardware, or a combination the manufacturer did not test may put the installation outside what the certification describes. This needs resolving with the manufacturer during design, not discovering during inspection.
Quick Tip: Ask the installer to demonstrate the safety features at final walkthrough rather than accepting a report. Obstruct the door and watch it reverse. It takes two minutes and it is the only verification that reflects the door's actual state.
Assembling the documentation package
A complete package generally includes:
Certification documentation for the specified operator
Product data covering the operator, control system, and safety devices
The safety device schedule, identifying what is installed where
Shop drawings showing mounting and configuration as built
Commissioning records including force testing and sensor verification
Manual release and emergency operation instructions
Maintenance requirements and recommended service intervals
Our technical specifications and configuration drawings library holds motor specifications, mounting configuration drawings, component data, and certification documentation for reference during design development and permitting.
Beyond compliance, this package has a second life. Owners inherit it, facility teams reference it years later when a component needs service, and insurers ask for it after an incident. A package assembled properly at closeout is worth considerably more than one reconstructed under pressure.
Frequently Asked Questions
Is UL 325 required by code?
It depends on jurisdiction and application. Many building codes reference UL 325 for automated door operators, and many building departments request certification documentation at permitting or inspection regardless of whether the base code names it explicitly. Local amendments vary and the authority having jurisdiction has final say. Specifying a certified operator is the safe default because it satisfies the requirement wherever it exists and creates no problem where it does not.
Does a certified operator make my installation compliant?
No. Certification covers the product in a tested configuration. It says nothing about whether the equipment was installed the way it was tested. Sensors mounted incorrectly, force settings adjusted past their tested limits, or safety devices bypassed during commissioning all produce a non-compliant installation using a fully certified operator. Specify installation in accordance with the certification and require commissioning documentation at closeout.
Does UL have to be the certifying body?
No. UL 325 is a standard, and several Nationally Recognized Testing Laboratories certify against it, including Intertek, TÜV, and CSA. Their marks are equally valid. Specifying "UL listed" is narrower than most architects intend and can exclude an operator certified by another NRTL to the same standard. "Certified to ANSI/CAN/UL 325 by a Nationally Recognized Testing Laboratory" is the phrasing that says what you actually mean.
Does one certificate cover everything a manufacturer makes?
Not automatically. Certification documents describe the equipment they cover, and a manufacturer may hold more than one across a range. Rather than assuming, ask the supplier to confirm that the documentation covers what is being supplied for your project.
What documentation will a building inspector actually ask for?
Practice varies by jurisdiction, but certification documentation for the specified operator is the common request, sometimes accompanied by commissioning records showing that safety features were tested and function. Some inspectors also want the safety device schedule and shop drawings showing as-built configuration. Assembling the full package at submittal costs little and prevents an occupancy delay.
Do residential automated doors need UL 325 certification?
The safety concerns are identical regardless of occupancy, and residential installations commonly fall under the same requirements. Beyond code, specifying a certified operator on a residential project matters for insurance and for liability if an injury occurs. The standard exists because powered doors have injured people, and a residence is not exempt from that.
Can an existing door be retrofitted to a compliant automated system?
Frequently, but the assembly has to be evaluated rather than assumed. The frame and structure must support the forces automation introduces, the existing hardware must suit powered operation or be replaced, and the electrical infrastructure must supply dedicated power. A certified operator attached to an unsuitable door does not produce a compliant installation. Professional evaluation determines feasibility and identifies what needs upgrading first.
What is the difference between UL 325 and the ANSI/BHMA A156 standards?
UL 325 is a product safety standard governing the operator itself, covering entrapment protection, force limits, emergency operation, and electrical safety. The ANSI/BHMA A156 series addresses power operated pedestrian doors as installed systems, with different documents covering full power operation, low energy operation, and power assist. They are complementary rather than alternative, and many pedestrian door applications engage both.
Who is responsible for compliance on a project?
Responsibility is distributed, which is exactly why it slips. The architect specifies, the manufacturer certifies the product, the installer installs and commissions, and the AHJ verifies. The gap tends to open between specification and commissioning, where nobody has explicitly been made responsible for confirming that the installed system still matches what was specified. Requiring commissioning documentation at closeout assigns that responsibility to someone in writing.
How often should safety features be tested after installation?
Annual inspection is the general recommendation for residential installations, and semi-annual is worth considering for commercial applications with high cycle counts. Safety features can drift out of adjustment through normal use, building settlement, and component wear. A door that passed inspection three years ago is not necessarily performing to the same standard today, and the components most likely to drift are the ones that matter most.
Specifying with confidence
UL 325 is not complicated once the central distinction is clear. It certifies the operator, not the installation, and closing the gap between those two is a specification problem rather than a product problem.
The specifications that hold up name the standard, require certification by a Nationally Recognized Testing Laboratory, require installation in accordance with that certification, and demand commissioning documentation at closeout. Four requirements, and they eliminate most of what goes wrong.
Door Automation Systems works with architects, builders, and facility teams on automated door specification from design development through commissioning and closeout, including the documentation package building departments request. If you are specifying automated doors and want the compliance path settled before construction documents go out, get in touch.
Complete motor specifications, configuration drawings, component data, and certification documentation are available in our technical library for architects and installers.
This article is provided for general informational purposes and does not constitute code, legal, or engineering advice. Safety standards, building codes, and local amendments are revised over time, and requirements vary by jurisdiction, occupancy, and application. Verify current requirements with the authority having jurisdiction, a licensed design professional, and the operator manufacturer for your specific project. Door Automation Systems makes no warranty as to the completeness or applicability of this information to any particular installation.
