Ask ten superintendents how a job is doing and you'll get ten different answers, most of them a shrug and "we're about 60 percent." Sixty percent of what? Sixty percent of the drawings? Sixty percent of the money spent? Sixty percent of the guys think we'll finish on time? Progress feels obvious until you have to defend a number to an owner who's holding a retention check. The whole point of tracking progress in software is to replace that gut feel with something you can point to on a screen and stand behind.
Here's the thing nobody tells you when you buy a platform: the software doesn't know how your job is going. It only knows what you feed it. Every method below is really a discipline dressed up as a feature. Understand what each one actually measures — and what it hides — and you'll use the right tool for the right question instead of trusting a dashboard that's quietly lying to you.
Percent Complete: The Number Everyone Games
Percent complete is the default because it's easy to enter and easy to read. It's also the easiest number on the job to fudge. A framer who's stood up every wall but hasn't touched the blocking or backing will tell you he's 90 percent done. He's not. That last 10 percent — the fire blocking, the nailer for the grab bars, the backing the drywallers will curse him for missing — routinely eats a third of the total hours. This is the classic "90 percent done, 90 percent to go" trap, and it's how schedules slip three weeks while the bar chart still reads dark green.
Two habits fix most of it. First, tie percent complete to something physical wherever you can, not to somebody's feeling. Second, cap self-reported percentages until an inspection or a quantity check backs them up. A lot of teams use rules-of-credit — 0 percent until started, 50 percent at a defined checkpoint, 100 percent only after sign-off — so nobody can drift a task to 85 percent and park it there for a month. It's blunt, but blunt is honest.
Physical Quantities: The Progress You Can Count
The most defensible progress on any job is the kind you can walk out and count. Linear feet of pipe hung. Square feet of drywall boarded. Cubic yards placed. Doors set. When your software tracks installed quantity against a planned total, you get a number that doesn't care how anyone feels — either the 1,400 linear feet of underground is in the ground or it isn't.
Quantity tracking also quietly gives you production rates, which is where the real intelligence lives. If your electricians roughed in 40 devices a day for the first floor and you've got four identical floors above it, you can forecast the rest with actual data instead of the estimator's original assumption. When the rate drops to 25 a day, that's your early warning — a coordination problem, a material shortage, or a crew that got quietly pulled to another job. The number moves before the schedule does, which is exactly when you want to know.
Milestones: Progress the Owner Actually Cares About
Owners and lenders don't think in activities. They think in events: building dried-in, permanent power energized, temporary certificate of occupancy, first units turned over. Milestone tracking rolls up hundreds of tasks into the handful of dates that trigger draws, move-ins, and everybody's stress level.
The discipline here is picking milestones that are binary and inspectable. "Roughly done with MEP rough-in" is not a milestone; it's an argument waiting to happen. "MEP rough-in inspection passed, floors 1 through 3" is a milestone — it either happened or it didn't, and there's a signed card to prove it. Good milestones are the ones you'd be comfortable putting money on, because on most jobs, someone is.
Planned vs. Actual: Where the Truth Hides
A single progress number tells you where you are. Comparing it to where you said you'd be tells you whether you're in trouble. This is the heart of real progress tracking, and it's why a baseline matters so much. Without a saved plan to measure against, "we're 60 percent complete" is just trivia. Against a baseline that said you'd be 75 percent by this date, that same 60 percent is a red flag you can act on today instead of explaining away in a claim next quarter.
The trap is letting the baseline drift. Every time you quietly re-baseline to match reality, you erase the evidence of the slip — and the memory of why it happened. Keep the original plan frozen. Track your current forecast against it. When the gap opens, the shape of that gap over a few weeks tells you whether you're recovering, holding, or sinking. One bad week is noise. Three bad weeks trending the same direction is a pattern, and patterns are what you manage.
Earned Value: Tying Schedule to Money
Earned value is the method finance people love and field people usually ignore, and both are half right. Done properly, it fuses schedule progress and cost into two numbers you can read in five seconds. Schedule Performance Index (SPI) tells you if you're ahead or behind the plan; Cost Performance Index (CPI) tells you if you're over or under budget. Above 1.0 is good, below 1.0 is a problem, and the two together catch a specific nightmare: a job that looks on schedule only because you're burning overtime and premium labor to hold the date. The SPI looks fine; the CPI is bleeding.
The catch is that earned value is only as good as your cost loading. If the budget behind each activity is garbage, the indices are garbage with decimals. On a well-run job with clean cost codes it's genuinely powerful. On a job where nobody trusts the estimate, it's theater. Know which job you're on before you present those numbers to anybody.
Photos and Daily Reports: The Record That Saves You Later
Progress photos and daily logs feel like busywork right up until the day you need them. Then they're worth more than anything else in the system. A dated photo of installed backing behind the drywall settles a change-order fight in thirty seconds. A daily report showing the concrete sub had no-showed four days running is the difference between a defensible delay claim and your word against theirs.
The trick is capturing them at the source. When a foreman shoots a photo from his phone and it lands attached to the actual task — with a timestamp and a location — you build a record without anyone doing paperwork twice. A mobile app that lets crew leaders log what got done and snap a photo without opening a laptop is worth ten reminders to fill out the log later, because "later" never comes and memories are worthless in a dispute.
Look-Ahead Readiness: The Progress Metric That Predicts the Future
Every method above tells you what already happened. The most useful progress signal on a jobsite tells you what's about to happen — and whether it can. This is where short-interval and look-ahead scheduling earn their keep. Instead of only measuring completed work, you measure whether the next two to six weeks of work is actually ready: materials on site, prerequisite trades finished, RFIs answered, permits in hand, equipment lined up.
The number to watch is how much of your planned near-term work actually has every constraint cleared — the make-ready that the Last Planner crowd built their whole method around. If only half of next week's tasks are truly ready to go, you don't have a scheduling problem, you have a supply-and-coordination problem that will become a scheduling problem the moment those crews show up to a wall they can't work. Tracking readiness turns your look-ahead from a wish list into a commitment you can measure. It's also the honest answer to "how's the job going," because a job that's 60 percent complete with a clear runway ahead is in far better shape than one that's 65 percent complete and blocked on every front.
This is exactly the gap a visual, location-based planning tool like LookAheadWall is built to close — you can see at a glance which trade flows are teed up and which are jammed, week by week, so readiness stops being a surprise you discover on Monday morning.
Critical Path and Phase Rollups: Knowing What Actually Moves the End Date
Not all progress protects your completion date. You can crush a week of finishes on units that were never going to hold up turnover while the elevator inspection — sitting dead on the critical path — slips a day and drags the whole job with it. Tracking progress specifically on critical activities keeps your attention where it belongs. Ten percent behind on float-rich work is a rounding error. One day behind on the critical path is a real day off the end of the job, every time.
Phase rollups do the same thing at a higher altitude. Rather than drowning in a thousand tasks, you watch a handful of phases — foundations, structure, dry-in, rough-in, finishes, closeout — advance across the calendar. It's the view you want when the owner walks the site and asks where things stand. You point at the phase board, not the Gantt chart, and everybody in the room understands it.
Dashboards Are the Answer, Not the Question
Every platform sells the dashboard — the tidy screen of dials and bars that makes a job look under control. A dashboard is only as honest as the field data feeding it, and a beautiful dashboard built on stale updates is more dangerous than no dashboard at all, because it manufactures confidence you haven't earned. The teams who get real value out of progress tracking aren't the ones with the prettiest charts. They're the ones with a boring, consistent habit: crews report what they actually did, quantities and inspections back up the percentages, and the whole thing gets updated on the same cadence every week without fail.
Pick two or three methods that fit your job and run them religiously. On a fast production build, physical quantities and look-ahead readiness will tell you almost everything. On a cost-sensitive job with a nervous owner, milestones and earned value carry the day. The software is just the instrument. The reading is only as good as the hand on the gauge — and on a jobsite, that hand is yours.