Note
When the Project Runs Over: Managing a Timeline Slip
Most Thai electrical contractors plan an installation by estimating the number of working days and booking the crew. The plan is usually sound. What is harder to plan for is a project that runs over its intended end date while the crew is still on site.
When a factory installation runs long, the cost spreads to invoicing, to the next job’s start date, and to the client relationship if nobody communicates early. Managing a timeline slip well means catching it early enough that options still exist, not discovering it on the last planned day.
Why Do Factory Installations Run Over Schedule?
The most common causes are access delays, material timing issues, scope additions, and task durations that run longer than estimated. Usually it is a combination.
Access delays. The factory schedules a maintenance window for the contractor to access the main panel. The window gets shortened because a production run overran. The crew has the panels up but the connection cannot be made until the rescheduled window, which is now four days away.
Material substitutions. A specific cable specification is unavailable. The locally sourced alternative requires different support spacing. Recalculating and adjusting the installation adds a day that was not in the plan.
Scope added mid-project. The factory engineer asks, while the crew is on site, whether two more circuits can be added to the same distribution board. It gets done. It adds a day, and nobody updates the job timeline.
Actual durations exceeding estimates. Running cable through an industrial ceiling on a 10,000 sqm factory floor takes longer on day one than the estimate built on a previous job in a 2,000 sqm warehouse. The crew is faster by day two. But day one does not come back.
How Do You Know the Project Is Behind?
The earliest useful signal is the gap between technician-days spent and work remaining.
Take a concrete example. You planned a project for 40 technician-days across 8 working days with a 5-person crew. On day 5 you have spent 25 technician-days. If the work is 60% complete, you are on schedule. If the work is 40% complete, you are one day behind with three days left to close a two-day gap.
Run the same check on your own numbers:
- Planned technician-days = crew size x planned working days
- Used technician-days = crew size x days elapsed
- Work remaining = (1 minus percent complete) x planned technician-days
- Days remaining = planned end date minus today
If work remaining is greater than what the current crew can deliver in the remaining days, the project is behind.
That calculation needs two inputs: a running count of technician-days used (which daily job tracking provides) and an honest estimate of what remains (which the site lead needs to confirm, not guess from memory).
Without those, most site leads discover the timeline problem on the last planned day of the project. The right moment to catch it is day 3 or 4 of an 8-day project: early enough that something can still be done about it.
What Are the Options When the Timeline Slips?
There are three options, and they are not equally available in every situation.
Add more technicians. If the project is behind because the task volume was underestimated, adding crew to the remaining days can recover the schedule. Whether this is possible depends on the board: are those people available, and can their current work shift without creating a different problem?
Adding technicians is not always faster. On tasks where coordination is tight, such as commissioning a solar inverter, additional hands do not help. Where extra crew pays off is on physically separable work: cable runs across a large floor, fixture installation along a production bay, conduit runs where teams can progress independently.
Accept the revised timeline and confirm a new end date. This is the most common outcome. The project runs two or three extra days, the crew stays allocated, and the end date moves. The critical step is confirming the new date with the client before the original date arrives, not after. A client told on Wednesday that handover is now the following Tuesday has time to adjust. A client who expected Friday delivery and receives no update will follow up on Friday, often escalating.
Defer part of the scope. If the delay is driven by something outside the crew’s control, such as a PEA grid-connection inspection that cannot be expedited, completing everything else and doing a partial handover may be the cleanest path. Not every client will accept this, but on large projects it is sometimes the right answer.
Updating the Job Record After a Slip
When the end date moves, four things in the job need to be updated:
- The revised handover date, so the system reflects what is actually expected, not the original plan.
- Technician assignments for the extended days, so those days are not accidentally allocated elsewhere.
- Payment milestone dates, if any billing was tied to a completion date. Progress billing linked to a specific project end needs to be re-confirmed with the client when that date changes.
- The start date of the next project that depends on this crew, if a dependency exists. A two-day extension here may push a confirmed start date for the following job, which needs its own client communication.
A board that shows a project ending on Friday when the site lead knows it runs to the following Wednesday is not a scheduling tool. It is a false picture that leads to decisions being made on wrong information.
FAQ
When does a timeline slip become a contract issue?
Most Thai installation contracts specify a completion date. Whether a delay is a breach depends on the cause and what the contract says about time extensions. Access delays or material issues outside the contractor’s control are typically grounds for an extension, but this needs to be documented and agreed before the original date passes. The habit of confirming revised dates in writing creates a record regardless of what follows.
Is adding more technicians always faster?
Not always. Some tasks have a ceiling based on the work itself, not the number of people. Before committing to extra crew, the site lead should identify the specific tasks that will benefit: tasks where the work divides cleanly and teams can progress without waiting on each other.
What does a slip here do to the next project?
If the extended crew is already booked for the next project’s start date, the slip at this site directly affects the next client. The sooner this is surfaced, the more options exist: moving a technician ahead to start site preparation, phasing the next project’s start around a partial crew, or communicating the schedule change while there is still enough lead time to make it manageable.
If your job orders do not show a running technician-day count against remaining work, you may not know a project is behind until the last day of the plan. The TRACE 30 program builds this visibility into the board so the slip is visible early enough to act on.