Commercial Operation Date COD

What it is (precise)

COD marks the formal handover of a stationary storage plant from "being built" to "operating commercially." By that date the containers, racks, PCS, MV transformers and the POI substation must be installed, commissioned and energized, and the plant must have demonstrated it can charge and discharge to its contracted power (MW) and energy (MWh) under the conditions defined in its agreements.

The exact prerequisites are written into the interconnection agreement, the EPC contract, and the offtake agreement (a Power Purchase Agreement, Tolling agreement, or capacity contract), so COD is a contractual term of art whose precise definition varies project to project.

Practically, declaring COD requires a chain of acceptances: utility or ISO permission-to-operate at the POI, completion of a capacity and performance test proving deliverable MW, MWh and round-trip behavior, closure of NFPA 855 commissioning items and authority-having-jurisdiction inspections, and lender or independent-engineer acceptance for financed projects.

COD is distinct from mechanical completion, from substantial completion (an EPC milestone), from first energization or backfeed, and from trial operation under the interconnection agreement. A single project can carry several differently worded COD definitions — one in the interconnection agreement, one in the offtake, one in the financing documents — and they rarely align by accident.

Why it matters in a real grid-scale project

COD is the trigger that starts revenue and resets the financial clocks. Offtake revenue, capacity payments, and incentive timelines typically begin at COD, while the construction loan converts to term debt, the Special Purpose Vehicle shifts from spending Capex to earning against Opex, and the warranty and availability-guarantee periods start counting.

For lenders, a credible path to COD is central to Bankability: slipping past the guaranteed COD promised to the offtaker can trigger daily liquidated damages, default provisions, or loss of an interconnection position or incentive deadline, so the date is the most heavily protected milestone in the schedule.

Engineering decisions are downstream of this. Because the long-term capacity warranty, the degradation table and the augmentation plan are all referenced to COD, the as-built usable energy demonstrated at COD sets the beginning-of-life baseline against which LFP cell fade is measured for the life of the asset — a weak or padded COD test distorts every Levelized Cost of Storage and augmentation calculation that follows.

Rushing commissioning to hit a contractual COD — truncating the performance test, skipping a complete UL 9540A-informed hazard review, or leaving NFPA 855 punch-list items open — trades a schedule win for operational and safety risk that surfaces later.

Typical values and standards

COD is a date, not a measured quantity, so the numbers that matter are the test thresholds and timelines around it. Capacity tests typically require demonstrating roughly 95 to 100 percent of the contracted MWh at the POI, net of PCS, transformer and auxiliary losses, with buy-down liquidated damages below the guarantee; round-trip efficiency guarantees for lithium-ion plants commonly sit in the 85 to 92 percent AC-AC range depending on the metering boundary.

Availability guarantees beginning at COD are typically 95 to 98 percent. Delay liquidated damages are commonly quoted per MW per day or as a fraction of contract price per day, with an outside "sunset" date some 90 to 365 days after the guaranteed COD.

Schedule-wise, treat COD as the end of a commissioning and testing window: for a 100 MW-class, 2-to-4-hour plant, commissioning plus capacity testing and market qualification commonly runs 2 to 4 months after mechanical completion, longer if grid outages or ISO test slots are scarce.

The standards stack is a precondition, each with a distinct role: NFPA 855 governs the installation, UL 9540 is the ESS product safety certification the AHJ expects on the equipment, UL 9540A is the fire-propagation test method whose data supports the NFPA 855 hazard case, and NFPA 68/69 cover the deflagration strategy. In US markets, ISO commissioning tests and resource registration (plus NERC registration for larger plants) must also close before commercial dispatch.

How it shows up in specs, studies and contracts

A working engineer meets COD first in the EPC contract, where it sits above substantial completion in the milestone ladder and carries the delay-LD regime, and in the offtake, where it is a condition precedent to payment. Read the capacity-test protocol like a datasheet: what MWh figure is guaranteed, at which reference point (POI net, not DC nameplate), at what ambient temperature and SOC window, over how many consecutive cycles, and with what allowance for auxiliary consumption.

Then check that the interconnection agreement's trial-operation requirements and the offtake's COD conditions can physically be satisfied in the same window — mismatched definitions are a classic source of a plant that is "done" but cannot yet earn.

COD also anchors everything long-dated. Degradation and augmentation tables count anniversary years from COD; the battery capacity warranty and the availability guarantee start at COD; insurance flips from construction all-risk to operational coverage on that day, which is where Insurability reviews concentrate; and in the US the tax-credit placed-in-service determination is a related but legally separate test.

Useful questions on any project: which document's COD definition governs which obligation, who certifies the capacity test (usually an independent engineer), what happens on partial or phased COD for a multi-block site, and whether the guaranteed COD still clears the interconnection and incentive deadlines after known slippage.

Worked examples

Baseline case. Take a 100 MW / 400 MWh plant with a guaranteed COD of 1 June and a contracted 380 MWh deliverable at the POI. Mechanical completion lands 1 March; backfeed energizes the auxiliary supply on 15 March; the capacity test runs 20-28 April and measures 372 MWh net at the meter; the utility grants permission to operate on 12 May; the independent engineer signs on 20 May; COD is declared 25 May. The plant was physically finished for almost three months before it earned a cent — that gap is the commissioning window, and it is where schedules quietly slip.

Capacity shortfall. Change one number: the same test measures 361 MWh instead of 372 — 95.0% of the 380 MWh guarantee. If the contract sets a 95% floor with buy-down damages below it, the project scrapes through and the owner keeps a plant whose warranted baseline is 19 MWh thinner than the model assumed; every augmentation and Levelized Cost of Storage calculation for the next fifteen years now starts from that lower number. If the floor had been 97%, the same result would have triggered a buy-down payment instead.

Delay damages. Miss the date and the arithmetic reverses — an ISO test slot slips COD to 24 June, twenty-three days late, and delay damages are set at $1,500 per MW per day. That is 100 MW × 23 days × $1,500 = $3.45 million, payable before the plant has earned anything — which is why guaranteed COD is the most heavily negotiated date in the contract and why teams are tempted to truncate the very test that protects them.

Phased COD. A 300 MW site built as three 100 MW blocks can declare partial COD per block — block 1 in April, block 2 in June, block 3 in August — with capacity payments, availability guarantees and warranty clocks all pro-rated per block. Get this drafted explicitly and block 1 earns for four months while block 3 is still being commissioned; leave it implicit and the offtaker can argue no payment is due until the whole site is complete.

Definitional trap — the cheapest to avoid, the most common to hit. A project passes the interconnection agreement's trial-operation requirement in May and the team books revenue in the model from 1 June — but the offtake defines COD to additionally require a 72-hour continuous availability demonstration that has not been run. The plant is energized, tested and legally allowed to operate, yet it is not at COD under the document that actually pays. Always ask which contract's definition governs which obligation.

Common pitfalls

The recurring trip-wires are definitional. Teams conflate first energization or mechanical completion with COD and discover the revenue meter is not running; they let the interconnection COD, offtake COD and lender COD drift apart so the plant passes one gate and fails another; or they demonstrate DC nameplate energy instead of the contracted usable MWh at the POI, leaving a few percent of shortfall to be discovered at the worst possible moment.

Phased projects need explicit partial-COD mechanics — pro-rated capacity payments, LDs and warranty starts per block — or the paperwork will not match the electrons.

The other family of pitfalls is treating the COD test as a formality. The capacity test is the baseline for a decade or more of degradation claims, so its conditions — temperature, resting SOC, auxiliary loads, measurement points — must be recorded with test-report rigor.

A test run at favorable conditions overstates the baseline and quietly shifts warranty risk to the owner. And note the one consumer-world contrast worth making: unlike an EV delivered with a factory-certified pack, a grid-scale BESS proves its rating in the field, on its own site, against its own contracts — which is exactly what COD exists to formalize.