An IT contract review checklist for small businesses

Auto-renewals, price increases and weak service credits sit in the fine print. Here’s what to check before you sign or renew an IT contract. Not legal advice.

Green graphic reading Read it before it renews, with three checks: renewal, exit, price

Technology contracts are written by the vendor. Auto-renewals, price increases, minimum seat counts, and weak service credits usually sit in the fine print, and most businesses only notice them after the renewal date has passed. By then the leverage is gone.

This checklist is for an owner or manager who is about to sign or renew an IT, software, cloud, internet, or equipment contract. It is a technical and financial read, not legal advice. For anything binding, consult a licensed attorney.

If you want a second pair of eyes on the documents, Green Orb’s IT contract review is a fixed-price project quoted after a free call. You work directly with Kevin Whitney, backed by a 25-agent operation. The list below is the same ground we cover.

1. Term and auto-renewal

  • What is the initial term, and what happens when it ends?
  • Does the contract auto-renew? For how long?
  • How much notice do you have to give, and how must it be given (email, portal, certified letter)?
  • Put the notice date on a calendar now, with a reminder well before the window closes.

A contract that renews for another full year unless you write 60 or 90 days ahead is common. Missing that date is how a “we’ll see how it goes” deal becomes another year of spend.

2. Termination and exit help

  • Can you leave at the end of the term without a cause letter and without an exit fee?
  • What happens if you need to leave early? Are there termination fees, and how are they calculated?
  • Will the vendor help you export data, move numbers, or hand off equipment, and is that help timed and priced in the contract?
  • What do you still owe if you leave — unused term, installation charges, “recovery” of discounts?

If exit help is “available on request” with no deadline, treat that as optional. Ask for a date and a format.

3. Who owns the accounts and the data

  • Whose name is on the accounts, domains, phone numbers, and licenses — yours, or the vendor’s?
  • Who owns the data you put into the service, including backups and logs?
  • How do you get a complete export, in a form you can actually use, and how long do you have to request it?
  • What does the vendor keep after you leave, and for how long?

If the vendor holds the logins “for your convenience,” you do not fully control the service. The same issue shows up in AI work: the accounts should be in your name from the first day. See the questions we ask before hiring a consultant for the same test in that context.

4. SLAs and remedies

  • What is actually promised — uptime, response time, repair time — and how is it measured?
  • What is excluded (maintenance windows, third-party outages, “factors beyond our control”)?
  • What do you get when the vendor misses the target? A credit, a refund, a right to walk away, or a report?
  • Is the credit automatic, or do you have to file a claim in a short window?
  • Is the credit large enough to matter, or is it a token amount against a much larger invoice?

A service level without a remedy is a target, not a commitment. Read the exclusions as carefully as the headline percentage.

5. Price increases

  • Can the vendor raise the price during the term, and by how much?
  • Is there a cap, a published index, or an open-ended “then-current rates” clause?
  • Do discounts expire on renewal?
  • Are there minimum seats, minimum spend, or overage charges that are easy to miss on the invoice?

Ask for a renewal price in writing before the notice window, not after it.

6. Scope exclusions

  • What is included in the monthly or annual fee, in plain language?
  • What is billed extra — after-hours work, on-site visits, new devices, projects, security tools, “premium” support?
  • Are there overlapping contracts that already pay for the same thing?
  • Do you have unused seats or licenses you are still paying for?

Write down what you think you bought, then read the exclusions. The gap is usually where the next invoice grows.

How to use the checklist

Gather the contracts, the last few invoices, and a list of who uses each service. Do not send passwords by email. Walk the six items above, and write down dates, amounts, and questions. If a term is unclear, ask the vendor to explain it in writing before you sign.

IT contract review is the paid version of this read: a plain-English summary, a renewal calendar, a ranked list of costly or risky terms, and negotiation points. We can join the vendor call if you want a technical voice in the room. We do not guarantee savings; some contracts are already fair, and we will say so. Price is fixed in writing before work starts. You can stop after any step.

Related: IT projects and, if you are comparing managed IT quotes, what a managed IT agreement should include.

Text 404-333-8432 or book a free 30-minute call.

This article is not legal advice. For anything binding, consult a licensed attorney.

Want a second read on a contract?

Ask about an IT contract review, or book a free 30-minute call first.