Request a quote
Emergency SectorsCareers About us Blog Get in touch
Table with printed charts, a laptop and a hand holding a pen

An IT support agreement: what belongs in it, and what you only notice when you leave

An IT support agreement rarely looks like a problem on the day you sign it. The gaps are in what it leaves out: who holds the passwords, what sits outside the monthly fee and what happens when you leave. This is the list we go through before anyone signs an IT maintenance contract, including one of ours.

7 min read Written by the ITproposal team
Short answer

The most important part of an IT support agreement is the list of what is not included. That is where the invoices and the arguments come from.

Admin accounts, passwords, licences and documentation should be in your organisation’s name, not the supplier’s, and that is agreed before you need it.

An agreement is only complete with an exit clause: what you receive, how quickly and on what terms. Then have the whole thing reviewed by a lawyer; that is not something we do.

What is in scope, and above all what is not

An IT maintenance contract describes the ongoing work a supplier does on systems you already have. It is different from a project agreement (building something new) and different from a manufacturer’s warranty (replacing a faulty device). In practice the three get mixed up, and that is where most disputes start.

Write the scope as a list, not a sentence. “Management of the IT environment” says nothing. What does work:

  • Which devices: laptops, servers, network, printers, phones, with numbers and a reference to the asset register.
  • Which users and sites: including home workers and a second office, because on-site work is a different job from remote work.
  • Which software: operating systems and Microsoft 365 are usually in scope; the finance package or sector software often is not, because it belongs to a third party.
  • What is explicitly excluded: projects, setting up new starters, office moves, training, recovery after your own changes. If it is not listed, it becomes extra work later.

For every exclusion, ask how it is handled instead: at what rate, with what prior approval, and who is allowed to give it.

Preventive and corrective maintenance

Corrective maintenance is fixing what has broken. Preventive maintenance is making sure it breaks less often: updates and patches, firmware on network equipment, checking that the backup can actually be restored, watching disks and certificates before they fill up or expire.

You only see the difference in the agreement if the preventive part has a frequency. “We keep systems up to date” is an intention. “Security updates within an agreed period, a backup restore test every quarter, and a monthly report showing both” is a commitment you can check.

Two questions sharpen it: who decides when maintenance may take place (an update that forces a restart at nine in the morning costs more than it delivers), and what happens to devices that no longer receive updates. A supplier who simply keeps “supporting” those is supporting a risk.

Response and resolution times: what the agreement must settle

The numbers themselves belong in a service level agreement, and how to write one that is achievable and measurable is covered in our article on SLAs you can actually meet. The IT support agreement settles something else: how that SLA is attached to it.

  • Which document prevails. If the SLA contradicts the contract, it must say which one takes precedence.
  • When the clock runs. Office hours only, or evenings and weekends too, and from which moment: the call or its triage.
  • What happens when a target is missed. A review, an improvement plan, a service credit or eventually grounds for termination. Without a consequence, a target is a wish.
  • Who measures and reports. Preferably from the ticketing system, in a report you can read without an explanation.

Time and materials or a fixed fee

There are two basic models, and they reward different behaviour. With time and materials you pay for hours worked: clear for a small estate with few tickets, but the supplier earns more when more goes wrong. A fixed fee per device, per user or per seat makes costs predictable and rewards preventive work, because every incident that does not happen saves the supplier time.

In practice it is often a mix: a fixed fee for ongoing maintenance and hours for projects and changes. What drives the price is the same either way: the number of devices and how varied they are, the hours covered, how much has to be done on site, and how old and how standardised the environment is.

What you agree in both models: when something counts as extra work, who approves it in advance and above what size, how the fee moves when you grow or shrink, and how often and on what basis the rate may change.

Who owns the passwords and the documentation

This gets the least attention at signing and costs the most when you leave. The rule of thumb: everything needed to run your environment without this supplier belongs to you.

  • Admin accounts and passwords. At least one admin account in your organisation’s name that the supplier cannot disable, and a password vault you can export on request.
  • Licences and subscriptions. In your tenant and in your name, even if the supplier buys them.
  • Domain name and DNS. Registered to your organisation. Recovering a domain held by a former supplier can take weeks.
  • Documentation. Network diagrams, configurations, the asset register and procedures. Agree that you can request them at any time, not only at exit, and that they are kept current.

If the supplier has access to personal data, and in support it almost always does, you need a data processing agreement under UK GDPR or the GDPR alongside the contract.

Term, notice and handover

An initial term of one year or more is common and not unreasonable: the supplier invests at the start in learning and standardising your environment. Watch three things around it.

  • Automatic renewal. For how long the contract renews and how much notice you must give. Put that date in your diary the day you sign.
  • Early termination. Whether it is possible when commitments are repeatedly missed, and how that is established.
  • The exit clause. What the supplier still does after notice: handover to a successor, delivery of documentation, passwords, backups and logs, within what period and on what terms. Also agree that this cooperation applies if you part ways in a dispute; that is exactly when you need it.

How such a move works in practice is covered in our article on changing IT supplier.

Liability in plain English

Almost every IT contract limits the supplier’s liability, and that in itself is normal. What you need to understand is how far the limit goes:

  • A cap. The maximum the supplier will pay, often linked to what you pay over a given period. Compare that with what a day of downtime costs you.
  • Excluded losses. Indirect and consequential loss, loss of profit and loss of data are often excluded entirely. That last one makes the backup arrangements more important than any liability clause.
  • Wilful misconduct and gross negligence. A limit usually does not apply to these; check that the contract says so too.
  • Standard terms. The real arrangement is often in the supplier’s terms and conditions rather than the contract. Read them as well and check which prevails if they conflict.

Whether a limit is reasonable for your situation, and whether you insure the remaining risk, is a question for a lawyer and your insurer.

Where our work stops

What we do. We supply and deliver the technical part: a scope written as a list, preventive maintenance with a frequency, reporting from the ticketing system, admin accounts and documentation in the client’s name, and an exit clause we can honour ourselves. We are ISO 9001 and ISO/IEC 27001 certified, which describes how we work, not a verdict on your contract.

What we do not do. We are not lawyers. We do not review contracts legally, including another supplier’s, and we do not tell you whether a liability cap or a termination clause is acceptable for you. Always have an IT support agreement reviewed by a lawyer before you sign. Nor are we an insurer: which remaining risk to insure is a conversation with your own insurer.

Frequently asked

Questions we get about this

The five that come up most often.

What should an IT support agreement include?

The scope (which devices, users, sites and software), preventive and corrective maintenance, the link to the service level agreement, the pricing model and the rules for extra work. Then ownership of passwords, licences and documentation, the term and notice, the exit clause and liability. The most useful part is the list of what is explicitly excluded.

What is the difference between an IT maintenance contract and an SLA?

The contract governs the relationship: what is done, at what price, for how long and how you get out. The SLA governs performance: response and resolution times, availability and how they are measured. The contract should state which one prevails if they conflict, and what happens when an SLA target is missed.

Is a fixed fee better than paying by the hour?

It depends on the estate. Paying by the hour is clear when there are few devices and few tickets. A fixed fee makes costs predictable and rewards the supplier for preventing problems rather than fixing them. Many agreements combine both: fixed for maintenance, hours for projects, with prior approval for extra work.

Who owns the passwords if we change IT supplier?

Your organisation should, and the contract should say so. Agree that there is an admin account in your name the supplier cannot disable, that the password vault can be exported, and that licences, the domain name and documentation are in your name. Leaving that until exit means negotiating from a weak position.

Can you review our IT contract legally?

No. We are not lawyers and do not review contracts legally, including another supplier’s. What we can do is explain what a technical commitment means in practice and whether we could honour it ourselves. Always have the contract itself reviewed by a lawyer before you sign.

Related services

Further reading

What this agreement connects to.

Shall we hold your agreement up against practice?

Send us the scope and the exit clause you have now. We will tell you which technical commitments are concrete enough to honour and which are not; the legal review we leave to your lawyer.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call