Commercial Lighting Control Systems: Types, Retrofit Options and Quoting Checklist

Commercial lighting control systems determine when lights operate, how much light they provide and which fixtures respond together. A system may serve one room or coordinate lighting across an entire building.
For distributors and ESCOs quoting retrofits, the challenge is matching the controls to the installed equipment, the way each space is used and the scope the customer expects. A sensor count alone does not establish a complete project price.
This guide explains the main system types, compares wired and wireless options, and provides a practical checklist for turning a site assessment into a controls quote with clear costs and savings assumptions.
How Commercial Lighting Control Systems Work
A commercial lighting control system combines inputs, control logic and devices that switch or dim lighting. Inputs may come from a wall control, occupancy sensor, daylight sensor, schedule or another building system.
Separate three decisions when evaluating a project:
Decision | What it describes | Examples |
System architecture | How broadly devices coordinate | Standalone, room-based, building-wide networked |
Communication method | How devices exchange control signals | Wired, wireless or hybrid |
Control strategy | What causes lighting to change | Occupancy, scheduling, daylight response, task tuning |
A wireless product is not automatically a building-wide control system. Likewise, specifying a networked system does not establish which energy-saving strategies will be configured.

Document the required behaviour first, then identify the equipment and architecture that can deliver it.
Main Types of Commercial Lighting Control Systems
Standalone Controls
Standalone controls operate a fixture or local lighting group without wider coordination. Examples include a wall-switch sensor or a photocell controlling an exterior lighting circuit.
They can suit a defined local problem, such as lights left on in a storage room. Include coverage, switching capacity and setup in the assessment rather than assuming one sensor will suit every room.
Room-Based Controls
Room-based systems coordinate devices within a space. A meeting room might combine wall controls, occupancy sensing and separate daylight-responsive lighting zones.
Identify how the room should behave during normal use, presentations, vacancy and overrides. The required functions determine the quote more accurately than the room’s floor area alone.
The GSA’s lighting and controls guidance distinguishes standalone, room-based and centrally networked architectures.
Networked Lighting Controls
Networked lighting controls connect devices so that settings and operation can be coordinated across a wider installation. Depending on the system and selected components, capabilities may include centralized scheduling, grouping, reporting and building-system integration.
The DesignLights Consortium’s system definitions describe networked controls as a combination of sensors, network interfaces and controllers that change luminaire operation.
Ask which capabilities are included in the proposed configuration. A platform’s marketing page may describe options that require additional hardware, software or services.
Luminaire-Level Lighting Controls
Luminaire-level lighting controls, or LLLC, integrate control capabilities at individual fixtures. The DLC’s definition includes networked occupancy and ambient-light sensing integrated into each luminaire during manufacture.
This can support detailed control at the fixture level. Confirm the actual system configuration and grouping capabilities before building the scope. A fixture with an integrated motion sensor should not automatically be described as a qualified LLLC system.
Control Strategies to Consider in a Retrofit
Choose strategies by space and operating conditions. An office perimeter, interior meeting room and warehouse aisle may need different approaches within the same project.
Strategy | What it does | What the estimator should establish |
Occupancy sensing | Automatically activates lighting and switches it off or reduces output when the space is vacant | Detection coverage, timeout, occupied and vacant settings |
Vacancy sensing | Uses manual activation with automatic shutoff after vacancy | Accessible wall controls and the intended user workflow |
Scheduling | Changes lighting operation at specified times | Working hours, holidays and after-hours overrides |
Daylight harvesting | Adjusts electric lighting in response to available daylight | Daylight zones, dimming compatibility and sensor setup |
High-end trim or task tuning | Limits maximum light output to an appropriate level | Required lighting levels and the proposed maximum setting |
Demand response | Adjusts lighting in response to a demand-response event | Customer participation, system capability and acceptable operation |
The DLC’s guide to lighting control strategies explains occupancy, vacancy, scheduling, daylight harvesting and task tuning. For quoting, connect each selected strategy to a specific space and documented requirement.
Define the Intended Behaviour
Write a short sequence of operations for each distinct space type. This describes how the lighting should respond under different conditions.
For example: “Manual-on lighting in enclosed offices, automatic shutoff after the agreed vacancy timeout, and separately commissioned daylight-responsive control for the window-side fixtures.”
The designer or responsible project professional should establish settings that satisfy the applicable requirements and user needs. Your estimate should include the work required to configure and verify them.
Keep emergency and egress operation identified separately. A general controls recommendation should not assume that every fixture can be switched off when a sensor detects vacancy.
Wired vs Wireless Lighting Controls
Wired controls communicate through physical connections. Wireless lighting controls exchange signals by radio, although fixtures and some control devices still need wired power. Hybrid installations combine both approaches.
PNNL’s lighting controls guide explains why wireless communication can reduce control-wiring work in retrofits while device power, communication range and system limits still need review.
When Wired Controls May Fit
Evaluate wired options where suitable control wiring already exists, access is straightforward or the specified architecture calls for wired communication.
Price the actual route and installation conditions. Cable, conduit, ceiling access, occupied-space restrictions and making good can materially change the scope.
When Wireless Controls May Fit
Evaluate wireless options where installing new control wiring would be disruptive or difficult. Confirm device power, gateway requirements, communication coverage and manufacturer limits.
Include programming, grouping and testing. Reducing control-wiring work does not remove those tasks from the project.
Compare the Same Scope
Compare wired and wireless proposals against the same sequence of operations and handover requirements. A room-level switching solution and a centrally managed dimming system are not equivalent bids simply because both use sensors.
Manufacturers offer different levels of functionality within their own ranges. For example, Lutron’s commercial systems comparison distinguishes Vive and Athena by components, startup, management and integration capabilities.
Check LED and Driver Compatibility Before Pricing
An existing LED installation can still be a candidate for controls, but the proposed control must work with the actual driver, fixture and circuit.
Verify the Dimming Interface
Record the driver model and supported control method. A description saying “dimmable LED” is not enough to establish compatibility with a particular dimmer or control system.
For example, Leviton’s 0–10V dimmer guidance specifies compatible 0–10V drivers and ballasts for the products discussed. It does not describe a universal dimmer for all LED loads.
Confirm compatibility using the selected manufacturer’s documentation, including the dimming range, shutoff behaviour, load limits and any required interfaces.
Decide What Can Be Retained
Separate fixtures that can accept the proposed controls from those requiring driver replacement, a retrofit kit or fixture replacement.
Flag uncertain equipment for investigation before committing to a fixed scope. Where practical, test a representative fixture and control combination before ordering the full package.
A controls-only option should identify exactly what is retained, what is added and what remains subject to verification.
Retrofit Audit Checklist for Controls Quotes
Capture the following information during the lighting audit. Use consistent area and space names so the estimator can match field records to pricing and proposal options.
Audit item | Record on site | Why it affects the quote |
Existing lighting | Fixture counts, system watts, model details and condition | Establishes the baseline and retained equipment |
Drivers and dimming | Driver labels, supported interface and available control wiring | Determines compatibility and replacement scope |
Existing controls | Switches, sensors, timers, dimmers, panels and known settings | Identifies what already works and what needs changing |
Space use | Actual operating hours, intermittent occupancy and after-hours use | Supports strategy selection and savings assumptions |
Daylight conditions | Windows, skylights, relevant zones and shading conditions | Establishes where daylight control needs assessment |
Circuits and zones | Available drawings, circuit information and required control groups | Helps define switching, dimming and installation work |
Access conditions | Ceiling height, ceiling type, obstructions and working restrictions | Supports labour, lift and making-good allowances |
Emergency lighting | Identified emergency and egress equipment and interfaces | Keeps required operation visible in the scope |
Building integration | Requested BAS functions, network arrangements and responsible contacts | Identifies interfaces, coordination and startup work |
Owner requirements | Local overrides, reporting, training and future changes | Defines commissioning and handover deliverables |
Photograph the Information That Resolves Uncertainty
Photograph fixture and driver labels, existing control devices, relevant panels and access conditions. Associate each image with its space or fixture group.
If a driver label cannot be read or a circuit cannot be confirmed during the visit, record that limitation. Give the follow-up investigation an owner before final pricing.
Build a Complete Controls Retrofit Quote
Avoid pricing only the visible sensors. Build the scope around the selected configuration and the work needed to make it operate as intended.
Separate the Cost Categories

Include applicable costs for:
Sensors, wall controls, controllers, relays and gateways.
Driver changes, retrofit kits or fixture replacements.
Wiring, conduit, electrical installation and access equipment.
Programming, startup, testing and commissioning.
Integration hardware and coordination with other trades.
Software licences or subscriptions, where applicable.
Documentation, operator training and agreed follow-up.
Identify recurring fees separately from the installation price. Confirm whether they are required for everyday operation, optional reporting or another service.
Define Commissioning and Handover
State who will configure the system and what must be demonstrated before handover. Include agreed checks for sensor coverage, timeouts, daylight response, schedules, overrides and applicable emergency interfaces.
Deliver the zone map, final settings, relevant product documentation and instructions for routine adjustments. Agree who will retain administrative access and handle future changes.
Present Options With Clear Differences
Where appropriate, quote separate options such as:
Correcting schedules and recommissioning existing controls.
Adding targeted controls to compatible fixtures.
Installing a networked package with defined management capabilities.
Show what changes in scope, cost and expected performance. Do not force the most complex system into every project, or omit controls required by the applicable code.
Calculate Controls Savings Without Double-Counting
Establish what the existing controls already do before estimating additional savings. A space with effective automatic shutoff should not be modelled as if its lighting runs uncontrolled throughout all building operating hours.
For a combined LED and controls project, show the LED-only case and the additional controls effect separately. GSA’s guidance explains that energy-saving measures are not simply additive.
Worked Example: LED Upgrade Plus Controls
This is an illustrative calculation, not measured project performance. The assumed controls reduction is not a default savings recommendation.
Input | Illustrative value |
Existing fixtures | 100 fixtures at 80W each |
Proposed LED fixtures | 100 fixtures at 40W each |
Existing annual full-output operation | 3,000 hours |
Assumed additional controls reduction | 25% of the LED-only annual energy |
Assumed avoided electricity cost | $0.15/kWh |
Existing lighting:100 × 80W × 3,000 hours ÷ 1,000 = 24,000 kWh/year.
LED-only case:100 × 40W × 3,000 hours ÷ 1,000 = 12,000 kWh/year.
LED plus controls:12,000 × (1 − 0.25) = 9,000 kWh/year.
The LED upgrade saves 12,000 kWh/year. Controls add 3,000 kWh/year of savings. Together, they save 15,000 kWh/year, or 62.5% of the original lighting energy.
Adding 50% LED savings and 25% controls savings would incorrectly produce 75%. The controls percentage in this example applies to the smaller LED-only energy use.
At the assumed electricity rate, the LED savings equal $1,800/year and the additional controls savings equal $450/year. Use that additional $450 when assessing the incremental financial return of the controls option.

Document the Basis for Every Savings Assumption
For a real project, support controls assumptions with the existing settings, observed use, logging, an accepted calculation method or other relevant evidence.
If multiple strategies overlap, evaluate their combined operation. Do not apply separate occupancy, scheduling and daylight percentages without checking what each changes in the same space.
Dimming output is not necessarily proportional to electrical power. Use suitable fixture or driver power information where the calculation depends on a dimmed operating level. PNNL’s research on 0–10V controls documents differences in light output and input power across tested drivers and luminaires.
Keep demand-charge savings separate and assess them against the customer’s tariff and relevant peak conditions. A reduction in annual kWh does not automatically establish the same percentage reduction in billed demand. The DOE’s utility-rate guide explains the different billing components to consider.
Check Code and Rebate Requirements Before Finalizing the Scope
Record the applicable jurisdiction, project type, adopted code edition and any required controls testing. Retrofit requirements depend on the actual work being performed.
For California work, the California Energy Commission states that permit applications submitted on or after January 1, 2026 fall under the 2025 Energy Code. Review the relevant requirements for the project rather than reusing an older specification.
Rebate eligibility is a separate check. Verify the exact system, required configuration, installation scope, application timing and whether pre-approval is required. The DLC Qualified Products Lists can help check listed products and control systems, but qualification alone does not guarantee a utility incentive.
Label proposal rebates as estimated, pending approval or confirmed, as appropriate. LumaQuote’s commercial lighting rebate guides provide starting points for checking the relevant program.
Keep Controls Connected to the Audit and Proposal

A controls quote is easier to review when the existing conditions, proposed strategies, assumptions and costs remain tied to the same spaces and fixture groups.
LumaQuote helps organize existing and proposed controls alongside the lighting retrofit workflow. Its Pro plans include controls analysis, installation costing and proposal output. The estimator still needs to verify compatibility, technical scope and project-specific assumptions.
For a workflow example, compare one familiar project with its base LED scope and a separately defined controls option. Make the additional costs and savings visible so the customer can evaluate the choice.
Explore LumaQuote’s lighting retrofit software, review available plans, or see how to build a lighting retrofit proposal.
FAQ: Commercial Lighting Control Systems
What are commercial lighting control systems?
They are combinations of controls and devices that manage when commercial lighting operates, its output and which fixtures respond together. Systems range from local sensors and wall controls to coordinated building-wide networks.
What is the difference between occupancy and vacancy sensing?
Occupancy mode generally provides automatic activation and automatic shutoff or reduction after vacancy. Vacancy mode requires manual activation and provides automatic shutoff. Confirm the selected equipment’s behaviour and applicable project requirements.
Are wireless lighting controls always networked?
No. Wireless describes communication, while networked describes how devices coordinate. A wireless local control arrangement and a building-wide managed system can have very different capabilities.
Can controls be added to existing LED fixtures?
Sometimes. Confirm the driver, dimming interface, circuit and control compatibility. Some fixtures can be retained; others need a driver change, retrofit kit or replacement to support the proposed system.
What determines the cost of commercial lighting controls?
The scope includes the selected hardware, retained or replaced equipment, installation access, wiring, programming, commissioning, integration and any applicable recurring services. A sensor price alone does not establish the installed project cost.
How much energy will lighting controls save?
There is no single percentage suitable for every project. Savings depend on existing controls, operating patterns, daylight, configured strategies and equipment response. State and support the assumptions used for each quoted space.
Does a DLC-listed control system guarantee a rebate?
No. The utility or program determines eligibility. Verify the specific system configuration, project scope, deadlines and approval requirements before including an incentive in the financial model.


