Grid access

Interconnection Queue Context

Nearby queue volume, ISO/RTO congestion signal, and project mix for site feasibility conversations.

Natural language query

Ask a dataset

Compose once, then run the prompt in Gridleaf or copy it into Claude or ChatGPT with the dataset context attached.

gridleaf_queue_context

Visual target

Queue depth + congestion signal

Query inputs

query_contract
Claude setup

Portal handoff

Open

Gridleaf dataset: Interconnection Queue Context Tool: gridleaf_queue_context Sources: ISO/RTO queue data, Gridleaf interconnection model Source readiness: On-demand queue context / Feasibility screening Query contract: - Title: Queue context query contract - Primary entity: Interconnection area - Time grain: Latest queue snapshot - Visualization mode: Queue depth + congestion signal - Inputs: location (geo, required) e.g. near Lubbock, TX; market (enum, optional) e.g. ERCOT; radius_miles (number, optional) e.g. 25 miles; technology (list, optional) e.g. solar, storage - Example queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Interconnection Queue Context baseline analysis - Output: Queue depth + congestion signal - Result preview: Queue context result (Queue MW) - Query contract: Queue context query contract (Latest queue snapshot) - Metrics: Queue MW, Project count, Congestion signal, Technology mix - Sources: ISO/RTO queue data, Gridleaf interconnection model - Source readiness: On-demand queue context (Feasibility screening) - Source caveats: ISO/RTO queues can lag withdrawal and milestone changes.; Nearby queue density is not an interconnection capacity guarantee. - Source next actions: Refresh queue status before ranking competing projects.; Pair queue density with local substation and congestion evidence. - Steps: Route the natural-language question to the right Gridleaf dataset. -> Run or prepare the matching Gridleaf portal tool with source-status caveats. -> Return a decision-ready answer and the next Claude or ChatGPT prompt. Result preview contract: - Title: Queue context result - Chart: Queue MW mix - Primary metric: Queue MW - Fields: technology, queue_mw, project_count, congestion_signal - Example rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Interconnection Queue Context baseline analysis - Visualization: Queue depth + congestion signal - Fields: technology, queue_mw, project_count, congestion_signal - Rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) - Source readiness: On-demand queue context (Feasibility screening) - Next queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site?; How crowded is the queue near this site?; What project mix is competing for interconnection? For a solar or storage site near Lubbock, TX, summarize interconnection queue context, congestion signal, and the follow-up diligence questions for Claude. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. User question: Show queue MW mix near Lubbock for solar and storage. query_contract: Queue context query contract Primary entity: Interconnection area Time grain: Latest queue snapshot Query inputs: - location: near Lubbock, TX (required) - market: ERCOT (optional) - radius_miles: 25 miles (optional) - technology: solar, storage (optional) Required inputs covered by provided values or contract examples. Return Queue depth + congestion signal with source_status_policy caveats, result_preview fields, and the next Gridleaf portal or Claude follow-up.

Gridleaf answer preview

Gridleaf will route this ask to gridleaf_queue_context and return Queue depth + congestion signal for near Lubbock, TX.

answer_preview

Primary result

Solar: 640 MW / Crowded

Visual

Queue MW mix

Source

On-demand queue context

Preview rows

Solar

9 projects

640 MW

Crowded

Storage

7 projects

520 MW

Watch

Hybrid

4 projects

310 MW

Moderate

Answer notes

Expected output fields: technology, queue_mw, project_count, congestion_signal.

Source readiness: On-demand queue context (Feasibility screening).

ISO/RTO queues can lag withdrawal and milestone changes.

AI handoff package

Copy a provider-ready package with source readiness, analysis steps, and the Gridleaf return URL.

Provider

Claude

Source readiness

On-demand queue context

Return

Gridleaf portal

Return to Gridleaf

External AI return

Bring the Claude or ChatGPT answer back with the external_ai_return contract and source checks.

Result preview

Queue context result

Nearby project mix, queue MW, congestion signal, and feasibility questions for grid access.

Queue MW

Queue MW mix

MW
Solar
72
Storage
64
Hybrid
38
Load
28
Other
16

Example rows

Solar

9 projects

640 MW

Crowded

Storage

7 projects

520 MW

Watch

Hybrid

4 projects

310 MW

Moderate

technologyqueue_mwproject_countcongestion_signal
Query contract

Queue context query contract

Ask with location, ISO/RTO, radius, technology filters, and congestion or project-mix focus.

query_contract

Primary entity

Interconnection area

Time grain

Latest queue snapshot

Visualization

Queue depth + congestion signal

Inputs

Location

location

Required

Site, coordinates, substation area, or market region.

Example: near Lubbock, TX

Market

market

Optional

ISO/RTO or utility territory when known.

Example: ERCOT

Radius

radius_miles

Optional

Distance around the target site for nearby queue context.

Example: 25 miles

Technology

technology

Optional

Project types to include in queue mix.

Example: solar, storage

Natural-language examples

Show queue MW mix near Lubbock for solar and storage.

How crowded is the interconnection queue within 25 miles of this site?

Analysis playbooks

Run a structured workflow in the portal, then carry the same prompt into Claude or ChatGPT.

2 workflows
Playbook

Queue density brief

Nearby queue depth, project mix, and interconnection risk memo.

1Measure queue depth
2Classify competing projects
3Draft interconnection risk memo

Claude + ChatGPT prompt

Gridleaf dataset: Interconnection Queue Context Tool: gridleaf_queue_context Sources: ISO/RTO queue data, Gridleaf interconnection model Source readiness: On-demand queue context / Feasibility screening Query contract: - Title: Queue context query contract - Primary entity: Interconnection area - Time grain: Latest queue snapshot - Visualization mode: Queue depth + congestion signal - Inputs: location (geo, required) e.g. near Lubbock, TX; market (enum, optional) e.g. ERCOT; radius_miles (number, optional) e.g. 25 miles; technology (list, optional) e.g. solar, storage - Example queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Queue density brief - Output: Queue depth + congestion signal - Result preview: Queue context result (Queue MW) - Query contract: Queue context query contract (Latest queue snapshot) - Metrics: Queue MW, Project count, Congestion signal, Technology mix - Sources: ISO/RTO queue data, Gridleaf interconnection model - Source readiness: On-demand queue context (Feasibility screening) - Source caveats: ISO/RTO queues can lag withdrawal and milestone changes.; Nearby queue density is not an interconnection capacity guarantee. - Source next actions: Refresh queue status before ranking competing projects.; Pair queue density with local substation and congestion evidence. - Steps: Measure queue depth -> Classify competing projects -> Draft interconnection risk memo Result preview contract: - Title: Queue context result - Chart: Queue MW mix - Primary metric: Queue MW - Fields: technology, queue_mw, project_count, congestion_signal - Example rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Queue density brief - Visualization: Queue depth + congestion signal - Fields: technology, queue_mw, project_count, congestion_signal - Rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) - Source readiness: On-demand queue context (Feasibility screening) - Next queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site?; How crowded is the queue near this site?; What project mix is competing for interconnection? For a solar or storage site near Lubbock, TX, summarize interconnection queue context, congestion signal, and the follow-up diligence questions for Claude. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: Queue density brief Outcome: Nearby queue depth, project mix, and interconnection risk memo. Workflow steps: 1. Measure queue depth 2. Classify competing projects 3. Draft interconnection risk memo Playbook prompt: Build an interconnection queue density brief. Summarize nearby queue MW, project mix, congestion signal, and the diligence questions to continue in Claude.

Run playbook in portal
Playbook

Grid-access watchlist

Follow-up queue and congestion questions for site screening.

1Identify grid access signals
2Rank project competition
3Recommend next portal queries

Claude + ChatGPT prompt

Gridleaf dataset: Interconnection Queue Context Tool: gridleaf_queue_context Sources: ISO/RTO queue data, Gridleaf interconnection model Source readiness: On-demand queue context / Feasibility screening Query contract: - Title: Queue context query contract - Primary entity: Interconnection area - Time grain: Latest queue snapshot - Visualization mode: Queue depth + congestion signal - Inputs: location (geo, required) e.g. near Lubbock, TX; market (enum, optional) e.g. ERCOT; radius_miles (number, optional) e.g. 25 miles; technology (list, optional) e.g. solar, storage - Example queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site? Analysis plan contract: - Version: gridleaf-analysis-plan.v2 - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Grid-access watchlist - Output: Queue depth + congestion signal - Result preview: Queue context result (Queue MW) - Query contract: Queue context query contract (Latest queue snapshot) - Metrics: Queue MW, Project count, Congestion signal, Technology mix - Sources: ISO/RTO queue data, Gridleaf interconnection model - Source readiness: On-demand queue context (Feasibility screening) - Source caveats: ISO/RTO queues can lag withdrawal and milestone changes.; Nearby queue density is not an interconnection capacity guarantee. - Source next actions: Refresh queue status before ranking competing projects.; Pair queue density with local substation and congestion evidence. - Steps: Identify grid access signals -> Rank project competition -> Recommend next portal queries Result preview contract: - Title: Queue context result - Chart: Queue MW mix - Primary metric: Queue MW - Fields: technology, queue_mw, project_count, congestion_signal - Example rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) Dataset insight packet: - Version: gridleaf-dataset-insight.v1 - Contract key: dataset_insight - Dataset: Interconnection Queue Context (queue-context) - Tool: gridleaf_queue_context - Workflow: Grid-access watchlist - Visualization: Queue depth + congestion signal - Fields: technology, queue_mw, project_count, congestion_signal - Rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate) - Source readiness: On-demand queue context (Feasibility screening) - Next queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site?; How crowded is the queue near this site?; What project mix is competing for interconnection? For a solar or storage site near Lubbock, TX, summarize interconnection queue context, congestion signal, and the follow-up diligence questions for Claude. Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query. Analysis playbook: Grid-access watchlist Outcome: Follow-up queue and congestion questions for site screening. Workflow steps: 1. Identify grid access signals 2. Rank project competition 3. Recommend next portal queries Playbook prompt: Create a grid-access watchlist for a solar or storage site. Rank queue crowding, competing project mix, congestion signal, and next Gridleaf portal queries.

Run playbook in portal
Source readiness

Use this dataset with clear source caveats.

mixed

Freshness

On-demand queue context

Decision grade

Feasibility screening

Sources

2

Caveats

ISO/RTO queues can lag withdrawal and milestone changes.

Nearby queue density is not an interconnection capacity guarantee.

Next source actions

Refresh queue status before ranking competing projects.

Pair queue density with local substation and congestion evidence.

Coverage

Queue depth, project mix, nearby generation/storage activity, and congestion signal for interconnection feasibility checks.

Metric

Queue MW

Metric

Project count

Metric

Congestion signal

Metric

Technology mix

Ask this dataset

How crowded is the queue near this site?

What project mix is competing for interconnection?

What diligence questions should Claude answer next?

AI-ready prompt

Use the same prompt shape in the portal, Claude, or ChatGPT when this dataset is selected.

Start prompt
Gridleaf dataset: Interconnection Queue Context
Tool: gridleaf_queue_context
Sources: ISO/RTO queue data, Gridleaf interconnection model
Source readiness: On-demand queue context / Feasibility screening

Query contract:
- Title: Queue context query contract
- Primary entity: Interconnection area
- Time grain: Latest queue snapshot
- Visualization mode: Queue depth + congestion signal
- Inputs: location (geo, required) e.g. near Lubbock, TX; market (enum, optional) e.g. ERCOT; radius_miles (number, optional) e.g. 25 miles; technology (list, optional) e.g. solar, storage
- Example queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site?

Analysis plan contract:
- Version: gridleaf-analysis-plan.v2
- Dataset: Interconnection Queue Context (queue-context)
- Tool: gridleaf_queue_context
- Workflow: Interconnection Queue Context baseline analysis
- Output: Queue depth + congestion signal
- Result preview: Queue context result (Queue MW)
- Query contract: Queue context query contract (Latest queue snapshot)
- Metrics: Queue MW, Project count, Congestion signal, Technology mix
- Sources: ISO/RTO queue data, Gridleaf interconnection model
- Source readiness: On-demand queue context (Feasibility screening)
- Source caveats: ISO/RTO queues can lag withdrawal and milestone changes.; Nearby queue density is not an interconnection capacity guarantee.
- Source next actions: Refresh queue status before ranking competing projects.; Pair queue density with local substation and congestion evidence.
- Steps: Route the natural-language question to the right Gridleaf dataset. -> Run or prepare the matching Gridleaf portal tool with source-status caveats. -> Return a decision-ready answer and the next Claude or ChatGPT prompt.

Result preview contract:
- Title: Queue context result
- Chart: Queue MW mix
- Primary metric: Queue MW
- Fields: technology, queue_mw, project_count, congestion_signal
- Example rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate)

Dataset insight packet:
- Version: gridleaf-dataset-insight.v1
- Contract key: dataset_insight
- Dataset: Interconnection Queue Context (queue-context)
- Tool: gridleaf_queue_context
- Workflow: Interconnection Queue Context baseline analysis
- Visualization: Queue depth + congestion signal
- Fields: technology, queue_mw, project_count, congestion_signal
- Rows: Solar: 640 MW (Crowded); Storage: 520 MW (Watch); Hybrid: 310 MW (Moderate)
- Source readiness: On-demand queue context (Feasibility screening)
- Next queries: Show queue MW mix near Lubbock for solar and storage.; How crowded is the interconnection queue within 25 miles of this site?; How crowded is the queue near this site?; What project mix is competing for interconnection?

For a solar or storage site near Lubbock, TX, summarize interconnection queue context, congestion signal, and the follow-up diligence questions for Claude.

Return a concise analytical memo, call out source freshness and caveats, and suggest the next Gridleaf portal query.

Related datasets