How to Write a Weekly Construction Project Update

The client sees the site every evening but still asks whether the project is on track. You have been busy coordinating trades, checking deliveries and resolving practical issues. From your perspective, there has been constant activity. From theirs, there has been very little explanation.

A contractor weekly progress update closes that information gap. It should not become a polished account of everything the team has done or a stream of photographs without context. Its job is to give the client a reliable picture of progress and a clear view of the next decisions and dependencies.

The format can be short. The underlying discipline matters more: distinguish what is complete from what is planned, identify what may change the forecast and keep requests visible until they have a documented outcome.

Report what happened before promising what comes next

Begin with completed work that is relevant to the client’s understanding of the project. Use clear locations and task descriptions. If a task has started but is not complete, say so. Avoid broad phrases such as nearly finished when they conceal important work still required.

A weekly update is not an inspection certificate. Explain any formal checks or approvals accurately and do not imply they have occurred because a task appears visually complete. Keep technical verification in the appropriate professional process.

Next, describe the planned work for the coming period. Label it as a plan or forecast where dependencies remain. Clients can handle uncertainty more easily when the explanation identifies what is known and what is still being confirmed.

Replace reassurance with a reason

“Everything is on track” may be comforting briefly, but it becomes unhelpful if the client cannot see the basis. A better explanation links the current position with the schedule: the task completed, the next activity, the dependency and any material effect on the expected sequence.

Do not promise a revised completion date without the information needed to support it. If you are still assessing an impact, state that, explain what is being checked and give a realistic time for the next update. Silence while you wait for certainty can create more concern than a candid interim report.

Distinguish a fact, a forecast and an open question

A delivered item is a fact when receipt has been verified. An expected delivery date is a forecast. An unanswered supplier enquiry is an open question. Putting all three into the same confident language makes the report sound smoother but less useful.

Use explicit wording: “The item arrived on Tuesday”; “The supplier currently expects delivery on Friday”; or “We are awaiting confirmation and will update you by Thursday afternoon.” Adapt those examples to the actual position rather than treating them as ready-made promises.

The same distinction applies to work duration. A provisional sequence can be useful without being presented as a guaranteed timetable. Explain the assumptions that materially affect the customer’s planning, such as access, a required inspection or an unresolved technical matter.

Keep a single source for the status

A site supervisor, administrator and business owner should not send three different versions of the schedule. Agree who maintains the current project record and who is responsible for the client update. Gather input before sending and resolve obvious contradictions.

A simple shared record can work for a small project if access and version control are managed. More complex projects may need specialist project-management software. A document template can organise a report, but it does not synchronise everyone automatically.

Make action requests specific

A request such as “Please let us know about the access” is easy to misunderstand. Identify the information or permission needed, why it matters and the practical date by which a response would help. Do not describe every question as urgent merely to increase the chance of an answer.

If a response is missing, explain the actual dependency and discuss the next step. Avoid claiming an automatic time extension or extra fee through an informal update. Contractual notices, variations and entitlement questions need the applicable process.

A weekly status email is a progress summary, not a formal notice, change order or approval. Use the process in your agreement for variations and other formal project communications, and get qualified advice when you are unsure which requirements apply.

Keep the report shorter than the conversation it replaces

Consider a fictional week in which five unplanned progress calls take 12 minutes each. That is 60 minutes. If preparing one useful update takes 20 minutes and two follow-up calls take 10 minutes each, the total becomes 40 minutes in this illustration.

The apparent difference is 20 minutes, but it is not a guaranteed saving. Clients may still need conversations, and a complex week may require a longer report. The comparison is useful only if the update improves understanding rather than suppressing legitimate questions.

Track the time and the nature of repeated queries in your own projects. A client who asks about a risk after reading the report may be engaging constructively. A client who repeatedly asks what is happening tomorrow may need a clearer explanation of the next planned activities.

Choose photographs that explain something

Use a small number of permitted images with clear captions. Each should identify the relevant location or stage and what the client should understand. A general site photograph can be useful context, but it should not be treated as proof of concealed work or compliance.

Respect privacy, site security and any agreed restrictions. Avoid unnecessary images of occupants, personal possessions, access codes or sensitive details. Use appropriate storage and sharing arrangements rather than distributing an uncontrolled folder to everyone involved.

The report should remain understandable without relying on tiny annotations in a photograph. On a phone, short captions and a simple sequence usually communicate more clearly than a dense collage of images and technical labels.

A short update a client can use

Example only: “This week: the agreed preparation work in the utility room is complete. Next: the next trade is provisionally planned for Tuesday, subject to the required confirmation. Current issue: we are checking a delivery date and will update you by Monday afternoon. Your action: please confirm the agreed access arrangement by Monday morning. Our next update: Friday, or earlier if the delivery changes the sequence.”

Replace every statement with verified project information. Link to any formal change or notice separately. The strength of this format is that the client can distinguish a completed task, a provisional plan and a request without having to interpret a general reassurance.

Match the process to the project

A weekly rhythm may suit many active residential projects, but it is not mandatory or sufficient for every job. Agree an appropriate frequency and channel with the client. Material issues may need immediate communication rather than waiting for the next scheduled report.

Clear, regular updates help clients understand the work and the decisions ahead. Keep the report connected to the project agreement and current record; it does not replace required notices, approvals or change documentation.

For your next update, write four short sections: completed work, planned work, current issues and assigned actions. Check every date for its status as fact or forecast. Then remove anything that does not help the client understand or act. A reliable update earns trust through accuracy and usefulness, not length.

Sources and product information updated in 2026. Worked scenarios are illustrative, not industry benchmarks.