Establishing secure connection…Loading editor…Preparing document…

Co-location Service Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

CO-LOCATION SERVICE AGREEMENT

This Co-location Service Agreement (the "Agreement") is entered into as of by and between:

Provider Name:

Provider Address:

Client Name:

Client Address:

WHEREAS

WHEREAS, Provider owns and operates a secure co-location facility and offers rack space, power, network cross-connects, and physical security services suitable for hosting Customer equipment; and

WHEREAS, Client desires to place certain telecommunications and/or information technology equipment within Provider's facility and to receive ancillary services under the terms set forth herein; and

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows:

1. SCOPE OF SERVICES

Services to be provided include but are not limited to provision of rack or cabinet space, designated power circuits, network cross-connects as ordered, physical security and access control, environmental monitoring, and remote-hands assistance in accordance with this Agreement and any applicable Service Order.

2. PAYMENT TERMS

Client shall pay all fees in accordance with the schedule set forth above. All payments are due net as specified; unpaid amounts shall accrue interest at the rate specified for late payment and Provider may suspend services for nonpayment after prior written notice in accordance with Section 5.

3. TERM AND TERMINATION

Term Start Date:

Term End Date:

Either party may terminate this Agreement for cause if the other party materially breaches any obligation under this Agreement and fails to cure such breach within the notice period specified above. Provider may immediately terminate or suspend services if Client presents a material safety, security or regulatory risk, subject to Provider's reasonable documentation of such risk.

4. CONFIDENTIALITY

"Confidential Information" means all non-public information disclosed by one party to the other in connection with this Agreement, whether written, oral or electronic. Each party shall maintain the confidentiality of the other party's Confidential Information using at least the same degree of care it uses to protect its own confidential information, and shall not use or disclose such information except as necessary to perform under this Agreement or as required by law.

Confidential Information shall not include information that is or becomes publicly known through no breach of this Agreement, is rightfully received from a third party without restriction, or is independently developed by the receiving party without use of the disclosing party's Confidential Information.

5. ACCESS, SECURITY AND FACILITY OPERATIONS

Provider will maintain reasonable physical security, access control, environmental controls and monitoring at the facility. Client shall provide a list of authorized personnel and shall ensure that all equipment installed complies with Provider's reasonable facility rules and applicable law. Provider may, upon prior notice except in emergency, restrict or deny access where necessary for safety, compliance or to perform maintenance.

6. LIABILITY, INDEMNITY AND INSURANCE

Except for gross negligence or willful misconduct, neither party shall be liable to the other for special, incidental, indirect or consequential damages, including loss of business, revenue or data. The aggregate liability of Provider for claims arising out of or related to this Agreement shall be limited to the greater of the fees paid by Client to Provider under this Agreement in the twelve (12) months preceding the claim or $ .

Client shall indemnify and hold Provider harmless from claims arising from Client's equipment, content, or use of the services, except to the extent caused by Provider's gross negligence or willful misconduct.

7. COMPLIANCE WITH LAWS

Each party shall comply with all applicable laws, regulations and codes in the performance of its obligations. Client is responsible for ensuring that its equipment and operations comply with all applicable environmental, safety and telecommunications requirements.

8. NOTICES

9. GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by and construed in accordance with the laws of without regard to choice of law principles. Any dispute arising out of or relating to this Agreement shall be resolved by binding arbitration or in the state and federal courts located in the county of the Provider's principal facility, at Provider's election. The prevailing party shall be entitled to recover reasonable attorneys' fees and costs.

10. ASSIGNMENT; AMENDMENT

Neither party may assign this Agreement without the prior written consent of the other party, except that Provider may assign or subcontract its rights and obligations in connection with a sale of all or substantially all of Provider's assets. Any modification or amendment to this Agreement must be in writing and signed by authorized representatives of both parties.

11. ENTIRE AGREEMENT

This Agreement, together with any Service Orders and attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or representations, whether written or oral, relating to such subject matter.

12. MISCELLANEOUS

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions will remain in full force and effect. The parties are independent contractors and nothing in this Agreement creates an agency, partnership or joint venture between them.

Provider Printed Name:

By:

Date:

Client Printed Name:

By:

Date:

Enter text✕

What a Co-location Service Agreement Covers

A Co-location Service Agreement is a written contract that defines the relationship between a colocation provider and a customer who places servers or other IT equipment in a provider facility. It specifies services such as rack space, power and cooling allocations, network connectivity, physical and logical security, access policies, service levels, maintenance responsibilities, billing and payment terms, liability limits, insurance requirements, and termination procedures. The agreement clarifies ownership of equipment, migration windows and handover tasks, and typically includes provisions for audits, data protection, and dispute resolution to reduce operational and legal ambiguity.

Why a Clear Agreement Matters for Colocation

A well-drafted Co-location Service Agreement allocates operational responsibilities, quantifies service levels and remedies, and documents security and compliance commitments. This reduces operational downtime risk, supports regulatory compliance, and makes pricing and termination predictable for both parties.

Why a Clear Agreement Matters for Colocation

Who Typically Prepares or Signs This Agreement

The agreement is used by technical and commercial stakeholders at both provider and customer organizations before equipment installation and recurring billing begins.

  • Data center operators and account teams use the agreement to define rack, power, and access rules for customers and carriers.
  • Enterprise IT departments and cloud architects use the agreement to document uptime expectations, connectivity options, and migration timelines.
  • Managed service providers and systems integrators sign to establish custody, service responsibilities, and pass-through billing for hosted customer equipment.

Typical signers include authorized business representatives, technical contacts for operations, and legal counsel for any negotiated liability, insurance, or confidentiality terms.

Representative Signers and Their Roles

VP of Infrastructure

Responsible for operational requirements, capacity planning, and approving technical addenda. Reviews SLA metrics, power allocation, and access control clauses to ensure compatibility with enterprise standards.

Provider Contracts Manager

Manages commercial terms, billing cycles, and termination clauses. Coordinates RMA, maintenance scheduling, and escalation pathways with legal and operations teams to reduce dispute risk.

Essential Information to Include

Customer Name: Legal entity name
Facility Address: Physical colocation site
Equipment List: Rack/serial identifiers
Power Requirements: kW or kVA per rack
Primary Contact: Name, email, phone
SLA Tier: Uptime and remedy tier

Top Risks and Contractual Consequences

Service Interruption: Lost availability exposure
Data Breach: Regulatory fines possible
Misrouted Liability: Coverage disputes with insurer
Late Payment: Termination and fees
Unapproved Work: Access revocation risk
Incorrect TIN: Backup withholding triggers

Common Preparation Errors to Avoid

  • Failing to list equipment serial numbers and rack units, which complicates warranty and recovery actions during hardware replacement.
  • Leaving SLA remedies vague or uncapped, producing disagreement after an outage about credits or service restoration obligations.
  • Not aligning power and cooling requirements with the provider’s available capacity, creating risk of forced migration or additional charges.
  • Neglecting to document access windows and escort requirements, leading to denied access during critical maintenance or emergency response.

Key Clauses Every Professional Agreement Should Contain

A complete Co-location Service Agreement organizes core obligations into distinct clauses so both parties can measure performance and act on exceptions.

Term & Termination

Defines initial term, renewal options, early termination rights, and post-termination cooperation for equipment removal and data retention to avoid stranded assets and unexpected costs.

Service Levels

Specifies uptime percentage, scheduled maintenance windows, incident response times, and credit formulas for missed SLAs so expectations and remedies are clear.

Security & Access

Covers physical controls, badge policies, escort rules, remote hands procedures, and audit rights to meet compliance and limit unauthorized access.

Power & Cooling

Allocates power, breakers, and redundant feeds; describes metering, overage rates, and procedures for power faults to protect equipment and manage costs.

Maintenance & Repairs

Details patching, hardware replacement, provider-performed tasks, scheduling, and liability for maintenance-caused outages to reduce confusion during support events.

Pricing & Billing

Lists recurring and one-time fees, payment terms, tax treatment, dispute resolution for invoicing, and conditions that trigger rate changes or additional charges.

Step-by-Step: Preparing and Signing the Agreement

Follow these steps to move from draft to executed agreement with clear technical and commercial acceptance by both parties.

  • 01
    Draft Terms: Assemble clauses and technical addenda.
  • 02
    Complete Fields: Fill legal names, addresses, equipment lists.
  • 03
    Internal Review: Operations and legal approve changes.
  • 04
    Execute Document: Sign, date, and distribute executed copies.

Configuring an Online Signing Workflow

Set up a repeatable electronic workflow that enforces required fields, authentication, and retention policies for signed agreements.

Field Configuration | Notes
Notifications Email and SMS alerts | Track signers
Authentication Email link or SMS code | Optional KBA
Template Reusable template | Preserve clause consistency
Retention Preserve signed PDF/A | Include audit trail

Where to Send and How Execution Occurs

Execution typically moves from the drafting party to signers and then to archival storage; the sequence below maps the common routing steps.

  • Upload Document: Sender uploads final agreement.
  • Place Fields: Add signature, date, and initial fields.
  • Send to Signers: Distribute by email or secure link.
  • Archive Executed Copy: Store signed PDF with audit trail.

Technology and Format Considerations for eSigning

Choose a platform that supports required authentication, integrations, and file formats used for colocation contracts.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File Formats: PDF, DOCX, HTML, Excel
  • Authentication: Email link, SMS code, SSO

Ensure the chosen system preserves an immutable audit trail, provides secure storage with AES-256 encryption at rest and TLS in transit, and supports export of signed documents in standard PDF/A format for retention and legal reproducibility.

Typical Timelines and Notice Periods

Colocation agreements include several time-sensitive milestones; record them clearly to avoid operational or billing disputes.

Negotiation Window:

30–60 days for commercial and technical approval.

Effective Date:

Date entered in Effective Date field starts obligations.

Migration Window:

Typically 14–90 days for equipment move-in.

Billing Cycle Start:

Begins on Effective Date or first day of next month.

Termination Notice:

30–90 days depending on contract clause.

How This Agreement Differs from Similar Contract Types

Compare common contract types to confirm whether a dedicated colocation agreement, a lease, or a master services agreement best fits the business relationship.

Criteria Co-location Agreement Lease Agreement
Purpose asset hosting real property occupancy
Term Flexibility narrow technical terms broader real-estate terms
SLA Included typically no
Equipment Ownership customer-owned tenant-owned or installed

eSignature Vendor Pricing Snapshot for Contract Execution

Common eSignature vendors and core plan characteristics for executing colocation agreements. Pricing reflects published entry-level plans and common plan features.

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 free trial, no card required Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Yes Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year limit Varies by plan Varies by plan Varies by plan

Real-World Examples of Electronic Execution

Organizations of different sizes use eSignature to accelerate colocation onboarding, reduce in-person handoffs, and centralize executed agreements.

Optica Ventures (Brian Fitzgibbons)

A data-center operator used electronic signatures to speed contract turnaround and reduce in-person meetings.

  • Carrier onboarding accelerated across markets.
  • Brian Fitzgibbons, COO, Optica Ventures LLC: "The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Martin Properties (Tim Martin)

A small colocation provider replaced paper routing with digital workflows to centralize executed contracts and billing.

  • Migration windows adhered to reliably.
  • Tim Martin, Founder, Martin Properties: "I can process and execute all of these documents online with 100% compliance and built-in security."

Practical Tips for Accurate, Efficient Completion

Adopt consistent procedures and review checkpoints so contracts are both enforceable and operationally actionable.

Standardize Templates
Use a single master template with configurable annexes for power, connectivity, and security. Standardization reduces negotiation time, keeps SLA language consistent, and speeds approvals across repeat customers.
Validate Technical Data
Have operations verify power and cooling entries, rack assignments, and serial numbers before signing. Technical validation prevents post‑execution disputes and unplanned migration costs.
Document Access Procedures
Record badging, escort requirements, and after-hours access policies inside the agreement or an exhibit. Clear access rules reduce denied‑entry incidents and speed emergency responses.
Preserve Audit Trails
Keep signed PDFs with embedded audit trails and timestamps. Retain exports in PDF/A for legal reproducibility and to support regulatory or insurance claims if incidents occur.

Frequently Asked Questions About Co-location Service Agreements

Answers to common questions about signing, notarization, security, and amendments for colocation contracts using electronic workflows.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users