---
title: "Project Controls Monthly Report: Structure and Template"
description: "Write a project controls monthly report that drives decisions: a proven structure, what each section needs, a sample narrative and AI drafting tips."
url: https://optimizeall.com/blog/project-controls-monthly-report
updated: 2026-10-05
---

# Project Controls Monthly Report: Structure and Template

Optimize All Editorial · 20 July 2026 · 7 min read

![Dark blue cover with horizontal schedule bars and the words Project controls and finance](https://optimizeall.com/api/v1/files/01a10be7-a427-7c21-acab-1a7793b6b239)

Most project controls teams spend a large part of every month producing a report. Many of those reports are long, accurate and almost entirely unread. They describe what happened in great detail but never quite say what it means or what someone needs to decide.

A good **project controls monthly report** is different. It is short at the top, evidence-based underneath, and built around decisions. This guide sets out a structure that works across industries, explains what each section needs, gives a sample narrative and shows where AI can take the drudgery out of drafting without taking the judgement out of the content.

## Start with the reader

Before choosing charts, decide who reads the report and what they need:

| Reader | What they need from the report |
|---|---|
| Sponsor or steering board | The forecast, the main risks and the decisions required — in two minutes |
| Project manager | Where performance is slipping and what actions are working |
| Control account managers | Their own variances, compared with the rest of the project |
| Finance | Cost forecasts, cash flow and accrual positions |
| Client (if shared) | Progress against contract milestones and approved changes |

A single report can serve several audiences if it is layered: an executive summary that stands alone, followed by sections that provide the detail.

## A structure that works

### 1. Executive summary (one page)

Write this last but put it first. It should answer five questions:

1. Where are we against the baseline for cost, schedule and key milestones?
2. Where do we forecast we will finish, with what confidence?
3. What changed since last month, and why?
4. What are the top three risks or issues?
5. What decisions or support are needed, from whom and by when?

Use a small status table and three to five short paragraphs. If a sponsor reads only this page, they should be able to act.

### 2. Schedule performance

- Key milestone table: baseline, previous forecast, current forecast, variance.
- Critical path summary: what is driving the finish date, and did it change?
- Schedule quality metrics, such as those from a [DCMA 14-point assessment](/blog/dcma-14-point-schedule-assessment).
- Look-ahead: critical activities in the next period.

### 3. Cost performance

- Budget, actuals, commitments and estimate at completion by control account.
- Earned value metrics — CPI, SPI, cost and schedule variances — with trends, not single months.
- The planned, earned and actual [S-curves](/blog/s-curve-project-management) on one chart.
- Main variances explained: cause, impact and action.

### 4. Forecast

- Estimate at completion with its basis (formula, bottom-up or hybrid) and a range.
- Forecast finish date with confidence level if schedule risk analysis is available.
- Comparison with last month's forecast and explanation of the movement.

### 5. Risk, contingency and reserves

- Top risks with owners, actions and trend.
- Contingency and management reserve position, drawn and remaining, compared with remaining risk exposure. Our guide to [contingency vs management reserve](/blog/contingency-vs-management-reserve) shows a simple reserve table.

### 6. Change

- Changes approved, pending and rejected this period, with cumulative impact.
- Ageing of pending requests. See our guide to [project change control](/blog/project-change-control-process).

### 7. Decisions and actions log

- Decisions required, by whom and when.
- Actions from previous reports with status.

### Appendices

Detailed tables, control account reports, data quality notes and methodology. Readers who need them know where to look; everyone else does not have to wade through them.

## Writing narratives that lead to decisions

Weak narrative describes numbers. Strong narrative explains them and proposes action. Compare:

> *Weak:* "CPI for the month was 0.88 and SPI was 0.94. Cost variance was −310,000."

> *Strong:* "Mechanical installation is overrunning: CPI has fallen from 0.97 to 0.88 over three months because rework on pipe supports has absorbed around 1,800 hours. If productivity does not recover, the estimate at completion rises by about 0.9 million, which would use most of the remaining contingency. We recommend approving a design clarification by 15 May and a two-week targeted supervision increase; the decision is needed from the project board this month."

The strong version gives the cause, the quantified impact, the recommended action and the decision required. A useful pattern for every variance is **what — why — so what — now what**.

## A one-page executive summary template

| Item | Status | Comment |
|---|---|---|
| Cost (EAC vs budget) | Amber | EAC 52.4m vs 51.0m budget; within contingency |
| Schedule (forecast completion) | Red | Forecast 6 weeks late; switchgear delivery on critical path |
| Key milestone: energisation | Red | Forecast 12 June vs 1 May baseline |
| Contingency remaining | Amber | 1.1m remaining vs 1.4m identified exposure |
| Safety and quality | Green | No reportable incidents; two open non-conformances |

**Decisions required:** approve expediting cost for switchgear (0.15m) by 30 April; confirm acceptance of partial handover for Building B.

## A monthly reporting calendar

Good reports depend on a predictable cycle. A typical calendar for a monthly report looks like this:

| Working day after period end | Activity |
|---|---|
| Day 1–2 | Cost cut-off, accruals posted, progress measured against rules of credit |
| Day 2–3 | Schedule updated to the data date; quality checks run |
| Day 3–4 | Earned value calculated; variances identified by control account |
| Day 4–5 | Control account managers explain variances and update estimates to complete |
| Day 5–6 | Forecasts, risks and contingency reviewed; draft report compiled |
| Day 7 | Project manager review and sign-off |
| Day 8 | Report issued; decisions taken at the project board |

The exact days vary, but the sequence matters: data first, then analysis, then explanation, then forecast, then decisions. Skipping straight to the narrative before the numbers are stable is how reports end up contradicting themselves.

## Common mistakes

- **Too long at the top.** If the executive summary runs past a page, it is not a summary.
- **Charts without messages.** Every chart needs a one-line caption saying what it shows.
- **Monthly numbers without trends.** One month's CPI means little; three to six months tell a story.
- **Inconsistent data dates.** Schedule, cost and risk must report the same period.
- **No forecast range.** Single-point forecasts create false precision.
- **Decisions buried in the appendix.** Put them on page one.

## Keeping the report consistent month to month

Readers learn where to look. Keep the same section order, chart types, colour conventions and definitions every month, and record any change in methodology in a short note at the front. Consistency lets sponsors spot real changes in seconds instead of re-learning the report each time.

## Using AI to draft — safely

AI assistants are well suited to the mechanical parts of reporting: pulling numbers from exports into tables, comparing this month with last month, drafting variance explanations from structured inputs and checking for inconsistencies between sections. A practical workflow:

1. Produce the numbers from your controlled systems.
2. Ask the assistant to draft narratives **using only the data provided** and to flag uncertainties.
3. Have the control account manager correct causes and actions — the assistant cannot know why rework happened.
4. Label AI-assisted sections according to your governance policy.
5. A named person signs off the report.

Our guide to [AI for project scheduling](/blog/ai-for-project-scheduling) includes example prompts for the schedule section, and the printable [AI in project controls playbook (PDF)](/downloads/ai-in-project-controls-playbook.pdf) sets out review steps for AI-assisted reporting. For dashboards that complement the report, see [project controls KPIs](/blog/project-controls-kpis-dashboard).

## Building the skill

Clear reporting is where project controls turns data into decisions. Optimize All's free course [Project Controls with AI](/learn/project-controls-with-ai) includes report templates and narrative exercises, and the [PCI AI](https://pciai.org) PCL-AI credential treats reporting and governed AI as part of the controls leader's role. Our [PCI AI partner page](/partners/pci-ai) summarises the certification.

## Frequently asked questions

### How long should a monthly project report be?

The executive summary should fit on one page. The full report depends on project size, but detail belongs in sections and appendices that readers can skip.

### Who should write the narrative?

The controls team usually compiles it, but explanations of causes and actions should come from the control account managers who own the work. The project manager signs off.

### Should the report include a forecast range?

Yes, wherever possible. A range, or P50 and P80 values, communicates uncertainty honestly and supports better decisions.

### Can AI write the monthly report?

AI can draft much of it from verified data, but it cannot know causes, judge risks or make recommendations on its own. Treat its drafts as a starting point for the accountable authors.

### How do I get control account managers to provide explanations on time?

Agree a fixed reporting calendar, give them a short template (what, why, so what, now what) and review variances with them rather than chasing by email. When explanations are used in decisions, people see the value and respond faster.

---

*Optimize All is the official marketing partner of PCI AI and Certuvo.*

- [Project controls & finance](https://optimizeall.com/blog?category=project-controls)

## About Optimize All Editorial

Guides from the Optimize All editorial team on project controls, project finance and professional certification. Optimize All is the official marketing partner of PCI AI and Certuvo.

## Related articles

- [The S-Curve in Project Management: How to Read It](https://optimizeall.com/blog/s-curve-project-management): What the S-curve in project management shows, how to build planned, earned and actual curves, and how to read gaps, slopes and forecasts correctly.
- [Project Change Control: A Practical Process and Log](https://optimizeall.com/blog/project-change-control-process): Set up project change control that works: a six-step process, a change log template, impact assessment, decision rights and a worked example.
- [Contingency vs Management Reserve: What's the Difference?](https://optimizeall.com/blog/contingency-vs-management-reserve): Contingency vs management reserve explained: what each covers, who controls it, how to size it with risk analysis and how to report drawdowns honestly.
- [Project Controls KPIs: Building a One-Page Dashboard](https://optimizeall.com/blog/project-controls-kpis-dashboard): Choose the project controls KPIs that matter: leading versus lagging measures, CPI and SPI, forecast accuracy, change-order rate and float on one page.
- [Earned Value Management Explained: A Worked Example](https://optimizeall.com/blog/earned-value-management-explained): Earned value management step by step: PV, EV, AC, CPI, SPI, EAC and TCPI with a full worked example, common traps and how to read the numbers.
- [AI for Project Scheduling: What Works and What to Avoid](https://optimizeall.com/blog/ai-for-project-scheduling): Where AI for project scheduling adds value today: drafting schedules, quality checks, delay prediction and narratives, plus the governance planners need.