Note
When the Shutdown Window Ends With Work Still Open
A factory shutdown window is not flexible. When the factory returns to production, outside contractors have to leave, whether the work is finished or not. For solar and LED installations in Thai factories, this situation is more common than most contractors plan for. A six-hour window turns out not to be enough because the conduit routing takes twice as long, or the customer’s engineer arrives late to witness a test, or the panel count differs from the drawing.
When the crew leaves the site with work still open, the question is not whether a second session is needed. It is how much time that second session will spend reconstructing what the first session left behind, before anyone picks up a tool.
Why Factory Windows Run Over
A planned maintenance window at a Thai factory is typically four to eight hours, and it is not flexible. What most contractors underestimate is how often the usable portion is shorter than the nominal time. Safety inductions that run long, factory engineers who arrive late to witness tests, equipment that has to be isolated twice because a handover was missed: all of these eat into the window without touching the installation itself. A six-hour window becomes four hours of actual work time, applied to a task list sized for six.
This is not failure. It is normal in factory electrical work. The problem is what happens next.
What Does “Leaving Work Open” Actually Cost?
The most immediate cost is reconstruction time. A crew returning two or three days later, possibly with different technicians, faces the same question at the start of every window: where exactly did the first session stop?
Without documentation, they reconstruct this through memory and inspection. The foreman calls whoever was on site. The crew walks the cable runs looking for junction points. Someone scrolls a chat thread. In a four-hour window, thirty minutes on reconstruction is time already paid for, spent again.
Two other risks compound this:
- Scope uncertainty. “Started but not finished” means different things. Did the crew pull the cable through and leave it unterminated? Terminate one end only? Terminate both ends but not test? Each requires a different next step, and none is recoverable from a note that says “cable runs mostly done.”
- Materials on site. Factory floors are active. What was left between sessions may not be where the second crew expects it. Without a precise record, that gap surfaces on arrival, with the window already running.
Both costs arrive before a single new task begins.
What Has to Be Captured Before the Crew Leaves?
The close-out routine at the end of an interrupted session should produce a snapshot that a different crew can brief from in fifteen minutes.
That snapshot covers:
- Tasks completed in full. Specific named items: which cable runs are terminated and tested, which sections of conduit are run and fixed.
- Tasks started but not finished. What was done, what remains, what the next step is. “DB section 2: upper tier terminated, lower tier unterminated, test pending” is useful. “Most of DB section 2” is not.
- Tasks not yet started. So the second crew can check the remaining list against the available window before anything starts.
- Photos of every open state. Unterminated cable ends, conduit entries not yet sealed, DB sections mid-work. Working photos for the next crew, not the customer.
- Materials on site. Count, type, and location. If the factory does not allow materials to be left between sessions, this becomes a take-back list.
- Customer contact for the second session. Who at the factory to notify on arrival, and whether the same engineer is available to witness tests.
How Does the Second Crew Use What Was Captured?
The difference between a second session that starts clean and one that starts from scratch is whether the incoming crew reads a state snapshot or assembles their own.
A crew with a task list, session photos, and a materials note begins actual work within ten to fifteen minutes of the window opening. They know which cable runs are ready for termination and which still need to be pulled. They know the untouched DB section is exactly that.
A crew without context spends thirty to forty minutes on assessment the departing crew already did. In a four-hour window, that is a costly start.
When session documentation exists, the second session is a continuation. When it does not, it is a restart.
What Changes When Session State Lives in the Job Record?
Most field teams capture end-of-session state in a group chat. The problem is that a chat thread is not a job record. It mixes updates from multiple jobs, does not survive the crew member leaving the company, and gives the owner no view of which open jobs are mid-session.
When session state lives in the job order, the owner sees something the chat never shows: not just “job open” but “job in session two, seven tasks in progress, second window confirmed for Thursday.” That is a scheduling input. It tells whoever books the next crew day what the site needs, without a call.
A job with two partial sessions open is a different business risk than a job on its first day. That distinction matters on Monday morning when the owner is looking at the board.
FAQ
Is session documentation different from the photos we take for handover?
Yes. Handover photos show the finished, accepted state: clean installation, labeled correctly, the work as the customer receives it. Session photos are working documentation: cable ends mid-pull, open junction boxes, DB sections half-populated. They are for the next crew, not the customer. A job that is properly documented through to close will have both sets, taken at different stages for different purposes.
What if the factory will not let us leave materials on site between sessions?
Then the materials note at session end becomes a take-back list. Each item noted with quantity, so the incoming crew is briefed on what is coming with them and can confirm it is all present before the window opens. The inability to leave materials on site makes the materials record more important, not less, because any gap discovered after arrival is time inside the window.
What if the next step depends on a factory action before we can continue?
Mark it as “waiting: factory action required” with a description of what is needed and who owns it. This is no different from a punch list item on the customer’s side. The second crew should not plan to close that task without first confirming the factory action was taken. Putting that check into the session plan prevents the crew arriving to a blocked item with the clock running.
If your current setup has no structured place to hold session state between visits, and what the crew leaves behind lives only in a chat thread, the TRACE 30 program page describes how job orders carry both job-level and session-level documentation through to close. If you want to talk through how this applies to the factory installation work you run, you can schedule a short call.