Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example
BCP-004 — Key person unavailability plan

History

What is live now, and every settled version, newest first.

Current

This version cannot be attributed to anyone.

Plan

Response steps

  1. The line manager tells the Chief Operating Officer when a colleague who holds a key responsibility will be away for more than three working days.
  2. The Chief Operating Officer names a deputy from the Roles register, and the ISMS Manager checks that the deputy has the access the work needs.
  3. The absent colleague's open tickets, changes, and incidents are handed over in the ticketing system, with a note on anything that is waiting for a customer.
  4. Passwords and keys held by one person alone are moved to the shared credential vault.
  5. When the colleague returns, the deputy hands the work back and the line manager records what was learned.
Code
BCP-004
Scenario
KeyPersonLoss
Title
Key person unavailability plan

Are you sure?

This action cannot be reverted.

Leave this page?

Your changes on this form are not saved. If you leave, they are lost.