The Plan You Can Actually Keep
I spent years running monthly field plans because that's how I was taught. Print the 30-day at the Monday-after-the-first meeting, hand it out, and refer back to it exactly never. By week three the paper on the trailer wall described a jobsite that no longer existed. We were running the job off phone calls and the last conversation in the gang box, and the schedule was a museum piece.
The switch to a rolling three-week lookahead wasn't some methodology I read about. It was surrender. The monthly plan kept lying to me, so I stopped asking it to see that far. Three weeks is the honest horizon — far enough out to actually get material and manpower moving, close enough that the prediction still holds by the time you get there. This is the case for why a three-week look-ahead beats a monthly field plan, in the terms that matter on a jobsite.
Uncertainty Compounds — Detail Past Three Weeks Is Fiction
Every activity you schedule carries a little uncertainty. The delivery slips a day. The inspector reschedules. The trade ahead of you runs two days long. Those errors don't just sit there — they stack and multiply the further out you look.
Think about it in terms of the trade in front of you. If framing is running at roughly 85% reliable day to day — and 85% is a good crew — then the activity that depends on framing four handoffs downstream is only landing where you drew it maybe half the time. Draw that same chain out across a full month and you're writing detailed start dates for work that has a coin-flip's chance of happening when the paper says. You're not planning at that point. You're doing arts and crafts.
Three weeks is where the math still works in your favor. You can name the crew, name the area, name the constraint, and be right often enough that people believe the paper. Spend your planning energy inside that window and stop pretending you can sequence day-by-day work five weeks out.
Make-Ready: The Real Reason It's Three Weeks and Not Two
The three-week window isn't arbitrary, and it isn't just about accuracy. It's sized to make-ready — the lead time it takes to knock the constraints off an activity so it's genuinely ready to run.
Walk the constraints on any activity and you'll see why:
- Material. Stocked items, a few days. But specialty items — dampers, custom glazing, switchgear, anything with a submittal in front of it — you want two to three weeks of runway to catch a "that's not what we approved" before it's a schedule hit, not after.
- Manpower. Your subs staff off your look-ahead. Give a sub three weeks of visibility and they can pull two more guys off another job. Give them three days and you get whoever's on the bench, if anyone.
- Prerequisite work. The trade ahead has to finish and, usually, get inspected. That handoff is where schedules die.
- Information. The open RFI, the pending ASI, the detail nobody's answered. Two to three weeks is roughly how long it takes to run an RFI to ground on most jobs.
- Access and equipment. The lift, the crane pick, the area cleared and dried in.
Most of those constraints clear inside three weeks if you start working them now. That's the whole point of the window: it's a make-ready staging area. Work enters the far edge with a list of what's not ready, and every week you knock items off until an activity is clean enough to commit to. Monthly planning has no equivalent to this — the first of the month arrives and work drops into the "should be running now" zone whether anyone did the make-ready or not. Then you're standing in front of a crew with no material and a pending inspection, apologizing.
Update Frequency: A Monthly Plan Is Wrong 75% of the Time
Here's the part nobody says out loud. A monthly plan is roughly current for about the first week after you publish it. After that, actual progress drifts from the drawn plan and the gap only widens. By week three you're referencing a document that's mostly wrong, and everyone on site knows it, so nobody references it.
The three-week look-ahead lives on a weekly heartbeat. Every week you slide the window forward one, drop the week that just finished, and pull a fresh week onto the back. The plan never gets more than seven days stale before it's refreshed against reality. That's the difference between a schedule people trust and a schedule people ignore.
Weekly updates are also where the tooling earns its keep. Doing this on a whiteboard or a spreadsheet is real work — re-drawing sticky notes, re-keying dates, chasing subs for status. This is exactly what a look-ahead app is for: you slide the window, drag the activities that moved, and the trades see the current plan on their phones the same afternoon instead of waiting for the next printout. LookAheadWall is built around that weekly slide, but the discipline matters more than any particular tool — the point is that the refresh has to be cheap enough that you'll actually do it every week.
Commitment Feels Different at Three Weeks
There's a psychology to this that's easy to dismiss until you've watched it work. When a foreman commits to finishing an area "in the next two weeks," that commitment has weight. He can picture the work, count his guys, see the constraints. He'll defend that date because he made it with his eyes open.
Ask that same foreman what he's doing on the 24th, three weeks and change out, and you get a shrug and a maybe. It's too far to feel real. Monthly commitments are soft commitments — plenty of runway for things to change, plenty of room to defer the decision. And soft commitments don't get defended. The look-ahead horizon sits right at the edge where a commitment still feels binding.
The Coordination Meeting Gets Shorter and Sharper
Run your weekly coordination meeting off a three-week board and it more or less runs itself. Three columns, three passes:
- This week — confirm what's committed and hunt for anything that's going sideways in the next five days.
- Next week — this is the money column. Every activity here should be in active make-ready. Walk the constraints out loud: material in? Inspection lined up? Prior trade actually going to finish? Anything still open is somebody's action item before the next meeting.
- Third week — a preview. You're not committing here, you're flagging the long-lead constraints so they don't ambush you.
Try to run that same meeting off a 30-day plan and it turns to soup. Discussion wanders across a month, the critical detail for next Tuesday gets buried under a debate about work three weeks out, and everybody leaves tired without leaving with a to-do. Twenty minutes on a focused three-week board beats an hour on a monthly plan every time.
Trade Partners Can Smell a Schedule That Lies
Your subs run multiple jobs. They have a finely tuned instinct for which GCs' schedules are worth staffing off of and which are fairy tales. A look-ahead that's consistently right trains them: when the board says drywall starts the 15th, drywall starts the 15th. Once they believe that, they'll pull manpower to you and hit your dates, because your dates have earned it.
A schedule that changes every time they look at it teaches the opposite lesson. They learn to ignore the paper and wait for the phone call that tells them what's really happening. The moment your subs are managing your job by text instead of by your schedule, the schedule is dead — it's become paperwork. Reliability is the whole currency here, and short-horizon planning is how you earn it.
It Adapts at the Speed of the Job
Jobs change. A rain week wipes out exterior work, an owner change flips a sequence, a bad soils condition stops the excavator. The question is how fast your plan can absorb the hit. A three-week look-ahead re-plans in an afternoon — you fix the affected activities, re-sequence what's downstream, push the new window, and the trades have the recovery plan the same day.
A monthly plan just sits there and stays wrong until the next monthly cycle. In the gap between the change and the next official update, the "real" plan lives in your head and a handful of texts, and everybody's working off a different version of the truth.
Faster Feedback, Faster Improvement
The weekly rhythm gives you a scoreboard. At each meeting, count what you committed to last week against what actually got done — that's your Percent Plan Complete, PPC. Most crews start somewhere in the 50s when they first measure it honestly, which is a gut-punch the first time, and climb toward the 80s as the planning tightens up.
The real value isn't the number — it's the second question. For every commitment that missed, ask why. Log the reasons: waiting on material, waiting on the trade ahead, waiting on an RFI, weather, changed our mind, ran out of crew. After a month those reason codes stop being random. You'll see the same two or three causes eating your reliability, and now you can fix the actual disease instead of firefighting symptoms. A weekly cycle gives you fifty-some of those learning loops a year. Monthly planning gives you twelve. That gap is why short-interval teams pull ahead.
Handling the "It's More Work" Objection
Somebody always says weekly planning is more overhead than monthly. More meetings, more updates, more fuss. And on paper the up-front hours look higher, sure.
But that comparison ignores the cost of a wrong plan, which never shows up on a timesheet as "scheduling." It shows up as the crew that mobilized to an area that wasn't ready and stood around, the second trip because the material wasn't staged, the trade stacked on top of another trade because nobody sequenced the handoff, the weekend acceleration to recover a slip you'd have caught three weeks earlier. That chaos costs multiples of what a weekly update costs. You're not choosing between more work and less work — you're choosing between a couple of planned hours a week and a whole lot of unplanned firefighting.
Where the Monthly and Master Views Still Belong
None of this means you throw out the long view. You absolutely still need the master schedule and the milestone plan — for procurement lead times, for phase logic, for the owner's dates and the loan draws. Long-lead items live on the master and get ordered off it months out. That's the right tool for that horizon.
The mistake is trying to run daily field coordination off that long-range plan. The master tells you where the job is going; the three-week look-ahead tells you what your crews touch tomorrow. Keep both, and keep them connected — the look-ahead should pull its context from the master so you're never planning near-term work that quietly contradicts a milestone. Good scheduling software should let you hold both altitudes at once without confusing which one governs which decision. Just be clear which layer you're standing on when you make a call.
How to Make the Switch Without Blowing Up Your Process
You don't need a clean break. Start next Monday:
- Keep your master and monthly plan exactly as they are for the big picture.
- Filter or pull just the next three weeks of field activity into its own view. That's your look-ahead — you already have the data, you're just cropping it.
- Put a weekly meeting on the calendar. Run the three-column pass above. Twenty minutes, standing up.
- Every week, slide the window forward one and score last week's PPC. Write down the miss reasons.
Give it a month. What happens is quiet but unmistakable: your subs stop calling to ask what's really going on and start showing up to the board. The surprises thin out. The Friday panic gets rarer. Somewhere around week six you'll realize you haven't looked at the monthly plan for field decisions in a while — and you won't miss it. That's the whole argument, and it's not really an argument once you've felt it. Plan the horizon you can actually keep, keep it honestly every week, and the job stops running you.