PCLR in three charts: where you sit, how the deal splits, when you decide

ERCOT’s Provisional Controllable Load Resource is mostly a regulatory mechanism — the kind of thing that lives inside stakeholder ballots, nodal protocol revisions, and ten-page client alerts. The parts that actually matter for whether a specific data center site should enroll come down to three things: where the site sits geographically, how a single MW request gets split between firm and flexible service, and how short the decision window is. Three charts, in that order. The technical companion for each, with primary-source citations, is the deeper post on ERCOT PCLR and Batch Zero.

1. Geography is the single biggest variable

The same 500 MW request lands on completely different operating economics depending on which substation it connects to. ERCOT curtails a PCLR most often when its electrical “shift factor” on a binding constraint is high — meaning the site is electrically close to a transmission bottleneck. Sites in the Panhandle and West Texas sit on top of the wind-export bottleneck that has produced ERCOT’s highest historical congestion costs. Sites in the Houston load pocket sit behind a chronic import constraint. Sites in East Texas and the south historically clear at much lower curtailment frequencies.

The chart is schematic. The math behind it — nodal topology, shift factor on each binding constraint, historical shadow-price profile — is what Cliff is being built to compute per site. Until that exists in productized form, every developer is estimating curtailment frequency on instinct or paying a consultant to model it.

2. The deal splits one request into two slices

Under PGRR145 / NPRR1325 a load doesn’t pick “PCLR or firm.” A single request gets split between a firm slice (Low Power Consumption, planned under existing transmission) and a flexible slice that ERCOT bindingly dispatches down via SCED whenever local congestion binds. The firm slice waits for normal transmission upgrades. The flexible slice can energize immediately, in exchange for accepting routine curtailment. The allocation between them is decided per site by ERCOT in the Batch Zero Interconnection Study, delivered Jan 29, 2027.

For a developer, the three numbers that determine whether the deal pencils are: (a) how much firm allocation ERCOT grants, (b) how often the flex slice actually gets curtailed in operation, and (c) the dollar value of energizing years sooner versus the dollar cost of operating without that flex MW during congestion events.

3. The decision window is 14 weeks, not 14 months

ERCOT’s Board target for approving PGRR145 / NPRR1325 is June 1, 2026. The PCLR-specific declaration deadline for developers is July 24, 2026. From today, that’s under 14 weeks. Miss the declaration and the project stays on the standard firm-queue path; miss the March 2027 IA execution and the allocation goes away.

The financial commitment at IA execution is currently set in PUC Project 58481’s Proposal for Publication at $50K/MW intermediate-stage financial security plus $50K/MW non-refundable interconnection fee — though several stakeholder branches are still live and could change the final number. For a 500 MW project that’s roughly $50M committed before commissioning.

What’s next

If you’re evaluating PCLR for a specific Texas site — even early-stage, with just a candidate parcel and rough lat/long — send us the location. We’ll tell you how often ERCOT would actually dial you down at that node and what the math looks like against waiting in the firm queue. Free for the first ten Texas projects evaluated before the July 24 deadline.

For the technical breakdown — PGRR145 §9.7.2 specifics, the Adjusted Bid Cap formula, and the live financial-security branches at PUC Project 58481 — see the companion post on ERCOT PCLR and Batch Zero. For the parallel rulemaking in PJM territory, see PJM’s flex interconnection year.