Every Monday morning, somebody on your job is lying to you about progress. Not maliciously. The drywall foreman says he's "about 80 percent" on the third floor because that's what he said last week and it feels like he's made progress since. The truth is he's at 60, he lost two hangers to another job, and you won't find out until the tapers show up Thursday to a wall that isn't ready. Progress tracking isn't paperwork. It's the difference between managing your schedule and finding out about problems after they've already cost you a week.
Good tracking answers one question: is the work actually where the plan says it should be, and if not, how far off and why? Everything below is about getting an honest answer to that question fast enough to do something about it. Software helps, but only if you know what you're measuring and what the numbers are hiding.
Status is the floor, not the answer
The most basic thing you track is state: not started, in progress, complete. It's useful because it's fast — a foreman can flag ten activities in thirty seconds — and because "complete" is a clean, binary word that's hard to fudge on inspected work. Underground's either signed off or it isn't.
The trap is the giant gray bucket in the middle. "In progress" covers an activity that started an hour ago and one that's been stuck at the finish line for a week waiting on a missing part. When half your board reads "in progress," you know nothing. Status tells you what's moving. It doesn't tell you whether it's moving fast enough, and it never tells you why something stopped. Treat it as the entry point, then push for detail on anything that's been "in progress" longer than its duration should allow.
Percent complete and the 90 percent lie
For longer activities you need partial progress, and percent complete is the usual tool. It's genuinely useful for earned-value math and for anything measured in installed units — you can defend "60 percent of the fixtures are set" because you can count them. The danger is the self-reported percentage on work you can't count, where a foreman's optimism becomes your baseline.
The classic failure is the activity that races to 90 percent and then sits there for as long as it took to get there in the first place. The last 10 percent is punch, trim-out, the odd fixture on backorder, the one corner nobody wants to touch. If you're tracking rooms, "9 of 10 rooms done" beats "90 percent" every time, because the ninth room being finished is a fact and 90 percent is a feeling. Tie percentages to something physical and countable, or don't trust them past the halfway mark.
Actual dates are your memory of what really happened
Status and percentages tell you about today. Actual start and finish dates tell you what happened, and that record is worth more than people think. Capture the real start and the real finish on every activity, not the planned ones, and do it while it's fresh — nobody remembers three weeks later whether framing on level two actually started the 4th or the 7th.
Two things fall out of clean actuals. First, planned-versus-actual duration: if you budgeted five days for a task that keeps taking eight, that's not bad luck, that's a bad number you'll keep repeating on every floor until you fix it. Second, dates are your paper trail. When the delay claim shows up at closeout, the job with dated activity records wins the argument and the job running on memory pays for it. A look-ahead schedule that carries real actuals alongside the plan turns into the most credible document on the project.
Labor hours: the early-warning signal
On labor-driven work, hours burned against hours planned is often your first honest signal that something's wrong — earlier than percent complete, because it's harder to fake a timecard than an estimate. If you planned 200 hours for a task and you're at 150 hours with the work half done, you don't have a schedule problem yet, but you have a productivity problem that's about to become one.
The number that matters isn't total hours, it's the ratio of hours spent to work in place. Watch that ratio drift and you can catch a crew that's undermanned, poorly sequenced, or fighting the same access problem over and over, while there's still time to add people or unstick the bottleneck. Hours lag reality by a day or two, so pair them with a walk. But as a trend, they rarely lie.
Quantities and the units that don't move
For scoped work — linear feet of pipe, square feet of deck, number of doors hung — installed quantity against total quantity is the cleanest progress measure there is, because you can walk out and count it. It also feeds an honest percent complete instead of a guessed one.
Track quantities by location, not just by activity. "40 percent of the plumbing is roughed" is nearly useless. "Roughed on floors one and two, floors three and four untouched" tells you exactly where the next crew can and can't start. The location breakdown is what turns a quantity into a decision.
Photos: proof, not decoration
A dated photo settles arguments that words can't. Progress photos with automatic location and timestamp metadata are worth capturing on anything that's about to be covered — before the wall closes, before the slab pours over the conduit, before the ceiling grid goes in over the ductwork.
The habit that pays off is the before-you-cover-it shot. When the inspector, the owner, or the next trade asks what's behind that wall, you have the answer. When a sub claims they never had access to an area, the photo with the date on it ends the conversation. Photos don't measure progress, but they prove it, and proof is what you're missing at 10 a.m. on the day the dispute starts.
Capture it in the field or don't bother
Here's the rule that makes or breaks everything above: progress gets recorded where the work is, when the work happens. The moment tracking requires a foreman to remember his morning and type it up at a desk at 4 p.m., the data degrades into a rough guess, and by Friday it's fiction.
Mobile entry from the floor is what keeps the numbers honest. A foreman standing in the room, counting the actual fixtures, tapping in the actual count — that's real data. The same foreman reconstructing his day from memory an hour after he's left the building is writing a story. This is exactly where a mobile companion built for crew leaders earns its keep: the person doing the work updates the plan from the spot where the work is, and the schedule reflects the floor instead of somebody's recollection of it. LookAheadWall's crew-leader app exists for precisely this reason.
Real-time visibility changes who finds out first
When progress posts the moment it's captured, the whole team sees the same picture at the same time — no waiting for the Monday meeting to learn that Thursday went sideways. That speed is the entire point. A delay you learn about the day it happens is a problem you can still solve by resequencing or shifting a crew. The same delay discovered five days later is just damage.
The value of a live weekly work plan isn't the technology, it's the calendar you get back. Finding out Tuesday that Monday's pour slipped means you can protect the rest of the week. Finding out at next Monday's meeting means you've already lost it.
Variance, trends, and constraints — reading the data
Raw progress is data. The three things you do with it are where the management actually happens.
Variance is planned versus actual, and the discipline that separates good jobs from lucky ones is recording the reason for every miss, not just the miss. "Behind" is noise. "Behind because the material release was late three weeks running" is a pattern you can fix at the source. Track the reasons and you stop treating the same recurring problem as a fresh surprise every week.
Trends tell you where you're heading, not just where you are. A crew whose reliability climbs from 60 to 85 percent over a month is a crew you can lean on for the next phase. One drifting the other way needs attention before the number becomes a crisis. In lean scheduling terms, tracking how many weekly commitments a crew actually completes — the percent of promises kept — is one of the most predictive signals you have about whether the next month goes smoothly.
Constraint progress is the one most jobs ignore until it bites. Before an activity is ready to run, it usually needs a stack of things cleared — material on site, prior trade complete, inspection signed, RFI answered, equipment available. Tracking how those make-ready items are closing out, well ahead of the scheduled start, is what keeps you from arriving Monday with a crew and no way to put them to work. An activity that's "on schedule" but sitting on two open constraints is not on schedule. It just doesn't know it yet.
Rolling it up: subs, milestones, and the meeting that matters
Your subs' progress is your progress, so their updates have to land in the same picture as your self-perform work. A trade that's quietly a week behind on their scope is a week you're going to eat downstream, whether or not it shows in your numbers. Give trade partners a way to report against the commitments they made and you replace the weekly "how's it going" — answered with a shrug — with something you can actually see.
At the top sits milestone tracking: dried-in, permanent power, TCO, whatever the owner is counting. Milestones are how you communicate progress upward without drowning the owner in activity detail, and they're where all the small variances downstream finally add up into a number somebody cares about.
Pull it together and the discipline is simple, even if it isn't easy. Capture honest status, percentages tied to things you can count, real dates, hours against plan, installed quantities by location, and photos of anything about to disappear. Do the capture in the field, at the moment, so the numbers stay true. Then read the variance, the trends, and the constraints, and act while you still have runway. The crews that do this don't have fewer problems than everyone else. They just find out about them four days sooner — and on a construction schedule, four days is the whole ballgame.