A template you can use without contacting us
Data center requirements brief
Bring the project's aims, requirements and open questions together before a site search or screening. Prepare the draft and take it to your next conversation.
Contents
- Project aim and buyer role
- Geographic boundary
- Load definitions: IT load, facility load or connection — not a bare number
- Stages and what a target date means
- Hard requirements and preferences, kept apart
- Existing evidence and confidentiality level
- The next decision the delivery should support
Copyable brief outline
Start with the decision you need to make. Separate hard requirements from preferences and use unknown where no answer exists. A completed brief is a working draft; it does not mean the sizing has been reviewed.
Fill in what you know. Answers stay in this open page and are lost when you leave or reload it. Copy or download the draft to keep it. Nothing is submitted to Powered Sites here.
Record when the brief was written and which version applies.
Describe the purpose of the first assignment and the commissioning role.
State the search area or approximate location. Sensitive location details can wait.
If you state MW, identify IT load, facility load or grid connection need. Use unknown if it is not defined.
Distinguish a preferred date from a confirmed statement. State what the date refers to.
Separate conditions that must be met from preferences that can be discussed.
Name documents, dates and who can provide them. Summarise without sensitive contractual details.
Describe the roles involved, open questions and what the next delivery should enable.
Powered Sites · Requirements brief Your working draft · not reviewed by Powered Sites Version and date Not provided / unknown What decision do you need to make? Not provided / unknown Geography and location Not provided / unknown Load and phases Not provided / unknown Timing and milestone Not provided / unknown Hard requirements and preferences Not provided / unknown Available evidence Not provided / unknown Responsibilities and next steps Not provided / unknown
How an initial brief can be written
Synthetic example — not a real project
- Decision
- Decide whether a search across two possible regions is defined well enough to commission.
- Requirements and preferences
- Requirement: scope for phased development. Preference: proximity to the operations team. Acceptable travel time and future power needs are not yet defined.
- Open question and next step
- The project team needs to define the load type and the meaning of its target date before candidates can be compared against consistent requirements.
Check the brief before sharing
- Decision and role — what decision should the file support, and who is commissioning it?
- Location and scale — geography, land or building, and approximate extent.
- Load and stages — IT load, facility load or connection need; first and later stage.
- Timing — month or range, what milestone the date refers to, and whether it is a preference or requirement.
- Requirements — hard requirements kept separate from preferences.
- Evidence and interfaces — what exists, what confidentiality level applies, and which external roles are involved.
- Next decision — what should be decidable after the first delivery?
Give the brief a version number and date. The form does not automatically send this page.