Note
When the Site Lead Can't Come Back Mid-Project
A four-week factory LED retrofit is in its second week. The lead technician collapses at the site on Tuesday with a serious illness and is admitted to hospital that evening. The factory is in Rayong. The crew has been on the road since Monday. The project is roughly halfway through its planned scope. A replacement needs to be on site by Thursday.
What happens next depends almost entirely on what the first technician had written down before Tuesday happened.
What a Site Lead Actually Carries
A site lead on a factory installation carries more than their tools. By day three on a new site, they have accumulated knowledge that exists nowhere else in the business.
Physical layout decisions. The electrical drawings are from the survey, not the build. During installation, the crew finds the actual cable routes are six metres longer than planned, one distribution board is in a different room from the drawing, and two zones need different fixture heights because of a beam. The lead handles these decisions on site. None of them are in the original job order.
Relationship context. The factory’s electrical supervisor, who controls access to the MDB room, has a shift that ends at 15:30. He and the lead have worked out an informal arrangement: the crew completes that section before 14:00 so he can inspect before leaving. His name and number are in the lead’s phone, not in the job file.
In-progress status. The job order shows the scope. It does not show which circuits are complete, which are halfway through, and which are waiting on a part that arrives Thursday.
Informal scope additions. On day four, the production manager asked to add two fixtures in the packaging annex. The lead made a note in his pocket and got pulled away before the message reached the office.
This is what the replacement cannot reconstruct from the job order alone.
Why Does a Mid-Project Handoff Cost More Than Day One?
Bringing someone new into a project on day one is manageable. The scope is in the job order. The site is fresh. Every decision still lies ahead.
Bringing someone new in on day twelve of a twenty-day project is different. Decisions have already been made. Work is started but not finished. The customer has expectations set by conversations the replacement was not part of. Every open question now has history behind it, and most of that history is not written down.
A replacement who arrives without a handoff has two choices: move slowly while figuring out what was already decided, or make assumptions and risk undoing completed work. Either costs time a fixed-end-date project cannot absorb.
What Does a Replacement Actually Need to Start Moving?
If the original lead kept records in the job order, the replacement can start with:
- A photo log of completed circuits and confirmed fixtures, captioned by zone and date
- A written note on each open circuit: what stage it is at and what is needed to finish it
- The name of the factory contact the crew has been working with, and what was agreed about access
- Any scope additions that were discussed but not formally confirmed in writing
The first three items come from a well-structured job order if each day’s work was closed into it. The fourth is the dangerous one. If informal additions were discussed but not confirmed in writing, the replacement walks into a situation where neither they nor the factory contact has a clear shared record. The scope confirmation discipline matters most in the hours before the original lead becomes unavailable.
How Does a Day-End Record Change the Outcome?
The scenario above looks significantly different if the job order is kept current daily rather than updated at project close.
At the end of each working day, the lead closes the day’s progress into the record: photos of completed zones, notes on open work, and a copy of any scope-addition message. Five to ten minutes per day, under two hours across a twenty-day project.
When Tuesday happens, the replacement opens the job order and sees which zones are done (with photos), what is open, and what the crew was planning for Wednesday. The physical walk-through on Thursday morning becomes a confirmation, not a full reconstruction. A handoff conversation that would have taken four hours becomes forty minutes.
A Worked Example
A warehouse LED retrofit: 200 fixtures across five zones, planned across four weeks with a six-person crew. The lead records progress every evening using the job order on their phone: zone photos, open items, and the day’s decisions.
On day fourteen, the lead is suddenly unavailable for the rest of the project.
The replacement reviews the job order before travelling to site. Zones A and B are complete (with photos). Zone C has 60 of 70 fixtures hung, waiting for one switchboard connection. Zone D has wiring pulled but no fixtures installed. Zone E has not started.
The replacement travels to site on day fifteen with a clear task list. No zones need to be re-inspected to understand their current stage. The factory’s electrical supervisor, whose contact details appear in the job notes from day two, receives a call the afternoon before. The project runs three days late instead of the ten to fourteen days it would without the records.
The difference is not the absence. It is what was documented before it.
FAQ
How quickly can a replacement be productive if the job order is current?
If photo records and progress notes are current as of the last working day, a replacement can be briefed in under an hour and productive within half a day of arriving on site. Without current records, the same briefing typically requires a full site visit that produces no installation work, adding a lost day before the replacement can begin anything useful.
What if the replacement has never worked on this site type before?
A replacement who knows how to install the system but has not visited this factory needs two things: site-specific context (contacts, access, what is already in place) and technical context (what was changed from the original drawings). A well-kept job order handles the first. The second requires the lead’s direct notes or a brief call with the lead if they are reachable, even for fifteen minutes.
Does the customer need to be told?
In most cases, yes. A factory on a planned shutdown window will notice a different crew lead on day fifteen. Telling them directly is better than letting them work it out. The message is short: a team member has a medical issue and the project continues with a temporary lead. A project that stays on schedule under a different face is not a problem. Days lost without explanation is.
If your job orders show scope but not progress, this scenario is more likely to cost two weeks than two days. The TRACE 30 program builds daily progress records into job orders by default, so the job stays recoverable regardless of who is on site. Book a short call to see what that looks like for a factory installation business.