# Three planned buildings do not establish one India delivery date

CoreWeave specifies three buildings and phased India delivery. Building count does not establish the number of commissioning phases or one date for the whole campus.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-10-07
Original announcement: https://investors.coreweave.com/news/news-details/2026/CoreWeave-Enters-India-Expanding-AI-Cloud-Platform-With-AdaniConneX/default.aspx
Canonical URL: https://retrivium.ai/retrospectives/retro-india-power-phase-timeline/

CoreWeave's India release specifies three planned buildings and a phased delivery schedule. It does not say those buildings equal exactly three commissioning phases. Keeping the physical unit separate from the delivery unit prevents a campus total from becoming an invented single availability date or an unsupported phase count.

## Read the two units separately

The [October 7, 2026 announcement](https://investors.coreweave.com/news/news-details/2026/CoreWeave-Enters-India-Expanding-AI-Cloud-Platform-With-AdaniConneX/default.aspx) describes three 80 MW buildings and the first phase expected in mid-2028. The first statement describes physical scope; the second describes timing. They should remain separate fields.

| Published item | Unit | Meaning preserved |
| --- | --- | --- |
| Three buildings | Physical facilities | Planned campus structure |
| 80 MW per building | Electrical capacity | Building-level design scale |
| First phase in mid-2028 | Delivery milestone | Expected initial availability |
| Later capacity in phases | Delivery sequence | Additional timing remains to be specified |

The table does not allocate a particular building to a phase because the source does not provide that mapping.

## Earlier roadmaps have their own units

CoreWeave's [January 5 Rubin roadmap](https://www.coreweave.com/news/coreweave-extends-its-cloud-platform-with-nvidia-rubin-platform) concerns platform adoption. The [August 4 Indonesia expansion](https://www.coreweave.com/news/coreweave-expands-cloud-ai-platform-to-indonesia-marking-first-move-into-asia-pacific-region) concerns another set of future facilities. These dated precursors establish technical and geographic development before India.

Neither supplies the missing building-to-phase mapping. The causal hypothesis is coordinated expansion across several kinds of planning object, which makes preserving units more important as the program grows.

## A phase needs a usable scope

For an application team, an initial phase becomes relevant when its usable configuration and operating window are known. A building may contain equipment at different readiness states. A delivery phase may cover a defined portion of the program. These are general possibilities, not a disclosure of the campus's unpublished schedule.

The source therefore supports an expected first milestone without identifying every workload or allocation that milestone will serve. Treating it as an all-campus date would enlarge the claim beyond its stated scope.

## Keep dependencies attached to the right milestone

An illustrative project calendar can link facility commissioning, equipment readiness and application acceptance rather than giving them one shared date. A delay can then be assigned to the relevant dependency instead of being described vaguely as “the campus is late.”

This structure also recognizes partial progress. Some usable capacity can matter before an entire physical program is complete, provided its operating boundary is actually established.

## Report the first date without inventing the rest

The retrospective result is precise: a planned campus has a first expected phase and later phased capacity. The public record leaves further scheduling questions open.

[GPU availability](/journal/gpu-availability-cost-per-hour/) explains useful operating windows. [GPU onboarding](/journal/gpu-pool-onboarding/) explains readiness transitions. Together they make a phased infrastructure plan understandable without equating buildings, delivery phases and customer allocations.