Ask a superintendent what happened on the job eight weeks ago and you'll usually get one of two answers. Either they pull up a clean record and tell you exactly why the drywall slipped four days, or they squint, shrug, and say "I think that was the elevator inspection." One of those supers keeps their job when the delay claim lands. The other one becomes the delay claim.
Weekly work plan documentation is the boring, unglamorous discipline that separates those two outcomes. Nobody gets into this trade because they love filling out reports. But the record you build every week is what protects you in a dispute, what tells you honestly whether your planning is any good, and what lets the next super pick up where you left off. Here's how to build a documentation standard that actually earns its keep instead of one that just fills a folder nobody opens.
Why the record matters more than you think
Three things live or die on your weekly documentation.
First, accountability. When a crew commits to closing a wall by Thursday and it's still open Monday, you want a record of the commitment and the miss — not to hang anybody, but because a commitment you can't track is a commitment nobody made. The Last Planner method calls this Percent Plan Complete (PPC): the fraction of what you promised that actually got done. You can't calculate PPC if you didn't write down what you promised.
Second, claims and defense. Delay claims are won and lost on contemporaneous records — notes made the day it happened, not reconstructed six months later when memory has gone soft and everyone's got a lawyer. A dated photo of the slab still wet when the framer showed up is worth more than any amount of after-the-fact testimony. If it's not written down, on a jobsite, it didn't happen.
Third, and the one supers underrate most, learning. The reason your plan blows up is rarely a mystery once you've tracked variances for a month. If you write down why each activity missed — not just that it missed — patterns show up fast. "Waiting on the architect" three weeks running is a different problem than "crew got pulled to another job," and you only see it if you captured the reason at the time.
The core weekly record: what actually goes in it
Strip away the fancy talk and a weekly work plan record has four parts. Everything else is supporting material.
- Commitments made: the activities each crew committed to for the week, with the responsible party named. Not "framing" — "east wing corridor framing, layout through top track, Ramos crew."
- Completion status: did it, didn't, or partial. Be honest about partial. A wall that's 80% up is not done, and calling it done is how you lie to yourself for a month before the schedule catches you.
- Variance reasons: for every miss, why. Keep the categories tight and consistent — prerequisite work not complete, materials, manpower, design/RFI, weather, inspection, change in priority. Six or seven buckets, used the same way every week, so you can actually count them.
- PPC: commitments completed divided by commitments made, as a percent. Track it week over week. A healthy crew runs 70–85%. If you're routinely above 90% you're sandbagging the plan; below 60% and the plan isn't real yet.
That's the spine. If you capture nothing else, capture those four, every week, without fail. A good look-ahead tool like LookAheadWall records commitments and completion as a natural byproduct of building the plan, which is the point — the documentation should fall out of the work, not sit on top of it as a second job.
Activity-level detail worth keeping
Underneath each committed activity, four fields carry their weight in a dispute or a lessons-learned review:
- Clear description — location-based, not vague. "Level 3 north, in-wall rough plumbing" beats "plumbing."
- Responsible party — the crew or sub who made the commitment, by name. Ownership without a name is a wish.
- Planned dates — start and finish as committed.
- Actual dates — when it really started and finished. The gap between planned and actual, logged consistently, is your single most useful data set. It tells you which trades chronically run long and by how much, so next quarter's plan stops being fiction.
Constraints: log them before they become excuses
Make-ready planning is where the real money is, and the constraint log is how you prove you did it. For anything blocking a future activity, capture three things: the constraint identified, the action taken to clear it, and who owns it with a need-by date. "RFI 214 blocks the canopy steel — submitted 6/10, need answer by 6/24, owner: PM." When the steel slips because the answer came back 6/28, your log shows you flagged it two weeks out. That's the difference between a defensible delay and one that lands on you.
Photos, and doing them so they're actually useful
Everybody takes site photos. Almost nobody takes ones that hold up. Three habits fix that:
- Capture progress at consistent vantage points — same corners, same angles, every week. A time-lapse from a fixed spot tells a story a hundred random shots never will.
- Capture conditions that affect work the moment you see them — the wet slab, the missing embed, the stacked material blocking the corridor. These are the photos that win arguments, and they're only good if they're dated the day of.
- Capture issues tight and in context — one wide shot for location, one close for detail. A crack photo with no reference could be anywhere; useless six months later.
The metadata matters as much as the image. A photo with no date, no location, and no note is a photo you'll never find again. Geotagged, timestamped, and tied to the activity it documents — that's a record.
Daily records that feed the weekly picture
The daily report is the raw material the weekly plan sits on top of. Keep it lean but keep it every day: work accomplished by area, weather (real conditions, not "sunny" — "rain until 10am, 40 mph gusts, roofers stood down"), and crew counts by trade. Those manpower numbers are gold. When a sub claims they had ten guys on your job all month and productivity says otherwise, your daily counts settle it. Fill the daily out same-day, every day. A daily report written Friday for the whole week is a work of fiction, and everyone downstream knows it.
Standards that make the record usable, not just present
Documentation that exists but can't be found or trusted is barely better than none. Three standards fix that:
- Templates. Same fields, same order, every week. Consistency is what lets you compare week to week and lets a new hire produce a usable record on day one.
- Naming conventions. Decide a format — project, area, date, type — and never deviate. WestTower_L4_2026-07-03_dailyreport sorts and searches; report final FINAL (2) does not.
- Version control. One current version, clearly marked, and superseded ones archived, not floating. Two "current" plans on a job is how a crew builds to last week's sequence.
Timing: when the record gets made
The value of a record is inversely proportional to how long you waited to make it. Status that updates in real time as the plan runs beats a memory dump at week's end. Daily documentation done same-day. Weekly summaries closed out the same week, not saved up for the monthly owner meeting. The instant you defer documentation, accuracy starts bleeding out of it.
Who owns what
Diffuse responsibility means nothing gets documented well. Draw the lines clearly:
- Foremen own daily status, progress, and crew counts — they're closest to the work and their record is the ground truth.
- Superintendents own the weekly plan meeting notes, the commitment record, and the weekly summary.
- Project managers own oversight and the quality check — spot-reviewing that the record is complete and honest, not just present.
Mobile entry is what makes this stick. A foreman logging status from their phone at the wall, or a crew leader checking the day's plan from the field, closes the gap between the work and the record. The moment documentation requires walking back to the trailer and opening a laptop, it starts slipping to "later," and later means never.
Subcontractors are half your record
On most commercial jobs the subs do most of the work, so a documentation standard that only covers self-perform is documenting the wrong half. Capture sub commitment and completion status the same way you capture your own. Log coordination issues — the plumber and the electrician both wanting the same chase Tuesday — when they happen, not when they blow up. And keep a thread of sub communication tied to the schedule: when you told them the area was ready, when they said they'd be there, when they actually showed. Those records are exactly what a sub's delay claim will try to rewrite.
Archive, retrieve, and review
Snapshot the schedule at meaningful milestones and at each weekly cycle, and keep those snapshots. A schedule you can't roll back to is a schedule with no memory — you lose the ability to show what the plan was before it changed. Set a retention period that matches your contract and statute-of-limitations exposure (often years past closeout), and store records so they're actually retrievable — the point of keeping them is finding them when the claim lands.
Then close the loop with a quick quality review: is it complete, is it accurate, and is the crew getting feedback on their documentation the way they get it on their work. A five-minute completeness check every week beats discovering the hole eight months later when you need the record and it isn't there.
The habit is the whole game
None of this is complicated. The commitments, the completion status, the reasons for variance, the dated photo, the same-day daily — every piece is simple on its own. What's hard is doing it every week when the job is on fire and documentation feels like the thing you can skip. It isn't. The super who keeps the honest record is the one who knows why the job is really behind, who can defend the schedule when the claim comes, and who hands the next person a job they can actually understand.
Good documentation done today is a problem you don't have to solve tomorrow. Build the standard, keep it simple enough that people actually follow it, and let the tools do the parts they're good at so your crews can stay on the wall instead of buried in the trailer.