Low-Voltage Field Reference • Technical term
End-of-Line Resistor (EOL) Explained for Alarm and Access Inputs
An end-of-line resistor lets compatible equipment distinguish expected circuit states by measuring resistance or voltage. The required value and arrangement are controller-specific; the resistor belongs at the supervised end of the field circuit, not wherever it is easiest to reach.
Direct answer
what is an end of line resistor: the practical answer
An end-of-line resistor lets compatible equipment distinguish expected circuit states by measuring resistance or voltage. The required value and arrangement are controller-specific; the resistor belongs at the supervised end of the field circuit, not wherever it is easiest to reach.
For a working contractor, the value of this definition is its ability to translate field language into a verifiable design decision. Use the sequence meaning → project consequence → evidence → acceptance. The label alone never proves compatibility, compliance or performance.
What this changes in the design package
End-of-Line Resistor (EOL) Explained for Alarm and Access Inputs should change at least one controlled project record. On a floor plan, identify the physical location or route affected by panel input specification and required resistor value and tolerance. On the riser or signal-flow drawing, show how the selected equipment, pathway, power and communications relationships support the intended outcome. In the schedule, preserve the exact data needed to buy, configure, install and test the system.
Plan
Show the device, route, zone or interface in context. Use stable IDs rather than relying on a symbol alone, and flag any assumption that can change quantity or performance.
Riser or schematic
Show origin, destination, intervening equipment, shared infrastructure and interface responsibility. A diagram should expose relationships the floor plan cannot show clearly.
Schedule
Record single or dual supervision scheme, contact state logic, cable resistance and route and tamper and enclosure plan where they can be reviewed and revised without redrawing the entire plan.
Proposal
State the verified design basis, named allowances, exclusions, owner/IT/electrical dependencies, testing method and the event that triggers a change order.
Field method
A repeatable definition workflow
Start by deciding what the term must communicate on this project. Then connect the definition to a selected device, a measurable setting, a drawing note and an acceptance result.
- 1. measure each expected state at the panel.
- 2. open and short the field cable intentionally.
- 3. confirm alarm, trouble and tamper reporting.
- 4. record actual resistor placement.
After the final step, repeat the original operating scenario. A correction is not complete until the system passes the required function, the drawing and schedule match the installed condition, and the handoff record identifies what changed.
Decision and evidence table
| Question | Evidence to collect | Where to record it | Acceptance signal |
|---|---|---|---|
| What controls panel input specification? | measure each expected state at the panel; use exact model, reading, setting, photo or log evidence. | zone wiring detail, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls required resistor value and tolerance? | open and short the field cable intentionally; use exact model, reading, setting, photo or log evidence. | resistance-state table, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls single or dual supervision scheme? | confirm alarm, trouble and tamper reporting; use exact model, reading, setting, photo or log evidence. | device schedule note, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls contact state logic? | record actual resistor placement; use exact model, reading, setting, photo or log evidence. | commissioning measurements, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
Keep evidence close to the decision it supports. A screenshot without an equipment ID, a cable test without the cable identifier, or a code note without edition and jurisdiction is difficult to audit later.
Technical deep dive
Six controls that make end of line resistor defensible
1. panel input specification
trace panel input specification before the team commits EOL resistor to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to measure each expected state at the panel. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for selecting a resistor by habit, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the zone wiring detail. Tie it to end of line resistor and EOL resistor with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
2. required resistor value and tolerance
reconcile required resistor value and tolerance before the team commits supervised input to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to open and short the field cable intentionally. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for installing EOL inside the panel, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the resistance-state table. Tie it to end of line resistor and supervised input with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
3. single or dual supervision scheme
challenge single or dual supervision scheme before the team commits double end of line to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to confirm alarm, trouble and tamper reporting. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for mixing normally open and normally closed logic, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the device schedule note. Tie it to end of line resistor and double end of line with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
4. contact state logic
preserve contact state logic before the team commits alarm zone wiring to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to record actual resistor placement. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for assuming values are interchangeable among controllers, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the commissioning measurements. Tie it to end of line resistor and alarm zone wiring with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
5. cable resistance and route
establish cable resistance and route before the team commits tamper supervision to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to measure each expected state at the panel. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for selecting a resistor by habit, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the zone wiring detail. Tie it to end of line resistor and tamper supervision with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
6. tamper and enclosure plan
measure tamper and enclosure plan before the team commits end of line resistor to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to open and short the field cable intentionally. Compare the evidence with the intended intrusion detection outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for installing EOL inside the panel, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the resistance-state table. Tie it to end of line resistor and end of line resistor with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
Field-capture worksheet
Before leaving the site, collect enough evidence that another qualified person can reconstruct the decision. Start with the site, floor, room and stable asset ID. Record the date, technician and current drawing revision. Photograph the overall context before taking close-ups, and place a readable label or reference in the image when practical.
- Identity
- Exact manufacturer, model, firmware or listing, terminal names, cable ID, panel/port/zone/door address, and the related plan symbol.
- Observed state
- What the user reported, what the technician reproduced, timestamps, LEDs or messages, logs, settings and whether the condition is continuous or intermittent.
- Measured state
- Applicable voltage, current, resistance, optical level, cable result, protocol status, signal format or environmental condition, including the instrument and test boundary.
- Change control
- The one change made, authorization, before/after evidence, temporary workaround, regression checks and any effect on other devices or shared infrastructure.
For this topic, call out panel input specification, single or dual supervision scheme and cable resistance and route. Use the vocabulary end of line resistor, EOL resistor, supervised input consistently so the field note, drawing, schedule and proposal can be found together.
Worked field example
From an uncertain condition to a controlled record
A renovation team receives a report involving end of line resistor. The available plan shows a symbol, but it does not identify panel input specification, required resistor value and tolerance or single or dual supervision scheme. Instead of pricing or repairing from the incomplete symbol, the team opens a single issue record and assigns the affected equipment, cable or location a stable ID.
The technician collects the current settings, model information, photos and measured state. The designer compares that evidence with the selected equipment documentation and the current authoritative sources listed below. The estimator separates verified scope from allowances. The project manager records who owns any external dependency, such as an electrical circuit, network policy, door hardware condition, AHJ decision or owner-furnished device.
The corrected package includes the zone wiring detail, resistance-state table and device schedule note. The team then repeats the operating test under the same conditions that produced the original question. That closed loop turns EOL resistor and supervised input from search terms into traceable project decisions instead of isolated notes.
Common failure modes—and why they happen
Failure 01
selecting a resistor by habit
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 02
installing EOL inside the panel
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 03
mixing normally open and normally closed logic
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 04
assuming values are interchangeable among controllers
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
When a failure involves regulated life safety, egress, listing, energized work, public-safety radio, or code interpretation, stop at the boundary of your authorization. Escalate to the responsible qualified party and preserve the condition and evidence.
Minimum contractor deliverables
A useful answer survives the handoff from design to estimating, proposal, installation and closeout. At minimum, create the following:
- zone wiring detail.
- resistance-state table.
- device schedule note.
- commissioning measurements.
Each deliverable should show the project, revision, author, review status and the identity of the system element it controls. If a value is not verified, label it as an assumption, allowance, pending submittal or owner/AHJ decision. Do not let a blank field become an accidental commitment.
How to carry the answer into scope and proposal language
Describe the outcome first: what the customer will receive, where it applies and how it will be tested. Then name the basis used for end of line resistor, including the controlling drawing revision and selected equipment data. Include the labor and documentation needed to produce zone wiring detail and resistance-state table.
Separate dependencies explicitly. Examples include usable owner drawings, accessible ceilings, working branch power, network addressing and policy, compatible owner equipment, door hardware readiness, permits, shutdown windows, AHJ review and access to occupied areas. If one of those facts is unknown, write an allowance or qualification and define how the price changes when the fact is confirmed.
Finish with acceptance: identify who witnesses the test, what evidence is retained and which result constitutes completion. This makes the page commercially useful without turning it into a product pitch.
Commissioning, handoff and future service
Commissioning should prove the designed function, not simply show that equipment turns on. Run the accepted scenario, an expected failure or trouble state, recovery, and any interface that crosses to network, electrical, fire alarm, door hardware, controls or owner systems. Save results against stable IDs and the approved revision.
At handoff, give the owner the zone wiring detail, resistance-state table, final configuration, approved substitutions, warranties and the contact path for unresolved external responsibilities. Remove default credentials and temporary access where applicable. Explain which changes can invalidate the result—for example a new firmware release, equipment replacement, changed speaker tap, moved camera, added cable, revised AHJ direction or modified switch policy.
Future service begins by comparing the current condition with this accepted baseline. If the record is missing, recreate it before making broad changes. That discipline reduces repeated troubleshooting, protects proposal scope, and lets the next technician distinguish a design issue from a later operational change.
Frequently asked questions
What should I verify first?
Start with panel input specification and required resistor value and tolerance. Establish the exact product, project location and current system state before applying a diagram or changing configuration.
Can I use this page as a construction detail?
Use it as an editorial planning and verification aid. Convert it into a project detail only after reconciling the manufacturer instructions, adopted requirements, approved submittals and responsible professional or AHJ direction.
What belongs in the closeout package?
Include zone wiring detail, resistance-state table, device schedule note, commissioning measurements, plus test evidence, deviations, final settings and the identity of the person or authority that accepted the result.
What should I read next?
Continue with Security Camera WDR Explained: When Wide Dynamic Range Helps, ONVIF Profile S vs Profile T: What Security Designers Should Specify, OSDP Access Control Explained: Wiring, Supervision and Secure Channel, Wiegand Reader Interface: Signals, Limitations and Upgrade Planning and the Intrusion Detection design software resource.
Authoritative references and how to use them
These links are starting points for current primary-source information. Confirm the current edition, product revision, publication status, jurisdiction and applicability. Accessed for this release on 2026-08-08.
- Security Industry Association OSDP — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- UL Standards and Engagement — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- CISA Secure by Design — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.