All articles
IT support

Planned maintenance or break-fix IT support: which is right for your business?

Published30 October 2026
Reading time7 min read
AuthorJames Powell
In short

Break-fix means you call someone when something stops working and pay for the time it takes to fix. Planned maintenance means someone looks after your systems on a regular basis so that fewer things stop in the first place. Neither is right for every business. Break-fix can be perfectly sensible for a very small, low-risk setup, but it has one built-in weakness: you only find out how much it costs once the problem is already happening. This guide explains the difference in plain English, shows what usually goes wrong, and gives you a way to decide.

What each model actually means

Break-fix. Nothing is looked after in advance. When a machine fails, the internet drops or an update causes a problem, you call, an engineer attends or connects remotely, and you pay for that time. There is usually no monthly cost.

Planned maintenance. Systems are checked and looked after regularly, in the background and on a schedule. Problems are spotted and dealt with earlier, updates are planned rather than arriving at random, and there is a regular, predictable cost instead of occasional unpredictable ones. Many providers deliver this as part of a managed service. If you want to see how that is typically packaged, read what is included in managed IT support.

How the two models differBreak-fix reacts after the failure. Planned maintenance works ahead of it.
Break-fix compared with planned maintenanceTwo timelines. Break-fix: a steady line interrupted by sudden failures, each followed by a scramble to fix. Planned maintenance: a smooth line with scheduled checks, updates and tests along the way.BREAK-FIXsomething failssomething failsscramble to fixscramble to fixPLANNED MAINTENANCEcheckedupdatedtested
Illustration only. The shapes are a simplified sketch, not data.

Why break-fix looks cheaper

On paper, break-fix is easy to like. You pay nothing when nothing is wrong, and you only buy support when you need it. For a business with a handful of machines and nothing that cannot wait a day, that logic can hold up.

The weak point is timing. With break-fix, the bill arrives in the middle of the problem: your staff cannot work, your customers are waiting, and you are making decisions in a hurry. The invoice for the fix is only part of the cost. Our guide to what downtime actually costs a small business shows how to work out the rest: idle staff, lost or delayed work, and the effort of getting back up.

What actually causes IT downtime

Most outages are not dramatic. They are ordinary. The Databarracks Data Health Check 2026, an annual survey of 500 IT professionals, asked organisations what caused their IT downtime. Four of the causes it reported are the everyday kind:

  • Hardware failure at 18.6%
  • Connectivity problems at 14.0%
  • Upgrades and patches at 12.0%
  • Cloud outages at 11.4%

Together, that is 56% of respondents. Only 11% reported no downtime at all in the last year.

These are exactly the sort of problems that planned maintenance exists to catch early or make less disruptive: a failing component, a connection that has been getting worse, an update that should have been planned for a quiet evening rather than a busy morning.

Hardware failure is also simply normal. As an illustration, Backblaze, which runs a large data centre, reported a quarterly annualised failure rate of 1.73% across 354,415 hard drives in Q2 2026 (published 29 September 2026). These are data centre drives, not office PCs, so treat the figure as a reminder that failure is a matter of when rather than if, and not as a prediction for your own equipment.

What planned maintenance covers

The details vary by provider, so ask exactly what you are getting. In general, good planned maintenance includes:

  • Monitoring, so problems with disks, connections and devices are spotted before users report them
  • Planned updates, scheduled for quiet times, rather than left until they cause trouble
  • Backups that are tested, not just assumed to be working
  • Keeping track of equipment age and warranty, so replacements are planned rather than forced
  • Written recovery plans, so there is a route back if something does go wrong

At i90, our planned approach includes proactive monitoring, patch management, tested backup restores and documented recovery plans. Because much of the day-to-day work can be done remotely, we keep on-site visits for work that genuinely needs someone there, which means fewer, more useful visits rather than more of them.

Side by side

Break-fixPlanned maintenance
When you payWhen something failsRegularly, in advance
Cost patternUnpredictablePredictable
Who spots problemsYou, when something stopsYour provider, often earlier
UpdatesOften left until something forces themScheduled in advance
Best suited toVery small, low-risk setupsBusinesses that rely on their IT every day

When break-fix is perfectly fine

It would not be honest to say planned maintenance is always the answer. Break-fix can be a sensible choice if you have a very small number of devices, none of your work depends on being online at a particular moment, you are comfortable with a day's wait when something fails, and you have someone you trust to call. If any of that stops being true, such as taking on staff, moving work online or relying on a server, it is time to look again. Our guide to the signs you have outgrown your IT support is a good checklist.

What proactive monitoring looks like in practice

It is easy to say "we monitor your systems", so here is what that means day to day. We run monitoring software across the machines we look after, and it tells us when something needs attention. It watches machine health, including disk space, temperatures and performance. Numerous times a month it flags an upcoming issue before the customer is even aware of it, which means we can deal with it before it turns into an interruption. A drive that is running out of space, for example, can be sorted before it stops a machine working.

Some of the things we are alerted to:

  • Disk space, thermals and performance, so a struggling machine is dealt with before it fails
  • Stopped processes, such as the print spooler, which can stop printing across an office
  • Host firewalls being switched off, so we know straight away if a machine has lost that protection
  • Servers going offline, so we are told as it happens rather than when someone phones to say they cannot get in
  • Antivirus notifications, mailbox monitoring and phishing alerts, which help catch problems early and keep disruption to a minimum

Each of these is small on its own. The point is that together they let us manage your IT in the background, so the people using it are inconvenienced as little as possible.

North East businesses: what to ask a local provider

We support businesses across County Durham, Newcastle, Gateshead, Sunderland and Washington. Whoever you choose, a few plain questions will tell you whether they work in a planned way:

  1. What do you check in advance, and how will I know it has been done?
  2. How do you decide what is fixed remotely and what needs an engineer on site?
  3. When were our backups last test-restored, and what was restored?
  4. Do you keep a list of our equipment, its age and its warranty status?
  5. What is the plan if something fails out of hours?

If you would like to talk it through, get in touch or see how we work with businesses in your area, for example IT support in Newcastle or IT support in County Durham.

Common questions

What is the difference between break-fix and managed IT support?

Break-fix means you pay for support only when something fails. Managed IT support means a provider looks after your systems on an ongoing basis for a regular cost, with monitoring, updates and planning included.

Is break-fix IT support cheaper?

It can look cheaper because there is no regular charge, but the cost arrives when something has already gone wrong, and it does not include the cost of lost working time. Work out your own figure using the method in our downtime guide before deciding.

What causes most IT downtime?

In the Databarracks Data Health Check 2026, hardware failure (18.6%), connectivity problems (14.0%), upgrades and patches (12.0%) and cloud outages (11.4%) together accounted for 56% of respondents' downtime.

When is break-fix the right choice?

When you have a very small number of devices, nothing that cannot wait a day if it fails, and someone reliable to call. If your work depends on being online, planned maintenance is usually the better fit.

How much does planned IT maintenance cost?

It depends on the size of your business and what is included. Our guide to IT support costs for UK small businesses sets out the options.

Talk it through with us

If you would like to talk it through, get in touch and we will give you a plain-English view of what would suit your business.

Get in touch