Automated Gate Installation and UL 325 Safety Standard

Purpose

An automated gate is a machine with the strength to crush a child against a post, and UL 325 exists because that has happened often enough to write a standard around it. This procedure exists so "the operator works" is reached by verifying every entrapment device is actually monitored and every force is actually measured, not by watching one clean demo cycle. A gate that opens and closes correctly on the bench and has no monitored secondary sensor is not commissioned; it is a liability sitting in the driveway waiting for the day the primary sensor fails silently.

Scope

Covers installing a powered operator on a swing or slide gate already built and hung, from confirming the gate's own construction through device wiring, force verification, travel-limit setting, and customer handoff, for Class I (residential) and Class II (light-commercial general-access) installations.

Does not cover hanging or building the gate itself; the swing gate hanging and sliding gate track HowTo pieces own that and this SOP assumes it's already done and verified. Does not narrate the UL 325 class definitions, device catalog, or F2200 construction requirements; the automated gate compliance reference owns that and this SOP cites it. Does not cover pool-barrier self-closing and self-latching verification where the gate also serves as a required pool barrier; that runs under its own standard in addition to this one. Class III and IV (industrial, restricted, guard-operated) are out of scope.

Roles and responsibilities

Procedure

1. Confirm the gate meets ASTM F2200 construction before mounting anything. Check infill openings against the maximum sphere passage in the swept path the current edition of F2200 sets, commonly 2.25 inches but confirm the figure against the edition your jurisdiction has adopted before citing it, confirm exposed slide-gate rollers are guarded, and confirm no pinch point forms between the gate and any fixed post or wall as it travels. Acceptance: every opening, roller, and closing gap checked and passing. Wrong looks like proceeding because the gate "looks fine" without measuring the bottom-rail opening, exactly where a small child's hand reaches. Stop rule: any failing dimension stops the automation job here; the gate is modified or replaced before an operator goes on it, regardless of how much the customer wants it running today.

2. Classify the installation by actual use, not gate size. Determine Class I (single-family residential) versus Class II (general public access: a shared apartment drive, a retail lot). Acceptance: the class documented in writing, matched against the device schedule the compliance reference sets for it. Wrong looks like defaulting to Class I because the hardware in the truck is residential-grade. Stop rule: an ambiguous-use site (delivery or visitor traffic beyond the household) is classified up to Class II, never down.

3. Confirm or route dedicated power before mounting the operator. The operator needs its own GFCI-protected circuit at the manufacturer's amperage; where the crew isn't licensed for the panel connection, this hands to a licensed electrician and does not proceed on a borrowed circuit. Acceptance: a tested, correctly rated, GFCI-protected circuit terminated at the operator. Wrong looks like running the operator off an extension cord "to test it," which then becomes the permanent supply. Stop rule: no verified dedicated circuit, no powered testing of any kind. Hazard: panel work is not a task for an unlicensed installer; if nobody on site is qualified for it, the work goes to the electrician, not to whoever is confident with a multimeter, and if a shock or arc occurs during the panel work, the circuit is shut down at its source breaker before anyone touches the installer.

4. Mount the operator per the manufacturer's dimensioned geometry, not a field guess. Set the arm or rack-and-pinion mounting to the drawing for this gate's swing radius or slide length, and torque every structural fastener to spec. Acceptance: mounting dimensions matching the drawing within its stated tolerance, fasteners torqued. Wrong looks like eyeballing the arm geometry "about where it looks right," which changes the force the operator produces past what its entrapment settings were calibrated for. Stop rule: no drawing on hand for this operator-and-gate pairing, no mounting.

5. Install and wire primary and secondary entrapment protection matched to the class. Mount photo eyes on both sides of the path at the heights the device schedule calls for, and contact-edge sensors on every leading, trailing, and pinch-point edge the class requires, each landed on the operator's own monitored input, never a shared or spliced one. Acceptance: every required device on its own monitored terminal, confirmed against the wiring diagram terminal by terminal. Wrong looks like a photo eye that's mounted and lit but wired to an unmonitored auxiliary input, correct on a walk-by and worthless in practice. Stop rule: any device not landed on a genuinely monitored input does not count as installed.

6. Prove the monitoring is real by deliberately breaking each sensor's circuit in turn. With the area clear, disconnect or block one device and command a cycle; repeat one device at a time. Acceptance: the operator refuses to run every time, for every device, and logs the specific fault. Wrong looks like the gate running anyway with a sensor unplugged, meaning that device was never actually monitored. Stop rule: any device that fails to stop the operator sends the install back to step 5 for that device before anything else proceeds. Hazard: faulting a sensor removes the protection this step exists to verify, so everyone stays clear of the swept path for the whole test; restore each device immediately after its own test and re-run that same device's fault test a second time to confirm the restoration actually reconnected it, before faulting the next one, and never leave more than one device disconnected at a time.

7. Measure operating force against the operator's programmed setting, using a test object, never a hand, arm, or leg. With every device restored and passing step 6, place the manufacturer's test object, or a padded rigid rod, in the closing path and run a full cycle, reading peak force off the operator's display or an inline gauge. Acceptance: measured force at or below the programmed setting, both directions, recorded. Wrong looks like calling a force spike "close enough," when the whole point of a measured reading over a felt one is that a hand cannot reliably tell 15 pounds of resistance from 40. Stop rule: force exceeding the programmed setting is not adjusted upward to pass; the mechanical cause (binding track, misaligned arm, worn roller) is found and fixed and the test reruns clean. Never stand in the path or reach into the closing gap to "feel" resistance at any point.

8. Set mechanical travel stops and confirm they hold under power, independent of the operator's electronic limits. Install or verify a physical stop at both full-open and full-close, run three full powered cycles, and confirm the gate contacts the mechanical stop, not just the programmed limit, at both ends. Acceptance: gate reaches and holds against a physical stop at both limits across all three cycles. Wrong looks like trusting the limit switch alone because it "always stops right" on the bench; a switch that drifts over months of cycling has nothing behind it without a mechanical stop. Stop rule: no functioning mechanical stop at either end, no handoff, regardless of how clean the powered cycles looked. Hazard: the swept path is live for all three powered cycles the same as any other test in this SOP; clear it before each cycle rather than assuming a bench-tested limit switch means the gate will stop where expected.

9. Post signage, verify battery backup, and complete a customer walkthrough. Mount the manufacturer's pinch-point placards on both sides at the specified locations, load-test the battery backup against its rated runtime (some jurisdictions set their own minimum for gates serving fire-department access; confirm locally rather than assuming a figure), and walk the customer through the monthly self-test: open the gate, place a test object in the closing path, confirm it stops and reverses. Acceptance: signage posted, battery load-tested, walkthrough completed and acknowledged in writing. Stop rule: no signed acknowledgment, no closed job; a customer never shown the self-test can't catch a failed sensor between visits.

The record this produces

One record per install: the F2200 pass from step 1, the documented class and device schedule, the electrician's circuit sign-off where applicable, terminal-by-terminal wiring confirmation, every fault-test result with restoration confirmed, the measured open and close force against the programmed setting, the mechanical-stop confirmation, the battery load-test, and the signed walkthrough. The office files it with the permit paperwork; a tech on a later service call reads the programmed force figure before touching the setting rather than guessing what "normal" was.

One run, including the stop that fired

Job: a Class I swing-gate operator on a single-family driveway, replacing a homeowner-installed unit with no secondary sensor. Step 1 passed clean on 2 inch picket spacing. Step 2 classified it Class I. Step 3 handed the panel connection to the shop's electrician, who landed a new GFCI-protected 20 amp circuit.

Steps 4 and 5 went in clean: operator mounted to the drawing's arm geometry, a photo-eye pair at spec height and a contact edge on the leading rail, each landed on a labeled terminal.

Step 6 fired the stop. Blocking the photo eye and commanding a cycle, the gate ran anyway. The wiring diagram showed the pair landed on the auxiliary input rather than the monitored primary, an easy mix-up on this operator's terminal block, one row apart and both labeled in small print. The install went back to step 5, the leads moved to the correct terminals. Re-running step 6, the gate now refused and threw the correct fault code; the contact edge tested clean on its own first pass. Both devices were restored and each individually re-tested a second time before moving on.

Step 7 measured 22 pounds peak closing force against a 25 pound programmed setting, a pass with margin, using the padded test rod. Step 8 confirmed the gate held against physical stops at both ends across three cycles. Step 9 posted signage, load-tested the battery to its rated 4 hours (no local emergency-access minimum applied here, confirmed with the building department beforehand), and walked the homeowner through the self-test, signed on the spot.

When the site does not match this procedure

If the gate fails step 1 and the customer wants the operator installed anyway to skip the cost of gate work, refuse and document it; do not automate a gate that fails its own construction standard. If the quoted operator model is unavailable and a substitute has a different force range or terminal layout, restart from step 4 on the substitute's own manual rather than carrying over the original's dimensions or wiring notes. If a Class II site can't get every required secondary device installed on the scheduled day, the gate does not go into service under power in the meantime; leave it manual-only and lock out the operator circuit until the remaining devices pass step 6.

References

• Manuall internal: Fence Contractor Automated Gate UL 325 and ASTM F2200 Compliance (class definitions, device catalog, construction requirements)
• Manuall internal: Fence Contractor Swing Gate Hanging and Hardware Installation Technique / Sliding Gate Track and Roller Installation Technique (the mechanical work this SOP assumes is complete)
• Manuall internal: Fence Contractor Pool Barrier Gate Self-Closing Verification Standard (run in addition to this SOP where the gate also serves pool-barrier duty)
• UL 325, Standard for Door, Drapery, Gate, Louver, and Window Operators and Systems
• ASTM F2200, Standard Specification for Automated Vehicular Gate Construction