Introduction
Every continuity plan rests on assumptions, whether anyone writes them down or not. A plan that assumes all staff can reach the hospital, or that power returns within an hour, will fail the first time reality differs. For Eastern General Hospital (EGH), stating assumptions openly lets leaders challenge them before an incident does.
Chapter 4 set measurable objectives. This chapter records seven planning assumptions, A1 to A7, and shows how to test each one. The assumptions relate to the risk and impact work in clauses 6.1 and 8.2 of ISO 22301:2019. They also reflect that Singapore has no national BCM policy for hospitals, so EGH must justify its own assumptions to the Ministry of Health (MOH), SingHealth and its own board. All values below are illustrative.
Why Assumptions Matter
An assumption is a condition treated as true for planning purposes. Planners need them because the future is uncertain, but they also hide risk. If an assumption proves wrong, every plan built on it is weakened at once.
A good assumption is specific, realistic, owned and testable. It also states the consequence if it fails. For a hospital still under construction, assumptions should be marked as provisional and reviewed at each phase of opening.
Seven Planning Assumptions for EGH
A1: Workforce
A large share of staff may be absent for an extended period, for example during a pandemic wave or a transport disruption. EGH might plan for a stated percentage of absence and test whether minimum safe staffing for emergency, critical care and theatres can still be met. Cross-trained staff and secondments within SingHealth are likely mitigations.
A2: Premises
Part of the campus may become unusable, for example through a fire, flood or contamination event. SingHealth states that areas of the campus can be closed off to limit pathogen spread and that spaces can be converted quickly, so EGH might assume it can continue with reduced capacity rather than lose a whole building.
A3: Utilities
Mains electricity, water, telecommunications or medical gas supplies may fail. Backup systems exist only for a limited period. EGH should assume that backup power and water cover the most critical areas first and have defined run times that are tested regularly.
A4: Technology
Core clinical systems, such as the electronic medical record, may be unavailable for an extended period. Staff should have downtime procedures and paper forms for the most critical activities. For EGH, whose Smart Hospital Roadmap promotes digital care, this assumption deserves extra attention because dependence grows with every new platform.
A5: Suppliers and shared services
Key suppliers or shared SingHealth services may fail or be delayed. EGH should assume that stocks of critical medicines, consumables and sterile supplies must last until alternatives are secured, and that some services provided by the cluster may not be available at the moment of need.
A6: Patient demand
Demand may rise during a disruption. A pandemic, a mass-casualty event or a neighbouring hospital's outage could bring more patients than normal. EGH should assume that its capacity to transfer patients to other SingHealth institutions or to Eastern Community Hospital is limited and takes time to arrange.
A7: External support
Help from MOH, SingHealth and emergency services is available but not immediate. EGH should assume that it must sustain itself for an initial period before external support arrives.
Assumptions Specific to the Opening Phase
The seven assumptions above apply to any hospital. EGH also faces assumptions that come from its own stage of development. These should be recorded in the same register and marked as temporary.
- Build quality: buildings and systems handed over will perform as designed. In practice, early defects are common, so plans should allow for repairs after handover.
- Staff familiarity: staff will know their way around a new hospital. In practice, new teams take time to learn layouts, equipment and routines, which affects response times.
- Cluster support: other SingHealth institutions can lend support while EGH grows. In practice, they will face their own demands during a cluster-wide event.
- Digital readiness: new platforms will be stable from day one. In practice, systems often need weeks of tuning, and downtime procedures should be ready from the start.
Treating these as assumptions makes them visible. A project manager who sees "digital platforms will be stable from day one" on a risk and assumptions register is more likely to ask for a rollback plan.
What a Good Assumptions Register Contains
A register should be short enough to be read and detailed enough to be used. For each assumption, EGH might record a reference, a plain statement, the owner, the evidence behind it, how and when it was last tested, the plans that depend on it, the consequence if it fails and the next review date. The register should also note who approved it. Approval matters because some assumptions, such as the level of staff absence to plan for, are policy choices and not facts.
Assumptions should connect to other documents. The business impact analysis will use A1 and A3 when it estimates how long a service can run with fewer people or with backup power. The risk register in Chapter 9 will use A4 and A5 when it rates cyber and supplier risks. When an assumption changes, the owner should check which of these documents also need updating.
Testing and Maintaining Assumptions
Assumptions should be tested through the business impact analysis, workshops and exercises. For example, an exercise that removes electronic records for several hours tests A4 directly. A table-top exercise in which a supplier fails tests A5.
A register should record each assumption, its owner, how it was validated, when it was last reviewed and what the consequence is if it fails. Assumptions should be reviewed at each phase of opening, after every significant incident and at least annually.
Summary Table
Table 5: Determining BCM Assumptions for Eastern General Hospital
| Ref | Assumption | If it proves wrong | How EGH might test it |
|---|---|---|---|
| A1 | Large staff absence for an extended period | Unsafe staffing in critical areas | Staffing scenario in the BIA; cross-training review |
| A2 | Part of the campus unusable | Loss of capacity larger than planned | Table-top exercise on closing a ward block |
| A3 | Utilities fail, backup is limited | Loss of life-supporting equipment | Backup run-time tests |
| A4 | Core clinical systems unavailable | Delayed care, medication errors | Downtime exercise with paper procedures |
| A5 | Suppliers or shared services fail | Shortage of critical supplies | Supplier review; stock-cover check |
| A6 | Demand rises, transfers are limited | Overcrowding, delays | Surge exercise with SingHealth and ECH |
| A7 | External help is not immediate | Unsupported initial response | Incident exercise with agreed arrival times |
All assumptions are illustrative and subject to EGH's own approval.
Conclusion
Seven assumptions give EGH a shared, challengeable starting point for planning. Each names a consequence and a test, which moves the discussion from opinion to evidence. As the campus opens in phases, EGH should expect some assumptions to change and should record the reason each time.
The next chapter asks who will own these assumptions and run the programme: the BCM team.
Sources
Continue reading: Chapter 6, Composing BCM Team for Eastern General Hospital, explains who should sit on EGH's BCM team, from the governing body to the shift staff.
Keeping Care Running: Managing and Implementing Business Continuity Management at Eastern General Hospital |
|||||
| eBook 1: Understanding Your Organisation | |||||
| C1 | C2 | C3 | C4 | C5 | C6 |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
| C7 | C8 | C9 | C10 | C11 | C12 |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |





![[BCM] [EGH] [E1] [C1] Overview of BCM Case Study](https://no-cache.hubspot.com/cta/default/3893111/4fadfc5a-aaef-4a8d-9e12-73a4962607a3.png)
![[BCM] [EGH] [E1] [C2] Understanding Your Organisation](https://no-cache.hubspot.com/cta/default/3893111/91481e02-5830-45d2-9792-b5ac62d31648.png)
![[BCM] [EGH] [E1] [C3] Establishing Organisational Goals](https://no-cache.hubspot.com/cta/default/3893111/2399832a-3fa8-4392-b904-dbac8a9394ce.png)
![[BCM] [EGH] [E1] [C4] Establishing Business Continuity Objectives](https://no-cache.hubspot.com/cta/default/3893111/ff56e4d3-ce31-4bcb-b4dc-c2dad8dc1d66.png)
![[BCM] [EGH] [E1] [C5] Determining BC Assumptions](https://no-cache.hubspot.com/cta/default/3893111/af5d7f28-5791-4e05-97c4-d1247b775a7f.png)
![[BCM] [EGH] [E1] [C6] Composing BCM Team](https://no-cache.hubspot.com/cta/default/3893111/d161235c-fffb-4a81-bb52-bcb5062d58ac.png)
![[BCM] [EGH] [E1] [C7] Analysing Operating Environment](https://no-cache.hubspot.com/cta/default/3893111/33fefd15-96cd-48e5-84c5-cc7612cf3246.png)
![[BCM] [EGH] [E1] [C8] Implementing the BCM Planning Methodology](https://no-cache.hubspot.com/cta/default/3893111/9f97be88-5011-40d8-8391-83e0dced4dba.png)
![[BCM] [EGH] [E1] [C9] Assessing Risks and Threats](https://no-cache.hubspot.com/cta/default/3893111/eaf1e003-d44e-438b-9bc3-f44711c2beed.png)
![[BCM] [EGH] [E1] [C10] Identifying Critical Business Functions](https://no-cache.hubspot.com/cta/default/3893111/cb4749ae-a696-4d2c-b505-28e05a8f4091.png)
![[BCM] [EGH] [E1] [C11] Summary](https://no-cache.hubspot.com/cta/default/3893111/d050e49a-b47b-4b63-90d2-2b49d7ef1a23.png)
![[BCM] [EGH] [E1] [C12] Back Cover](https://no-cache.hubspot.com/cta/default/3893111/8a1f3bea-63cc-48bd-81e4-a58d1f2347f9.png)





