A computer maintenance contract template: what makes a clause binding, and what to strike out

Anyone searching for a computer maintenance contract template does not want a file. They want to know what they is about to sign. And in most cases the supplier's contract has already reached him: two pages, a clause on scope, a clause on response, and a place to sign. A contract nobody wrote for his situation, which will nonetheless govern the coming year.

This article does not give you text to copy. It gives you how to read that contract as a document: what parts it is made of, which definitions decide whether a clause is worth anything, and what to ask to have struck out. The list of what you should be asking for in the first place is in the clauses to ask for in a maintenance contract, and this article starts where that one stops.

Why there is no template to download here

You will not find a ready-made contract on this page, and the reason is not caution: a template pushes people to sign without reading. Anyone who downloads a file headed “maintenance contract” assumes its contents have already been reviewed and tested, so he runs his eye over the clauses — which is exactly the reading that landed him in the contract he has now.

And the most important part of the contract is not in its body but in the hardware annex, which no template can write for you because it is an inventory of your own equipment. The supplier is the one who puts forward his wording in most cases, so the skill you need is reading his contract and amending it.

What the document is made of

The parties, the signing authority, and the address for notices

The full name of both companies as it appears in the commercial register, and the register and tax card numbers for each. Then the part that most often goes missing: the capacity of the signatory. A contract signed by a sales engineer who cannot bind his company becomes an argument at the point of dispute, not at the point of signature. And the notices clause sets the address to which any notice of termination or of refusal to renew is delivered. If email is an accepted channel, name the addresses themselves rather than “the company's official email” — the address of somebody who has left the company is no way to serve a termination notice.

The annexes are the contract

The usual annexes are four: the inventory of hardware and sites; the service levels and fault classification; the schedule of value and what is charged outside it; and the contact list and escalation path. Three things about them as documents:

• The annex is signed, stamped and dated exactly like the body. An unsigned printed annex makes it easy to say a year later that it was only a draft.
• The body must state that the annexes form an integral part of it. Without that sentence the annex becomes an attachment for information.
• A mechanism for updating the annex. An inventory frozen on the day of signature is wrong six months later: a machine went out, a server came in, a branch opened. Write that it is updated by written acknowledgement from both sides without a new contract, and that an added device enters cover from a known date.

Order of precedence, and language

A body plus annexes means a possible conflict between them, and the order-of-precedence clause is what decides which text prevails. More important still: the technical proposal you received before contracting is not a contract. Many contracts carry a clause stating that the contract and its annexes supersede every prior communication, which wipes out whatever reassured you in the proposal. So whatever you based your decision on, move it into the annex. And a contract drawn up in both Arabic and English needs a sentence naming which version governs in case of difference; Egyptian courts work in Arabic, so any document in another language will need translating if matters reach a dispute.

The definitions that decide whether a clause is worth anything

This is where the contract earns its value or is emptied of it. A clause that does not define its terms is interpreted by the party with an interest in them, and most contracts in the market carry no definitions section at all.

“Within 24 hours”: from which moment, and which hour

“Response time: within 24 hours” commits nobody to anything until the contract answers three questions:

• From which moment? From the fault occurring, from your becoming aware of it, from its being logged on the official channel, or from the supplier acknowledging receipt? The gap between the first and the last can be a full working day, and a contract that does not name the moment leaves the supplier free to start counting from his own acknowledgement.
• Calendar hours or working hours? Twenty-four working hours inside cover that ends at the close of the day and stops at the weekend is not one day: a ticket logged late on Thursday afternoon, under cover running Sunday to Thursday, is due a response on Sunday — and the contract has been performed in full. So the days of cover are enumerated by name and the holiday calendar the contract follows is identified; a supermarket whose peak is Friday and a factory running two shifts are not served by an unwritten custom.
• And does the clock stop? Serious contracts carry a clause that pauses the count while something is awaited from you: information, access to the site, approval of a part. The clause is legitimate and needs one constraint — that the pause be by written notice saying what is awaited, with the count resuming when it is provided. Without that, you discover that every late ticket had been paused.

What counts as a response, and who keeps the evidence

A response clause satisfied by an automatic reply from the ticketing system is worth nothing. The definition that helps names the act: a particular engineer in contact with whoever logged the ticket, who has reached the device or obtained information from it, and has begun diagnosis. The same goes for arriving on site: arrival means a technician present and able to work, not passing by to look at the problem and leaving.

Then a question nobody asks: who keeps the evidence? The only record of ticket times is the supplier's own ticketing system. So give yourself the right to an export of your ticket history, or every time is whatever the party being measured by it says it is.

Who grades the fault

Severity definitions mean nothing if the supplier alone does the grading. Grading goes by impact; you should have the right to raise a ticket at the level you judge it to be, and the supplier the right to regrade it in writing with a written reason. A contract that leaves grading to one side hands that side the key to every time written into it.

What is a “device” and what is a “site”

One server carrying ten virtual machines: one device or eleven? An employee's laptop at home: inside the site or outside it? The definition sets both what you pay for and what you can claim, and it needs a clause alongside it setting out how a new device or a new site enters cover.

“Maintenance”, “repair” and “replacement”

A contract that covers “maintenance” and says nothing about replacement leaves open a perfectly sound and very uncomfortable outcome: the supplier is fully compliant and the server is still down, because what binds him is inspection, diagnosis and an attempt, not restoration of service. Licence renewal is a third and separate matter: a firewall keeps working after its licence expires while its protection services quietly stop updating, and the maintenance contract does not renew that licence unless it says it does.

What to strike out or narrow

Most of what weakens a maintenance contract is not a clause written in bad faith, but elastic wording that reads as reassurance:

• “As soon as possible”, “as the case may be”, “subject to technician availability”. Any sentence carrying no time and no consequence for lateness is a statement of intent. Ask for a stated time in its place, or delete it and know that it does not exist; the worse of the two is counting it as a guarantee.
• Sole discretion. “The supplier shall determine whether the fault is within scope” means that whoever bears the cost of the repair decides whether it is covered. The alternative is a named tiebreak: a joint report signed by both sides.
• “Best endeavours” where an obligation belongs. A clause saying the supplier will use his endeavours to restore service can neither be measured nor breached. It is acceptable where he genuinely does not control the outcome, such as a part not available in the market, and unacceptable for what he controls entirely: attending, diagnosing and reporting.
• Automatic renewal at an open value. A contract that renews itself at a value set by the next invoice, with a notice window that closes before you remember it. Ask for renewal by written acknowledgement, or for a mechanism for adjusting the value written down in advance.
• Subcontracting without consent. A clause letting the supplier pass the work to whomever he chooses puts somebody you do not know on your domain administrator account. Narrow it: subcontracting with your written consent, and full responsibility staying with the original supplier.
• “Including but not limited to” in the exclusions list. A list that opens with that phrase is not a list; it is permission to add an exclusion nobody has read. Exclusions are enumerated exhaustively, and whatever is not named in them is covered.
• Blank fields. A contract signed with “to be agreed” in it, or an empty line in the table of times. It never does get agreed later.

And the liability clause deserves candour: the exclusion of indirect damages — business interruption, data loss — sits in almost every services contract, and it is rare for a maintenance supplier to take it out. Do not waste the negotiation there. Take measurable obligations instead: a documented restore test of the backups, a change log, and a documented handover at the end.

Parts and ownership: who owns what

Ownership of spare parts drops out of most contracts because it looks like a detail, and is then discovered on the day of the fault. Four cases need a sentence:

• The removed part. The disk that comes out of your server holds your data, and a clause letting the supplier take the failed unit away to return it to the manufacturer needs its counterpart: either documented secure destruction before it leaves, or your right to keep it while bearing the difference in the replacement procedure.
• The temporary loan unit. It is the supplier's property in your custody, and needs a sentence on damage or loss and when it goes back.
• The supplied part. When does title pass to you: on fitting, or on payment? Anything fitted into your machine and not yet paid for needs a clear position, or it becomes leverage in any later dispute.
• What you paid for separately is yours even if the supplier fitted it, and even after the contract ends. Write it down rather than assuming it.

The exclusion everybody forgets: the environment

Buyers read the exclusions list looking for a trick, and skim past what actually harms them. What harms them is not a surprise exclusion but a gap: something that is in neither the covered list nor the excluded one — and whatever is named on neither side becomes a dispute rather than a clause in your favour.

What falls into that gap most often is the environment around the equipment: power and its earthing, the air conditioning, the UPS batteries, the state of the rack. The supplier excludes them legitimately, since they are not a fault in a device, yet a large share of server failures starts there. So if your server room is outside scope, put in writing who checks its temperature and who tells you a UPS battery has reached its end, even if the clause is to inspect and report rather than to repair. The aim is not for the contract to cover everything, but for everything to be on a known side of the line.

Preventive maintenance: written as an obligation, not a promise

The preventive visit is the most useful thing in the contract and the easiest to evaporate from it, because it is the only obligation whose absence nobody is alerted to: nobody raises a ticket because a visit did not happen. Its content item by item is in the companion article, headed by a real restore test of the backups. What makes it an obligation is two things:

• A written output for every visit. A report of what was checked, what was found and what is recommended, signed by the technician and by someone on your side. A visit with no report is a visit that cannot be shown to have happened.
• What happens to a missed visit. Most contracts are silent, so the visit simply disappears; write that it carries over to the following month or is deducted from the value. And in the same fairness: an obligation on you to provide an access window, because most preventive visits that do not happen are cancelled by the client, not the supplier.

The end: make the handover a condition of payment

The list of what you receive at the end is in the companion article; what is missing here is what makes it enforceable. A handover clause tied to nothing is a request, not an obligation — so tie it to the final instalment: due after a signed handover covering the passwords, the device configuration files, the up-to-date documentation, the hardware inventory and the ticket history. And that handover needs two clauses before it to be possible at all: a list of every account the supplier creates, delivered updated with each report — the account nobody knows exists is the account that survives the end of the contract — and a change log saying who changed what and when.

A clause obliging you to pay for the whole term if you leave early is not merely a commitment to a term but an exit penalty, so read it under that name. And finally: whatever the supplier holds of your data — monitoring exports, copies on his cloud, configuration images — is returned or destroyed within a stated period, with written confirmation, or you have left a copy of your network with a company you no longer work with.

The order in which to read it

The body of the contract is rarely the problem. Three parts decide its value, and read them in this order: the definitions, then the exclusions, then the exit clause; and if the contract has no definitions, start by writing them, as they are the cheapest amendment with the largest effect. One last step saves a long read: ask the supplier to explain why any clause you want struck is there. A clause with an operational reason is explained in one sentence, while a clause nobody can say why is there has usually been copied from another contract and is deleted at nobody's cost.

We at ZEMAVO sign support and maintenance contracts, and you will find on this page neither a template to download nor times announced in advance, because a time written before anyone has surveyed what you have is marketing, not a commitment. What we accept being held to is what is above: a signed inventory, written definitions, exhaustive exclusions, and a handover tied to the final instalment. Put your existing contract in front of us and go through it clause by clause against this article — including the clauses that run in your favour against us.