DATA CENTER RADAR · Published Oct 11, 2026 · Source passages reviewed Oct 11, 2026 · Research workflow updated Oct 14, 2026
Before pursuing work on a data center, ask what its construction timeline actually measures. A zoning decision, a completed shell, utility energization and an accepted fit-out describe different milestones. A campus headline can also combine an operating building with phases that have yet to start.
This guide helps contractors, suppliers and business-development teams compare schedule evidence and decide what to ask next. Use the construction manager's milestone worksheet to identify responsibilities, then use the comparisons below to read dates at the same scope.
How long does data center construction take?
Start by defining the facility and the clock. JLL's January 2026 Global Data Center Outlook, page 24, reports an average global build time of 18 months for a 50 MW facility. That is a dated benchmark for a specified facility size, not a promised U.S. campus schedule. It does not establish the start and finish of a particular project's timeline.
For the site you are researching, establish whether the estimate covers a new facility, an expansion, a shell or a fit-out. Record the building or phase, what starts the clock, and what ends it. Land acquisition through first operational use is a different interval from site work through shell completion. Do not add overlapping design, equipment and construction periods as if every activity happens in sequence.
Read the milestones separately
| Milestone | What to check | What it does not establish |
|---|---|---|
| Approvals and permitted work | Authority, case or permit number, dated decision, conditions and exact work covered; check later hearings, revisions or withdrawals. | Actual work on site, every required approval, or a procurement award |
| Utility service | Dated service milestones, prerequisites, work responsibilities and confirmation of energization requirements | Usable power from a proposed capacity announcement or an equipment delivery |
| Equipment readiness | Approved design, release to manufacture, factory testing, delivery commitment and site readiness for the specified package | Installation or acceptance merely because a purchase order exists |
| Shell and fit-out | A dated progress statement identifying the exact scope completed and the remaining electrical, mechanical or other work | Completion of the fit-out, another building or the whole campus |
| Testing and handoff | Required tests, acceptance criteria, outstanding items and the party authorized to accept the work | Accepted handoff or operational use from a statement that testing has begun |
Approvals need a locality check. Loudoun County's permitting resource explains that county approval can leave other applicable approvals outstanding. This is a named locality example; use the responsible jurisdiction's documents for your site. The permit-check workflow explains how to identify the authority and match a decision to its work scope.
Track utility service separately from a quoted MW figure. Read the contractor and capacity field guide before comparing IT capacity, utility requirements or phased announcements. Its power-readiness evidence checklist identifies the supply milestone and next unanswered question. Do not infer an energization date or a phase's power allocation from a campus total.
For equipment, record which event starts the delivery clock: order, deposit, approved submittals or release to manufacture. Delivery still needs to fit the site's receiving, installation and testing sequence. The equipment lead-time guide provides package-level questions.
Turner & Townsend's data-centre delivery overview describes coordination across design, procurement, construction and commissioning. It supports treating those activities as connected; it is a service-provider description, not a duration benchmark or evidence about a Radar project.
Compare two updates without creating a false delay
Fictional examples: the following dates and buildings are invented to illustrate how to read a schedule. They do not describe Radar project records.
| Earlier statement | Later statement | Supported reading |
|---|---|---|
| Building A shell completion forecast: June 30 | Building A fit-out completion forecast: September 30 | Different finish milestones. These dates do not establish a three-month delay. |
| Building A shell completion forecast: June 30 | The same shell forecast revised to July 31 | A changed forecast at the same scope. Check the reason and whether the earlier date was a contractual commitment before describing a missed commitment. |
| Building A is operating | Building B is proposed for a later phase | One building's operational status does not establish whole-campus completion or Building B's construction start. |
Keep the original source and the later update. Compare the site, building, work package, milestone and date type before calculating a change. A forecast revision, a documented missed commitment and a recorded actual finish are different observations. If the sources disagree about scope, retain both and record the unresolved question.
Check a hearing's outcome and subsequent actions before using it to describe the schedule. A hearing notice is not a decision. Match a withdrawal or denial to its application and scope before attributing it to an entire campus. Record the specific local risk and its source; avoid turning regional opposition or a general grid constraint into a claim that this project is delayed.
Copy a blank milestone register
Create one row per milestone. Leave unsupported dates blank and mark them unknown. This template contains no project data.
| Field | Entry to record |
|---|---|
| Site, building, phase and work package | ________ |
| Milestone and exact source claim | ________ |
| Date and type | ________ / forecast, commitment, actual or unknown |
| Source URL and source date | ________ / ________ |
| Date checked | ________ |
| Prerequisite and supporting evidence | ________ |
| Responsible party and next question | ________ / ________ |
| Earlier claim, revision or unresolved conflict | ________ |
The date you checked a document is a research date, not a new construction event. A recent article can also repeat an older forecast. Record the underlying document's date and distinguish a quoted plan from a new development.
Turn the timeline into a qualified next step
Start with the U.S. project directory, then check the recorded development stage and the evidence for your package. Confirm who buys it, the procurement route and whether an opportunity remains open before committing pursuit time. A construction stage alone does not confirm an open bid, a purchase order or buying authority.
If the milestone is unknown, make the next action specific: ask the relevant department about a permit's scope, the project team about the service milestone, or the package purchaser about release conditions. Separate what the source says from what you still need to establish.
Radar's research methodology explains source and coverage limits. Membership provides available project details and supporting sources; research depth varies by record. The free weekly digest is another way to follow reviewed previews.
Sources and what each supports
- JLL, January 2026 Global Data Center Outlook, printed page 24: the global benchmark for a 50 MW facility used above. Record its size and geographic scope; it is not a project-specific forecast.
- Loudoun County permitting: a locality example of checking applicable permissions separately. It does not establish the requirements or progress of a site in another jurisdiction.
- Turner & Townsend data-centre delivery overview: provider context previously reviewed October 11, 2026. It is not independent evidence of a project duration.
The milestone table, fictional comparisons and blank register are Radar's editorial method. When reporting a schedule change, link the comparison and retain both underlying dated statements at the same site, phase and milestone. Report a change in forecast as a change in forecast; an actual finish needs its own evidence.
Use this guide as a source
Use this guide to explain how to compare milestones, date types and scope before interpreting a schedule change. The checklists are Data Center Radar's editorial research method. They do not establish a particular project's current status or a complete inventory of its permissions.
Reference: Data Center Radar. Data center construction timeline: milestones to check. Research workflow updated October 14, 2026. Include the date you accessed the page and link to the relevant section.
For a project claim, cite its underlying document as well: publisher or authority, document title and date, page or reference, exact site or phase, and the date checked. Keep a forecast, recorded decision and completed work distinct. State any conditions, later action or unresolved conflict that changes the meaning.
The three linked source passages were reviewed October 11, 2026; research workflow and citation guidance updated October 14, 2026. Market research, locality procedure and provider descriptions are context; they do not verify individual project schedules.