6 Integrated Project Control Scenarios

The purpose of integrated control

Project control compares actual performance with an approved plan, explains significant differences, forecasts likely outcomes, and guides decisions. It integrates scope, schedule, cost, and risk because a change or problem in one area can affect the others.

Connect approved baselines and risks

Before work begins, establish compatible, approved baselines. The Scope baseline defines the included work and deliverables through the approved scope statement, work breakdown structure (WBS), and WBS dictionary. The Schedule baseline sets the approved sequence and timing of that work, including milestones and the critical path. The Cost baseline is the approved, time-phased budget for authorized work.

The project’s total authorized budget may also include management reserve. Management reserve is not part of the performance measurement baseline.

Link scope, schedule, and budget through the WBS and assigned responsibility. This allows a status report or proposed change to be traced to the work package it affects. Record assumptions and uncertainties, and connect significant risks to affected scope, activities, milestones, costs, owners, and responses. Risk analysis can show a range of possible outcomes; having a single baseline does not make uncertain forecasts certain.

Measure performance with earned value

Earned value management (EVM) compares the budgeted value of completed work with the time-phased plan and actual cost. At a status date, use these measures:

• Planned value (PV): budgeted value of work scheduled to be complete.

• Earned value (EV): budgeted value of work actually completed.

• Actual cost (AC): cost incurred for the work performed.

• Budget at completion (BAC): total budgeted value of authorized work in the performance measurement baseline.

The main calculations are:

• Cost variance: $\mathrm{CV} = \mathrm{EV} - \mathrm{AC}$. A negative value means the completed work cost more than budgeted.

• Schedule variance: $\mathrm{SV} = \mathrm{EV} - \mathrm{PV}$. A negative value means less budgeted work was completed than planned. EVM schedule variance is expressed in budget units, not calendar time; consult the schedule and critical path to assess time impact.

• Cost performance index: $\mathrm{CPI} = \mathrm{EV} \div \mathrm{AC}$. A value below $1.0$ indicates unfavorable cost efficiency.

• Schedule performance index: $\mathrm{SPI} = \mathrm{EV} \div \mathrm{PV}$. A value below $1.0$ indicates unfavorable progress against the time-phased plan.

For example, at the end of a reporting period, a project has $\mathrm{PV} = \$100{,}000$, $\mathrm{EV} = \$80{,}000$, and $\mathrm{AC} = \$90{,}000$. The results are:

The project completed less budgeted work than planned and spent more than the earned value of that work. Neither index alone explains the cause or predicts the finish date. Investigate the affected work packages, remaining critical-path activities, and risks.

Forecast outcomes and report for decisions

If current cost efficiency is assumed to continue, a simple forecast is:

For a $\mathrm{BAC}$ of $\$200{,}000$, this gives an estimated $\mathrm{EAC}$ of about $\$225{,}000$. This is a forecast under an assumption, not an approved budget change. Document the assumption and compare the forecast with other reasonable scenarios.

A decision-ready status report distinguishes facts, analysis, forecasts, and decisions required. It should state the reporting date and baseline version; summarize completed and remaining scope; report milestone and critical-path status; show actual cost, variances, and forecasts; and explain significant risks, issues, changes, and corrective actions. Give each action an owner, due date, and measurable result. Escalate exceptions against agreed tolerances rather than obscuring them with an overall “green” rating.

For example, reporting that a design review is two weeks late is more useful when paired with the affected critical-path activities, likely effect on the finish date, cause, recovery options, cost implications, risk exposure, and the decision or support needed from the sponsor.

Control changes and choose actions

A Variance is a difference between actual performance and the approved plan; it does not authorize a new plan. A Change request proposes a modification to an approved baseline or another controlled project element. Assess a proposed change across scope, schedule, cost, quality, resources, risk, and contractual or stakeholder commitments. Submit it to the designated authority or change control board under the project’s change process. Record the decision and update relevant documents and baselines only after approval. Do not silently rebaseline to make unfavorable performance disappear.

Corrective action addresses an existing performance problem, while Preventive action reduces the likelihood or impact of a future problem. Before acting, identify the cause and compare options. Adding staff, for example, might shorten a critical-path activity but could increase cost, require onboarding, or create coordination risk.

A sound action specifies what will change, what it will cost, which milestone or deliverable it protects, what new risks it creates, who owns it, and how its effectiveness will be checked.

Apply control to schedule and scope scenarios

A team reports $\mathrm{SPI} = 0.85$ and $\mathrm{CPI} = 1.02$. A critical-path supplier delivery is late, while other work packages have spent less than planned. The sponsor asks whether the project is “under budget and therefore fine.” Favorable aggregate cost efficiency does not remove the schedule threat. Confirm the supplier delay’s effect on the critical path and completion forecast, assess recovery choices and their costs and risks, report the likely outcome, and assign an owner to the supplier response. Do not infer a calendar delay directly from $\mathrm{SPI}$.

A stakeholder requests an additional dashboard after the scope baseline has been approved. The feature may require new data access, testing, and training. Log the request and assess its scope, dependencies, schedule, cost, quality, and risk impacts. Present options such as approving it with a revised target, exchanging it for lower-priority scope, deferring it, or rejecting it. Obtain a decision from the authorized approver; until approval, continue against the current baseline.

Respond to realized risks and worsening cost

A previously recorded equipment-availability risk occurs. A key activity may now miss a milestone, and a mitigation reserve was planned. Treat the event as an issue as well as tracking its remaining risk. Confirm impacts on linked activities, cost, and deliverables; implement the authorized response; update forecasts and risk and issue records; and escalate decisions beyond the project manager’s authority. Use reserve according to its authorization rules, and request formal approval if the response changes a baseline.

Across two reporting periods, the $\mathrm{CPI}$ declines while the team says it can recover by “working harder.” Verify the status data and identify the work packages driving the trend. Test whether the cause is rework, underestimated effort, changed conditions, or incomplete work measurement. Forecast the cost to complete and evaluate realistic actions, owners, costs, and risks. Report a supported forecast and seek a decision if tolerances or authorized funding may be exceeded; do not promise recovery without evidence.

Bring the control cycle together

Integrated project control ties approved scope to scheduled, budgeted work and monitors risks that can alter expected outcomes. Use status data to identify and explain variances, forecast likely results, and make decisions about the future. Evaluate proposed changes across all affected baselines, obtain proper authorization before updating them, and make corrective actions specific, owned, and measurable.