Low Voltage RFP Requirements: What Every Spec Should Include

What "low voltage" actually covers

The phrase "low voltage" is a trade-classification holdover from the electrical code — anything operating below 70 volts is low voltage, distinct from line-voltage electrical work above that threshold. In practice, that catch-all definition has grown to cover six different commercial trades: structured cabling, surveillance, access control, fire alarm and life safety, audiovisual, and building automation.

Each of those six trades has its own state licensing, its own installer credentials, its own manufacturer relationships, and its own field crew. Some contractors hold licenses across all six; most specialize in two or three. An RFP that says "low voltage work" without specifying which work types is asking each bidder to interpret scope on their own. The bids come back priced against six different interpretations.

The fix is structural: scope each work type separately in the RFP, require credentials specific to that work type, and let bidders no-bid the work types they can't perform directly. That produces honest responses where direct capability is distinguished from subcontracted capability — both legitimate, but only one of them should be priced the same.

State licensing — the disqualifier most RFPs miss

Low voltage is regulated state by state, and the licensing requirements vary significantly. The RFP that doesn't require state-by-state license disclosure ends up with bids from contractors operating outside their license — a problem that surfaces at the first inspection.

The major-state landscape:

• California: C-7 Low Voltage Systems license required above the $500 jurisdictional threshold. Verify on the CSLB license lookup.
• Texas: Texas Department of Licensing and Regulation issues Electrician licenses with low-voltage endorsements; Texas Commission on Private Security regulates security-system work.
• Florida: ES Limited Energy Systems Specialty Contractor (ES) for low-voltage work; separate Burglar Alarm and Fire Alarm licenses for those specialties.
• Tennessee: LLE Limited Licensed Electrician with low-voltage endorsement.
• Massachusetts: Systems Contractor (SC) or System Technician (ST) with the appropriate endorsement.
• Other states: Many states delegate to the municipal level. The RFP must require bidders to disclose every jurisdiction (state and municipal) in which the project will operate.

What the RFP must require: a complete list of every state and municipal license the bidder holds active at the time of response, with license numbers and expiration dates. Generic "we're fully licensed nationally" is the single most common bidder claim that doesn't survive a quick CSLB lookup. Reject responses that don't itemize.

The 6 work types every spec should scope separately

For each work type: what it covers, which credentials apply, and what the licensing specificity looks like in most jurisdictions. The RFP should have a separate scope section for each work type the project touches, even if one bidder is responding across all of them.

Single-vendor stack vs multi-vendor specialty

The RFP must declare upfront whether it's buying an integrated single-vendor platform or assembling specialty vendors per work type. The decision drives bid count, bid spread, and the integration risk over the system's lifetime.

An earned opinion:Splitting access control and surveillance across two specialist vendors usually beats a single integrated platform from one vendor. Integrated single-vendor platforms (the "one pane of glass" pitch) typically cost 30-60% more on hardware and lock the client into that vendor's roadmap. Two specialists with documented integration points (ONVIF for cameras, OSDP for readers) cost less, swap independently, and survive vendor consolidation events that always happen on a 5-10 year horizon. The opposite is true for sites under 8 cameras and 4 doors — integration overhead isn't worth the savings, and a packaged single-vendor product wins on simplicity.

What the RFP must specify:

• Stack architecture: single-vendor or multi-vendor (each affects pricing and vendor qualification).
• For multi-vendor: which integration standards are non-negotiable (ONVIF Profile S for cameras, OSDP for ACS readers, BACnet for BMS, SIP for VoIP).
• Reader-to-controller wiring standard: OSDP is the current standard; Wiegand is legacy and should be phased out, not specified for new work.
• VMS or PSIM platform if recording or aggregation matters across cameras from multiple manufacturers.

The integration trap: how RTSP, ONVIF, and OSDP show up

Most low-voltage RFPs underspecify integration, then blame "vendor compatibility issues" when the system doesn't work end to end. The integration trap is a real cost — usually the largest hidden cost in a multi-vendor low-voltage project — and it's avoidable if the RFP specifies the right protocols up front.

We took over a 21-camera site where cameras 1-10 had been sold as one brand but were actually Jovision OEM (RTSP path /live0.264) and cameras 11-21 were a Hikvision-clone OEM (RTSP path /Streaming/Channels/101). The client had no documentation. The original installer never noted it. Nothing worked through the new VMS until we walked the site, sniffed the streams, and re-documented every RTSP path and credential. Two days of work that should have been delivered with the original install paperwork. The lesson isn't that OEM rebrands are bad — it's that the RFP must require RTSP path documentation as a closeout deliverable, not a nice-to-have. Same logic applies to ONVIF profile support and OSDP secure-channel keys.

Integration deliverables the RFP must require at closeout:

1. For surveillance: camera-by-camera spreadsheet with MAC address, IP, RTSP main-stream URL, RTSP sub-stream URL, ONVIF profile support, and credentials. PDF and Excel both.
2. For access control: reader-by-reader spreadsheet with OSDP address, controller binding, door schedule, lock type, REX device, position switch state. Plus a backup of the controller configuration.
3. For fire alarm: NFPA-compliant as-built drawings, point list, monitoring service test certificate, AHJ approval letter.
4. For AV: system block diagram, DSP configuration backup, control system code (Crestron, Extron, Q-SYS), room-by-room device inventory with firmware versions at install.
5. For BMS: point list with BACnet object IDs, point types, present values at commissioning, control logic documentation.

Common mistakes

Lumping all six work types under one "low voltage" line item. Bidders price six different trades as one number and the comparison is meaningless. Force separate scoping per work type even when one bidder is responding to all.

Specifying the manufacturer without specifying the credential. "Install Verkada cameras" doesn't mean the installer is a Verkada-credentialed partner. Manufacturer credentials are what preserve warranty and qualify the bidder for partner-tier pricing — verify them, don't assume.

Ignoring municipal licensing inside multi-state rollouts. Many cities require municipal low-voltage licensure on top of state. Chicago, Houston, and several Florida municipalities have stricter requirements than the state baseline. Bidders must disclose every level of licensing in scope.

Wiegand for new access control work. Wiegand is a legacy reader-to-controller protocol with known security weaknesses (no encryption, easily cloned). OSDP Secure Channel is the current standard. Specifying Wiegand in 2026 commits the buyer to a system that's already obsolete on day one.

Skipping the closeout documentation requirement. Cabling RFPs require Fluke test reports; low-voltage RFPs need the equivalent for each work type (above). Without explicit closeout deliverable requirements, half the bidders won't include documentation and the buyer ends up with a working system and no record of how anything is configured.

When a low-voltage RFP isn't the right tool

Single-trade work at small scale. If the entire scope is one trade and the project is under $25K, the RFP overhead costs more than the price spread. Issue an RFQ to three local contractors who hold the right credential, get fixed quotes after a site walk, decide in two weeks.

Emergency replacement on existing systems. Fire alarm panel failed inspection? Camera system went dark? RFP cycles don't work for restoration. Invoke the existing maintenance contract, or call your low-voltage partner direct for emergency dispatch.

Residential or small-commercial under-100-foot scope. Most of the structure in this post applies to commercial multi-trade work. Residential and very small commercial work has different licensing thresholds (often below the jurisdictional license requirement entirely) and doesn't need the same level of scope separation. Hire a local low-voltage electrician who runs Cat6 as part of a broader scope.

Straight answers

The questions facilities directors, GCs, and procurement leads ask before issuing a low-voltage RFP.

Next step

For multi-trade low-voltage work, download the IT RFP Template and adapt the scope sections to each of the six work types. For cabling-only scope, the 42-item cabling checklist covers Work Type 1 in detail. Both are free.

If your scope crosses multiple work types and you'd rather bring a deployment partner into pre-RFP scoping — useful when the work types interact (cameras need cabling, access control needs cabling and electrical) — email partners@srsnetworks.com with the site count, target geography, and work types in scope.

SRS Networks is a nationwide IT infrastructure deployment partner headquartered in Salinas, California, with offices in South San Francisco, Pasadena, Massachusetts, and Texas. Founded 1996. 500-plus deployments across 5,000-plus sites in 48 contiguous states. We cover Work Types 1, 2, and 3 directly with credentialed in-house W-2 leads; Work Types 4, 5, and 6 we either run with specialty subcontractors under our MSA or refer to the right specialty firm in your metro. See our channel partner program for the MSA and NDA flow.