5.2. Plan and Manage Project Compliance
💡 First Principle: Compliance spans far more than regulatory checkboxes — security, health and safety, and sustainability are explicitly named alongside regulatory compliance in the 2026 ECO, and this task tests whether you can classify a compliance requirement correctly and act proportionally to its risk.
Enablers: confirm project compliance requirements (security, health and safety, sustainability, regulatory), classify compliance categories, determine potential threats to compliance, use methods to support compliance, analyze the consequences of noncompliance, determine the necessary approach/actions, and measure the extent of compliance.
Classifying compliance categories correctly drives everything downstream: a security-compliance gap and a sustainability-compliance gap warrant very different remediation approaches, different stakeholders, and different urgency — treating all compliance issues with one generic response process misses this task's intent.
⚠️ Exam Trap: Treating "compliance" as synonymous with "regulatory/legal" only. A scenario describing an unaddressed workplace-safety risk or an unmanaged sustainability commitment is still testing this task, even without a regulator in sight.
Reflection Question: Name a compliance requirement from a past project that wasn't purely regulatory (security, safety, or sustainability-driven instead). How was it classified and who owned the response?
