Note
Progress Updates During Installation: What to Send and When
Around day three of a factory installation, the customer’s engineering manager asks how things are going. The project manager opens the LINE group with the crew. The last message was a photo of a cable tray. Before that, a question about conduit sizing. Getting a current picture of actual progress takes ten minutes of reading back through a thread designed for operational coordination, not project reporting.
This is the default for most contractor businesses. The crew is doing solid work. The customer is not seeing a structured view of it. By the time the acceptance inspection arrives, the customer walks in carrying questions that collected over two weeks of silence. A structured progress update each week would have answered most of them before they became inspection issues.
Why does the information gap develop?
The site lead’s job is to run the installation. Writing reports is not part of that role, and most site leads are not going to do it consistently unless there is a clear, lightweight structure that makes it simple.
Most crews do communicate with the customer, but through informal channels: a photo dropped into a group chat, a call to the project manager who summarises verbally. This creates activity but not a record. The customer has a general sense that work is moving. What they do not have is something they can share with their own engineer or use to answer internal questions about when a zone will be operational.
The result is information debt. It accumulates quietly through the project and arrives all at once at the acceptance inspection. The inspector walks in carrying questions about material choices, completions, and deviations. The contractor walks in without a log of the answers.
What is a structured progress update actually for?
A structured progress update is not a status call. It does three things informal updates cannot.
It creates a shared record of what was completed and when. If a scope question arises at handover about whether a particular circuit was included in the original contract, the update log shows when it was done and who confirmed it.
It manages the customer’s internal expectations. The customer’s engineer is not the only person following the project. A production manager, a procurement team, and a finance team may all need different pieces of information at different times. A weekly summary they can forward internally reduces the volume of status calls to the contractor.
It gives both parties a natural moment to raise concerns. A customer who receives a weekly update has a structured opportunity to flag a question in week two. That question gets resolved before it affects the critical path. The same question raised at the acceptance inspection can delay the handover by days.
What should a progress update contain?
A weekly update for a factory installation does not need to be long. It needs to be consistent.
- Work completed this period. Named zones, systems, or tasks confirmed done: not “we made good progress” but “Zone A LED fixtures mounted and powered, 140 of 140 units; Zone B string wiring complete, awaiting inverter connection.”
- Work in progress. What is actively running, with a brief status: “DB room cable terminations: 60% complete.”
- Planned for next period. What the crew will work on next week, and what the customer needs to do before then: site access confirmation, a key holder name for a restricted area, a decision on a flagged substitution.
- Open items requiring customer action. One sentence per item, with who owns the next step and by when.
- Two or three photos. Covering the major completions of the week, not every image from the job record.
A site lead with a clear template can fill this in within ten to fifteen minutes at end of week. Without a template, the same information either goes uncaptured or takes three times as long to pull together.
How often should updates go out?
For projects shorter than five working days, a brief end-of-day note is useful. The project is moving fast and the customer has limited time to check in. A short summary each evening is better than silence until the last day.
For projects running one to four weeks, weekly is usually enough. Send it at the end of each working week. If a significant milestone completes mid-week (a commissioning test passed, a major zone cleared), a brief milestone note is worth the two minutes it takes.
For longer projects, the weekly rhythm holds. What changes is the forward view: this week’s completions, the next three weeks’ plan, and any schedule changes against the original baseline.
Does progress reporting change what happens at the acceptance inspection?
It changes what the inspection has to resolve. An inspector who has received three weekly updates arrives already knowing what happened in each zone and when. The open items at the inspection are the ones that remain genuinely open. Everything else was logged as it happened.
Disputes at the acceptance inspection are rarely about the physical work itself. They are about deviations, documentation, and expectations. A customer who has been briefed weekly already knows that the driver substitution in Zone C was discussed and agreed in week two. That conversation does not happen during the inspection. It already happened.
A completed project with no progress record requires the contractor to reconstruct the project history at handover. That reconstruction takes time and produces an incomplete picture. A project with a weekly log does not need reconstruction.
FAQ
What if nothing significant happened this week?
Send the update anyway. “Cable containment complete in Zones A and B; Zone C material arrived and staged; no customer actions required this week” is a useful update even for a routine week. Silence during a live project reads as a problem to a customer who has no other source of information about what is happening on their site.
Who should write the progress update?
The site lead captures the raw content: what was done, what photos are worth including. The project manager reviews and sends it to the customer. This keeps the customer-facing communication with the person who holds the project relationship, and gives the project manager a chance to flag anything that needs a follow-up before the update goes out.
Does a progress update replace the handover documentation?
No. The update is a communication for the customer during the project. The handover file is the formal record of the completed installation. They serve different purposes, but the data overlaps: task completions, material confirmations, and test results captured during the project are far easier to compile into a handover file than to reconstruct from a chat thread after the crew has moved on.
The job record that TRACE 30 builds during each installation carries the task completions, photos, and open items the crew captures on site. That is the same data a structured progress update draws from, and the same documentation that goes into the handover file at close. You can see how the program works at /program/, or book a short call to talk through how it applies to your current projects at /schedule-a-call/.