Skip to content
    Free Construction Template

    Construction Progress Report Template

    A weekly and monthly reporting structure for owners, developers, general contractors, CMs, and project-controls teams. It summarizes what changed during the reporting period, the current cost and schedule position, unresolved exposure, major decisions, risks, and the two-to-four-week look-ahead.

    The workbook includes a printable Executive Report sheet that reads from source sheets for cost, schedule, changes, and risk. No email required.

    View Example Report
    Fictional Project Example

    What one reporting period looks like

    Harbor Point Office Renovation is a fictional project used across Jet.Build's project-control resources. Every value, date, and status below is illustrative. Notice how the narrative, the forecast movement, the milestone exposure, and the open decisions are the same story told at different levels of detail.

    Fictional example — monthly progress report

    Harbor Point Office Renovation

    Reporting period Jul 21 – Aug 20, 2026 · Construction · Project-defined status: Watch

    What changed this period

    Construction progressed on schedule at Levels 1 and 2. Forecast increased $65,000, driven by the storefront coordination revision and the Level 3 framing condition still awaiting an RFI response. Pending exposure of $87,500 remains unresolved and is not yet in approved cost. Two decisions are required before the storefront fabrication release.

    Cost position

    Approved budget

    $4,250,000

    Committed cost

    $3,680,000

    Actual cost

    $2,940,000

    Forecast at completion

    $4,315,000

    Prior forecast

    $4,250,000

    Forecast movement

    +$65,000

    Storefront revision and Level 3 framing

    Pending change exposure

    $87,500

    Not approved cost

    Contingency remaining

    $185,000

    Milestones

    Level 2 MEP rough-in completeBaseline Aug 14 · Forecast Aug 14 · Complete
    Storefront fabrication releaseBaseline Aug 25 · Forecast Aug 25 · Watch
    Electrical switchgear releaseBaseline Aug 28 · Forecast Sep 2 · At Risk
    Level 3 framing revision startBaseline Sep 8 · Forecast Sep 8 · Watch

    Decisions required

    Confirm revised storefront package before fabrication releaseProject Manager · due Aug 22
    Return the switchgear review actionMEP Engineer · due Aug 28
    Answer RFI-046 so the framing revision can be pricedArchitect · due Aug 24
    Owner finish selection — Level 3 carpetOwner Representative · due Sep 5

    Want this same period already populated in the workbook, so you can see how the Executive Report sheet pulls from the source sheets?

    What a construction progress report is

    A construction progress report is the periodic account of what happened on a project between two dates. It is issued on a cadence, distributed to a defined list, and kept as part of the project record. Its job is to explain movement — in cost, in dates, in exposure, in risk — and to put the decisions that require attention in front of the people who can make them.

    That is a different job from showing current status. A reader who only wants today's numbers can look at a project dashboard. A progress report exists because someone needs to understand what changed, why it changed, and what happens next.

    The most common failure is a report that reproduces status. If the reader can compare this month's report to last month's and not learn anything they could not have read off a dashboard, the report has not done its work.

    What the report should include

    Report header

    Enough context that the rest of the report can be read correctly, and filed later.

    • Project and phase
    • Reporting period start and end
    • Reporting date
    • Project executive and PM
    • Project-defined status

    Executive summary

    What changed during the period, in the reporter's own words, with the cause named.

    • What moved
    • Why it moved
    • Accomplishments this period
    • 2–4 week look-ahead

    Cost position

    Approved position and unresolved exposure belong in the same report, in separate fields.

    • Approved budget
    • Committed cost
    • Actual cost
    • Forecast at completion
    • Prior forecast
    • Forecast movement
    • Pending change exposure
    • Contingency remaining

    Schedule position

    Milestones in relation to what has to happen before them, not a date list.

    • Key milestones
    • Baseline vs. forecast dates
    • Variance
    • What changed this period
    • Upcoming dependencies

    Changes

    A change affects the report long before it is executed.

    • Potential changes raised
    • Pricing status
    • Approved this period
    • Pending cost exposure
    • Time impact

    Risks and issues

    An issue without an owner and a date is a note, not a control.

    • Description
    • Exposure
    • Affected milestone
    • Next action
    • Responsible party

    Decisions required

    The part leadership actually has to act on before the next period.

    • Decision
    • Source record
    • Owner
    • Due date
    • What it holds up

    Progress report vs. dashboard vs. daily report

    Progress / status report

    Purpose
    Explains what changed between two dates and what decisions are required.
    Cadence
    Weekly or monthly, on a defined cycle
    Audience
    Owners, executives, project teams, formal distribution

    Dashboard

    Purpose
    Shows current position, open exposure, and exceptions, with drill-down.
    Cadence
    Continuous
    Audience
    Project team and leadership checking status between reports

    Daily report

    Purpose
    Records site activity, labor, equipment, deliveries, and conditions on one day.
    Cadence
    Daily
    Audience
    Field record and source documentation

    These are complementary, not competing. The dashboard surfaces the exception, the progress report explains it, and the daily report is often the source record that proves when it started. If you need the live view rather than the period package, the construction project dashboard template covers that side.

    Weekly vs. monthly reporting cadence

    There is no universal cadence. Many teams run both: a short weekly report that keeps the project team aligned, and a formal monthly package that goes to owners and leadership. The right answer depends on project complexity, pace of change, contract requirements, and the organization's own procedures.

    Weekly

    Operational. Short enough that people actually read it on a Monday morning.

    • What moved this week
    • Work planned for next week
    • Newly raised issues and RFIs
    • Deliveries and near-term procurement
    • Decisions needed within days
    • Immediate field constraints

    Monthly

    The formal package. Reconciled, explained, and kept as part of the project record.

    • Cost position and forecast movement
    • Explanation of why the forecast moved
    • Milestone status against baseline
    • Change exposure and approvals
    • Risk position and mitigation
    • Decisions requiring leadership action
    • Contingency position

    What leadership actually needs to see

    What changed since last period

    Leadership already knows the project exists. The report earns its place by explaining movement — cost, dates, exposure, risk — and naming the cause.

    Approved position vs. unresolved exposure

    These are different numbers. Reporting only approved cost understates the position; reporting only exposure overstates it. Show both, labeled.

    Exceptions, not the full register

    An executive report is not a copy of every project record. It is the items that moved, carry exposure, or require a decision.

    Decisions with an owner and a date

    Every escalation should name who decides and by when. Without that, the report documents a problem instead of moving it.

    A path back to the source record

    When a number is questioned, the report should be traceable to the change, RFI, submittal, commitment, or milestone that produced it.

    That framing is covered in more depth in executive construction reporting, which looks at the reporting model itself rather than the document.

    How cost, schedule, changes, risk, and decisions should appear

    Cost

    Show approved budget, commitments, actuals, forecast at completion, prior forecast, and the movement between them. The movement line is the one that matters, and it should carry an explanation tied to a record. Keep pending exposure in its own field. How the forecast itself is built is a separate discipline — the construction cost forecasting guide covers inputs, methods, and cost-to-complete.

    Schedule

    Report milestones against baseline, with variance in days and a note on what changed this period. A date that has not moved can still be at risk if the work feeding it is blocked — say so rather than reporting the unchanged date as good news.

    Changes

    Separate what was raised, what was priced, what was approved, and what remains unresolved. Approved amounts belong in the cost position; unresolved amounts belong in exposure. Both totals should be visible in the same report.

    Risk

    Each item should carry exposure where it can be estimated, the affected milestone, the next action, and a responsible party. Avoid invented probability scores unless the project has an approved scoring method.

    Decisions

    List the decision, the record it comes from, the owner, the date it is needed, and what it holds up. This is the section leadership reads first when the report is doing its job.

    How to write the “what changed this period” summary

    1. 1

      Start with the movement

      Lead with what changed and by how much. If the forecast moved $65,000, say so in the first sentence, then name the cause.

    2. 2

      Attribute the cause to a record

      "Forecast increased on the storefront coordination revision" is useful. "Costs trended up" is not. Tie the movement to a change, RFI, or milestone.

    3. 3

      Separate approved from pending

      State what has been approved this period and what remains unresolved. Keep the two in different sentences so neither gets misread.

    4. 4

      Say what is blocked, and by whom

      If a release is held pending a review action, name the action, the party, and the date it is needed.

    5. 5

      Close with the look-ahead

      Two to four weeks of what is coming and what has to be decided to protect it. This is what turns a recap into a usable report.

    How to use the Excel workbook

    The workbook has seven sheets: Executive Report, Project Summary, Cost & Forecast, Schedule & Milestones, Changes & Decisions, Risks & Issues, and Instructions & Definitions. The Executive Report reads from the others.

    1. 1

      Set the reporting cut-off

      Enter the period start, period end, and reporting date on the Project Summary sheet. Use the same cut-off across every source sheet so the numbers reconcile.

    2. 2

      Update the cost position

      Maintain Cost & Forecast by cost code. Revised budget, forecast movement, and variance are calculated; approved changes stay separate from pending exposure.

    3. 3

      Update milestones

      Maintain Schedule & Milestones with baseline and current forecast dates. Variance in days is calculated, and each row carries what changed this period.

    4. 4

      Update changes and decisions

      Maintain Changes & Decisions. Log pending exposure before approval, and record the required decision, owner, and due date.

    5. 5

      Update risks and issues

      Maintain Risks & Issues with exposure, affected milestone, next action, and responsible party. No probability scoring is imposed.

    6. 6

      Write the executive summary

      Explain what changed and why. The summary field feeds directly into the Executive Report sheet.

    7. 7

      Review and issue the Executive Report

      The Executive Report sheet reads from the source sheets and is set up to print. Use it as the period package.

    Before the next reporting cycle, use the construction project controls checklist to review how the underlying records are maintained.

    Common construction reporting mistakes

    Reproducing status instead of movement

    A report that restates current position without explaining what changed gives leadership nothing to act on.

    Reporting only approved cost

    Pending exposure that is excluded until approval makes the position look better than it is, then arrives as a surprise.

    Inconsistent cut-off dates

    Cost pulled at month-end, schedule pulled mid-month, and changes pulled the morning of the report do not reconcile.

    Escalations with no owner

    An issue listed without a responsible party and a due date will appear again, unchanged, next period.

    Copying the whole register

    Attaching every RFI and change to an executive report buries the three items that actually needed attention.

    Status colors without definitions

    If nobody can say what separates yellow from red on this project, the color is decoration rather than reporting.

    Unexplained forecast movement

    A new forecast number with no attribution invites the wrong question — whether the number can be trusted at all.

    When Excel is enough, and when manual reporting starts to break down

    Excel works well when

    • A single project or a small portfolio
    • One person controls the inputs
    • A stable, well-understood reporting format
    • Change volume the team can keep current by hand
    • Cost, schedule, and change records that are already reconciled elsewhere

    Strain usually appears when

    • Inputs maintained by different people in different systems
    • Cost, change, and schedule records that disagree at the cut-off
    • Reporting across many projects with different field definitions
    • Version confusion about which workbook was issued
    • Time spent reconciling sources instead of explaining movement
    • No traceable path from a summary number back to the record

    The workbook does not usually fail because a formula is missing. It fails when assembling the period takes longer than explaining it — and the same reconciliation problem shows up again at portfolio level, which is why capital project management tends to standardize reporting fields before anything else.

    Connected Reporting

    When the report is built from live records, the period package is assembly, not reconstruction.

    Jet.Build keeps budgets, commitments, actuals, change exposure, milestones, RFIs, submittals, approvals, and decisions on the same project record — so a reporting period can be pulled from the records the team already maintains, and any number in the report traces back to the record that created it.

    Explore Reporting Explore Cost Management

    Where AI can help with period reporting

    Jenny can help teams surface and summarize underlying project information and investigate the records behind a reported number — which change drove the movement, which review action is still open, which milestone the exposure attaches to.

    The project team remains responsible for forecasts, pricing, approvals, contractual decisions, scheduling judgment, and what the report ultimately says.

    Frequently asked questions

    What is a construction progress report?
    A construction progress report is a periodic report — usually weekly or monthly — that explains what changed on a project during a defined reporting period. It covers work completed, cost and schedule position, changes and unresolved exposure, risks and issues, decisions required, and a short look-ahead. Unlike a dashboard, it is issued on a cadence and carries a narrative.
    What should a construction progress report include?
    At minimum: project and reporting period identification, an executive summary of what changed, cost position including approved budget, commitments, actuals, forecast and pending exposure, milestone status against baseline, changes raised and approved during the period, risks and issues with owners, decisions required with due dates, and a two-to-four-week look-ahead.
    What is the difference between a construction progress report and a construction dashboard?
    A dashboard shows current position continuously, with exceptions and drill-down into the underlying records. A progress report explains what changed between two dates, why it changed, and what needs to be decided, and it is issued and distributed on a defined cycle. Most reporting environments use both.
    How often should construction progress reports be issued?
    There is no universal standard. Many teams issue a short weekly report to the project team and a formal monthly report to owners and leadership. Cadence depends on project complexity, pace of change, contract requirements, and the organization's approved reporting procedures.
    What should an executive construction report show?
    Movement and exceptions rather than the full record set: what changed since the prior period, the cause of any forecast movement, approved position separate from unresolved exposure, milestones at risk, and the decisions that require leadership action — each with an owner and a due date.
    Can I create a construction progress report in Excel?
    Yes. Excel works well when one person controls the inputs and the format is stable. The workbook on this page includes an Executive Report sheet that reads from source sheets for cost, schedule, changes, and risk. The strain appears when inputs live in different systems and reconciling them becomes the real work.
    What should be included in a weekly construction report?
    A weekly report is shorter and operational: what moved this week, work planned for next week, newly raised issues and RFIs, near-term deliveries and procurement, immediate field constraints, and decisions needed within days.
    What should be included in a monthly construction report?
    A monthly report is the formal package: cost position and forecast movement with an explanation of the cause, milestone status against baseline, changes raised and approved, pending exposure, contingency position, risk and mitigation status, and decisions requiring leadership action.
    How should pending changes and cost exposure be shown?
    In separate fields from approved cost. Show approved changes in the approved position, and show unresolved potential cost as pending exposure with its own total. Exposure is a project-control view of unresolved cost, not an automatic contractual liability, and the report should label it that way.
    How should risks and required decisions appear in the report?
    Each risk or issue should carry a description, the exposure if known, the affected milestone, the next action, and a responsible party. Each required decision should name the decision, the source record, the owner, and the date it is needed to protect downstream work.

    Related construction reporting resources

    The records behind a progress report each have their own process. These resources cover them in detail.

    See how Jet.Build builds the reporting period from live project records.

    Take about 30 minutes with our team to see how cost, schedule, changes, approvals, and decisions come together into the report leadership actually reads.

    Schedule a Demo