February 20, 2026
Demand response (DR) used to be a niche energy-procurement tool—something big factories did through an aggregator when the grid got tight. In 2025 and heading into 2026, that’s changed. Across the U.S., utilities and ISOs/RTOs are expanding DR and load‑management programs that pay large electricity users to reduce consumption on cue, sometimes with just minutes of notice.
For indoor cultivation, where lighting, HVAC, and dehumidification can represent a major portion of operating costs, DR can look like “found money.” But participation increasingly comes with audit‑style verification: automated controls, pre‑defined control sequences, documented test events, and measurement & verification (M&V) plans that tie directly to settlement data.
This post explains what’s changing, how DR works in key U.S. power markets (CAISO, ERCOT, ISO‑NE), what utility/aggregator auditors look for, and the load‑shed strategies that typically pass audits without risking crop quality.
Informational only: This article is for general education on energy programs and operational compliance. It is not legal, engineering, or financial advice.
Many new and updated programs are built around the idea that DR should be dispatchable and provable—similar to how generation resources are treated.
In practice, that means auditors and program implementers increasingly expect:
If you can’t produce those artifacts quickly during a program check—or if your logs don’t match settlement intervals—you risk failed tests, payment reductions, or incentive clawbacks.
Indoor cultivation sites can participate through two broad paths:
Utilities run programs directly or through program administrators. These often include:
These programs may be paired with energy-efficiency rebates, and they may be the most practical “first DR” step.
Aggregators can enroll customer loads into ISO/RTO markets. Requirements tend to be more rigorous on telemetry, dispatch, baselines, and registration.
The key operational point: even if you “only” sign with a utility program, your utility or aggregator may still structure expectations around wholesale market rules and audit rigor.
The U.S. has many DR frameworks, but three markets show the direction of travel.
CAISO supports multiple DR participation models, including Proxy Demand Resource (PDR) and Reliability Demand Response Resource (RDRR), which allow aggregated loads to participate in CAISO markets through demand response providers.
CAISO’s DR information hub and participation references are here:
From an operator perspective, California is also notable because OpenADR is deeply embedded into program ecosystems and building-control expectations.
ERCOT’s DR landscape includes programs such as Emergency Response Service (ERS) and Load Resource participation (providing ancillary services and/or demand response as a registered Load Resource).
ERCOT’s Load Resource participation overview (including registration and telemetry setup expectations) is here:
The practical takeaway for cultivation operators in ERCOT territory: you should assume telemetry, qualification testing, and strict timelines are part of the deal if you pursue deeper market participation.
ISO‑NE provides a clear framework for active demand response where dispatch instructions and near‑real‑time reporting matter.
A useful ISO‑NE explainer (definitions for demand response assets and resources) is here:
If you operate in New England, expect program designs to focus on baseline methodology, dispatch response, and interval data quality.
Many DR programs now want a “machine-to-machine” way to deliver event signals and record responses. That’s why you’ll hear about:
An OpenADR reference many implementers use is the OpenADR program implementation guide:
California’s building energy code environment is particularly explicit about demand-responsive lighting controls. The California Energy Commission (CEC) maintains Demand Responsive Lighting Control certification information and declarations, including OpenADR 2.0 virtual end node capability references:
Even if your facility is not undergoing a permitted lighting alteration today, this ecosystem influences what utilities, implementers, and auditors expect a “serious” DR lighting control system to look like.
Utilities often cross-reference DesignLights Consortium (DLC) guidance because DLC-qualified products are commonly used to determine rebate eligibility.
DLC’s Networked Lighting Controls (NLC) technical requirements are here:
Why it matters in DR audits:
All of that makes your “we reduced load by 120 kW for 2 hours” claim more defensible.
Think of a DR audit as a hybrid of commissioning, controls verification, and settlement reconciliation.
Auditors commonly request:
Failure mode: the enrolled meter doesn’t match the actual load being controlled, or the committed kW is unrealistic given operating schedules.
Expect to show:
Failure mode: a control sequence exists “in someone’s head,” not in a controlled document; or execution depends on a person being present.
Auditors look for:
Failure mode: clocks aren’t synced, event duration differs by system, or logs are missing when the internet drops.
Your M&V plan should specify:
Failure mode: baseline disputes because operations changed (new rooms came online, lighting schedule changed) but the program wasn’t notified.
Many programs require commissioning tests, and some require periodic tests.
Failure mode: the site can’t replicate the shed reliably because the control system was modified, zones were reconfigured, or firmware updates changed behavior.
The best DR strategies are repeatable, staged, and measurable. They also include “guardrails” that prevent harm to product quality.
Below are common approaches that auditors tend to accept because they are controllable and easy to verify.
For indoor cultivation, lighting is often the biggest controllable load.
Audit-friendly strategies include:
Guardrails to document in your SOP:
What auditors like: a networked lighting control system where they can see commanded dim level changes and timestamps.
HVAC shed strategies must be careful: comfort metrics in cultivation are crop metrics.
Common DR tactics:
Guardrails:
What auditors like: BAS trend logs for setpoints, valve positions, compressor stages, and room sensors.
Dehumidification loads can be significant, especially in flower rooms.
Audit-friendly shed approaches:
Guardrails:
What auditors like: discrete enable/disable logs per unit and room RH trends showing you stayed within defined bounds.
Depending on facility design, you may have:
These can be good “buffer” loads because they often have less direct plant impact.
Guardrails: document what is truly non-critical and confirm it’s on the enrolled meter.
A strong DR documentation pack makes audits faster and reduces disputes.
Keep a version-controlled set of:
Use language like:
(Adjust to match your program contract requirements.)
DR can materially offset retrofit costs—especially when programs pay for enablement (controls, gateways, commissioning) and then also pay for performance.
But DR economics are only real if the site can reliably deliver.
Plan for these common risk areas:
When programs include clawback provisions, the best defense is a conservative commitment and robust documentation.
Most facilities can reach “audit-ready DR” on a fast track if they treat it like a commissioning project.
Demand response is becoming part of modern cannabis compliance because energy controls, documentation, and audit readiness now affect profitability and operational continuity. Use https://cannabisregulations.ai to track compliance requirements that intersect with facility operations, document control procedures, and stay ahead of evolving regulations, incentives, and enforcement trends impacting the industry.
