20.1 Cost Reports, Performance Dashboards & the Reporting Cycle
Key Takeaways
- Create Reports and Documentation is 11% of the CCP exam (13 of 119 questions), covering cost reports and dashboards, cost performance reporting, and schedule status reports.
- Progress, cost, commitments, and schedule must share one published data date; staggered cutoffs manufacture variances that are artifacts of the mismatch rather than real performance.
- Cost performance reporting has three layers — position at the data date, trend over at least six periods, and forecast to completion — and reporting position alone is the most common weakness.
- Plotting contingency drawdown against percent complete predicts overruns earlier than any earned value index, because contingency is consumed by realised risk before the indices fully absorb it.
- A schedule status report showing improvement must state whether the gain came from production or from re-logic, constraint removal, or duration changes.
20.1 Cost Reports, Performance Dashboards & the Reporting Cycle
Domain 3 of the CCP blueprint — Create Reports and Documentation — is 11% of the exam, 13 questions. Its tasks are 3.A prepare/update cost reports and dashboards, 3.C report cost performance, and 3.E prepare schedule status reports. The domain exists because the report is the product. Every calculation in this guide reaches a decision-maker through a document, and a correct number in an unreadable report changes nothing.
1. The Reporting Cycle
Reporting is a repeating process with hard dependencies. Compressing it produces either late reports or wrong ones.
| Day (typical monthly cycle) | Activity | Owner |
|---|---|---|
| Cutoff (day 0) | Data date fixed for progress, cost, commitments, and schedule alike | Project controls |
| +1 to +2 | Field quantities and progress collected and verified | Field engineering |
| +2 to +3 | Accruals raised and validated against work in place | Cost engineering |
| +3 to +4 | Actuals downloaded; ledger reconciled to project cost system | Cost / accounting |
| +4 to +5 | Earned value computed; variances analysed; forecast updated | Cost engineering |
| +5 to +6 | Schedule update and critical path analysis reconciled to progress | Planning |
| +6 to +7 | Report drafted, reviewed, and issued | Project controls |
| +7 to +10 | Review meetings; corrective actions and recovery decisions | Project management |
[!IMPORTANT] A common data date is non-negotiable. If cost is cut off on the 25th, progress on the 28th, and the schedule on the 30th, the variances reported are partly artifacts of the mismatch. Every stream must share one cutoff, and the cutoff must be published in advance so contributors plan to it.
2. What a Cost Report Must Contain
| Element | Content | Why |
|---|---|---|
| Header block | Project, report period, data date, revision, preparer | Makes the report citable and auditable |
| Executive summary | Forecast, variance to budget, principal causes, decisions required | Most readers stop here |
| Cost summary table | Budget, commitment, actual, accrual, forecast, variance by major area | The core of the report |
| Earned value metrics | PV, EV, AC, CV, SV, CPI, SPI, EAC, ETC, VAC, TCPI | Performance measurement |
| Trend charts | Cumulative S-curves and index trends over at least six periods | Direction matters more than position |
| Contingency status | Original, drawn, remaining, with drawdowns tied to risk events | Prevents silent consumption |
| Change status | Approved, pending, and anticipated, with values | The forward view |
| Cash flow / funding | Actual and forecast disbursement by period | The finance interface |
| Exceptions | Accounts breaching threshold, with cause and action | Directs attention |
| Basis and assumptions | The forecast method used and any material assumption | Makes the number defensible |
3. Designing a Dashboard That Works
A dashboard is a compression of the report, and compression means choosing what to lose.
| Principle | Application |
|---|---|
| One screen, no scrolling | If it does not fit, it is a report, not a dashboard |
| Status, trend, and forecast together | Where we are, which way we are moving, where we will end |
| Thresholds, not raw values alone | A CPI of 0.94 means nothing to a reader without the tolerance band |
| Consistent colour semantics | Red always means the same thing on every tile |
| Drill path | Every tile traces to the detail behind it |
| No metric without an owner | An indicator no one is accountable for will not be acted on |
Selecting the tile set
A capital project dashboard that carries these eight tiles covers the ground without clutter: forecast cost at completion versus budget; cumulative CPI trend; percent complete planned versus actual; contingency remaining versus percent complete; commitment ratio; change value approved and pending; safety metric; and forecast completion date versus contract date.
[!TIP] Plot contingency drawdown against percent complete on the same axes. If the contingency line falls faster than the completion line, the project is consuming its risk provision faster than it is retiring risk. This single comparison predicts overruns earlier than any earned value index, because contingency is drawn down by realised risk before performance indices fully absorb it.
4. Reporting Cost Performance (Task 3.C) and Schedule Status (Task 3.E)
Cost performance reporting has three layers, and the exam expects a cost professional to distinguish them:
- Position — where the project stands now: CV, SV, CPI, SPI at the data date.
- Trend — the direction over time. A single period's index is noise; six periods is signal.
- Forecast — where it will end: EAC by a stated method, ETC, VAC, and the funding requirement.
Reporting position alone is the most common weakness. It tells the reader what happened without telling them what it means or what will happen.
The schedule status report
A cost engineer is expected to prepare or contribute to schedule status reporting, and the content is not the same as cost reporting:
| Element | Content |
|---|---|
| Data date and update basis | When, and whether progress was measured or estimated |
| Milestone status | Baseline, forecast, and variance in days for each key milestone |
| Critical path | Current controlling path, and whether it has shifted since the last update |
| Float position | Total float on the critical and near-critical paths, and the trend |
| Logic and calendar changes | Any change made since the last update, with justification |
| Forecast completion | Against contract date, with the driving activities named |
| Recovery actions | What is being done, by whom, and its modelled effect |
[!WARNING] Disclose logic changes. A schedule that appears to recover because activities were re-sequenced, constraints removed, or durations shortened without a production basis has not recovered. Any schedule status report that shows improvement must state whether it came from production or from re-logic — an omission here is exactly the kind of incomplete reporting the Canons of Ethics prohibit.
A project cuts off cost data on the 25th, collects field progress on the 28th, and updates the schedule on the 30th of each month. The monthly report shows an unexplained favourable cost variance that reverses the following period. What is the most likely cause and the correct remedy?
A project is 35% complete and has drawn 68% of its original contingency. Cumulative CPI is 0.97 and the sponsor considers the position acceptable. What does the contingency comparison indicate?
A schedule update shows the forecast completion date improving by three weeks. Investigation reveals that two finish-to-start relationships were changed to start-to-start with lag and a milestone constraint was removed; physical production was unchanged. How must the schedule status report present this?