CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Corrective action realigns current project performance with the approved plan. When a variance is detected (e.g., behind schedule, over budget), corrective actions (crashing, fast tracking, re-estimating, adding resources) are taken to bring performance back in line. Preventive actions address future potential problems; corrective actions address current deviations.

**Why not A:** Actions taken to prevent future problems that have not yet occurred describe preventive actions, not corrective actions. Preventive actions are proactive measures to avoid potential issues, while corrective actions are reactive measures to fix current deviations from the plan.

**Why not B:** Adding features beyond the original scope is scope creep or a scope change, not corrective action. Corrective actions address deviations from the plan to bring performance back in line — they do not expand what the project delivers.

**Why not D:** Changing the baseline to reflect actual performance is re-baselining, not corrective action. Corrective action aims to bring performance back to the existing baseline, while re-baselining accepts the deviation and creates a new reference point. These are fundamentally different responses to variance.