During a coastal storm season, a coordinator wants to silently rewrite the project’s risk strategy overnight without formal review. What is the appropriate action?
Select an answer to reveal the explanation.
Short Explanation
Changing the risk playbook mid-storm still needs the change-control on-ramp—not a quiet rewrite in a notebook. Governance is how the whole team stays aligned when the plan itself must shift. Document and approve the change.
Full Explanation
Silently rewriting a project’s risk strategy overnight during coastal storm season bypasses governance. The appropriate action is to route the proposed change through change control rather than a unilateral edit. Storm conditions may justify accelerated review, but acceleration is not the same as skipping authorization on a civic project’s approved risk approach.
Allowing a silent rewrite because storms feel urgent normalizes undocumented plan changes and leaves stakeholders working from inconsistent assumptions. Deleting the risk register so updates seem unnecessary destroys the memory of uncertainties the city already identified. Publishing a rewrite only on a personal blog for the crew fails formal communication and change processes entirely.
Exam caveat: CAPM associates should treat strategy and plan updates as controlled changes. Emergencies can compress timelines for review boards or sponsors, yet the change still needs visibility and approval appropriate to organizational procedure.
Operational check: draft the proposed risk-strategy revision, mark it as a change request, convene the accelerated approvers named in the change approach, communicate the approved update, and retire the prior strategy version in the project repository.