Technology and AI

How to build construction dashboards owners actually use

A construction dashboard gets used when it answers the owner's three or four standing questions (Do we have cash? Are jobs making money? Is enough work coming?) on one screen, with numbers the owner trusts, clear thresholds, and a weekly meeting where it is the first thing opened.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

Owners use a construction dashboard when it answers their real questions on one screen, the numbers match what the bookkeeper and PMs say, and it is the first thing opened in a regular meeting. Most dashboards fail because they start from the data the software happens to have instead of the decisions the owner has to make. You end up with 30 charts, two of which matter, and an owner who goes back to asking the controller for "the real numbers."

Start with the owner's questions, not the charts

Sit down with the owner and write down the questions they ask every week. In most companies doing $3 million to $30 million, the list looks like this:

  • Do we have enough cash for the next six weeks of payroll and supplier payments?
  • Which jobs are making money and which are fading?
  • Are we billing what we have earned, or carrying work we have not billed?
  • Who owes us money, and how late is it?
  • Is enough work coming in to keep crews busy next quarter?

Every chart on the dashboard should answer one of those questions. If a chart does not, it goes on a secondary page or gets deleted.

How to build the dashboard in 6 steps

  1. Pick 6 to 8 numbers. Fewer is better. See the table below for a typical set. More ideas are in construction KPIs every owner should track.
  2. Define each number in writing. "Gross margin" means projected gross margin at completion from the latest cost-to-complete update, not margin to date. Write the definition next to the chart so nobody argues about it later.
  3. Name the source and the owner of each number. Cash comes from the bank feed, AR aging from accounting, job margin from the PMs' monthly projections. Each number has a person responsible for keeping it current.
  4. Set thresholds. Green, yellow, red only works if the lines are set ahead of time. For example: any job whose projected margin drops more than 3 points from bid turns red.
  5. Show trend, not just today. A single number tells the owner where things are. A 13-week line shows which direction they are going.
  6. Tie it to a meeting. The dashboard is opened first in the weekly owner review. If the dashboard is not in a meeting, it will not be looked at. How construction owners should review the numbers each week lays out an agenda.
A typical owner dashboard
QuestionMetricTypical sourceUpdate
CashCash on hand and 6-week projected low pointBank feed and cash flow forecastWeekly
CollectionsAR over 30, 60, and 90 daysAccounting systemWeekly
BillingNet over or under billing by jobWIP reportMonthly
Job healthProjected margin at completion vs bid, by jobPM cost-to-completeMonthly, big jobs weekly
LaborHours used vs budget on active jobsTimesheets by cost codeWeekly
PipelineBacklog in dollars and months of workSigned contracts minus billedMonthly
SalesBids out and hit ratioEstimating logMonthly

Worked example: a $9 million GC's one-page dashboard

Say a general contractor running 11 active jobs builds a dashboard with the seven rows above. In the first week it shows cash at $610,000 with a projected low of $240,000 in week five because two owner payments are expected late. AR over 60 days is $380,000, most of it one retainage balance. Net underbilling across jobs is $145,000, and one $1.4 million medical office job shows projected margin at 8.5 percent against a 13 percent bid.

That one screen gives the owner three actions for the week: call the owner on the retainage balance, ask the PMs why $145,000 of earned work has not been billed, and schedule a cost review on the medical office job. None of it required a chart with 40 lines. The underbilling flag, in particular, is the kind of thing that sits unseen in a spreadsheet; overbilling and underbilling explained with examples covers why it matters.

Get the data right before you design anything

A dashboard is only as good as the data under it. Before building charts, check three things.

  • Cost codes are consistent across jobs. If one PM codes drywall to 09-200 and another to 09-250, labor and margin comparisons are noise. See how to build a construction cost code structure.
  • Committed costs are captured. Margin projections that ignore signed subcontracts and open POs look great until the invoices arrive.
  • PM projections happen on a schedule. If cost-to-complete is updated whenever someone remembers, the job health row is fiction.

Owner, PM, and superintendent views are different

One dashboard for everyone ends up serving no one. The owner needs the company picture and the few jobs that need attention. A project manager needs every line of their own jobs: budget, committed, cost to date, projected cost, open change orders, and what is billed against the schedule of values. A superintendent needs the next three weeks, labor hours against budget for the crews on site, and open RFIs and deliveries. Build the owner's page first, since it is the one that forces the data cleanup, then give each role a filtered view of the same data rather than a separate spreadsheet.

The rule that keeps all three honest is simple: every number on the owner's page must be traceable, in one or two clicks, to the PM's job page and then to the transactions under it. If the owner sees red on a job and the PM's page shows green, fix the definition before adding anything new.

Mistakes to avoid

  • Too many charts. If the owner has to scroll, the bottom half is never seen.
  • Vanity metrics. Total revenue year to date is nice to know but rarely changes a decision this week.
  • No drill-down. When a job turns red, the owner should be one click from the job cost report behind it.
  • Manual rebuilds. If someone spends Monday morning pasting exports into a spreadsheet, the dashboard dies the first busy week. Automate the feeds or keep the dashboard small enough to update in 15 minutes.
  • Numbers the PMs do not recognize. Walk each PM through their jobs' numbers before the owner sees them. Surprise data starts arguments, not decisions.

Tools and templates

You can start with a spreadsheet built from the WIP report template and the construction cash flow template, and move to software once the definitions are settled. Read how to read a construction WIP report if billing position is new to the team.

Smart Business Automator provides job costing and WIP views fed from the same project, invoicing, and change order data the team enters every day, so the owner's numbers come from the work itself. See job costing and WIP automation.

Frequently asked questions

What should be on a construction owner's dashboard?

Usually cash and projected cash, AR aging, over and under billing, projected margin by job, labor hours against budget, backlog, and bid activity. Keep it to the 6 to 8 numbers that drive weekly decisions.

How often should a construction dashboard update?

Cash, AR, and labor hours weekly. Job margin and WIP usually monthly, with weekly updates on the largest or riskiest jobs.

Can I build a construction dashboard in Excel?

Yes. Many owners start in a spreadsheet. The risk is the manual work of updating it, so keep it small and automate data feeds when you can.

Why don't owners use the dashboards their software provides?

Default dashboards show what the software tracks, not what the owner asks. They also often rely on data the team does not keep current, which destroys trust.

Who should own the dashboard?

One person, usually the controller or office manager, keeps it running. Each number has a named source owner, such as the PM for job projections.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment