Keep the claim attached to its evidence.

1. Match the site and phase

A nearby site, similar name or common developer does not establish that two records describe the same project.

• Reported project name and aliases
• Reported developer/operator and role (do not merge these roles)
• City, county, state and responsible jurisdiction
• Parcel or site identifier, if publicly documented
• Campus, building or phase covered; evidence for the match

2. Keep one row per claim

Keep reported wording separate from your conclusion. A source check is not independent confirmation or a new project milestone. Use unknown when a date is not stated.

• Claim and exact source wording
• Public source URL, publisher and document/case identifier
• Source publication date (or explicitly unknown)
• Event/effective date stated by source (separate from publication)
• Date you found the source; date you last checked it
• Reported stage, role or capacity; geographic and phase scope
• What the source establishes; what remains unknown
• Later source, contradiction or correction and its public explanation

3. Separate hearings from decisions

A hearing notice or favorable recommendation does not establish final approval. A land-use decision alone does not establish construction, power availability or every environmental permission.

• Authority, case number, site and scope
• Application, notice, staff recommendation, hearing or adopted decision
• Meeting date and agenda item; minutes, resolution or decision URL
• Result, conditions and work authorized, quoting the instrument
• Later withdrawal, denial, appeal, amendment or superseding action
• Which permissions and jurisdictions still need checking

4. Preserve the capacity basis

Do not turn an up-to amount into delivered capacity, add overlapping phases, or equate electrical demand with IT load. If the basis is unclear, retain that uncertainty.

• Source-qualified wording, range or category
• Unit and basis: IT load, site power, utility demand or other
• Per-building, phase, site or portfolio scope
• Requested, proposed, contracted, energized or delivered
• Forecast date and dependencies, if explicitly reported

5. Record the remaining business question

A named contractor or a project stage does not establish an open bid package, a buying contact or an available assignment.

• Decision this evidence can support
• Unresolved identity, stage, permission or team question
• Next public source or responsible authority to check
• Known contradiction disclosed alongside the claim
• Researcher review date; separate editorial publication/update date

Citation and method limits

Suggested method citation: Data Center Radar, Data center project evidence worksheet, edition October 19, 2026, https://datacenterradar.com/research/data-center-project-evidence-worksheet, accessed [your access date].

Cite the original document for each project claim. Citing this worksheet does not substantiate a project's identity, status, capacity or approval. It is a research aid, not a national census, engineering assessment or complete list of required permissions. The edition date describes this worksheet, not a check of any project.

Record publication, event, discovery, source-check and editorial dates separately. Do not fill a missing date with today's date. Disclose known contradictions and corrections alongside the affected claim; do not quietly replace the earlier account. A missing search result leaves a question unresolved.

Use public sources for a public worksheet. Do not include private contact details or member-only evidence in a public copy. Third-party source documents retain their own reuse terms; this worksheet grants no rights to them.