Colocation evaluation checklist

Download the comparison worksheet

Download the free colocation comparison CSV. Open it in your spreadsheet, duplicate the provider columns as needed, and keep written evidence alongside each response. No registration required.

This worksheet structures your evaluation. It does not certify a facility or replace your technical, security and contract reviews.

1. Define the deployment before requesting quotes

Give each provider the same starting brief. Include rack count, equipment dimensions and weight, expected load per rack, growth allowance, target date and locations you can accept. Separate what must be available at move-in from what you might need later.

• List the equipment configuration and the expected operating load, with the assumptions behind it.
• Identify the applications, networks and users that constrain location or latency.
• State the installation sequence, delivery access needs and who will perform the work.
• Record must-have requirements separately from preferences.

2. Confirm the power and cooling offered to your racks

Ask for the power allocation and cooling capability of the proposed cabinet, cage or suite. A campus-wide capability does not establish what is available in your assigned space.

• Document the included power commitment, billing method, available feeds and usable capacity during the agreed failure scenario.
• Ask who provides the PDUs, cabling and any required distribution upgrades.
• For dense equipment, request written confirmation of the supported configuration and cooling design.
• For liquid-cooled systems, identify the facility and customer responsibilities for connections, fluid requirements, maintenance and leak response.
• Record what is already installed, what needs construction, and which dates are contractual.

3. Verify connectivity and access

List the carriers and cloud connections you need. Confirm service availability at the specific facility, then identify cross-connect charges, installation lead times and the parties responsible for each segment.

If diverse paths matter, ask for evidence of the proposed routes and common dependencies. Count the actual paths serving the deployment, not the number of provider logos. Confirm building entry, equipment delivery, visitor approval and emergency access procedures.

4. Establish operating responsibilities

Define who monitors, who responds and who has authority to act. Ask for remote-hands coverage, rates, minimum charges, escalation contacts and examples of work that is excluded.

Request the evidence your security team needs for the service in scope, including the applicable report period and exclusions. Review incident communication, maintenance notices, recovery responsibilities and any dependencies you must operate yourself.

5. Normalize the commercial comparison

Compare the same rack count, power assumptions, connectivity, support scope and contract length. Separate monthly commitments, metered charges, one-time work and renewal changes. The colocation cost guide gives a simple comparison method.

Record the delivery commitment, reservation conditions, expansion rights, notice dates and exit responsibilities. An unanswered item belongs in the open-questions column, not in an assumed allowance.

6. Resolve the gaps before selecting the site

Ask each provider to confirm its responses in writing. Assign an owner to every unresolved requirement, and record who accepts any remaining exception. Keep the final responses with the order and agreed scope.

For an operator shortlist, send ColoHunter your deployment brief. If the facility move also involves cloud or network changes, our parent company offers NexusLink infrastructure advisory.

Put the brief to work.

Tell us what you need to deploy.