Direct answer: Rebates for networked lighting controls are paid on the system, not on the fixtures, and the system has to be listed on a qualified products list with the required functions genuinely enabled and documented. Two things decide whether you get paid: the system must sit on the DLC Networked Lighting Controls Qualified Products List under a scope that matches your project, and you must hand the program a commissioning record showing the savings functions were configured as designed. Specifying an unlisted system, or listing a QPL system that was commissioned with half its functions switched off, is the standard way projects lose a controls incentive that was already priced into the payback.
Why controls carry more rebate value than fixtures per dollar
Fixture incentives reward efficiency you can measure on a nameplate. Controls incentives reward savings that depend on how the building actually runs, which is why programs pay for them differently — often as a bonus on top of the fixture rate rather than as a separate measure.
One representative utility structure pays a base rate per watt reduced for the LED fixture and a smaller bonus rate per controlled watt for a qualified networked controls system, with the two stackable on the same project. The fixture rate is the larger number, but the controls bonus is where the system decision is made, because it is only available if the controls are on an accepted list.
The trade-off is asymmetric. An unlisted fixture loses its efficiency bonus. An unlisted or incorrectly scoped controls system loses the controls bonus and usually invalidates the higher-tier calculation that was sold to the end user. Programs are also explicit that controls incentives are not combinable with every other measure: some utilities refuse to stack sensor rebates with a networked controls incentive, and a few exclude exterior NLC projects entirely at this time.
What DLC NLC V5.2 changed — and what it left alone
The DLC finalized its Networked Lighting Controls technical requirements V5.2 on June 24, 2026. The version took effect August 3, 2026, with applications accepted from August 17, 2026. The previous version, NLC V5.1, stopped accepting applications on April 15, 2026 — a detail worth knowing if you are quoting from an older specification template.
Four changes are relevant to a project spec:
- Recognition of lighting-to-HVAC integration, where occupancy data from the lighting system drives smart thermostats. The DLC cites additional HVAC savings in the range of 8% to 21% where that integration is implemented.
- Standardized reporting of energy-saving configuration settings, aligned with the ANSI/NEMA C137.9 standard, so a program can verify the system was programmed as designed.
- A clearer, more comparable QPL format, intended to make system capability comparison faster for specifiers.
- Eligibility for horticultural control systems that meet the DLC requirements.
Cybersecurity requirements were left unchanged. The DLC states the same stringent requirements continue to apply, so any expectation of a lighter security review in V5.2 is unfounded.
Scale matters here: the DLC says the NLC QPL is used by more than 100 utilities to determine incentive eligibility, and the list carries roughly 96 systems from more than 60 manufacturers. That is a large enough pool to specify competitively and small enough that you should verify the specific model, not the brand.
System scope: the first thing to match to your project
NLC qualification happens at the system level, and each listed system qualifies for one or more scopes based on its capabilities. Selecting a system that is listed for the wrong scope is a rejection that is easy to avoid.
| Scope family | Scopes | What goes wrong when it is mismatched |
|---|---|---|
| Indoor | Room or Zone, Whole Building, Portfolio/Enterprise, Structured Parking | A room-level system applied to a whole-building specification cannot deliver the scheduling and reporting the program expects |
| Outdoor | Structured Parking, Area/Building Outdoor/Parking, Streetlight, Roadway | Roadway and streetlight scopes have different expectations again, and some programs exclude exterior NLC from incentives entirely |
One structural point that trips up buyers: the DLC NLC requirements cover the control system, while the DLC solid-state lighting requirements cover luminaires and luminaire-integral controls. The two are complementary and non-overlapping. A fixture with controls built into it is qualified under the SSL requirements, not under NLC — and if the utility’s controls measure requires an NLC-listed system, that integral-control fixture does not satisfy it on its own. DC and PoE networked control systems can also be qualified under the DLC’s testing and reporting requirements for DC and PoE products.
The capabilities your system must actually have enabled
Every program publishes its own list, but the functional core converges. Treat the table below as the minimum set to specify, then check the local program document for additions.
| Capability | How a program verifies it | Common failure |
|---|---|---|
| Occupancy sensing | Commissioning report and configuration export | Sensors installed but left in manual-on mode |
| Daylight harvesting | Sensor locations plus configured setpoints | Photocells installed on the wrong plane so the loop never closes |
| High-end trim / task tuning | Documented trim level; some programs set a floor such as 10% minimum | Trim never commissioned, so the wattage claimed is not the wattage delivered |
| Continuous dimming | Driver and controller compatibility, dimming curves | Stepped or non-dimming drivers substituted late in procurement |
| Zoning | Zoning plan against the floor plan | Zones created physically but not carried into the control schedule |
| Networked communication | Network architecture diagram | Gateway specified but omitted from the purchase order |
| Scheduling | Schedule configuration with override behaviour | No override for safety or after-hours work, which can void the measure |
| Energy monitoring | Reporting method and, increasingly, measured data | Reported via calculation when the program requires direct measurement |
Where a program operates two incentive tiers, the split typically works like this: the lower tier accepts a system with a minimum number of listed capabilities — three is a common threshold — while the higher tier requires the system to be listed on the DLC NLC QPL. Some programs also let you claim trimmed wattage as the post-upgrade load, but only if the trim is permanent and you supply screenshots or power measurements. That single provision can move a project several percentage points of savings, so it is worth asking about before the design is frozen.
The documentation package that decides whether you get paid
Rebate applications fail on paperwork far more often than on equipment. The controls-related documents are the ones most often missing.
| Document | Who produces it | Typical failure mode |
|---|---|---|
| Pre-approval letter and scope of work | Utility and applicant | Equipment purchased before pre-approval, which disqualifies the invoice date |
| Time-stamped QPL listing proof | Applicant | Product delisted between quotation and purchase with no evidence of listing at pre-approval |
| Control narrative and control specification | Designer | Missing entirely, leaving the commissioning agent nothing to verify against |
| Controls commissioning report | Installer or commissioning agent | Signed without per-function verification, or listing functions that are not enabled |
| Dated invoices with full model numbers | Contractor | Integral controls not identified in the model string on the invoice |
| Reported post-installation energy data | Owner or controls platform | Reporting period too short — some programs require an initial 30 days of reported savings |
| Scaled floor plan and reflected ceiling plan | Designer | Withheld on request, which stalls review |
The commissioning report is the document that converts a hardware purchase into an eligible project. Where a program requires measured post-installation data, a system that cannot export energy and configuration data by itself is a liability regardless of how well it controls light.
Design decisions that quietly cost you the incentive
Four specification habits recur in rejected applications.
- Quoting a “DLC listed” fixture and assuming that covers the controls. Luminaires and control systems are listed separately, and a rebate program asking for an NLC-listed system will not accept a fixture listing as evidence.
- Freezing the specification before checking the local program document. Prescriptive requirements differ: some utilities demand a specific function list for interior systems and a different list for exterior, including bi-level dimming and dusk-to-dawn photocell control.
- Letting the integrator commission to the sequence they prefer rather than the sequence on the plan. Standardized configuration reporting under the new version exists precisely because this gap was unverifiable before.
- Ignoring the delisting calendar. Products that are not re-certified to the current requirement version are removed from the list, and the DLC publishes application cut-off dates for each retired version. Long-lead projects should carry a vetted alternate model on the same list.
Two practical habits pay for themselves. First, screenshot the QPL entry for every model at the pre-approval stage and file it with the application, because eligibility is judged on the state of the list at that point. Second, build a rebate bill of materials with a primary and an alternate model so a delisting does not stop procurement.
For the wider context on how incentives interact with specification choices, see our guide to modern office lighting solutions and the hidden costs of smart lighting controls in commercial projects. If your controls strategy still depends on which protocol the fixtures speak, why your project specification might already be dated covers that decision.
Frequently asked questions
Can I claim a controls rebate with integral sensors instead of a networked system?
Sometimes, but not as a networked controls measure. Integral luminaire controls are qualified under the DLC’s solid-state lighting requirements, while NLC rebates are tied to systems listed on the NLC QPL. A fixture with built-in sensing may qualify for a sensor or multi-level controls rebate, which is usually paid at a lower rate than a Tier 2 networked controls incentive.
Does the rebate depend on the fixtures I buy?
Partly. Many programs require the retrofit luminaires to be listed on the applicable DLC or ENERGY STAR list as well, and the controls bonus is often only claimable alongside a qualifying fixture upgrade. Networked lighting control systems rebated as a stand-alone measure are the exception rather than the rule.
How much of the total project cost do controls rebates cover?
It varies by program, by building type and by whether the project is prescriptive or custom. Rates are commonly expressed as a bonus per controlled watt or per square foot of controlled area, and the DLC says the QPL underpins incentive eligibility across more than 100 utility programs. Always price the specific local program rather than a national average.
If the system is on the QPL, is the rebate guaranteed?
No. Listing is necessary but not sufficient. The system must also be installed within the listed scope, commissioned with the required functions enabled, and supported by a complete documentation package including invoices, commissioning records and, where required, measured post-installation energy data.
What happens if the specified system is delisted mid-project?
The usual protection is evidence of listing at pre-approval, plus an alternate model that is also listed. Programs publish application cut-off dates when a requirement version is retired, so a long-lead project should be checked against that calendar before the order is placed.
