Study guide
20.1 Cost Reports, Performance Dashboards & the Reporting Cycle
AACE Certified Cost Professional CCP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Total Cost Management (TCM) Framework
1.1 AACE CCP Exam Structure, Eligibility & the In-Exam Memo 1.2 The Total Cost Management (TCM) Framework & PDCA Cycle 1.3 Strategic Asset Management vs. Project Control Processes
2 Chapter 2: Cost Estimating Fundamentals & Classification
2.1 AACE Recommended Practice 18R-97 Estimate Classification System 2.2 Direct vs. Indirect Costs and Cost Element Breakdown 2.3 Quantity Takeoff, Standard Cost Databases & Pricing Sources
3 Chapter 3: Conceptual & Parametric Estimating Techniques
3.1 Capacity Factoring & the Six-Tenths Rule 3.2 Parametric Estimating, Lang Factors & Hand Factors 3.3 Cost Indices, Location Adjustments & Escalation Modeling
4 Chapter 4: Cost Engineering Economics & Time Value of Money
4.1 Simple & Compound Interest, Equivalence & Cash Flow Diagrams 4.2 Discrete Compounding Formulas & Uniform Series Factors 4.3 Nominal vs. Effective Interest Rates & Continuous Compounding
5 Chapter 5: Project Profitability & Capital Investment Decision-Making
5.1 Net Present Value (NPV) & Present Worth Analysis 5.2 Internal Rate of Return (IRR) & Incremental IRR Analysis 5.3 Payback Period, Benefit-Cost Ratio (BCR) & Breakeven Analysis
6 Chapter 6: Depreciation Methods, Taxes & Asset Valuation
6.1 Classical Depreciation Methods (Straight-Line, DDB, Sum-of-Years-Digits) 6.2 Modified Accelerated Cost Recovery System (MACRS) & Tax Shield 6.3 After-Tax Cash Flow Analysis & Asset Replacement Economics
7 Chapter 7: Project Scope, Work Breakdown Structure (WBS) & Baselines
7.1 Work Breakdown Structure (WBS) Principles & the 100% Rule 7.2 Organizational Breakdown Structure (OBS) & Control Accounts 7.3 Establishing the Performance Measurement Baseline (PMB)
8 Chapter 8: Critical Path Method (CPM) Planning & Scheduling Logic
8.1 Precedence Diagramming Method (PDM) & Dependency Relationships 8.2 Forward Pass, Backward Pass & Float Calculations (Total vs. Free Float) 8.3 Schedule Baseline Development, Calendar Constraints & Milestones
9 Chapter 9: Schedule Optimization, Compression & Probabilistic PERT
9.1 Schedule Crashing & Least-Cost Slope Optimization 9.2 Fast-Tracking Risks, Overlap Analysis & Execution Strategies 9.3 PERT Three-Point Estimating & Probabilistic Duration Variance
10 Chapter 10: Resource Management, Productivity & Learning Curves
10.1 Resource Loading, Leveling vs. Resource Smoothing 10.2 Labor Productivity Factors, Work Sampling & Efficiency Loss 10.3 Learning Curve Theory (Wright Cumulative vs. Crawford Unit Models)
11 Chapter 11: Earned Value Management (EVM) Core Principles & Metrics
11.1 ANSI/EIA-748 EVM Framework & Core Metrics (PV, EV, AC) 11.2 EVM Variances & Performance Indices (CV, SV, CPI, SPI) 11.3 Work Progress Measurement Techniques (0/100, 50/50, Milestone Weighting)
12 Chapter 12: EVM Forecasting, Indices & Baseline Change Control
12.1 Estimate at Completion (EAC) & Estimate to Complete (ETC) Formulas 12.2 To-Complete Performance Index (TCPI) & Variance at Completion (VAC) 12.3 Integrated Change Control, Baseline Revisions & Trend Management
13 Chapter 13: Risk Management Planning & Qualitative Risk Analysis
13.1 Risk Management Framework & Risk Breakdown Structure (RBS) 13.2 Qualitative Risk Assessment & Probability-Impact (P-I) Matrix 13.3 Risk Response Strategies & Threat/Opportunity Management
14 Chapter 14: Quantitative Risk Analysis, Monte Carlo & Contingency Estimating
14.1 Expected Monetary Value (EMV) & Decision Tree Analysis 14.2 Monte Carlo Simulation & Probability Distributions in Cost/Schedule 14.3 Contingency Estimating & AACE Recommended Practice 40R-08
15 Chapter 15: Contract Types, Procurement Strategy & Commercial Terms
15.1 Contract Types & Risk Allocation (Firm Fixed Price, Cost-Plus, T&M) 15.2 Project Delivery Systems & Procurement Lifecycle (DBB, DB, EPC, CMAR) 15.3 Commercial Terms, Bonds, Retainage & Claims Management
16 Chapter 16: Quality Management, Value Engineering & Technical Communication
16.1 Quality Management & Cost of Quality (CoQ) 16.2 Value Engineering, Function Analysis System Technique (FAST) & Life Cycle Costing 16.3 The CCP Memo, Cost Report Writing, Data Presentation & AACE Ethics 16.4 AACE CCP Capstone Review & High-Yield Exam Strategies
17 Chapter 17: Cost Accounting, Budget Administration & Cost System Governance
17.1 Historical Cost Databases, Data Organization & Benchmarking 17.2 Committed Costs, Accruals, Work-in-Place & Invoice Validation 17.3 Budget Creation, Operating Budgets & Funding Requirement Forecasting 17.4 Cost System Governance, the Code of Accounts & Preserving Project Controls Data
18 Chapter 18: Estimate Preparation, Review & Cost Driver Analysis
18.1 ROM, Summary-Level and Detailed Estimates: Preparing and Reviewing 18.2 Verifying the Basis of Estimate & Analyzing Estimates 18.3 Cost Drivers, Change Order Impact & Resource Utilization Analysis
19 Chapter 19: Interfacing with Other Disciplines & Stakeholders
19.1 Coordinating with Internal Disciplines & Supporting Project Leadership 19.2 Communicating Cost Estimates and Cost/Schedule Key Performance Indicators 19.3 Supporting Tenders, Procurement, Audits, Field Verification & Recovery
20 Chapter 20: Cost Reporting, Dashboards & Profitability Analysis
20.1 Cost Reports, Performance Dashboards & the Reporting Cycle 20.2 Variance Reports & Explaining Project Financial Health 20.3 Profit Margin Analysis & Profitability Enhancement
21 Chapter 21: Cost Support to Scheduling & the CCP Exam Memo
21.1 Cost and Resource Loading Summaries from the Project Schedule 21.2 Translating Schedule Change into Cost Impact 21.3 Writing the CCP Exam Memo: A Worked Domain 7 Walkthrough
20.1 Cost Reports, Performance Dashboards & the Reporting Cycle
Key Takeaways Explain This Topic AI
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.
Last updated: August 2026
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.