Premises
Describe the physical footprint (rack units, cage, suite), exact rack IDs or coordinates, and any reserved common areas that affect access or installation responsibilities.
A well-drafted Colocation Lease Agreement reduces disputes, clarifies operational responsibilities, and aligns expectations on availability, physical access, and data protection. It also documents payment, termination, and liability terms so both landlord and tenant can manage financial and compliance risk during the hosting relationship.
Several parties are commonly involved in preparing, reviewing, and signing a colocation lease, depending on the organization and the transaction size.
In larger transactions, security, compliance, and executive signatories may also be required to finalize the agreement.
A tenant IT or infrastructure lead signs to confirm technical specifications, rack layout, space, power, and service-level requirements. Their signature affirms the facility can meet cooling, power, and cross-connect expectations and documents accepted installation responsibilities.
A corporate officer or procurement representative signs on behalf of the tenant to bind the company to rent, indemnity, insurance, and payment obligations. This signatory confirms commercial terms and legal authority to enter the lease.
Describe the physical footprint (rack units, cage, suite), exact rack IDs or coordinates, and any reserved common areas that affect access or installation responsibilities.
Specify power allotments, redundancy, meters, transfer procedures, and allowed equipment heat loads plus cooling guarantees and remedies for outages.
Define access hours, credentials, visitor escort policies, background checks, and monitoring or badge requirements for on-site or remote access.
Set uptime targets for power, network, and environmental systems, measurement methods, reporting cadence, and credit or termination remedies for breaches.
State the initial term, renewal options, notice periods, early termination rights, and conditions for surrender or removal of tenant equipment.
Allocate risk for damage, loss, and data incidents; list required insurance types and limits and any indemnity or limitation of liability clauses.
| Field | Configuration |
|---|---|
| Signer Order | Tenant legal rep → IT approver → Landlord representative |
| Authentication | Email link plus optional SMS code for sensitive signers |
| Template Use | Create template for recurring colocation rows and pricing |
| Notifications | Send reminders at 3 and 1 days before due date |
Ensure the signing platform supports secure audit trails, authentication, and integrations needed for operational handoffs.
Use a platform that preserves an immutable audit trail and exports signed PDFs for legal and operational use.
| 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 | Yes, 7-day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Optica migrated customer infrastructure into third-party facilities using executed leases to govern access and power
A regional operator used online execution for multiple small-tenant colocation contracts