Note
Maintenance Revenue Starts at Installation
Contractors who install electrical work in factories often treat maintenance as something to figure out later. The install is the job. When a site is signed off, the next project is already waiting. Maintenance revenue is, in theory, recurring and good margin. In practice, most operations struggle to scale it past the handful of sites where someone still remembers the details. The reason is nearly always the same: the information needed to run maintenance well was never captured in a form that travels.
Why maintenance visits often start from scratch
When a factory calls eighteen months after an LED retrofit and reports a section that is flickering, the coordinator needs to answer several things before a technician goes out:
- What exactly was installed in that section
- Whether the work is still under warranty, and who bears the cost if it is
- What photos were taken during the original installation
- Who handled the job, and what the signed handover date was
If none of that is recorded in a findable place, the coordinator pieces it together from chat history, email threads, and whatever the technician who did the install can recall. At one site, this takes twenty minutes. At fifty sites, it becomes a part-time job. At a hundred, it stops happening reliably.
This is not a failure of effort or memory. It is a structural problem: the information existed at the moment the job was completed, and nobody captured it in a form the rest of the team can reach.
What does installation data actually unlock?
The records from installation create the conditions for maintenance that works at scale. Specifically:
Warranty status. The site register needs the signed handover date to calculate when coverage expires, which is why the register entry is written at the moment the handover is signed. Without a recorded date, every warranty question requires locating the original document and reading it. Across sixty or eighty sites, that search takes long enough that people stop doing it properly and start guessing.
Inspection scheduling. Factory electrical safety regulations require periodic inspection. Knowing when a site was signed off determines when the next inspection falls due. If that date is not connected to a staffed calendar, inspection rounds become ad hoc rather than planned, and sites fall through between rounds.
Scope for return visits. A technician returning to a site they did not install needs to know what was done. Without a scope record and photos from the original job, they are starting from incomplete information. What appears to be a new fault may be how something was configured. What looks unusual may be exactly what was specified.
Billing clarity. Doing work on a site without knowing whether it is under warranty creates disputes. If the handover document is easy to find, the dispute resolves in minutes. If it is not, you tend to absorb the cost to avoid arguing without evidence.
An example in round numbers
Take a contractor finishing eight projects a month. By the end of month twelve, they have around a hundred active sites. If factory electrical inspections run annually, that is roughly eight inspection windows coming due every month in year two, at about the same rate as new installs.
Each inspection is a short job, perhaps half a technician-day. Eight a month is four technician-days of recurring, schedulable work. At twenty per month, it is ten technician-days. None of that is billable without knowing, for each site, when the inspection is due, what the original scope was, and who to assign.
If that information is scattered across old email threads, the coordinator can handle the sites they remember well. The rest slip. The ceiling on maintenance revenue is not demand. Most factory clients in electrical work are open to a maintenance relationship with the contractor who installed the system. The ceiling is operational: how many sites one coordinator can track without a system behind them.
What needs to be captured, and when?
The useful window is narrow. During the install and at handover, the information is directly available. After handover, gathering it requires contacting the client or the original technician and waiting.
At minimum, closing a job should record:
- Scope of work: what was installed, how many units, which areas of the site covered
- Signed handover date: the date the customer’s engineer signed, not the date the crew finished
- Installation photos: at least one per section, plus any conditions worth noting
- Any agreed terms specific to this site
The critical point is when this happens. If filling in these fields is optional or treated as a separate task to complete later, it tends not to happen. If the system requires them before a job can be marked closed, they get filled in. The handover is the right moment to enforce this, because the technician is on site, the photos are in their phone, and the customer’s engineer is present to sign. Nothing needs to be reconstructed from memory.
FAQ
Does this apply to C&I solar as well as LED retrofit?
Yes. For solar installations, the installed capacity, the grid connection approval from PEA or MEA, the commissioning date, and the inverter configuration all matter for maintenance and warranty tracking. The inspection window for solar also tends to be shorter: shading, soiling, and inverter efficiency drift become visible within the first operating year. The principle is the same in both cases: the data captured at installation determines what the maintenance team can work from later.
We already have handover documents filed somewhere. Is that enough?
Filed documents solve part of the problem. The question is how long it takes to find and read the right one when a call comes in. A site register that draws from closed jobs makes that a thirty-second lookup rather than a ten-minute search through email folders. For sites where records are good, the work is moving them into a searchable format. For sites where records are patchy, the next best step is a brief visit to document current conditions before any maintenance work begins.
Is this mainly about software, or about process?
Both, in that order. The process is the rule: a job is not closed until the data is recorded. The system enforces the rule and stores the data in a form the coordinator can reach quickly. Without the process, any software produces a database that is incomplete in exactly the same way the email folder is incomplete. Software does not replace the decision to capture the information. It makes that decision part of closing the job.
Maintenance revenue is available to most contractors who install factory electrical work. The clients are there. The inspection cycles are mandated by regulation. What determines whether a contractor can capture that revenue reliably is whether their operation can track a hundred sites without losing the details. TRACE 30 closes jobs in a way that builds the site register automatically, carrying the completion date, warranty expiry, and next inspection date forward from each signed handover. If you want to see how that works with your current project volume, the program page has the details, or you can schedule a call.