This article was machine-translated from French and is being reviewed. Prices are in Algerian dinars excl. VAT.
A computer maintenance contract sets in writing what the provider does, within what timeframes and at what price. Without this document, disputes arise at the worst moment: a major outage, an unexpected invoice, or the departure of the person who knew the installation.
In short
- A computer maintenance contract defines the scope (equipment and services), response and restoration times, billing and duration.
- It distinguishes what is included from what is billed separately: replacement parts, licenses, travel outside the wilaya.
- It specifies backup (amount of data acceptable to lose, allowable downtime), escalation for critical incidents and exit conditions.
Essential elements of a maintenance contract
1. Scope of services
Write what the contract covers, equipment by equipment: workstations, servers, NAS, printers, switches, Wi‑Fi access points, firewall, UPS. Attach an appendix inventory with brand, model, serial number and purchase date. Then specify the services: user support, hardware maintenance, updates, backups, security.
A common trap: a contract covers the server but excludes the business software installed on it, or covers ten workstations but not Wi‑Fi. Also list exclusions and the rule for equipment added during the contract: addendum, or pre‑priced unit rate. To assess the fleet before signing, see renew the IT fleet and repair or replace a PC.
2. Types of maintenance
Specify whether the contract includes preventive maintenance (actions before failure: visits, updates, backup checks, supervision) and corrective maintenance (intervention after failure). The contract may combine both, and their billing can differ: a flat fee for preventive, a per‑intervention or flat fee for corrective. Write the visit frequency, what each visit contains and the report delivered afterward. See preventive or corrective maintenance to choose the right balance.
3. Response and restoration times
A serious contract distinguishes three timeframes, often conflated under the SLA (Service Level Agreement) acronym:
- Response: the provider has logged the request, qualified it and begins to address it.
- Restoration: the service is operational again, possibly thanks to a provisional workaround.
- Final resolution: the cause of the problem is addressed.
Committing to a service level does not guarantee restoration. Define each deadline by priority level (critical, major, minor), cross‑referencing impact (one person, a service, the whole company) and urgency. A printer failure is a minor incident in an office but critical in a retail store that prints receipts.
Numerical values are negotiated and written into the contract: they depend on scope, covered hours, and price. Also state when the deadline starts (ticket opening), whether it counts in business hours or calendar hours, and what interrupts it: waiting for a part, inaccessible premises, power or Internet outage on the client side.
4. Pricing and billing
Specify the payment method: flat fee, per‑visit billing, or mixed formula (flat fee plus out‑of‑plan interventions). List items billed separately:
- Travel and intervention : on our confirmed quotes, this line appears in 27 orders, with a median of 4,500 DA HT and amounts from 1,500 to 18,000 DA HT (source: our quotes, median).
- Travel outside the wilaya : 3 orders, from 5,000 to 18,000 DA HT, median 8,000 DA HT (source: our quotes, median).
- Replacement hardware (disk, power supply, memory, UPS, PC): price from the computer store in DA HT, plus installation.
Indicate whether the contractor supplies the equipment or if you purchase it yourself. All amounts in this guide are in DA HT.
5. Backups and continuity
The contract must state who backs up what, where, how often, and who verifies. Rely on the 3-2-1 backup rule: 3 copies of the data (the original plus two backups), on 2 different media, including 1 off‑site copy.
Two objectives must be in the contract. The RPO (Recovery Point Objective) is the maximum data loss you accept, expressed in time: an RPO of 24 hours means the last usable backup must not be older than one day. The RTO (Recovery Time Objective) is the maximum downtime you accept before service returns. These objectives precede solution choice, not vice versa.
Also write who tests restorations and at what frequency. A backup never restored is not a guarantee. RAID is not a backup, nor is a NAS that holds the only copy of data. See the guide on choosing between server and NAS and the one on the UPS, which protects these devices from outages.
6. Availability and escalation
Specify the days and hours covered: Sunday to Thursday during the day, or also Friday, Saturday and public holidays. Write how to report an emergency: channel to use, contact person, possible on‑call and its surcharge. Designate one or two client persons authorized to open requests and approve paid interventions. To organize this internally, see the IT helpdesk of an SME.
7. Software, licenses and access
Specify who purchases and renews the licenses (antivirus, operating system, business software) and in whose name: the company must remain the holder of its licenses and accounts. Administrative credentials must be documented and known to the company, not just the provider.
If the provider works remotely, name the remote‑control tool (RustDesk, AnyDesk, TeamViewer or other). TeamViewer and AnyDesk limit their free versions to personal use: a company needs a professional licence. RustDesk is open‑source and its server can be hosted by you. Require user consent for sessions, named accounts, two‑factor authentication and a confidentiality clause, because the technician sees what is on screen. See also why a firewall in an SME and link sites via VPN.
8. Duration, termination, tariff review
Set the contract duration and exit conditions: notice, possible early‑termination penalties. Provide reversibility: at contract end, the provider returns documentation, credentials, inventory and backups. Write how rates evolve: fixed during the term, revised on anniversary date, or subject to your prior agreement.
A contract protects both sides
For you, it defines the expected services and deadlines, preventing ad‑hoc requests at any time. For the provider, it bounds the scope and avoids “just in case you can also look at…”. A provider who refuses to set the scope and deadlines in writing leaves you without a basis in case of dispute.
Get a clear maintenance contract signed
A contract reviewed and signed by both parties is your protection. To define a suitable contract for your fleet, see the page IT maintenance. Depending on your needs, also consult our solutions for professional IT hardware and network security and firewalls.
Frequently asked questions
Should you have a multi‑year contract or renew annually?
A one‑year contract keeps flexibility if your needs change (relocation, growth, reduction of the fleet). A longer term may come with a negotiated rate but ties you more: then check exit conditions. Annual renewal with written notice is a simple formula.
What is the difference between response time and restoration time?
Response time measures the provider’s reaction: the request is logged and someone handles it. Restoration time measures when service returns to your users. The first can be met without the second, hence why both should be in the contract.
What to do if the provider fails to meet deadlines?
Include a compensation clause in the contract: a discount on the invoice, credit for intervention days, or the option to terminate without penalty after repeated breaches. To track deadlines, require each request to be logged in a time‑stamped ticket.
Can a contract be made without a duration commitment?
This is an option to discuss with the provider. Without a minimum duration, it becomes harder to amortise implementation (inventory, documentation, configuration), which may lead to billing per intervention rather than a flat fee.
Need an opinion on your site? A technician can come to assess your needs and advise you.