Of all the disclosure decisions a solar developer makes, none has the risk profile of interconnection queue position — because nothing else you could publish is simultaneously all four of these things:
A public record. Your position, stage, and study status sit in the grid operator’s published queue for anyone to pull — which means every claim you make about it is checkable in one tab, by readers who keep that tab open. Your most underwritable asset. In a market where grid access is the scarce input, a real position with real progress is much of what a development-stage project is — the thing capital, offtake, and acquirers are actually pricing. Competitive intelligence. Your portfolio’s queue pattern — where you filed, what you’re advancing, what you’re optioning — is your land-and-grid strategy written in a public ledger, read by every competitor with an analyst. And volatile. Studies return badly, upgrade allocations kill economics, positions get withdrawn — meaning today’s confident claim is next quarter’s correction.
An asset you must talk about, recorded in a register you can’t edit, revealing strategy you’d rather hold, describing a status that can change under you. That’s the calibration problem, and most developers resolve it badly in one of two directions: saying too much, wrongly — or saying nothing, and letting the public record narrate their flagship asset without them. Here’s the middle, stage by stage.
The audience defines the discipline, and every reader arrives with different checking behavior:
Offtake buyers and their advisors run the arithmetic. We’ve covered how the shortlist screen works; the queue-specific version is brutal in its simplicity: your published COD target gets tested against your published study stage, and a 2028 delivery claim from a project sitting in a phase whose remaining path makes 2028 impossible doesn’t read as optimism. It reads as either the developer can’t do the math or hopes I can’t — and the buyer doesn’t need to decide which.
Tax equity and lenders are underwriting interconnection risk as a core exposure — study completion, upgrade cost allocation, the gap between position and energization. Your public framing doesn’t replace their diligence; it sets the prior their diligence tests. Calibrated public language means diligence confirms; inflated language means diligence catches — and everything after a catch gets read differently.
Acquirers pricing development-stage assets are, to a first approximation, pricing your queue. In dev-stage M&A the position, its vintage, its stage, and its cost exposure are the asset — which makes your public claims about it the first exhibit in a future process, subject to the standing rule: everything gets compared against the record, on the buyer’s timeline, without your commentary in the room.
The host community reads “in the queue” as “it’s happening” — and that misread is the developer’s fault to prevent. A county told “the project is in the interconnection queue” without stage honesty experiences every normal study delay as a broken promise, and the announce-then-stall pattern is how local trust dies before construction starts.
Competitors read for strategy. This is the one audience you’re calibrating against rather than for — and the reason “publish everything” is as wrong as “publish nothing.”
Before any content question, a fluency rule that sorts developers instantly for sophisticated readers: queue language is regime-specific, and using the wrong regime’s vocabulary is a tell.
An ERCOT project moves through ERCOT’s process — screening study, full interconnection study, the standard generation interconnection agreement — under a connect-and-manage philosophy that gets projects to the grid faster in exchange for the generator carrying congestion and curtailment risk. A project in a FERC-jurisdictional RTO lives in a different world: cluster studies, phased windows, network upgrade cost allocations, readiness deposits and withdrawal penalties — a slower, gated process that the recent reform era rebuilt specifically to flush speculative positions.
Public materials that blur these — cluster-study language on an ERCOT project, “SGIA executed” claims where no such instrument applies, generic “late-stage interconnection” that maps to nothing in any regime — tell the professional reader the copy was written by someone who’s never filed in either. Precision here is nearly free and does double work: it’s accurate, and it’s a fluency credential, because only teams inside the process use the process’s real names.
One ERCOT-specific note, since that’s home for most of this readership: connect-and-manage speed is a genuine story and developers underuse it — but sophisticated counterparties know what the speed costs, and an ERCOT project touting queue velocity while silent on basis and curtailment posture reads half-fluent. The credible version pairs them: fast to grid, clear-eyed about merchant risk, and here’s the offtake structure that answers it.
What to say publicly, keyed to where the project actually sits:
Early / screening phase: the project exists on the pipeline page as part of an aggregated early-stage figure — market, capacity band, nothing more. Naming individual screening-phase projects publicly buys you nothing with capital (they discount it correctly), tips your filing pattern to competitors, and plants a flag the community will hold you to through years of uncertainty. The portfolio taxonomy handles this tier; the taxonomy is the disclosure.
Active study phase: the project can be named, with stage stated in regime-correct terms — “full interconnection study underway” / “cluster phase [X]” — and a COD expressed only as a target window whose arithmetic a checker’s open tab will confirm rather than contradict. This is the phase where the false-precision trap lives: a hard delivery date from mid-study isn’t confidence, it’s a future correction filed in advance. “Targeting [year window], subject to study completion” survives every outcome; the naked date survives one.
Agreement executed: now the position is a headline asset and gets stated as one — the instrument named by its real name, the milestone dated on the record, the timestamps beginning their usual work of accumulating into a trail that can’t be retro-faked. This is also when the interconnection story can carry commercial weight publicly: executed grid access is the scarce thing; say the true version plainly.
And when a position withdraws: the pipeline discipline’s attrition move applies with extra force here, because the withdrawal is itself public — the queue report announces it whether you do or not. A quiet removal from your site is fine; the occasionally acknowledged transition is better; and the worst available option is the one developers default to — the project lingering on the pipeline page for eighteen months after the register shows it dead, converting your whole page from evidence into impeachment.
The withhold list, so calibration doesn’t drift into oversharing: amendment and advancement strategy — which positions you’ll push, restudy, or let lapse is live tactics; individual statuses are checkable anyway, but the portfolio logic is yours. Upgrade cost specifics — allocation exposure is data-room material; publishing numbers mid-process arms counterparties and ages instantly. The honest public posture is stage accuracy without cost commentary — sophisticated readers know the category exists and will diligence it; naive readers don’t need it introduced. Commercial readiness postures — what you’d accept, when you’d transact, how motivated you are. The queue page is a record of facts, not a term sheet.
If the whole calibration compresses to a rule: say exactly what the register says, in the register’s own words, plus only the target language your stage’s arithmetic supports — and nothing about why. The facts, precisely; the strategy, never; the dates, in windows; the withdrawals, owned. Developers who hold that line get the compounding this discipline always pays: a public queue story that diligence confirms instead of catches, read by buyers who arrive at the first meeting already believing the position — which, in a market where the position is most of the project, is most of the meeting.
The register is public either way. The only question is whether your version and its version match — because every reader who matters has both open, and the comparison is the screen.
Texas Energy Marketers builds queue-position disclosure into every solar developer engagement — the stage-calibrated project pages, regime-correct language, and pipeline architecture that survive the open-tab check. Request a free Diligence Audit and we’ll run your public claims against the register the way your counterparties already do.
A free review of your digital presence — website, search, and AI visibility — scored the way your counterparties actually see it. No pricing games, no funnels.
Or call (713) 810-8080
Digital presence for the Texas energy sector — the websites, search, AI visibility, and reputation your deals are judged on.
© 2026 - Texas Energy Marketers, All Rights Reserved.
Houston Energy Corridor · Built for Texas energy
