# OpenVMO vendor intake form

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

Eight questions to answer before signing up to a new vendor. The answers create its register entry and tier (practices INT-1 and TIER-1). Use it as a shared form that writes to your register.

| # | Field | Notes |
| --- | --- | --- |
| 1 | **Requester** | Who is asking. |
| 2 | **Vendor** | Company name and website. |
| 3 | **Purpose** | What we will use it for, in one or two sentences. |
| 4 | **Data (rubric Q1)** | What data will it see or hold? None or public / internal or employee data / customer production, special-category data or secrets. |
| 5 | **Access (rubric Q2)** | What access will it get? None / ordinary sign-on users or read-only / admin, production or API write. |
| 6 | **Criticality (rubric Q3)** | If it disappeared tomorrow: mild inconvenience / internal disruption with a workaround / customers affected or we cannot operate. |
| 7 | **Estimated spend** | Per year, with currency. Include free plans as zero. |
| 8 | **Business owner** | The person who will answer for this vendor. Usually the requester's manager or team lead. |

## After submission

1. The vendor management lead tiers the vendor with the rubric (also asking rubric Q4 and Q5).
2. Approvals follow the tier (INT-2): owner only for Tier 3; plus security and privacy for Tier 1 and 2; plus finance above the spend threshold.
3. Checks for the tier are completed (DD-1 to DD-3) **before** any data or access is given (INT-3).
4. The register entry is completed and the vendor set to active.