Full Access BCI CBCI Tutorials

The CBCI 7.0 course advises that when establishing a BCMS, an initial focused scope limited to high-value or critical parts of the organization is practical to manage complexity and costs effectively. This allows targeted efforts on areas that pose the greatest risks or have the most significant impact on continuity. Over time, the scope can be expanded as maturity develops. Including everything initially or focusing only on IT disaster recovery limits effectiveness or overcomplicates early efforts, respectively. Crisis management is part of BCMS but not the sole focus of the initial scope.

In PP1 (Establishing a BCMS), defining scope is a foundational activity because it sets clear boundaries for what the BCMS applies to and what it does not. Good practice requires a scope statement that makes coverage explicit (e.g., products/services, sites, functions, legal entities, interfaces, and exclusions) so stakeholders understand the BCMS’s intended reach and so analysis and solutions design are directed appropriately. The GPG 7.0 Lite highlights that BCMS development includes developing the scope and policy, and it emphasizes continual improvement and review—implying scope may need review when organizational context changes. (thebci.org)

Option C captures the definition accurately: scope clarifies what is covered and not covered. Option A is too absolute; you consider relevant suppliers/customers, but scope does not automatically include “all.” Option B is incorrect because scope is reviewed as the organization changes (mergers, delivery model changes, regulatory change). Option D describes the policy, not the scope. Therefore, C is the correct statement.

In CBCI 7.0 (based on BCI GPG 7.0), Validation (PP6) is the professional practice that confirms whether the BCMS meets the objectives set out in policy and whether the organization can actually perform response and recovery as intended. Validation does this through exercising, maintenance, and review, which collectively test and measure real-world performance—how competent individuals are in their roles, how well teams coordinate under pressure, and whether capabilities (plans, tools, procedures, resources) work to the required standard.

Solutions Design (PP4) selects strategies and solutions, but it does not measure competence. Analysis (PP3) identifies requirements (impacts, priorities, targets) and informs what should be validated. Enabling Solutions (PP5) implements solutions and develops response structures and plans, but the act of measuring team cohesiveness and capability effectiveness happens through validation activities—especially exercises and post-activity reviews that identify lessons learned and improvement actions.

During an incident, immediate people-related requirements prioritize life safety, welfare, and accountability. In BC response structures, People/HR (often called People & Culture) typically focuses first on confirming who is affected, ensuring personnel are safe, supporting access to medical/physical care, and establishing reliable communications with staff and (where appropriate) family members. These actions reduce harm and enable leadership to make accurate decisions about escalation and support. This aligns with crisis/incident management good practice where “accounting for people” and welfare support are immediate priorities before broader recovery work is initiated. (ready.gov)

Option C—assigning recovery responsibilities to staff away from the site—is important for recovery enablement, but it is not an immediate care/wellbeing requirement. It belongs more to operational recovery coordination and plan activation once the immediate safety picture is understood. Options A, B, and D are directly tied to immediate welfare: confirm personnel status, contact and support staff/families, and enable access to care. Therefore, C is the correct “NOT immediate requirement” for the People and Culture Management team when the focus is specifically care and wellbeing.