Monitoring, Evaluation, and Control
The Monitoring, Evaluation, and Control domain tests whether you can measure performance against intent, distinguish monitoring from evaluation, and take proportionate corrective action.
Core rules
- Monitoring is continuous performance tracking; evaluation is periodic judgment of relevance, effectiveness, efficiency, impact, and sustainability.
- Choose KPIs tied to objectives and outcomes, not just activity counts. Pair leading indicators with lagging results.
- Set tolerances and thresholds in advance; a variance inside tolerance may be managed, not escalated.
- Control is a cycle: measure, compare with baseline, analyze cause, act, and verify.
- Protect baseline integrity. Rebaseline only through approved change, not to hide variance.
- Track benefits after delivery; outputs are not benefits.
Worked example
At mid-point, a project planned 50% completion but is at 40%, while spending is 60% of budget. The variance is not just that spending is high; schedule and cost are both adverse. Investigate root cause, forecast the finish, and choose corrective action such as resequencing, reducing scope through approval, or adding resources with a cost trade-off. Do not report green status because the team is busy.
Traps that cost marks
Measuring activity as outcome; changing the baseline to make variance disappear; treating a threshold breach as automatically fatal; and confusing evaluation with audit. Evaluation asks whether the intervention worked and why; audit checks compliance and evidence.
Exam habit
State the metric, baseline, actual, variance, threshold, cause, action, owner, and date. That chain is the control story exam questions reward.