Note
Annual Inspection: What to Capture and Close on the Day
For a contractor running commercial solar or industrial LED installations at Thai factories, the annual site inspection is a predictable event. You know the date is coming (or you should), you staff someone to go, they do the work, and they drive back. The job should be done.
But “they went and came back” is not the same as “the inspection closed.” The difference lives in what they brought home: four specific outputs. Without all four, the work sits in a gap between field and office, producing nothing.
The inspection crew did the work. Why does the job still feel unfinished?
Most annual inspection problems do not show up on the day of the visit. They show up two weeks later.
- The customer’s facilities manager asks for a copy of the inspection report. You have internal notes. The signed report is somewhere in the technician’s bag, or still in the truck.
- Your billing team tries to raise an invoice. The job ticket says “completed” but no document has been attached. The invoice waits.
- A new technician joins the crew. The person who ran last year’s inspection left no condition notes. Nobody knows whether the reading recorded was normal or worth watching.
Each traces back to the same point: the inspection was performed but not closed. Performing and closing are two distinct steps.
What does a complete inspection record actually contain?
An annual site inspection has four outputs that matter to the business, not just to the technician on the day.
Equipment readings and test results. For solar systems this means string voltages, inverter output, and protection settings. For LED installations it means illuminance readings at representative points, control panel function checks, and a visual inspection of fixtures and wiring for signs of deterioration. The exact list depends on what was installed and what the customer’s compliance requirements specify. What matters operationally is that the checklist exists before the technician leaves the office, not after they return.
A photographic record of current condition. Annual inspection photographs are not the same as installation photographs. The installation record shows what was put in. The inspection record shows what condition it is in now: whether the mounting is still secure, whether cabling at the distribution board is undisturbed, whether any luminaire is visibly degraded. For this comparison to mean anything, the technician needs the original handover photographs as a baseline. If the site record is complete, pulling those takes thirty seconds. If it is not, the technician is making observations with no reference point.
A signed inspection report. The customer’s engineer or facilities manager must sign before the technician leaves. A report emailed later is not a signed report. An unsigned document returned with “I will get the signature next time” starts a cycle that is genuinely difficult to end. The signature happens at the site, on the day, as part of the visit structure, not as something arranged later.
An updated site record. The inspection visit generates new information: condition notes, updated contact names, equipment serial numbers that have changed, and the date that resets the next inspection clock. If that information goes into the technician’s notebook instead of the site file, it is lost the day that technician leaves the company.
Why is the closing step the one most likely to get skipped?
The technician’s priority is the technical work. The administrative close looks like paperwork that happens after the real job is done, which places the most consequential step last, where time pressure and fatigue work against it.
Two practical approaches change this reliably.
Build the close into the visit structure, not after it. The last thirty minutes of the inspection visit are reserved for uploading photos, confirming readings are in the job ticket, and obtaining the customer’s signature. Tell the customer when booking that you need a representative available at that time.
Make the job ticket unresolvable without all four outputs. If a technician cannot mark a job closed until the signed document is attached and the site record is updated, they learn quickly that the signature needs to happen before the truck leaves. One return trip is usually enough to establish the habit.
What does the inspection report need to contain for the customer to sign it?
The format the customer accepts varies by industry and by each factory’s own compliance process. The content that almost always needs to be present includes:
- Site name, address, and date of the visit
- Reference to the original installation: project number, equipment type, and installation date
- A summary of what was tested or inspected, with readings where applicable
- Observation notes: anything found in a condition different from the original installation record
- Technician name, company name, and signature
- Customer representative name, signature, and date
A report that says “system checked and found to be working normally” gives the customer’s engineer very little to sign with confidence. A report listing what was tested and what was found, item by item, is the one that gets signed on the day without a follow-up conversation. The same principle decides whether a handover document gets signed on the day at the end of an installation: an engineer signs what they can verify.
How do you know when the inspection job is actually closed?
The inspection is closed when all four outputs are in hand before the technician drives away:
- Readings and test results recorded in the job ticket, not a notebook
- Inspection photographs attached to the site record
- Signed inspection report in hand, or photographed and uploaded from the site
- Site record updated with today’s date and the next inspection due date
If any one is missing, the job is finished in the field and open in the office. Finished and closed are not the same thing, and the difference costs something every time.
FAQ
What if the customer’s engineer is not available on the day of the inspection?
Resolve this before the visit, not at the gate. Call ahead and confirm the signing authority is available. An inspection where the engineer is out produces an unsigned report and a second trip. Build signature confirmation into the booking step.
Should annual inspection photographs be kept separately from the original installation photographs?
Keep them in the same site record, tagged with the inspection date. Years from now, someone reading that record needs to know immediately whether they are looking at the installation condition or a later inspection.
Does the annual inspection reset or extend the warranty on the installed equipment?
That depends on the warranty terms in the original contract. The site record should carry a note of what warranty still applies, who issued it, and when it expires. That information belongs in the site register, not in the technician’s head and not in a folder that only one person knows where to find.
Getting the inspection done is the straightforward part. Getting it closed on the day, without a second trip, is the discipline: not a question of effort, but of whether the system requires it.
To see how Field Operation System structures inspection job orders so that nothing reaches billing without a complete record, visit /program/ or schedule a call to walk through how it works.