Business Continuity and Disaster Recovery Plan
Authoritative document
- Link to PDF or official URL: TBD
Ownership
| Field | Value |
|---|---|
| Owner | Takayuki KIKUCHI |
| Last reviewed | 2026-4-13 |
Purpose
The purpose of this business continuity plan is to prepare Rendering Consulting Inc in the event of service outages caused by factors beyond our control (e.g., natural disasters, man-made events), and to restore services to the widest extent possible in a minimum time frame.
Scope
All Rendering Consulting Inc IT systems that are business critical. This policy applies to all employees of Rendering Consulting Inc and to all relevant external parties, including but not limited to Rendering Consulting Inc consultants and contractors. In the event of a loss of availability of a hosting service provider, the CEO will determine an appropriate response strategy.
General requirements
In the event of a major disruption to production services and a disaster affecting the availability and/or security of the Rendering Consulting Inc office, senior managers and executive staff shall determine mitigation actions. A disaster recovery test, including a test of backup restoration processes, shall be performed on an annual basis.
Alternate work facilities
If the Rendering Consulting Inc office becomes unavailable due to a disaster, all staff shall work remotely from their homes or any safe location.
Communications and escalation
Executive staff and senior managers should be notified of any disaster affecting Rendering Consulting Inc facilities or operations. Communications shall take place over approved channels such as Slack and/or email. Key communication contacts are maintained in this list: Key Contacts List
Roles and responsibilities
| Role | Responsibility |
|---|---|
| CEO | The CEO shall lead all BC/DR efforts, including mitigation of losses and recovery of corporate network and information systems. The CEO shall be responsible for all internal communications to employees, external and client communications regarding any disaster or business continuity actions, and any actions needed to maintain continuity of business functions and Rendering Consulting Inc services to customers. The CEO shall also be responsible for the physical health, safety, and security of all staff during a disaster event. In the event that the CEO delegates responsibilities to contractors or external parties, such delegation shall be documented. |
Continuity of critical services
Procedures for maintaining continuity of critical services in a disaster can be found in Appendix A. Recovery Time Objectives (RTO) and Recovery Point Objects (RPO) can be found in Appendix B. Strategy for maintaining continuity of services can be seen in the following table:
| Key business process | Continuity strategy |
|---|---|
| Customer (Production) Service Delivery | Rely on Azure availability commitments and SLAs |
| IT Operations | Not dependent on a physical office. All IT operations are cloud-based and accessible remotely. Critical systems and data are hosted across cloud service providers including Microsoft Azure, GitHub, and Google Workspace, each providing georedundant infrastructure and backed by their respective service level agreements. |
| Utilize Gmail and its distributed nature, rely on Google's standard service level agreements. | |
| Finance, Legal and HR | All systems are vendor-hosted SaaS applications. |
| Sales and Marketing | All systems are vendor-hosted SaaS applications. |
Plan activation
This BC/DR shall be automatically activated in the event of the loss or unavailability of the Rendering Consulting Inc office, or a natural disaster (i.e., severe weather, regional power outage, earthquake) affecting the larger Shibuya, Tokyo, Japan region.
Appendix A - Business continuity procedures by scenario
Business Continuity Scenarios
HQ Offline (power and/or network)
- CRM, Telephony, Video Conferencing/Screen Share & Corp Email unaffected
- CEO and HQ Staff offline (30-60 minutes)
- Remote Staff unaffected
Procedure:
- CEO and HQ Staff relocate to home offices (30-60 minutes)
- Verify Telephony, CRM, & Email Connectivity at home offices (10 minutes)
- Remotely resume normal operations
Disaster Event at HQ
- CRM, Telephony, Video Conferencing/Screen Share & Corp Email unaffected
- CEO and HQ Staff offline (variable impact)
- Remote Staff unaffected
Procedure:
- Activate Remote Staff
- Notify Customer Base of impaired functions & potential delays
- CEO assumes all critical response functions directly
SaaS Tools Down
- CRM, Telephony, Video Conferencing/Screen Share, or Corp Email Affected
- CEO and HQ partially affected (no new cases, manual triage required)
- Remote Staff unaffected
Procedure:
Telephony Down
- Notify Customer Base to use Email for support inquiries
- CEO uses mobile phone as needed
Email Down (Gmail/Corp Email)
- CEO manually manage 'case' related communications
- CEO use alternate email accounts as needed (e.g., Outlook)
CRM Down
- Notify Customer Base that CRM is down
- Activate 'Spreadsheet' Case Tracking (Google Sheets)
Video Conferencing/ScreenShare Down (Zoom)
- CEO utilizes alternate service as needed (e.g., Google Meet)
Appendix B - RTOs/RPOs
| Rank | Asset | Affected Assets | Business Impact | Users | Owners | Recovery Time Objective (RTO) | Recovery Point Objective (RPO) | Comments / Gaps |
|---|---|---|---|---|---|---|---|---|
| 1 | Azure Data Center | Production | Core services | All | CEO | 48 hours | 24 hours | |
| 2 | Google Workspace | Email, Docs, Collaboration | Communication and collaboration | All | CEO | 4 hours | 1 hour | |
| 3 | GitHub | Source code | Development continuity | CEO | CEO | 4 hours | 1 hour | |
| 4 | Corporate Office | Site | Site | All | CEO | 2 hours | N/A | Remote work fallback applies |
| 5 | Corporate Network | Network | Network access from office | All | CEO | 2 hours | N/A | Cloud tools unaffected |
| 6 | freee | Accounting | Financial operations | CEO | CEO | 24 hours | 24 hours | |
| 7 | Pipedrive CRM | CRM | Sales operations | CEO | CEO | 24 hours | 4 hours | |
| 8 | Company Laptops | Hardware | Staff productivity | All | CEO | 24 hours | N/A | |
| 9 | Personal Mobile Device | Hardware | Communication backup | All | N/A | N/A | N/A | Used as fallback for telephony |