You've probably heard some variant of the saying "what gets measured, get's managed"
I don't think that's completely right.
It should be, "what get's measured and communicated, get's managed"
A construction dashboard should help someone make a decision.
My recommendation is to start with who will use it and what they need to know. A project team needs upcoming milestones, cost overruns and risks requiring action. A client overseeing several projects may also need a simple scope summary.
I would build it around three areas:
Cost: Are we forecast to finish within budget? Where are variations accumulating, and when are payments due?
Risk: Which risks need attention? How much will our planned treatments reduce their likelihood or impact?
Programme: Which milestones are approaching, and where have dates slipped against the original plan?
The information behind it needs to be structured and maintained. Build updates into your existing forecasting, payment and reporting processes so the dashboard stays current without duplicating administration.
Then use it in your project reviews. If the same question keeps sending you back into a spreadsheet, that information probably belongs on the dashboard.