TL;DR

Buying for a business?Offer from Amazon

Get business pricing on tools and workshop supplies

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

A two-week look-ahead schedule translates your master schedule into specific, assignable tasks for the next 14 days, with locations, owners, dates, and completion measures. The process works in ten steps: review the master schedule, walk the work areas, break activities into field-level tasks, confirm dependencies, run a constraint check, validate resources with trade partners, secure commitments, publish a readable schedule, review it in a coordination meeting, and track results weekly using Percent Plan Complete (PPC).

Your master schedule says “electrical rough-in, Levels 1–3” starts Monday. That tells your electricians almost nothing. Where? Which rooms? Is the conduit on site? Did the framing inspection clear? A two-week look-ahead schedule answers those questions before Monday morning, and it’s the difference between crews working and crews standing around waiting on answers.

A two-week look-ahead is a short-term production control tool that converts the master schedule into field-level tasks for the next 14 days. It coordinates crews, materials, equipment, inspections, and trade handoffs — and it surfaces problems while you can still fix them.

This guide walks you through the full process: what to include, how to run the constraint check, how to structure the document, and how to measure whether your plan is actually reliable. No theory. Just what works on a real jobsite.

What a Two-Week Look-Ahead Actually Does (And What It Doesn’t)

A two-week look-ahead schedule is a rolling, 14-day plan that turns your master schedule into tasks a foreman can assign on a Monday morning. It does not replace your contract schedule, your baseline, or your critical-path analysis. Those documents answer “what must happen and when for the project to finish on time.” The look-ahead answers “what exactly gets built next week, by whom, with what materials, in which rooms.”

Think of it like this: the master schedule is the road map for a cross-country trip. The look-ahead is the turn-by-turn directions for the next hundred miles. Both matter. One gets you through Tuesday.

The window is rolling. When one week ends, you add another week at the far end, so you’re always looking 14 days ahead. Many teams split the two weeks into two distinct categories:

• Week 1: committed work — tasks that are ready, resourced, and promised
• Week 2: preparation work — tasks coming up that still need confirmation, deliveries, or approvals

Some projects use three-to-six-week look-aheads for longer lead coordination. Even then, the first two weeks remain the commitment window. ForemanBrief’s guidance is consistent here: the look-ahead exists for production control and near-term coordination, not for reporting to the owner.

A quick example. On a mid-size office tenant fit-out, the master schedule shows “drywall rough-in complete” as a single line. The look-ahead breaks that into: install conduit in Level 2 east corridor, pull feeders from Panel A to the mechanical room, and obtain above-ceiling inspection for Rooms 201–215. Each task has a location, an owner, a date, and a finish line you can verify by walking the space.

The 10 Steps That Build a Look-Ahead You Can Trust

Here is the process, start to finish. Run it every week and it becomes routine — an hour or two of planning that saves days of lost production.

1. Review the current project schedule. Pull the activities, predecessors, and milestones falling in the next 14 days. Use the latest approved update, not the baseline you got at kickoff.
2. Walk the work areas. Compare the plan to what’s actually built. Is the predecessor work really done? Is the area accessible? A schedule that ignores reality is a wish list.
3. Break activities into field-level tasks. Split master-schedule lines into work a crew can finish and verify within one to several shifts. Organize by area, floor, zone, or system.
4. Confirm dependencies. For every task, list what must happen first — construction predecessors plus admin items like permits, submittal approvals, and deliveries.
5. Run the constraint check. Use a readiness checklist covering labor, materials, equipment, information, access, safety, quality, and preceding work. Assign an owner and a due date to every open item.
6. Confirm resources with trade partners. Ask each sub to validate crew size, production rate, deliveries, and equipment. Resolve conflicts — two crews needing the same hoist, the same crane, or the same hallway — before you publish.
7. Establish commitments. Only move tasks into Week 1 when they’re genuinely ready. Tasks with unresolved constraints stay visible but marked at risk, not promised.
8. Publish a readable schedule. Format it so a foreman gets the answer in five seconds, not five minutes.
9. Review it in a coordination meeting. Focus on exceptions: what changed, what’s at risk, what needs escalation, where trades collide.
10. Track results and learn. Compare planned versus completed every week and record why anything slipped.

Step 5 is where most look-aheads earn their keep. A task isn’t executable just because the schedule says so. It’s executable when the drawings are approved, the material is on site, the crew is available, the area is clear, and the inspection slot is booked. Miss any one of those and you’ve scheduled hope.

The Right Level of Detail: Specific Enough to Assign, Not So Detailed It Dies

Detail level makes or breaks the document. Too vague and it’s useless — “electrical work, Week 2” tells nobody anything. Too detailed and nobody maintains it past week three. The sweet spot is a task a foreman can assign, coordinate, and verify in one to several shifts, with a clear location, a named responsible party, and a measurable finish line.

Compare these two entries for the same work:

• Bad: “MEP rough-in, Level 3”
• Good: “Install 40 light fixtures, Rooms 301–312, ABC Electric, Tue–Thu, complete when fixtures energized and inspected”

Notice what the good version carries: quantity (40 fixtures), location (specific rooms), owner (named sub), dates, and a completion measure you can see with your own eyes. That’s the standard. Other examples that work: pour 6,000 square feet of slab, Zone B, or complete drywall in 12 rooms, west wing.

Every task should answer five questions: what, where, who, when, and what “done” looks like. If a task can’t answer all five, it isn’t ready for Week 1.

One more rule worth writing down: don’t fill every crew to 100 percent capacity. Packing the plan wall-to-wall leaves zero room for the normal stuff — a late delivery, a rain day, a rework request. Research on the Last Planner System consistently shows that plans built with buffer are more reliable than plans built at theoretical maximum output. A plan that finishes 90 percent of a realistic workload beats a plan that finishes 60 percent of an ambitious one.

What Your Look-Ahead Document Should Contain

A practical look-ahead schedule includes a consistent set of fields so anyone reading it — foreman, sub, project engineer, owner’s rep — can find what they need without calling you. Here’s the field set ForemanBrief recommends, and what each column is for:

Two fields deserve extra attention. The Activity ID keeps your look-ahead traceable to the master schedule — which matters enormously if a delay dispute ever lands on a scheduler’s desk. And the constraint status column turns hidden problems into visible action items with names and dates attached.

Can you do this in a spreadsheet? Yes — for small and mid-size projects, a well-maintained spreadsheet beats abandoned software every time. Dedicated scheduling tools earn their cost when you need multi-user updates, automated notifications, audit trails, or links to RFIs and submittal logs. The tool matters less than the discipline.

Constraints and Trade Handoffs: Where Look-Aheads Save the Most Money

Constraint removal is half the job of short-term planning — arguably the more valuable half. Sequencing tasks is easy. Making sure each task can actually run is where you prevent the expensive stalls. Before any task earns a spot in Week 1, check it against this list:

• Approved drawings and submittals
• Materials delivered or delivery confirmed
• Labor and equipment available
• Predecessor work complete
• Work area access (including shared access, hoists, cranes)
• Permits and inspection slots booked
• Safety plans and temporary utilities in place
• Owner or designer decisions made
• Other-trade coordination resolved

Record every unresolved constraint with three things: the item, the owner, and the date it must clear. “Somebody needs to chase the submittal” is not a constraint plan. “Panel schedule approval — J. Ortiz — needed by Thursday” is.

Trade handoffs are the second big win. Short-term schedules shine exactly where one crew’s finish is another crew’s starting condition: framing hands to MEP rough-in, rough-in hands to inspection, inspection hands to insulation and drywall. Sequence by physical area, not just by discipline — location-based planning reveals congestion and crew conflicts that a straight activity list hides completely.

Here’s a scenario every superintendent recognizes. Drywall crew scheduled for Rooms 201–215 Monday. Friday afternoon, you discover the above-ceiling inspection hasn’t happened because the fire caulking detail is still an open RFI. Now the drywall crew shows up with nothing to hang board on — that’s 160 labor hours burned in one morning. A constraint check the previous Tuesday would have caught it. That’s the whole point: the look-ahead is a tool that translates your schedule into specific, actionable work, with problems caught weeks early instead of hours late.

Weather counts as a constraint too. If a task is weather-sensitive — a slab pour, roof work, crane picks — show the dependency, watch the forecast inside your planning window, and line up alternate indoor work. Foreseeable seasonal weather is not a surprise, and treating it like one won’t help you in a delay claim.

Measure Reliability With PPC — Or You’re Just Guessing

At the end of each week, compare what you planned against what you completed. The standard metric is Percent Plan Complete:

PPC = completed planned activities ÷ total planned activities × 100

If you planned 40 tasks and finished 30, your PPC is 75 percent. Most teams starting structured short-term planning land in the 50–60 percent range and improve from there. World-class Lean construction programs sustain PPC above 85 percent.

But the number alone is just a scoreboard. The value is in the reasons behind the misses. For every incomplete task, record why: missing information, labor shortage, late material, predecessor delay, rework, weather, or unrealistic planning. After a month, patterns emerge. If a third of your misses trace back to late submittal approvals, that’s a design-coordination problem, not a field problem — and it deserves escalation, not shrugging.

Two rules make PPC honest. First, don’t delete missed tasks — document them. Automatically carrying slipped work into next week hides recurring problems and builds an invisible backlog. Second, keep prior versions of the schedule. Version history matters for accountability, and it can matter contractually if delay and disruption questions ever arise.

One caution: the look-ahead can carry contractual weight even though it’s “just” a planning tool. It may become part of the project record and relevant to notice requirements or delay claims. Follow your contract’s rules and keep clean version histories.

Five Mistakes That Kill Look-Ahead Schedules

Most failed look-aheads die the same handful of deaths. Skip these and you’re ahead of most of the industry.

1. Copying master-schedule activities verbatim. If “Level 3 MEP” appears in your look-ahead unchanged, you haven’t planned — you’ve reformatted.
2. Publishing without field input. A schedule built by the superintendent alone, without foremen and subs validating crew sizes and production rates, won’t earn real commitments. People commit to plans they helped build.
3. Scheduling tasks with open constraints. Promising work that needs an approval you don’t have sets everyone up to fail on Monday.
4. Ignoring resource conflicts. Two crews in the same corridor, two tasks on the same crane, zero workspace — catch it in planning, not in the field.
5. Updating only before meetings. A look-ahead touched once a week for the meeting is a prop, not a control tool. Record progress daily, revise formally weekly.

Two more honorable mentions: using vague completion criteria (“work on drywall” — how much? where?) and assuming scheduling software generates a realistic field plan automatically. Software formats the plan. It doesn’t make the phone calls that clear the constraints.

Frequently Asked Questions

Why use a two-week window instead of one week or six weeks?

Two weeks gives enough visibility to coordinate resources, order materials, and clear constraints without leaning on uncertain long-range assumptions. Many teams run three-to-six-week look-aheads for lead-time planning but treat the first two weeks as the firm commitment window.

Who should prepare the look-ahead schedule?

The superintendent or project scheduler usually owns the document, but foremen, subcontractors, project engineers, procurement staff, and safety personnel should all validate it. A schedule built without field input rarely reflects actual conditions or earns reliable commitments from the crews doing the work.

How often should a two-week look-ahead be updated?

Record progress daily and formally revise the plan at least once a week in a coordination meeting. When one week ends, roll the window forward by adding another week so you’re always planning 14 days ahead.

Should delayed tasks just move into next week’s plan?

No. First record why the task was missed, confirm the constraint is resolved, and check the effect on downstream work and milestones. Automatically carrying tasks forward hides recurring problems and builds an unrealistic backlog you’ll eventually have to confront.

Can I build a look-ahead schedule in a spreadsheet?

Yes. A spreadsheet works fine for small and moderately complex projects if it’s consistently maintained with locations, owners, dates, and constraint status. Dedicated software pays off when you need multi-user updates, integration with RFIs and submittal logs, automated notifications, or audit trails.

Does a look-ahead schedule have contractual significance?

It can. Although it’s primarily an operational tool, it may become part of the project record and relevant to notice, delay, or disruption claims. Follow your contract’s planning requirements and preserve version histories so you can separate routine adjustments from compensable delays.

Conclusion

Here’s the one thing to remember: a look-ahead schedule is a commitment and coordination tool, not a reporting document. If it isn’t driving phone calls to clear constraints, resolving trade conflicts, and producing promises crews intend to keep, it’s decoration. Build it with field input, check every constraint, keep tasks specific and measurable, and track PPC so the misses teach you something.

Start Monday. Pull the next two weeks off your master schedule, walk the areas, break the work into tasks a foreman can actually assign, and get your subs in a room to commit. Two weeks from now, you’ll wonder how you ran jobs without it.