Ready reckoner
Clause map
| Clause | Requirement in one line | Key output |
|---|---|---|
| 4.1 | External + internal issues; is climate change relevant? (Amd 1:2024) | Context register |
| 4.2.1 | Interested parties + their requirements + which the BCMS addresses | Parties register |
| 4.2.2 | Process to identify, access, assess legal/regulatory requirements; documented, kept current | Regulatory register |
| 4.3 | Scope: products/services, parts of organisation, exclusions explained; documented | Scope statement |
| 4.4 | Establish, implement, maintain, improve the BCMS and its processes | Process map / manual |
| 5.1 | Leadership: strategy fit, integration, resources, communication, direction | Minutes, budgets, participation |
| 5.2 | Policy: fits purpose · objective framework · meet requirements · continual improvement | 2–3 page policy |
| 5.3 | Roles, responsibilities, authorities; reporting on performance | RACI, terms of reference |
| 6.1 | Risks & opportunities to the BCMS → actions → evaluate | RO register |
| 6.2 | Measurable objectives; what · resources · who · when · how evaluated | Objectives plan |
| 6.3 | Plan changes to the BCMS | Change criteria |
| 7.1–7.5 | Resources · competence · awareness · communication · documented information | Matrix, records, controlled docs |
| 8.1 | Plan and control processes including outsourced | Criteria, evidence |
Issues vs risks
Issue = condition or trend ("one cloud region"). Risk scenario = event + consequence ("region outage stops collections 24 h"), assessed in 8.2.3.
Regulatory register columns
Source + version · why it applies (direct / flow-down / voluntary) · requirement · BCMS element · owner · evidence · last checked. Review at least quarterly in BFSI.
Scope statement — five parts
- Products and services · 2. Locations (incl. cloud regions) · 3. Activities and teams · 4. Exclusions with reasons · 5. Interfaces and dependencies.
Traps: IT-only scope · excluding something critical services depend on · certificate scope that misleads customers.
Critical operations
Screen every product/service: customer harm · market/system harm · viability · regulatory naming → board-approved list → tolerance → map → test.
| Regime | Term |
|---|---|
| Basel, RBI | Critical operations |
| UK | Important business services |
| DORA | Critical or important functions |
| SEBI CSCRF | Critical systems (IT supporting core business) |
Granularity: something an external user experiences and that can take a time limit ("borrowers can pay EMIs and see them posted").
Governance
Board (policy, critical ops, tolerances) → committees (RMC; ITSC / IT committee; ISRMC for insurers) → steering group → executive owner → BCM manager → plan owners · crisis team · recovery teams · coordinators. 2nd line challenge (op. risk, CISO); 3rd line audit.
Objectives — weak vs strong
| Weak | Strong |
|---|---|
| Improve continuity | Tier 1 recovered within RTO in each half-yearly drill |
| Run exercises | Every critical operation exercised yearly; ≥ 90% actions closed on time |
| Comply with RBI | Customer cyber notice ≤ 2 h in 100% of cases |
Support essentials
- 7.3 awareness includes each person's role before, during and after a disruption.
- 7.4 = routine BCMS communication; 8.4.3 = warning and communication in a disruption.
- Plans: offline · off-site · current contacts · classified · checklists · accessible without SSO.
Documented information typically required: scope · legal register · policy · objectives · competence evidence · BIA and risk results · plans · exercise and evaluation results · monitoring · audit programme and results · management review · nonconformities.