Arlington North, 420 MW, filed in 90 days.

Customer drops the project into the Queue Intelligence workspace: 420 MW, Q1 2028 COD, three candidate POIs in Oncor territory. Our engine normalizes the load profile against the ERCOT base case and generates the initial queue risk memo within an hour.

Cliffcenter's SB 6 eligibility engine runs the project against the PUCT 58481 draft rule. The result: the customer qualifies for the ERCOT Batch Study framework at two of three POIs, with a self-curtailment commitment of 18% required to clear the third.

The incentive atlas returns 14 eligible Texas programs across the three candidate counties. Our form-mapping engine produces a ranked list: Ch. 313 replacement (TX), Trinity Metro opportunity zone, Arlington local property tax abatement, and a TWDB water infrastructure grant. Projected capture: $84M NPV.

The Site Intelligence moratorium watch flags a newly-filed Arlington city council ordinance proposing a cooling-water cap for large industrial loads. Our community engagement playbook fires: we draft a public-comment response, a meeting brief for the city council member representing the district, and talking points for the customer's public affairs lead.

Queue Intelligence generates the draft ERCOT submittal package: GIR request, GINR, load profile template, SCADA spec, single-line diagram, financial readiness attestation, self-curtailment commitment, and per-POI upgrade cost narrative. Ready for counsel review.

The customer's outside counsel — a mid-tier Texas energy firm, not an AmLaw 100 — reviews the package in 8 days. Four redlines, three of which are counsel preferences and one of which catches a potential Batch Study eligibility argument we hadn't flagged. We update the schema in production that same day.

We accompany the customer to an informal pre-filing meeting with ERCOT planning staff. The meeting brief, prepared by Cliffcenter and reviewed by counsel, walks through the upgrade cost envelope and the self-curtailment proposal. ERCOT asks three clarifying questions; answers are resolved in two days.

The ERCOT submittal package is filed electronically. Every field sources to a document in the customer's workspace. Counsel signs; the customer's project team gets a copy of the filing and a compliance calendar seeded with every downstream deadline.

ERCOT confirms the project advances into the Batch Study window. Two competitors fail the readiness gate; the customer moves up two slots in the schedule.

The Texas Ch. 313 replacement application package ships. Our form-mapping engine handled 38 of 44 fields without a human in the loop; the customer's CFO signed the attestation. Local property tax abatement package is 80% complete.

The Arlington cooling-water ordinance is amended to exempt projects that commit to a water reclamation target. Our playbook had pre-identified three ordinance precedents with similar carve-outs — the customer's public affairs lead used them in direct testimony.

Every upstream filing is active: ERCOT interconnection, Ch. 313 replacement, Arlington property tax abatement, TWDB water infrastructure, Trinity Metro opportunity zone. The BTM Workflow page shows a clean regulatory graph with 22 downstream deadlines, all green.