Blog · Board and management reporting · Manufacturing
Build a new product development dashboard from cost exports and milestone registers. Compare spending, forecast completion cost, and launch readiness with a worked manufacturing example and spreadsheet formulas.
An NPD dashboard compares new product development costs and launch milestones with an approved plan. Start with actual spending, remaining cost estimates, and a milestone register; keep the cost result separate from the evidence that the product is ready to launch.
The dashboard should answer whether the team can reach the next launch decision within its approved funding and schedule. It should also identify the workstream owner who needs to resolve a gap.
Use a fixed review date across every export. Keep the original approved budget visible beside the latest forecast, following the distinction in budget versus forecast. A forecast update changes what the team expects; it does not authorize more spending.
Make acceptance explicit. NASA's project life-cycle guidance describes decision points as reviews of readiness to progress. A manufacturer can apply that principle to its own product gates without copying aerospace review requirements: name the evidence, approver, and decision required for each milestone.
Prepare a cost export with project ID, workstream, posting date, document ID, and amount. Reconcile its total to the project ledger. Add approved budget, spending planned through the review date, and the latest estimate of remaining cost by workstream.
Remaining cost must cover work still needed, including unbilled work where appropriate. It must exclude costs already in actual spending. Explain how open purchase orders enter that estimate rather than adding the entire order register to actual costs.
Separate development and launch expenses from recurring costs after launch. The SBA's startup-cost guidance distinguishes one-time expenses from monthly expenses; the same separation helps prevent a product launch budget from silently absorbing ongoing operations. This dashboard uses a defined development-to-launch boundary.
The milestone register needs milestone ID, baseline due date, acceptance date, evidence reference, owner, and current forecast date. Customer evidence belongs in the gate criteria; customer analytics for new product development covers that supporting analysis.
Consider an illustrative US industrial manufacturer developing a pump controller. Its review date is October 23, 2026. Put the following inputs in a sheet named Costs, with headers in row 1 and workstreams in rows 2 through 5.
| Workstream | B: Approved budget (USD) | C: Planned spending to date (USD) | D: Actual spending (USD) | E: Remaining cost (USD) |
|---|---|---|---|---|
| Design | 180,000 | 160,000 | 150,000 | 50,000 |
| Validation | 240,000 | 200,000 | 190,000 | 70,000 |
| Tooling | 300,000 | 150,000 | 120,000 | 210,000 |
| Launch preparation | 80,000 | 40,000 | 30,000 | 50,000 |
| Total | 800,000 | 550,000 | 490,000 | 380,000 |
Add forecast completion cost in F2 and forecast overrun in G2, then fill down:
=D2+E2
=F2-B2
| Workstream | Forecast completion cost (USD) | Forecast overrun (USD) |
|---|---|---|
| Design | 200,000 | 20,000 |
| Validation | 260,000 | 20,000 |
| Tooling | 330,000 | 30,000 |
| Launch preparation | 80,000 | 0 |
| Total | 870,000 | 70,000 |
Sum columns B through G in row 6. Calculate actual spending against the time-phased plan, the forecast overrun percentage, and the share of approved budget spent:
=D6-C6
=IFERROR((F6-B6)/B6,"")
=IFERROR(D6/B6,"")
Actual spending is $60,000 below the $550,000 planned to date. Yet forecast completion cost is $870,000, or $70,000 above the approved budget: 8.75%. The team has spent 61.25% of its approved budget. These percentages are shown to two decimal places; neither represents physical completion.
Put the review date in Control!B1 as a real spreadsheet date. In a sheet named Milestones, put the milestone name in column A, baseline due date in B, and acceptance date in C. Empty acceptance cells mean unaccepted work.
| Milestone | Baseline due date | Acceptance date | Status at October 23 |
|---|---|---|---|
| Concept approved | October 2, 2026 | October 2, 2026 | Accepted on time |
| Design released | October 9, 2026 | October 12, 2026 | Accepted 3 days late |
| Validation accepted | October 16, 2026 | October 16, 2026 | Accepted on time |
| Packaging approved | October 20, 2026 | — | Unaccepted; 3 days overdue |
| Pilot accepted | October 30, 2026 | — | Not yet due |
There are four milestones due and three accepted by the review date, so due-milestone completion is 3 / 4 = 75%. These formulas calculate that share and the overdue count:
=IFERROR(COUNTIFS(B2:B6,"<="&Control!B1,C2:C6,"<>",C2:C6,"<="&Control!B1)/COUNTIF(B2:B6,"<="&Control!B1),"")
=COUNTIFS(B2:B6,"<"&Control!B1,C2:C6,"")+COUNTIFS(B2:B6,"<"&Control!B1,C2:C6,">"&Control!B1)
The overdue count is one. The formula includes milestones still blank and milestones accepted after the selected review date, so a historical review preserves the backlog that existed then. Retain the late acceptance date for design: a completed milestone should not erase evidence of a missed baseline date.
Show the cost table beside the milestone table. The headline is a forecast overrun and an unaccepted packaging milestone, even though current spending is below plan. If the baseline launch is November 6, 2026, and the current forecast is November 13, the launch slip is seven calendar days. Record the dependency supporting that forecast rather than inferring delay from the spending gap.
The cost check is $490,000 actual plus $380,000 remaining equals $870,000 forecast. The workstream overruns must total $70,000, equal to forecast less approved budget. Use the same sign convention as your variance analysis: here a positive cost variance means an overrun.
Reconcile each milestone count to named rows. The dashboard should expose a specific funding or acceptance decision, with the supporting documents available in the team's existing review process. Project cost management covers the wider budget-control process.
Bring your project cost export, remaining estimates, and milestone register to Covirage; its tools compute and check the comparisons after mapping the uploaded columns. The external AI model explains the result with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.
See Covirage for industrial manufacturers for the manufacturing context.
NPD means new product development. The dashboard follows a specific product from approved development work toward launch, showing its cost position and readiness evidence. A broader innovation portfolio report compares investment choices across products; this dashboard supports the next decision on one product.
Spending below budget can reflect work that has been delayed. Compare actual spending with the spending scheduled by the review date, then examine remaining costs and accepted milestones. A project can be under its spending plan today while forecasting a final overrun and a later launch.
Divide milestones due by the review date that were accepted by that date by all milestones due by that date. State the acceptance criteria and the owner. A milestone count describes scheduled deliverables; it is not a measurement of the percentage of engineering work completed.
The product or program manager owns the combined review. Finance confirms actual spending and budget versions, workstream leads update remaining cost estimates, and named approvers accept milestones. The launch owner explains dependencies behind the current launch date and records the next decision.