Skip to content
itsorted.online
IT Support guide

IT Support Contract and SLA: What Should Be in Writing

An IT support contract is only as useful as what it puts in writing. Many small business agreements promise 'fast response' and 'unlimited support' but say nothing about who owns the admin passwords, what happens to your data, or how you leave. This guide explains the parts of an IT support contract and service level agreement (SLA) that protect you: response versus resolution times, scope boundaries, admin access, the PDPA clauses for a provider that handles personal data, exit and handover, and reporting. It ends with a checklist to use before you sign. It is general guidance, not legal advice.

By IT Sorted teamReviewed 8 min readHow we write guides
in

Key takeaways

  • Response time is how fast someone acknowledges and starts; resolution time is how fast it is fixed.
  • Priorities need definitions, such as 'whole office cannot email' versus 'one printer is slow'.
  • Admin and billing accounts for Microsoft 365, Google, domain and backups should be in your company's name.
  • A provider handling your personal data is likely a data intermediary under the PDPA; put protection and breach duties in writing.
  • An exit clause should cover handing back credentials, documentation and data within a set time.
In this guide · 8 sections
  1. 01Response time vs resolution time in an IT SLA
  2. 02Scope: what the IT support contract covers (and does not)
  3. 03Admin access and ownership: keep the keys in your name
  4. 04PDPA and data protection clauses
  5. 05Exit, handover and reporting
  6. 06Red flags in IT support agreements
  7. 07Do it yourself or get help?
  8. 08Frequently asked questions

Short answer

A good IT support SLA sets response and resolution targets by priority, lists what is in and out of scope, keeps admin accounts in your name, has a PDPA data clause with breach reporting, and promises handover help when you leave. Replace words like 'unlimited' or 'ASAP' with numbers.

Response time vs resolution time in an IT SLA

Most disputes over IT support come from mixing these up. A provider promising a '1-hour response' may only promise that someone replies within an hour, not that the problem is fixed.

  • Response time: how long until a person acknowledges the ticket and starts work. Easy to promise, easy to measure.
  • Resolution or restore time: how long until the service works again, even with a temporary workaround. Harder to promise; often given as a target rather than a guarantee.
  • Support hours: the clock the SLA runs on. A 4-hour response 'in business hours' raised at 5pm Friday may mean Monday morning.

Ask for both numbers, by priority, and the hours they apply in. The example below shows the structure; the right targets depend on your business and budget.

PriorityExample definitionExample responseExample restore target
P1 CriticalWhole office cannot work: email down, ransomware, main system offlineWithin 1 business hourSame business day, or workaround
P2 HighSeveral people affected, or one key person fully blockedWithin 4 business hoursNext business day
P3 NormalOne user, workaround existsWithin 1 business dayWithin 3 business days
P4 RequestNew user, software install, changeWithin 2 business daysScheduled
Illustrative structure only, not an industry standard. Agree your own numbers and hours.

Scope: what the IT support contract covers (and does not)

'Unlimited support' rarely is. Get scope written as lists, so both sides know what is included in the monthly fee and what is billed extra.

Usually included (check)

  • Named users and devices, with a per-user or per-device count
  • Microsoft 365 or Google Workspace administration
  • Antivirus or endpoint protection management
  • Patching and updates on a stated schedule
  • Backup monitoring and periodic restore tests

Often excluded or billed extra

  • On-site visits and travel time
  • Projects: office moves, migrations, new systems
  • Line-of-business software (accounting, clinic, POS) vendor issues
  • Hardware purchase and warranty handling
  • Incident response after a breach beyond first containment

Also check how out-of-scope work is quoted: an hourly rate, a minimum block, and whether the provider must get approval before starting chargeable work. Our managed IT vs ad-hoc support guide helps decide which model suits you.

Admin access and ownership: keep the keys in your name

The most expensive IT contract problem shows up when you try to leave: the provider set up your Microsoft 365 tenant, domain, firewall or backups under their own account, and getting control back takes weeks. Write ownership into the contract from day one.

Ownership clauses to ask for

PDPA and data protection clauses

An IT provider that can access your mailboxes, files and customer database processes personal data on your behalf. Under the PDPA, a data intermediary that processes personal data for another organisation under a written contract is subject to the Protection, Retention Limitation and Data Breach Notification Obligations, as summarised in the PDPC's Advisory Guidelines on Selected Topics. Your business remains responsible for the data either way.

The PDPC's data breach guide requires data intermediaries to notify the organisation they work for when they detect a breach. Once you have credible grounds to believe a breach occurred, you must assess within 30 calendar days whether it is notifiable, and notify the PDPC within 3 calendar days of deciding it is. You cannot meet those deadlines if your provider is slow to tell you.

  • Purpose: the provider uses your data only to deliver the service.
  • Security: MFA on admin accounts, least-privilege access, logging. The PDPC's Guide to Data Protection Practices for ICT Systems is a useful reference list.
  • Breach notice: the provider tells you without delay, with a stated maximum such as 24 hours from discovery.
  • Subcontractors and location: who else touches the data, and in which countries.
  • Return and deletion: data and copies returned or deleted at the end, with confirmation.

Exit, handover and reporting

Write the end of the relationship into the start. An exit clause costs nothing to agree on day one and is very hard to negotiate during a dispute.

  1. Notice period

    One month is common for small business contracts. Avoid automatic multi-year renewals.

  2. Handover pack

    Credentials, admin accounts transferred, documentation, licence list and open tickets, delivered within a set number of days.

  3. Transition help

    A set number of hours at an agreed rate to brief the new provider.

  4. Removal of access

    Provider's accounts and remote tools removed, with written confirmation. Our offboarding IT checklist applies to outgoing providers too.

For reporting, ask for a monthly or quarterly summary: tickets raised and resolved against SLA, patch and backup status, security alerts and recommendations. If the contract involves security work, the CSA's Cyber Essentials mark gives a useful baseline to report against. It is valid for two years once certified.

Red flags in IT support agreements

Walk away, or at least negotiate, if a proposal shows any of these.

  • No numbers: 'priority support', 'fast response' or 'unlimited' without defined hours or targets.
  • The provider owns your tenant, domain or licences.
  • No mention of personal data, breach notification or what happens to backups when you leave.
  • Long lock-in with auto-renewal and a fee to release your own credentials.
  • Every exclusion vague, every inclusion specific to what is cheap to deliver.

For a wider view on picking a provider, see how to choose IT support in Singapore and our IT support cost guide.

Do it yourself or get help?

You can use the checklists above to review any proposal yourself; most providers will add ownership, breach and exit clauses if asked. Have a lawyer review long or high-value contracts.

IT Sorted's monthly plans are written this way. Protect Standard (S$19 per user per month, minimum 3 users) covers endpoint protection, encryption compliance, password manager admin, monthly awareness lessons and quarterly backup restore tests, with help within 1 business day when you forward a vendor alert. Care Plus (S$349 per month) covers website and workspace care with replies within 4 business hours. Both are cancel-any-time, and accounts stay in your name.

Frequently asked questions

It depends on what you can afford to be without. Many small businesses aim for a response within about an hour for critical outages and within one business day for routine requests. More important than the number is that the SLA defines each priority level and states the hours it applies in.

Response time is how quickly the provider acknowledges your issue and starts work. Resolution or restore time is how quickly the service works again, possibly with a workaround. Contracts often guarantee response but only target resolution, so ask for both and read which is binding.

If they process personal data on your behalf, such as managing mailboxes, files or customer systems, they are likely a data intermediary. Data intermediaries working under a written contract must protect the data, follow retention limits and notify you of breaches. Your business remains responsible, so put these duties in the contract.

Your business should. The domain, Microsoft 365 or Google Workspace tenant, licences and backups should be registered to the company, and the owner should hold at least one emergency admin account with MFA. The provider can use its own named admin accounts for day-to-day work.

A notice period, a handover pack with credentials, documentation and licence lists, transfer of admin access, a set number of transition hours, removal of the provider's accounts and remote tools, and return or deletion of your data with written confirmation, all within stated timeframes.

Rather have it done for you?

Fixed price, set up in your own accounts.

Order online, get a written scope, and keep full ownership of everything we set up. Questions first? Ask us in writing.