Purpose
Provide one integrated enabling process for operational resilience, technology, software assurance, finance, people, internal control, regulatory reporting, training and Odoo backup governance.
Policies Implemented
- POL-BCM-001 Business Continuity Manual
- POL-IT-001 IT and Cybersecurity Manual
- POL-COTS-001 Commercial Off-The Shelf Software Acceptance and Testing Manual
- POL-FIN-001 Finance and Tax Compliance Manual
- POL-EMP-001 Employee Handbook
- POL-ICA-001 Internal Controls and Audit Manual
- POL-REG-001 Regulatory Reporting and Communication Manual
- POL-TRAIN-001 Training and Awareness Manual
- POL-ODOO-001 Odoo SaaS Backup Policy
Trigger
The process starts when a continuity, technology, software, finance, people, control, reporting, training, backup, incident, change or assurance requirement requires action.
High-Level Flow
Identify enabling or assurance need -> assess criticality and obligations -> plan and approve activity -> execute the applicable procedure -> test and reconcile -> manage incidents and exceptions -> report and assure -> retain evidence and improve.
Inputs
- Business-impact, continuity, technology, security and change information.
- Financial, tax, accounting, reconciliation and reporting information.
- Employee, competence, training, conduct and access information.
- Control testing, audit, regulatory reporting and remediation information.
- Odoo backup, recovery and provider-dependency information.
Outputs
- Resilient, secure and controlled systems and services.
- Complete financial, tax, people and regulatory records.
- Tested continuity, software, backup and recovery capabilities.
- Training, assurance, issue and remediation evidence.
Roles
- Compliance coordinates regulatory alignment, reporting and BCMS traceability.
- Technology owns system, security, change, testing, backup and resilience execution.
- Finance owns accounting, reconciliation, tax and financial reporting activities.
- Management owns people, resources, continuity and remediation decisions.
- Business owners provide evidence and maintain operating controls.
- Independent assurance tests design and operating effectiveness.
Operating Model
This is a primary BCMS process. It links directly to policies, requirements, procedures, controls and systems. It does not contain or depend on subordinate PRC objects. Detailed operating steps remain in the linked PROC objects.
Relationships
- Architecture decision: ADR-003 Flatten Compliance Process Architecture
- Continuity policy: POL-BCM-001 Business Continuity Manual
- IT policy: POL-IT-001 IT and Cybersecurity Manual
- COTS policy: POL-COTS-001 Commercial Off-The Shelf Software Acceptance and Testing Manual
- Finance policy: POL-FIN-001 Finance and Tax Compliance Manual
- Employee policy: POL-EMP-001 Employee Handbook
- Assurance policy: POL-ICA-001 Internal Controls and Audit Manual
- Reporting policy: POL-REG-001 Regulatory Reporting and Communication Manual
- Training policy: POL-TRAIN-001 Training and Awareness Manual
- Odoo backup policy: POL-ODOO-001 Odoo SaaS Backup Policy
Assurance
- Design status: implemented through approved resilience, systems and assurance policies.
- Operating status: inherited from the linked procedures and controls.
- Evidence status: defined in the linked controls and systems.
- Overall status: implemented primary process; operating effectiveness remains subject to linked issues and assurance.
History
- 2026-07-26: Created as one of the five active processes in the flattened BCMS process architecture.