Many small businesses run for years with IT handled informally: a friend who knows computers, a vendor called when something breaks, or an employee who looks after the router in their spare time. That works until a server fails, a backup turns out to be empty or nobody knows the admin passwords. A written agreement does not have to be complicated, but it should make clear who is responsible for what. This checklist covers what a good agreement includes and what to question before signing.

Choosing the right type of agreement

Not every business needs the same arrangement. The common forms are:

  • An IT maintenance agreement for scheduled, recurring work on a defined list of systems.
  • Prepaid IT support hours, a block of time used for requests and small jobs, with a log of how each hour was spent.
  • A project contract for one defined job, such as a network upgrade or server replacement, with a fixed scope and schedule.
  • Managed IT services, where a provider takes broader, ongoing responsibility for monitoring and support.

Many businesses combine them: a maintenance plan for the essentials plus a block of hours for everything else. The right mix depends on how much you rely on your systems and whether you have anyone in-house.

The checklist: what should be in writing

1. Scope and covered systems

List the devices, servers, network equipment, software and cloud services the agreement covers, with locations. Anything not on the list should be clearly out of scope or billed separately. Review this list whenever you add staff, move offices or change systems.

2. The maintenance schedule

Define what happens and how often: operating system and application updates, firmware on firewalls and switches, antivirus checks, disk and hardware health, and server maintenance tasks such as log review and capacity checks. Specify whether work is done on-site, remotely or both, and in which maintenance windows to avoid disrupting staff.

3. Backups and test restores

A backup nobody has tested is a hope, not a plan. The agreement should say what is backed up, where copies are kept, how long they are retained and how often a test restore is done and documented.

4. How requests are handled

Explain how staff raise requests, how priorities are set and what counts as urgent. Be wary of vague promises. Clear definitions of priority levels and how they are handled are more useful than broad claims.

5. Security responsibilities

Spell out who manages user accounts, multi-factor authentication, firewall rules, remote access and security updates, and what happens when an employee leaves.

6. Documentation and access

You should own your documentation: network diagrams, device lists, license records and admin credentials held securely under your control. This protects you if you change provider.

7. Reporting

Ask for a short written report after each maintenance round, covering what was done, what was found and what is recommended. It keeps the work visible and helps plan budgets.

8. Billing and exclusions

State whether the fee is monthly, per device, prepaid hours or per project. List what is excluded, such as hardware purchases, major projects or after-hours work, and how extra work is approved.

9. Term and exit

Include the contract length, notice period and a handover process: return of documentation, credentials and data, and cooperation with the next provider.

Red flags when reviewing a business IT service contract

  • No list of covered systems, just "all IT".
  • No mention of backup testing.
  • The provider keeps admin passwords and documentation exclusively.
  • Automatic renewals with long notice periods and no exit process.

When a written contract pays off

An IT service contract is most valuable for businesses with a server, several workstations, security cameras or regulated data, where downtime or data loss is expensive. Smaller offices may start with a block of hours and move to IT maintenance contracts once they see which tasks recur. For businesses in Los Angeles and Long Beach looking for professional IT services under a written agreement, see IT service contracts and maintenance agreements from Breeze IT.

IT maintenance agreement FAQ

Is an IT maintenance agreement the same as managed services?

Not quite. A maintenance agreement usually covers scheduled work on defined systems, while managed services often add broader monitoring and responsibility. The contract wording defines the difference.

Are prepaid hours better than a monthly plan?

Prepaid hours suit businesses with occasional, unpredictable needs. A monthly plan suits those that need regular maintenance done on a schedule.

How often should the agreement be reviewed?

At least once a year, and whenever your systems, staff or locations change significantly.