Not every unusual clause in an MSP agreement is a problem — some asymmetry is normal in any commercial contract. But a handful of patterns turn up often enough in published managed-IT agreements, and cost clients real money often enough, that they are worth specifically checking for before you sign. This guide covers the ones we see most, in plain language, with what to look for in your own document.
One-sided termination rights
Look for a "termination for convenience" clause — the right to end the agreement without cause, on notice, for any reason. The red flag is not that this right exists; it is that it sometimes exists for only one party. In published contracts, this shows up as the provider reserving a convenience-termination right to itself with no matching right given to the client. A balanced version of the same clause lets both parties end the agreement for convenience on the same notice — check whether yours does.
A related pattern: some agreements let the provider terminate if you decline a recommended security upgrade or service change, with no equivalent right running the other way if the provider declines something you ask for.
Stacked exit fees
Read the termination section for how many distinct charges apply when you leave, not just whether a fee exists. Two separate and stackable charges are common: an early-termination fee (frequently calculated as the fees that would have been due for the rest of the term, sometimes plus unrecovered setup or onboarding costs) and a separate off-boarding or data-transition charge, billed at the provider's rates in effect at the time — often with no ceiling or advance quote given in the contract itself. See our data-return guide for what to check specifically about getting your own data back.
Also check whether the termination fee applies even when you are terminating because the provider breached the agreement. In a contract structured evenly, a client terminating for the provider's uncured breach should not owe the same exit fee as a client leaving for convenience — but not every published contract makes that distinction.
Short or one-sided cure periods
A "cure period" is the time you (or the provider) has to fix a breach before the other side can terminate for it. Thirty days is a common benchmark in published contracts; shorter periods do appear — as little as five business days in at least one published agreement. Check whether the cure period is the same length for both parties' breaches, or whether the provider gets more time to fix its own failures than you get to fix yours.
Renewal terms set by someone else
Some agreements incorporate a third party's terms by reference — commonly for software licensing or a subcontracted service — and state that those terms can change unilaterally, without notice to you, and that you are bound by them anyway. A specific version of this appears in at least one published contract as an explicit pass-through: the vendor's own auto-renewal policy applies to you, and the MSP is not liable for charges that result. If your contract references a third party's terms, get a copy of those terms too — "as amended from time to time" is not something you can verify by reading only the MSP agreement.
Liability that only runs one direction
Limitation-of-liability and indemnity clauses are close reading, and worth their own guide — see what a liability cap really means. As a quick check here: look for whether consequential, indirect, or lost-profit damages are waived against the provider only, with no matching waiver running the other way, and whether an insurance or indemnity obligation is placed on you without a corresponding one on the provider.
Indemnity and insurance obligations placed only on you
Some agreements require the client to carry a specific level of cyber-liability or general-liability insurance, and to indemnify the provider for a range of claims, without imposing any equivalent obligation on the provider itself. Check whether the contract states what coverage, if any, the provider carries — a contract that requires you to insure against a risk while saying nothing about the provider's own coverage for the same category of loss is worth reading closely, especially if that same indemnity is not itself brought inside the liability cap discussed in our companion guide.
Vague service levels with no consequence for missing them
A services agreement may describe response times or uptime targets in marketing language elsewhere while the actual contract contains no enforceable service-level commitment, or no termination right tied to repeatedly missing one. If the only consequence for a missed target is an apology, that is worth knowing before you sign, not after the third outage. Look specifically for whether repeated failure to meet a stated service target gives you any right at all — a credit, an escalation path, or a termination right — or whether the target is aspirational language with nothing behind it.
How to use this list
None of these patterns automatically make a contract unfair or unusual for the industry — commercial contracts are negotiated documents, and a provider is entitled to protect its own position. The point of this list is narrower: know which of these patterns your specific contract contains, in its actual language, before you sign or before the renewal window closes, so you can decide whether to accept it, negotiate it, or take it to an attorney. Reading a 20- or 40-page agreement start to finish looking for six different patterns is slow and easy to get wrong under time pressure — which is exactly the situation most business owners are in when a renewal notice window is closing in a matter of days.
Check your own contract against this list
TermSentinel reads an uploaded MSP agreement against a published rule set covering these patterns — termination rights, exit fees, cure periods, and liability terms — and quotes the exact contract language next to each finding it makes.