We spent about three months talking to project managers at commercial GCs about what they actually look at in the morning before they go to site. Not what they thought we wanted to hear about dashboards and data platforms. What they genuinely reach for when they arrive at the office at 6:30 and have 20 minutes before the first call.

We talked to 12 PMs — mostly commercial office, mixed-use, and mid-rise residential GCs in Texas, Colorado, and the Southeast. Projects ranged from $15 million to $120 million. Some were running two projects simultaneously. Some had been using construction management software for years, some were still managing primarily from Excel and email. The answers about what information they needed had a lot more in common than we expected, and a lot less overlap with what most dashboard products actually serve up as the default view.

What They Actually Look At First

The most consistent answer across all 12 PMs: they look at what's supposed to happen today and whether the preconditions for it are in place. Not the overall project health score. Not the RFI log count. Not the weather forecast (though several check that on their phone before the office computer is even open). The specific question is: what's scheduled for today, and does the field have what it needs to execute?

The precondition check involves four things:

  • Is the material for today's work on site, confirmed, or at risk?
  • Are the crews for today's activities confirmed mobilized or imminent?
  • Are there any open RFIs or unresolved questions that affect today's work specifically?
  • Are any predecessor activities from yesterday still incomplete that block today's start?

Only one of those four is typically surfaced in a standard construction software dashboard. Most platforms lead with project percentage complete, cost-to-date versus budget, and submittal or RFI counts. Those are useful numbers but they answer a different question than "can my crew start work this morning."

The 3-Week Look-Ahead Is the Real Operating Document

Seven of the 12 PMs we talked to described the 3-week look-ahead as their primary operational document — more used, more current, and more decision-relevant than the CPM master schedule. This surprised us initially. CPM schedules represent months of scheduling work and contain all the logic relationships. But they're updated weekly at best, are often managed by a scheduler who isn't the PM, and aren't organized around daily crew-level decisions.

The 3-week look-ahead is owned by the PM and updated based on what they know is happening in the field. It shows activities at the 2-4 day level of detail, organized by trade and location, and it's the document that gets revised when a pour gets pushed or a sub calls in short-staffed. It's also the document that the PM is personally accountable for — if the look-ahead shows Floor 12 MEP complete by Thursday and it isn't, that's the PM's failure, not the scheduler's.

What this means for a dashboard: the useful information view isn't the high-level project summary, it's a view that maps to the look-ahead horizon. Which activities are due to start or complete in the next 3-5 days? Which ones are at risk based on current productivity rates? Which predecessor activities are incomplete and creating drag on upcoming starts? The master schedule sits behind that as reference, but the daily operating view should be the look-ahead horizon, not the project timeline.

What They Don't Want (And Why)

The critique of most dashboard products from the PMs we talked to was consistent: too much information they can't act on, not enough information they need to act on.

Specific examples of dashboard content that PMs described as "looks useful but isn't":

  • Aggregate project completion percentage: "I know what percent complete it is. I was there yesterday. The number doesn't help me figure out what to do today."
  • Total open RFI count: "The number by itself is useless. I need to know which RFIs are blocking work this week, not the total count."
  • Weather forecast beyond 48 hours: "Anything past two days I can't plan around anyway. Weather forecasts at that range aren't reliable enough to make schedule decisions."
  • Cost trending charts: "I look at cost once a week in the job cost report. Having it on the dashboard doesn't change when I need to make a cost decision."
  • Subcontractor contact directories: "I know who my subs are. I have their numbers in my phone. I've been working with them for eight months."

The common thread is that these information items are reference data, not action-triggering data. A PM looking at a dashboard at 6:30 AM before site walk doesn't need reference data — they need to know what's different from yesterday and what specifically needs attention today.

The Information They Said They Wish They Had

This was the most useful part of the conversations. When we asked what information they were missing — what they had to go find manually that they wished was served up automatically — four categories came up repeatedly:

1. Predecessor Activity Status Relative to Planned Successor Starts

PMs consistently described needing to manually check whether predecessor activities were complete before downstream work was about to start. "I have to call my super on Floor 8 every morning during MEP rough-in to find out if the deck penetrations are done before the mechanical sub is supposed to mobilize." This is a condition check that should be automatable: if Activity B is scheduled to start Monday and Activity A (its predecessor) is flagged as incomplete in the field log as of Friday, the PM should see that flag over the weekend, not discover it Monday morning when the sub shows up.

2. Productivity Rate Versus Plan for Active Activities

Not "is Activity X complete" but "at current productivity, when will Activity X complete?" PMs on repetitive activities — floor-by-floor concrete work, MEP rough-in across multiple floors, drywall — track productivity rates mentally and project forward. "I know my drywall sub is hanging 4,000 square feet a day and they need to hang 24,000 on this floor before the painting crew mobilizes. That means they have six days of work remaining." They're doing that math themselves. A dashboard that showed the productivity rate and projected completion for active activities based on that rate would replace a calculation the PM currently does in their head.

3. Which Open Issues Are on the Critical Path

Every project has 20-40 open RFIs, 10-15 pending submittals, and 5-10 pending change orders at any given time in active construction. Maybe three of those are actually on the critical path and affect upcoming work. The other 35 will get resolved eventually and don't require this week's attention. PMs described spending significant time triaging the issue log to identify which items needed urgent resolution versus which could wait. A view that filtered the issue log by schedule impact — specifically, which open items are associated with CPM activities due to start in the next 14 days — would reduce that triage time substantially.

4. As-Built Versus Planned Field Status at the Floor Level

Every PM we talked to described some version of "I need to know what's actually done versus what people say is done." This is the observation that drove our own product development work. The gap between self-reported completion percentages and field-verified completion is real and persistent on commercial construction projects. The PMs who had experienced projects where that gap created problems — a sub reporting 80% on a pay application that was actually 55% in the field — were the most interested in systematic visual verification. Not because they didn't trust their subs, but because they wanted a documented cross-reference that wasn't dependent on a field walk they hadn't had time to do.

What a Useful Dashboard Actually Looks Like

Based on these conversations, the dashboard structure that GC PMs described as genuinely useful has three zones, not one unified view:

Zone 1 — Today's action list (occupies 60% of screen): Activities due to start or complete today, organized by trade and floor. Predecessor status flags for activities starting today or tomorrow. Open issues blocking this week's activities. Crew confirmations for today's critical activities.

Zone 2 — 3-week look-ahead summary (20% of screen): Activities by trade with projected completion versus plan, organized by floor. Flags for any activity where projected completion is behind planned completion by more than 2 days. No more detail than the 3-week horizon — master schedule is a click away, not a default view.

Zone 3 — Status updates requiring attention (20% of screen): Submittals or RFIs whose response deadlines fall within the next 7 days. Pay applications approaching submission date. Quality observations flagged as unresolved. Nothing that doesn't require action in the current week.

What's not on this dashboard: project health score, aggregate completion percentage, cost curves, weather beyond 48 hours, contact directories, anything that requires action in more than 14 days. Those live in the software's other views and the PM accesses them when they need them, not as the default morning view.

The underlying principle that came through clearly in every conversation: a useful PM dashboard is an action trigger, not a status report. A status report is what you build for the OAC meeting or the monthly owner's review. The morning dashboard tells you what you need to do in the next four hours and what might go wrong by the end of the week. Those are different documents serving different functions, and most dashboard products confuse them.