A solar business in Samut Prakan is running a multi-day installation job: 24 residential panels, three days on site. Day one goes well: scaffolding up, rails mounted, roof penetrations sealed. Day two, the crew is delayed by a parts delivery mix-up and arrives an hour late. Nobody informed the homeowner. At 8:15 AM the customer calls the office: “Where are your people? I cancelled my morning for this.”

The job finishes on day three. The workmanship is solid. But the handover feels sloppy, the customer gives a lukewarm referral, and the business owner cannot pinpoint what went wrong because the job “just happened” rather than being run.

That is the cost of treating a three-day job as a one-day job with extra steps.

What Makes Multi-Day Jobs Different from a Single Visit?

A single-visit service call is a discrete event. One technician or team arrives, completes a defined scope, documents it, and leaves. The job either happened or it did not.

Multi-day installations introduce continuity problems that single visits never face:

Progress state lives in someone’s head. What was done yesterday, what is half-finished, what the customer was told on site — all of this must transfer cleanly from one day to the next, often across different crew members.
Customer expectations reset overnight. A homeowner who agreed to a three-day solar install on Monday wakes up on Tuesday with zero visibility into what is happening on their roof until someone contacts them.
Partial installations carry real risk. An unsecured panel, a capped pipe run, or a camera wired without an NVR connection left overnight is a site in a transitional state. If anything goes wrong overnight, the question is immediately “whose fault?”
Material consumption is unpredictable across phases. If day one uses more conduit than planned, day two’s crew arrives understocked unless someone tracked and restocked between shifts.

These are not bad-luck problems. They are structural problems that a clear system removes.

How Do You Track Progress Across Multiple Days?

The answer is not a group LINE chat.

LINE threads for multi-day jobs have a consistent failure mode: photos, status updates, and task notes scroll off into history, buried under logistics messages (“what time arriving?”, “bring 16mm conduit”, “the guard needs your name”). By day three, nobody is certain what the thread actually reflects — and whoever ran day one is now on a different job.

A persistent job record — one document that stays current and travels with the job — solves this. The record lives in a job management system, not in any one person’s phone. It contains:

Phase checklist with completion state. Each installation step marked done or pending, by whom, at what time. “DC cable run to inverter — done, Khun Arthit, 14:30, Day 2.”
Photo log per phase. Roof penetrations before sealing, cable routing, panel orientation before final torque, inverter installation. These photos serve quality control during the job and customer documentation after it.
Materials consumed and remaining. If a phase uses 60 meters of conduit where 80 were delivered, the record shows 20 meters available for day three — and flags if that is not enough.
Open items. Anything deferred, any issue discovered, any instruction the customer gave on site.

When the next day’s crew opens this record before leaving their depot, they know exactly where the job stands. No catch-up call to the day-one technician. No duplicating work that was already done.

What Should You Tell the Customer Each Day?

A residential solar customer who paid 180,000 baht committed real money to a three-day process they cannot see from inside the house. Their tolerance for silence is low, and their imagination of what could go wrong is high.

A practical daily communication pattern requires exactly two touchpoints:

Morning (when the crew is en route): A short LINE message or SMS stating who is arriving, at approximately what time, and what today’s work covers. “Good morning, Khun Somchai. Khun Arthit and the crew will arrive around 8:30. Today they’ll complete the panel wiring and connect the conduit to your distribution board.”

Evening (before 6 PM): A brief status summary. “Today: panels wired, conduit run completed. Tomorrow: inverter installation and commissioning. Completion still on track for Thursday.” Four sentences. Two minutes to send.

The customer who receives both messages does not call the office wondering what is happening. The one who does not receive them calls three times.

When a problem occurs — delayed start, material shortage, a day’s extension — communicate before the customer notices. “We hit a bracket alignment issue this afternoon and need an extra three hours tomorrow. Completion moves to Thursday PM rather than AM. We’ll confirm the exact time by 7 PM tonight.” A proactive delay message keeps trust. A customer who discovers a delay on their own, and only then hears from you, does not.

How Do You Stage Parts and Tools Over Multiple Days?

A technician’s service van carries standard tools and common parts. A multi-day solar, CCTV, or fire suppression install often requires materials that exceed van capacity or that must arrive in sequence.

A materials list by phase eliminates most shortage problems:

For a 24-panel residential solar install:

Day 1: Scaffolding, mounting rails, roof anchors, sealing compound, roofing screws
Day 2: Solar panels, DC cable, conduit, combiner box, inverter
Day 3: AC disconnect, grounding hardware, labels, commissioning kit, grounding rod

Each day’s delivery is tied to that day’s scope. Delivering everything on day one means panels sitting on the ground during a scaffolding day — a trip hazard, a damage risk, and a site manager complaint.

Returning unused materials is a formal closing step, not an afterthought. Parts that drift into van stock “for the next job” become unresolved stock variances that compound over weeks until nobody knows what is actually on the vans.

What Does a Clean Day-End Handoff Look Like?

At the end of each working day on a multi-day job, before the technician leaves the site, five things need to happen:

Update the task checklist. Mark what is done; note anything started but not finished, and why.
Upload the day’s photos. Roof, wiring, panel placement, DB room — whichever phases advanced today.
Log materials consumed. What was used, what is still on site, what needs replenishing overnight.
Flag any issue. An unexpected structural finding, a customer instruction that changes scope, a safety observation.
Confirm tomorrow’s start. Arrival time agreed with the customer or site contact, crew size needed, any access arrangements.

Five items. Fifteen minutes at most. The next day’s crew — whoever the dispatcher assigns — arrives with full context and zero catch-up calls needed.

This matters most when the primary technician is absent the next day. The job record is not inside their head. It is in the system, accessible to anyone dispatched to the site. That resilience is what a three-day job requires.

FAQ

How do you handle scope changes discovered mid-job?

Document the change immediately in the job record with photos, then call the customer before continuing. For Thai install businesses, a verbal on-site agreement is common for minor additions. Follow it immediately with a written LINE message: “As we discussed this morning: the additional conduit run to the second floor adds 1,800 baht to today’s invoice. I’ll include it in the final report.” That message prevents invoice disputes at completion and gives the customer a written record they appreciate.

Should multi-day jobs use a different work order format?

The same work order format works with one addition: a phase structure. Break the task list into Day 1, Day 2, and Day 3 sections. Each day’s crew sees what belongs to their phase. Completed tasks from earlier phases are visible but locked. This prevents a day-two technician from re-doing work they were not sure had been finished — a real problem when no one communicates between shifts.

What is the right way to leave a site overnight?

Photograph the site at each day’s end, regardless of how clean it looks. The photos establish the state of the installation when your team left — protecting your crew from claims that damage occurred during work, and proving the site was left in a safe, controlled condition. Exposed DC wiring, unsecured panels, and open roof penetrations are not acceptable overnight states. If the day’s scope cannot reach a safe stopping point, plan phases differently before the job starts, not at 5 PM when the crew is tired.

OnSiteQ’s work orders support multi-day job checklists, per-phase photo logs, and materials tracking — so whoever shows up on day two or three opens the same live record, not a LINE thread buried under logistics messages.

Managing Multi-Day Installation Jobs Without Losing Track