In CBCI 7.0, PP1 – Establishing a BCMS includes defining the BCMS scope and recognizing that BCMS activities are not one-time tasks; they evolve as the organization changes. Scope review is normally triggered by changes that materially affect continuity requirements—such as structural changes, changes to products/services, delivery models, locations, technology, critical resources, or external obligations. A merger (A) can significantly change organizational boundaries, critical activities, and dependency networks, requiring scope reassessment. A change in legal/regulatory requirements (B) can introduce new continuity obligations and thresholds for unacceptable impact, again affecting scope. A change in how products/services are delivered (C)—for example increased outsourcing, new platforms, or new channels—changes dependencies and recovery priorities, often requiring scope review.

Option D is different: appointing a communications manager to run a promotion campaign is not, by itself, a material change to continuity requirements or the operating model of prioritized products and services. Unless it creates a new critical service/dependency (which the option does not state), it would not normally trigger a BCMS scope review.