Key takeaways
- The Question: What should a monthly construction progress report for owners and lenders contain, and how do you make it a document people trust and act on?
- The Answer: A good monthly report states the project's position on schedule, cost, change and risk, shows how each of those moved since last month, and backs every claim of progress with dated evidence. It follows a fixed cut-off and a review routine agreed between contractor and owner, so risks reach decision makers while they can still be managed.
- The YelloSKYE Angle: Construct IQ records the site on a set rhythm using drones, fixed cameras and 360° cameras, so the report can point to a dated visual record and measured quantities instead of descriptions.
A construction progress report is the monthly document that tells the owner, the lender and senior management where a project stands: how much has been built, whether key dates are still achievable, what the money position is and which risks need a decision. A good one is short at the front, supported by evidence at the back, and consistent from month to month so that trends are obvious.
This guide covers the monthly report specifically. It sets out who reads it, what each section should contain, a template you can adapt, how to make the figures credible and how the review between contractor and owner should run. Day-to-day site logs are a different document, covered in our guide to the construction daily report. Throughout, we show where a dated visual record from Construct IQ strengthens the report.
Who reads the monthly report, and what they look for
The same document has several audiences, and each reads it for a different reason. Writing with all of them in mind is what separates a useful report from a long one.
| Reader | What they need from it | What they will act on |
|---|---|---|
| Owner's board or investment committee | A clear position on time, cost and risk in plain language | Funding, scope and programme decisions |
| Owner's project manager or representative | Detail by area and trade, with evidence they can check | Instructions, payment certification, escalations |
| Lender and technical adviser | Confidence that value claimed exists and the project can finish within the facility | Drawdown approval, conditions, reserve calls |
| Contractor's leadership | Margin, cash and recovery position across the job | Resourcing, commercial strategy, recovery plans |
| End users or future operators | Progress on the areas and systems they will take over | Fit-out, move-in and commissioning planning |
The board reads the first page. The owner's representative and the lender's adviser read everything, and they read it sceptically. The report has to satisfy both.
What a monthly progress report should contain
Most owners specify the contents in the contract or the project execution plan. If they do not, the following structure covers what nearly every reader needs.
1. The one-page position
A summary written last and read first: overall status, the forecast completion date compared with the contract date and last month's forecast, the cost forecast against budget, and the three to five issues that need attention. Use a simple status for each area, but define in advance what each status means numerically, so that "on track" is not a matter of mood.
2. Schedule and milestones
Planned against actual progress for the period and cumulatively, the milestones due this month and next, and any movement in the critical path. Show the trend: a forecast that has slipped by a week in each of the last four reports tells the reader more than the current date alone.
3. Progress by area or package
What was completed in each zone, floor or work package, stated in measurable terms where possible: slabs poured, facade panels fitted, linear metres of services installed, earthworks volumes moved. Link each statement to the evidence in the appendix. If you calculate percent complete, say how: the methods and their weaknesses are set out in percent complete explained.
4. Cost, change and cash
The current budget, committed cost, cost to date, forecast final cost and the movement in each since last month. List approved changes, changes under negotiation and early warnings that could become changes. Cash flow against forecast matters to lenders as much as cost does.
5. Risks and issues
The risks that could move the completion date or final cost, each with an owner, the action being taken, the date for the next review and whether its rating rose or fell this month. Issues are risks that have already happened; keep them separate.
6. Health, safety, quality and environment
Incidents and near misses, inspections, non-conformance reports opened and closed, and any outstanding statutory or permit items. Keep the definitions consistent so that months can be compared.
7. Look-ahead and decisions required
The work planned for the coming month, the information or approvals the contractor needs from the owner, and any decision the report is asking the reader to make. If nothing is being asked, say so.
8. Evidence appendix
Dated images, survey outputs, inspection records and measured quantities that support the sections above. This is the part sceptical readers go to first.
A monthly progress report template
The table below can be copied into a report outline. Page counts are a guide for a mid-sized building project; adjust for scale.
| Section | Key content | Evidence that supports it | Typical length |
|---|---|---|---|
| Position summary | Status, forecast dates, forecast cost, top issues | Links to the sections below | 1 page |
| Schedule | Planned vs actual, milestone status, critical path movement | Programme extract, progress curves | 1–2 pages |
| Progress by area | Work completed per zone or package, in quantities | Dated site captures from fixed viewpoints, survey data | 2–4 pages |
| Cost and change | Budget, forecast final cost, change register | Cost report, approved instructions | 1–2 pages |
| Cash | Claims made, certified, paid; cash flow against forecast | Payment certificates, cash flow chart | 1 page |
| Risks and issues | Top risks with trend, owner and action | Risk register extract | 1–2 pages |
| Safety and quality | Incidents, inspections, non-conformances | Inspection logs, closure records | 1 page |
| Look-ahead | Next month's work, decisions and information needed | Short-term programme | 1 page |
| Appendix | Supporting captures and measurements | Image references, survey outputs | As needed |
Making the report credible
An owner who has been surprised once reads every report afterwards as if it is hiding something. Credibility comes from evidence and consistency, not from the length of the document.
Separate what was reported from what was verified
State clearly which figures come from the contractor's own records and which have been checked against site evidence or measured. Readers forgive a figure that is honestly labelled as an estimate. They do not forgive one that was presented as fact and turns out to be wrong.
Use the same viewpoints every month
Images taken from different angles each month cannot be compared. Fixed camera positions, repeated drone flight paths and consistent 360° routes let the reader see exactly what changed between two dates. Our time-lapse monitoring use case shows how a fixed viewpoint builds a milestone record across the whole build.
Measure where you can
Earthworks volumes, stockpiles, slab areas and facade coverage can be measured from drone surveys rather than estimated. A quantity that has been measured from survey data ends arguments that a description starts.
Date and locate every piece of evidence
Every image or measurement in the appendix should carry its capture date and location, and each statement in the body should point to the item that supports it. That cross-reference is what lets a technical adviser complete their review without a site visit for every line.
Report the trend, not only the snapshot
A single month's status can look acceptable while the direction is poor. Show the forecast completion date and forecast final cost for each of the last several reports. A steady drift is the earliest sign of trouble, and it is invisible if each month is read on its own.
Cadence: how the monthly report fits with other reporting
The monthly report sits on top of a rhythm of shorter reports. If the lower layers are weak, the monthly report has nothing reliable to summarise.
| Report | Frequency | Audience | Purpose |
|---|---|---|---|
| Daily site report | Daily | Site and project team | Factual log of resources, events and delays |
| Weekly progress update | Weekly | Project team, owner's representative | Short-term progress, constraints, look-ahead |
| Monthly progress report | Monthly | Owner, lender, senior leaders | Position, trend, risks and decisions |
| Quarterly or milestone review | Quarterly or at key stages | Boards, funders | Strategic review, forecasts, scope decisions |
Align three dates: the report cut-off, the progress payment claim cut-off and the site capture. If the drone flight happens on the 25th, the claim covers work to the 25th and the report uses the same date, every number in the pack refers to the same physical state of the site. When those dates differ, much of the review time is spent reconciling them.
The owner-contractor reporting workflow
A report is only as useful as the routine around it. The workflow below keeps risks visible because each step has an owner and a deadline, and nothing reaches the board that has not been through the project team first.
| Day (relative to cut-off) | Step | Who |
|---|---|---|
| Day −2 to 0 | Site capture of all active areas; final quantities measured | Contractor or capture provider |
| Day 0 | Cut-off: progress, cost and claim frozen at this date | Contractor |
| Day +1 to +3 | Package managers update progress and risks; planner updates forecast | Contractor's project team |
| Day +4 | Draft report issued to owner's representative | Contractor's project manager |
| Day +5 to +7 | Owner's team checks progress against evidence and raises queries | Owner's representative, cost consultant |
| Day +8 | Progress review meeting: agree position, agree actions on red risks | Both teams |
| Day +10 | Final report issued; owner's summary sent to board and lender | Both |
Agree escalation rules in advance
Decide at the start of the project what triggers escalation. Typical triggers are a forecast milestone slipping beyond an agreed number of days, a risk whose cost exposure passes a set value, or a package that has fallen behind for two consecutive months. Escalated items need a written recovery plan from whoever owns them, and the owner's representative should accept or reject it at the review meeting rather than let it drift into the next month.
Disagree early and on evidence
If the owner's team disputes the reported progress, the conversation should happen between the draft and the final report, using the same dated captures. In our aerial progress capture use case, a weekly drone programme shortened stakeholder meetings from two hours to half an hour, since every party had looked at the same record beforehand.
Keep one version
The final report should be the version both parties have reviewed. A contractor's report and a separate owner's narrative that tell different stories are a sign that the review step is not working.
Common faults in monthly progress reports
- Activity instead of progress. Lists of what crews worked on, with no statement of what is now complete.
- Status without definitions. Green, amber and red applied by judgement, so every project is green until it is suddenly red.
- Forecasts that never move. A completion date that stays fixed while the work visibly falls behind.
- Evidence that cannot be compared. A handful of photos from new angles each month, with no dates or locations.
- Risks without owners. A long register in which nothing changes and nobody is accountable.
- Mismatched dates. A report, a payment claim and a programme update each using a different cut-off.
Where YelloSKYE fits
Construct IQ supplies the evidence layer under the monthly report. Drones fly pre-programmed routes, usually weekly or fortnightly, and produce orthomosaics, 3D models and measured volumes. 360° walkthroughs record interiors along repeatable routes, and fixed cameras keep a continuous record of selected zones. Everything is stored by date and location in the DEX platform, which shows planned against actual progress and lets the reader scroll back through the site history to see what was built when.
For owners with several projects, capturing every site with the same parameters means reports from different contractors can be compared on the same footing. In our portfolio monitoring use case, leadership reviews more than ten sites in 30 minutes. Captured progress can be passed by API or as standard files into Procore, MS Project or Autodesk Construction Cloud, wherever the report is assembled.
Checklist: setting up a monthly report that people trust
- Agree the report contents, cut-off date and issue date with the owner before the first claim.
- Define what each status colour means in numbers for schedule, cost and risk.
- Align the site capture, progress claim and report to the same cut-off date.
- Capture from fixed viewpoints and repeatable routes so months can be compared.
- Measure quantities from survey data wherever the work allows it.
- Label every figure as reported or verified, and link it to dated evidence.
- Show the trend in forecast dates and forecast cost for at least the last six months.
- Give every red risk an owner, an action and a review date, and record decisions at the review meeting.
- Issue one final version that both contractor and owner have reviewed.
