Announced vs Delivered: The Slippage Signal

A data center project speaks in two voices. The first is the announcement: the ceremonial groundbreaking, the press release naming a go-live quarter, the round megawatt figure quoted to analysts. The second is the delivery: the day the transformer actually arrives, the day the utility actually energizes the connection, the day the first customer actually powers on a rack. The distance between these two voices is the single most useful piece of information an analyst of this industry can track. It is called slippage, and learning to read it separates people who understand the market from people who repeat its press releases.

Start with why announcements are unreliable by nature. They are made early, by parties with an incentive to project confidence, and they are anchored to the best-case schedule — the timeline that assumes every long-lead component arrives on time, every permit clears, and the grid connects on the promised date. In a supply environment as strained as the current one, the best case is rarely the real case. So the announced go-live date is not a lie exactly; it is an aspiration stated as a fact. The delivered date, by contrast, is the aspiration after reality has finished editing it. Faraday's read: never mistake the groundbreaking for the go-live, and never take a megawatt figure as capacity until it has actually been energized. Announced capacity and operating capacity are different quantities, and the difference between them, aggregated across a market, is one of the most mispriced facts in the sector.

The practical skill is knowing which milestones carry information and which are theater. A groundbreaking carries almost none — dirt can be moved on a site that will not be energized for years. Steel topping out carries a little more. But the milestones that genuinely bind are further down the chain: the placement of the long-lead equipment order, which sets the earliest possible energization; the utility's firm energization date, which is often the true constraint; and the commissioning completion, which is the last gate before revenue. An analyst who tracks these load-bearing milestones, and ignores the ceremonial ones, gets a far cleaner read on where a project actually stands than one who counts press releases.

Slippage is most valuable read as a rate, not a single event. A project that slips a quarter once may have hit a discrete problem. A project that slips a quarter every two quarters is telling you something structural — its supply chain is not holding, or its grid connection is receding, or its execution capability is weaker than claimed. Tracking the trajectory of the announced date over time, as it is quietly revised, reveals the underlying trend. When a go-live that was promised for one year is walked, revision by revision, into a year later, the pattern of walking is the signal. The endpoint is less informative than the slope.

This reading scales up from individual projects to whole markets. If you aggregate announced capacity across a metro and compare it with what actually energizes, the gap tells you whether the market's headline pipeline is real. Contested markets — where grid interconnection queues stretch for years and transformer allocation is fought over — show wide, persistent gaps: enormous announced pipelines, modest delivered capacity, and slippage that compounds. Less constrained markets show tighter gaps and more reliable delivery. An investor or operator deciding where to commit capital learns more from the market's historical slippage than from its announced pipeline, because the slippage reveals the true friction of building there.

There is a subtle trap to avoid. Because everyone now announces early and orders speculatively, some announced projects are options rather than commitments — placeholders that may never convert. This inflates announced pipelines with phantom capacity that was never going to be delivered on the stated date, or at all. So slippage must be read with judgment: distinguish a real project that is genuinely delayed from a speculative announcement that was never firm. The tell is usually in the load-bearing milestones. A project with a placed equipment order and a firm energization date is real and merely late; a project with nothing but a press release and a rendering is an option wearing a project's clothes.

The discipline, in the end, is one of skepticism applied systematically. Take every announced date as a hypothesis, not a fact. Watch the load-bearing milestones, not the ceremonial ones. Read slippage as a rate and a trend, not a single miss. Discount announced pipelines by the market's historical delivery gap. Do this consistently and you acquire something rare: an early, honest view of what supply is actually going to exist, months or years before it shows up in anyone's reported numbers. In a market where everyone is shouting about what they will build, the person quietly measuring what actually gets delivered holds the more valuable information.