Two-Week Look-Ahead Schedule Template for Contractors

The drywall crew is booked for Thursday. The electrician says rough-in will be finished Wednesday. But the inspection has not been booked, two fixtures still need an owner decision, and nobody has checked whether the delivery truck can reach the building during paving.

Thursday looks clear on the calendar. The work is not ready.

A two-week look-ahead schedule makes those missing conditions visible while someone still has time to resolve them. For a small contractor, a shared sheet and a short foreman meeting can be enough. Each task needs a location, a crew, a finish condition, and evidence that its prerequisites are cleared.

The Lean Construction Institute's Last Planner System distinguishes making upcoming work ready from making weekly commitments. That distinction is useful even if your company does not use the full system: keep possible work on the look-ahead, but commit crews only after checking what they need.

What belongs on a two-week look-ahead?

Record the project and schedule reference, issue date, planning window, activity ID, location, scope, start and finish, crew, predecessor, material status, inspection or access gate, unresolved constraint, responsible person, required-by time, and readiness status. Keep actual results alongside the original promise once work begins.

Put the issued sheet in the same job folder as the current plans, approvals, and field records. A row saying “approved” should point to the approval someone can actually find.

Define the window before filling in dates

“Two weeks” can mean ten working days or fourteen calendar days. State which you mean, including shifts, holidays, shutdowns, and the date through which actual progress has been checked.

For example:

Job JB-02418 · Look-ahead LA-06 · Issued October 2, 2026 · Status through October 2 · Window October 5–16 · Monday–Friday day shift · Based on schedule update U-04.

Use the current project schedule as the starting point. Check the previous week's actual progress with the foremen before carrying dates forward. “Nearly finished” needs a remaining quantity or a clear list of unfinished work.

The GAO Schedule Assessment Guide, GAO-16-89G explains why linked activities, resources, and accurate progress matter to a reliable schedule. Your short-term sheet should preserve the connection to that larger plan. If a missed handoff changes the project forecast, send the facts back to whoever maintains the controlling schedule.

A two-week field view may also be too short for procurement. Keep longer-lead selections, fabrication, utility coordination, and equipment orders on a separate forward list, then bring them into the field window when relevant.

Copy this schedule structure

Use one row per task that a foreman can assign and verify. Split a large activity by room, zone, system, or inspection boundary when that makes the handoff clearer.

These are suggested fields, not a universal contract requirement. Adapt them to the job's scheduling and reporting procedure.

For released tasks, a Construction Work Order can carry the detailed scope, location, drawing reference, and finish condition. Keep the schedule row brief and use the same task ID on both records. The work order supports the field assignment; it does not itself establish every required approval.

Give every blocked task a person and a clearing test

“Waiting on owner” is not an action. Write who will ask for what, when the answer is needed, and what evidence will clear the task.

Use an RFI when the missing item is a design clarification. Use the Submittal Register to track required reviews and releases. A Purchase Order records an order, but the schedule still needs delivery confirmation and a receiving check.

Keep those distinctions visible. Ordered is not received. Received is not accepted. An inspection booking is not an inspection result.

The research paper Rethinking Lookahead Planning to Optimize Construction Workflow identifies weak constraint removal and inadequate learning from failed plans as practical problems. A constraint log gives your team something specific to review: which prerequisite remained open, who owned it, and what should change next time.

Work through one handoff before promising the next

Here is an illustrative sequence for a small interior project. Dates and crew sizes are planning assumptions, not recommended trade durations or staffing levels. The unresolved rows are candidates, not promises; confirm each crew allocation and prerequisite before commitment.

Give each row an observable finish condition. For LA-01, that could be “framing complete in the named rooms, openings checked against the released drawings, and handoff accepted by the rough-in foremen.” For LA-03, completion means the required acceptance is recorded and any blocking corrections are closed, not simply that an inspector visited.

The drywall foreman can see why LA-04 is blocked. The superintendent can see what to resolve before assigning the crew. The owner can see that the fixture decision has a required-by point rather than an open-ended request. Reserve time for inspection corrections and reinspection if needed; do not assume an October 9 visit will automatically release the walls for October 12.

At the next review, update each gate from evidence. Record inspection findings and unresolved corrections in the Construction Inspection Report. If framing finishes late, check the rough-in crew's availability and the inspection arrangement before simply sliding every bar one day.

When the field condition changes the design or priced scope, follow the clarification and approval process for plans that do not match the field. A revised look-ahead date does not approve extra work or settle responsibility for a delay.

Run a short weekly review, then check daily

Review the sheet with the people who can assign crews and clear constraints. For a small job, that may be the superintendent, project manager, and affected foremen, with procurement or the owner joining for specific decisions.

Work through five questions:

1. What actually finished, and what remains?
2. Which tasks fall inside the next window?
3. What could prevent each task from starting or finishing?
4. Who will clear each constraint, and by when?
5. Which ready tasks can the performing foremen commit to?

Check shared resources across rows. The same crew, lift, loading area, shutdown, or work space cannot serve conflicting assignments just because both rows are green. Confirm the applicable safety and quality prerequisites with the responsible people before release.

Issue a dated version after the meeting. During daily huddles, review today's handoffs and tomorrow's readiness. Preserve field results in the daily report, using the same task and issue IDs. The guide to construction daily reports explains how to distinguish planned work, actual work, and remaining work.

Preserve missed promises instead of hiding them

Suppose eight tasks were promised for the week and seven met their stated finish conditions by their promised dates. Percent Plan Complete (PPC) is:

7 completed promises ÷ 8 total promises × 100 = 87.5%

LCI uses PPC to review whether weekly tasks were completed on time. Count a task as complete only when it meets the agreed finish condition by its promised date; partial or late completion is a missed promise for that week's score. PPC is not the percentage of the project built, a critical-path calculation, or proof that the contractual completion date will be met.

For the unfinished task, record the reason and next action. “Two door frames rejected at receipt; supplier replacement confirmation due Monday” tells the team more than “carpentry late.” Preserve the original promised date, add the actual result, and issue a new forecast. Do not overwrite last week's sheet to make the missed promise disappear.

Sources

Sources reviewed October 2, 2026. The sample fields, dates, and workflow above are practical editorial examples.

• Lean Construction Institute, The Last Planner System: From Pull Planning to Weekly Work Planning — make-ready planning, commitments, daily review, and planning reliability.
• Farook R. Hamzeh, Glenn Ballard, and Iris D. Tommelein, Rethinking Lookahead Planning to Optimize Construction Workflow, Lean Construction Journal, 2012, pp. 15–34 — constraint removal and learning from plan failures.
• U.S. Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules, GAO-16-89G, December 22, 2015 — integrated schedules, resources, sequencing, and progress updates.

Disclaimer

This article provides general planning and documentation guidance, not a project-specific construction schedule, contract interpretation, delay analysis, or safety plan. The sample dates and fields are illustrative. Check the governing contract, current schedule, site conditions, permit and inspection requirements, and applicable safety procedures with the people responsible for the project before assigning work. A look-ahead does not authorize a change in scope, price, or contractual completion dates.