Why Four Weeks Is the Number Most Jobs Settle On
Ask ten superintendents what horizon they run their look-ahead on and most of them will land somewhere around four weeks. Not because a textbook told them to, but because they've been burned on both ends. Plan out one week and you're forever reacting — the mason shows up Monday and there's no scaffold, the inspector wants two days notice you didn't give him. Plan out eight weeks in real detail and half of it is fiction by the time you get there, and you've spent your Thursday afternoon maintaining a schedule nobody trusts.
Four weeks is the spot where the work is close enough to be real, but far enough out that you can still do something about it. That's the whole game. A look-ahead isn't a forecast you admire from a distance — it's a to-do list for the near future that you actually intend to execute. The horizon has to be long enough to catch the constraints that take time to clear, and short enough that the plan doesn't rot before you use it.
Give Each Week a Different Job
The mistake I see most often is treating all four weeks the same — same level of detail, same confidence, same expectation that everything holds. It doesn't work that way. The near weeks are commitments; the far weeks are warnings. Run your look-ahead so each week has a distinct purpose:
Week 1 is a promise. Everything in the current week should be de-constrained already — materials on site or confirmed, crew assigned by name, access clear, prior work complete and inspected. If something in week 1 is still a question mark, you have a problem, not a plan. Changes here should be the exception, and when they happen you treat them as a failure to plan ahead, not routine.
Week 2 is final prep. Deliveries confirmed with the supplier, not just ordered. Crews sized to the work. Any coordination between trades in the same area worked out on paper before they're standing on top of each other. Small adjustments still happen, but the shape is set.
Week 3 is where you actually earn your money — make-ready. This is the week you chase constraints. If a long-lead item hasn't been ordered, it's late already. If you need an inspection, you're calling the AHJ now. If there's an open RFI blocking that scope, you're escalating it today, not the morning the crew shows up. Almost everything that goes wrong in week 1 is something nobody handled back in week 3.
Week 4 is early warning. You're not committing to dates here — you're scanning. What's coming? What has a lead time longer than three weeks that needs to move right now? What sequence conflict is visible from here that you can still design around? Week 4 exists so nothing arrives as a surprise.
When you color-code or otherwise visually separate these weeks — which any decent look-ahead scheduling tool lets you do — people read the plan correctly. Full attention on the front two weeks, active chasing in week three, a scan on week four. Without that separation, everyone stares at week four dates like they're gospel and then acts betrayed when the work moves.
The Detail That Actually Helps a Foreman
Detail is only worth having if a foreman can act on it. "HVAC — Building A" tells nobody anything. "Install supply ductwork, Bldg A, Level 3, grids 4–8, 3-man crew, Tue–Thu" is a plan a crew leader can show up and execute against. That's the granularity a four-week window supports and a longer one usually can't sustain.
Get the activity size right and everything downstream gets easier. A useful rule of thumb: size activities so most of them fit inside a single week and no single activity runs more than about ten working days without being broken into pieces. If an activity spans your whole horizon, you can't tell whether it's on track, and you can't hand a discrete piece to a crew. Break "drywall Level 2" into hang, tape, and finish by area, because those are handoffs — different crews, different inspection points, different constraints.
Where the four-week detail pays off:
- Crew loading by name and location. You can see you've got the same three-man crew promised to two areas in week 2 and fix it before the foreman does at 6:45 Monday morning.
- Delivery timing you can verify. Procurement can line up the delivery ticket against the install date and catch the mismatch while there's still time to expedite.
- Trade sequencing on real geography. Location-based planning — this crew on this level, this grid — is where the conflicts actually surface. Time blocks hide overlaps; floor plans expose them.
Trade-Flow Gotchas the Horizon Should Catch
Most schedule blowups aren't one late activity — they're a handoff that nobody buffered. The look-ahead is where you catch these, because you're looking at the actual sequence of trades through a space, not just a bar chart of durations. A few that bite repeatedly:
- Frame-to-rough-in. Leave a day or two between framing complete and the trades starting rough-in — for cleanup, for the framing inspection, and for the layout the MEP crews need. Stacking rough-in on top of framing in the same area the same day is how you get an inspection failure and two trades in each other's way.
- Rough-in to cover. Don't schedule insulation or drywall to close a wall until rough-in inspections have signed off — and until the electrician has meggered the runs and the plumber has held pressure on the lines. Close a wall over an untested run and you're cutting it back open. Build the inspection as its own line item in the look-ahead, not an assumption baked into someone's duration.
- Wet trades and dry-in. Anything involving cure or dry time — slabs, self-leveler, mud-set, paint before flooring — needs its clock shown on the schedule, not carried in someone's head. A one-day float that ignores a three-day cure isn't a float.
- Ceiling grid and the trades above it. Grid can't close until everything above the ceiling is in, inspected, and above-ceiling sign-off is done. That's a hard predecessor that a coarse schedule routinely misses.
Modeling these as explicit trade-flow links — where a downstream activity can't start until its predecessor plus its buffer clears — turns the look-ahead from a wish list into a sequence. A tool built around trade flows will flag the conflict when you drag a date; a spreadsheet just lets you overlap them and find out on site.
Constraints: Four Weeks Is Enough Runway for Most
The reason four weeks works as a default is that it covers the lead time on most constraints — if, and only if, you're actually running make-ready in week three. Rough guides worth internalizing:
- Standard materials usually clear inside four weeks; commodity stuff much faster. The killers are the specialty and long-lead items — switchgear, custom glazing, elevators, some HVAC equipment — that run eight, twelve, twenty weeks out. Those cannot live in your four-week look-ahead. They belong on a separate procurement log, and week 4 is where you confirm the ones landing soon are truly on the way.
- Inspections in most jurisdictions want a day or two of notice, sometimes a week for specialty ones. Four weeks gives you comfortable buffer — the failure is never lead time, it's forgetting to call.
- Labor — your own crews and your subs — can generally be arranged inside four weeks if the sub has visibility. That's the whole argument for sharing the look-ahead with your trades: give them three weeks of notice and they can staff you; give them three days and you get whoever's left.
- Information — RFI answers, submittal approvals, design clarifications — is the sneaky one. These routinely blow past their expected turnaround. Track them like materials, with a needed-by date pegged to the activity they block, and escalate the moment they're at risk.
Run a standing constraint review as activities cross into week 3. Every activity entering the make-ready zone gets asked the same questions: materials, labor, equipment, information, access, prior work, permits and inspections. Anything not green gets an owner and a date. That discipline — not the horizon length — is what actually keeps week 1 clean. The four weeks just gives you the room to do it.
Where It Aligns With How the Business Actually Runs
There's a practical bonus to four weeks that has nothing to do with field execution: it lines up with how most projects report. Billing runs monthly. Owner and OAC meetings run monthly. Progress reports, pay applications, and lender updates all run on roughly the same cycle. When your planning horizon matches your reporting rhythm, the same look-ahead that drives Monday's coordination also feeds the monthly status without a separate exercise. One source of truth instead of two, which means fewer numbers that quietly disagree with each other.
When Four Weeks Is the Wrong Number
Four weeks is a default, not a law. Nudge it when the job tells you to:
- Go shorter — two or three weeks — when the work is genuinely fast and chaotic: heavy demo, tight interiors, a punch-and-turnover phase where activities are one and two days long and the far weeks are pure guesswork. Maintaining four weeks of detail there is effort spent planning fiction.
- Go longer — six weeks — when the sequence is slow and deliberate: structural concrete cycles, curtain wall, heavy MEP infrastructure where activities span weeks and long-lead coordination is the whole ballgame. Just accept that weeks 5 and 6 are coarse and will move, and don't kid your subs that those dates are firm.
The trap on the long end is maintenance burden. Six weeks of fine-grained detail is a lot of activities to keep current, and a look-ahead only earns trust if it's actually maintained. A stale six-week plan is worse than an honest three-week one, because people stop believing any of it. If you're going to extend the horizon, extend the coarse part, not the detailed part.
Making It Roll
The whole thing lives or dies on one habit: the plan has to actually roll forward every week. Same time each week — Thursday afternoon is common, before the next week locks — you capture what got done, drop what completed, pull a fresh week onto the back end, and re-chase the constraints. A look-ahead that doesn't roll is just an old bar chart with optimistic dates.
That weekly cadence is exactly the work LookAheadWall is built to carry: activities placed by location and week, trade-flow links that hold the sequence and its buffers, a horizon you set to fit the job, and a shared view your subs and crew leaders can actually read on their phones. But the tool is the easy part. The four-week look-ahead works because it forces a disciplined weekly conversation about what's real, what's at risk, and what has to happen now so the crew that shows up Monday has everything it needs to do the work. Get that conversation right and the horizon almost takes care of itself.