Skip to content
Back to the Handbook
Free direct downloadResilienceSecurityDORA & NIS2

Exit Kit Starter

Record ownership, architecture, handover evidence and supplier-exit questions before a dependency becomes lock-in.

Download the ZIPSee the files

No account and no email needed. An optional email copy is below.

How to use it

How to use this pack

A neutral starter for documenting who owns the accounts, data, code, billing and recovery paths around a service. It adds a dependency map, evidence checklist and supplier questions so transferability is designed before exit day.

  1. Fill exit-kit-template.md for one service you depend on.
  2. Draw its accounts, data and suppliers in system-context-template.md.
  3. Ask the supplier-exit questions before you sign or renew.

Before you rely on it

Contract, data-protection and regulatory exit duties require legal and environment-specific review.

Want a copy in your inbox?

Optional email delivery makes the link easy to recover. You can download above without submitting anything.

Used only to fulfil this request. Read the privacy notice.

Published by Michal Jatczak, trading as ITSailor.SHA-256 for this pack