Scope of Services
Describe physical space (rack, cabinet, caged area), power allocations (amps and redundancy), cross-connects, remote-hands tasks, and any managed-services inclusions so each deliverable is unambiguous.
A well-drafted Business COLO Document reduces operational risk by assigning responsibilities for equipment custody, uptime guarantees, and security, and by making billing and escalation procedures explicit.
Businesses and providers use the COLO document to define obligations, protect assets, and set operational SLAs before equipment is colocated.
The document serves legal, technical, and financial stakeholders to reduce disputes and speed provisioning of colocation services.
The IT Director or Infrastructure Manager signs to confirm technical requirements (rack units, power draw, cross-connects) and to accept service-level commitments, ensuring the facility can meet continuity and performance needs.
A corporate signatory (CFO, VP of Procurement, or authorized officer) signs for financial and legal acceptance of billing, liability caps, insurance requirements, and termination clauses on behalf of the business.
Describe physical space (rack, cabinet, caged area), power allocations (amps and redundancy), cross-connects, remote-hands tasks, and any managed-services inclusions so each deliverable is unambiguous.
Specify uptime targets, response and restoration times, credits or remedies for SLA breaches, and monitoring responsibilities to align operational expectations and escalation pathways.
Document physical access procedures, on-site badge or escort policies, visitor logs, video surveillance, and data center personnel responsibilities for maintaining chain-of-custody and facility security.
Itemize recurring fees (space, power, network), one-time installation charges, taxes, invoicing cadence, payment terms, and late-payment consequences to prevent billing disputes.
Set mutual liability caps, indemnities, required insurance types and limits, and procedures for damage claims to allocate risk and reduce litigation exposure.
Define initial term, auto-renewal conditions, early-termination fees, notice periods, and post-termination migration assistance required to avoid service interruptions.
| Field | Configuration |
|---|---|
| Signer Order | Sequential: Legal → Finance → IT |
| Authentication | Email + SMS code for critical signers |
| Conditional Fields | Show power details only if managed-power selected |
| Attachments | Allow upload: rack diagrams, insurance certificates |
Confirm the eSignature platform supports required file formats, integrations, and authentication methods before sending the COLO document.
Ensure the chosen provider can export signed PDFs with an immutable audit trail and supports any compliance needs such as HIPAA or 21 CFR Part 11 where applicable.
Signatures obtained and fully executed agreement stored
Provider confirms rack space, power, and install date
Cross-connects and IP assignments completed
Equipment racked, powered, and tested
Net 30 from invoice date
Typically 5–10 business days after execution
Provider gives 48–72 hours for scheduled maintenance
Critical incidents: initial response within 4 hours
30–90 days depending on contract clause
Tim Martin reduced turnaround on facility agreements by moving signing online and keeping mobile access intact.
Dan Rotelli selected a compliant eSignature workflow to preserve SOC 2 evidence and audit trails.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |