Per-Project Dashboards for Construction Subcontractors

A per-project dashboard puts one job’s labor hours, budget, change orders and margin on a single screen, so you can tell in seconds whether that job is making or losing money. For a commercial subcontractor, the dashboard that works is the one fed by your field time and change order records. A general contractor’s schedule view, or a spreadsheet someone updates on Fridays, won’t do the same job.

This guide covers what to put on a per-project dashboard, which numbers to skip, how to keep the data clean, and where Excel and BI tools stop being enough.

TL;DR

• Track 5 to 7 KPIs per project. If the status isn’t clear within five seconds, the dashboard is too busy.
• For subs, the numbers that matter most are labor hours against budget, change order status and value, and margin by job.
• Dashboards are only as good as the data behind them. Field entries that arrive late or by hand make the charts wrong faster.
• Timing matters: changes late in a job hurt far more than early ones, so alerts beat monthly reports.
• Tools that share one login and one data set across time, change orders, bids and takeoff remove most of the double entry.

Table of Contents

• What a per-project dashboard is for a subcontractor
• The KPIs worth putting on the page
• Layout: the five-second test
• Per-project vs. portfolio view
• Where the data comes from, and why that is the real work
• Excel, Power BI or a purpose-built suite
• Our perspective: the dashboard starts in the field
• How Won2Build fits
• A simple rollout plan
• Mistakes that make dashboards useless
• FAQ
• Sources

What a per-project dashboard is for a subcontractor

Most dashboard guides are written for owners or general contractors. They track overall health, schedule, cost, scope, risks, issues, resources and milestones across a whole building. A subcontractor has a narrower and sharper question: is my scope on this job making the margin I bid?

That changes what you display. You rarely control the master schedule, and you don’t carry the full project budget. You control your crew’s hours, your material purchases, the changes you price and the paperwork that gets those changes approved. A per-project view built around those four things gets read. One built around everything gets ignored.

The Construction Management Association of America describes the useful kind as a decision dashboard. It pulls from workflows you already run, such as time tracking, scheduling and inventory, instead of asking people to enter data twice. The same paper reports that these tools can cut problem identification time by 60 to 80 percent and solution development time by 40 to 60 percent. Treat those as the publisher’s figures, not a promise for your shop.

The KPIs worth putting on the page

One Power BI design guide recommends 5 to 7 core KPIs aligned to project risk. Its list includes schedule variance, cost variance, earned value, safety incident rate, change order volume, RFI and submittal cycle time, and punch list items. It also recommends charting budgeted against actual cost to catch overspending early.

That list is built for a whole-project view. Here is how we would adapt it for a commercial sub.

Seven rows is the ceiling. If you have to add one, remove one.

Why labor and change orders lead the list

Two findings explain the ordering. The Construction Industry Institute reports that performing work on changes costs about 30 percent in labor efficiency, and that field disruptions such as missing materials or out-of-sequence work can cut daily efficiency by 26 to 47 percent. That research dates from 1994, so use it for direction, not for exact forecasting. It does show why hours and changes belong side by side on one screen.

Second, timing. A study of change orders at five U.S. Army Corps of Engineers districts found that changes in the final 20 percent of a project timeline have about six times the impact on budget and schedule as those in the first 20 percent. The data comes from federal mechanical and plumbing work, so it won’t match every private job. Still, the lesson holds for dashboard design: a late change should trigger an alert, not wait for a month-end summary.

Layout: the five-second test

A good dashboard passes what practitioners call the five-second rule. Someone opens it and knows whether the job is healthy before they’ve finished a sip of coffee. If they have to dig to interpret a chart, it is over-built.

A layout that works for one project:

1. Top row, three or four tiles. Margin to date, labor hours used vs. budget, pending change order value, and the oldest unapproved change in days. Use plain red, yellow and green against thresholds you set.
2. Middle, one trend chart. Budgeted vs. actual labor cost over time. Overspending shows up as a gap opening between two lines.
3. Bottom, one list. Open change orders and T&M tickets sorted by age, with the amount and who needs to sign.

That’s it. Everything else lives one click deeper, in reports you open when a tile turns red.

Thresholds beat raw numbers

A tile that says 412 hours means little. A tile that says 412 of 500 budgeted hours used with the job 70 percent complete means a great deal. Set a yellow and red line for each KPI when you set up the job, based on the estimate, and let the dashboard do the comparing.

Per-project vs. portfolio view

You need both, in a particular order. Start with one project’s view because that is where decisions get made: add a second crew, send a change order, push back on out-of-sequence work. The portfolio view is the same tiles rolled up so you can see which jobs need attention first.

The FMI quarterly on data analytics points to a more advanced use: margin gain and fade analysis. Once you have several finished jobs in the system, you can look for patterns by geography, design team or client. The same FMI piece, together with a study in the Journal of Construction Engineering and Management, notes there is no standardized, universal set of project control metrics. Pick yours for your trade and typical job size, and keep them consistent so jobs can be compared.

Where the data comes from, and why that is the real work

The chart is the easy part. A dashboard built on bad inputs just shows you wrong numbers faster.

One Power BI reporting case study describes a general contractor’s reports being computed nightly from project management and accounting systems and published only after a few hundred automated data-quality checks. The point applies to any size of company: the goal is removing manual entry, and a report should not go out until key fields are validated.

For a subcontractor, the equivalent rules are small and practical:

• Every time entry has a project and a cost code before it is accepted.
• Every T&M ticket has a description, quantity and a signature or approval status.
• Every change order has a date it was first communicated to the GC.
• Estimated hours from the bid are loaded into the project at kickoff, not reconstructed later.

Handwritten daily logs typed in on Friday fail every one of those rules. Entries made in the field on a phone, the same day, pass them. That is the argument for capturing time and change events at the source. Our guide to same-day change order documentation lays out the field checklist, and same-hour notices explain why speed matters when you want to be paid.

Field layout and measurement data deserve the same discipline. A field guide to construction surveying is a useful reminder that layout and control work depends on consistent, checked measurements, the same principle that keeps a dashboard honest.

Excel, Power BI or a purpose-built suite

There are three realistic paths for a sub.

Excel templates. Free, familiar, fine for one or two small jobs. The problem is manual refresh. Someone has to paste in hours and update change orders, and when that person is busy the dashboard is stale. It also tends to live on one laptop.

BI tools such as Power BI. Powerful when you have someone who can model data and connections to your accounting and field systems. The Power BI guide shows how much design goes into it. For a 10 to 50 person sub without a data analyst, the build and upkeep can outweigh the benefit.

Purpose-built subcontractor software. The dashboard is a by-product of the tools your crews already use, so there’s nothing to rebuild or refresh. The trade-off is that you work within the reports the software offers instead of designing every visual yourself.

Guidance published with the CMAA stresses avoiding siloed data by choosing tools that integrate with the systems you already use. Whatever path you pick, ask the same question: does the number on the screen get there without anyone retyping it?

Our perspective: the dashboard starts in the field

We built Won2Build from the perspective of a working subcontractor, and the pattern we see is consistent: margin is rarely lost in the office. It’s lost on a Tuesday afternoon when a crew does extra work, nobody records it, and the paperwork shows up three weeks later, if at all.

So we don’t think of the dashboard as a separate product. It is what you see when four jobs are already connected: the hours your crew logs, the change orders you submit, the estimate you won, and the quantities you measured from the plans. When those sit behind one login and share data in real time between the field and the office, you stop reconciling and start deciding.

Our advice to any sub starting out is simple. Pick five numbers. Make sure each one is captured in the field the same day. Look at them every Monday for every active job. Add a sixth only after the first five have caught something real.

— Jen Reese

How Won2Build fits

Won2Build Hub brings four apps together under a single sign-on: Time Budge for labor tracking, CO Hub for change orders and T&M tickets, Bid Track for bids and estimates, and Takeoff for digital plan quantities. Data moves between them without double entry, and reporting is organized per project.

Published pricing on our pricing page: Time Budge is $199 per month per company, Bid Track is $199 per month per company, and CO Hub is $59 per month per company. Active field workers add $2 per month each. Takeoff and the Hub itself are listed at $0 per month. Companies can subscribe to individual apps or the full bundle, and there is a free trial before billing begins.

If you want a place to start, look at the suite and see which one app would catch your biggest leak first. For most subs, that is labor or change orders. Our walkthrough on setting up project budget tracking shows how to load a budget so the comparisons mean something.

A simple rollout plan

You don’t need a quarter-long project. Try this over three weeks:

1. Week 1: choose the KPIs. Pick five from the table above. Write down the threshold for yellow and red on each.
2. Week 1: load one active job. Enter the bid hours and budget by cost code. Pick a job that is at least 25 percent from completion so you have time to see it work.
3. Week 2: capture in the field. Have foremen log hours daily and flag any extra work as a potential change the same day.
4. Week 2: review on Monday. Spend 15 minutes looking at the top tiles. Note every surprise.
5. Week 3: tighten. Fix the data gaps the review exposed, such as missing cost codes or unsigned tickets, then roll the setup out to your other jobs.

For more on timelines, our posts on change order turnaround and real-time reporting on commercial projects go deeper, and resource allocation covers what to do when the labor tile turns red.

Mistakes that make dashboards useless

• Tracking everything. More than seven KPIs and nobody can read it.
• Automating bad data. Automating handwritten, late entries amplifies the errors. Fix capture first.
• Equal weighting of changes. A change at 90 percent complete is not the same as one at 10 percent. Alert on late ones.
• No thresholds. Raw numbers without a target invite debate instead of action.
• Keeping it private. Guidance from industry groups favors metrics that are transparent and shared with stakeholders. Share the change order tile with your PM and your GC contact so approvals move.
• Never closing the loop. After each job, compare final margin with the bid. Feed the difference into the next estimate. Our piece on bid win rates shows one way to do it.

FAQ

How many KPIs should a per-project dashboard have?

Five to seven. That range is what one Power BI design guide recommends, and it matches the five-second rule. Start with labor hours, change order value and age, cost variance and margin to date.

What is the best way to show a project’s health at a glance?

Use red, yellow and green tiles against thresholds drawn from your estimate, then one trend line of budgeted against actual cost. Put open change orders in a short list sorted by age. Anything beyond that belongs in a drill-down report.

Can I build a construction dashboard in Excel?

Yes, and it works for a small number of jobs. The weak point is manual updating, so entries go stale and errors creep in. If you manage many active projects or crews, a tool that captures field data directly will save more time than a better template.

Do subcontractors need a different dashboard than general contractors?

Usually yes. A GC tracks the full schedule, RFIs and the whole budget. A sub needs labor against estimate, change orders and margin for its own scope, which is why the view should be built around your field and change data.

Sources

• Actionable Analytics, Construction Management Association of America
• Getting the Right Project Data, Construction Management Association of America
• The Effects of Change on Labor Productivity, Construction Industry Institute
• The Impact of Mechanical & Plumbing Change Orders on USACE Construction Projects
• Designing a Construction Project Management Dashboard in Power BI
• Beyond the Buzz, FMI Quarterly
• Metrics That Matter, Journal of Construction Engineering and Management
• Construction Reporting in Power BI: Procore, Sage, Outbuild

Recommended

• Subcontractor Project Reports: 3 Templates for Same Day Proof
• Why Subcontractors Need Real-Time Data to Win in 2026
• Construction Software Solutions for Subcontractors and PMs