Revenue leakage in installation companies

Revenue leakage in installation companies is work that was carried out, material that was used or a contract right that exists, without it ever becoming an invoice. The largest leaks usually sit not in the big projects but in the daily flow: job sheets that are never invoiced, material from the van that never makes it onto the sheet, maintenance contracts that go unindexed for years, and call-outs booked as contract work when the cover does not allow it. Each case is worth tens or hundreds of euros. Over a year and thousands of job sheets, it adds up to six figures.

This article describes the patterns of revenue leakage in installation companies as they occur in practice: where it happens, why it keeps happening, and how to measure it. How to monitor it structurally and continuously is covered in Revenue Intelligence for installation companies.

Why do installers have so many small leaks?

An installation company has an unusual ratio between the number of transactions and the value per transaction. Alongside projects worth hundreds of thousands or millions sit thousands of small jobs a year: call-outs, maintenance visits, small modifications, replacements. Each of those jobs passes through the same chain: report, scheduling, execution, job sheet, processing, invoice. Each step is done by someone different, often in a different system.

On a EUR 500,000 project, someone looks at every stage payment. On a EUR 180 job sheet, nobody looks unless something goes wrong. And that is exactly why small leaks stay unnoticed for so long: nobody is looking, and the amount per case is too small to raise the alarm.

Where does an installation company leak revenue?

1. Job sheets that never become an invoice

The engineer completes the job sheet in the app. The sheet goes to the office, or into a queue in the ERP, or to the planner who needs to check it. Somewhere along that route, some of them get stuck. Because it shows as complete in one system, everyone assumes it has been dealt with. Because it was never flagged as billable in the other system, it never reaches an invoice.

This is the most direct form of leakage and at the same time the easiest to measure: count all completed job sheets for a month and find, for each, an invoice line or an explicit note that it falls under a contract. The general pattern is called forgotten invoicing, and how to trace it in any business is covered in how do you find forgotten invoices.

2. Hours that never make it onto the sheet

Travel time, waiting time, the second engineer who came to help for a while, the extra half hour because the installation was hard to reach. Engineers often fill in the job sheet with what they think is reasonable for the customer, not with what they actually did. That is well meant, but it is a pricing decision taken in the wrong place.

A simple check: compare the hours on a week's job sheets with the hours worked according to the time registration or the vehicle tracking. Not all of the difference is leakage, since it includes training and workshop time, but a structural gap of an hour per engineer per day is a signal.

3. Material from the van

Engineers carry stock in the van. What they use from it should go on the job sheet. In practice that does not always happen: a coupling, a length of pipe, a seal, a fuse. Too small to write down, especially if the job sheet app needs five taps to do it.

You measure it through stock: compare, per period, what was replenished in the vans with what was invoiced on job sheets or booked as contract material. The difference consists of breakage, loss and material that never made it onto the sheet. That last part is often the largest.

4. Call-outs outside the cover

A customer with a maintenance contract calls about a fault. The planner sees there is a contract and books it as contract work. But the contract may cover only labour and not parts, only faults during office hours, or only the installation that existed when the contract was signed. The part outside the cover is not invoiced because nobody checked the cover.

This leak arises because the cover is written in the contract while the decision sits with the planner or the engineer, who does not know the contract. The fix is to make the cover visible on the job sheet, or to have someone check afterwards.

5. Maintenance contracts without indexation

Maintenance contracts often run for years on automatic renewal. The price was set when the contract was signed. If nobody applies the indexation every year, the contract gets cheaper in real terms every year while wages and material costs rise. After a few years you are delivering service below cost without knowing it.

This is the most underestimated leak, because it compounds. A missed indexation of 3 percent costs 3 percent this year. Missed two years running, it costs over 6 percent next year, and it stays that way until someone corrects it. The mechanism is worked out in revenue leakage from missed price indexation.

6. Contracts that do not grow with the installation

A customer extends their installation: an extra circuit, a second air handling unit, a larger security system. The project is invoiced properly. But the maintenance contract stays at the old scope. From that moment the engineer maintains more than the contract covers, without the customer paying more.

7. Installations that never come under contract

The handover of a project should come with an offer for maintenance. Who makes that offer is often not defined. The project manager is busy with handover, the service department does not know the project is finished, sales does not have it on the list. The result: installations visited only when they break down, with no standing contract. That is missed recurring revenue, and often a worse situation for the customer too.

8. Variations through the main contractor

On projects where the installation company is a subcontractor, variations run through the main contractor. The installer carries out a change at the request of the main contractor's site manager, who later submits it to the client as a variation. Whether the installer ever gets its share invoiced depends on how well it recorded and submitted the change itself. The same patterns apply here as in revenue leakage in project businesses, with an extra link in the chain.

Worked example

Worked example: suppose an installation company with 35 engineers and EUR 6 million in revenue. The company carries out 7,000 job sheets a year and has 500 maintenance contracts with an average value of EUR 1,400 a year.

That is over 2.5 percent of revenue. The individual assumptions are modest: a quarter of an hour a day, ten euros of material, one percent of job sheets. It is precisely those modest assumptions that make the leak hard to take seriously. Nobody is going to challenge an engineer over fifteen minutes.

The figures are illustrative. There is no reliable average for leakage in installation companies. The only way to know your own figure is to measure it.

Why does the leakage persist?

Engineers are managed on productivity, not on completeness. An engineer who does many jobs a day is seen as good. An engineer who records every job in full is not necessarily. If the job sheet app is cumbersome, the engineer chooses speed.

The office only sees what comes in. It invoices the job sheets it receives. What does not come in, it does not see. It has no way of knowing a sheet is missing.

Contracts are invoiced, not managed. The contract sits in the system with an amount and an invoicing frequency. Whether the amount still matches the installation and the market price, nobody asks.

Every leak is small. As long as nobody calculates a total, no single leak feels like a priority.

A checklist for this week

You can estimate the size of the leakage in your own company in a few days. These seven checks cost little and give you a picture straight away.

1. One month of job sheets against invoices. How many completed sheets have no invoice line and no contract note?
2. Job sheet hours against time registration. Take one week. How many hours were worked and how many are on job sheets?
3. Van stock against invoiced material. Take one quarter. How much was replenished, how much was processed on job sheets?
4. Contract prices against the start date. For what share of contracts is the price the same as when the contract was signed?
5. Call-outs at contract customers against the cover. Take twenty call-outs. How many fell entirely within the cover?
6. Completed projects against maintenance contracts. How many installations handed over in the past year have a contract?
7. Extensions against contract changes. On how many extension projects was the maintenance contract updated?

Scale the result of each check up to a year. That gives you a first, rough estimate that is good enough to decide where to start.

What do you do about it?

Make the job sheet easier, not stricter. Add standard materials with one tap, fill in travel time automatically from the schedule, add a mandatory field for "within contract yes or no". The easier recording is, the more complete it becomes.

Put the contract cover on the job sheet. The engineer and the planner should see what the contract covers when they open the sheet. Then the decision is taken at the right moment.

Schedule indexation as a fixed event. Once a year, on a fixed date, for all contracts, with notice to the customer. Not per contract on its anniversary, because that gets forgotten.

Make handover and contract a single step. No project is closed until a maintenance offer has gone out and the outcome has been recorded.

Check the job sheet flow weekly. A simple count: sheets completed this week, sheets invoiced or booked as contract work this week. Any difference is investigated the same week.

For installation companies that also run maintenance and facilities management as a main activity, with SLAs and performance contracts, other patterns come into play. Those are covered in revenue leakage in technical services.

Frequently asked questions

What is the biggest source of revenue leakage for installers?

It differs by company, but in many cases it is the maintenance contracts: indexation that was never applied and contracts that do not grow with the installation. Those leaks recur and compound. Job sheets without an invoice are often the most visible, but not always the largest.

Should I make engineers responsible for complete recording?

Engineers are responsible for what they record, but the organisation is responsible for how easy that is. A cumbersome app produces incomplete sheets, however often you ask. Start with the process, not with the engineer.

Isn't it unfriendly to customers to invoice small things?

It is a choice you are entitled to make deliberately. Giving away a small part can be good for the relationship. But then you want to know how much you give away that way, and you want the choice to be made by the organisation, not by each engineer on each job.

How often should maintenance contracts be indexed?

As often as the contract allows, usually once a year. More important than the frequency is that it happens consistently. An annual indexation for all contracts on one fixed date is easier to sustain than doing it contract by contract.

Can I measure this without new software?

Yes. For a first measurement you need exports from your job sheet system, your invoicing and your contract management, and a spreadsheet. Automation becomes worthwhile when you want to do it continuously and the number of job sheets is too large to check by hand every month.