Proactive vs reactive AV maintenance: the real cost difference

Reactive maintenance has no monthly fee, so it looks cheaper. Its real cost builds up in five places, and only one of them shows on the service invoice.
Ádám Horváth
9 min
October 14, 2026
Team in a meeting room watching a wall-mounted display, with a conference speaker on the table

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

Reactive audiovisual (AV) maintenance is not cheaper than proactive maintenance; it only looks cheaper because it has no fixed monthly fee. Its real cost is higher, because most of it does not show up on the service invoice: IT hours, lost meetings, management time and early equipment replacement. GHT-SYS is a vendor-independent AV systems integrator based in Hungary. We also provide SLA-based maintenance for corporate clients. Yet we rarely come across a maintenance calculation that adds these items up at all. That is exactly why the idea that reactive is the cheaper model persists.

In short: Reactive maintenance looks cheaper because it has no fixed fee. Its real cost builds up in five places, and only the service fee appears on the invoice. The rest is IT time, management time, lost meetings and early equipment replacement. The operations and maintenance guide of the US Department of Energy (DOE) estimates that preventive maintenance can save as much as 12-18% on average compared with reactive maintenance. Below, you will find a simple framework for calculating your own difference.

Why does reactive maintenance look cheaper than it is?

Reactive maintenance looks cheaper because it shows only one number: the service invoice. Proactive maintenance has a visible annual fee, but you can plan for it in advance. The reactive approach costs nothing until something breaks. Then it brings unplanned spending, downtime and extra work, all at once.

Skipping maintenance therefore does not remove the cost. It defers it. The Operations & Maintenance Best Practices Guide from the Federal Energy Management Program (FEMP) of the US Department of Energy (DOE) estimates, based on earlier studies, that preventive maintenance can save as much as 12-18% on average compared with reactive maintenance. Where a facility relies heavily on reactive repairs and moves to predictive, condition-based maintenance, the guide says the savings opportunity can exceed 30-40%.

These figures are general facilities management data, not AV-specific measurements, and the guide dates from 2010. The mechanism behind them still applies to meeting rooms: a planned intervention costs less than a rushed one.

The hidden costs of reactive maintenance

Of the five places where the reactive model’s cost builds up, four never appear on the service invoice. You only see the real price when you add all five together.

  • Emergency call-out fee. This is the only item that shows on the invoice, and even this one is higher than the planned equivalent. An urgent call-out, priority scheduling and a fast-tracked fix all carry a premium compared with a visit booked in advance. The same applies to parts: with planned maintenance they arrive at the normal price and lead time, with an unexpected fault they come with a surcharge and express delivery.
  • IT time. Audio and video faults are an everyday occurrence. Lightyear is a US company that builds a procurement platform for telecoms and network services, and in October 2025 it surveyed 1,000 US workers. According to its own survey, 73% of respondents had been in a meeting with an audio or video problem in the previous seven days, and 40% find connectivity problems very or extremely frustrating. Some of these problems become tickets, and every ticket takes IT time away from something else. Recurring faults, such as meeting room audio freezing after a Teams update, usually point to a maintenance gap, not a one-off stroke of bad luck.
  • Management time. The direct cost of a boardroom outage can be several times the service fee once you count the time of the people sitting in the room. Ten people waiting twenty minutes is more than three working hours, which can easily cost more than the repair itself, and this item is not recorded anywhere.
  • Lost meetings. An outage does more than cause a delay. A decision gets put off, a client meeting is cut short. The business consequence of that can be far larger than the repair fee, and it does not appear on any invoice either.
  • Early equipment replacement. Unmaintained equipment reaches the end of its life sooner. Manufacturers also treat poor ventilation and heat as a real cause of failure: under Crestron’s warranty terms, the warranty is void if the product has been exposed to insufficient ventilation or incorrect temperatures. Cleaning fans and vents regularly is therefore part of maintenance. With regular maintenance, replacement can also be planned ahead, so it does not arrive as an unexpected capital expense.

None of these items is dramatic on its own. Together, though, they can easily add up to several times the service invoice, and they stay invisible precisely because no single line in the accounts brings them together.

Why has the reactive model become riskier in recent years?

The reactive model has become riskier because meeting room technology has become far more complex. When a meeting room had just a projector, finding a fault took a few minutes. In a hybrid meeting room today, the audio runs on the DSP, the video on the codec and the control on a third manufacturer’s processor, and each device follows its own firmware cycle.

What does that change in cost terms? Mainly the time spent finding the fault. If a platform update or an incompatibility takes the room down, the technician has to check several systems from several manufacturers before it is even clear where the fault lies. Under a reactive arrangement, that time is billed at the emergency rate, and the room stays down for all of it.

The more complex the environment, the more expensive the “we’ll fix it when it breaks” attitude becomes. Nobody is swapping a single part any more. They are working through an entire chain. At the worst possible moment.

Cost or insurance? Two ways to look at the maintenance fee

One view holds that the maintenance fee is a cost: if nothing breaks, the money was wasted. The other holds that the maintenance fee is a predictable expense, while reactive service arrives unexpectedly, always at a bad time, and brings more hidden costs than the invoice shows.

If you look only at the service fee, monthly maintenance is a line you can cut. If you look at the full operational risk, the same fee works more like insurance: it covers the cost of unplanned outages. Same number, two completely different decisions.

At GHT-SYS, we take the second view, with one addition. The maintenance decision should not be made once a fault has already happened, because by then the reactive logic is in charge and the decision becomes emotional, not financial. Maintenance belongs in annual budgeting, not in firefighting.

Where do maintenance decisions go wrong?

Bad maintenance decisions are typically made at the same four points, and all four come from an incomplete calculation.

  1. Only the service fee is counted, and management, IT and user time are left out.
  2. Maintenance is postponed because nothing has gone wrong lately, even though the fault-free period is exactly what the proactive model produces.
  3. Nobody records how many IT hours went on AV tickets, so there is nothing to compare.
  4. Maintenance only comes onto the agenda after a fault, not as part of annual planning.

On top of that, the missing items all pull in the same direction: everything you leave out of the calculation makes the reactive model look cheaper.

How can you calculate the real difference?

You can calculate the real difference without an outside expert, using a few numbers that most companies have not yet collected. The framework has three steps, and it is also where we start at GHT-SYS when a client wants a clear view of their maintenance costs.

  • Pull your AV tickets. Count the AV tickets IT dealt with over the last twelve months, and estimate the working hours they took.
  • Work out the full cost of service calls. For the last few call-outs, check whether the emergency surcharge, the IT time and the time lost to disrupted meetings are included. If they are not, the real figure is higher than the one on the invoice.
  • Move the maintenance fee to a different line. In the next budgeting round, put maintenance on the “operational risk reduction” line, not the “optional spending” line.

How much does this come to over a year? Here is an illustrative example for a mid-sized office. The figures are examples only, so replace them with your own.

ItemExample calculationAnnual impact
IT time on AV tickets18 tickets × 1.5 hours27 IT working hours
Emergency call-outs4 visits, with surchargeservice fees with surcharge
Lost boardroom time6 outages × 20 minutes × 8 people16 management working hours
Early equipment replacement1 unplanned replacementone-off capital expense
Total reactive costIT hours × internal hourly rate + management hours × management hourly rate + surcharge + replacementput this total next to the annual maintenance fee

The table does not give you a price. It shows which lines are missing from the usual calculation. Most companies only see the second line: the emergency call-outs.

There is a telling sign here as well. If nobody in your organisation knows how many AV tickets there were last year, or what reactive service cost, that in itself is information: an invisible cost cannot be tracked if nobody documents it. A well-built maintenance contract records this from the start, and we have set out the six elements of a good meeting room SLA in a separate article.

When is proactive maintenance not worth it?

Full proactive maintenance is not worth it in every environment. Where there is a single, simple meeting room that is rarely used, a comprehensive SLA can be more than the room needs, and reactive repair remains a realistic choice. The proactive model pays off most where there are several rooms, a business-critical boardroom, heavy use or a complex, multi-vendor system.

So the decision is not ideological. Is there a room where an outage carries a real business or time cost? If there is, proactive maintenance is the safer choice for that room. If there is not, the reactive model is defensible. Most corporate offices, however, have at least one such room, and often more.

The first step is a number, not a contract

You do not have to decide on a maintenance contract straight away. All you need to do is gather last year’s AV tickets, service invoices and outage times before the next planning round. If the reactive column then turns out to be the smaller one, your decision is well founded. If it turns out to be the larger one, the discussion from then on is about how much you are currently paying for not having maintenance.

Frequently asked questions

What is the difference between proactive and reactive maintenance?

Proactive maintenance is planned, scheduled work that finds most faults before they cause downtime, while reactive maintenance only starts once a fault has already happened. At GHT-SYS, we do not think the main difference is which one costs money. It is that one can be scheduled in advance, while the other arrives unexpectedly and always at a bad time.

Is proactive maintenance really cheaper in the long run?

In a business-critical AV environment, proactive maintenance is cheaper in the long run once you count every cost. The US Department of Energy’s operations and maintenance guide estimates that preventive maintenance can save as much as 12-18% on average compared with reactive maintenance; this is general facilities data from a 2010 guide, not an AV-specific measurement. The saving comes from avoided emergency surcharges, less lost time and equipment replacement that can be planned.

Why does an emergency service call cost more than a planned visit?

An emergency service call costs more because the unscheduled call-out, the fast-tracked fix and the express sourcing of parts all carry a surcharge. On top of that comes the time spent finding the fault, which can run to hours on a complex, multi-vendor system, and the IT and management time lost during the outage, which does not appear on the invoice.

When should you decide on meeting room maintenance?

The right time to decide on meeting room maintenance is during annual budgeting, not after a fault. After a fault, the decision is rushed and emotional, and it is made on reactive logic. In annual planning, last year’s tickets, service invoices and outages let you compare the two models in financial terms.

How do I show management that maintenance is worth it?

The most convincing argument for management is your own calculation: collect the AV tickets from the last twelve months and the IT hours spent on them, then add the full cost of the last few service calls, including the emergency surcharge and the time lost to disrupted meetings. You can put this total directly next to an annual maintenance fee, and management can see from your own figures which one is higher.

About the author

Ádám Horváth is the managing director, founding owner and a systems engineer at GHT-SYS.

About GHT-SYS: GHT-SYS is a Hungary-based audiovisual (AV) systems integrator. The company designs, installs and commissions integrated AV systems in Hungary and across Europe, and provides SLA-based maintenance for corporate clients in Hungary. If you would like to work out your own reactive versus proactive cost difference, book a consultation and we will help you build the calculation.

Related articles:

Sources