Ask any superintendent what makes a schedule go stale and you'll get the same answer: nobody's telling it the truth. The plan on the wall says drywall's hung on level three, but you walk it Thursday afternoon and half the board is still banded on the deck. The schedule didn't lie to you. A foreman did — usually not on purpose, usually because reporting progress felt like paperwork instead of part of the job.
Progress reporting is the single most undervalued task on a jobsite. A look-ahead schedule is only as good as the last honest update fed into it. Get the reporting habit right and your weekly work plan stays a live tool that crews actually trust. Get it wrong and the schedule becomes a poster — something the office prints, everyone nods at, and nobody follows. This is a field-level guide to doing it right.
Why the update matters more than the plan
Here's the uncomfortable truth about short-interval scheduling: the plan you build Monday is a hypothesis. The value comes at the end of the week when you compare what you said would happen against what actually did. That comparison — planned percent complete versus actual, and why the gap exists — is the whole point of the Last Planner approach. Skip the honest reporting and you've thrown away the only feedback loop that makes next week's plan smarter than this week's.
A foreman who reports well isn't doing the office a favor. He's protecting his own crew. When your reported progress is accurate, the super stops standing over your shoulder, the general contractor stops second-guessing your durations, and the trades stacking behind you show up when the work is actually ready instead of a day early to stand around and bill for it. Reliable reporting buys you autonomy. That's the trade.
Report at the task level, not "we're good"
The most common reporting failure isn't dishonesty — it's vagueness. "We're about 80 percent on the second floor" tells the schedule nothing it can use. Eighty percent of what? Which rooms? Is the remaining 20 percent the easy runs or the mechanical room that's going to eat two days?
Report against the actual activities on the plan, by location. If your look-ahead breaks the floor into zones — and it should — then your update is zone by zone: Grid A–C rough-in complete and ready for inspection; Grid C–F wall done, ceiling grid starts tomorrow; Grid F–H blocked, no power to the panel yet. That's a report a superintendent can act on before the day's over. Location-based reporting is where visual look-ahead tools earn their keep — in an app like LookAheadWall you're dragging the status on a specific activity in a specific area, not typing a paragraph nobody reads.
Partial progress: be honest about the last 20 percent
Every trade knows the drywall math: the first 80 percent goes fast and the last 20 percent — the closets, the soffits, the coordination with the plumber who left a stub in the wrong spot — takes as long as everything before it. When you mark partial completion, weight it toward reality, not optimism.
A rule of thumb that's saved a lot of superintendents grief: don't call anything "90 percent" for more than one day. If a task has been sitting at 90 for three straight reports, it isn't at 90 — it's stuck, and something is blocking the finish. That plateau is a flag, not a status. Report the blocker instead of the percentage.
Completions clear the deck for the trade behind you
Marking work complete does more than clean up your own line on the schedule. It's the release signal for the next trade. Framing complete and inspected is what lets electrical and plumbing rough-in start. Rough-in complete and signed off is what lets insulation and drywall close the wall.
So when you mark something done, mean it. "Done" should mean done and ready for the hand-off — inspected where an inspection gates it, punched where it needs punching. A framer who marks a wall complete while it's still missing backing for the grab bars has just set up the drywall crew to hang board over a wall that has to be reopened. Every premature "complete" is a callback waiting to happen, and callbacks are where schedules go to die.
Build the buffer into your thinking. Frame-to-rough-in usually wants a one-to-two-day gap for cleanup, layout verification, and the inspection sign-off — reporting the frame "complete" the same afternoon the last stud goes up ignores that the trade behind you can't actually start until the paperwork clears.
Track quantities, because durations are just quantities in disguise
The foremen who get respected in planning meetings are the ones who report production, not just status. "We set 340 linear feet of top track today" is worth ten times "we made good progress." Quantities turn into productivity rates, and productivity rates turn into durations you can actually defend when the GC pushes you to compress.
Keep it simple: pick the one or two units that drive your trade — linear feet of wall, squares of roofing, fixtures set, cubic yards placed — and log them daily. Over two or three weeks you'll know your crew's real rate on this job, on this building, with this access. That number is your best weapon the next time someone hands you a look-ahead with durations that were pulled out of thin air. You'll be arguing from data instead of gut feel.
A photo is worth a hundred status arguments
Attach a photo to the progress you report, especially for work that's about to get covered. Nobody argues with a picture. When the drywall's up and someone asks whether the fire caulk got done at the penetrations, the photo you took at rough-in ends the conversation in ten seconds instead of a destructive-testing order.
Photos also protect you. Progress reporting isn't only about the schedule — it's a record. The day a delay claim shows up six months later, the foreman who documented what was actually complete, when, with timestamped photos tied to specific activities, is the one who's covered. The one who reported "we're good" every day has nothing to stand on.
The variance is the whole point — write the reason down
When a planned task didn't get done, the schedule doesn't need an apology. It needs a reason, and a specific one. "Didn't finish" is useless. "Couldn't close Grid F–H — panel wasn't energized, waiting on the EC" is gold, because it names the constraint and points at the fix.
Track the reasons and patterns jump out fast. If half your incomplete tasks trace back to the same missing prerequisite — materials late, prior trade not done, RFI unanswered, access blocked — you've just found the real problem on the job, and it isn't your crew. This is the discipline behind Last Planner's reasons-for-variance: the point isn't to assign blame, it's to stop the same constraint from wrecking next week too. A few honest variance notes over a month will tell you more about why the job is slipping than any Gantt chart ever will.
Report while you're standing in it
The worst time to report progress is the next morning from memory. By then the details are gone — you've rounded up, forgotten the blocker, and lost the exact quantity. Capture it in the field, while you're looking at the work.
This is the practical case for a mobile companion app over a clipboard that gets transcribed at the trailer. When a crew leader can stand in the room, mark the activity, snap the photo, and note the blocker on his phone, the schedule updates in real time and the superintendent sees it before the day ends. That immediacy is what turns a weekly work plan from a Monday ritual into a living document. The tool matters less than the habit — but the right tool makes the habit almost frictionless, which is the only way a habit survives a busy jobsite.
Accuracy over optics — always
There's a temptation, especially when the pressure's on, to report the progress you wish you had. Resist it. An optimistic report doesn't buy you anything — it just moves the reckoning to a worse moment, usually the day the trade behind you shows up to work you swore was ready.
The best foremen I've worked with had a reputation for one thing: when they said it was done, it was done. That credibility is worth more than any single good week. A schedule built on honest reporting can absorb bad news — you replan, you resequence, you recover. A schedule built on wishful reporting collapses all at once, usually near the end, when there's no room left to recover.
The daily habit, in five lines
- Report by location and activity — zone by zone, against the actual tasks on the plan, not a blanket percentage.
- Log real quantities — the one or two units that drive your trade, every day, so your durations are defensible.
- Name the blocker — when a task didn't finish, write the specific reason, not "didn't get to it."
- Photograph anything about to be covered — rough-in, backing, fireproofing, waterproofing. Tie it to the activity.
- Do it in the field, same day — from where the work is, while the details are fresh, not from memory the next morning.
None of this is complicated. It's five minutes at the end of a walk, done consistently. But it's the difference between a look-ahead schedule that everyone trusts and one that quietly becomes fiction. The plan gets the headlines in the planning meeting. The update is what actually keeps the job running — and the foreman who masters it becomes the one every superintendent wants on the next building.