A maintenance contract is signed once, then rolls over automatically for years. Nobody rereads it — until the day it has to be used.
On that day you discover it does not say what you thought. It describes what the supplier undertakes to do, not what you are entitled to receive. The distinction looks slight; it governs everything else.
Best endeavours or outcome: the only question that matters
A maintenance contract is almost always a best-endeavours obligation. The supplier undertakes to attend with skill and diligence. It does not undertake that the system will work.
Shifting to a guaranteed outcome is exactly what a service level agreement does. It requires four things in writing: an availability figure, a response time, a resolution time, and a penalty that applies if the commitment is missed. Leave out one and all that remains is an intention.
A commitment without a penalty is not a commitment. It is a statement of intent that has been given legal form.
Why two quotes cannot be compared
The price of a maintenance contract means nothing until three variables are aligned across the quotes:
- scope — hardware, applications, environments covered, and above all what is expressly excluded
- cover — working hours, on-call, public holidays, and the rate for attending outside those windows
- included volume — how many call-outs are covered, the point at which billing starts, and the unit of measurement
Two proposals thirty per cent apart usually cover three different scopes. The comparison only becomes honest once you have written the scope yourself and imposed it on both suppliers.
The clauses whose absence costs you
- Exit. Term, notice period, renewal date. Six months’ notice on an automatically renewing contract locks you in for another year if the date is missed.
- Handover. Credentials, administrator accounts, configurations, operating documentation: within what time, in what format, at what cost. Unwritten, it is negotiated at the worst possible moment.
- Growth. What happens when you add twenty machines or an application. With no adjustment rule, every change reopens the whole negotiation.
- Traceability. A log of call-outs available without having to ask. It is the only record that lets you verify a commitment was met.
What to have settled before signing
Not the price, but the level of service the business actually needs. Four hours of downtime is of no consequence to some organisations and costs others a day’s output. That figure is worked out internally; it is not asked of the supplier, who has no way of knowing it.
What a contract provides for matters less than what it provides for leaving it. That is the clause you wish you had written.
Once that threshold is set, the contract becomes legible: it meets the commitment, or it does not. Without it, you are negotiating a rate without knowing what you are buying.
Common questions
How do you draft an IT maintenance contract?
By first setting, internally, the service level the business needs. Then writing the scope yourself, a quantified service commitment with penalties, exit and handover terms, the rule for changes to the equipment, and access to the intervention log.
Why can two IT maintenance quotes not be compared?
Because three variables change from one offer to another: the scope covered and its exclusions, the hours of cover, and the intervention allowance. Until they are aligned, the price gap means nothing.
Does a maintenance contract guarantee the system works?
Generally not: it is an obligation of means. Only a complete service commitment — availability rate, response time, restoration time and an enforceable penalty — brings it closer to an obligation of result.
How do you get out of an automatically renewed maintenance contract?
By giving notice before the anniversary date: a long notice period missed can commit you for another year. The return of access rights, configurations and documentation must be provided for in writing, or it is negotiated at the worst moment.