FIELD GUIDE / FIELD PLANNING

How to build a useful two-week look-ahead schedule

Translate a project schedule into ready-to-work tasks, constraints, and daily handoffs.

The main point

A look-ahead is useful when it tests whether work can start, not when it simply copies bars from the master schedule.

Pull work from the project plan

Start with the activities expected over the next two weeks, then break them into areas and handoffs the field can recognize. A broad 'install level 3' bar is less useful than areas with access, material, crew, and predecessor status. Keep enough detail to make a decision without turning the look-ahead into a daily timesheet.

The GC's master schedule gives context, but your trade needs its own readiness test. Confirm the sequence with the foreperson who will execute the work.

  • Name the area and deliverable.
  • Identify planned start and finish windows.
  • Connect the task to the milestone it supports.

Check constraints before promising a start

For each task, ask whether drawings are released, material is present, access is available, preceding trades are complete, equipment is booked, and the right crew is assigned. Use simple ready, at risk, and blocked statuses with an owner and due date for each open constraint.

A task with an unresolved predecessor should remain visible, but not as unconditional committed work. This is especially important when a GC requests a look-ahead before area readiness has been confirmed.

  • List each blocker beside the affected work.
  • Assign the party who can clear it.
  • State the last useful date for resolution.

Review daily changes without losing the baseline

At the weekly meeting, agree on the coming sequence. During execution, note actual starts, finishes, and new blockers. A short daily adjustment may change crew assignments without changing the overall milestone; larger shifts should flow back to the project schedule.

Use the next look-ahead to test whether previously blocked tasks are now ready. Repeating a task for three weeks without explaining why is a signal that the constraint process is failing.

  • Keep one owner for the current look-ahead.
  • Record why an activity did not start.
  • Escalate repeated blockers into the main schedule.

Worked example

An electrical crew is scheduled to rough in rooms on Tuesday. Materials and drawings are ready, but the framing inspection has not passed. The look-ahead should flag the rooms as blocked, name the inspection owner, and show another ready area the crew can work in if access is granted.

The project schedule may still show the same completion milestone if the alternate sequence absorbs the delay. If no ready work exists, update the forecast before the week is lost.

  • One blocked area does not always block the whole crew.
  • Alternate work needs its own readiness check.

Measure readiness, not just activity

The most useful look-ahead question is whether a crew can start and continue productively. A task might have drawings and material but still lack access, inspection, or preceding work. Mark the constraint and the date it must clear. A percentage-complete field alone cannot explain that readiness.

Bring the foreperson's feedback into the next weekly plan. Actual productivity may differ from the estimate because of congestion or changed sequence. Update the remaining duration and crew loading rather than copying the same two-week bars forward. If the forecast changes a milestone, carry the adjustment into the main project schedule.

Make the meeting accountable. End with a short list of constraints, owners, and decision dates. At the following review, close or escalate each one. Repeatedly listing the same blocker with no owner makes the look-ahead a status report instead of a planning tool.

Look-ahead checklist

A useful look-ahead is easy to read in a coordination meeting. It should let the GC and your field team see what will happen, what must be cleared, and when a decision is needed.

  • Is each task specific to an area?
  • Are material, drawing, access, and predecessor status known?
  • Is there an owner for each blocker?
  • Does the main schedule reflect any material change?

Common questions

Why two weeks?

It is a practical near-term window, not a universal rule. Use a longer horizon when procurement or access decisions need more lead time.

Should we share blocked work with the GC?

Yes, with the required decision and last useful date, so the shared plan reflects the condition rather than hiding it.

Keep the plan connected.

Milno is being prepared for its first users. It is designed to help subcontractors build schedules around milestones and update linked work as dates change.

Get launch updates