When daily plan changes need a phase review: rebuild from actual conditions
The envelope superintendent has rewritten the lookahead on eleven of fourteen mornings. Scaffold movements recur as a constraint, yet each meeting shifts another task without resolving the shared sequence. The team needs to assess whether the phase plan remains credible rather than keep presenting daily edits as a workable commitment.
Call a phase review when evidence shows repeated patching is no longer producing a credible sequence. Agree meaningful triggers for the project's conditions and act when they matter; three weeks is not a universal waiting period. A half-day session may be useful, but a revised plan is ready only when its actual dependencies, assessments and receiving commitments support it. The meeting itself cannot guarantee the next three weeks will hold.
Rebuild from the actual state and owned constraints
- Identify why the current plan needs review. Bring dated revisions, repeated constraints, completion evidence and changed assumptions. Check the meaning of any reliability measure and its denominator before using it. Define the effect on actual commitments. Do not wait for an arbitrary count when an immediate response is needed, or use every small adjustment as proof the entire phase failed.
- Establish the current receiving conditions. With the relevant trades and decision roles, locate completed work, usable areas and outstanding releases. Include access, resources, procurement and technical questions that affect the sequence. Keep fixed obligations and forecast assumptions identifiable. Moving a sticky note cannot approve a changed scaffold arrangement or erase an unresolved interface.
- Build and assess feasible sequence options. Work through actual dependencies and trade handovers, identifying what each option needs and who must decide. Obtain required technical, access and commercial reviews. Agree resource and receiving commitments where possible, with owners for missing answers. A preferred option remains proposed until its actual conditions are met.
- Issue statuses and verify the handover. Give affected people the received sequence, clear boundaries and the pending items they must not assume resolved. Record the current forecast and any further approval route. Set a useful review of actual progress and constraint closure. A same-day issue can communicate proposals and holds without falsely presenting every task as released work.
Common mistakes
- Waiting for a fixed three-week threshold despite a consequential trigger.
- Building the new plan from assumed rather than actual readiness.
- Treating moved schedule notes as approved technical changes.
- Issuing every proposed task as a confirmed release.
Checklist
A phase review should produce
- Evidence for the review and actual commitment effects.
- Current work state and located unresolved constraints.
- Assessed sequence options and required decisions.
- Received commitments separated from pending proposals.
- An owned handover and progress-review trigger.
Check your understanding
The session produces a same-day lookahead, but one access change is unreviewed. Can that section be marked ready?
