1. Introduction

Aggregated demand response (ADR) is a mechanism under which an aggregator combines the electricity-consumption flexibility of numerous customers—such as households, commercial buildings, industrial facilities, electric-vehicle owners, batteries, or smart appliances—and offers the combined reduction or shift in electricity demand into an electricity market.

The legal difficulty is that the market sees one aggregated resource, while the physical response is produced by many independent customers and devices. If the aggregation fails to deliver the promised demand reduction, delivers it late, responds by the wrong amount, or causes a distribution-system problem, an important question arises:

Who should bear the resulting liability—the individual customer, aggregator, distribution utility, market operator, or some combination of them?

Modern regulatory systems increasingly place primary market-facing responsibility on the aggregator while allocating underlying contractual, technical and operational risks through contracts and market rules.

The issue is particularly important because demand response is no longer merely a voluntary utility programme. In the United States, the Supreme Court confirmed that wholesale demand-response compensation falls within FERC's authority where it directly affects wholesale rates. Justia Law In the European Union, legislation expressly requires participants engaged in aggregation to be financially responsible for imbalances they cause. EUR-Lex India is also developing regulatory frameworks for demand flexibility and aggregation, including recent Maharashtra and Delhi initiatives. Maharashtra E.R.C.

2. Meaning of Aggregated Demand Response

Traditional demand response involves a customer voluntarily reducing consumption in response to:

• a price signal;
• a utility instruction;
• a system emergency;
• a market signal; or
• a contractual demand-response event.

In an aggregated model, an aggregator combines numerous small responses.

For example:

1,000 commercial customers each agree to reduce consumption by an average of 10 kW during a peak event.

The aggregator may therefore offer approximately:

1,000 × 10 kW = 10 MW

of demand-response capacity to the market.

The market operator does not ordinarily want to administer 1,000 separate transactions. Instead, it interacts with the aggregator as the market-facing participant.

FERC's Order No. 2222 framework similarly recognizes that many small distributed energy resources may be combined into an aggregation sufficient to participate in wholesale markets. Federal Energy Regulatory Commission

3. The Central Liability Problem

Aggregated demand response produces a multi-layer liability structure.

There may be at least five relevant actors:

1. Individual participating customer
2. Demand-response aggregator
3. Distribution system operator/licensee
4. ISO/RTO or electricity market operator
5. Transmission/system operator

A sixth actor may sometimes be relevant:

1. Technology provider, such as a smart-meter, software, communications or automated-control provider.

The legal question is therefore not simply whether an obligation was breached. The real question is:

Which actor controlled the risk that produced the breach?

A sensible liability framework should distinguish between market liability, contractual liability, network liability, data liability, and physical damage.

4. Primary Liability of the Aggregator

The aggregator is generally the most logical party to bear market-facing performance liability.

This follows from its position as the entity that:

• submits the demand-response bid;
• forecasts aggregate flexibility;
• communicates with customers;
• controls or coordinates response;
• receives market payments;
• reports performance;
• manages measurement and verification; and
• interfaces with the system operator.

Consequently, if an aggregator promises 20 MW of demand reduction but delivers only 12 MW, the market should generally be able to impose the applicable performance consequence on the aggregator rather than pursuing hundreds of individual customers.

FERC's aggregation framework expressly treats the aggregator as the entity that combines distributed resources for participation in wholesale markets. Federal Energy Regulatory Commission

This creates a useful principle:

Single market-facing liability, internally distributed contractual liability.

The market operator deals with one responsible entity, while the aggregator subsequently determines whether some or all of the economic loss should be recovered from participating customers or technology providers.

5. Customer Liability

The participating customer should not automatically be liable for every failure of the aggregation.

Customer liability should depend upon the contractual obligations undertaken.

For example, a customer might promise:

• a maximum load;
• a specified reduction;
• availability during particular hours;
• participation in a specified number of events; or
• maintenance of an automated control device.

If the customer deliberately defeats the agreed response—for example, by overriding a control system without contractual justification—the aggregator may have a contractual claim.

However, customer liability should normally be limited where failure results from:

• a communication failure outside the customer's control;
• an aggregator software failure;
• inaccurate baseline calculation;
• an incorrect dispatch instruction;
• force majeure;
• utility outage;
• equipment failure not attributable to customer negligence; or
• an erroneous market signal.

This prevents an aggregator from transferring all operational risks to consumers merely because the consumer is physically located at the end of the chain.

6. Aggregator's Baseline Risk

One of the most important sources of liability is the baseline.

Demand response is normally measured against an estimate of what the customer would have consumed without the demand-response event.

Suppose:

• estimated baseline = 100 kWh;
• actual consumption during event = 75 kWh.

The apparent reduction is:

100 − 75 = 25 kWh.

But if the customer's genuine expected consumption was actually 85 kWh, the claimed reduction is overstated.

Therefore, inaccurate baseline methodology can generate:

• excessive market payments;
• penalties;
• false performance claims;
• disputes between aggregators and customers;
• disputes with market operators; and
• possible regulatory enforcement.

The aggregator should generally bear responsibility for methodological errors in aggregation and measurement, particularly where it controls the relevant data and algorithm.

7. Measurement and Verification Liability

Aggregated demand response requires reliable:

• interval meters;
• telemetry;
• communications;
• customer identification;
• baseline calculations;
• event records; and
• performance verification.

FERC's Order No. 2222 specifically identifies metering, telemetry, information and data requirements as important components of aggregation arrangements. Federal Energy Regulatory Commission

A useful legal distinction is:

The principle should be control plus causation, rather than simply imposing liability on the party closest to the consumer.

8. Imbalance Liability

Imbalance liability is particularly important.

Suppose an aggregator commits 50 MW of demand reduction but produces only 35 MW. The difference is:

50 MW − 35 MW = 15 MW

The system must obtain the missing flexibility elsewhere.

The EU Electricity Directive provides a particularly clear model. Member States must establish rules requiring market participants engaged in aggregation to be financially responsible for the imbalances they cause, either as balance-responsible parties or through delegated balancing responsibility. EUR-Lex

This approach has three advantages:

First, it creates a clear market counterparty.

The system operator knows whom to charge.

Second, it creates incentives for accurate forecasting.

The aggregator cannot simply promise excessive flexibility and shift the resulting costs to the electricity system.

Third, it allows internal contractual allocation.

The aggregator can impose appropriate contractual consequences on participating customers whose conduct caused the failure.

9. Compensation for Suppliers

Aggregated demand response can also adversely affect a customer's existing electricity supplier.

Suppose:

• Supplier A expects a customer's normal consumption;
• an independent aggregator activates the customer;
• the customer's consumption falls;
• Supplier A's purchasing and balancing position changes.

The EU framework recognizes this problem and allows Member States to require financial compensation where market participants or balance-responsible parties are directly affected by demand-response activation. Such compensation is intended to be limited to resulting costs and should not create an unnecessary barrier to aggregation. EUR-Lex

This demonstrates an important legal principle:

Demand-response participation should not allow one market participant to externalize its activation costs onto another participant.

At the same time, compensation should not become so extensive that it destroys the economic viability of aggregation.

10. Distribution-System Liability

An aggregator may successfully satisfy the wholesale market requirement while simultaneously creating a local distribution-system problem.

For example, 5,000 customers may suddenly increase consumption after a demand-response event ends.

This may cause:

• transformer overload;
• voltage problems;
• reverse power-flow issues;
• congestion;
• local reliability problems.

Therefore, aggregation rules increasingly require coordination between:

Aggregator + Distribution Utility + Wholesale Market Operator.

FERC Order No. 2222 specifically requires coordination among the RTO/ISO, DER aggregator, distribution utility and relevant retail regulator. Federal Energy Regulatory Commission

Consequently, an aggregator should not necessarily be liable for every network consequence of activation if:

• the distribution utility approved the participation;
• the event was within the authorized operating envelope; and
• the network problem arose from a distribution-system condition outside the aggregator's reasonable control.

Conversely, an aggregator that knowingly activates resources in violation of network restrictions may face liability.

11. Cybersecurity and Data Liability

Aggregated demand response depends heavily on digital infrastructure.

The aggregator may possess:

• customer identity information;
• electricity consumption data;
• building information;
• device information;
• operational schedules;
• control-system credentials.

A cybersecurity failure can therefore produce both data liability and electricity-system liability.

California's regulatory framework, for example, requires demand-response providers/aggregators handling customer data to comply with applicable privacy and security requirements, and customers can pursue complaints or actions concerning DR services. California Public Utilities Commission

A modern liability regime should therefore distinguish:

Data breach

Unauthorized disclosure or misuse of customer information.

Operational cyberattack

Unauthorized manipulation of demand-response devices.

Communications failure

Loss of connection preventing dispatch.

Malicious customer conduct

Intentional manipulation of participation or measurement.

The responsible party should depend upon the relevant security obligation and causation.

12. Important Case Law

A. Federal Energy Regulatory Commission v. Electric Power Supply Association, 577 U.S. 260 (2016)

This is the most important U.S. Supreme Court authority for demand response.

The Supreme Court upheld FERC's authority to regulate compensation for demand-response bids in wholesale electricity markets. It held that demand response directly affects wholesale rates and that FERC was regulating the wholesale market rather than impermissibly regulating retail sales. Justia Law

Relevance to liability allocation

The case establishes the legal foundation for treating aggregated demand response as a legitimate participant in wholesale electricity markets.

It therefore supports a framework in which:

• aggregators submit market bids;
• wholesale market rules establish performance requirements;
• compensation and penalties can be incorporated into market tariffs; and
• market participants can be subjected to economically enforceable performance obligations.

The case does not, however, establish a comprehensive tort or contractual liability regime between aggregators and individual customers.

That distinction is important.

B. Electric Power Supply Association v. FERC, D.C. Circuit (2014)

Before the Supreme Court decision, the D.C. Circuit had reached the opposite conclusion concerning FERC's authority over demand-response compensation. The court regarded the rule as intruding into retail regulation. Justia Law

The Supreme Court subsequently reversed that decision.

Relevance

The litigation illustrates why jurisdictional allocation is fundamental to ADR liability.

An aggregator may operate simultaneously across:

• wholesale regulation;
• state retail regulation;
• distribution regulation; and
• private contractual relationships.

Thus, liability cannot be analysed exclusively under one regulatory layer.

C. PJM Power Providers Group v. FERC

The PJM Power Providers Group litigation concerns the legality of FERC-approved PJM market arrangements and demonstrates the importance of FERC's tariff-based regulation of organized electricity markets. The Third Circuit upheld FERC's acceptance of PJM's challenged tariff after reviewing claims that the tariff was unjust, unreasonable and discriminatory. Justia Law

Although the case was not principally an aggregator-liability case, it illustrates an important principle:

Market participants' economic rights and obligations may be substantially determined by FERC-approved market tariffs.

Accordingly, liability in aggregated demand response will often be governed first by the applicable market tariff rather than by ordinary common-law principles.

D. FERC Order No. 2222 and related proceedings

Order No. 2222 is not a judicial case, but it is indispensable to understanding modern ADR liability.

FERC requires RTO/ISO frameworks to address:

• eligibility;
• metering;
• telemetry;
• data;
• coordination;
• distribution-system impacts;
• market participation; and
• interaction with retail programmes. Federal Energy Regulatory Commission

FERC subsequently addressed compliance filings and specifically confirmed that demand-response-only aggregations fall within the aggregation framework. Federal Energy Regulatory Commission

These rules provide the institutional structure within which contractual liability can operate.

13. Indian Legal Position

India is moving toward more sophisticated demand-side and demand-flexibility mechanisms.

The Electricity Act, 2003 provides the broader statutory framework for electricity regulation, while CERC's deviation-settlement framework deals with deviations and grid discipline.

CERC's recent materials show continuing development of deviation-settlement regulation and grid-discipline mechanisms. CERC

At the state level, Maharashtra's Demand Flexibility and Demand Side Management Regulations, 2024 expressly recognize an aggregator as an entity registered with the distribution licensee to provide services including demand-response services, distributed generation and energy storage within a control area. Maharashtra E.R.C.

Delhi has also considered an aggregator-based demand-response programme, including a proposal involving competitive procurement of negawatt capacity. Delhi Electricity Regulatory Commission

These developments suggest an emerging Indian model in which the aggregator acts as an intermediary between consumers and the distribution licensee.

However, Indian jurisprudence specifically addressing civil liability for failure of an aggregated demand-response portfolio remains comparatively underdeveloped. Therefore, existing electricity-regulatory principles, contractual law, deviation-settlement rules and regulatory orders will be important until more specialized case law develops.

14. Contractual Allocation of Liability

A properly drafted aggregator agreement should address at least:

1. Performance obligation

Precisely define the customer's promised reduction.

2. Availability obligation

Specify when the customer must be available.

3. Baseline methodology

Specify how expected consumption will be calculated.

4. Measurement

Identify the authoritative meter and data source.

5. Dispatch authority

Clarify who may activate the customer.

6. Override rights

Specify when customers may legitimately ignore an activation.

7. Penalties

Define consequences for non-performance.

8. Force majeure

Identify events outside reasonable control.

9. Network constraints

Specify what happens when the DSO restricts activation.

10. Indemnification

Allocate third-party claims and regulatory penalties.

11. Cybersecurity

Specify security standards and incident reporting.

12. Data protection

Define ownership, access and permitted use of consumption data.

13. Termination

Specify circumstances permitting withdrawal.

14. Dispute resolution

Provide mechanisms for disputes between aggregator and customer.

15. The "Control and Causation" Principle

A coherent legal system should avoid both extremes.

Extreme 1: Complete aggregator liability

The aggregator becomes responsible for every failure anywhere in the portfolio.

This could make aggregation economically unattractive.

Extreme 2: Complete customer liability

Every participating customer becomes independently liable for market consequences.

This destroys the principal administrative advantage of aggregation.

A better approach is:

Liability should follow control, causation, contractual responsibility and the location of the relevant risk.

For example:

16. Regulatory Penalties vs Private Damages

An important distinction must be made between regulatory penalties and private compensation.

A market operator might impose:

• imbalance charges;
• non-performance charges;
• forfeiture of payments;
• collateral requirements; or
• suspension from participation.

These are not necessarily equivalent to damages payable under ordinary contract law.

For example, if an aggregator pays a €50,000 imbalance charge, it does not automatically follow that it can recover €50,000 from each participating customer.

Recovery from customers requires a separate legal basis, usually:

• contract;
• indemnity;
• statutory authority; or
• applicable programme rules.

This distinction is essential for fair allocation.

17. Aggregation and Collective Responsibility

An interesting legal question is whether liability should be individualized or portfolio-based.

Suppose 100 customers form a 10 MW aggregation.

One customer fails to respond by 2 MW, but another unexpectedly reduces demand by 3 MW.

The overall portfolio delivers 11 MW.

Should the first customer be penalized?

There are two possible approaches.

Individual-performance model

Each customer is measured separately.

Advantages:

• greater accountability;
• clearer causation.

Disadvantages:

• higher administrative costs;
• more complicated measurement.

Portfolio-performance model

Only the aggregate result matters.

Advantages:

• lower transaction costs;
• allows portfolio diversification;
• rewards effective aggregation.

Disadvantages:

• may conceal individual underperformance;
• creates cross-subsidization among participants.

A hybrid approach is generally more workable: market-facing obligations can be portfolio-based while internal customer contracts establish individual performance rules.

18. Economic Rationale

Liability rules should also avoid undermining the economics of demand response.

Demand response produces public benefits including:

• reduced peak demand;
• lower wholesale prices;
• improved system flexibility;
• reduced congestion;
• improved reliability;
• potentially reduced investment in peaking generation.

The Supreme Court in EPSA recognized the role of demand response in reducing wholesale prices and improving grid reliability. Justia Law

Therefore, excessive liability can produce a regulatory paradox:

The system wants more flexibility → but imposes excessive risk on aggregators → fewer aggregators participate → less flexibility is available.

Consequently, liability should be sufficiently strong to prevent opportunistic behaviour without making legitimate aggregation commercially impossible.

19. Emerging Legal Challenges

Future litigation is likely to concern:

Artificial intelligence

AI may forecast customer behaviour and automatically submit bids. Liability will arise if an algorithm systematically overstates flexibility.

Automated buildings

Smart-building systems may independently alter consumption, making causation difficult to determine.

Electric vehicles

Thousands of EVs may simultaneously change charging patterns, creating distribution-network impacts.

Battery aggregation

Aggregated batteries blur the distinction between demand response and generation.

Cybersecurity

A successful cyberattack could simultaneously affect thousands of resources.

Data errors

A defective baseline algorithm could produce systemic overpayment or underpayment.

Double participation

A customer may participate simultaneously in:

• a utility DR programme;
• a wholesale aggregation;
• a capacity programme; and
• another flexibility service.

FERC's framework specifically addresses the need to prevent duplicative compensation and coordinate participation across programmes. Federal Energy Regulatory Commission

20. Conclusion

Liability allocation in aggregated demand response should be structured around the aggregator as the principal market-facing entity, while preserving contractual mechanisms for allocating underlying risks to customers, utilities and technology providers.

The key principles are:

1. Aggregator = primary market-facing responsibility.
2. Customer = responsibility for its own contractual non-performance.
3. Market operator = responsibility for errors within its own market functions.
4. Distribution utility = responsibility for network functions under its control.
5. Technology provider = responsibility where defective technology causes the loss and the contract/law supports recovery.
6. Imbalance costs should generally follow the party responsible for creating the imbalance.
7. Liability should depend on causation and control rather than merely physical proximity.
8. Regulatory penalties must be distinguished from private contractual damages.
9. Data, cybersecurity and baseline accuracy must form explicit parts of the liability framework.
10. The system should maintain sufficient liability discipline without creating disproportionate barriers to demand-response aggregation.

The most significant authorities demonstrate the direction of modern electricity law: FERC v. EPSA establishes the legal legitimacy of wholesale demand response; FERC Order No. 2222 establishes an institutional framework for aggregated distributed resources; EU legislation expressly addresses aggregator imbalance responsibility; and emerging Indian regulations are beginning to recognize the aggregator as a distinct regulatory participant. Justia Law

In short, aggregated demand response requires a layered liability architecture: the aggregator should stand between the electricity market and individual flexible consumers, accept clearly defined market obligations, and then distribute risk internally according to fault, control, contractual commitment and causation.