How to Build a Three-Week Lookahead Schedule Superintendents Actually Use
A three-week lookahead breaks the next three weeks of the master schedule into specific activities by area, trade and day, lists the constraints each activity needs cleared (RFIs, submittals, material, predecessor work, inspections, manpower), and assigns who clears them. Build it with sub foremen, update it weekly, and check last week's plan against daily reports so the lookahead reflects what actually happened.
Why lookaheads matter
The master schedule is too coarse for field coordination. The lookahead is where the superintendent turns "Level 2 MEP rough-in, 20 days" into which trade is in which rooms on which days, and what has to happen first. It is the main tool for preventing trade stacking and surprise delays.
What to include
| Column | Example |
|---|---|
| Activity | Level 2 electrical rough-in, rooms 201 to 210 |
| Master schedule ID | 3410 |
| Area | Level 2 east |
| Company | Northline Electric |
| Crew size | 6 |
| Start / finish | Mon wk 1 to Wed wk 2 |
| Constraints | Duct hung in corridor; RFI 118 answered |
| Constraint owner | Summit (duct), architect (RFI) |
| Status | RFI open, duct 60% |
Step by step
1. Pull the next three weeks from the master schedule
List every activity that starts, continues or finishes in the window.
2. Break activities down by area
Split by level, wing, room range or gridline so each line is a week or less of work for one crew.
3. Get input from foremen
Ask each sub foreman for sequence, crew size, and what they need first. Foremen know their constraints better than anyone.
4. List constraints for each activity
Check RFIs, submittals, material lead times, predecessor work, inspections, equipment, access and manpower.
5. Assign constraint owners and due dates
Every constraint gets one owner and a date it must be cleared.
6. Review weekly
At the sub meeting, walk the lookahead: what was done, what slipped, why, and what is next.
Use daily reports to keep it honest
The lookahead is a plan. Daily reports are what happened. Each week:
- Compare planned activities against work performed in the daily reports
- Check planned crew sizes against actual manpower by company
- Carry forward any delay or blocker reported in the field
- Note percent of planned activities completed (a simple measure of plan reliability)
| Week 1 activity | Planned | Actual from dailies | Reason |
|---|---|---|---|
| L2 electrical rough-in 201 to 205 | Complete | Complete | |
| L2 electrical rough-in 206 to 210 | Complete | 60% | Duct conflict room 207, 3 days |
| L2 framing inspection | Thu | Passed Fri | Inspector rescheduled |
| Roof Area B membrane | Complete | 70% | Rain Tue, dry-out Wed |
See construction manpower tracking and weather delay documentation.
Sample lookahead excerpt
| Activity | Company | Wk 1 | Wk 2 | Wk 3 | Constraints |
|---|---|---|---|---|---|
| L2 duct, corridor | Summit | X | Damper submittal approved | ||
| L2 electrical rough-in 206 to 210 | Northline | X | X | Duct complete in corridor | |
| L2 above-ceiling inspection | General contractor | X | Rough-in complete | ||
| L2 ceiling grid | Delta | X | Inspection passed | ||
| Roof Area B membrane | Bayside | X | Weather | ||
| RTU-3 set | Summit | X | Crane booked, curb flashed |
Common mistakes
- Copying the master schedule without breaking it down
- Building it without foremen
- Listing activities but not constraints
- Never checking last week's plan against what happened
- Not tracking who owns each constraint
Related reading
Running the weekly lookahead meeting
A 30-minute weekly meeting with sub foremen keeps the lookahead real:
- Last week (5 minutes): what was planned, what got done, using daily reports. Name the reasons for misses.
- Constraints (10 minutes): walk every open constraint for the next two weeks. Who owns it, and is the date still good?
- Next three weeks (10 minutes): confirm sequence and crew sizes by area. Resolve stacking.
- Commitments (5 minutes): each foreman confirms crew size and areas for next week.
Write down commitments and compare them to next week's daily reports. Over time, the percentage of commitments kept becomes a simple measure of how reliable the plan is.
Planning that starts from the field
Cascade is SMS-first field intelligence for general contractors and subcontractors: superintendents and foremen text in their day, along with their subs, and Cascade builds the daily report, so planned versus actual is visible without digging. Project + schedule planning is part of the scope: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers. Ask "what blocked Level 2 rough-in last week?" and get a plain-English answer.
Subcontractor access is free, and general contractors see 95%+ sub daily report compliance. See why Cascade and SMS daily construction reports. Free onboarding and integration, a one-month pilot on the general contractor plan with no contract lock-in, and a price below Raken, Procore and ACC, guaranteed.
Frequently asked questions
What is a three-week lookahead schedule?
A short-interval schedule covering the next three weeks of work in more detail than the master schedule, broken down by area, trade and day or week, with the constraints that must be cleared before each activity can start.
Who builds the lookahead?
Usually the general contractor superintendent, with input from each subcontractor foreman. It is reviewed and updated weekly, often at the subcontractor coordination meeting.
How often should a lookahead be updated?
Weekly at minimum. Week one should be checked against what actually happened, using daily reports, before rolling the schedule forward.
What is a constraint in a lookahead?
Anything that must be in place for an activity to start: answered RFIs, approved submittals, delivered material, completed predecessor work, inspections, access, equipment and manpower.