Working Start something skill
Manage a vendor onboarding
Bring a vendor into service with accepted deliverables, access controls, and accountable ownership.
Procedure
- Confirm executed scope, conditions, owners, milestones, dependencies, and acceptance authority.
- Translate obligations into an onboarding plan covering people, process, technology, data, billing, support, and exit.
- Complete required identity, security, privacy, insurance, tax, banking, and compliance verification through approved owners.
- Grant least-privilege access with named sponsors, expiry, logging, and removal steps.
- Validate configuration, integrations, data transfer, reporting, invoicing, and service contacts in a safe environment.
- Train users and operators, publish support paths, and rehearse failure and escalation.
- Run acceptance checks against requirements and record defects, conditions, and waivers.
- Approve service start only when mandatory evidence and operational ownership are complete.
Guardrails
- Do not let schedule pressure bypass mandatory identity, banking, security, or data checks.
- Never treat contract signature as proof of service acceptance.
- Minimize vendor access and shared confidential information.
--- name: manage-a-vendor-onboarding category: start description: Bring a vendor into service with accepted deliverables, access controls, and accountable ownership. Use when an awarded supplier must move from contract to safe operational use. --- # manage-a-vendor-onboarding ## Procedure 1. Confirm executed scope, conditions, owners, milestones, dependencies, and acceptance authority. 2. Translate obligations into an onboarding plan covering people, process, technology, data, billing, support, and exit. 3. Complete required identity, security, privacy, insurance, tax, banking, and compliance verification through approved owners. 4. Grant least-privilege access with named sponsors, expiry, logging, and removal steps. 5. Validate configuration, integrations, data transfer, reporting, invoicing, and service contacts in a safe environment. 6. Train users and operators, publish support paths, and rehearse failure and escalation. 7. Run acceptance checks against requirements and record defects, conditions, and waivers. 8. Approve service start only when mandatory evidence and operational ownership are complete. ## Guardrails - Do not let schedule pressure bypass mandatory identity, banking, security, or data checks. - Never treat contract signature as proof of service acceptance. - Minimize vendor access and shared confidential information. ## Done - An onboarding plan traces obligations to owners, milestones, controls, and acceptance tests - Access, integration, support, invoicing, and failure-rehearsal evidence is recorded - Authorized service acceptance and remaining conditions are documented