Skip to main content
Legia

IT Support & Consulting

What to Check in an IT Service Contract Before Signing

A vague IT service contract only shows its cost when something goes wrong. This checklist helps you review scope, SLA, account ownership, security, and exit terms before you sign.

SEO and Content Specialist

4 min read

Hands on a laptop keyboard

Short answer: before signing an IT service contract, make sure five things are clearly written: what is and is not included, response time by severity level along with service hours, who owns the accounts and data, which reports you receive, and how to exit, including the handover of access and documentation. A contract that is vague on these points only shows its cost when something goes wrong.

A subscription IT service contract hands part of the control over a company’s systems to another party. That is normal and is often more efficient than handling everything yourself. But the control you hand over needs clear limits. The US cybersecurity agency CISA, in its guidance for customers of managed service providers, stresses the same point: the responsibilities of the provider, the customer, and the shared ones need to be written explicitly in the agreement.

The checklist below is meant to be read alongside a draft contract.

Scope

1. A list of what is managed. The contract should state what is managed: the number of servers, cloud environments, work devices, user accounts, office locations, and networks. Without a list, every new request can turn into a debate over “included or not”.

2. What is not included. This matters as much as what is included. Common exclusions are device and license purchases, repair of broken hardware, cloud provider bills, and project work such as large migrations. Make sure these exclusions are written down, not first mentioned when the invoice arrives.

3. An initial inventory. A good provider starts by inventorying the running assets before setting a price. If the price is set without an inventory, check how the difference is handled when the number of assets turns out to be different.

Illustration: IT support

Response time and service hours

4. Severity levels and response time. “Fast response” is not a term. What needs to be written: a definition of each severity level (for example, an outage that stops work versus an ordinary request), the response time for each level, and the resolution target if there is one.

5. Service hours and after hours. Ask what happens if an issue appears at night or on a weekend: whether it is still handled, for which severity levels, and whether there is an extra charge.

6. On-site visits. Most requests can be resolved remotely, but some work requires a physical presence. The contract should state the coverage area, how visits are scheduled, and who bears the travel cost.

7. One recorded channel. Requests sent by private message to a single technician are hard to trace. Make sure there is an official channel with ticket numbers, so the status and handling history can be checked at any time.

Ownership and security

8. Accounts in the company’s name. Domains, cloud accounts, admin accounts, licenses, and devices should be registered in your company’s name, not in the name of the provider or its technicians. The provider is given access rights that can be revoked at any time. This is the most important principle in the whole checklist, because it determines how easily you can switch providers later.

9. Provider access and security. Ask who on the provider’s side holds access, whether that access uses two-step authentication, and whether the activity is logged. The CISA guidance recommends that customers keep full control over access to their systems and know what access the provider holds, through a policy agreed by both parties. If the provider processes personal data on behalf of the company, its role under the Personal Data Protection Law (UU PDP) should also be clear in the contract.

10. Employees joining and leaving. The contract should state who creates and revokes employee accounts, and how the revocation is recorded. A former employee’s account that is still active is a very common gap. The procedure is covered in IT Offboarding Procedure When Employees Leave.

Reports and exit

11. Reports and how to exit. The last two items are often overlooked:

  • Regular reports contain the number of requests, the most common types of issues, incidents, and recommendations. Without reports, it is hard to judge whether the service is worth its cost.
  • Contract term, notice period, and handover. Check the minimum subscription period, how much notice is required before leaving, and what is handed over on exit: all access, the asset list, configuration documentation, and ticket history.

Red flags in a draft contract

  • Scope is written as “all IT needs” with no list.
  • Response times are not differentiated by severity level.
  • Admin accounts or domains will be registered in the provider’s name.
  • There is no handover provision when the contract ends.
  • Device and license purchases are made by the provider without itemized pricing and in the provider’s name.

How a Legia contract is structured

In the IT Support & Infrastructure Management service, the contract starts with an initial inventory of servers, devices, accounts, licenses, and networks, so the basis for the price is clear before the subscription begins. All requests come in through one ticketed channel, response times follow the service hours and severity levels written in the contract, and you receive a monthly report. All accounts and access rights stay in your company’s name, device and license purchases are billed separately in your company’s name, and the minimum subscription period is 12 months. On exit, Legia hands over all access along with the asset list and documentation. A comparison with other options is in Subscription IT Support, an In-House IT Staff, or Call When Something Breaks?.

Frequently asked questions

What is the difference between an SLA and a service contract?

An SLA (service level agreement) is the part of the contract that governs the service level: response time, service hours, and resolution targets. A service contract covers more, including scope, pricing, confidentiality, and exit terms.

Should there be a penalty if the SLA is not met?

That can be negotiated. What matters more is that the SLA is measurable and recorded, so a breach can be proven and discussed in a regular review.

Who in the company should read this contract?

Ideally three parties: the day-to-day users of the service for scope and SLA, the finance team for pricing and exclusions, and the legal team for confidentiality, personal data, and exit terms.

Sources

Category IT Support & Consulting

Keep reading

Related articles

All Articles