What Most Lighting RFPs Get Wrong — and How Smart Cities Are Fixing It

Most lighting RFPs are written with good intentions—and outdated assumptions.

They focus heavily on fixture specs, unit pricing, and compliance checklists. Lumens. Wattage. Pole spacing. Delivery timelines. All important—but incomplete.

As a result, many cities and commercial property owners end up modernizing lighting without actually modernizing outcomes.

The good news? A growing number of public agencies and commercial buyers are changing how they write lighting RFPs—and getting dramatically better results dramatically as a result.

Mistake #1: Treating Lighting as a Commodity Instead of Infrastructure

Traditional RFPs treat lighting as interchangeable hardware. If it meets minimum specs and costs less, it wins.

Why this fails today:
Outdoor lighting now directly affects:

  • Public safety
  • Accident rates
  • Crime deterrence
  • Energy budgets
  • Insurance exposure
  • Operational visibility

When lighting is treated as a commodity, buyers miss opportunities to solve these problems together.

What smarter RFPs do instead:
They frame lighting as infrastructure—a long-lived system that supports safety, operations, and financial outcomes, not just illumination.

Mistake #2: Over-Focusing on Technical Specs and Under-Focusing on Outcomes

Specs matter—but specs don’t tell you whether a solution will actually work in the real world.

Many RFPs ask:

  • How many lumens?
  • What wattage?
  • What housing material?

Few ask:

  • How does this improve visibility of incidents where they occur?
  • How does this reduce operating effort in the first year?
  • How does this help us respond faster when something goes wrong?

What smarter RFPs do instead:
They start with outcome-based objectives, such as:

  • Reducing energy consumption
  • Improving nighttime safety
  • Increasing situational awareness
  • Lowering maintenance burden
  • Supporting risk and liability reduction

This allows vendors to propose integrated solutions instead of narrowly optimized fixtures.

Mistake #3: Separating Lighting and Security Into Different Silos

One of the most common—and costly—mistakes is issuing separate RFPs for lighting and security.

This leads to:

  • Duplicate poles and infrastructure
  • Gaps in coverage
  • Higher installation and maintenance costs
  • Fragmented operations between teams

Why this matters now:
Lighting poles are already positioned in the exact places where visibility and security matter most: roadways, parking lots, walkways, perimeters, and ports.

Treating lighting and security as separate systems wastes that advantage.

What smarter RFPs do instead:
They require integrated lighting and security architectures, in which cameras and sensors can be embedded in lighting infrastructure and managed through a unified platform.

Mistake #4: Evaluating Cost Without Evaluating Total Cost of Ownership

The lowest bid does not equal the lowest cost.

Traditional RFPs often reward:

  • The cheapest fixture
  • The lowest installation price

They rarely evaluate:

  • Energy savings in the first two years
  • Reduced maintenance and inspections
  • Operational efficiencies from remote monitoring
  • Avoided incidents or claims

What smarter RFPs do instead:
They ask for near-term total cost of ownership, typically focused on the first 24 months—a realistic window for modern solutions and newer vendors.

This keeps evaluations grounded while still rewarding value.

Mistake #5: Ignoring Risk, Liability, and Insurance Until After Deployment

Lighting decisions quietly influence insurance outcomes—but most RFPs never mention risk.

Poor lighting contributes to:

  • Slip-and-fall claims
  • Vehicle accidents
  • Property damage
  • Disputed incidents with no evidence

Once incidents happen, it’s too late to fix visibility or capture data.

What smarter RFPs do instead:
They explicitly evaluate how lighting solutions:

  • Improve visibility
  • Detect activity
  • Capture evidence
  • Support risk management discussions

This reframes lighting as a preventive tool rather than just a utility expense.

Mistake #6: Forgetting Data Governance, Privacy, and Cybersecurity

As lighting becomes smarter, it also becomes digital.

Surprisingly, many RFPs fail to address:

  • Who owns the data?
  • How access is controlled
  • How long is data retained
  • How systems are secured

Why this matters:
Cities and commercial operators are accountable for privacy, compliance, and cybersecurity—whether they ask about it or not.

What smarter RFPs do instead:
They include clear expectations for data governance, privacy controls, and secure system access from the start.

Mistake #7: Designing RFPs That Can’t Scale

Many organizations want to pilot smart lighting—but end up writing RFPs that lock them into small, isolated deployments.

What goes wrong:

  • Systems that don’t scale
  • Management tools that don’t unify sites
  • Inconsistent operations across locations

What smarter RFPs do instead:
They require solutions that support phased deployments, pilots, and expansion—without replacing earlier investments.

What Forward-Thinking Buyers Are Doing Differently

The most effective lighting RFPs today:

  • Focus on outcomes, not just fixtures
  • Integrate lighting and security
  • Evaluate near-term operational value
  • Address risk and insurance implications
  • Include data governance and cybersecurity
  • Allow room for innovation and scale

The result is not just better lighting—but safer spaces, lower operating costs, and smarter infrastructure decisions.

Next step:
If you’re preparing a lighting RFP for public spaces, parking lots, commercial properties, or ports, start with the right framework. 

Our Smart Lighting & Security RFP Guide is designed to help experienced buyers ask the questions that actually matter.

What Most Lighting RFPs Get Wrong — and What to Do Instead

Common RFP Mistake Why It Fails What Smart Buyers Do Instead
Treating lighting as a commodity Misses safety, risk, and operational value Treat lighting as critical infrastructure
Focusing only on specs (lumens, watts) Specs don’t guarantee outcomes Define outcome-based objectives
Separating lighting and security Creates blind spots and higher costs Require integrated lighting + security
Choosing the lowest upfront price Increases long-term operating costs Evaluate the 24-month total cost of ownership
Ignoring risk and insurance Misses liability reduction opportunities Score safety and risk mitigation explicitly
Overlooking data & cybersecurity Creates compliance and privacy risks Require data governance and security controls
Designing RFPs that don’t scale Locks buyers into pilots Require phased, scalable deployments

(FAQ) Frequently Asked Questions About Smart Lighting RFPs

What is the biggest mistake in lighting RFPs today?
The biggest mistake is treating lighting as a commodity purchase rather than as infrastructure that affects safety, energy costs, operations, and risk management.

Why are outcome-based lighting RFPs better?
Outcome-based RFPs allow buyers to evaluate solutions based on real-world improvements, such as energy savings, safety outcomes, and operational efficiency, rather than just fixture specifications.

Should lighting and security be included in the same RFP?
Yes. Integrating lighting and security reduces infrastructure duplication, improves coverage, and lowers the total cost of ownership compared to separate systems.

How should cities evaluate smart lighting costs?
Cities should evaluate the near-term total cost of ownership, typically over the first 24 months, including energy savings, maintenance reductions, and operational efficiencies.

Why does smart lighting affect insurance and liability?
Improved visibility and integrated incident documentation reduce accidents, support claims validation, and help lower liability exposure for public and commercial properties.

What data and cybersecurity issues should lighting RFPs address?
RFPs should address data ownership, access controls, retention policies, and cybersecurity protections for video and operational data.

Can smart lighting systems scale over time?
Modern smart lighting systems should support pilots and phased deployments while maintaining centralized management across multiple sites.

Next step:
If you’re preparing a lighting RFP for public spaces, parking lots, commercial properties, or ports, start with the right framework. 

Our Smart Lighting & Security RFP Guide is designed to help experienced buyers ask the questions that actually matter.