In short
- Efficiency and demand-side programs are funded by a rider on customer bills. If you pay the rider, you are funding the program.
- Prescriptive incentives pay a fixed amount per unit for defined measures, with light paperwork.
- Custom incentives are calculated from a specific project's projected savings and require pre-approval.
- Applying after installation is the most common way a qualifying project loses its incentive.
- Load management measures are often funded separately from efficiency measures, and demand projects belong there.
There is a rider on your bill funding energy efficiency and demand-side management programs. It is approved by the state commission, it is collected from every customer in your class, and it pays for the incentives your utility offers.
A site that never applies is funding rebates for everybody else. That is not an argument about fairness; it is a reason to treat the application process as part of the project rather than as an afterthought.
The two structures
Prescriptive incentives pay a fixed amount for a defined measure: so much per motor of a given size, per drive, per unit of lighting. The measure is on a published list, the amount is known in advance, and the paperwork is short. Suited to standard equipment replacements.
Custom incentives are calculated from the projected savings of a specific project that does not fit the prescriptive list. They can be much larger, and they require engineering documentation, a savings calculation the program will accept, and — almost always — pre-approval before the equipment is purchased or installed.
There is a third category that matters here more than either: load management and demand response programs, funded to reduce peak rather than energy. A demand project frequently belongs in this stream rather than in the efficiency one, and applying to the wrong program is a standard reason for rejection: demand response programs.
Pre-approval is the whole game
The most common way a qualifying project fails to receive a custom incentive is that somebody installed the equipment first.
Programs require pre-approval because the incentive is intended to influence the decision. Once the equipment is bought, the program's own logic says the decision was made without it, and most program rules say so explicitly.
The practical implication is a sequencing one. The incentive application has to start when the project is still a proposal, which means the savings calculation has to exist at proposal stage — which it should anyway, for the capital case: building the business case for demand reduction.
Getting the savings calculation accepted
Custom programs assess a projected saving, and they apply their own methodology. Two things follow.
Use the program's method, not yours. Programs specify how baselines are established, what counts as a qualifying baseline, what weather or production normalization is required, and what documentation is acceptable. A calculation that is technically correct but does not follow the program's method will be sent back.
Expect post-installation verification. Larger custom incentives are frequently paid in stages, with a portion held until measured performance is demonstrated. The measurement approach should be agreed with the program before installation, not designed afterward: measurement and verification that finance will accept.
That second point has a useful side effect. A verification approach rigorous enough to release an incentive payment is generally rigorous enough to satisfy your own finance function, so the two exercises collapse into one.
What to check about any program
- Whether it is prescriptive, custom, or a load management program, and which one your measure belongs in.
- Whether pre-approval is required, and how long approval takes — it can be months, and it affects the project schedule.
- The funding cycle and whether the current year's budget is committed. Programs run out of money before they run out of applicants.
- Caps: per project, per customer, per year.
- Whether the incentive is paid on installation, on verified performance, or split.
- What documentation is required at each stage, and who produces it.
- Whether the payment reduces the basis for tax credits and depreciation, and whether it is taxable: the investment tax credit and depreciation on energy equipment.
The funding cycle point catches people. Program budgets are set annually and are frequently exhausted before the year ends, so an application submitted in the last quarter can be technically approved and unfunded until the next cycle.
Beyond the utility
State-level programs, tax credits and financing mechanisms exist alongside utility incentives and are administered separately. The Database of State Incentives for Renewables and Efficiency is the standard reference for finding what applies in a given state, and it is worth checking before assuming the utility program is the only route.
Where several sources apply, check the stacking rules. Some programs prohibit combining with another incentive for the same measure; others reduce their payment by whatever else was received. That has to be established before the model is built, not after two applications have been submitted.
Where it belongs in the model
An incentive is a cash inflow at a specific point in time, and it belongs in the cash flow at that point rather than as a percentage reduction to capital. A payment held until verified performance twelve months after commissioning is worth less than one paid at installation, and a model that treats them identically is overstating the return.
It should also be treated as contingent until approved. A project that only clears the hurdle rate with an incentive that has not yet been granted is a project with a condition attached, and saying so in the proposal is better than explaining it later.