Keep Primavera P6 as the governed master schedule, then manage short-interval planning in a connected execution layer.

Translate near-term P6 activities and milestones into make-ready work, weekly commitments and daily coordination. Use a rolling look-ahead window appropriate to the project, identify constraints before work enters the weekly plan, and give every constraint an owner and required-by date.

Field teams should manage the detail needed to execute. Project controls should review exceptions, assess their schedule significance and control what becomes an accepted status or forecast update in P6.

This preserves one control schedule without forcing every field task, handoff and commitment into it.

Use P6 for control and the short-interval plan for production

Primavera P6 should remain the authoritative control schedule. It provides the governed activity logic, milestones, contractual dates, status position and forecast used by project controls.

Short-interval planning serves a different purpose. It helps the people performing and coordinating the work decide:
• What work should become available next
• What must be made ready
• What can genuinely be performed
• What teams will commit to completing
• What happened and why
• What project controls needs to know

The two planning levels should remain distinct but connected.

P6 remains the control schedule. Optimality connects the controlled plan to execution reality.

Build the look-ahead from controlled activities and milestones

Start with the relevant activities, milestones and work fronts in P6. Bring the near-term scope into a rolling look-ahead plan and develop it to the level needed for execution.

A look-ahead window is commonly several weeks long. Lean Construction Institute guidance describes a typical range of three to twelve weeks, with six weeks often used as a starting point. The correct window depends on procurement lead times, permits, design releases, access requirements and the amount of preparation needed to make work executable.

The look-ahead should retain a clear relationship to the appropriate P6 activity or milestone. It should not become a disconnected second master schedule.

P6 activity or milestone → rolling look-ahead → make-ready planning → weekly commitments → daily coordination → completion and variance evidence → project-controls review → governed P6 update

Make work ready before teams commit

Short-interval planning is most useful when it exposes what could prevent work from starting or finishing as intended.

For each upcoming package of work, confirm readiness across the factors that matter on the project, such as:
• Approved design information
• Materials and equipment
• Labour and specialist resources
• Access and work areas
• Permits and inspections
• Predecessor completion
• Temporary works
• Safety requirements
• Interfaces with other teams
• Required decisions

Record each unresolved constraint with a named owner, required-by date and relationship to the affected work.

The objective is not simply to produce another list of activities. It is to prevent unready work from being treated as a reliable commitment.

Turn ready work into weekly commitments

Once work is sufficiently ready, teams can select it for the weekly plan.

A credible commitment should identify the work, responsible party, intended completion point and any remaining coordination conditions. Daily coordination can then focus on current handoffs, emerging constraints, actual completion and the support teams need.

Not every crew-level task belongs in P6. Detailed execution tasks should remain at the level where they can be owned and updated by the people closest to the work.

The connection to P6 should preserve enough traceability to answer:
• Which controlled activity or milestone does this work support?
• Is a constraint threatening a controlled date?
• Does actual progress differ materially from the current schedule position?
• Does project controls need to assess a status or forecast change?

Feed exceptions and learning back to project controls

Weekly planning results should not automatically overwrite the P6 schedule.

Instead, project controls should receive structured execution signals such as:
• Work completed
• Work not completed
• Reasons for variance
• Constraints that remain unresolved
• Changed sequence or access conditions
• Emerging risks to milestones
• Forecast implications
• Supporting field evidence

Project controls can then determine whether the information represents normal execution detail, a temporary issue or a material schedule change.

This keeps professional judgment and schedule governance in the loop while reducing the delay and manual reconciliation involved in understanding field conditions.

How Last Planner connects with Primavera P6

Last Planner practices can operate beneath and alongside the P6 control schedule without replacing it.

Milestones and controlled activities establish the required outcomes and timing. Pull planning, make-ready planning, weekly work planning and daily coordination develop how teams will achieve those outcomes.

The important design principle is traceability without duplication:
• P6 governs the control position.
• Collaborative planning develops executable work.
• Constraint management makes upcoming work ready.
• Weekly commitments create reliable promises.
• Daily coordination captures current execution signals.
• Project controls determines what changes the governed schedule.

Where FlowSpan and Optimality fit

FlowSpan is intended to connect these planning levels.

It provides an execution-planning environment in which teams can develop near-term work, manage constraints, record commitments and capture progress while maintaining relationships to the relevant controlled schedule activities.

Optimality supports the operating model around that connection: planning responsibilities, review points, information flows, schedule governance and the decisions required to keep the control schedule informed by execution reality.

See how Optimality connects P6 with execution reality.

What a workable operating cadence looks like

A practical cadence might include:
• Project controls refreshes the governed schedule position.
• Planning teams identify the activities and milestones entering the look-ahead window.
• Delivery teams develop the executable work and identify constraints.
• Constraint owners remove or escalate blockers before the required dates.
• Teams make weekly commitments from work that is genuinely ready.
• Daily coordination records completion, emerging issues and reasons for variance.
• Project controls reviews schedule-relevant exceptions and evidence.
• Approved status or forecast changes are incorporated into P6 through the established controls process.

The exact meeting structure and planning horizon can vary. The essential requirement is a controlled loop between the master schedule and the people executing the work.

Frequently asked questions

Does every short-interval task need to be added to P6?

No. P6 should contain the level of detail needed for effective schedule control. Crew-level tasks, daily handoffs and detailed preparation can be managed in the execution plan, provided their relationship to controlled activities is clear.

How long should the look-ahead window be?

Use a window long enough to identify and remove constraints before they affect execution. Lean Construction Institute guidance describes three to twelve weeks as a typical range, with six weeks commonly used. Projects should adjust the window for their planning cycle and lead times.

Should completed weekly work automatically update P6?

No. Completion information should be reviewed through the project-controls process. The scheduling engineer or responsible controls professional should determine the appropriate status, forecast and supporting evidence.

How should constraints be managed?

Every material constraint should have a clear description, owner, required-by date, status and connection to the affected work. Constraints threatening controlled dates should be visible to project controls.

How is this different from maintaining two schedules?

The execution plan is not a competing control schedule. It develops the near-term work required to deliver the controlled plan. P6 remains authoritative, while the execution layer provides more detailed coordination and field intelligence.

How do you keep P6 aligned with actual field execution?

Use a governed information loop between execution planning and project controls. See How do you keep a P6 control schedule aligned with what’s actually happening in the field?

Next step

See how FlowSpan connects planning to execution.

Sources

• Oracle Primavera P6 Professional: Scheduling projects
• Oracle Primavera P6: Activity Look Ahead
• Lean Construction Institute: Last Planner System
• Lean Construction Institute: Lean Construction Planner Standard Work
• Lean Construction Institute: Last Planner System 2020 Current Process Benchmark

‍