The 3-Week Lookahead Schedule: How to Build One That Works

What Is a Lookahead Schedule and Why Do You Need One?

A lookahead schedule is a short-term planning tool that extracts a rolling window of work—typically 3 weeks—from the master project schedule. Unlike the master schedule, which may contain hundreds of activities and is updated monthly, the lookahead focuses on what the field crews will actually do in the near future. It bridges the gap between high-level planning and day-to-day execution.

Field teams often ignore the master schedule because it feels abstract or outdated. A well-built lookahead, however, shows only the next few weeks of tasks, with clear assignments and ready resources. It answers the question: “What are we doing next Monday?” This makes it the single most useful schedule for foremen, superintendents, and trade partners.

Pulling the Right Window from Primavera P6

Building a lookahead starts in Primavera P6. Here’s a step-by-step method to extract a clean 3-week window:

• Set the data date. Ensure your project schedule has a current data date (usually today or the last working day). All activities with a start date before the data date should be statused.
• Apply a filter. Create a filter that shows only activities with an early start or early finish within the next 21 calendar days. Include activities that are already in progress.
• Remove non-field tasks. Exclude procurement, submittals, and long-lead items that don’t require daily field attention. Keep only construction, installation, and testing activities.
• Sort by early start. Order the activities chronologically so the crew sees what comes first.
• Export or print. Use P6’s layout or report features to produce a simple table. Columns should include: Activity ID, Description, Early Start, Early Finish, Duration, and Responsible Resource.

If you don’t have P6 access or want to verify your export, you can use Project Assure—a free browser tool that parses XER files locally. It can help you check that your lookahead window aligns with the master schedule’s logic.

Keeping It Tied to the Master Schedule

The lookahead must remain a subset of the master schedule, not a separate plan. If you allow the lookahead to drift, you’ll end up with two schedules that disagree. Here’s how to maintain alignment:

• Update the master first. Always status the master schedule before generating the lookahead. This ensures that completed work, delays, and logic changes flow into the short-term plan.
• Use the same activity IDs. Never rename activities in the lookahead. The foreman’s daily list should reference the same IDs that appear in P6.
• Flag constraints. If a lookahead activity has a date constraint (e.g., “Start No Earlier Than”), note it. Constraints in the master schedule often cause confusion in the field.
• Review weekly. Hold a 30-minute lookahead meeting every week. Compare the upcoming week’s activities against the master schedule. If the lookahead shows work that isn’t in the master, investigate.

Common Lookahead Mistakes (and How to Fix Them)

Even experienced schedulers make errors when building lookaheads. Here are the most frequent pitfalls:

Making the Lookahead Actionable

A lookahead is only valuable if it drives action. Here are three tips to make it stick:

• Print it. Post a physical copy in the site trailer. Digital versions get buried in email.
• Assign a “lookahead champion.” One person (often the project engineer) owns the weekly update and meeting.
• Track commitments. During the lookahead meeting, ask each foreman: “Can you start this activity on Tuesday?” If not, update the master schedule immediately.

By following these steps, your 3-week lookahead will become the go-to tool for daily coordination—keeping field work aligned with the master plan without overwhelming the crew.