Intersection-support RFQ guide
Traffic Signal Poles: What to Confirm Before RFQ
A traffic signal support should be quoted from the intersection layout and the actual equipment schedule—not a mast-arm length alone. Keep the signal heads, pedestrian equipment, cable route, access and project review path visible from the first RFQ.
This is a buyer and engineering-input guide. It does not establish traffic control design, structural capacity, foundation design, installation method or authority approval.
The short answer: quote the intersection assembly
A traffic signal pole is part of an intersection assembly. The useful RFQ shows the layout, pole positions, mast-arm or bracket concept, signal and pedestrian equipment, cable/control interfaces, access constraints and the parties responsible for final review.
Some inputs may be provisional at the budget stage. Identify them clearly instead of converting an example photo or a previous project into a final configuration.
Layout and movements
Intersection or access-road drawing, pole locations, mounting side/direction, nearby utilities or structures, curb/grade context and available authority/client requirements.
Equipment schedule
Signal heads, pedestrian signals, signs, cameras or other attachments; model/data status, mounting interface, orientation, quantity and supplied information when available.
Project interfaces
Cable route and entry, base/civil status, installation and maintenance access, supply boundaries and responsible review parties.
What belongs in a traffic signal pole RFQ
An early RFQ does not need to pretend that every design decision is complete. It should make the known inputs, open items and review responsibilities clear.
| Intersection and layout | Provide the available plan, pole positions, approaches, intended mounting directions, adjacent structures, finished-grade context, utilities and project/authority requirements. |
|---|---|
| Pole and mast-arm concept | Preferred support type, pole and mast-arm arrangement, signal positions, access-door direction, base/grade information and reference drawings or photos when available. |
| Signal and attachment schedule | Signal heads, pedestrian signals, signs, cameras or other devices; selection status, mounting interface, quantity, orientation, supplied weight/projected-area information where available and cable/control notes. |
| Electrical and cable interface | Project-supplied power/control information, cable entry and routing, enclosure/interface requirements, ownership boundaries and responsible electrical coordination parties. |
| Civil, access and site context | Base/foundation status, work area, traffic or pedestrian restrictions, drainage/site inputs where available, installation approach and maintenance access constraints. |
| Review and release scope | Budget or formal quote stage, drawing/submittal needs, responsible traffic/structural/electrical/civil/maintenance reviewers, authority conditions and production-release requirements. |
Keep equipment selection visible
A signal head or pedestrian device can be unselected during early pricing. It should still be named as provisional so that mounting zones, cable routing, access and review are not silently omitted.
Where device data is available, attach it. Where it is not, state the expected function, location and party responsible for final selection rather than inventing dimensions or loads.
Plan cable and service access before release
The signal assembly needs a practical access and cable discussion beside the equipment schedule. Identify cable entry, door direction, anticipated service approach, working-area restrictions and the project parties coordinating final maintenance.
A clear elevation does not prove that every connection and enclosure can be installed or serviced on the actual site. Keep open constraints visible for the designated review.
At the pole
Cable entry, access-door direction, lower equipment, mounting faces and any enclosure or controller interfaces.
At the mast arm
Signal and pedestrian-device positions, attachment brackets, orientation, cable path and access approach.
At the intersection
Traffic/pedestrian restrictions, work area, utilities, civil boundaries, maintenance access and project ownership.
A practical RFQ sequence
Separate budget intent from approved production release.
| 1. Concept or budget | Send layout, preliminary support/equipment concept, known interfaces and unresolved items. |
|---|---|
| 2. Drawing coordination | Align support, mast arm, signal equipment, mounting zones, cable route, grade/base status and access direction. |
| 3. Project review | Confirm responsible traffic, structural, electrical, civil, installation, maintenance, safety and authority reviews with required documentation. |
| 4. Production release | Release only approved support configuration, equipment schedule, interfaces, finish, documents and contracted scope after designated confirmation. |
Common gaps that create rework
A short unresolved-items list is more useful than a precise-looking pole quote built from incomplete intersection information.
Only mast-arm length is provided
Add the layout, equipment positions, mounting direction, cable route, base/grade context and review scope.
Equipment is added later
List likely signals, pedestrian devices, signs, cameras or other attachments during the first RFQ, even when final models remain open.
Cable route is not assigned
State entry preference, power/control boundaries, route assumptions and responsible coordination parties.
Service access is omitted
Identify traffic controls, working area, maintenance constraints and access-door direction before final release.
Related guides for the project package
Use these guides to connect traffic signal support inputs with the wider light-pole RFQ package.
Source references
These public FHWA and U.S. Department of Energy references provide general lighting-infrastructure context. They do not replace project-specific traffic, structural, electrical, civil, access, safety or authority requirements.
FAQ
What should a traffic signal pole RFQ include?
Include the intersection or site layout, signal and pedestrian-equipment schedule, proposed pole and mast-arm concept, mounting and cable interfaces, grade/base status, access constraints, site information, applicable standards or authority requirements and responsible project-review parties.
Can a traffic signal support be quoted from a photo or arm length alone?
A visual reference or nominal arm length can begin a concept discussion, but it does not define the complete assembly. The actual signal equipment, mounting positions, cable routing, site/civil interface, access and project review path also need to be identified or marked open.
What equipment information is useful before quotation?
Send available signal-head, pedestrian-signal, sign, camera or other attachment data; mounting interface, quantity, orientation, supplied weight or projected-area information where available, cable/control notes and selection status. Unknown devices should be stated as open.
Who confirms the final traffic signal pole configuration?
The responsible project parties confirm the final configuration through applicable traffic, structural, electrical, civil, installation, maintenance, safety and authority review. A supplier quotation or buyer guide does not replace that process.
Send a Traffic Signal Pole RFQ
Send the intersection layout, equipment schedule, support concept, cable/power notes, access constraints, base/civil information and required review stage. Mark open items clearly.
When is a custom signal pole required?
A custom signal pole is appropriate when the intersection layout, carried signal equipment, arm or bracket arrangement, access method, cable routing or installation interface must be coordinated for a specific project. The quotation discussion should identify those items and clearly mark any equipment or authority-review decision that remains open.
For the product-side configuration, see the custom traffic signal pole page.
Leave a Reply