# OpenVMO offboarding checklist

OpenVMO v1.0 · Licence: CC BY 4.0 · https://vendorapp.co/openvmo/offboarding/

Run this every time a vendor relationship ends (practice EXIT-1). Save the completed copy with the vendor's records. Each step needs evidence, not just a tick.

| Vendor | Owner | Reason for ending | Last day of service |
| --- | --- | --- | --- |
| | | | |

| # | Step | Done (date) | Evidence |
| --- | --- | --- | --- |
| 1 | User accounts and single sign-on access removed | | |
| 2 | API keys, tokens and service accounts revoked | | |
| 3 | Webhooks, integrations and network access removed | | |
| 4 | Data return requested and received (if you need the data) | | |
| 5 | Data deletion requested | | |
| 6 | **Data deletion confirmed in writing by the vendor** | | |
| 7 | Final invoices settled and recurring payments cancelled | | |
| 8 | Equipment, documents and other assets returned | | |
| 9 | Confidentiality obligations reaffirmed, if the contract requires it | | |
| 10 | Register updated: state set to offboarded, with the date, the reason and a link to this checklist | | |

Do not delete the vendor from the register. The offboarded entry is the record an auditor will ask for.