Note
After the Handover: Tracking the Return Trips Nobody Records
The handover is signed. The customer shook the foreman’s hand. The job is closed and the invoice is raised. Three weeks later, a technician drives back out because one LED driver in the production hall is flickering. Nobody logs it. Two hours on site, two hours of travel. The trip never makes it into any project file.
This happens continuously. For a contractor running four to eight active projects at any time, small unrecorded return visits accumulate into a real share of weekly technician-time. These trips are not warranty callouts. They are not punch list closes. They are informal responses to small post-handover issues that fall between those two categories.
That gap has a cost, and most contractors have not measured it.
What counts as a follow-up trip?
A follow-up trip is a return visit to a closed site, triggered by something small, that does not reach the threshold of a formal warranty callback. Common examples:
- A customer message saying one fixture looks dimmer than the others
- A request to adjust an inverter parameter the factory team does not have access to
- A cable entry that needs re-sealing after the first rainy season
- A conduit run that has worked loose from a wall clip
- An inverter event log the factory’s maintenance engineer requested
None of these typically trigger the formal warranty process. But all of them send a technician somewhere.
They do not get tracked for the same reason other informal work does not get tracked: it feels too small to justify paperwork. The foreman calls a technician. The technician goes. The issue is sorted. Nobody opens a job order for a two-hour trip that does not need an invoice.
That reasoning is understandable and consistently expensive.
Why does an untracked return trip actually matter?
Lost time is the obvious cost. A technician spending four hours on an unscheduled return is not available for the project they were assigned to that day. If the trip is not visible in the schedule, the project manager plans as if that technician-day is free. When the technician does not arrive at the project site, someone improvises.
Less obvious but more serious: an untracked trip creates a gap in the site’s documentary history. If the customer raises a defect claim six months later and you send a technician to investigate, there is now a prior visit with no record. What did that technician touch? Did the adjustment they made on the informal trip cause the later fault, or clear an issue that had been building? You cannot answer, because the trip was never logged.
This ambiguity runs in both directions. It can expose the contractor to liability they do not deserve. It can also remove evidence that they acted responsibly and found nothing wrong at the time.
A site with a gap in its visit history is harder to defend.
How many return trips is your operation actually running?
Most contractors who have not tracked this have no clear picture of the total. A useful starting point is a direct question to the team: in the last four weeks, how many times did a technician return to a site already closed, for something not logged as a warranty job?
The honest answer is usually higher than expected.
Worked example: A contractor with 18 technicians closes six projects in a typical month. Each project generates, on average, one informal return trip in the first three months. Each trip takes half a technician-day including travel. Over a quarter, that is 18 return trips at half a day each: 9 technician-days of invisible work in three months. For a business that tracks technician utilisation by project, those days appear nowhere. They belong to no project and generate no record.
At that scale, the question is not simply about documentation. It is a resourcing question. Should the contractor account for this time when planning project capacity? Should some of these trips be billed? Without the data, neither question can be answered accurately.
What does a proper record for a follow-up trip need?
A return trip does not require the same documentation as a new installation, but it needs something:
- The date, site, and technicians present
- What triggered the visit (customer request, technician observation, scheduled check)
- What was checked, what was found, and what was done
- At least two photographs: the condition as found, and the state after any action
- A note on whether warranty coverage was relevant to what was found
This record does not need to be long. A few lines and two photos, attached to the site’s record, are enough. The point is that the visit is visible in the site’s history, what happened is clear, and the next person who looks at that site can see it without calling the foreman.
If the visit reveals something under the installation warranty, log it as a warranty visit and update the warranty record. If the issue is outside warranty or was caused by something the customer changed, note that.
FAQ
Does every informal trip really need a record?
There is no useful lower limit. Even a 30-minute visit where nothing changed deserves a note: technician visited, checked X, found no fault, no action taken. That single line is more useful than a blank record if the customer later claims a fault existed on that date. Documentation does not need to be proportional to time spent; it needs to exist.
What if the foreman responds without the office knowing?
That is the gap. The fix is not to slow down the foreman’s response. It is to make logging the visit part of how the job is closed, rather than an extra step on top of it. If the phone the foreman already carries supports a job close format, two photos and a brief note takes five minutes after leaving the site.
Do follow-up trips affect the warranty period?
The warranty period runs from the handover date, not from the most recent visit. But a return trip that identifies and addresses a warranty-relevant issue sets a record of when the issue was known and what was done. That record is useful if the same issue appears again later and the question becomes whether it was the same fault.
Bringing informal trips into the visible system
A closed site should have a complete visit history, not just the installation record and the handover document. Any return visit, regardless of size, belongs in that history. The practical case is not complicated: the information already exists in the foreman’s head after every trip. The gap is between that knowledge and the file.
If your current setup makes it possible to log every site visit from a phone and see every closed site’s full visit history from one screen, that is what a complete record looks like. If it does not, the TRACE 30 program is built to close exactly this gap: job closes from the phone, attached to the right site, visible to whoever holds the owner’s screen. You can also schedule a call to walk through how that works for your operation.