Note
Multi-Day, Multi-Technician Projects on One Board
Most scheduling problems in Thai factory electrical contracting do not come from having too many jobs. They come from the format those jobs take: projects that run four to ten technicians across five to fifteen working days, often overlapping with each other and rarely finishing exactly when planned.
A board built to track which jobs are active cannot answer the question that actually matters day to day: which technician is on which site tomorrow, and when do they come off it?
Why do multi-day projects break simple scheduling?
A single-day call is easy to track. You assign a technician, the job happens, and they are available again the next morning. The assignment is correct at dispatch and stays correct at close.
A project spanning multiple days is different. You assign four technicians to a solar rooftop install at a factory in Pathum Thani, estimated at eight working days. On day three, two of those technicians hit an unexpected problem with the structural mounting and need an extra day on that task. On day five, the factory closes roof access for a safety audit and loses a full day. The project now runs to day ten.
At every one of those changes, the original assignment is out of date. Not wrong enough to stop work, but wrong enough that any other project waiting for those technicians will be planned incorrectly. If the foreman adjusts in their head and nobody updates the board, the board becomes a record of where people were supposed to be two weeks ago.
What does a multi-day project board actually need to show?
A board tracking multi-day projects needs to answer three questions clearly, without calling anyone:
- Which technicians are assigned to which site today, and for how many days going forward?
- Which technicians are expected to come off a project, and when?
- Which technicians are unassigned, and from which date?
The third question is the one most often missed. A technician finishing a project on Thursday is not “available from Friday” until someone updates the board to reflect that. If the update never happens, they disappear from view: still showing as assigned to a project that is now closed, invisible to anyone looking for free capacity.
In a business running two or three active projects, this happens to one or two people every week: real capacity that the board cannot show. Counted properly, that is several technician-days a month that were paid for and never sold.
How is this different from just listing active projects?
Consider this example. A contractor is running three projects at once:
- Solar rooftop, 300 kWp, Samut Sakhon (5 technicians, days 1 through 8)
- LED retrofit, large factory, Ayutthaya (3 technicians, days 3 through 9)
- LED retrofit, medium factory, Nonthaburi (2 technicians, days 7 through 10)
A list showing those three project names says ten technicians are committed through day ten. That is accurate the day the plan is written.
Now the Samut Sakhon job finishes early, on day six, because the structural work was simpler than estimated. Three of the five technicians are free from day seven. The Ayutthaya job runs over and will not close until day eleven.
A board tracking project status tells you: two projects still active, one closed. It does not tell you that three specific technicians are free on days seven and eight, or that the Ayutthaya crew is committed until day eleven. The information that should drive the next dispatch decision is nowhere on the board.
A board tracking people, not projects, makes both facts visible the moment someone records the updated completion dates.
What does a people-first board look like?
It does not need to be complicated. A grid with one row per technician and one column per working day covers most businesses. Each cell shows the site the technician is assigned to, or sits empty.
For multi-day projects, this means a block spanning multiple columns for each assigned technician. When a project runs long, extend the block. When it closes early, shorten it. The unassigned cells that result are immediately visible without any extra step.
Three entries the board needs for every active project:
- Start date: the first day any technician from this project is on site
- Estimated end date: the last day any technician is expected on site, updated whenever the estimate changes
- Assigned technicians: by name, not by “crew” or “team”
The estimated end date is the one that gets skipped most often. Writing it down feels unnecessary when everyone knows roughly how long the job takes. But when three projects are overlapping and a fourth is waiting for capacity, “roughly” is the reason the business makes a commitment it cannot keep.
When should a technician return to the available pool?
The transition between projects is where assignments most often go wrong. A technician finishes the last day on a solar job Friday afternoon, gets assigned to an LED job starting Monday, and nobody records either event until admin notices on Wednesday.
Between Friday afternoon and Wednesday morning, that technician appears assigned to a finished project. Any view of free capacity is short by one person. If two or three technicians are in the same state at the same time, the visible capacity figure is off enough to affect a real decision.
The rule that prevents this is simple: closing a project on the board frees the assigned technicians immediately. The board does not wait for a job ticket to be processed or a timesheet to be filed. The project is done, the people are available. Record it when it happens.
FAQ
What if technicians move between projects mid-job?
Record the move on the board the day it happens. A technician pulled off a solar job to cover a delay on an LED site is no longer on the solar job from that point forward. If you do not update the board, it tracks a version of the crew’s location that no longer matches what is actually happening on site.
Does the board need to show hours or just days?
For multi-day installation work, days are enough. The question you are answering is: which technicians are available for a new project starting next week? That answer requires knowing which days are committed. It does not usually require knowing whether someone is leaving at 3pm on Thursday or staying to close out paperwork.
What happens when a project start date shifts?
Shift the block on the board to match. If a factory pushes an LED job start from day three to day five, the three assigned technicians are free on days three and four. Update the board when you get the call. That capacity is real and should be visible to anyone looking at the month.
The TRACE 30 program installs a month-view board built around technician-days as one of its five steps. Unassigned days appear immediately when a project closes or shifts, so the dispatch picture is current without a separate update task. Details on how it is set up are at /program/. To talk through whether it fits your current project mix, schedule a call.