Guide

What to check in an IT services or MSP contract before you sign or renew

A plain-language checklist for small-business owners: scope, pricing, renewals, liability, data return, admin access, and offboarding in an IT or MSP contract.

TermSentinel is not a law firm. This is not legal advice, and using this page or the product does not create an attorney-client relationship. Nothing here predicts how a court would rule on your specific contract. Before you sign or terminate anything, have a licensed attorney in your state review it.

Most owners skim the price page and the renewal date. The parts that actually cause trouble later are scattered through the rest of the agreement: who owns your cloud accounts, what happens to your data when you leave, how fast prices can rise, and whether you can get your systems back without a fight.

This guide walks through the main sections of a typical IT services or managed service provider (MSP) contract. Use it before you sign a new deal, or a few months before an existing one renews. It is not legal advice. It is a practical checklist so you know what to ask.

1. Scope of work and service levels

What to look for: A clear list of what is included (help desk hours, monitoring, patching, backups, on-site visits) and what is not. Vague phrases like "best effort" or "industry standard" leave room for disagreement when something breaks.

Also check the service-level agreement (SLA): response times by severity, how downtime is measured, and what credit you get if they miss a target.

Ask the provider: "Can you show me, in writing, which tickets are covered, how fast you respond by priority, and what credit applies if you miss an SLA?"

2. Pricing and escalators

What to look for: The base monthly or annual fee, what drives extra charges (after-hours work, new devices, project work), and any automatic price increases. Many agreements allow a yearly bump tied to an index or a fixed percentage, sometimes with little notice.

Watch for "pass-through" fees for Microsoft 365, security tools, or cloud licenses. Confirm whether those markups can change mid-term.

Ask the provider: "What can increase my bill without a new quote, and how much notice do I get before a price change?"

3. Term, renewal, and notice dates

What to look for: The initial term length, whether the contract auto-renews, and the notice deadline—often 30, 60, or 90 days before the renewal date. Missing that window can lock you into another full term.

Also check how notice must be delivered (email to a named address, certified mail, portal form). A calendar reminder for the renewal date is not enough if the notice date is earlier.

Ask the provider: "What is the exact non-renewal notice deadline, and which delivery method counts?"

4. Termination and early-exit fees

What to look for: Whether you can leave for convenience, only for cause, or not at all until the term ends. Early termination fees are common; some equal several months of fees, or the remaining contract value.

Also note any "cure" period: if they breach, how long they have to fix it before you can exit without a fee.

Ask the provider: "If we need to leave early, what fee applies, and is there a step-down after year one?"

5. Liability caps and indemnity

What to look for: A liability cap that often limits their exposure to a few months of fees, even if a mistake costs you far more. Indemnity language decides who pays if a third party sues over something in the services.

Read both directions: what they cover for you, and what you are asked to cover for them. Extremely one-sided caps are common in MSP templates and are often negotiable before you sign.

Ask the provider: "Can the liability cap be raised for data loss or security incidents caused by your team?"

6. Data return and deletion

What to look for: What happens to your backups, ticket history, documentation, and configuration data when the relationship ends. Some contracts say data is deleted after 30 days. Others only return files if your account is "current."

Get the format, timeline, and who pays for the export in writing. "We'll help with transition" is not the same as a defined data-return clause.

Ask the provider: "In what format and within how many days will you return our data, backups, and documentation after termination?"

7. Admin access and tenant ownership

What to look for: Who owns your Microsoft 365 (or Google Workspace) tenant, domain registrar, DNS, and firewall admin accounts. If the provider is the only global admin, switching firms later can turn into a hostage situation.

You should be able to hold a break-glass or owner-level account in your own name, with their tools as additional access—not the reverse.

Ask the provider: "Will we hold Global Admin (or equivalent) on our own tenant, and can we revoke your access without your help?"

8. Offboarding and handover

What to look for: A written offboarding process: who hands over credentials, runbooks, diagrams, vendor contacts, and monitoring tools, and how many days they have to do it. Blank or missing offboarding sections are a red flag.

Some agreements bill offboarding as a project; that can be fair if the scope and price are clear up front.

Ask the provider: "What does a clean handover include, how long does it take, and is there a fixed fee or hourly rate?"

9. Security responsibilities

What to look for: A split of duties. Who patches servers, who owns endpoint protection, who responds to incidents, and who is responsible if a phishing email leads to a breach.

If the contract is silent, you may assume they cover something they do not. Ask for a short RACI-style list (responsible / accountable) for backups, MFA, logging, and incident response.

Ask the provider: "Which security controls are your responsibility, and which stay with us?"

10. Changes to terms

What to look for: Whether they can update the agreement by posting a new version online, or only with your signed consent. Online-only changes can quietly rewrite pricing, SLAs, or data terms mid-relationship.

Prefer language that requires written agreement for material changes, or at least advance notice with a right to exit if you disagree.

Ask the provider: "Can you change these terms without our signature, and if so, do we get a chance to leave before the new terms apply?"


A simple way to use this checklist

  1. Pull the signed PDF (or the draft) and search for each heading above.
  2. Highlight anything vague, missing, or one-sided.
  3. Send your questions in one email so answers are in writing.
  4. Put the notice deadline—not just the renewal date—on your calendar.

You do not need to become a contract lawyer. You do need to know where the surprises usually hide.


Not legal advice

This page is general information for business owners. It is not legal advice, and it does not create an attorney-client relationship. For decisions that affect your rights or obligations, talk to a licensed attorney in your state.

TermSentinel produces an automated risk report from the contract you upload. No TermSentinel team member reads your contract. Only you (and people you authorize) can see it. The report flags possible risks and opportunities; it is not a legal opinion.


If you want a faster pass before you sign or renew, TermSentinel offers a free automated risk check of your IT services or MSP agreement.


FAQ

What should I check first in an MSP contract?

Start with term and notice dates, pricing escalators, admin/tenant ownership, and data return. Those four areas cause most of the painful surprises for small businesses.

When should I review my IT services contract?

Before you sign a new agreement, and again at least 90 days before renewal so you still have time to send non-renewal notice or renegotiate.

Is an automated contract risk report the same as legal advice?

No. An automated risk report highlights clauses that often create commercial or operational risk. It is not a substitute for advice from a licensed attorney.