Monitoring and Controlling Projects

A project plan is a hypothesis. It is a structured prediction of how resources, time, and money will combine to produce a result. Monitoring and controlling is the process of testing that hypothesis against reality — and correcting course before the deviation becomes irreversible.

---

Why Monitoring & Controlling Is Where Projects Are Won or Lost

Consider this: planning determines what should happen. Execution determines what does happen. Monitoring and controlling determines whether anyone notices the difference in time to do something about it.

The PMBOK Guide identifies monitoring and controlling as the process group that spans the entire project implementation phase. Its purpose is to collect, measure, and disseminate performance information so that preventative or corrective action can be taken before variances become permanent.

The four core project elements — scope, time, cost, and quality — each require dedicated control processes. But here is the critical insight that many practitioners miss: these four elements are interdependent. You cannot change one without impacting the others.

Core Principle: Due to the strong relationship between the four core elements, one cannot change one without impacting the others. This interdependency is what makes integrated monitoring and controlling essential — and what makes siloed control dangerous.

MONITOR & — CONTROL — PROJECT WORK

Scope — Control

Schedule — Control

Cost — Control

Quality — Control

Relationship details

From	Relationship	To
MONITOR & — CONTROL — PROJECT WORK	leads to	Scope — Control
MONITOR & — CONTROL — PROJECT WORK	leads to	Schedule — Control
MONITOR & — CONTROL — PROJECT WORK	leads to	Cost — Control
MONITOR & — CONTROL — PROJECT WORK	leads to	Quality — Control
Scope — Control	Interdependent	Schedule — Control
Schedule — Control	Interdependent	Cost — Control
Cost — Control	Interdependent	Quality — Control
Quality — Control	Interdependent	Scope — Control

---

The Monitoring & Controlling Process: Inputs, Tools, and Outputs

This top-level process feeds into the four specific control processes detailed below.

---

Control 1: Scope Control

Scope control is concerned with influencing and controlling the factors that create project scope changes. It is a set of iterative processes that produce corrective actions to ensure deliverables fit precisely with defined requirements.

Preventing Scope Creep

Scope creep — the incremental, unauthorised addition of work to a project — is prevented through specific procedures:

• Define who can submit potential changes
• Define who can approve changes
• Define which elements cannot be changed under any circumstances
• Establish scope change notification protocols

Risks of Unmanaged Scope Changes

When scope changes escape the control system, the consequences cascade:

• Rework is required after the project is already under time pressure (fast tracking becomes necessary)
• Activities cross the plan-execute boundary — teams are building while still designing
• Project control is performed when the team is least able to be proactive
• The budget is adversely affected not only by the change itself but by the cost of additional planning
• The overall size of the project increases, compounding the process overhead

---

Control 2: Schedule Control

Schedule control compares the current project position against the project management plan, identifies factors creating schedule changes, and manages those changes.

Progress Reporting

The project schedule is the primary tool for comparing current status with planned start and finish dates. Progress reports should:

• Be presented in a consistent format throughout the project
• Be distributed to stakeholders as specified in the Project Communication Plan
• Draw on charts providing a graphical representation of the schedule baseline, current position, and forecast completion dates

Best Practice: A CPM (Critical Path Method) resource-loaded schedule should be developed prior to full funding. During execution, the actual schedule is compared to the target schedule and corrective actions — which may include changing resources or adjusting activity logic — are taken on an ongoing basis.

Workstream	Activity	Type	Timing / dependency / duration
Milestones	Project Start	Milestone	milestone · ms1 · 2026-01-01 · 0d
Milestones	Project Finish (Forecast	Milestone	milestone · ms2 · 2026-04-15 · 0d
Activity A	Baseline Plan	Activity	done · a_base · 2026-01-01 · 30d
Activity A	Actual Progress	Activity	active · a_act · 2026-01-01 · 35d
Activity A	Forecast Completion	Activity	crit · a_fc · 2026-01-01 · 40d
Activity B	Baseline Plan	Activity	done · b_base · 2026-02-01 · 30d
Activity B	Actual Progress	Activity	active · b_act · 2026-02-05 · 35d
Activity B	Forecast Completion	Activity	crit · b_fc · 2026-02-05 · 45d
Status	Today	Milestone	milestone · today · 2026-03-01 · 0d

---

Control 3: Cost Control

Cost control monitors and records positive and negative variances within the project budget and applies preventative or corrective actions to minimise cost overruns.

Costs That Must Be Managed

Cost Control Activities

Cost control is not merely tracking expenses. It encompasses:

• Maintaining an approved and accurate budget
• Predicting the final cost of the project and comparing with approvals
• Influencing factors that create negative budget changes
• Tracking, approving, and reporting expenditure against budgets
• Informing appropriate stakeholders of approved changes
• Acting to bring expected cost overruns within acceptable limits

---

The Earned Value Technique: The Quantitative Heart of Project Control

Earned Value Management (EVM) is the most powerful analytical tool in the project controller's arsenal. It compares the value of completed project work with both actual costs and scheduled costs to determine the scale of any variances.

The Three Fundamental Variables

Variance Calculations

These three variables produce two critical variance metrics:

Cost Variance (CV) — Are we over or under budget for the work completed?

$$CV = EV - AC$$

• If $CV > 0$: Under budget (favourable)
• If $CV < 0$: Over budget (unfavourable)
• If $CV = 0$: On budget

Schedule Variance (SV) — Are we ahead of or behind schedule?

$$SV = EV - PV$$

• If $SV > 0$: Ahead of schedule (favourable)
• If $SV < 0$: Behind schedule (unfavourable)
• If $SV = 0$: On schedule

Performance Indices

Beyond raw variances, performance indices express efficiency as ratios:

Cost Performance Index (CPI):

$$CPI = \frac{EV}{AC}$$

• $CPI > 1.0$: Getting more value per dollar spent (efficient)
• $CPI < 1.0$: Getting less value per dollar spent (inefficient)

Schedule Performance Index (SPI):

$$SPI = \frac{EV}{PV}$$

• $SPI > 1.0$: Progressing faster than planned
• $SPI < 1.0$: Progressing slower than planned

Forecasting: Estimate at Completion (EAC)

Once current performance is known, EVM allows forecasting the total project cost at completion:

$$EAC = \frac{BAC}{CPI}$$

Where BAC (Budget at Completion) is the total authorised budget for the project.

The Estimate to Complete (ETC) — how much more will be needed — is derived as:

$$ETC = EAC - AC$$

The To-Complete Performance Index (TCPI)

TCPI answers a forward-looking question: what cost performance is needed on remaining work to achieve a target?

$$TCPI = \frac{BAC - EV}{BAC - AC}$$

• $TCPI > 1.0$: Must perform more efficiently than planned on remaining work
• $TCPI = 1.0$: Must maintain current performance
• $TCPI < 1.0$: Can afford to be less efficient on remaining work

EVM Visualised

Planned Value — (PV) — What SHOULD be done

Earned Value — (EV) — What WAS done

Actual Cost — (AC) — What it COST

Cost Variance — (CV)

Schedule Variance — (SV)

Cost Performance — Index (CPI)

Schedule Performance — Index (SPI)

Estimate at — Completion (EAC)

Relationship details

From	Relationship	To
Earned Value — (EV) — What WAS done	EV - AC	Cost Variance — (CV)
Earned Value — (EV) — What WAS done	EV - PV	Schedule Variance — (SV)
Earned Value — (EV) — What WAS done	EV / AC	Cost Performance — Index (CPI)
Earned Value — (EV) — What WAS done	EV / PV	Schedule Performance — Index (SPI)
Cost Performance — Index (CPI)	BAC / CPI	Estimate at — Completion (EAC)

Time →

Cumulative Cost →

SV (EV < PV) — Behind Schedule

CV (AC > EV) — Over Budget

Relationship details

From	Relationship	To
PV1	leads to	PV2
PV2	leads to	PV3
PV3	leads to	PV4
PV4	leads to	PV5
EV1	leads to	EV2
EV2	leads to	EV3
EV3	leads to	EV4
EV4	leads to	EV5
AC1	leads to	AC2
AC2	leads to	AC3
AC3	leads to	AC4
AC4	leads to	AC5
EV4	SV	PV4
AC4	CV	EV4
Time →	leads to	PV1
Cumulative Cost →	leads to	AC5

---

Total Cost Management: The Broader Toolkit

EVM is the centrepiece, but it operates within a larger Total Cost Management (TCM) framework. Lavingia maps the full TCM toolkit across the project lifecycle:

Workstream	Activity	Type	Timing / dependency / duration
Analysis & Estimation	Economic Analysis (NPV, ROR	Activity	active · 0 · 3
Analysis & Estimation	Cost Estimating (Progressive	Activity	active · 0 · 5
Planning & Scheduling	Planning/Scheduling (CPM	Activity	active · 1 · 4
Planning & Scheduling	Benchmarking	Activity	active · 1 · 4
Execution Controls	Performance Measurement (EVM	Activity	active · 3 · 4
Execution Controls	Cost Control/Forecasting (WBS	Activity	active · 3 · 4
Execution Controls	Contracting/Procurement	Activity	active · 2 · 4
Reporting & Audit	Progress Reporting	Activity	active · 3 · 5
Reporting & Audit	Finance/Audit	Activity	active · 4 · 5

Key Insight from Lavingia: The major reason for cost overruns and schedule delays on most projects is scope creep. A structured PMP with management's active participation helps freeze the scope before full funding. Value improving practices optimise that scope. Total cost management then converts the optimised scope into cost and schedule. TCM works downstream of scope management — it cannot compensate for scope failures.

---

Reducing Project Cycle Time

Kul Uppal introduces a complementary concept: project cycle time — the span from team formation to facilities in production. He identifies three drivers that delay project starts and then compress execution:

Uppal's recommendations for reducing cycle time include performing work concurrently rather than sequentially, adding resources to accelerate critical activities, and rescheduling work to exploit time-saving opportunities — all of which require robust monitoring and controlling to avoid introducing new risks.

---

The Pitfalls: Where Monitoring & Controlling Fails

1. EVM is calculated but not acted upon. Calculating CV and SV is meaningless if the numbers are not connected to decision-making authority. EVM outputs must trigger predefined corrective actions.

2. Progress is reported as percentage complete without earned value context. A task reported as "80% complete" tells you nothing about cost performance. Without EV and AC, you cannot distinguish between a task that is 80% done at 60% of budget (excellent) and one that is 80% done at 120% of budget (catastrophic).

3. The baseline is changed to match reality. Re-baselining should be a formal, approved act — not a quiet adjustment to make the reports look better. If the baseline is changed every time a variance appears, the project has no fixed reference point and monitoring becomes theatre.

4. Schedule compression is treated as free. Fast tracking (overlapping activities) and crashing (adding resources) both have costs — financial, quality, and risk. Monitoring should flag the need for compression; control should quantify its consequences before authorising it.

5. Forecasting starts too late. EAC calculations are most valuable when they are produced early and often. By the time a project is 70% complete, the CPI has historically been shown to stabilise — meaning the final cost is largely locked in. If forecasting only begins at 70%, it is too late to change the outcome.

---

Key Takeaways

• Monitoring and controlling spans the entire implementation phase — it is not a late-stage activity.
• The four control processes (scope, schedule, cost, quality) are interdependent. A change in one always affects the others.
• Earned Value Management is the quantitative backbone of project control, using three variables (PV, EV, AC) to calculate variances and forecast final costs.
• The critical formulas are: $CV = EV - AC$, $SV = EV - PV$, $CPI = EV/AC$, $SPI = EV/PV$, and $EAC = BAC/CPI$.
• EVM is only useful if it drives action. Calculate → Interpret → Decide → Act. Without the last step, it is expensive bookkeeping.
• Total Cost Management provides the broader toolkit — but it works downstream of scope management. TCM cannot fix a scope failure.
• Project cycle time can be reduced through concurrency, resource augmentation, and rescheduling — but each requires monitoring to manage the additional risk.

---

Next in the series: Part 4 — Integrated Change Control & Stakeholder Management. When the numbers tell you something needs to change, what happens next? We explore the governance systems that turn variance detection into controlled action — and the human dimension that makes or breaks every change decision.