How Do You Write a Weekly Owner Update?
By Wyatt Cooper · Published · 7 min read
Key takeaways
- A weekly owner update is one page: what got done, whether the job is on track for its completion date, what is coming, and what the owner has to decide.
- Lead with the schedule status in one line (on track, at risk or behind) and the reason, because that is what the owner reads first.
- Give the same handful of numbers every week, so the owner can compare this week to last: percent complete, days to substantial completion, open and overdue RFIs, pending change orders.
- Put owner decisions in their own list with a date each one is needed by; a decision buried in a paragraph is a decision that doesn't get made.
To write a weekly owner update, fit it on one page: a one-line schedule status (on track, at risk or behind) with the reason, a short list of work completed this week, the next week or two of work, issues and decisions the owner must make with a needed-by date, and the same few numbers every week: percent complete, days to substantial completion, open and overdue RFIs and pending change orders. Send it on the same day each week.
What the owner wants from the update
Most owners read the weekly update for three answers: is the job on time, is anything going to cost me more, and is anything waiting on me. Everything else is support. An update that opens with three paragraphs of trades and quantities hides those answers.
Public owners ask for the same thing in their own reports. Connecticut's construction administration manual has its construction administrator produce a monthly report "with a narrative summary of the physical progress of construction", noting potential delays and problems and their impact on "the overall project completion date". The City of Los Angeles Bureau of Engineering's progress reports procedure says writing one forces the team to compare the project to the plan and to discuss "the corrective actions required to get the project back on schedule".
A weekly update is the short version of those reports. The owner's side of the job is in the owner's guide; this post is for the GC writing to them.
The sections of a weekly update
| Section | What to write | Where it comes from | Common mistake |
|---|---|---|---|
| Schedule status | On track, at risk or behind, and one sentence why | The schedule's key dates against the baseline | "Progressing well" with no date |
| Numbers | Percent complete, days to substantial completion, open and overdue RFIs, submittals pending, change orders pending and their total | The schedule and the logs | Different numbers each week |
| Work completed | Five to eight lines by area or trade | The week's daily logs and finished schedule activities | Every crew and quantity |
| Coming up | The next one to three weeks, with dates | The three-week look-ahead | Leaving out the owner's own dates (IT, furniture) |
| Issues and decisions | Each issue, who it is waiting on, and the date a decision is needed | Overdue RFIs, pending changes, owner action items from meetings | Burying the decision in a paragraph |
| Photos | Three or four with captions | The site | Forty photos and no captions |
The federal scheduling spec gives a good test for the schedule section. UFGS 01 32 01.00 10 asks each schedule narrative to describe "current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective actions taken or required to be taken". If the job is at risk, say what you are doing about it in the same sentence.
A filled-in example: week of April 6
Alder Street Medical Office — Weekly update #14 — Week of April 6
- Schedule
- At risk. Substantial completion is September 18, 164 days from today (April 7). Roof dry-in may slip 3 days if RFI 019 (roof drain sizing) isn't answered by April 9.
- Numbers
- 41% complete · 6 open RFIs, 1 overdue · 9 submittals pending · 2 change orders pending, $7,310
- Done this week
- Level 2 framing 60% complete, east half. Level 1 overhead plumbing rough-in inspection passed. Storefront shop drawings sent for review. OAC meeting #14 held; minutes sent.
- Coming up
- Level 2 framing complete April 17. Roof deck April 20. Crane pick for rooftop units April 21 (street closure permit requested). OAC meeting #15 April 14.
- Decisions needed from the owner
- 1. IT room equipment list, needed April 9 (was due April 3). 2. Sign change order 007, added floor drains, $4,860, by April 10. 3. Card readers at two doors: price coming April 14.
- Waiting on the design team
- RFI 019, roof drain sizing, 4 days overdue with the MEP engineer.
- Photos
- Level 2 framing from the northeast corner; Level 1 overhead plumbing rough-in at grid B before the inspection; storefront mock-up area
The two pending change orders add up: $4,860 for the floor drains plus $2,450 for a relocated electrical panel is $7,310. The owner can see the total and the one they need to sign this week. And the at-risk status names the cause and the date it turns into a slip.
How to write it every week without it taking all morning
- Pick one day and send it then, every week, even when the week was quiet.
- Start from the records, not memory: the week's daily logs, finished schedule activities, RFIs answered and meetings held.
- Write the schedule line last, after you've looked at the key dates, and change it only when the dates change.
- Move every owner action item from the meeting minutes into the decisions list with its date.
- Keep the numbers in the same order every week, so a change stands out.
- Reread it as the owner: can they tell in thirty seconds whether anything is late, costing more, or waiting on them?
Don't use the update to argue a delay or a change. Notice of a claim goes the way your contract requires; the update is a summary, and saying a delay is "possible" in an update may not count as notice.
How it works in Conflo
In Conflo's owner updates, starting this week's update fills in a draft from the week's records: the work the daily logs recorded and schedule activities finished, RFIs answered, meetings held and tasks completed. Coming up lists the next weeks of the schedule and upcoming OAC and owner meetings, and issues lists overdue RFIs with who owes the answer, open RFIs that affect the schedule, and open meeting action items assigned to the owner.
The draft suggests a schedule status of on track, at risk or behind, which you can change, and you edit every section before publishing. Each update keeps the project's numbers as of the day it was saved: percent complete, days to substantial completion, open and overdue RFIs, submittals and change orders pending. The pending change order total shows only to people who see the project's money. Once published, the update is locked, and the owner and the GC team can comment on it.
The bottom line
A weekly owner update is one page that answers three questions: is the job on time, is anything going to cost more, and what does the owner need to decide by when. Give the same numbers every week and send it on the same day.
If writing it means rereading a week of daily logs and emails, start from a draft built from the week's records.
Sources
- 0600 Construction Administration Procedures Manual, §2.4 (monthly progress and schedule reports) — State of Connecticut Department of Administrative Services. Read October 22, 2026.
- Project Delivery Manual, 5.2 Progress Reports — City of Los Angeles, Bureau of Engineering. Read October 22, 2026.
- UFGS 01 32 01.00 10, Project Schedule (August 2026), §3.5.2 Narrative Report — U.S. Army Corps of Engineers (Whole Building Design Guide). Read October 22, 2026.
Questions
What should a weekly construction report to the owner include?
A one-line schedule status with the reason, work completed this week, work coming up, issues and decisions the owner must make with dates, a few photos, and the same numbers every week: percent complete, days to substantial completion, open and overdue RFIs, and pending change orders.
How long should a weekly owner update be?
One page. Owners read it for whether the job is on time, whether anything will cost more, and what is waiting on them. Detail belongs in the logs and the monthly report, linked or attached if the owner wants it.
Is a weekly owner update the same as a monthly progress report?
No. The monthly report usually goes with the pay application and covers schedule analysis, cost and the period's progress in depth. The weekly update is the short version that keeps the owner current between them.
Does saying a delay is possible in an owner update count as notice?
Don't rely on it. Contracts set how notice of a delay or claim must be given, to whom and by when. Give that notice the way your contract requires, and mention it in the update as well.
Related
Construction
How Do You Run an OAC Meeting?
How a GC runs an owner-architect-contractor meeting: who attends, what each party brings, a worked agenda, and how open items carry to the next one.
· 8 min read
Role hub
The Owner's Guide to a Commercial Building Project
The owner's role on a commercial building project, phase by phase: delivery method, choosing the contractor, pay apps, change orders and closeout.
· 7 min read
Construction
How Does an Owner Read a Construction Schedule?
How an owner reads a contractor's schedule: the Gantt chart, milestones, the critical path, float, the baseline, and what to ask at each update.
· 6 min read
Construction
How to Write a Construction Daily Log (With Example)
How to write a construction daily log: what to record each day, a filled-in example, and the habits that make a log hold up in a delay claim.
· 6 min read
Role hub
The General Contractor's Guide: Bid to Closeout
What a general contractor is responsible for at every phase of a commercial job, from bidding and buyout to RFIs, change orders, pay apps and closeout.
· 8 min read
