Use one site alias and one row per phase.
Use a site alias and metro for an initial reply. Identify the responding role and the response date. If a second facility is an option, give it a separate reply so the buyer can assess any same-site requirement.
For each block, give the incremental rack count, usable IT kW, supported peak kW per rack, cooling method and earliest usable date. If the buyer’s rack layout or cooling arrangement needs engineering review, say what you still need to confirm.
Give the basis for each power date.
- Tested
- Describe the work already completed, when it was verified and what load it supports. Identify any limits on handover.
- Forecast
- State the expected date, the unfinished milestone, the role responsible for confirming it and when the buyer can expect a dated update.
- Unknown
- Say which answer is unavailable. Give a next review date if one is known, or say when the question can be reopened.
Explain what would hold the capacity.
State whether the block can currently be offered, whether both phases can be provided at this facility and what approval would reserve them. Include any deadline or condition on a hold. If commercial terms are open, leave them open in the reply.
A working date can help the buyer plan even while a quote is pending. Clearly identify who can issue the quote and who can verify the technical date.
A written reply the buyer can compare.
Phoenix metro, site A. Response dated 12 March 2027. We expect to support the first 15 air-cooled racks at 20 kW each on 1 June. The additional 300 kW at this site is forecast for 15 October, subject to switchgear commissioning. Our commissioning lead will confirm the date basis by 19 March. Reservation terms remain open.
Illustrative operator reply
Use the buyer guide to see how a deployment team can describe a fixed deadline. The sample brief shows how the dates above affect that team’s decision.