Published by Stacked AI
Use this blank worksheet to connect a proposed power-delivery date to a defined requirement, supporting documents and unresolved dependencies. It supports a screening decision: what can be relied on for the next step, what still needs evidence, and what would change the assessment.
Copy it into a private working document and create one version per proposal. Keep the requirement consistent when comparing sites. Empty fields mean unknown, not zero or “no issue.” This is a blank working tool, not a completed engagement or a delivery commitment.
1. Define the requirement and the milestone
| Working field | Your entry |
|---|---|
| Proposal/site reference and worksheet revision date | — |
| Decision to make and decision deadline | — |
| Required initial usable IT load; units and measurement boundary | — |
| Facility/utility demand, if known; basis for relating it to IT load | — |
| Later capacity and expansion milestones | — |
| Rack density, cooling and connectivity requirements | — |
| Earliest and latest acceptable operating dates | — |
| What “ready” means, including installation and acceptance work | — |
| Permitted phasing, interim capacity and fallback | — |
Distinguish utility service available at the site, an energized facility and capacity usable by the proposed workload. Record which milestone each quoted date describes. Do not convert a utility supply figure into usable IT load without a documented basis.
Use evidence statuses consistently
| Status | Meaning in this worksheet |
|---|---|
| Unknown | The relevant information or source has not been identified. |
| Requested | A specific request has an owner and due date; its answer has not been assessed. |
| Received — not reviewed | Material is available, but the relevant claim has not been checked. |
| Reviewed — unresolved | Material has been examined, but a gap, condition or conflict prevents a conclusion on this claim. |
| Verified — with scope | A specific claim has been checked against the recorded source. Record the check, reviewer role, date and limits. |
These workflow labels complement the evidence and editorial methodology. Mark reported statements, assumptions and estimates explicitly. “Verified” applies only to the stated check; it does not guarantee delivery, establish legal enforceability or certify the whole site. A document can confirm one claim while leaving another unresolved. Split those claims into separate entries.
2. Identify the claims to check
Use these prompts to open an evidence record for each relevant claim. Documents and responsible parties vary by site and service arrangement.
| Item | Question to resolve | Possible source to request |
|---|---|---|
| P1: Capacity | What quantity is available for this proposal, at what boundary, and after which existing commitments? | Service documentation, electrical design, provider allocation and capacity schedule |
| P2: Service identity | Do the documents refer to this location, service recipient and proposed use? | Dated utility correspondence and relevant service documents |
| P3: Utility timing | What supports the date, and is it an estimate, target or stated commitment with conditions? | Utility correspondence, studies, service or construction documents |
| P4: Remaining utility work | Which upstream work, funding, approvals, access or construction remains? | Scope, milestone schedule and current status evidence |
| P5: Facility and equipment | What equipment, construction and workload-specific preparation remains? | Procurement records, design status and construction schedule |
| P6: Acceptance | What must be tested or accepted before this workload can operate? | Commissioning scope, test records, outstanding exceptions and acceptance responsibilities |
| P7: Change and fallback | What happens operationally if quantity, scope or timing changes? | Proposed commercial milestones, contingency plan and specialist review of relevant terms |
A document's title or signature alone does not resolve every dependency. Technical suitability belongs in the appropriate engineering review; interpretation of rights and contractual obligations belongs with counsel.
3. Copy this evidence record for each claim
| Evidence record | Your entry |
|---|---|
| Item ID and exact claim being checked | — |
| Evidence status | — |
| Source/issuer, document date, version and relevant section | — |
| What the document actually states; units, location and scope | — |
| Check performed, reviewer role and review date | — |
| What is supported by that check | — |
| Conditions, conflicts, assumptions and information still missing | — |
| Decision affected; effect if the claim is not supported | — |
| Next request/action, responsible party and due date | — |
Retain superseded versions and explain a changed conclusion. If a received document contradicts an earlier statement, record the conflict rather than averaging the two dates or capacities.
4. Connect the remaining dependencies
Work backward from the required workload-ready milestone. Record dependencies between activities, not just a list of target dates.
| Activity / predecessor | Responsible party | Milestone and supporting record | Effect on the requirement if delayed |
|---|---|---|---|
| — | — | — | — |
| — | — | — | — |
| — | — | — | — |
Include customer installation work where it sits outside the provider's scope. A confirmed equipment order does not by itself establish that site preparation, delivery, installation and commissioning are complete.
5. Record the screening conclusion
| Decision field | Your entry |
|---|---|
| Statements supported by the reviewed evidence | — |
| Statements still unsupported or conditional | — |
| Next step: continue review, seek evidence before further commitment, carry a fallback, or set aside for now | — |
| Reason for that next step; evidence IDs | — |
| New evidence or changed condition that would alter it | — |
| Action owner, next review date and decision deadline | — |
Do not collapse a confirmed delay, a missing document and a technical mismatch into the same score. They may require different next actions. Completing the worksheet organizes the evidence; it does not replace the required utility, engineering or contractual review.
Read the companion power-delivery evidence guide. For a site shortlist, explore the Site Screen, or contact Stacked AI with the decision, requirement and deadline. Agree a suitable sharing process before sending confidential project records.