1.10 Phase Relationships, Baseline Plan, Forecasts, and Risk/Recovery Planning

1.10 Phase Relationships, Baseline Plan, Forecasts, and Risk/Recovery Planning

A project plan becomes actionable when major phases and deliverables are related in a feasible sequence. Engineering releases enable procurement and construction; installed systems enable testing; testing enables turnover; and turnover enables operation. These relationships may overlap, but the required information and acceptance interfaces must be explicit.

Sequence and phase relationships

Start with a phase map:

• design maturity and release packages;
• procurement inquiry, award, vendor data, fabrication, delivery, and acceptance;
• enabling works and permanent construction;
• system completion, pre-commissioning, commissioning, and performance testing;
• training, documentation, turnover, and closeout.

Avoid a single finish-to-start chain when the strategy uses controlled overlap. For example, construction can begin from issued-for-construction packages before all design ends, but each work package needs a real release predecessor and change-risk treatment.

Baseline plan

The baseline is the approved reference against which performance is measured. Approval should follow scope, constructability, resource, risk, stakeholder, estimate, and schedule review. The baseline includes or references the scope, dates, budget, assumptions, calendars, logic, and acceptance criteria needed to understand the commitment.

Freeze and preserve the approved version. A late forecast is not repaired by moving baseline dates. Baseline revision requires authorized change under the project’s governance.

Periodic forecasts

A forecast answers, “Given actual progress and current information, what is now expected?” It should use:

• actual starts and finishes;
• realistic remaining durations;
• current logic and calendars;
• approved and pending changes shown under policy;
• productivity and trend evidence;
• procurement and decision status; and
• current risks and mitigation.

The forecast can differ from both the baseline and a recovery target. Report all three clearly when relevant.

Risk plan

The risk plan identifies threats and opportunities, owners, triggers, probability/impact, response actions, and schedule interfaces. Some responses avoid or reduce probability; others reduce impact, transfer risk, accept it with contingency, or exploit an opportunity.

Link material risks to activities or milestones so the team knows when exposure begins and when a response decision is due.

Recovery planning

Recovery planning begins when the forecast no longer meets required dates or when trend indicates that failure is likely. Generate alternatives such as:

• resequencing preferential logic;
• opening parallel workfronts;
• adding qualified resources or shifts;
• expediting information or material;
• changing means and methods;
• negotiating phased turnover; or
• obtaining an authorized time change when supported.

Each alternative needs quantified time effect, cost, resources, safety/quality review, risk, and responsible commitments. A recovery bar chart produced by shortening durations without operational agreement is not a plan.

Scenario example

A vendor delivery threatens commissioning. The current forecast shows a twenty-day miss. One option expedites freight for eight days, another resequences pre-commissioning for twelve days, and a combined plan may recover more but creates trade congestion. The team models each option, checks resource and safety effects, chooses a funded plan, and tracks its assumptions. The original baseline remains visible while the approved recovery target and current forecast are reported separately.

Governance questions

• Who approves the baseline and revisions?
• Which pending changes appear in the working forecast?
• What variance triggers a recovery schedule?
• Who can authorize premium cost or additional shifts?
• When is the risk model or contingency draw updated?

Planning is complete only when these decision rules accompany the technical sequence.

Applied review: connect the planning products

Sequencing translates execution strategy into relationships among phases, work packages, decisions, and interfaces. Review phase handoffs explicitly: design information enables procurement; procurement and access enable installation; systems completion enables testing; accepted testing enables turnover. Summary-level relationships help communicate the plan, but the detailed network must contain the actual drivers so that an update can explain movement.

The baseline records the approved scope, sequence, durations, resources, calendars, milestones, and assumptions at a defined point. A periodic forecast answers a different question: given actual status, current information, remaining work, and current risk, when are future events now expected? Preserve baseline history while updating the forecast. If an approved change modifies the baseline, retain authorization and a bridge from the previous reference.

Risk and recovery planning close the loop. Identify threats and opportunities, assign owners, model material effects, and define response triggers. A recovery plan should target the actual controlling paths with feasible changes to logic, methods, resources, calendars, or scope. Quantify time and cost consequences and test safety, quality, procurement, and approval effects. Merely replacing current dates with desired dates is not recovery. A strong exam answer keeps baseline, current status, forecast, risk response, and approved change as related but distinct control records.