Two-Week Lookahead: How to Build One Crews Actually Use

A two-week lookahead is a short-range schedule that pulls the next 14 days of work out of your master schedule and breaks it into tasks with names, dates and cleared constraints. ForemanBrief describes it as work split into 1 to 5 day tasks with named owners. You update it weekly, and its real job is to make sure that when a crew shows up, nothing blocks them.

This guide shows what goes on the sheet, how to build it step by step, how to run the Friday meeting, and how to tell whether it’s working. Use it with a spreadsheet today or with scheduling software later.

TL;DR

• A lookahead is a planning tool, not a status report. Its purpose is to remove obstacles before work starts.
• Capture six fields per task: description, dates, responsible party, prerequisites, constraint status and required resources.
• Keep it to one page that a foreman can read in a trailer meeting without scrolling.
• Roll it forward every week: add a new week, drop the finished one, and update the constraint log.
• Track Percent Plan Complete (PPC) to see whether you’re committing only to work that is truly ready.

Table of Contents

• What a two-week lookahead is, and what it is not
• The six fields every task needs
• How to build one, step by step
• Make work ready: the constraint log
• Run the Friday meeting
• Measure it with Percent Plan Complete
• Common mistakes
• Spreadsheet or software?
• Our view: the lookahead is a promise, not a report
• Run your lookahead from your schedule
• FAQ
• Sources

What a two-week lookahead is, and what it is not

Your master schedule shows the whole job. It is built for owners, lenders and project executives. Crews can’t run a day from it, because the activities are too big and the logic is too loose.

The lookahead sits between the two. The Lean Construction Institute’s research describes it as the critical link between the high-level master schedule and daily work, and the point is to clear the path for field crews so they can work without interruption.

The Lean Construction Institute’s standard work defines lookahead planning as the part of the Last Planner System that focuses on making work ready: assuring that work that should be done can be done.

That has a practical consequence. If you spend most of your lookahead time recording what already happened, you have a status report. The same LCI material warns that this is a sign the planning system isn’t protecting your team from variability. A good lookahead looks forward and asks one question for every task: what has to be true for this to start on its date?

Two weeks, three weeks or six

Two weeks is the most common window for detailed field planning because plans stay reliable that far out. Three and four weeks are common too. Lean practice often runs a longer rolling window: LCI’s research describes lookahead planning as preparing tasks for the upcoming six weeks. A practical setup is a six-week window where the first two weeks are detailed, down to the day, and the later weeks are rougher and focused on ordering and approvals.

Pick the window by your longest lead time for clearing a constraint. If an inspection takes 10 working days to book, two weeks is already tight for it. Look further out for those items and keep two weeks for crew assignments.

The six fields every task needs

A lookahead without consistent fields turns into a wish list. LCI’s planner standard work lists six data fields per task, and they make a good minimum:

1. Activity description. Specific and visible: “Rough-in level 2 east corridor, branch conduit,” not “Electrical.”
2. Specific dates. Start and finish, not a vague week.
3. Responsible party. One named foreman or company, not a trade category.
4. Prerequisites. What must finish first, such as a wall inspection or a slab cure.
5. Constraint status. Confirmed, pending or at-risk.
6. Required resources. Labor, materials and equipment.

These six fields come from the LCI standard work document. Add a location column if your site is large. It helps foremen see where trades will collide.

A sample layout

The at-risk row is the most useful one on the page. It’s where your Friday meeting should spend its time.

For a real public example of the format, the D.C. Department of Energy and Environment hosts a sample two-week look-ahead construction schedule for a green infrastructure project in Washington, D.C. It’s a good reference for how a one-page layout reads.

How to build one, step by step

The process below follows the approach in ForemanBrief’s how-to guide, adapted for a general or specialty contractor.

1. Pull the master schedule lines for the next 14 days. Include anything that starts, finishes or is in progress in that window.
2. Walk the site. Compare the schedule to what’s actually built. Update the baseline picture before you plan forward.
3. Break activities into 1 to 5 day tasks. Anything longer than a week is usually hiding several handoffs.
4. Assign a named owner to each task. A company name isn’t an owner. A foreman is.
5. Add the six fields. Prerequisites and resources are where most sheets stay thin.
6. Log the constraints. Each open constraint gets an owner and a due date, earlier than the work date.
7. Review with the trades. Do it with the people who will do the work, not for them.
8. Issue it. Print it, post it and send it, in a form people will read.
9. Track completion. Mark what was done as planned and why anything wasn’t.
10. Roll forward. Repeat next week.

Get the trades in the room

The most common failure isn’t a bad template. LCI research notes that poor communication between main contractor and subcontractors is the biggest barrier to effective lookahead planning. If the GC builds the lookahead alone and emails it, the field treats it as someone else’s document.

Have each foreman say what they can really commit to. If a framing foreman says the level 3 walls won’t be ready until Thursday, change the sheet. Don’t argue with the crew’s read of the site. If you manage many subs, our guides on automated subcontractor coordination and coordinating subcontractors with one platform go deeper on keeping that loop tight.

Make work ready: the constraint log

The most useful thing you can add to a lookahead is a constraint log. It’s a short list of anything that could stop a task from starting: permits, submittals and approvals, late deliveries, incomplete predecessor work, inspections, access, crane time or labor shortfalls.

LCI describes the lookahead as a make-ready exercise in which teams identify and remove constraints before the start date, instead of reacting to delays afterward. A log turns that idea into a habit. Each line has:

• the constraint in plain words,
• the task it blocks,
• one person who owns clearing it,
• a date it must be cleared by, and
• a status you update every week.

The clear-by date matters. If a task starts Wednesday of next week, the delivery confirmation is due this Friday, not Tuesday morning.

Don’t forget tools, equipment and consumables

Constraints aren’t always big items. A crew that arrives and can’t find the right lift, specialty tool, PPE or consumables loses a morning just the same. On sites with many subs sharing equipment, it helps to have a way to know what’s checked out and by whom. Systems built for automated tool and consumables tracking show one approach to that problem, even if you start with a simple sign-out sheet.

Run the Friday meeting

The weekly meeting is where a lookahead earns its keep. Keep it short and structured.

1. Review last week. Which tasks were completed as planned? For each miss, name the cause in a few words.
2. Check the constraint log. Walk the at-risk items first.
3. Roll forward. Drop the completed week and add a new one at the far end.
4. Confirm commitments. Each foreman says yes or no to the next week’s tasks.
5. Issue the new sheet. Same day, same format.

ForemanBrief’s advice on adoption is practical: keep the export readable in a trailer meeting without scrolling, focus on the who and what for the next 14 days, and use the Friday meeting to add a new week and drop the finished one. If your sheet needs a projector and a scroll bar, shrink it.

Measure it with Percent Plan Complete

You can’t improve a lookahead if you don’t measure it. Percent Plan Complete (PPC) is the standard lean metric. LCI defines it as assignments completed divided by total assignments made, times 100.

Here’s an example. Your crews committed to 40 tasks this week and finished 30. Your PPC is 75%.

LCI’s planner standard work says high-performing teams using these methods typically reach PPC between 75% and 90%. Treat that as a reference range, not a promise for your job.

What a low PPC usually means

If PPC is consistently low, you’re probably committing to work that isn’t ready. Check these first:

• Tasks listed without a confirmed prerequisite.
• Constraints with no owner or no clear-by date.
• Commitments taken from the master schedule instead of from the foremen.
• Tasks too large to finish in the period.

The fix is almost never to plan harder. It’s to commit only to what you’ve made ready. Record the reason for each miss, then count them. Within a month you’ll see which causes repeat, such as late deliveries, rework or trade stacking.

Common mistakes

• Treating it as a recap. Spend the time on next week’s constraints.
• No owners. “Trades to coordinate” means nobody will.
• Sheet too long. If it takes more than one page per area, split by area or level.
• Dates without logic. Without prerequisites, the sheet can’t warn you about trade stacking.
• Updating only when something breaks. The weekly rhythm is what builds trust.
• Ignoring labor. A task with no crew assigned isn’t ready. For multi-job crews see our guide to scheduling MEP crews across multiple jobs and commercial construction workforce planning.

Spreadsheet or software?

A spreadsheet is a fine place to start, particularly on one or two jobs. The trouble starts when you run several projects. Dates are retyped from the master schedule, the constraint log lives in a different file and the foremen carry three versions of the sheet.

The benefit of software is that the two-week view is a filter on the master schedule, so a date change shows up in both places. If you’re weighing the move, our piece on cutting manual scheduling work covers what to automate first.

Our view: the lookahead is a promise, not a report

We build construction software, and we see the same pattern in contractors who come to us from spreadsheets. The lookahead exists, but it’s a copy of the master schedule with the dates trimmed. Nobody owns the constraints, so the foreman finds out about a missing submittal on the morning the crew is supposed to start.

Our position is simple. The lookahead should sit in the same system as your schedule, your job costs and your field updates, so that a delay in one place shows up everywhere. When schedule, accounting and field data are separate, someone ends up retyping, and the retyped version is always a week behind.

That’s why we designed DesignFlow Build as one platform covering project management, accounting and field operations, with an integrated scheduler. We want the weekly meeting to be about clearing blockers, not about assembling the sheet.

The human part still matters most. No tool replaces a foreman who says “I can’t start Wednesday.” Build the habit first, then let software carry the bookkeeping.

— Keith

Run your lookahead from your schedule

If you’re tired of rebuilding the two-week view by hand, take a look at our construction scheduling software. Field crews can update progress from the mobile field app, so what happened on site reaches the schedule without re-entry. Pricing is published on the pricing page: Pro is $100 per month per office user, and Field seats are $25 per month per user. There is also a free tier, so you can start free and see how it fits your jobs.

Not sure what a term means? The construction software glossary explains scheduling and ERP vocabulary in plain words.

FAQ

What is the format for a two-week look-ahead schedule?

Use one page with a row per task and columns for description, start and finish dates, owner, prerequisites, constraint status and resources. Group rows by area or trade so foremen find their work fast. Add a short constraint log under or beside it.

What is a two-week rolling schedule?

It’s a lookahead that moves forward each week. At the weekly meeting, you remove the completed week, add a new one at the end and update the open constraints. The window always shows the next 14 days.

How is a lookahead different from the master schedule?

The master schedule covers the whole project at a high level. The lookahead takes the next few weeks and turns them into assignable tasks with named owners and cleared constraints. It’s the link between the two, as LCI research describes.

What is a three-week lookahead?

It’s the same tool with a longer window. Teams choose three, four or six weeks when constraints take longer to clear, such as long inspection lead times or deliveries. The nearest two weeks stay detailed, and the later weeks are rougher.

How often should I update it?

Weekly at minimum, ideally at a fixed meeting such as Friday. Update it sooner if a major constraint changes. Consistency matters more than frequency, because crews stop reading a sheet that is often out of date.

Sources

• Last Planner System Standard Work, Lookahead Planning (Lean Construction Institute)
• Health-Check Framework for Assessing Last Planner System Implementation (Lean Construction Journal)
• Lean Construction Journal, PPC and short-term planning research
• How to Build a Two-Week Look-Ahead Schedule (ForemanBrief)
• Creating a Two-Week Look-Ahead Schedule: A How-To Guide (ForemanBrief)
• Example Two-Week Look Ahead (D.C. Department of Energy and Environment)

Recommended

• 90 Day Playbook to Achieve Real Time Project Visibility
• Resource Leveling With Live Crew Data for Construction
• Cut Manual Scheduling Work 70%: Construction Project
• Schedule MEP Crews Across Multiple Jobs: Contractor’s Guide