Cost Dashboard

One page, one truth: current cost versus target for each module, refreshed on a fixed rhythm.

Time45 min
FormatSolo
StageTrack

Cost Dashboard: what it is and why it works

A Cost Dashboard is a single page that shows, for every module or major cost element, the target cost, the current estimated cost, the gap, the trend since the last refresh and the confidence grade of the current figure. It has one data owner and one refresh rhythm, weekly or biweekly during active design, and a simple alert rule, such as any module drifting more than 5% above target or moving the wrong way for two consecutive refreshes. It is reviewed in a meeting that already exists, so cost status gets discussed alongside schedule and technical issues rather than in a separate forum nobody attends.

The dashboard works because conflicting spreadsheets destroy trust faster than bad news does. When engineering, purchasing and finance each carry their own numbers, meetings are spent reconciling figures instead of acting on them. A single, owned source with visible confidence grades lets people argue about decisions rather than data. The lineage runs through project cost control and earned value management practice in US defense and space programs, where a disciplined, regular status against a baseline is central. The dashboard is the main input to the Cost Gate Review, surfaces the gaps that Variance Analysis explains, and makes the Cost Ownership Map visible by showing an owner beside each line.

What you need

Target cost per module from the cost breakdown
Current estimates per module with their confidence grades
A named data owner and a fixed refresh date
An alert threshold and a list of the meetings where the dashboard is reviewed

What you get

One-page status: target, current, gap, trend and grade per module
Alerts on modules drifting beyond the threshold
A history of refreshes showing the trend over time
Actions decided in the review meeting, linked to owners

When to use it

When cost status lives in spreadsheets that contradict each other.

How to do it, step by step

Define the dashboard lines: module, target cost, current cost, trend.
Set one refresh rhythm and one data owner.
Show confidence grades next to the numbers.
Add a threshold alert: any module drifting more than five percent.
Review the dashboard in the recurring project meeting.

Worked example: One page for a compressor package development

Illustrative scenario — figures are realistic but not from a real company.

An industrial gas equipment company was developing a new skid-mounted compressor package with a target cost of $412,000, split into nine modules. Engineering tracked cost in a design spreadsheet, purchasing in a sourcing file and finance in a monthly report. The three disagreed by up to $35,000.

The project named a cost engineer as sole data owner and set a biweekly refresh on Thursday, before the Monday project meeting.
The dashboard showed nine lines with target, current estimate, gap in dollars and percent, a trend arrow, the A/B/C grade and the owner's name.
The alert rule flagged any module more than 5% above target. On the first refresh, the cooler module was 11% over, and the enclosure was on target but graded C.
The Monday meeting spent ten minutes on the dashboard: an action to requote the cooler with two suppliers and one to upgrade the enclosure estimate with a sheet metal quote.

Result. Within six weeks the spreadsheets were retired, the cooler came back to 3% over target after a design change to the fin pitch, and the enclosure quote came in 8% above its guess, which the team caught before the design was frozen. Total status moved from 7% over to 2% over target.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

Multiple owners updating the dashboard, which reintroduces conflicting numbers.Name one data owner who collects inputs and publishes the only official version.
Showing numbers without confidence grades, which makes a guess look like a quote.Display the A/B/C grade next to each current cost.
Adding a new meeting to review the dashboard.Put the dashboard on the agenda of an existing project meeting with a fixed time slot.
Tracking so many lines that nobody reads them.Keep to modules or the top cost elements, and drill down only on alerted lines.

Frequently asked questions

What should a project cost dashboard include?

At minimum: the item or module, target cost, current estimate or actual, gap in value and percent, trend since the last update, confidence in the current number, and the owner. Add an alert rule and a date of last refresh. Keep it to one page so it can be discussed in a few minutes.

How often should a cost dashboard be updated?

Match the pace of change. During active design, weekly or every two weeks is typical; during stable production, monthly may be enough. The key is a fixed rhythm aligned with the meeting where decisions are made, so the numbers are fresh when people need them.

How does a cost dashboard relate to earned value management?

Earned value management tracks cost and schedule performance of project work against a baseline, using measures such as planned value, earned value and actual cost. A design-to-cost dashboard tracks the product's estimated unit or build cost against its target. Both rely on a baseline, regular status and variance thresholds, and they can sit side by side in project reviews.

Origin

Cost transparency dashboards — project cost control practice (earned value lineage, US DoD/NASA).

Used in these playbooks

Gate cost review pack 1 day

One day before each gate: dashboard refreshed, variances explained, attainment measured — and the go/no-go decision documented.