The master schedule tells you where the job is supposed to be in eight months. It does not tell your framing lead what to hang on Tuesday. That gap — between the big Gantt chart on the trailer wall and the actual work that happens between Monday and Friday — is where jobs quietly bleed out. The weekly work plan is the bridge across that gap, and building one well is a learnable skill, not a personality trait. This is how to stand the process up on a real job without it turning into another meeting nobody respects.
What a Weekly Work Plan Actually Is
A weekly work plan is a short list of the specific tasks each crew has committed to complete in the coming week, in a specific location, with the constraints already cleared. That last part is the whole ballgame. Anyone can write down "drywall building B." A weekly work plan says "hang and tape units 201–210, second floor B, Wednesday through Friday, five-man crew, material staged Tuesday, ceiling inspection signed off Monday." The difference between those two sentences is the difference between a wish and a plan.
The weekly plan is fed by your look-ahead — the three, four, or six-week rolling view that everyone in the trailer keeps talking about. The look-ahead's job is to see problems early and make work ready. The weekly plan's job is narrower and harder: take the work that is actually ready right now and get real commitments against it. Think of the look-ahead as the funnel and the weekly plan as the last inch of the spout. Only make-ready work should ever make it into the week.
Set the Rhythm First, Before You Touch the Content
The single most common reason weekly planning dies is inconsistency. If the meeting floats around the calendar, the trades stop preparing for it, and within a month you are back to firefighting. Pick a day and a time and defend it like a punch date.
Most superintendents I trust run it like this:
- Thursday or Friday afternoon — the planning meeting where next week's commitments get made. Late in the week works because the trades already know how their current week landed, so their promises are grounded in reality.
- Monday morning, fifteen minutes — a short confirmation huddle. Weather changed over the weekend, a delivery slipped, someone's key guy called out. You adjust before boots hit the ground, not at 10 a.m. when the damage is done.
- Daily, five minutes at the gang box — each foreman translates the week's commitment into today's tasks with their own crew.
Keep the main meeting to 30–45 minutes. If it runs an hour, you are re-planning the master schedule in the room, and that is a different meeting. The weekly plan meeting is for commitments, not debate about the project logic.
Run the Meeting Around Commitments, Not Status
Here is the shift that separates a real weekly planning process from a glorified status update. You are not going around the table asking "how's it going?" You are asking each trade lead a much sharper question: "What will you complete next week, and is anything standing in your way?"
A commitment is a promise between two people, made out loud, in front of the other trades. That social weight is the point. When the plumbing foreman says "I'll have the underground roughed and tested in grid C by Wednesday" in front of the concrete crew who's pouring Thursday, that promise means something. It also flushes out the truth: if he can't commit, you want to know why on Friday, not on Thursday morning with a pump truck idling.
Before you let a task onto the plan, run it through a simple make-ready screen. The task only earns a spot if every one of these is a yes:
- Prior work complete — the trade before them is actually done in that location, not "mostly done."
- Materials on site — staged and counted, not "on the truck somewhere."
- Information clear — no open RFI, no pending change, latest drawings in hand.
- Crew and equipment available — the manpower exists and the lift/pump/scaffold is booked.
- Space and access — the area is physically available and not blocked by another trade's laydown.
- Inspections lined up — anything that needs a sign-off before they can proceed is scheduled.
Any "no" on that list means the task is not ready. Don't schedule it. Instead, capture the blocker as a constraint with a name and a date attached — "get the fire-caulk inspection scheduled, Ramon, by Tuesday." Unowned constraints are just complaints. Owned constraints get cleared.
Sequence and Buffer Like You Mean It
Selecting the week's work is where a superintendent's trade-flow instinct earns its keep, because the plan lives or dies on handoffs between crews. A few hard-won rules of thumb for the buffers between trades:
- Frame to rough-in: leave a 1–2 day buffer for cleanup, layout verification, and the framing inspection before mechanical, electrical, and plumbing start opening walls. Send the rough-in crews in on top of a framing inspection that hasn't passed and you'll be tearing work back out.
- Rough-in to insulation/cover: do not close a wall until the runs are proven. Megger the electrical, pressure-test the plumbing, and get the rough inspections signed. Drywall over an untested line is the most expensive shortcut on the job.
- MEP overhead coordination: in a tight ceiling, sequence the big stuff first — main duct, then large-diameter waste and storm, then sprinkler mains, then conduit and branch work that can weave around them. Reverse that order and someone's re-hanging their work.
- Concrete and wet trades: respect cure and set times as real durations, not soft ones. A slab you poured Thursday afternoon is not a work surface Friday morning. Build the wait into the plan instead of pretending it away.
Don't load the week to 100 percent. Crews that are planned bumper-to-bumper have nowhere to go when one handoff slips, and one always slips. Plan the committed work to roughly 80–85 percent of available capacity and keep a short list of ready backlog tasks — work that's fully make-ready but not date-critical. When a crew gets rained out of their primary task or finishes early, they pull from the backlog instead of standing around or, worse, going home. That backlog is your shock absorber.
Assign Resources to Locations, Not Just Tasks
The plan isn't done when you know what happens; it's done when you know who is where. Two trades unknowingly assigned to the same corridor on the same afternoon is the classic collision, and it's completely avoidable if the plan is location-based. This is exactly where a visual, location-driven look-ahead tool pulls its weight — laying the week out by area and by trade flow makes those overlaps jump off the screen before they happen on the floor. LookAheadWall was built around that idea, and its mobile companion means the framing lead sees his committed week on his phone at the gang box instead of relying on a photo of a whiteboard from last Tuesday. But the discipline matters more than any tool: if you're still drawing the plan on a marker board, at least draw it by location.
Measure What Got Done — and Why It Didn't
A weekly planning process without measurement is just optimism on a schedule. The number that matters is your completion rate: of the tasks the crews committed to this week, what percentage actually got done, in full, as promised? If a task was 90 percent complete, it counts as zero — partial credit teaches crews to over-promise. Most jobs start somewhere in the 50s and climb toward the 80s as the process matures. Getting into the high 80s consistently is genuinely good performance.
But the raw percentage is the boring half. The gold is in the reasons for the misses. Every task that didn't get done, you ask one question: why? Then you tally the reasons over time:
- Prerequisite work wasn't finished
- Material or equipment showed up late or not at all
- Design/RFI wasn't answered
- Crew got pulled to another job or called out
- Weather
- Plan was simply unrealistic to begin with
Do this for a month and a pattern emerges that no gut feeling would have shown you. When you notice that a third of your misses trace back to one supplier's late deliveries, you've found something worth fixing — and now you have the receipts to have that conversation. Chasing reasons is how the process gets smarter instead of just older.
The First Six Weeks Are the Hard Part
Be honest with yourself about the rollout. The first few weekly meetings will feel clumsy. Trades will over-commit to look good, then miss, and you'll have to reset expectations without turning it into a blame session — the moment the meeting becomes a place to get chewed out, people stop telling you the truth, and honest commitments are the entire value of the exercise. Protect that.
Start small if you have to. Run the process with your two or three most reliable trades first and let the others watch it work. When the drywall crew stops getting blindsided because the ceiling grid actually got inspected on time, word travels. A few things that keep the wheels on early:
- Same day, same time, no exceptions — protect the rhythm above everything else.
- One page, not twenty — the plan a foreman can't read in two minutes is a plan he won't use.
- Track reasons from week one — even a hand-tallied list beats no data, and you'll want the trend early.
- Close constraints out loud — start each meeting by reporting which of last week's blockers got cleared. It proves the process does something.
None of this is complicated, which is exactly why it gets skipped. The superintendents who run tight jobs aren't smarter than everyone else — they've just decided that a promise made on Friday is worth more than a schedule printed in January. Build the weekly plan, defend the rhythm, chase the reasons, and the job starts telling you what it needs before it becomes a problem instead of after. That's the whole trick.