Plans do not run themselves. When a typhoon signal is raised, or a system fails, specific people must decide, act and communicate. This chapter explains how Sands China Ltd (SANDS) can compose its BCM team, from the executive sponsor to resort and department coordinators, and how responsibilities are shared.
Chapter 5 recorded the planning assumptions. Chapter 6 addresses clauses 5.3 (roles, responsibilities and authorities), 7.2 (competence) and 7.3 (awareness) of ISO 22301:2019. All role titles and structures below are hypothetical proposals, since SANDS' internal organisation is not public.
Two further principles apply. First, BCM roles should map to the existing organisation rather than create a parallel hierarchy. Second, every role needs a named alternate, because the person who holds a role may be unavailable in an emergency, for example, when a typhoon prevents travel.
SANDS' size and the number of resorts suggest a layered model: a central team that sets the framework, and local coordinators at each resort and key departments who adapt it. This approach lets SANDS keep one standard while respecting the differences between a hotel, a convention hall and a ferry operation.
The structure below is illustrative. SANDS' leadership can adjust it to fit its existing governance.
An executive sponsor on the senior leadership team provides visible commitment, as clause 5.1 requires. A steering committee of senior leaders from operations, technology, finance, legal and compliance, human resources and security approves the policy, the scope and the assumptions register, and reviews performance. For example, the committee might meet quarterly in the first year and twice a year afterwards.
The organisation-wide BCM coordinator runs the programme day to day. This person maintains the methodology, supports analysis, tracks actions and reports to the steering committee. A small central team, which could include a risk specialist and a communications liaison, supports the coordinator.
Each resort and each critical business function (CBF) owner nominates a coordinator who maintains local plans, takes part in exercises and reports status. These coordinators link the central framework to the gaming floor, the hotel front desk, or the engineering control room.
When an incident occurs, a different structure activates. An incident response team at each resort manages the immediate event, while a crisis management team at group level handles decisions on closures, regulator contact, media and investor communication. Chapter 8 describes how these teams fit into the planning methodology, and eBook 2 develops their plans.
Clause 7.2 requires the organisation to determine the competence needed by people who affect BCM performance and to take action where gaps exist. Clause 7.3 requires that people doing work under the organisation's control are aware of the policy and their role.
For example, the BCM coordinator could hold a recognised ISO 22301 implementer qualification, while resort coordinators receive shorter training on analysis and exercises. Team members across the organisation need basic awareness: what to do when a closure order arrives, where to assemble and how they will be contacted.
Cybersecurity roles deserve a separate note. Macao's Cybersecurity Law (Law No. 13/2019) [verify] reportedly requires critical infrastructure operators to appoint a responsible person and a substitute with the necessary experience and Macao residence. SANDS' BCM structure should connect to that role so incident response is coordinated.
A responsibility matrix removes doubt about who does what. It uses four letters: R for responsible, A for accountable, C for consulted and I for informed. The matrix in Table 6 is an illustrative starting point.
A steering committee works best when its mandate is written down. Terms of reference should set out its purpose, membership, quorum, meeting frequency, decision rights and reporting line. For SANDS, the committee would approve the business continuity policy, scope, assumptions register and exercise programme, and review performance against the objectives in Chapter 4.
The terms should also say what the committee does not do. It does not run incidents; that belongs to the crisis management team. Keeping the roles distinct avoids confusion when an event occurs and the same executives wear two hats.
Disruptions often remove the people plans depend on. A typhoon that halts transport can prevent a coordinator from reaching work, and an infectious disease can reduce a whole team. Every BCM role at SANDS should therefore have at least one trained alternate, ideally based at a different location or on a different shift.
The BCM coordinator can keep an alternates list as part of the responsibility matrix, with contact details held in the notification system. For example, if the head of engineering at one resort is unavailable, a named deputy takes over the CBF-9 and CBF-10 responsibilities until the owner returns. Alternates should attend exercises so that they are ready to act, not meeting the plan for the first time in an emergency.
Not every incident needs the full structure. A graded model lets SANDS match its response to the event. The levels below are illustrative.
Clear triggers for each level prevent both under-reaction and over-reaction. They also tell people when to alert the regulator and the executive sponsor. Chapter 8 places the incident response structure within the planning methodology, and eBook 2 builds the detailed plans.
A central team cannot run BCM alone. Resort and department coordinators bring the practical knowledge, but they also have full-time jobs. To keep them engaged, SANDS can agree a time allowance for BCM work, recognise the role in performance reviews and give coordinators early access to training and tools.
Regular coordinator meetings also help. A monthly call or forum in the first year lets resorts share what they have learned, compare progress and raise obstacles. Sharing is particularly valuable across SANDS' interconnected resorts, where one resort's solution to a problem, such as a flood barrier procedure, may suit the others.
Table 6: Composing BCM Team for Sands China Ltd
| Role (hypothetical) | Main responsibilities | Policy and scope | Analysis and plans | Exercises | Incident response |
|---|---|---|---|---|---|
| Executive sponsor | Visible commitment, resources, decisions | A | I | I | A |
| Steering committee | Approve policy, assumptions, scope; review results | R | C | I | C |
| BCM coordinator | Run programme, methodology and reporting | R | A | A | C |
| CBF owners | Own analysis and plans for their function | C | R | R | R |
| Resort coordinators | Maintain local plans, run local exercises | I | R | R | R |
| Crisis management team | Strategic decisions and external communication | I | C | C | A |
| Human resources | Training, competence and team member welfare | C | C | C | R |
| Legal and compliance | Regulator and listing obligations | C | C | I | R |
The structure, titles and letters are illustrative and require confirmation by SANDS.
A layered BCM team lets SANDS combine executive authority with local knowledge. Named alternates, defined competence and a clear responsibility matrix make the programme resilient to the absences that disruptions often cause. Once SANDS confirms its structure, the team can begin work on context and methodology.
The next chapter looks outward, analysing the operating environment in which this team will work.
Continue reading: Chapter 7, Analysing Operating Environment for Sands China Ltd, examines the political, economic, social, technological, legal and environmental factors that shape SANDS' continuity needs, along with its interested parties.
| eBook 1: Understanding Your Organisation | |||||
| C1 | C2 (x) | C3 (x) | C4 (x) | C5 (x) | C6 (x) |
| C7 (x) | C8 (x) | C9 (x) | C10 | C11 (x) | C12 (x) |
To learn more about the course and schedule, click the buttons below for BCM-300 Business Continuity Management Implementer [BCM-3] and BCM-5000 Business Continuity Management Expert Implementer [BCM-5].
|
Please feel free to send us a note if you have any questions. |
||