Note
A Site Register That Survives the Install Team Moving On
The install team finishes the work, the handover document gets signed, and everyone moves to the next project. Six months later, the maintenance coordinator needs to know whether Site 14 is still under warranty. Nobody is certain. The technician who did the install has since worked on a dozen other sites. The foreman has the handover document somewhere, probably attached to an email.
This gap shows up in almost every contractor’s operation once the project count gets past a certain point. Individual sites are manageable when you finish them. The problem is the accumulation. A business doing eight to ten projects a month has over a hundred active sites within a year. Knowing what is at each site, who is responsible, and what the current obligations are is not something you can carry in your head.
A site register handles this. But a useful one requires specific thinking about what goes in it and when it is written.
What is a site register for electrical installation work?
A site register is a written record of what was installed at each site, what was tested, when the work was completed, and what ongoing obligations come with it. It is not the same as the handover document, though they are closely related. The handover document is what you give the customer’s engineer to sign. The site register is what your business keeps.
For a Thai contractor doing factory electrical work, the register typically covers:
- Site identity: client name, site name, address, and the facility contact
- Scope summary: what was installed and which zones or areas were covered
- Key equipment: make, model, and serial number for major items
- Completion date: the date the handover was signed, not the date the work stopped
- Warranty expiry: calculated from the signed handover date
- Next inspection date: the annual date required under Thai electrical safety regulations
- Assigned maintenance contact: who owns this site going forward
A single row in a shared spreadsheet, filled in correctly every time, does the job. The contents matter more than the format.
Why does site information not survive naturally?
Three patterns come up consistently.
First, the install team and the maintenance team are often different people. In a contractor running eight to forty technicians, the person who wired the panels is not necessarily the one who returns twelve months later for the inspection. If the knowledge lives only with the installer, it does not transfer.
Second, the handover document stays with the customer. This is correct, but it means your copy is sitting in an email or a folder somewhere. Finding the answer to “is Site 22 still under warranty” requires locating the right handover document and reading it. Across sixty active sites, this is not a practical way to work.
Third, completion dates and warranty start dates often get confused. Some contractors count warranty from when the main installation work was done. The customer counts from when they signed. If the register does not record the signed handover date specifically, disputes about coverage become routine, because the clock that runs from the signed date is the one the customer counts from.
When is the right time to create the register entry?
When the handover is signed, not before.
Using the signed handover as the trigger means the entry is always accurate: the completion date is the signed date, the warranty runs from there, and the inspection anniversary calculates correctly. It also gives the entry discipline. The handover is already a required step. If updating the register is part of closing a job, it happens. If it is a separate task someone completes later, it tends not to.
Tying the entry to the handover step removes the deferral option. The job does not close without the register entry.
What happens when the register is not there?
The costs are mostly invisible until something goes wrong.
A maintenance call arrives for a site. The technician does not know whether the warranty covers the repair. They call the foreman. The foreman is at another site. Nobody knows without research, and the handover document is not easy to locate quickly. The technician does the work and the billing question is resolved with some friction afterward.
Or: the annual inspection round starts. The coordinator works from a list of known sites, but three sites from eight months ago are not on it because they were completed but never registered. Those sites miss their inspection window.
Or: a client asks when their warranty expires. A thirty-second question takes twenty minutes to research and comes back with an apology.
None of these are dramatic failures. They are the kind of friction that accumulates over a year and makes a business feel harder to run than it should.
Does the site register connect to inspection planning?
It should, and this is where the register becomes genuinely useful rather than just a record-keeping exercise.
If the register includes the next inspection date for each site, the annual round can be planned and staffed in advance. For a contractor with sixty or more active sites, knowing in November that eleven sites are due in March, eight in April, and seven in May means staffing can be arranged before the busy season begins. The alternative is discovering the load in late February, with no room to adjust.
The calculation is simple: one year from the signed handover date, adjusted for any regulatory grace period. The difficulty is not the arithmetic. It is making sure the date is recorded when the job closes, not reconstructed later from documents that are hard to find.
FAQ
What is the difference between a handover document and a site register?
The handover document is given to the customer’s engineer on completion and signed by them. It confirms what was installed and what they are accepting. The site register is your business’s internal record, built from the same information and kept for your own reference, maintenance planning, and warranty tracking. They are companions, not substitutes. One leaves the building; the other stays.
How many fields does a useful site register actually need?
Seven to nine fields cover most situations: site name, client contact, scope summary, completion date, warranty expiry, next inspection date, assigned maintenance contact, and a notes field for anything unusual. More than twelve fields and the register tends to fall behind, because updates become burdensome enough to skip.
How does TRACE 30 handle the site register?
TRACE 30 builds the site register from closed jobs. When a field team submits a signed handover through the system, the completion date is recorded, the warranty expiry is calculated, and the next inspection date is set. The inspection calendar then raises job orders as dates approach. The register is a result of closing jobs correctly, not a separate administrative task.
If your business has a site register that has fallen behind, or has never managed to keep one current for more than a few months, the TRACE 30 program is built to solve this at the point where it actually breaks: the transition from installation to maintenance. Schedule a call to see how it works against your current project load.