/
Information Continuity Plan and Process

Information Continuity Plan and Process

This page outlines the process and procedures to ensure we can continue to operate as an organisation in case of disaster such as hardware loss, office closure, or a global pandemic. In general, Vertic works exclusively in cloud-based services and no local data is stored nor critical to be stored locally on laptops. This means, Vertic employees can be up and running relatively quickly in case of an outage, such as the one mentioned.

Hardware Loss

In case of hardware loss, which could include work laptops breaking down or being stolen, the following steps must be taken to ensure continuity:

  1. Notify the COO (@Matt Romeo) of this scenario via either Email or Slack.

  2. Place an order for a replacement laptop at MacBook Pro (@Jan Tenenberg to approve this order)

  3. Once received, perform the following steps:

    1. Install Google Chrome from https://www.google.com/intl/en_au/chrome/

    2. Log into your Vertic Google Account within the Chrome browser; this will provide immediate access to:

      1. Email

      2. Online Documents including GoogleDocs and GoogleSheets (which we use exclusively for any documentation)

    3. Install and sign in Bitwarden from Download the Bitwarden Password Manager App for iPhone, Android, Chrome, Safari, and More | Bitwarden to gain access to:

      1. Your stored passwords to various online services

    4. Install Slack from https://apps.apple.com/us/app/slack/id618783545 to gain access to:

      1. Vertic’s organisation chat and collaboration platform

    5. Send the Serial Number of the new laptop to @Jan Tenenberg to update the Vertic Asset Register

  4. Test the newly configured laptop setup by using the following steps:

    1. Send an email to @Matt Romeo confirming the new work laptop

    2. Send a Slack message to @Matt Romeo confirming the new work laptop

Switching to Remote Working Location

In case of the office being unavailable for a range of reasons, the following steps must be taken to ensure continuity:

  1. Notify the COO (@Matt Romeo) of this scenario via either Email or Slack.

  2. Select an appropriate remote working location, such as Home (preferred) or a temporary shared office space like https://www.coworkme.com.au/

  3. Ensure all physical security compliance requirements are met as per our Physical Security Policy

  4. Notify the COO (@Matt Romeo) of the selected remote working location.

Software Unavailability

In case of a software service Vertic utilises (such as Salesforce) becoming unavailable, the following steps must be taken to ensure continuity:

  1. Notify the COO (@Matt Romeo) of this scenario via either Email or Slack.

  2. Notify the software provider (such as Salesforce) to gain an understanding of the issue via their online channels, including:

    1. Salesforce Customer Support

    2. Atlassian Customer Support

    3. Google Customer Support

  3. Contact all clients you manage to let them know of this scenario via Email

The unavailability of online software services will effectively stop Vertic from continuing to operate smoothly; it is likely that we will experience an outage but no data loss.

Staff Illness or Accident

In case of staff illness or unavailability, the following steps must be taken to ensure continuity:

  1. Notify the COO (@Matt Romeo) of this scenario via either Email or Slack.

  2. Navigate to the project budget sheet and familiarise yourself with the Statement of Work to understand project scope

  3. Navigate to the Project Jira project and familiarise yourself with all tickets marked as To Do, In Progress, Internal Review

  4. Navigate to the Project Confluence space and familiarise yourself with all relevant pages to continue the project delivery

  5. Connect with key client contacts (this can be found in the project status pages) and arrange an initial meeting to discuss the following:

    1. Handover to yourself

    2. Your understanding of the project so far and going forward

    3. Confirm your understanding of the project scope

    4. Agree on next steps (which may potentially include a timeline extension)

  6. If any issues are encountered, involve either the COO (@Matt Romeo) or CEO (@Jan Tenenberg)

 

The most recent evidence for the above procedures can be found here.

 

Related content

Supplier Due Diligence Assessment (Template)
Supplier Due Diligence Assessment (Template)
Read with this
Vertic Employee Off boarding Process
Vertic Employee Off boarding Process
More like this
Information Security Policy for Supplier Relationships
Information Security Policy for Supplier Relationships
Read with this
Resource Planning and Management Process
Resource Planning and Management Process
Read with this