On this page
The monthly owner report is one of those documents that grows a page every time someone asks a question. By month fourteen it’s sixty pages: a cover letter, photos, every log exported in full, a schedule printout, a cost report, safety stats, minutes from the last three meetings. It takes a project engineer two days to assemble. The owner’s rep reads the first page and the cost summary.
That’s not laziness on the owner’s part. It’s a signal. The report is long because nobody decided what it’s for.
What the owner is actually trying to learn
Owners, owner’s reps and their lenders read the monthly report to answer four questions:
- Where is the money? Contract value, changes, what’s been billed and paid, and what’s still coming.
- Where is the schedule? Are we on track for the milestones that matter to them: occupancy, turnover, a phase opening?
- What’s at risk? Pending changes, open issues, anything that might cost them money or time.
- What do they need to decide? Approvals, selections, direction on RFIs, change orders waiting on signature.
Everything else is backup. Backup belongs in an appendix or behind a link, not in the body.
01 · Money
This is the section owners scrutinize hardest, and it’s where inconsistency does the most damage. The core table:
| Line | What it shows |
|---|---|
| Original contract | As signed |
| Approved change orders | Total, with a count |
| Revised contract | Original + approved |
| Pending changes | Submitted, not yet approved, with values |
| Potential changes | Known exposure not yet priced or submitted |
| Billed to date | Through the latest pay app |
| Paid to date | What the owner has actually paid |
| Retainage held | Current balance |
| Balance to finish | Revised contract − billed to date |
On a cost-plus or GMP job, owners also want contingency drawdown (what’s been used, for what, and what’s left), allowance reconciliation, and buyout status. On a lump-sum job, they mostly care about the contract and change side, not your internal costs.
02 · Schedule
Not a 900-activity Gantt chart printout. Owners want:
- Milestone status: planned date, current forecast, variance, for the five to ten milestones they care about.
- The critical path in a sentence. What’s driving the end date right now?
- What changed since last month and why.
- The next 30 days from the look-ahead, at a summary level.
If a milestone moved, the report should say what moved it (weather, a late owner decision, a supplier, a change in scope) and what’s being done about it. Delay causes have contractual implications. Write them down plainly and contemporaneously.
03 · Risk
This is the section most reports get wrong, either by leaving it out or by listing everything. A useful risk section is short:
- Pending and potential changes that could affect the owner’s budget, with rough values.
- Open issues with consequences: an RFI blocking work, a long-lead item at risk, a permit or inspection holding up a phase.
- Overdue items that need the owner’s team: RFIs past their response date, submittals awaiting review.
On our sample job, that might read:
| Item | Status | Owner action |
|---|---|---|
| 4 overdue RFIs | Past response date, two affect L3 ceiling close-in | Design team response this week |
| CO #14, fire dampers | Approved, $86,400, billed on Pay App #9 | None |
| Pay App #9 | $2.31M this period, 10% retainage | Review and approve |
04 · Decisions
The most valuable part of the report, and the shortest. A numbered list of what you need from the owner, by when, and what happens if it’s late:
- Approve the pending change for the added corridor lighting by the 20th, to hold the ceiling close-in date.
- Confirm finish selections for the level 4 waiting area by the 15th. The supplier quotes a long lead time.
- Respond to the four overdue RFIs.
A decision list makes the owner’s job easy, and it creates a written record of what you asked for and when. If a milestone slips because a decision was late, that record matters.
What to cut
Most of the length in a typical report is logs exported in full: every RFI, every submittal, every daily report. Summarize them (counts, overdue, average turnaround) and link to the detail or put it in an appendix. Same for photos. Six photos that show progress on the milestones in section two are worth more than sixty.
Why reports take two days
The report is slow because it’s a reconciliation. The contract and change order totals come from accounting. Pending changes come from the PM’s log. Billing comes from the pay app spreadsheet. The schedule comes from the scheduler. RFI counts come from the PM platform. Every number is copied from somewhere, and every copy is a chance for the report to disagree with itself.
What we’re building
In os.construction, the contract, change orders, pay apps, RFIs and schedule milestones live on one job record. Analytics (in preview) builds dashboards and scheduled PDF reports from those live records today. Owner-report templates, and the Reporting agent that drafts the summary for a PM to edit and approve, are planned.
Reporting is live. Owner-report templates are planned. If your owner report takes two days and gets read for two minutes, start a free trial.
Share this article