△
Readiness Cue
Task-specific guidance for ordinary lookahead readiness and constraint issues.
Project 06
Create a Two-Week Lookahead Schedule
Produce one executable two-week lookahead that converts the approved baseline schedule into daily field commitments supported by confirmed labor, material, information, access, safety, quality, and inspection readiness, using the current master schedule, constraint log, and field status as the controlling information.
Field Cue System
These cues appear at the point of work. They identify readiness, constraint, and coordination issues before they become missed commitments, unsafe congestion, or unready field work.
✋
Critical Readiness Cue
A missed commitment, unsafe trade stacking, or premature task release is possible.
⛑
Field Coordination Cue
Practical trade, delivery, and access coordination for the lookahead window.
▤
Authority Alert
Permit, inspection, or authority scheduling conditions vary. Verify before assuming.
▧
Contract Instruction Cue
Follow the executed agreement's specific terms for notice, access, and approval.
▱
Documentation Cue
Recordkeeping and traceability guidance for the lookahead and constraint log.
Job Overview
This project qualifies you to convert the approved baseline schedule from Project 05 into one executable two-week lookahead — the working document field supervision and trades use to commit to specific tasks in a specific area on a specific day. The finished work product is one published, constraint-checked two-week lookahead grid supported by a current constraint log, confirmed labor and material readiness, coordinated access, and scheduled inspections.
You will update the master schedule with actual progress, extract activities planned within the window, break broad schedule activities into daily field tasks, confirm predecessor completion, documents, labor, material, equipment, safety, quality, and inspection readiness for each task, enter unresolved items in a constraint log with an owner and due date, coordinate trade work zones and deliveries, obtain explicit commitments from trade leads, and publish the lookahead to the project team.
This project depends directly on the baseline schedule approved in Project 05 and the WBS built in Project 03. It also draws on the procurement plan built in Project 07 and feeds the coordination meeting run in Project 09, the trade handoff process in Project 08, and the constraint tracking used throughout the rest of the book. A lookahead is not a wish list: a task does not belong on this document until its readiness has actually been checked.
Skills You Will Demonstrate
- PM-031 — Identify near-term tasks.
- PM-032 — Confirm labor needs.
- PM-033 — Confirm material needs.
- PM-034 — Confirm inspection dates.
- PM-035 — Identify constraints.
- PM-036 — Publish a two-week lookahead schedule.
Where This Skill Fits
The baseline schedule approved in Project 05 tells the project what should happen over the life of the job. The lookahead built here tells the field what will actually happen in the next two weeks, and only after every readiness condition has been checked. Every later coordination activity in this book — the procurement release dates in Project 07, the trade handoffs in Project 08, the coordination-meeting agenda in Project 09, and the punch-list sequencing in Project 14 — depends on a lookahead that has not been allowed to drift into an unchecked wish list.
The discipline of confirming readiness before a task appears on the lookahead, taught in this chapter, is the same discipline used later to confirm readiness before a trade is released into an area in Project 08 and before an inspection is requested in Project 16.
Scope and Intended Use
This project covers:
- updating the master schedule with actual starts, actual finishes, progress, and remaining duration before building the lookahead
- extracting and breaking down activities planned to occur within the two-week or approved short-interval window
- confirming predecessor completion, current documents, labor, material, equipment, access, safety, and quality readiness for each task
- confirming inspection requests, inspector availability, and required hold points
- entering unresolved items in a constraint log with one owner and one due date
- coordinating trade work zones, deliveries, and daily inspections to avoid overcrowding and damage
- obtaining explicit trade commitments and publishing the lookahead to affected parties
- tracking daily completion, missed commitments, and reasons to improve the next lookahead
This project does not authorize the learner to:
- place a task on the lookahead before its drawings, decisions, labor, material, equipment, access, predecessor work, safety controls, and inspection requirements have actually been checked
- rebaseline or overwrite the approved master schedule from Project 05; the lookahead reports against that baseline, it does not replace it
- commit a subcontractor, supplier, or inspector to a date without confirming that commitment directly with the responsible party
- remove a required safety control, quality hold point, cure period, or inspection to make the lookahead appear achievable
Any conflict between the master schedule, the field's actual progress, and reported readiness must be identified and resolved in the constraint log before a task is published on the lookahead.
Reference Conventions
Establish these references before building the lookahead, and do not change them mid-cycle without a recorded revision.
| Term | Definition |
|---|---|
| Lookahead window | The two-week or other approved short-interval period the current lookahead covers |
| Committed task | A task whose readiness has been checked and confirmed by the responsible trade lead for a specific day and area |
| Conditional task | A task that remains on the lookahead labeled as dependent on a specific unresolved constraint |
| Constraint | Any unresolved condition — information, labor, material, equipment, access, safety, or inspection — that must be removed before a task can proceed |
| Constraint owner | The specific named person or role responsible for removing a given constraint by its due date |
| Completion reliability | The ratio of tasks completed as committed to tasks committed, tracked across lookahead cycles |
Lookahead Publication Record
Before distributing the published lookahead, record the publication identification directly on the lookahead cover sheet:
Project name: ______ Reporting date: ______ Window covered: ______ to ______ Revision: ______
Prepared by: ____________ Reviewed with field supervision: ____________ Published to: ____________
Prerequisites
- An approved baseline schedule from Project 05, including calendars, milestones, and critical path
- An established WBS from Project 03 with cost codes, schedule identifiers, and quality and inspection assignments
- Access to current drawings, specifications, RFIs, selections, and the procurement log
- A two-week lookahead grid template, constraint log template, and readiness checklist ready for use
- A defined communication method for publishing the lookahead to owners, trades, suppliers, and inspectors
Common Field Fundamentals
Every lookahead in this book, from this chapter's first published cycle through the recurring cycles run inside the Chapter 20 capstone, follows the same sequence: update, extract, break down, confirm, log constraints, coordinate, commit, publish, track. Learning that sequence here, on one residential project, means every later weekly cycle starts from a method already trusted by the field team.
UpdateMaster schedule refreshed with actual starts, finishes, and remaining duration
ExtractActivities planned to start, continue, finish, or constrain work in the window
Break downBroad schedule activities converted to daily, area-specific field tasks
Confirm readinessPredecessor, documents, labor, material, equipment, safety, and inspection checks
Constraint logUnresolved items recorded with one owner and one due date
CoordinateTrade zones, deliveries, and inspections scheduled to avoid conflict
CommitExplicit commitments obtained from trade leads, not assumed attendance
Publish and trackLookahead distributed; completion and reasons tracked for the next cycle
Committed Tasks, Conditional Tasks, and Removed Tasks
Every lookahead must distinguish a task that is genuinely ready from one that remains dependent on an unresolved constraint. Write conditional tasks clearly labeled with the constraint they depend on so a reader cannot mistake a conditional task for a committed one. A task placed on the lookahead without a completed readiness check becomes a missed commitment once the crew arrives and finds the area, material, or information is not actually ready.
PM-031 – PM-036
Schedule Execution / Field Coordination Qualification
Two-Week Lookahead Schedule
A. Finished-Project Specification
Deliverable: one published two-week lookahead grid, containing daily area- and trade-specific tasks confirmed for predecessor completion, documents, labor, material, equipment, access, safety, and inspection readiness, supported by a current constraint log with assigned owners and due dates, coordinated trade zones and deliveries, and explicit trade commitments, compared against the baseline schedule and distributed to owners, trades, suppliers, and inspectors according to the project communication plan.
B. Lookahead Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Cover and window | Reporting date, window covered, revision, preparer | Project calendar, prior lookahead | Establishes the current cycle and its currency |
| Extracted activities | Activities planned to start, continue, finish, or constrain work in the window, including near-window procurement or decisions | Updated master schedule | Defines the raw task list before breakdown |
| Daily task grid | Task, area, trade, crew, material, equipment, predecessor, inspection, constraint by day | WBS, drawings, procurement log | Converts broad activities into measurable daily field commitments |
| Readiness confirmation | Predecessor, documents, labor, material, equipment, access, safety, and quality checks per task | Field verification, procurement log, safety and quality plans | Confirms a task is genuinely executable before publication |
| Constraint log | Unresolved items with owner, due date, and impact date | Readiness confirmation results | Tracks what must be removed before a conditional task can proceed |
| Coordination record | Trade work zones, deliveries, shared equipment, and daily inspections | Trade leads, procurement log, inspection register | Prevents unsafe stacking, delivery conflicts, and missed inspections |
| Commitment record | Explicit trade-lead commitments for each daily task | Direct confirmation with trade leads | Distinguishes a genuine commitment from an assumed attendance |
| Tracking and variance | Comparison of the lookahead with the baseline; deviations explained | Baseline schedule, prior lookahead completion results | Shows how the short-term plan relates to the approved baseline |
C. Information and Document Takeoff
- Source records: the approved baseline schedule, WBS, current drawings, specifications, RFIs, selections, procurement log, safety plan, and quality plan, sufficient to draft every section of the document schedule above without inventing missing readiness information.
- Comparison records: the current master schedule with updated actual progress, used in Step 29 to explain deviation between the lookahead and the baseline.
- Commitment record: written confirmation from each trade lead of crew size, material readiness, and access for each committed task, obtained before publication.
- Revision control: a reporting-date and revision convention sufficient to distinguish the current published lookahead from every superseded cycle.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Master schedule currency | Updated with actual starts, actual finishes, progress, and remaining duration before extraction |
| Task measurability | Every daily task states a measurable commitment tied to a specific area, not a vague activity name |
| Readiness confirmation | Predecessor, documents, labor, material, equipment, access, safety, and inspection readiness checked and recorded for every committed task |
| Constraint log | Every unresolved item assigned one owner, one due date, and an identified impact date |
| Coordination | Trade work zones, deliveries, and shared equipment coordinated to avoid unsafe stacking or conflict |
| Commitments | Explicit trade-lead commitment obtained and recorded for each committed task, not assumed |
| Publication | Lookahead published to owners, trades, suppliers, and inspectors according to the communication plan, with the prior cycle archived |
E. Preparation — Update the Schedule and Extract the Window
- Select the current reporting date and define the two-week or approved short-interval window. Record the exact start and end date the lookahead will cover.
- Update the master schedule with actual starts, actual finishes, progress, and remaining duration. Do not extract activities from a schedule that has not been refreshed with current field status.
- Extract all activities planned to start, continue, finish, or constrain work during the lookahead window. Pull directly from the updated master schedule.
- Include activities just outside the window that require immediate procurement, decisions, or preparation. Record these separately so they are not mistaken for committed near-term tasks.
- Break broad schedule activities into daily or area-specific field tasks. Convert each master-schedule activity into one or more measurable daily tasks.
- Define the measurable commitment for each task. State the area, scope, and finish condition that marks the task complete.
F. Confirm Readiness for Each Task
- Confirm predecessor work is complete or forecast to be complete. Verify against the updated master schedule and field observation.
- Confirm current approved drawings, specifications, RFIs, submittals, and selections are available. Check the document register for the applicable task.
- Confirm permit, inspection, testing, and hold-point requirements. Check the inspection register and quality plan.
- Confirm the responsible trade and committed crew size. Contact the trade lead directly rather than assuming availability.
- Confirm required supervision, competent persons, operators, and specialty qualifications. Verify against the safety plan and trade documentation.
- Confirm material has been approved, ordered, shipped, received, inspected, and staged as required. Check the procurement log for the current status.
- Confirm tools, equipment, lifts, scaffolds, temporary power, water, lighting, and access. Verify availability with the responsible party for shared equipment.
- Confirm work area, laydown, parking, delivery, waste, and housekeeping conditions. Check the jobsite logistics plan from the safety and housekeeping plan.
- Confirm safety plan, hazard analysis, permits, orientation, and protective measures. Verify the applicable controls are active for the task.
- Confirm quality criteria, mockups, checklists, samples, and first-work inspection requirements. Check the quality plan for the applicable acceptance criteria.
- Confirm inspection requests and inspector availability. Contact the authority or inspecting party directly for the applicable window.
- Confirm owner access, occupancy, shutdown, noise, dust, utility, and security coordination. Verify against the communication plan for occupied-home conditions.
G. Log Constraints and Coordinate the Window
- Enter each unresolved item in the constraint log. Record every readiness check from Section F that did not pass.
- Assign one owner and due date to each constraint. Do not record a constraint without a specific responsible party and date.
- Identify the date after which an unresolved constraint will affect the task. State the exact impact date the constraint must be resolved by.
- Remove tasks that are not genuinely ready unless they remain clearly labeled as conditional. Do not publish an unready task as though it were committed.
- Identify alternative executable work for foreseeable constraints. Record a backup task for crews affected by a known constraint.
- Coordinate trade work zones to avoid overcrowding and damage. Confirm the sequence and boundaries for each shared area.
- Coordinate deliveries by date, time, route, unloading, and storage. Confirm delivery windows against site access and laydown capacity.
- Coordinate daily inspections, tests, and quality hold points. Schedule inspections against confirmed task readiness, not assumed completion.
- Add weather contingencies and protection activities. Identify tasks affected by forecast weather and their protection requirements.
H. Commit, Publish, and Track
- Prepare a daily grid showing task, area, trade, crew, material, equipment, predecessor, inspection, and constraint. Assemble the confirmed information from Sections E through G.
- Compare the lookahead with the baseline and explain deviations. State the reason for any task moved earlier, later, or off the current window.
- Review commitments with field supervision and trade leads. Walk the grid with the responsible parties before publication.
- Obtain explicit commitments rather than assuming attendance. Record a direct confirmation from each trade lead for each committed task.
- Publish the lookahead to owners, trades, suppliers, inspectors, and other affected parties according to communication rules. Distribute through the defined channel from the project communication plan.
- Post or provide the current field version. Confirm the field crew has access to the published version, not a prior draft.
- Track daily completion, missed commitments, reasons, and recovered work. Record actual results against each committed task.
- Use completion reliability and constraint causes to improve the next lookahead. Identify recurring constraint causes before building the next cycle.
- Archive the issued lookahead and preserve revisions. Move the superseded cycle to the archive location before publishing the next one.
Common Lookahead Inspection
Inspect every published lookahead using the same checks regardless of project size or complexity.
- Currency check: confirm the master schedule was updated with actual progress before the lookahead was extracted.
- Task check: confirm every daily task states a measurable commitment tied to a specific area and finish condition.
- Readiness check: confirm predecessor, documents, labor, material, equipment, access, safety, and inspection readiness was checked for every committed task.
- Constraint check: confirm every unresolved item is logged with one owner, one due date, and an identified impact date.
- Coordination check: confirm trade zones, deliveries, and shared equipment were coordinated to avoid conflict or unsafe stacking.
- Commitment check: confirm an explicit trade-lead commitment, not an assumption, was recorded for every committed task.
Complete the Lookahead Inspection Checklist in the Inspection Checklist section below before beginning Project 07.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with the current cycle published and tracked, not left as an unresolved draft.
- Confirm the lookahead publication record is dated, revised, and filed with the project documents
- Confirm the constraint log shows every unresolved item with an owner and due date, or explicitly carried forward with an updated impact date
- Move the prior published cycle to the archive location and confirm it is clearly marked as superseded
- Distribute the current published lookahead to every party identified in the project communication plan
- Provide the current lookahead, constraint log, and completion-tracking record to Project 07 and Project 09 for use in procurement release and coordination-meeting review
Field Terms
- Lookahead Window
- The two-week or other approved short-interval period the current lookahead covers.
- Committed Task
- A task whose readiness has been checked and confirmed by the responsible trade lead for a specific day and area.
- Conditional Task
- A task that remains on the lookahead labeled as dependent on a specific unresolved constraint.
- Constraint
- Any unresolved condition — information, labor, material, equipment, access, safety, or inspection — that must be removed before a task can proceed.
- Constraint Owner
- The specific named person or role responsible for removing a given constraint by its due date.
- Completion Reliability
- The ratio of tasks completed as committed to tasks committed, tracked across lookahead cycles.
- Readiness Confirmation
- The point-by-point check of predecessor, document, labor, material, equipment, access, safety, and inspection status for a task before it is committed.
- Trade Stacking
- Unsafe or unproductive congestion caused by scheduling more trades into an area than it can safely or efficiently hold.
- Explicit Commitment
- A direct confirmation obtained from a trade lead, distinguished from an assumed attendance based on the master schedule alone.
- Archive Cycle
- The controlled removal of a superseded lookahead from active use once the current cycle is published.
Skill Check
- Why must the master schedule be updated with actual progress before the lookahead is extracted?
- What is the difference between a committed task and a conditional task, and why must a lookahead distinguish them?
- What happens to a lookahead's field authority if a superseded cycle is not moved to the archive location?
- Why must every constraint be assigned exactly one owner and one due date rather than a general responsible group?
- What readiness conditions must be confirmed before a task can appear as committed on the lookahead?
- Why is an assumed attendance not equivalent to an explicit trade-lead commitment, and how does the learner confirm the difference?
- Why must trade work zones and deliveries be coordinated before the lookahead is published rather than after a conflict appears?
- What are three possible causes of low completion reliability across several lookahead cycles, and how does the learner confirm which one occurred?
- What must the learner do when a task is not genuinely ready but remains schedule-relevant, according to the constraint-logging rule?
- Why does this chapter require the lookahead to be compared against the baseline schedule rather than treated as an independent document?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-031 | Extracts and breaks down near-term activities from an updated master schedule into measurable, area-specific daily tasks | |||
| PM-032 | Confirms responsible trade, committed crew size, and required supervision or qualifications for each near-term task | |||
| PM-033 | Confirms material approval, order, shipping, receipt, and staging status against the procurement log for each near-term task | |||
| PM-034 | Confirms inspection requests, inspector availability, and hold-point requirements for each near-term task | |||
| PM-035 | Identifies unresolved constraints and records each with one owner, one due date, and an identified impact date | |||
| PM-036 | Publishes a coordinated, constraint-checked two-week lookahead with explicit trade commitments and tracks completion against it |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
Inspection Checklist — Lookahead Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Schedule currency | Master schedule updated with actual progress before extraction | ||
| Task definition | Every daily task measurable and tied to a specific area and finish condition | ||
| Predecessor readiness | Predecessor work complete or forecast to be complete for each committed task | ||
| Document readiness | Current approved drawings, specifications, RFIs, submittals, and selections confirmed available | ||
| Labor readiness | Responsible trade, crew size, and required qualifications confirmed | ||
| Material readiness | Material approved, ordered, shipped, received, and staged as required | ||
| Safety and quality readiness | Hazard controls, hold points, and first-work inspection requirements confirmed | ||
| Inspection readiness | Inspection requests submitted and inspector availability confirmed | ||
| Constraint log | Every unresolved item logged with one owner, one due date, and an impact date | ||
| Publication | Lookahead published to owners, trades, suppliers, and inspectors, with the prior cycle archived |
Constraint log status: ____________ Open items carried forward: ____________
Lookahead declared published: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
Performance Check
With the lookahead built and constraints logged, review it against the Acceptance Standards table and confirm the master schedule was current before extraction, every daily task is measurable and tied to a specific area, every committed task passed the full readiness confirmation, every unresolved item is logged with one owner and one due date, trade zones and deliveries are coordinated to avoid conflict, explicit trade-lead commitments were obtained rather than assumed, and the current lookahead has been published and the prior cycle archived. Complete the Lookahead Inspection Checklist and correct any failed item before beginning Project 07. If an item fails, identify whether the error occurred in schedule updating, task breakdown, readiness confirmation, constraint logging, coordination, or publication before revising.
Project Closeout
You have completed the sixth project in the construction project management sequence: creating a two-week lookahead schedule. This project required you to identify near-term tasks (PM-031), confirm labor needs (PM-032), confirm material needs (PM-033), confirm inspection dates (PM-034), identify constraints (PM-035), and publish a two-week lookahead schedule (PM-036).
You now have a published, constraint-checked lookahead, a current constraint log, and a completion-tracking record supporting future cycles. That working method carries directly into the next project: building the material procurement and delivery plan that will supply the confirmed material readiness this lookahead depends on every week going forward.
File your published lookahead, constraint log, and commitment record where Project 07 can incorporate confirmed installation dates into the procurement plan. Every later weekly cycle in this book is built from this exact working method.