Skip to content
Request a demo
EN

GControl team · Infonet Consultores5 min read

Two maintenance workers inspecting a water pump with blue pipes in a plant room

Industrial maintenance and technical service companies often live off two kinds of work at once: maintenance contracts with a fixed fee, and one-off jobs that are quoted and invoiced separately. The mess starts when the same technician, at the same site on the same day, carries out a contract inspection and a repair that the customer will pay for separately. If the hours all end up in the same pot, you won't know whether the contract is profitable or whether you're giving away extra work for free. This article explains how to separate them without duplicating tools.

Two ways of making money that behave differently

A maintenance contract is a bet: you charge a fixed amount and hope that the hours and materials it costs you over the year come in below it. A one-off job is a closed assignment: you quote, carry it out and invoice. Both need the same control (hours, materials, cost), but they are analysed differently:

Maintenance contractOne-off job
IncomeFixed periodic feeAmount quoted or of the work carried out
Analysis periodMonth, quarter or year of the contractFrom when it is opened until it is closed
RiskHours exceeding what the fee coversExecution costing more than quoted
Key questionIs it worth renewing on these terms?Did I earn what I expected?

Keeping the two in separate systems (the contract in one spreadsheet, the jobs in another) means moving data by hand and leaves gaps. Keeping them together but not telling them apart is worse. What works is a single system with a clear separation.

Every contract is a job with its own code

The simplest approach is to treat each maintenance contract as just another job, with its own code and an activity type that identifies it as maintenance. If the contract is annual, open one code per customer and year: that way each year of the contract has its own result and you can compare them.

One-off jobs have their own codes, with the relevant activity type (repair, installation, modification…). If a one-off job arises within a contract, it is still a separate job: it is quoted, approved and charged separately.

If the contract covers several sites or pieces of equipment

When a contract covers several sites or lines, you have two options: one code per site, or a single code with sections for each site. The first gives more detail; the second is simpler for the technician. Choose according to how the customer asks you for information and how you want to analyse it yourself.

The line between what the contract covers and what it doesn't

The weak point of maintenance contracts is the blurred line. If it isn't clear what is included in the fee, technicians will tend to log everything against the contract, because it's easier and avoids arguments with the customer. The result is a contract that looks loss-making and extra jobs that are never invoiced.

Some measures that help:

  • Put in writing what the contract includes: preventive inspections, number of visits, response times, materials included or excluded.
  • Give technicians a short list of what the contract does not cover, so they know when a new job needs to be opened.
  • When something outside the contract comes up, the technician should flag it before doing it, except in emergencies. The office decides whether to open a job and quote for it.
  • Review the contract hours every month: a spike usually hides work that should have been billed separately.

The technician's work report, with two lines if needed

Technicians don't have to think about accounting, only about logging things properly. If on one visit they carry out the contract inspection and an extra repair, the work report has two lines: one with the contract code and one with the one-off job code, each with its own hours. The same goes for materials: the filter from the inspection goes to the contract and the part for the repair goes to the one-off job.

To make this work in practice:

  1. The technician must be able to see that customer's open jobs on their phone.
  2. Codes are chosen from a list, not typed from memory.
  3. The job documentation (instructions, specifications) is on hand on the phone itself.

What to look at for each type of work

With everything in one system, the analysis uses the same data but asks different questions.

For contracts

  • Hours and materials consumed against the fee, by period.
  • Year-on-year trend for the same contract.
  • Contracts that consume far more than the average for their type.

For one-off jobs

  • Actual cost against the quote.
  • One-off jobs arising from each contract: if a customer generates many, that is a good customer; if they aren't being invoiced, there is a problem.
  • Time between finishing the job and invoicing it.

A practical tip: for each customer, review the contract and the one-off jobs that have come out of it together. A low-margin contract may be worth it if it opens the door to profitable one-off jobs; one with a good margin may not be if it forces you to keep someone available who bills nothing else.

This information also helps you renew contracts with solid arguments: if a contract consumes more hours each year than its fee covers, you have the work reports to prove it.

How it fits into GControl

GControl codes jobs in a standardised way by year, customer and activity type, so contracts and one-off jobs can coexist under different codes and be analysed separately or together. Work reports and materials are charged to each job, and you get its cost, income and profit. Technicians clock in and submit their work report from the mobile app, whether at your premises or at the customer's site, and they can see there the specifications and instructions attached from the office.

You can see how work reports from the mobile work and how the cost of each job is calculated.

More articles from the blog

See all

Contact

We'll show you GControl with your own jobs

Fill in the form and we'll call you to set up a free, no-obligation demo.