Describe the typical change-management process for SOPs.

• A. Identify need, implement immediately, archive old versions, notify none.
• B. Identify need, assess impact, draft revision, impact/risk analysis, approvals, implement, train, communicate, and archive previous versions.
• C. Skip assessment; implement changes directly; discard old SOPs.
• D. Change-management is only for IT systems.

Answer: (B)

Managing changes to SOPs relies on a structured change-management approach that keeps updates controlled, justified, and understood by everyone affected. The best answer captures a complete flow: identify the need for a change and assess its impact, draft the revision, perform an impact or risk analysis, obtain the necessary approvals, implement the change, train users, communicate the update, and archive the previous version for an auditable record. This sequence ensures that updates are warranted, properly vetted, and effectively rolled out, with clear visibility into what changed and why.

Skipping assessment or governance, or implementing changes without training and communication, leads to unmanaged updates, higher risk of noncompliance, and inconsistent practices. Treating change-management as only an IT concern ignores the broader need for control and clarity across all SOPs.