prepare-a-vendor-kickoff

# prepare-a-vendor-kickoff Use the executed agreement and approved changes as the commercial baseline. ## When to use - Use before delivery, implementation, onboarding, migration, or managed service work starts. - Do not grant production or sensitive access before approved need, controls, and ownership are verified. ## Procedure 1. Confirm executed contract, statement of work, scope, deliverables, assumptions, exclusions, dates, pricing, and change process. 2. Identify sponsors, delivery leads, decision rights, approvers, escalation paths, and meeting cadence. 3. Map responsibilities, dependencies, client inputs, third parties, environments, and acceptance evidence. 4. Review security, privacy, confidentiality, accessibility, safety, compliance, data, subcontractor, and records obligations. 5. Plan access, identity, onboarding, least privilege, support, equipment, and revocation. 6. Agree reporting, risks, issues, decisions, changes, invoices, quality, service levels, and communication. 7. Run the kickoff, capture questions and actions, confirm shared understanding, and publish the controlled record. ## Done - A kickoff pack records contract baseline, scope, deliverables, roles, governance, dependencies, controls, access, acceptance, and actions - Contract, owner, access, obligation, schedule, acceptance, escalation, and participant-confirmation checks verify readiness