coordinate-a-multi-vendor-project

# coordinate-a-multi-vendor-project Make interface ownership explicit where contracts meet. ## When to use - Use for implementation, construction, events, technology, research, or managed services with multiple suppliers. - Do not share one vendor's confidential or competitively sensitive information without authority. ## Procedure 1. Inventory contracts, scopes, deliverables, exclusions, dates, assumptions, responsibilities, and acceptance terms. 2. Define client sponsor, integration lead, vendor leads, approvers, decision rights, and escalation. 3. Build an interface register for every cross-vendor input, output, standard, environment, date, owner, and acceptance test. 4. Create an integrated schedule with dependencies, lead times, critical path, client obligations, and change windows. 5. Align security, privacy, safety, accessibility, data, quality, support, subcontractor, and records controls. 6. Manage risks, issues, decisions, changes, invoices, claims, and evidence through governed records. 7. Test component and end-to-end integration with clear defect ownership and no forced acceptance. 8. Accept deliverables contractually, transfer operations, close access, and preserve warranty plus residual obligations. ## Done - An integrated vendor plan records contracts, interfaces, roles, schedule, dependencies, controls, tests, changes, acceptance, and obligations - Contract, interface, critical-path, confidentiality, integration, defect, acceptance, access-removal, and warranty checks verify delivery