Skip to main content

Site selection evidence

Capacity-definition and delivery dependency register

Build an editable capacity-definition and delivery dependency register, with source locators, open decisions and a file your team can review.

data-center utility commitments, cooling dependencies and delivery stages

Start the work product
Conceptual illustration of data-center utility commitments, cooling dependencies and delivery stages

One working file to take back to the team

Connect the records. Preserve the exceptions.

1. Inspect two worked rows.

The fictional example shows the actual columns, document mismatches and open decisions for this task.

2. Build your own register.

Start blank, edit the cells and add as many records as the review needs, up to 200 rows per file.

3. Export and assign review.

Download the register as CSV or a readable text file, including source context and edition. The companion below helps organize the next document requests.

Your editable work product

Capacity-definition and delivery dependency register

Use this worksheet for data-center utility commitments, cooling dependencies and delivery stages. Record the actual document location beside each observation. The fictional example demonstrates a review problem, not a verified deal.

Bring these records

  • Delivery-stage definition
  • Capacity definition and technical basis
  • Utility commitment and conditions
  • Cooling and connectivity dependencies

How to use the table

  1. Start one row for each delivery element. Keep distinct documents and competing versions separate.
  2. Connect capacity / service meaning to the same row. Record a document locator and retain any mismatch instead of silently choosing a value.
  3. Complete acceptance decision with the decision still open and the person who should review it. Export the register with the source documents.

Start with a blank row or load the fictional example.

Your entries remain in this page only. Download or copy before leaving; nothing is automatically saved or fetched.

Add one record or comparison per row. Leave unknown facts blank or name the missing document. Scroll the table horizontally on a small screen. Each cell accepts up to 2,000 characters.

Capacity-definition and delivery dependency register · 1 row
RowDelivery elementRecord the delivery element from the documents or leave it unresolved.Capacity / service meaningRecord the capacity / service meaning from the documents or leave it unresolved.Document stageRecord the document stage from the documents or leave it unresolved.Condition / dependencyRecord the condition / dependency from the documents or leave it unresolved.Acceptance decisionRecord the acceptance decision from the documents or leave it unresolved.Document / page locatorEnter the actual file, page, exhibit or source record for this row. Method links below are not property evidence.Remove
1Your entry
1 / 200 rows

Take the working file with you

You can export this blank table before filling it in elsewhere. The export includes the kit edition, row provenance and method references. Method references do not verify your property.

CSV copy fallback

If file saving is blocked, copy this into a UTF-8 .csv file.

This table does not upload documents, search records, run an AI model or confirm source facts. The next-request worksheet below is a separate companion; entries are not copied between the two tools.

Companion: document requests

Turn unresolved items into a review handoff.

This separate four-item sheet helps organize supporting requests. It does not copy or analyze the entries in your register.

Open, work, export

Make the next decision easier to review.

Use this worksheet for data-center utility commitments, cooling dependencies and delivery stages. Record the actual document location beside each observation. The fictional example demonstrates a review problem, not a verified deal.

01 Delivery-stage definition

Prevents land or a shell from being described as an operating facility.

Observations and source reference
02 Capacity definition and technical basis

Separates service rating from supported IT load.

Observations and source reference
03 Utility commitment and conditions

Establishes what the supplier has actually committed to and when.

Observations and source reference
04 Cooling and connectivity dependencies

Identifies systems that can constrain the stated operating plan.

Observations and source reference

Works in this page. No uploads, record searches, contact capture or automatic saving. Download your sheet before leaving.

Method and source context

Keep the evidence with the worksheet.

These references explain the method. They do not verify facts about your property. Your export keeps their scope separate from the document references you enter.

Best Practices Guide for Energy-Efficient Data Center Design

U.S. Department of Energy · Checked 2026-09-30

July 2024 design guidance connecting IT loads, electrical systems, cooling and heat recovery.

  • Design guidance cannot verify utility delivery capacity, a connection date, redundancy or operating performance at a specific site.
Read source ↗
Commercial Real Estate Lending, Comptroller’s Handbook, version 2.0

Office of the Comptroller of the Currency · Checked 2026-09-30

March 2022 supervisory handbook; lease review, property income, re-leasing costs and property-type distinctions.

  • Bank supervisory guidance, not a property appraisal, current market survey or universal financing standard. No handbook percentage is adopted as a deal assumption.
Read source ↗
What this edition does
  • Editorial workflow, not an automated property investigation, valuation or approval.
  • Public sources support the research questions, not the fictional example facts.
  • A supplied reference remains subject to human review; unknown and conflicting evidence must stay visible.
NextAutomation · Working kit 2026-09-30.1