A dashboard is the first thing you look at with a cup of coffee in your hand at 6:15, before the gate opens and the day gets away from you. If it does its job, you spend ninety seconds on it and walk out to the trailer already knowing where today's fight is. If it doesn't, you scroll past a dozen gauges that all say "green" while the plumber who was supposed to be topping out today is nowhere on the plan, and you find that out at 9:30 when it's already a problem.
Most field management dashboards are built by people who have never had to stand in front of a subcontractor and explain a slip. They pack the screen with everything the database can produce and call it "visibility." Real visibility is the opposite of that. It's a small number of things that will hurt you if you ignore them, shown clearly enough that you can't. Here's what actually belongs on a superintendent's dashboard and why, drawn from having stared at both good ones and useless ones.
Start With What's Blocked, Not What's Green
The single most valuable thing a dashboard can tell you in the morning is which planned activities can't start. Not the schedule health index, not a percent-complete donut chart — the specific list of work you were counting on this week that is missing a prerequisite. In the Last Planner world these are called constraints, and a look-ahead is only as good as its constraint log.
A good dashboard surfaces constraints by category so you can act on them: waiting on material delivery, waiting on inspection sign-off, waiting on a prior trade to clear the area, waiting on an RFI answer, waiting on submittal approval. When you build weekly work plans in look-ahead software like LookAheadWall, those constraints ride along with each activity, and the dashboard rolls them up into one honest list of everything standing between you and the plan. That list is where your morning phone calls come from.
Rule of thumb: if your board shows a task as "ready" the day it's supposed to start, you found out too late. You want constraints flagged one to two weeks out — enough runway to chase a delivery or expedite an inspection before it becomes a slipped start.
Percent Plan Complete — The Number That Doesn't Lie
If you track one productivity metric, track PPC: of the tasks you committed to this week, what percentage actually finished. It's brutally simple and that's the point. Not "how much work got done somewhere on the job" — did the specific commitments you made last Friday come true.
A healthy crew running reliable weekly work plans lands somewhere around 70–85% PPC. Below 50% and your plan is fiction; people have stopped believing the schedule and are freelancing. Ninety-five percent every week isn't the win it looks like either — it usually means you're sandbagging, committing only to work you already know is safe, and leaving production on the table.
The number itself matters less than the trend and the reasons. A dashboard that shows PPC without capturing why tasks failed is half a tool. The gold is in the variance reasons — prerequisite work not finished, changed priorities, missing materials, weather, undermanned. Tally those over a month and the pattern tells you what's really broken. If "prerequisite work not complete" shows up in a third of your misses, you don't have a manpower problem, you have a sequencing and trade-flow problem, and no amount of pushing the crew fixes it.
The Three-Week Window, Not the Gantt
Your dashboard's schedule view should default to the near term — this week and the next two or three. The master CPM schedule has its place in the office, but on a working dashboard a thousand-line Gantt is noise. What you need to see is the short-interval window: what's in progress, what's on deck, and where the hand-offs between trades happen.
The value of a rolling look-ahead is that it forces the coordination conversation for the exact window where it matters. Show the trade-flow sequence in that window and you can spot the collisions before they happen — the drywallers scheduled into a room the electrician hasn't trimmed out, the two crews both planning to occupy the same corridor on Tuesday. Color-coding by trade or by status helps, but the layout matters more than the color. Location-based views, where you see the work by area rather than by an abstract activity list, are how superintendents actually think, and a dashboard that mirrors that is one you'll actually use.
Inspections and Sign-Offs, Because They Gate Everything
Nothing wrecks a week quietly like a missed inspection. You can have material, manpower, and a clean work area, and still be dead in the water because the framing inspection didn't get called and now you can't insulate, which means you can't close the wall, which means the whole stack of trades behind you idles.
A dashboard earns its keep here by showing upcoming required inspections and their status against the work that depends on them. Give me a view that says "rough-in inspection due Thursday, three activities blocked behind it" and I'll make sure it's scheduled. Tie that to the practical field discipline — megger the runs and pressure-test before you ever call the inspector, because a failed inspection isn't just a redo, it's a two-day hole while you wait to get back on the schedule. Build a one-to-two day buffer between "trade finishes" and "next trade starts" specifically so an inspection and a cleanup pass can happen without cascading a slip down the line.
Submittals and Long-Lead Items
Field crews don't lose jobs on the tools; they lose them waiting on things that should have been ordered months ago. A dashboard that connects submittal and procurement status to the near-term schedule is doing preventive work. What you want to see is not a list of all open submittals — that's a coordinator's screen — but the ones that gate work coming up in your window.
If the switchgear submittal is still in review and the electrical room activity is three weeks out, that's a flashing light, not a footnote. The most useful version of this ties the pending item directly to the affected activity, so the delay shows up as schedule risk in plain language rather than as a status buried in a document log. Long-lead items — gear, elevators, custom glazing, anything with a lead time measured in weeks — deserve their own persistent watch on the board until they're on site and checked.
Manpower: Planned Versus Actual, By Trade
Head counts on a dashboard should answer one question: did the crews that were supposed to show up show up, and at strength. A subcontractor who commits twelve men and sends six is telling you something about your schedule two weeks from now, and you want that signal early, not in the recovery meeting.
Track planned versus actual manpower by trade and let the gaps accumulate visibly. A drywall crew running consistently under its committed count is a slip that hasn't happened yet. This is also where you catch the opposite failure — trades stacking into the same area because the sequence wasn't respected, four crews fighting over one corridor while three other areas sit empty. Good look-ahead planning spreads the work across locations so nobody's tripping over anybody, and the dashboard should make an area that's overloaded or starved obvious at a glance.
Safety and Quality — Leading Indicators, Not Just the Scoreboard
Every dashboard shows the incident count. That's a lagging indicator — by the time it moves, someone's already hurt. The metrics worth watching are the leading ones: safety observations logged, near-misses reported, pre-task plans completed, corrections closed out. A jobsite where near-miss reporting suddenly drops to zero isn't safer; it usually means people stopped reporting, and that's the last thing you see before something serious.
Same logic on quality. Punch-list count at the end is a lagging number. First-time inspection pass rate and rework by trade are leading ones — they tell you where quality is slipping while there's still time to have the conversation. If one trade's rework rate is climbing, you address it now, not in a punch walk three months from now when it's ten times the cost to fix.
Weather, Because You Plan Around It or It Plans You
A dashboard that puts the forecast next to the weather-sensitive work in your window saves real days. Concrete pours, roofing, exterior painting, anything that can't take rain or a hard freeze — you want the forecast and the planned activity on the same screen so you can pull work forward into a good window or push it before you've got a crew standing in the mud. This isn't fancy; it's just having the two pieces of information in the same place at the same time, which is more than most tools manage.
What to Leave Off
Restraint is a feature. Cost and earned-value metrics belong on the PM's and executive's dashboards, not cluttering the superintendent's morning view — different role, different screen. Communication-volume charts and "message response time" gauges are vanity metrics; nobody ever prevented a slip by admiring their notification-delivery rate. If a tile doesn't change a decision you'd make that day, it's decoration, and decoration is what turns a dashboard into wallpaper you stop reading.
The best field dashboards I've used share one trait: they're built around the questions a superintendent actually asks at 6 a.m. — what can't start, what's behind, what's about to bite me — and they answer those questions before I've finished my coffee. Everything else is a report I can pull when I need it. Role-based views matter here; the foreman, the super, and the PM each need a different default, and a tool that lets each person see the slice relevant to their job is far more useful than one screen that tries to serve everybody and serves no one. Get that right, and the dashboard stops being something you check and starts being the thing that runs your morning.