Most colocation agreements start life as a customer’s redlines against whatever template the operator first sent out, which means the operator’s own protections often end up defined reactively, clause by clause, in response to what a particular enterprise customer pushed back on. A standard agreement built deliberately around the operator’s own risk position, rather than assembled from accumulated concessions, protects margin and limits exposure in ways a reactive one rarely does.
Size your liability cap to what you can actually insure
A liability cap set at a multiple of monthly fees is standard practice, but it should be set with your actual insurance programme in mind, not chosen arbitrarily and then hoped to be defensible later. A cap your insurer will not actually indemnify you for is not a real protection, it is a promise you cannot necessarily keep. Carve-outs are unavoidable, customers will reasonably expect your own gross negligence and wilful default excluded from the cap, but the carve-outs should be drafted narrowly and specifically, not left open-ended in a way that could be read to swallow the cap entirely in an ordinary service dispute.
Require the customer to insure their own equipment
Your property insurance covers your building and your infrastructure. It does not, and should not be assumed to, cover a customer’s servers sitting in your racks. A standard colocation agreement should expressly require the customer to maintain their own equipment insurance and, ideally, to name you as an additional interested party or to waive subrogation against you, so an insurer does not later pursue you for a loss the customer’s own policy was meant to cover. Silence on this point is not neutral, it defaults to an argument about whose insurance should have responded, conducted after a loss has already happened rather than settled in advance.
Scope your data protection role precisely, and no further
Where a customer processes personal data on equipment in your facility, you are very likely a data processor or sub-processor under section 42 of the Data Protection Act, and the written contract the Act requires should say exactly that, no more. Resist contract language that describes your role in broader terms than you actually control, since a clause that casts you as jointly responsible for the customer’s own processing decisions can expose you to liability for choices you had no part in making. Be equally precise about section 43 breach notification: your obligation is to notify the customer promptly of a security incident affecting their equipment, not to independently assess or notify the Data Commissioner on the customer’s behalf for a breach of data you were never the controller of.
Build exit terms that do not leave you holding abandoned equipment
A defined exit process protects you as much as the customer: a fixed notice period, a defined window for the customer to remove their equipment, and a clear right to charge storage fees, and eventually dispose of equipment consistent with your own data destruction obligations, where a customer simply disappears or disputes a final invoice rather than completing an orderly exit. Without this, an operator can end up holding a former customer’s servers indefinitely, unable to reclaim the rack space and unable to safely dispose of equipment that may still hold that customer’s data.
Keep audit and access rights proportionate
Enterprise customers, particularly regulated ones, will often want audit rights over your facility’s security and compliance posture. These are reasonable in principle but need boundaries: reasonable notice, a capped frequency, confidentiality over what an audit reveals about your other customers, and a mechanism to satisfy the request through an independent certification or report rather than an open-ended physical inspection every customer can separately demand on their own schedule.
Building the template once, properly
A colocation agreement built around these points from the outset still gets negotiated, enterprise customers will always push on liability caps and service credits. What changes is the starting position: an operator negotiating from a deliberately constructed template concedes specific, considered points, rather than discovering the gaps in an ad hoc document one customer dispute at a time.
