Content Comparison

...

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

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 /wiki/spaces/VERTIC/pages/1784905730) 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)