Option-to-Lease Expiration and Interconnection Milestones

The scenario that kills queue positions

A developer entered MISO's interconnection queue in Q3 2022 with a 150 MW solar project. At that time, FERC Order 2023 had not yet been issued (it was published in July 2023). The developer's land package was assembled with standard 3-year option-to-lease agreements, expiring in August 2025.

Under the old MISO rules, the timeline would have worked. But FERC Order 2023 imposed graduated thresholds retroactively on existing queue positions. At IA execution, MISO now requires 100% coverage with executed instruments only. Options are excluded entirely (allow_options = false).

The developer's IA execution date is November 2025. The options expire in August 2025. Even though the options are still active in August, they don't count toward coverage at the IA execution stage. The developer needs to convert those options to executed leases before IA execution — but the options expire before the conversion can be completed.

Result: coverage drops from 95% (with options) to 62% (executed instruments only). The MISO filing is rejected. The queue position, acquired over 3 years of study deposits and engineering work, is at risk.

Coverage calculation when an option expires

Understanding exactly how an expired option affects coverage requires walking through the calculation step by step.

Step 1: Status filter

The coverage audit's first filter checks instrument_status. Only instruments in executed or recorded status pass. An expired option has status expired and is immediately excluded from the spatial calculation. An active (unexpired) option in executed status passes this filter but may fail the next one.

Step 2: Eligible instrument type filter

Each RTO defines which instrument types are eligible at each stage. At IA execution for all RTOs, the eligible list is: fee_simple, executed_lease, easement, row_agreement. The types option_to_lease and option_to_purchase are not in this list. An active, unexpired option fails this filter at IA execution.

This is the critical distinction: an option does not need to expire to be excluded from coverage. At IA execution, even an active option with 10 years remaining on its term is excluded because the instrument type is not eligible.

Step 3: Spatial union

Only instruments that pass both filters contribute their parcel geometries to the spatial union. The coverage percentage is computed as:

Coverage % = ST_Area(ST_Union(qualifying parcel geometries) ∩ project boundary) / ST_Area(project boundary) × 100

Parcels controlled only by excluded options create gaps — holes in the coverage map where the project boundary has no qualifying instrument coverage.

Worked example

Total project boundary: 1,000 acres. Qualifying coverage at IA execution: 320 + 160 + 40 = 520 acres = 52%. Required: 100%. Gap: 480 acres across APN-003 (option type excluded) and APN-004 (expired).

At application stage (50% threshold, options eligible), coverage was 100%. The same land package drops to 52% at IA execution purely because of instrument type eligibility rules.

Options at different stages

Option treatment varies by RTO and stage. The transition from "options count" to "options excluded" is the most dangerous moment in a project's queue lifecycle.

CAISO is the only RTO that discounts options before excluding them entirely. At facilities study, CAISO options contribute at 75% of their acreage weight. A 100-acre option-controlled parcel contributes only 75 acres to coverage at facilities. This progressive discount serves as an early warning: if your project relies heavily on options, coverage will drop at facilities before it collapses at IA execution.

Three ways developers get caught

1. Option expires before IA execution date

The most straightforward failure. The option's expiration_date is earlier than the project's IA execution date. At the moment of expiration, the instrument's status transitions to expired and its acreage drops out of coverage entirely — even at stages where options would otherwise be eligible.

This is what a nightly expiration scan catches. At 90, 60, 30, and 7 days before expiration, alerts fire. But if no one is monitoring those alerts or taking action on them, the option quietly expires and coverage drops.

2. Option is active but ineligible at the current stage

The option has not expired. It's in executed status with years remaining. But the project has advanced to IA execution, where options are not in the eligible instrument type list. The option's acreage is excluded from coverage — not because the option is broken, but because the queue stage no longer accepts that instrument type.

This failure mode is invisible in spreadsheet-based tracking. A spreadsheet that shows "Option C — Active — Expires 2028" looks fine. But at IA execution, that option contributes zero acres.

3. Option expires before site_control_deadline

Each RTO derives a site_control_deadline from milestone dates. For MISO, it's the miso_definitive_study_agreement_date (if set) or ia_execution_date - 60 days. For CAISO, it's ia_execution_date - 30 days. An option that expires after IA execution but before the site control deadline still causes a problem because the developer must demonstrate coverage by the deadline.

Milestone-aware alerts

Standard expiration alerts (90/60/30/7 days before expiration) are necessary but not sufficient. They tell you an option is expiring. They don't tell you whether that expiration matters for your interconnection queue.

A milestone-aware alert system adds a critical layer: it compares the option's expiration date against the project's site_control_deadline. If an option expires before the site control deadline, a milestone_expiration_risk alert fires — even if the expiration is 365 days away.

The alert cadence for milestone-aware risks:

The 365-day alert is the most valuable. It gives land teams a full year to negotiate lease conversions, which typically take 30–90 days for willing landowners and much longer for reluctant ones.

Practical conversion timeline

Converting an option-to-lease to an executed lease is not instantaneous. The typical timeline:

1. Exercise notice (Day 0). Developer sends formal exercise notice per option agreement terms. Most options require 30–60 days' notice.
2. Lease negotiation (Days 0–60). Even though the option defines key terms, the full lease often requires additional negotiation: insurance requirements, restoration obligations, access roads, setbacks, and revenue sharing.
3. Title search (Days 30–45). PJM requires title search at facilities stage. CAISO recommends it at facilities. Run this in parallel with lease negotiation.
4. Execution and recording (Days 45–90). All owners must sign. For LLCs, you need the authorized signatory. For trusts, you need the trustee. For properties with multiple owners, you need every natural person in the ownership chain. Recording with the county clerk adds 1–4 weeks depending on the county.

Total realistic timeline: 60–90 days for a cooperative landowner with clean title. Longer if there are title defects, unresponsive owners, or contested terms.

This means the 90-day milestone alert is your last opportunity to begin conversion and still have it completed before the deadline. The 30-day alert means you're already behind unless the lease is nearly executed.

MISO-specific: the DSA trigger

MISO has a unique milestone: the Definitive Study Agreement (DSA) date, stored as miso_definitive_study_agreement_date. MISO's site control deadline is derived from this date (if set) or from ia_execution_date - 60 days.

For MISO projects, the system fires a conversion_deadline alert when:

• The project's current stage is approaching IA execution (within 90 days of ia_execution_date).
• The project contains option_to_lease or option_to_purchase instruments that have not been exercised.
• Those options are still in executed or recorded status (not yet expired or superseded).

This alert is specifically designed for the MISO conversion cliff: options count at DSA but are excluded at IA execution. The 90-day window before IA execution is the conversion deadline.

Spreadsheet limits vs. stage-aware spatial audit

Most land teams track site control in spreadsheets. A typical spreadsheet has columns for parcel APN, landowner, instrument type, execution date, and expiration date. Some add a "coverage %" column with a simple acreage formula.

This approach breaks in three ways under FERC Order 2023:

1. No stage awareness. The spreadsheet shows one coverage number. But coverage changes at every stage because eligible instrument types and option weights change. A project that shows 95% in a spreadsheet may be 52% at IA execution.
2. No spatial accuracy. Spreadsheet acreage is typically from assessor records or GIS estimates. It doesn't account for partial overlaps with the project boundary, setback buffers, or encumbrance exclusions. The real coverage percentage requires a spatial intersection (PostGIS ST_Intersection) between parcel geometries and the project boundary.
3. No milestone awareness. A spreadsheet can flag an option expiring in 60 days. It cannot flag that the option expiration is 30 days before the MISO DSA trigger date, making conversion critical. The interconnection timeline and the land timeline exist in separate systems with no link between them.

A stage-aware spatial audit solves all three. Coverage is computed at each stage using the RTO's rules for that stage. The spatial calculation uses actual parcel geometries intersected with the project boundary. And milestone-aware alerts link option expirations to interconnection deadlines.

The land team that discovers an option-coverage gap at IA submission has run out of options. The one that discovers it 365 days before the site control deadline has time to convert, renew, or find replacement acreage.