A Schedule You Don't Track Is Just a Wish List
Every job starts with a beautiful schedule. Clean bars, tidy logic, everybody nodding in the pre-con meeting. Then week three hits, the underground guy is three days behind because of a utility conflict nobody flagged, and the schedule on the wall might as well be a poster. It's decoration. Nobody's looked at it since the printout.
The difference between a schedule that runs your job and one that gathers dust is one thing: tracking. Tracking is the discipline of comparing what you planned to happen against what actually happened, on a regular cadence, and doing something about the gap. It's not glamorous. It's the part everybody skips. And it's the single highest-leverage habit a superintendent can build, because it's the only thing that turns a schedule from a prediction into a control system.
This is about how to actually track progress — what to record, how often, where the reported numbers lie to you, and how to read the variances so you're responding to trouble in week three instead of discovering it in week nine.
What "Tracking" Actually Means on a Live Job
At its core, tracking answers three questions for every activity in flight: Did it start when it was supposed to? Is it moving at the rate we assumed? And when will it really finish? Everything else — percent complete, remaining duration, variance reports — is just machinery for answering those three honestly.
The trap is treating tracking as a data-entry chore. Somebody types "60% complete" into a field, feels productive, and moves on. But 60% of what? Sixty percent of the drywall hung is a very different animal than 60% of drywall hung, taped, and ready for paint. If your tracking doesn't tie back to a physical, verifiable state on the floor, you're not tracking — you're guessing with more decimal places.
Record Actual Start and Actual Finish — Not Just Status
The two most valuable data points on any activity are its actual start date and its actual finish date. Not the plan. The reality. When did the crew truly break ground on that pour, and when was it truly done, ready for the next trade to walk on?
These matter for two reasons. First, actual dates are what let you calculate real durations, and real durations are how you fix your bad assumptions. If you budgeted five days for exterior sheathing on the first building and it took eight, you now know buildings two through six need eight — before you promise the owner a finish date built on the fantasy of five. Second, actual dates build the historical record that makes your next job's schedule less of a fairy tale. Most estimators are working from gut feel and a durations sheet from 2015. A firm that captures real actuals across jobs is compounding an advantage nobody else has.
Discipline here is simple but easy to drop: record the actual start the day work begins, not the Friday you get around to updating. Memory decays fast on a busy site, and "I think they started Tuesday" quietly becomes the wrong number in your history file.
Percent Complete Lies — Here's How to Make It Honest
Percent complete is the most abused metric in construction. It's abused because it's subjective, and subjective numbers drift toward optimism. Ask a foreman how his activity is going and the answer is almost always "about 90%." The last 90% then takes as long as the first 90%. Every super has lived this.
A few rules of thumb to keep percent complete grounded:
- Tie percentages to physical milestones, not effort spent. "We've been at it three days out of five" is not 60% done — it's three days of effort, which tells you about cost, not completion. Completion is about installed, inspected work on the floor.
- Use the 0/50/100 rule for short activities. For anything under a week, don't fuss with granular percentages. It's either not started (0), in progress (50), or done (100). The precision you'd gain isn't worth the argument, and false precision is worse than none.
- Never let an activity sit at 90-plus for more than a day or two. A pile of activities stuck at "95%" is the classic signature of a job that's actually behind and hiding it. Those trailing percentages are where schedules go to die.
For anything meaningful in length, remaining duration is the better question to ask than percent complete — which brings us to the number that actually drives your finish date.
Remaining Duration: The Number That Forecasts Your Finish
Percent complete looks backward — it tells you where you've been. Remaining duration looks forward, and forward is where the money is. When you ask a foreman "how many more days do you need to finish this?" you get a far more useful answer than "how done are you?" One is a forecast you can plan against; the other is a report card.
Here's why it matters mechanically: your schedule's projected completion is only as good as the remaining work feeding it. An activity that's "70% complete" with a wildly optimistic remaining duration will still show finishing on time right up until the day it blows the date. Update remaining duration honestly — including the cleanup, the punch, the inspection wait — and your projected finish stops lying to you. The activities downstream shift in real time, and you can see the pileup coming while you still have room to move.
Set a Status Date and Hold the Line
Every tracking update needs a status date — the "as of" line that separates what's done from what's forecast. Everything to the left of it is history and shouldn't move; everything to the right is your best current projection. Without a firm status date, updates turn to mush: half the schedule reflects last Tuesday, half reflects this morning, and nobody can tell you where the job truly stands.
Pick a consistent status point — end of day Friday is the industry norm for weekly tracking — and stick to it. When you update, you're marking "this is where we are as of Friday quitting time," and the rest of the schedule recalculates from that anchor. On a look-ahead scheduling app like LookAheadWall, that status line is what keeps the weekly work plan honest: last week's committed work is locked as fact, and the coming weeks redraw around what actually got done.
Where Your Progress Data Actually Comes From
Tracking is only as good as its inputs, and the inputs come from the field — not the trailer. The reliable sources, roughly in order of trustworthiness:
- Your own eyes. Walk the job. There is no substitute. A ten-minute walk tells you more about real status than an hour of reading reports, because you can see the pile of uninstalled material behind the wall that the "80% complete" number conveniently omitted.
- Foreman commitments and reports. The people doing the work know the work. Daily huddles and the foreman's own count are gold — as long as you're cross-checking against what you see.
- Timesheets and quantities installed. Good for cost tracking and useful as a sanity check, but remember they measure effort and money, not necessarily finished, inspected work.
The failure mode to avoid is tracking from a desk. If your only input is a foreman texting you a percentage while you sit in the trailer, you've built a game of telephone where everybody's incentive points toward "it's fine." It's usually not fine. Walk it.
Capture Progress in the Field, Not From Memory
The single biggest killer of tracking accuracy is delay. Progress recorded three days after the fact is progress filtered through faulty memory and wishful rounding. This is why field-based entry matters so much — when a crew leader can mark work complete on a phone standing right in front of it, you get the number while it's still true. That's the whole point of a mobile companion for the crew leads: the guy who knows exactly what got done today records it today, from the deck, instead of reconstructing it Friday afternoon.
The mechanics matter less than the habit. Whether it's an app, a marked-up plan, or a whiteboard photo, the rule is the same: capture it at the point of work, at the time of work.
Reading Variances — The Part That Earns Its Keep
Recording progress is bookkeeping. Variance analysis is where tracking pays for itself. A variance is simply the gap between planned and actual, and the whole game is spotting the ones that matter early enough to react.
What to actually watch:
- Variances on critical-path work. A trade slipping two days on activity that has a week of float is a note. The same two days on the critical path is a two-day hit to your finish date and possibly liquidated damages. Know the difference cold. Not all delays are equal, and treating them equally is how supers burn energy on the wrong fire.
- Trend, not snapshot. One activity behind is noise. Three activities from the same trade behind, week over week, is a signal — that sub is undermanned, and no amount of schedule pressure fixes a manpower problem. Tracking history is what lets you see the trend instead of reacting to each blip.
- Downstream compression. When an early activity slips and you're still holding the end date, somebody downstream just had their window squeezed. Find out who before they find out from you. That's the coordination gotcha that turns a small early slip into a trade stacking disaster at the end.
Verify Before You Trust the Numbers
Reported progress and real progress are two different quantities, and the gap between them is where jobs quietly go sideways. Build a habit of spot-verification: pick a couple of activities each week that show as complete or nearly complete, and go physically confirm them. Is that in-wall rough-in really done and inspected, or done-except-for-the-part-that-needs-the-wall-open-again? Was the run meggered before they closed it up? Verification isn't distrust — it's the recognition that "done" means different things to the person installing it and the person who has to build on top of it.
Keep the History — It's Worth More Than You Think
When a job closes out, most of the tracking data gets archived and forgotten. That's a mistake. Your recorded actuals — real durations, real start-to-start lags between trades, the activities that always ran long — are the raw material for scheduling the next job accurately. The firms that consistently hit their dates aren't smarter; they're the ones who bothered to remember what actually happened last time. A durations library built from your own completed jobs beats any published standard, because it reflects your crews, your subs, and your typical conditions.
The Bottom Line
Tracking isn't about the software, the reports, or the color-coded bars. It's a weekly discipline: set a status date, walk the job, record real actuals and honest remaining durations, and act on the variances that threaten your critical path. Do that consistently and the schedule becomes what it was always supposed to be — a tool that tells you where the job is heading in time to change course. Skip it, and you've got a very nice poster on the trailer wall. The good scheduling tools, LookAheadWall included, exist to make that weekly discipline fast enough that you'll actually keep doing it. But the discipline is yours. No app tracks a job you don't walk.