Here is the uncomfortable truth about most weekly work plans: they get built on Thursday, handed out on Monday, and never looked at again until the next Thursday. The plan and reality quietly drift apart all week, nobody writes down why, and by the time you're staring at a blown budget line at closeout you're guessing at what happened. Productivity tracking is just the discipline of closing that loop — writing down what you planned, what you got, and the gap between them, week after week, until the pattern tells you something you can act on.
You don't need a data science team to do this. You need a foreman who counts, a plan that lists quantities and hours, and the habit of comparing the two every Friday. That's the whole game. Everything below is how to play it well.
Why the Weekly Plan Is the Right Place to Measure
The master schedule is too coarse to teach you anything about productivity. It tells you drywall is a three-week activity; it does not tell you that your hangers did 42 sheets a day on the low corridors and 26 a day on the high-lid areas over the atrium. That difference — hidden inside a single Gantt bar — is where your money is either made or lost.
The weekly work plan is the finest-grained schedule you actually commit to out loud. Crews are named, areas are assigned, and the work is small enough that a foreman can look at it and say yes, we can do that, or no, we can't. Because it's already broken down by crew, area, and activity, it's the natural unit to measure against. You planned Crew B to hang the east corridors, second floor, Monday through Wednesday. On Friday you know exactly whether they did. No interpretation required.
That's the quiet advantage of doing short-interval planning inside a real look-ahead tool instead of a whiteboard photo: every commitment is already a discrete, ownable line. Productivity tracking stops being a separate spreadsheet chore and becomes a second column next to the plan you already made.
The Two Numbers That Matter: Quantity and Hours
Strip productivity down and it's two measurements per activity: how much work went in the wall (quantity), and how many labor hours it cost you (hours). Everything else is arithmetic on those two.
- Unit rate — labor hours per unit installed (LF of pipe, SF of drywall, each of light fixtures). This is the number you'll actually use to estimate next time. If your electricians are running 0.35 hours per fixture on this job and you bid the next one at 0.25, you have a problem you can see months early.
- Productivity factor (PF) — earned hours divided by actual hours. Earned hours are budgeted-rate hours for the quantity you actually installed. A PF of 1.0 means you're on budget. Below 1.0 you're bleeding. Above 1.0 you're beating the bid — and you should be as suspicious of that as of a low number, because it often means someone miscounted quantities.
Count quantities the same way the estimate counted them. This trips people up constantly. If the estimator bought drywall by the square foot of board hung, don't track it by the sheet — you'll never be able to compare your field number to the bid, and the comparison is the entire point. Pull the unit of measure straight off the budget and make the foreman report in that unit.
How to Actually Capture It Without Slowing the Job
The failure mode here is asking foremen to fill out a productivity form that takes twenty minutes and adds nothing to their day. They'll fake it by Wednesday. Keep the capture attached to work they're already doing.
The cleanest rhythm is this: hours come off the timecard you're already keeping, coded to the same activities that are on the weekly plan. Quantities get a two-minute walk at the end of each day — the foreman writes down what got installed, in plan units, against each activity line. That's it. If your look-ahead schedule already lists the week's activities by crew, the foreman is just putting a number next to a line he's already looking at. No parallel system.
The single most important discipline: capture the reason for any miss, not just the miss. A quantity that came in short is a data point. "Came in short because the fire-caulk inspection held us out of the east shafts for a day and a half" is a lesson. The reason codes are worth more than the numbers over time, because they're what let you fix root causes instead of nagging crews to go faster.
Reading the Numbers: What Good and Bad Look Like
Don't react to a single week. Field productivity is noisy — weather, a bad material delivery, one guy out sick, and your unit rate swings. Watch the trend across four to six weeks. Here's how to read what you see:
- A steadily declining unit rate (fewer hours per unit) as an activity ramps up is normal and healthy — it's the learning curve. Crews get faster as they learn the building. If you don't see this improvement in the first couple weeks of a repetitive scope, something is wrong with the setup, not the crew.
- A unit rate that spikes on specific areas tells you those areas have a hidden cost — congestion, height, a coordination clash, a detail that's harder than the typical. That's gold for planning the rest of the building.
- A productivity factor that looks great but quantities that don't add up to the model count almost always means over-reported quantities, not superhuman crews. Trust the tape, not the optimism.
- Consistent underperformance across every crew and trade is rarely a labor problem. It's usually a plan problem — you're feeding crews work that isn't ready, and they're spending a third of their day hunting for a clear area to work in.
That last point is the one superintendents miss most. When productivity is bad everywhere, stop measuring the crews and start measuring your own readiness. Which brings us to the real driver.
Productivity Is Mostly a Planning Problem
Twenty years on jobsites will teach you this: crews rarely lose productivity because they got slower. They lose it because they're waiting — on materials, on the trade ahead of them, on an inspection, on an RFI answer, on a clear and safe area to stand in. The hammer time is fine. It's the walking, waiting, and reworking that eats the budget.
This is exactly why tracking productivity against the weekly plan is more powerful than tracking it in isolation. When you can see that Crew B's unit rate tanked the same week the plan shows they were stacked on top of the mechanical rough-in that ran three days long, you've found your cause. The productivity number and the schedule sequence tell the story together.
A few coordination gotchas that quietly wreck field productivity — worth watching for whenever a rate goes bad:
- Overlapping trades in the same area. Two crews in one corridor don't do half the work each; they do maybe 60% each and generate friction. Sequence them, don't stack them.
- Rough-in without a clean buffer to close. Push framers hard against rough-in with no gap and you'll pay for it — figure a 1–2 day buffer between frame and rough-in for cleanup, corrections, and the inspection you cannot skip. Megger the runs and pressure-test the lines before anyone closes a wall, because the rework cost of a failed test after drywall is brutal and it never shows up in the crew's productivity — it shows up as a schedule fire three weeks later.
- Work fronts that aren't actually released. A crew assigned to an area that's still 90% ready spends the morning working around obstructions. The plan said go; the field said not really. That gap shows up as a bad unit rate and gets blamed on the crew.
Turning Data Into Better Plans
Tracking that doesn't change next week's plan is just bookkeeping. The payoff comes when your actuals start driving your durations. Here's the loop that actually improves a job:
- Measure the unit rate and PF for each activity this week, in budget units.
- Compare to the bid rate and to the same activity in prior areas. Note the misses and their reason codes.
- Adjust the durations in your look-ahead for the upcoming areas. If the field is running 30% slower than the bid on this scope and you can't change the manpower, then the three-day activity is a four-day activity. Pretending otherwise just moves the lie downstream.
- Attack the reasons. If the misses trace to material staging, fix staging. If they trace to a trade running long ahead of you, protect the buffer. Chase the causes in your reason codes, in order of frequency.
Do this for a month and something valuable happens: your weekly plans start coming true. Your percent-plan-complete climbs not because crews got heroic but because you stopped writing plans the field couldn't hit. That's the real win — a schedule people believe, built on rates you measured instead of rates you wished for.
Use the Data on People Carefully
One hard-earned warning. The instant productivity numbers become a stick to beat crews with, the data goes bad. Foremen will pad quantities, under-report hours, and stop writing honest reason codes. You'll have a beautiful dashboard full of fiction.
Keep the framing on the work, not the worker. The east corridors are slow — why? The atrium fixtures are eating hours — what's the detail costing us? Bring the foreman into reading his own numbers; he knows things the spreadsheet doesn't. Productivity tracking earns its keep as a tool for finding and clearing obstacles, and it only works if the people feeding it trust that's what it's for.
Start Small
You don't need to track every activity on the job to get value. Pick the three or four scopes that carry the most labor risk — the ones that'll make or break the budget — and track those hard. Quantities daily, hours off the timecard, reasons for every miss, compared against the weekly plan every Friday. Let the habit prove itself on the scopes that matter, then widen it.
What gets measured gets managed, sure. But the version that's actually true on a jobsite is narrower and more useful: what gets measured against a plan, with the reasons written down, gets improved. The weekly work plan gives you the plan. Counting gives you the actuals. The Friday comparison, done honestly and repeated, is where a good superintendent turns a noisy job into a predictable one.