Most of the reports that come out of subcontractor management software are printed, glanced at, and filed. That's the honest truth. A superintendent doesn't need another PDF with a green pie chart telling him the job is "72% on track." He needs to know which three subs are about to blow next week's plan, which insurance cert lapses on the 15th, and whether the drywall crew that's been showing up two men short is going to leave him hanging on the ceiling grid inspection.
Reporting isn't about volume. A system that spits out forty dashboards is worse than one that answers five questions cleanly. Below is how to think about the reports that actually move a job, and how to read them so they change what you do on Monday morning instead of just confirming what you already suspected on Friday.
Start with the question, not the dashboard
Before you look at any report, know what decision it's supposed to inform. If a report doesn't change an action, it's decoration. The useful ones answer a specific field question:
- Who is slipping, and by how much?
- What's expiring — certs, insurance, submittals — before it becomes a stop-work?
- Where is money hung up, and is it my problem or theirs?
- Which trade keeps generating the same rework, and why?
Everything else is context. When you evaluate a reporting feature, don't ask "does it produce this chart" — ask "does this chart let me catch a problem while it's still cheap to fix." A slipped commitment caught on Tuesday costs a phone call. Caught at the Thursday owner meeting, it costs a two-week recovery plan.
Schedule performance: PPC is the number that tells the truth
The single most valuable schedule report on any job is Percent Plan Complete — the ratio of commitments a crew actually finished to the commitments they made for the week. Not percent of the overall project complete. Percent of this week's promises kept.
PPC is honest in a way that a Gantt bar never is. A pull-planned week where the framers committed to eight tasks and finished six lands at 75%. That gap is your early warning. A healthy job trends between 70 and 85%. Consistently above 90% and your crews are sandbagging their commitments — they're promising less than they can do so they always "hit." Below 60% and either the plan is fantasy or something upstream is choking them, and you need to find out which before it compounds.
What makes PPC actionable isn't the number, it's the reasons for variance. Every missed commitment should carry a coded reason: prerequisite work not ready, missing materials, RFI outstanding, weather, manpower short, changed scope. Track those reasons over four to six weeks and the pattern jumps out. If half your misses code back to "prerequisite not ready," your problem isn't the crew that missed — it's the trade ahead of them. That's the whole point of running short-interval scheduling instead of just staring at the master schedule: the weekly work plan surfaces the handoff failures the master schedule hides.
A tool like LookAheadWall earns its keep here because the commitments and the trade-flow sequences live in the same place. When the report shows a slip, you can trace it back through the flow to the constraint that caused it rather than guessing.
Look-ahead status: read it three weeks out, not one
A one-week report tells you what already went wrong. The value is in the two-, three-, and six-week look-ahead — the window where you can still do something about it. When you review the rolling look-ahead, you're hunting for constraints that will land on a crew before the crew arrives:
- Long-lead materials that won't be on site when the sequence calls for them
- Design questions still open on work scheduled inside three weeks
- Inspections stacked on the same day with one inspector to cover them
- Two trades scheduled into the same location in the same window
Rule of thumb: any constraint sitting inside the three-week window that isn't actively being worked is a red flag. Inside two weeks it's an emergency. The report exists to make those constraints visible early enough that clearing them is routine. If your look-ahead only ever shows you next week, it's a rear-view mirror.
Compliance: the reports that keep you out of a shutdown
Compliance reporting is boring right up until it isn't. Then it's a subcontractor whose general liability lapsed three weeks ago, working on your site, and now you've got an exposure your risk manager will not enjoy explaining.
The report you want is not "who is compliant." It's what expires in the next 30 days. Insurance certificates, additional-insured endorsements, safety training cards, licenses, drug testing. Sort by expiration date, ascending, and work the top of the list. A good system flags the item 30 days out, nags at 15, and locks the sub out of new weekly commitments if it hits zero. Manual cert tracking in a spreadsheet is where jobs get burned, because nobody owns the spreadsheet and everybody assumes somebody else is watching it.
One practical note: separate "expired" from "expiring." An expired cert is a stop-the-work conversation today. An expiring cert is a two-line email to the sub's office. Conflating them either cries wolf or misses the real fire.
Payment and change-order reports: follow the money and the arguments
Payment aging reports matter to the field more than superintendents like to admit, because a sub who isn't getting paid on time starts pulling his best men to the job that is paying. When you see a trade's manpower quietly drop, check the payment aging before you write him up. Sometimes the schedule slip is a symptom of an accounting problem two floors up.
Change-order reporting is where you catch the slow bleed. Watch two things: volume trend and aging of unapproved COs. A single trade generating a rising count of change orders usually means the scope was bid loose or the drawings are fighting each other in that area. And a stack of COs sitting unapproved is a stack of work the sub may legitimately stop doing until someone signs. Reports that show CO value against the original subcontract also tell you when a "small" trade has quietly grown into a major cost risk nobody's tracking.
Quality and safety: track the pattern, not the incident
Anybody can log a deficiency. The report that helps you is the one that shows the same deficiency recurring. If the punch list keeps generating the same three callbacks from the same crew — misaligned blocking, missed fire caulk, sloppy penetrations — that's a training or supervision problem on that sub, and the fix is a conversation with their foreman, not another line item.
Watch first-time-pass rates on inspections by trade. A crew that passes rough-in on the first shot 90% of the time and one that passes 60% of the time cost you very different amounts of schedule, even if both eventually pass. The 60% crew is quietly eating your buffer with re-inspections. On safety, the leading indicators — near-miss reports, observation counts, training currency — tell you more about where the next incident is coming from than the recordable rate, which only tells you where the last one already happened.
Communication reports: RFI and submittal aging are constraint reports in disguise
An open RFI on work scheduled inside three weeks isn't a paperwork item — it's a constraint that will stop a crew cold. That's why RFI and submittal aging belong right next to your look-ahead, not buried in a separate document control report. Sort RFIs by age and by the schedule date of the work they affect. The dangerous one isn't the oldest RFI; it's the RFI feeding a task that starts Monday.
Response time is the metric that keeps the design team honest. If the architect's average turnaround is running twelve days and your look-ahead needs answers in seven, that gap is a schedule risk you can put a number on and raise at the owner meeting before it becomes a delay claim.
Portfolio reports: for the office, not the trailer
Cross-project reporting is genuinely useful — for the person running four jobs, not the super running one. When you roll PPC, compliance rates, and safety metrics across a portfolio, you start to see which subs perform everywhere versus which ones only look good on the easy job. That's how you build a real prequalification list instead of one based on who bought lunch. Just don't mistake portfolio dashboards for field tools. The super in the trailer needs this week's plan, not the company benchmark.
Make reporting a habit, not an event
A report you read once a month is a report you read too late. Build a short rhythm and stick to it:
- Daily: a two-minute look at today's commitments and any red compliance flags.
- Weekly: PPC and variance reasons at the plan meeting, look-ahead constraints for the next three weeks, RFI and submittal aging against upcoming work.
- Monthly: trends — CO volume, quality patterns by trade, payment aging — the slower-moving stuff you fix with policy, not a phone call.
Set the routine ones to generate and land in your inbox automatically so reviewing them is friction-free. And pull the whole thing up on your phone in the field — the value of a report drops fast the further you are from the work it describes. Good scheduling software supports the practice by keeping the plan, the trade flows, and these reports in one place, so the number you see always traces back to a task you can actually walk over and look at.
The best superintendents I've worked with don't run more reports than everyone else. They run fewer, they read them earlier, and they act on the first slip instead of the third. A reporting system is only as good as the Monday-morning decision it changes. Judge yours by that.