Colocation Services Addendum
What the Colocation Services Addendum Is
Why a Clear Addendum Matters
A precise Colocation Services Addendum reduces ambiguity about responsibilities, billing, and technical requirements, minimizing disputes and operational downtime. It documents agreed changes, preserves the continuity of the master agreement, and creates a clear audit trail for accounting, compliance, and future audits.
Who Typically Prepares and Signs This Addendum
The document is used by parties responsible for facilities, IT operations, contract management, and procurement who must formalize changes to colocation services.
- Data center operators and account managers who must record rack, power, or connectivity changes and maintain service records.
- Enterprise IT and infrastructure teams that request capacity changes, relocations, or new service levels and need formal acceptance.
- Legal and procurement professionals who review commercial terms, liability allocations, and billing adjustments before execution.
Ensure the signatories have authority to bind their organizations and that technical exhibits are attached to avoid later disputes.
Step-by-step: Completing the Addendum
-
01Identify the change: State the specific modification (e.g., additional cabinet, increased power, new cross-connect).
-
02Reference master agreement: Cite master contract title, date, and reference section to link the addendum.
-
03Attach technical exhibits: Include rack diagrams, power schedules, IP addressing, and acceptance criteria.
-
04Obtain authorized signatures: Have authorized reps sign, date, and include printed names and titles.
How to Configure an Online Completion Workflow
| Field | Configuration |
|---|---|
| Document Upload | Upload PDF/X or DOCX and attach exhibits as separate files |
| Signer Order | Define sequential or parallel signing roles (legal, ops, finance) |
| Authentication | Use email link plus optional SMS or KBA for higher assurance |
| Audit Trail | Enable full event logging (timestamps, IP, action history) |
Technical Considerations for eSigning and Integration
Choose a platform that supports your compliance needs, preserves exhibits, and integrates with procurement or ticketing systems.
- File formats: PDF and DOCX support
- Integrations: CRM, ERP, cloud storage
- Authentication: Email, SMS, enterprise SSO
Ensure the chosen platform stores a tamper-evident copy and audit trail and that it can export signed bundles for your records management system.
Typical Electronic Execution Flow
-
Prepare document: Upload addendum and attach technical exhibits.
-
Place fields: Add signature, date, and initial fields and any conditional fields.
-
Route to signers: Specify signer emails and signing order or generate a secure link.
-
Complete and archive: Signed package and audit trail saved, distributed to stakeholders.
Timing, Deadlines, and Processing Expectations
Effective Date:
Use the specified MM/DD/YYYY in the addendum to govern start of changes.
Billing Proration:
Define whether fees are prorated and the billing cycle affected.
Notice Periods:
Respect any required advance notices in the master agreement.
Implementation Window:
Specify operations lead time for rack moves or power changes.
Retention of Signed Copy:
Store executed addendum with exhibits for audit and dispute resolution.
Common Preparation Errors to Avoid
- Failing to attach updated technical exhibits or rack diagrams, causing scope disputes during implementation.
- Using inconsistent party names or omitting the master agreement reference, which can create enforceability questions.
- Leaving pricing or billing mechanics vague, producing unexpected charges or invoicing disputes.
- Not confirming signer authority, which can result in a voidable or contested amendment.
Consequences of an Incorrect or Incomplete Addendum
eSignature Vendor Comparison for Executing Addenda
| 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 | Verify with vendor | Verify with vendor | Verify with vendor | Verify with vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
Real-world Use Examples
Data Center Capacity Increase
A midmarket SaaS provider needed three additional cabinets and higher power per rack
- The addendum specified kW per rack and a prorated fee
- The signed addendum plus rack diagram prevented billing disputes and guided the data center technician during implementation.
Cross-Connect and IP Allocation
An enterprise required multiple new cross-connects and updated BGP peering details
- The addendum attached a network exhibit and acceptance test plan
- Clear acceptance criteria reduced provisioning time and avoided recurring network configuration disagreements.
Frequently Asked Questions
-
Can this addendum be signed electronically?
Yes. Under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA (adopted by most states), electronic signatures are generally enforceable if intent, consent, attribution, and reliable record retention are present.
-
When is notarization required?
Most commercial contract addenda do not require notarization. Notarization becomes necessary only if the master agreement or state law specifically requires it, or if a party requests a notarized acknowledgement for recordation.
-
What authentication level is appropriate?
Email link authentication suffices for many commercial amendments, but use stronger methods (SMS, SSO, KBA) for higher-risk changes or when regulatory compliance demands stronger signer identity proofing.
-
How should exhibits be handled electronically?
Attach technical exhibits as separate, versioned files and reference them by exhibit ID and date inside the addendum; ensure the signing platform bundles exhibits with the executed copy for auditability.
-
Who should review the addendum before signing?
Legal should confirm contract language and liability limits, operations should verify technical feasibility, and finance should confirm billing mechanics prior to execution.
-
How long to retain signed addenda?
Retain executed addenda for the agreement term plus at least 3 years; if subject to HIPAA or SEC rules, follow the specific statutory retention periods cited by those regulations.