Capital Project Earned Value and Cost Overrun Dashboard Matrix
Design a project controls dashboard matrix mapping WBS budgets, earned value metrics, and contingency burn rates for capital projects.
Use this template when scoping cost engineering and earned value management (EVM) dashboards for large-scale construction programs. It maps complex cost baselines into structured dashboard views.
Role: Lead Project Controls Analyst and Capital Program BI Architect.
Context
- Capital Program Name: {{program_name}}
- Budget Scale & Currency: {{budget_threshold}}
- Target Reporting Audiences: {{reporting_layers}}
- Project Controls Stack: {{cost_tracking_tools}}
- Work Breakdown Structure Depth: {{wbs_levels}}
- Contingency Governance: {{contingency_draw_policy}}
Task
Develop an Earned Value Management (EVM) and cost control dashboard specification matrix for {{program_name}} that aligns Work Breakdown Structure budget variances, forecast at completion, and contingency utilization into visual components.
Method
- Review the Work Breakdown Structure structure across {{wbs_levels}} to determine data roll-up rules from package level to executive tier.
- Map core EVM metrics (PV, EV, AC, CPI, SPI, EAC, VAC, TCPI) against target cost tolerance thresholds.
- Integrate {{contingency_draw_policy}} into trend lines and burn-rate tracking components.
- Evaluate {{cost_tracking_tools}} schema to match data extraction points with real-time financial tracking needs.
- Design user views tailored for {{reporting_layers}}, distinguishing between program oversight and package manager details.
- Select suitable financial visualization formats including S-curves, waterfall variance charts, and cost heatmaps.
- Define drill-through paths from macro program summary down to line-item change order logs.
- Build the consolidated dashboard engineering matrix.
Constraints
- MUST represent standard Earned Value formulas accurately without non-standard metric definitions.
- MUST NOT exceed the granularity supported by {{wbs_levels}}.
- MUST include explicit contingency draw indicators according to {{contingency_draw_policy}}.
- All financial variance calculations must reference the approved {{budget_threshold}} baseline.
Output format
1. Dashboard View Architecture
A brief outline of the 3 reporting tiers (Program Executive, Project Controls, Package Manager).
2. EVM & Cost Dashboard Specification Matrix
A Markdown table containing the following columns: | Dashboard View | Metric / KPI | Formula / Grain | Visual Type | Primary Source | Variance Alert Condition | Drill-down Target |
3. Data Integration Constraints
A numbered list of 3-5 technical requirements for syncing {{cost_tracking_tools}} with the dashboard data model.
Self-review
- Are all standard EVM metrics (CPI, SPI, EAC, VAC) explicitly mapped in the matrix?
- Does the design properly reflect the contingency rules from {{contingency_draw_policy}}?
- Are drill-down paths viable given the WBS depth in {{wbs_levels}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.