Esc

↑↓ move↵ openIndex · Pagefind

How to build a three-week look-ahead schedule the field will actually use

The master schedule says what has to happen. The three-week look-ahead says who does it, where, and what has to be cleared first. Here is how to pull it from the master, break it down to crew level, screen every activity for constraints, get commitments from the trades, and roll it forward each week, with a worked example.

Charley Forey6 min readScheduleProject managementField
On this page
  1. Step 1: Start from the current master schedule
  2. Step 2: Pull the activities in the window
  3. Step 3: Break each one down to how the field plans
  4. Step 4: Screen every activity for constraints
  5. Step 5: Give every constraint an owner and a date
  6. Step 6: Review it with the trades and get commitments
  7. Step 7: Track what got done and why the rest didn’t
  8. Step 8: Roll forward and feed the master
  9. Worked example: one week’s look-ahead
  10. Common mistakes
  11. How os.construction handles it
  12. FAQ

To build a three-week look-ahead, take every activity from the current master schedule that starts, runs or finishes in the next three weeks, break each one down by area, crew and day, list the constraints that must be cleared before it can start, give each constraint an owner and a date, and review it with the trade foremen every week. Roll it forward one week at a time and send anything that slipped back to the scheduler.

A look-ahead schedule is where the team checks that the plan can actually happen. Most delays are visible three weeks out as constraints: a submittal not approved, a delivery not confirmed, an RFI still open, an inspection not booked. The look-ahead’s job is to find those while there’s still time to clear them. The free three-week look-ahead template has the columns used below.

Step 1: Start from the current master schedule

Use the master schedule as of its latest update, and note its data date on the look-ahead. A look-ahead pulled from a schedule that hasn’t been updated in a month is planning against a plan nobody is following. If the master is stale, update it first or at least mark what has changed since.

Step 2: Pull the activities in the window

Take every activity that starts, is in progress, or finishes in the next three weeks. Include the ones already late: they still need a place in the plan. Note which are on or near the critical path or have little float, so the team knows which slips matter most.

Step 3: Break each one down to how the field plans

A master schedule activity like “L2 interior framing, 15 days” is too coarse to staff. Break it into the pieces a foreman plans: by area, by crew, by day or week. “L2 east framing, crew of 8, weeks 1–2; L2 west, weeks 2–3.” Add the field activities the master doesn’t show but the work depends on: inspections, deliveries, crane picks, shutdowns, layout.

Step 4: Screen every activity for constraints

For each line, ask what must be true before the crew can start, and write it down. The usual list:

  • Information: RFIs answered, drawings current.
  • Approvals: submittals approved.
  • Materials: on site or delivery confirmed.
  • Inspections: booked and, for preceding work, passed.
  • Preceding work: the previous trade finished and out of the area.
  • Labor and equipment: crew size available, lifts and cranes booked.
  • Permits and access: permits issued, areas released, shutdowns scheduled.

An activity with no constraints listed hasn’t been screened yet. “None” is a valid answer, but it should be a deliberate one.

Step 5: Give every constraint an owner and a date

Each open constraint gets one person responsible for clearing it and a date by which it must be cleared, set from the activity’s start. An RFI needed for week 2 work needs an answer by the end of week 1. Put the constraint in the RFI or submittal log as well, so it’s tracked where the people answering it look.

Step 6: Review it with the trades and get commitments

Go through the look-ahead with the foremen every week, usually in the trade coordination meeting. For week 1, each foreman commits to what their crew will finish, and only to work whose constraints are clear. Work that isn’t ready stays in the look-ahead but off the commitment list. This is the core idea of the Last Planner System: commit only to work that is ready.

Step 7: Track what got done and why the rest didn’t

At the end of the week, mark each commitment met or missed. Percent plan complete (PPC) is commitments met divided by commitments made. For every miss, record a reason: material, information, inspection, preceding work, labor, weather. Over a few weeks the reasons tell you which constraints to screen harder.

Step 8: Roll forward and feed the master

Drop the finished week, add a new week 3, and repeat. Anything that slipped in the look-ahead goes back to the scheduler so the master schedule is updated. A look-ahead that drifts away from the master leaves the owner and the field looking at two different jobs.

A three-week look-ahead window with constraintsThree weekly columns. L2 east framing runs in weeks 1 and 2 with no constraints. L2 east MEP rough-in runs in weeks 2 and 3 and has two constraints, an RFI answer and a damper delivery, that must clear by the end of week 1. Area C slab pour is in week 2 and needs a pre-pour inspection. Each week the window rolls forward one week.WEEK 1WEEK 2WEEK 3L2 EAST FRAMINGL2 EAST MEP ROUGHAREA C SLAB POURRFI + DAMPERS BY END WK 1PRE-POUR INSPECTIONEACH WEEK: DROP WEEK 1, ADD A NEW WEEK 3
Each constraint is due before the work it holds up is due to start. Illustrative.

Worked example: one week’s look-ahead

Illustrative exampleA made-up two-storey building. The master schedule shows “L2 interior framing”, “L2 MEP rough-in” and “L1 slab-on-grade, area C” in the next three weeks.
Activity Area Crew Wk 1 Wk 2 Wk 3 Constraints Owner, clear by Status
Interior framing L2 east Framing (8) X X None Ready
Interior framing L2 west Framing (8) X X L2 west deck cleared of stored material GC super, end wk 1 Ready by wk 2
MEP rough-in L2 east Mech, elec, plumb X X RFI-147 answer; fire damper delivery PM (RFI), mech PM (delivery), end wk 1 At risk
Slab-on-grade pour L1 area C Concrete (6) X Under-slab plumbing inspection; pre-pour inspection booked Plumbing foreman; GC super At risk
Drywall delivery L2 Supplier X Hoist booked; L2 east framing complete GC super Ready
Above-ceiling inspection L1 Inspector X L1 MEP rough-in complete GC super On track

The two “at risk” lines are the useful output. MEP rough-in on L2 east can’t start in week 2 unless RFI-147 is answered and the dampers arrive during week 1, so both go on the OAC agenda and the mechanical sub is asked for a confirmed delivery date today. The slab pour needs an inspection of the under-slab plumbing before the pre-pour inspection can even be booked.

At the weekly meeting the foremen commit to week 1: 12 commitments, all on work whose constraints are clear. At the end of the week, 9 were met:

PPC = 9 met ÷ 12 committed = 75%

The three misses: two because an inspection was rescheduled by the inspector, one because the electrical crew was short two people. Next week the superintendent books inspections a day earlier and asks the electrical foreman to confirm crew size at the meeting. Then the window rolls forward: week 1 drops off, a new week 3 is added from the master, and the L2 west framing that slipped a day goes back to the scheduler.

Common mistakes

  • Copying the master schedule. A look-ahead with the same activities and no constraints adds nothing.
  • Planning without the foremen. They know what their crews can do; the super’s guess doesn’t commit anyone.
  • Committing work that isn’t ready. Missed commitments become normal, and PPC stops meaning anything.
  • Constraints with no owner or date. They get noticed the morning the crew shows up.
  • Not rolling forward weekly. A look-ahead that’s two weeks old is out of date.
  • Not feeding slips back. The master and the look-ahead drift into two different jobs.

For the master schedule itself, the construction schedule (Gantt) template is a free Excel starting point.

How os.construction handles it

The Schedule tool can show an imported Primavera P6 or Microsoft Project schedule as a 3-week look-ahead, grouped into This Week, Next Week and Week After and flagged Overdue or At Risk, and submittals can be linked to the activities they feed. On the scheduling side, the Lookahead page lists activities with linked submittals, deliveries, RFIs and inspections as constraints, holds a weekly work plan of trade commitments, and reports PPC by week and by trade with reasons for misses (Last Planner). The three-week look-ahead walkthrough shows a weekly review, and construction scheduling software covers what to look for in any scheduling tool.

FAQ

What is a three-week look-ahead schedule?

A short-range schedule pulled from the master schedule that shows the next three weeks of work in enough detail for the field to plan crews, deliveries and inspections: each activity broken down by area and crew, with the constraints that must be cleared before it can start.

Who prepares the three-week look-ahead?

Usually the superintendent, working from the scheduler's current master schedule and with the trade foremen, who know what their crews can actually do. It's reviewed and updated every week, often in a trade coordination meeting.

What are constraints in a look-ahead schedule?

Anything that has to be true before an activity can start: an answered RFI, an approved submittal, material on site, a passed inspection, equipment available, a permit, labor available, and the preceding work finished and out of the way.

How is a look-ahead different from the master schedule?

The master schedule covers the whole job, usually at activity level with logic, and is often a contract document. The look-ahead covers the next few weeks at the level the field plans, by area, crew and day. The look-ahead should agree with the master; when it can't, the slip goes back to the scheduler.

Why three weeks?

It's long enough to see and clear most constraints, such as an RFI answer, a delivery or an inspection booking, and short enough to plan in detail. Some teams use two, four or six weeks, especially when lead times are long. The window matters less than reviewing it every week.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file