Owner reporting
How the monthly owner report is planned to assemble from live job records, tie out to the change order log and the latest pay app, and leave the PM to write the narrative and the decision list.
This is on the roadmap and not built yet.
The monthly owner report answers four questions for the owner and their lender: where the money is, where the schedule is, what’s at risk, and what they need to decide. The numbers are planned to come straight from the job’s records, so the report ties out by construction and the PM’s time goes into the parts that need judgment. Today you can build a project dashboard in Analytics and export or schedule it as a branded PDF, CSV or XLSX.
The four sections
| Section | What it shows | Built from |
|---|---|---|
| Money | Contract, approved and pending changes, billed, paid, retainage, balance to finish | Contract, change records, pay apps |
| Schedule | Milestone status, forecast vs plan, what changed | Schedule milestones |
| Risk | Pending and potential changes, overdue RFIs and submittals, open issues | Change records, RFIs, submittals |
| Decisions | What you need from the owner, by when | Written by the PM |
Backup (full logs, photos, meeting minutes) goes in an appendix or behind links, not in the body.
Ties out by construction
The most common problem with owner reports is that they disagree with themselves. Approved changes in the report don’t match the change order log, which doesn’t match the contract sum on the latest pay app. Because all three read the same change records, we plan it so they can’t drift:
- Approved changes in the report = the change order log = the G702 contract sum change on the latest pay app.
- Billed to date = the latest approved pay app.
- Retainage held = the retainage balance on the pay app record.
Contract types
Owners mostly care about the contract side: approved and pending changes, billing, retainage and the schedule. Your internal costs and margin are not part of the report.
Owners also see the cost side, because they pay it. The report adds contingency drawdown (used, for what, remaining), allowance reconciliation, buyout status against the GMP, and cost to date against the GMP by major category. Which cost detail is shared is set per job.
Building a report
-
Start from the period
Pick the job and the period. The money, schedule and risk sections fill from the records as of the period end.
-
Write the narrative
The PM writes the summary and the decision list. The Reporting agent can propose a first draft from the period’s records for the PM to edit. Planned.
-
Choose the backup
Select the photos and log summaries that support the narrative. Counts and aging for RFIs and submittals are included automatically.
-
Review and approve
Planned: the report follows your approval rules, for example PM then project executive. See Writing approval rules.
-
Snapshot and send
Approving the report locks a snapshot. The numbers in a sent report never change, even as the live job moves on.
Portfolio view
The same structure rolls up for your own leadership: every active job’s money, schedule and risk on one page, built from the same records as each job’s owner report. See Dashboards and reports.
Keep exploring
Related across os.construction
- BlogWhat owners actually want in a monthly reportMost owner reports are long because nobody decided what they're for. Owners read them for four things: where the money is, where the schedule is, what's at risk, and what they need to decide. Here's a structure that answers those, and the numbers that have to tie out.
- DocsOwner billing on GMP jobsHow billing on a guaranteed maximum price contract differs from lump sum, how cost of work, fee, contingency and allowances roll into each pay app, and how we plan to build the backup from job cost.
- ExplainerChange events vs change orders: the full lifecycleWhat a change event is, what a PCO and change order are, and where each one shows up in the budget, the contract and the pay app in os.construction.
- ExplainerWhy one data core: the same record everywhereSee how RFIs, field records, change orders, budget, pay apps and CRM link on one data core in os.construction, and why links beat copies and syncs.
- DocsChange events and change ordersTrack a change from the first sign of it to an executed change order. Change events, potential change orders, packages, commitment change orders and budget posting in the app.
- GlossaryContingencyMoney set aside in a budget or contract to cover unknown costs and risks that are expected but can't be pinned down yet.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →