Define: Dispatch Schedule

What Dispatch Schedule Means in a Contract

A Dispatch Schedule is the operational document, or series of documents, that tells a generator, supplier, or offtaker exactly when energy must be produced, delivered, or curtailed. In a contract, it functions as the practical instruction set that translates broad supply obligations into concrete, time-stamped actions. Rather than describing energy volumes in the abstract, the schedule ties performance to specific hours, days, or settlement periods.

The term typically appears in agreements governed by an Energy Purchase Agreement, where the buyer and seller need a mechanism for coordinating output with demand. Because energy cannot easily be stored and grid stability depends on precise timing, the Dispatch Schedule becomes one of the most operationally significant documents referenced in the contract, even though it is often issued separately from the main agreement.

Contracts usually treat the Dispatch Schedule as a living instrument. It is not fixed at signing but is generated, updated, or reissued by a system operator based on real-time or forecasted grid conditions. The contract's role is to define how that schedule is incorporated, how disputes over its content are resolved, and what happens if a party fails to follow it.

How Dispatch Schedule Is Defined or Measured

Dispatch Schedules are generally measured in discrete time blocks, such as half-hourly or hourly intervals, each specifying a required output level or delivery quantity. The precision of these measurements matters because deviations, even small ones, can trigger balancing charges, penalties, or curtailment payments depending on how the contract allocates risk.

Definitions commonly specify who issues the schedule (a transmission system operator, distribution network operator, or independent system operator), how far in advance it is communicated, and whether it is binding or indicative. Some contracts distinguish between a day-ahead schedule and a real-time or intraday adjustment, each carrying different compliance expectations.

• Time granularity of the schedule (hourly, half-hourly, or other intervals)
• Method and timing of communication from the system operator to the contracting parties
• Whether the schedule is firm or subject to later revision
• Consequences of deviation, including tolerance bands and remedial payments

Because measurement standards can vary by market design, the contract should reference the applicable grid code or operating procedures rather than assuming a universal formula.

Where Dispatch Schedule Appears in Agreements

The concept most often surfaces in power purchase arrangements, generation interconnection agreements, and balancing or ancillary services contracts. It also appears in operational annexes attached to broader supply agreements, where the main contract sets commercial terms and the annex incorporates the technical schedule by reference.

Within the Energy sector, Dispatch Schedules are central to contracts between generators and grid operators, as well as agreements between retailers and wholesale suppliers. They can also appear in contracts touching adjacent sectors, such as Manufacturing facilities with on-site generation or large industrial consumers with demand-response obligations.

In many agreements, the Dispatch Schedule clause sits alongside provisions on metering, settlement, and force majeure, since all of these mechanisms interact when actual delivery diverges from the scheduled plan.

Why the Exact Wording Matters

Precise wording determines whether the Dispatch Schedule is a binding obligation or merely an operational guideline. If the contract says a party "shall comply" with the schedule, deviations may constitute breach. If it says a party "shall use reasonable efforts to follow," the standard is softer and more forgiving of unavoidable variances caused by weather, equipment failure, or grid instructions.

The wording also affects liability allocation. Contracts that clearly state whether curtailment instructions from the system operator override the Dispatch Schedule, and who bears the financial consequences of that override, reduce the risk of disputes when actual dispatch differs from planned dispatch.

Ambiguity about update timing is another common source of conflict. A contract that does not specify how quickly a revised schedule must be communicated, or how parties should respond to late notice, leaves room for disagreement about whether a party had a fair opportunity to comply.

Drafting Considerations

Drafters should define who has authority to issue and revise the Dispatch Schedule, how that authority is exercised, and what documentary form the schedule takes (electronic notice, portal posting, or written instruction). Clear incorporation language ensures the schedule is treated as part of the operative contract terms rather than an informal courtesy communication.

It is also worth addressing tolerance thresholds, remedies for non-compliance, and the interaction between the Dispatch Schedule and force majeure or curtailment clauses. Where the underlying transaction involves complex technical coordination, drafters may want to build in a structured review process similar to how a Risk Management Plan allocates responsibility for anticipated operational variances.

Finally, because the law governing the contract may impose separate regulatory requirements on system operators, drafters should confirm that contractual definitions do not conflict with mandatory grid codes or licensing conditions, and should include a mechanism for amending the Dispatch Schedule provisions if regulatory obligations change over time.