Monthly progress reports owners can trust

Every month, the contractor tells the owner how the job is going. The monthly progress report is that story in writing, backed by the schedule update and the payment application. A report owners can trust is not the longest one. It is the one whose numbers agree with each other, whose narrative explains what changed, and whose bad news arrives early. This lesson sets out what the report should contain, how it ties to CCDC 2-2020, and how an owner tests it before passing a summary up the line.

Learning outcomes

• List the sections of a contractor's monthly progress report and the source document behind each.
• Connect the report to the monthly schedule update under CCDC 2-2020 GC 3.4 and the monthly payment application under GC 5.2.
• Apply six tests that show whether a report can be trusted.
• Turn the contractor's report into a one-page owner's report for Northgate's July 2027 period.

The lesson

Three monthly documents, one story

CCDC 2-2020 sets up a monthly rhythm without ever using the words "progress report". GC 3.4 requires the contractor to provide a construction schedule before its first application for payment, to monitor progress against it, and to update it monthly or as the Contract Documents say. GC 5.2 has the contractor apply for payment monthly, dated the last day of the payment period, for the value of work done and products delivered by that date, measured against the schedule of values. The progress report, which Division 01 normally requires under its construction progress documentation section, is the narrative that ties those two together.

That gives the owner three documents each month: the schedule update, the payment application and the report. They describe the same 30 days. If they do not agree, something is wrong, and finding the disagreement is most of the owner's job.

What goes in each section

Summary and decisions needed. Half a page: overall status against the milestones, the two or three issues that matter, and any owner decisions needed, each with the date it is needed by. If a reader stops here, they should still know what to do.

Schedule status, milestones and critical path. The data date, a milestone table with baseline and forecast dates, the critical path in words, and float on the near-critical paths. The narrative must explain what changed since last month and why. The native file, an XER from Oracle Primavera P6 on Northgate, comes with it; a PDF is not a schedule.

Progress by WBS. Planned and actual per cent complete for each WBS element, with progress photos keyed to grid lines. This is where the report meets the payment application.

Look-ahead. The next four to six weeks of work, the trades on site and the inspections and hold points coming up. The weekly three-week look-ahead is a separate tool, covered later in this track.

Procurement, submittals, RFIs and changes. Exceptions from each log: long-lead items at risk, submittals past their return date, RFIs older than target, and changes by status with values. Lessons 9 and 10 set out the measures.

Payment status. Contract Price with approved changes, billed to date, holdback retained and this month's claim, from the GC 5.2 application. The cost forecast is the owner's job and belongs to the next lessons on cost reports and cash flow.

Keep the report and the invoice apart. Under Ontario's Construction Act, payment is driven by the proper invoice, and a contract cannot make a proper invoice depend on the payment certifier's certification or the owner's approval. Since January 1, 2026, an invoice is also deemed proper unless the owner points out its defects in writing within seven days. A thin report is a reason to press the contractor under Division 01, not a reason to sit on the invoice. Ask your lawyer how your Supplementary Conditions handle this.

Quality, safety and risks. NCRs opened and closed, hold points released, safety statistics from the constructor, and the top risks with owners and actions.

Six tests of a report you can trust

AACE International publishes recommended practices on reviewing schedule updates, notably RP 53R-06, Schedule Update Review. An AACE article summarizing that family of practices lists the checks: contract compliance, a complete submittal with narrative and native file, comparison to baseline and the last accepted update, changes to logic and durations, an accurate narrative, signs of manipulation, critical and near-critical paths, and consistency with minutes, change orders and photos. Owners can turn that into six practical tests:

1. Do the documents agree? Per cent complete in the schedule, per cent billed in the payment application and what the photos show should tell the same story.
2. Does the narrative explain change? If the critical path moved, the report should say why.
3. Is the native file included? Without it, nobody can check logic or float.
4. Do forecasts move? A forecast that never changes while actual progress lags is a warning sign.
5. Do issues close or vanish? Last month's risks should appear as closed, open or escalated, not disappear.
6. Do the numbers reconcile month to month? Last month's "billed to date" plus this month's claim equals this month's "billed to date".

The owner's representative adds a seventh check of its own: does the report match what the representative saw on site that month?

The owner's own report

The contractor's report is written for the project team. The owner's executives, lenders or board need something shorter and independent. The owner's representative writes its own monthly report: a one-page dashboard, a short narrative and the decisions needed from the owner. It uses the contractor's data but adds the owner's view: total cost forecast including owner costs and contingency, risks to the owner's business dates (such as racking and occupancy), and an honest opinion on whether the contractor's forecasts are believable. On Northgate, it also updates the owner's master schedule in Microsoft Project from the contractor's P6 update; lesson 13 covers that monthly check in detail.

Northgate worked example

On Northgate Distribution Centre (fictional), Halvorsen Builders Ltd. (fictional) applies for payment monthly, with each payment period ending on the last day of the month. For this example, assume Division 01 requires its monthly report and P6 update within five Working Days after month end, and the owner's representative issues its owner's report to Northgate Logistics Inc. (fictional) within a further five. These periods are illustrative. Figure 2 shows the July 2027 cycle; see the Northgate fact sheet for the milestones.

View the data

Date (2027)	Event
Sat Jul 31	Payment period ends; application dated; schedule data date
Fri Aug 6	Halvorsen's report, P6 update and payment application due
Mon Aug 9 to Thu Aug 12	Owner's representative tests the report
Fri Aug 13	Owner's report issued to Northgate Logistics
Tue Aug 24	OAC meeting reviews open questions

Running the tests

Halvorsen's July report says the project is on track: every milestone forecast on its baseline date, including M6, roof complete and weathertight, on Friday September 3, 2027. The owner's representative runs the tests. Figure 3 shows the first one, planned against actual progress by WBS element, with illustrative numbers.

View the data

WBS	Element	Planned %	Actual %	Gap
2	Sitework and services	70	68	-2
3	Foundations and slab-on-grade	100	100	0
4	Structure	85	80	-5
5	Roofing and envelope	30	22	-8
6	Office mezzanine and interiors	10	8	-2
7	Mechanical, electrical, fire protection	20	18	-2
8	Dock doors and equipment	5	5	0
9	Commissioning and turnover	0	0	0

Three findings come out. First, roofing is eight points behind plan, yet the payment application claims 30% on the roofing line of the schedule of values. The documents disagree (test 1), so the owner's representative asks Ridgeline Architects Inc. (fictional), as payment certifier, to check that line before certifying. Second, M6 is still forecast on September 3, but the narrative does not explain how. The P6 file shows total float on the roofing path has dropped from 10 to 4 Working Days and the remaining roofing durations were shortened (tests 2 and 4). That may be a real plan to add a second crew, or it may be optimism; the owner's representative asks Halvorsen to say which. Third, last month's risk on the joist delivery has vanished from the risk table (test 5). The joists did arrive on July 5, so the risk should be shown as closed, not dropped. All of these figures are illustrative.

None of this is a claim or a dispute. It is the normal work of making the record accurate. The owner's report of August 13 says it plainly: milestones forecast on baseline, roofing behind plan with reduced float, a recovery plan requested, and one owner decision needed on the office finishes by August 27.

Owner's move

• Specify the report. Put the contents, the due date and the native schedule file in Division 01. A report that is not required arrives late and thin.
• Read the three documents together. Schedule update, payment application and report, side by side, every month.
• Ask for the narrative of change. What moved, why, and what the contractor is doing about it.
• Write your own report. One page for the owner's executives, with your view, not a forwarded copy of the contractor's.
• Keep a month-to-month file. Trends in float, RFIs and progress gaps matter more than any single month.

Common mistakes

1. Accepting a PDF schedule. Without the native file, logic, float and duration changes cannot be checked.
2. Reports that only describe work done. Without forecasts, risks and decisions, the report is history, not management.
3. Billing ahead of progress unchallenged. Over-certification erodes the owner's security and hides slippage.
4. Green status with shrinking float. A milestone "on track" with float falling every month is a trend, not good news.
5. Forwarding the contractor's report as the owner's report. The owner's executives need an independent view.

Quick quiz

1. Under CCDC 2-2020 GC 3.4, how often must the contractor update its construction schedule, unless the Contract Documents say otherwise?

   1. Weekly
   2. Monthly
   3. Quarterly
   4. Only when there is a delay

2. Under GC 5.2, what date does a Northgate payment application for July 2027 carry?

   1. The date it is sent
   2. The last day of the payment period, July 31
   3. The date of the OAC meeting
   4. The date the Consultant certifies it

3. The schedule shows roofing 22% complete, but the payment application claims 30%. Which test does this fail?

   1. Native file included
   2. Documents agree
   3. Issues close or vanish
   4. Narrative explains change

4. Why should the native P6 file come with the report?

   1. It is smaller than a PDF
   2. It allows logic, float and duration changes to be checked
   3. CCDC requires XER format
   4. It replaces the narrative

5. M6 is forecast on its baseline date, but float on its path fell from 10 to 4 days. What should the owner's representative do?

   1. Report it as green and move on
   2. Issue a default notice
   3. Ask the contractor to explain the recovery and flag the trend in the owner's report
   4. Change the baseline

Show answers and explanations

1. B. GC 3.4 requires monthly updates unless the Contract Documents stipulate otherwise.
2. B. Applications are dated the last day of the payment period, which is the last day of the month unless the parties agree otherwise.
3. B. Schedule progress, billing and photos should tell the same story.
4. B. A PDF shows results; the native file shows how they were produced.
5. C. Shrinking float is a trend worth reporting. Asking for the recovery plan is normal management, not a dispute.

Key terms

Monthly progress report

The contractor's monthly narrative of progress, forecast, issues and decisions, tied to the schedule update and payment application.

Data date

The date up to which progress is recorded in a schedule update.

Schedule update

The contractor's monthly revision of the construction schedule with actual progress, under GC 3.4.

Schedule of values

The breakdown of the Contract Price used to value progress in payment applications.

Narrative of change

The part of the report that explains what moved in the schedule since last month, and why.

Owner's report

The owner's representative's own short, independent monthly report to the owner.

References

1. Canadian Construction Documents Committee, CCDC 2-2020 Stipulated Price Contract, GC 3.4 and GC 5.2 (paraphrased).
2. Marina G. Sominsky, Ronald M. Winter and Katherine Baron, Getting back to basics: update schedule review by the numbers, AACE International Source (August 2022).
3. Catherine E. Willson, Ontario's new construction act: summary and timelines of major changes, Construction Canada (May 2018).
4. Fasken, Ontario's amendments to the Construction Act take effect January 1, 2026 (December 2025).
5. Ontario Association of Architects, Construction meetings: minutes (2015, updated June 2020).

Verified on November 6, 2026.

Next lesson in this trackSchedule updates: the monthly check