Field operations for installation contractors
One system, from the day you win the job to next year’s service round
No job lost on the way. No site nobody ever goes back to. Thirty days to install, and on day 30 we count three things you can check yourself.
For contractors installing electrical work in factories: solar C&I and industrial LED. 8–40 field technicians, 2–10 projects handed over a month.
What the system holds
The month on one board
A project eats several technicians for several days. See the whole month in one screen, staff it by team and by who is free, and let anything still unassigned stay flagged until someone takes it.
A closing gate, not a nagging habit
No signed handover means the job cannot be closed, and a job that is not closed never reaches the billing queue. Paperwork arrives complete because the work needs it, not because someone chased it.
Sites that stay on the books
Every handover writes itself into the site register, with a warranty clock and a due date for the next inspection. When the round comes up, the system raises the job order itself.
Sound familiar?
Four handoffs, and work leaks at three of them
- The schedule lives in the foreman’s head and a LINE group, so two crews get double-booked and a customer asks who is coming and nobody can answer
- “The job is finished, but the photos are short and nobody signed the handover”
- Paperwork rides around in the truck until month-end, then admin chases it one job at a time
- Work that is finished on site but cannot be invoiced yet, and nobody knows the total
- Handover done, and the site drops to zero: no owner, no return date, no reminder
- Warranties expire unused, inspection rounds slip, service contracts lapse with no warning
The villain is not your team and it is not the software. It is work that goes missing on the way: first as a job order stuck in a truck, then as a site nobody ever goes back to.
How it works
T·R·A·C·E: five steps, four short sessions, live on day 30
Not a consulting project. We set the system up from templates that already exist, teach the four people who touch it, and step back on day 30. You are with us for about five hours in total; the rest is our work behind the scenes.
Trace what you have
Days 0–3. One form and a short call: jobs in flight, technicians, sites you want carried over, what you dispatch with today. Anything beyond scope gets priced now, not later.
Rig the board
Days 4–14. A 90-minute kickoff where you pick from templates instead of designing: status flow, job order, handover form, inspection cycle. You sign off before you leave; we build it out.
Attach the real work
Days 15–21. Your live jobs and your site list go into the system, so when your team opens it they see their own work, not sample data. Then we train admin and the foreman.
Close the old channel
Days 22–27. One hour with the technicians: five taps per job, photos instead of typing. Then you close the dispatch group yourself. We watch the numbers remotely for the first three days.
Exit, and let it run
Days 28–30. You drive one full cycle while we keep our hands off the mouse: take a job, dispatch, close, issue the handover. Then we hand over the manual, the clips and the field card.
What we can prove today
We are at the start, and we would rather say so
No client case studies yet
TRACE 30 is a new program and nobody has finished a year on it. When we have contractors who have stayed six months, that will be the number we lead with. Until then we are not going to invent one.
A 90-second demo instead
On the call we hand you the phone and let you try to close a job without a signature. The system refuses. Sign, and it closes. You do not have to take our word for how the gate behaves.
We freeze your baseline on day one
Five numbers, measured and signed on the day you start: value finished but not invoiced, days from close to invoice, jobs needing a return trip for paperwork, in-warranty sites with no return date, and hours you spend answering “where is that job?”.
After 30 days
What the last day of the month looks like
- Every job on the board has a name against it, and the ones that do not are impossible to miss
- Jobs close with photos and a customer signature attached, because they cannot close without them
- The billing queue fills itself from closed jobs, so nobody chases the truck at month-end
- Every site you handed over is on the register with a warranty clock and a return date
- Inspection rounds raise their own job orders, so nobody has to remember them
Notes
Written for contractors who install and then maintain
Technician-Days, Not Job Tickets: Your Real Scheduling Unit
Most contractors count jobs per month. The number that tells you whether to take on more work is technician-days. Here is how to apply it.
ReadWhat Goes on a Handover Document an Engineer Will Sign
Getting a customer's engineer to sign a handover on the day requires specific content. Here is what goes on a handover document for factory electrical work.
ReadThe job is not finished when the truck leaves
Most contractors treat the end of the work as the end of the job. That one belief turns a finished site into nothing, and it costs more than bad scheduling.
ReadWant to see where jobs go missing in your own numbers?
Book a 45-minute call. We ask for three numbers you already have, turn them into baht in front of you, and you keep the arithmetic, whether or not we work together.
Book a call