Ask any superintendent who has run a job through a rough winter and they'll tell you the same thing: the schedule you carry in your head is always rosier than the one the numbers show. That gap — between what you feel is happening and what actually is — is exactly what reporting is supposed to close. A good report doesn't just record what happened. It tells you the truth before the owner, the lender, or the closeout does it for you.
The problem is that most scheduling tools bury that truth under a pile of charts nobody reads. So let's be honest about which reports earn their keep on a working jobsite, what each one is really telling you, and how to read them without fooling yourself.
Start With the One Number That Predicts the Job: PPC
If you only track one metric off your weekly work plans, make it Percent Plan Complete — the share of the tasks you committed to this week that actually finished this week. Not "mostly done." Done. It comes straight out of the Last Planner discipline, and it is the single most honest signal you have.
Here's the part people miss. PPC isn't a productivity number, it's a reliability number. A crew can be busting tail and still blow a 40% PPC because the work they committed to was never really ready. When you run at 50%, you're missing half your promises — and every downstream trade is planning around commitments that don't land. Reliable jobs live in the 75–85% range. Anybody quoting you 100% for weeks running is either sandbagging their commitments or not writing them down honestly.
The number itself matters less than the second column: reasons for variance. Every missed commitment gets a cause code — prerequisite work not complete, material not on site, RFI open, manpower short, weather, changed conditions. Log those every week and within a month you'll see the pattern. If 60% of your misses trace back to "prereq not complete," your problem isn't the crews, it's your make-ready. That's the report that changes how you run the job.
The Constraint Log Is Your Real Look-Ahead
People treat the three- or six-week look-ahead as a picture of future work. It isn't, not really. It's a list of promises you can only keep if the constraints on that work get knocked down in time. So the constraint log — not the bar chart — is the report that actually protects the schedule.
A useful constraint report shows three things at once: what's blocking each upcoming activity, who owns clearing it, and how old the constraint is. That last one, aging, is where jobs quietly die. A constraint that's been open eleven days on work scheduled to start in seven is a fire, and it should be red on the report whether or not anybody's shouting about it yet.
The discipline that keeps this honest is simple: no activity enters the weekly work plan until its constraints are cleared. Track your constraint-ready percentage against your total planned work, and you'll know weeks ahead whether next month is real or wishful. When a look-ahead tool like LookAheadWall ties each activity to its blockers and flags the ones aging past their start date, you stop discovering constraints in the Monday morning huddle and start clearing them the week before they bite.
Variance Reports: Compare Plan to Actual, Then Ask Why
A variance report lines up planned dates against actual dates and shows you the slip. Useful. But the slip is the easy half — the value is in the why, and that's where most teams stop short.
Break your variance down by cause the same way you code PPC misses. Weather, material delays, predecessor slip, labor, design changes, inspection failures. Do it consistently for a few months and the data starts arguing with your gut. You'll swear the drywall trade is your problem, then the report shows their starts slip because framing hands off late three times out of four. The bottleneck was upstream the whole time.
Watch for one specific trap: distinguishing an estimating problem from an execution problem. If an activity slips every single time you run it, the crew isn't slow — your duration was wrong. That's a planning fix, not a manpower fix, and no amount of leaning on the foreman will close it. Chasing execution when the number was bad from the start is how supers burn out good crews and never fix the schedule.
Progress Dashboards: Glance, Don't Live There
The color-coded dashboard — percent complete, activities behind, next milestones, the green-yellow-red lights — is genuinely useful for a thirty-second read before a walk or an owner call. Use it for exactly that.
Just know what percent complete hides. Overall percent complete is a weighted average, and weighted averages lie about sequence. You can be 70% complete on square footage and dead in the water because the 30% left is all on the critical path and all stacked behind one late long-lead item. The dashboard shows a comfortable green while the finish date quietly walks to the right. Always read percent complete next to your critical path and your milestone dates, never alone. A dashboard is a starting point for questions, not an answer.
Milestone Reports Are What the Owner Actually Reads
Your owner does not care that you poured column line 4 on Tuesday. They care about dry-in, permanent power, TCO, and turnover — the dates that move their money and their tenants. Milestone reporting rolls the thousand activities nobody upstairs wants to see up into the handful of dates they do.
Two rules keep milestone reports credible. First, show the projected milestone date, not just the contract date — the gap between them is the entire point, and hiding it only means a worse conversation later. Second, give milestones enough runway that the report is actionable. A slipping milestone spotted six weeks out can still be recovered with a resequence or a second crew. Spotted at two weeks, all you can report is that you missed it. The longer look-ahead exists precisely so milestone trouble surfaces while you can still do something about it.
Trend Reports Beat Snapshots Every Time
A single week's numbers are noise. Any crew can have a bad week — a knuckle-dragger of a rain event, a delivery that goes sideways. The signal lives in the trend.
Plot PPC week over week and the story writes itself. A line climbing from 55% toward 80% means your make-ready is working and you can start trusting the plan further out. A line sliding the other way is an early warning that fires weeks before it shows up in the milestone dates — which is exactly when you want it, while it's still cheap to fix. Trend reporting is the difference between managing the job and just documenting how it got away from you.
Subcontractor Scorecards: Data Beats Memory
Everybody "knows" which sub is the problem. The scorecard is what turns that hallway opinion into something you can actually act on. Track on-time starts, on-time completions, and PPC by trade over the life of the job, and you replace a grudge with a record.
That record cuts both ways, and that's the point. In the coordination meeting it lets you show a trade their own numbers instead of accusing them — "your last four starts slipped, here's the pattern" lands very differently than "you guys are always late." It also protects the honest sub. When a trade's dates slip because you kept handing off the deck late, the cause codes show it, and you don't scapegoat a good partner. And when you're leveling bids on the next job, a two-year completion history is worth more than the low number on the page.
Resource and Labor Reports — Handle With Care
Resource utilization reports — planned versus actual crew deployment, hours by activity, the labor curve across the job — are worth running, mainly to catch the staffing cliffs before you hit them. A labor histogram that spikes ugly in month five is telling you to smooth the plan now, while there's still time to pull work forward or push it back.
The caution: these reports are only as good as the field data feeding them, and field-entered hours are the messiest data on the job. A "productivity" number built on hours somebody guessed at the tailgate on Friday afternoon is worse than no number, because people believe it. If you're going to report on labor, invest in getting the inputs clean first. Otherwise you're making decisions on fiction with a decimal point.
Get Reports to the People Who Act on Them
The best report nobody sees is worthless. The wins here are unglamorous and real:
- Mobile access. A super lives on their feet. Pulling the day's plan and the open constraints on a phone in the field — where a crew-leader companion app matters most — beats walking back to the trailer every time. Field-entered progress also means the reports reflect this morning, not last Thursday.
- Automated distribution. Weekly work plans out to every trade after Monday's session. The owner milestone summary on the schedule your contract requires. Crew-specific plans to the right foreman and nobody else. Set it once so it happens whether or not you remembered.
- Role-specific views. The foreman needs this week's tasks and their blockers. The PM needs variance and cost-loading. The owner needs four milestone dates. Same data, three cuts — and burying each reader in the other two's report is the fastest way to get all three to stop reading.
The Reports That Actually Matter
Strip away the dashboard theater and it comes down to a short list. Track PPC and its variance reasons to know if your plan is real. Work the constraint log and its aging to protect the weeks ahead. Read variance by cause to fix the right problem. Watch trends, not snapshots, so trouble surfaces while it's cheap. Keep an honest sub scorecard so coordination runs on record instead of memory. Everything else is supporting cast.
Good look-ahead software — LookAheadWall included — earns its place when it captures this straight from the field and rolls it up without a night of spreadsheet surgery. But the tool only reports what you feed it. Commit honestly, code your misses, clear your constraints, and the numbers will start telling you the truth about your job — which, on a hard schedule, is the most valuable thing a report can do.