Utility Integrated Resource Plan Filing and Long-Term Resource Procurement
An integrated resource plan is the most consequential document a regulated utility produces, and it is filed in public. It states how the utility intends to meet forecast demand over a long horizon: what generation it retires and when, what it builds, what it contracts for, how much efficiency and demand-side management it procures, what transmission it needs, and how the portfolio performs under different fuel price, carbon policy, and load scenarios. Because it is filed with a commission, it attracts intervenor testimony from large customers, competitive suppliers, environmental organizations, and consumer advocates, so the assumptions get litigated line by line and the modeling has to survive adversarial review. That review burden is itself a purchase driver: a plan that cannot be defended with granular, reproducible capacity expansion and production cost modeling gets sent back. Load forecasting has become the contested center of these proceedings, because large interconnection requests from data centers, reshored manufacturing, and vehicle and building electrification have broken methods built on two decades of flat or declining demand. Everything downstream of the plan is procurement: all-source solicitations, technology-specific RFPs, capacity contracts, storage, and demand response. Avina detects these filings, the forecast revisions behind them, and the solicitations that follow.
Why an Integrated Resource Plan Filing Is a Buying Signal for Sales Teams
The integrated resource plan is unusual among corporate planning documents in that it is adversarial by design. A utility files it, and then parties with opposing commercial and policy interests get to challenge the assumptions on the record. Large industrial customers challenge the cost allocation. Competitive suppliers challenge the build-versus-buy conclusion. Environmental intervenors challenge the retirement timeline and the carbon scenarios. Consumer advocates challenge the load forecast and the resulting rate impact. That structure means the plan is not a document that merely has to be written, it is a position that has to be defended, and the quality of the underlying modeling determines whether it survives. That defensibility requirement is the first and most reliable purchase driver. Capacity expansion and production cost modeling at the granularity commissions now expect, with stochastic load and weather scenarios, hourly dispatch, resource adequacy accounting for intermittent generation, and reproducible runs that intervenors can interrogate, is not something a utility does on spreadsheets anymore. Plans that come back with deficiencies or conditions usually come back because the analysis could not answer a question, and the remediation is tooling and expertise rather than a redraft. Load forecasting has become the contested center of these proceedings, and it is a genuinely new problem. Utilities spent two decades planning against flat or declining demand, and the forecasting methods, organizational muscle, and even the headcount reflect that. Large interconnection requests from data centers, reshored manufacturing, and electrification of vehicles and buildings have inverted the picture, and a utility revising its forecast materially upward has to justify the revision against intervenors who will argue the load is speculative. Defending it requires new methods, new data sources, probabilistic treatment of uncertain large loads, and usually new tooling, and the utility has to acquire all of that inside a filing calendar. Everything downstream of an approved plan is procurement, which is where the larger budgets sit. The preferred portfolio translates into all-source solicitations, technology-specific requests for proposals, capacity auctions, power purchase agreements, storage and dispatchable capacity contracts, and demand response expansion. Each of those requires bid intake and evaluation capability, contract structuring, counterparty credit assessment, and portfolio risk management at a scale many utilities have not run before, particularly those that historically built rather than bought. Retirement dates create their own programs, and they are the most date-certain element of the plan. Committing publicly that a plant closes in a specific year starts decommissioning engineering, site characterization and remediation, workforce transition planning, replacement capacity procurement, and frequently repowering studies or interconnection rights reuse. Each of those has its own vendors and its own timeline anchored to a published date. Transmission is the binding constraint in most current plans, and this is relatively recent. A portfolio that looks optimal on paper is undeliverable if the transmission to move the energy does not exist or sits behind a multi-year interconnection queue. That pulls transmission planning studies, interconnection queue management, siting and right-of-way work, and grid modeling into the resource planning conversation, and it means transmission constraints have to be represented inside the capacity expansion model rather than checked afterward. Distribution planning has to align, which is often the last gap discovered. Electrification load does not arrive at the system level, it arrives on specific feeders and substations that were not sized for it, which connects the resource plan to distribution system planning, hosting capacity analysis, and advanced metering data. Utilities that treat these as separate exercises tend to find out at the feeder level. The process itself supplies calendar certainty that few commercial signals offer. Plans are filed on statutory cycles, comment periods and hearings run on schedules, and commission orders issue on known timelines. The window between filing and order is a period in which the utility is actively defending and refining its position, which is precisely when analytical capability gets bought.
How Does Avina Detect Integrated Resource Plan Activity?
Avina, an AI-powered GTM platform, monitors commission dockets, procurement solicitations, and planning hiring together, because the public record covers this process end to end. Docket filings are tracked directly. Integrated resource plan filings, resource adequacy filings, preferred portfolio selections, and the commission orders that approve, reject, or condition them are monitored with filing and order dates, since the conditions attached to an order specify exactly what analysis the utility now has to produce. Load forecasts are read for revision. Forecast updates, large load interconnection request disclosures, and data center, industrial, and electrification demand attributed in filings are tracked, because a material upward revision is both the most contested element of a plan and the clearest indicator that forecasting capability is being rebuilt. Procurement activity is captured as it follows the plan. All-source and technology-specific requests for proposals, capacity solicitations, bid evaluation reports, and announced power purchase, storage, and capacity agreements are monitored, which identifies the point at which the plan converts into contracting work. Retirement and addition commitments are tracked with dates. Plant retirement notices, replacement capacity filings, repowering studies, and new generation announcements are monitored, since each carries a published date and a defined program behind it. Adversarial process is monitored as a quality indicator. Intervenor testimony, stakeholder comments, settlement filings, and the specific deficiencies raised against a plan indicate where the utility's analysis failed and therefore what it needs. Transmission and distribution constraints are captured. Transmission planning studies, interconnection queue postings, siting applications, and hosting capacity filings are tracked because they determine whether the preferred portfolio is deliverable. Hiring confirms internal capability. Postings for resource planning engineers, capacity expansion and production cost modelers, load forecasting analysts, transmission planners, and power procurement managers indicate whether the utility is building the function or will source it externally. Each account is enriched with the plan filing and order dates, the preferred portfolio composition, forecast revisions and their drivers, retirement and addition commitments with dates, active solicitations, intervenor challenges and order conditions, transmission constraints, and resource planning staffing, then matched against your ICP filters.
What Happens When an Integrated Resource Plan Signal Fires?
Avina scores on the gap between what the plan commits to and the capability the utility has demonstrated. A utility filing a plan with a materially revised load forecast, large data center interconnection requests, near-term retirement dates, and order conditions requiring additional analysis scores highest, because the commission has effectively specified the purchase. A utility entering a new filing cycle with thin resource planning staffing scores high for modeling and advisory. A utility whose approved portfolio shifts it from building generation to contracting for it scores highest for procurement, bid evaluation, and contract management, because that is a capability change rather than a capacity change. Timing is set by statute and docket, which makes it unusually predictable. The pre-filing window is when modeling and forecasting capability gets acquired. The filing-to-order window is when the utility is defending assumptions and buying analytical and expert support. The post-order window is when conditions get remediated and solicitations launch. Retirement dates and solicitation deadlines sit further out but are published, so sequences can be built against them years in advance. Routing follows the plan's own structure. The vice president of resource planning or system planning owns the plan and the modeling decisions. The director of load forecasting owns the forecast that intervenors will attack. Power supply and procurement leadership own the solicitations and the contracts that follow approval. Transmission and distribution planning leadership own deliverability. Regulatory affairs and the general counsel's office own the docket, the testimony, and the case management, and are the right entry point for anything touching the filing process itself. The chief financial officer and treasury own the capital plan and the rate case that recovers it. Avina identifies which of these exist and flags utilities carrying large new load with limited planning staffing. Contacts are enriched with verified emails, phone numbers, and LinkedIn profiles through waterfall enrichment across resource planning, forecasting, power supply, transmission planning, and regulatory affairs roles. Reps receive a Slack alert naming the utility, the plan filing and expected order dates, the preferred portfolio, forecast revisions and the large loads driving them, retirement commitments, active solicitations, the specific conditions or intervenor challenges raised, and resource planning staffing. Salesforce and HubSpot records carry docket and solicitation dates so sequences fire against the regulatory calendar rather than press coverage. Qualified accounts can be auto-enrolled into Outreach or Salesloft sequences matched to the stage: capacity expansion and production cost modeling, load forecasting and electrification analytics, resource adequacy and reliability modeling, transmission and distribution planning tools, interconnection queue and study management, procurement and bid evaluation platforms, energy trading and risk management, contract lifecycle management for power purchase agreements, regulatory case management and testimony support, and the consulting and expert witness services that decide whether a plan survives the docket.
Start Tracking Integrated Resource Plan Filings With Avina
A resource plan commits a utility in public to a generation and procurement path that intervenors will attack line by line. Activate this signal in Avina's Signals Library. Every plan includes a 7-day free trial with no credit card required.