Vendor Check

1---2name: vendor-check3description: Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations.4argument-hint: "[vendor name]"5---6 7# /vendor-check -- Vendor Agreement Status8 9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).10 11Check the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship.12 13**Important**: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals.14 15## Invocation16 17```18/vendor-check [vendor name]19```20 21If no vendor name is provided, prompt the user to specify which vendor to check.22 23## Workflow24 25### Step 1: Identify the Vendor26 27Accept the vendor name from the user. Handle common variations:28- Full legal name vs. trade name (e.g., "Alphabet Inc." vs. "Google")29- Abbreviations (e.g., "AWS" vs. "Amazon Web Services")30- Parent/subsidiary relationships31 32Ask the user to clarify if the vendor name is ambiguous.33 34### Step 2: Search Connected Systems35 36Search for the vendor across all available connected systems, in priority order:37 38#### CLM (Contract Lifecycle Management) -- If Connected39Search for all contracts involving the vendor:40- Active agreements41- Expired agreements (last 3 years)42- Agreements in negotiation or pending signature43- Amendments and addenda44 45#### CRM -- If Connected46Search for the vendor/account record:47- Account status and relationship type48- Associated opportunities or deals49- Contact information for vendor's legal/contracts team50 51#### Email -- If Connected52Search for recent relevant correspondence:53- Contract-related emails (last 6 months)54- NDA or agreement attachments55- Negotiation threads56 57#### Documents (e.g., Box, Egnyte, SharePoint) -- If Connected58Search for:59- Executed agreements60- Redlines and drafts61- Due diligence materials62 63#### Chat (e.g., Slack, Teams) -- If Connected64Search for recent mentions:65- Contract requests involving this vendor66- Legal questions about the vendor67- Relevant team discussions (last 3 months)68 69### Step 3: Compile Agreement Status70 71For each agreement found, report:72 73| Field | Details |74|-------|---------|75| **Agreement Type** | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. |76| **Status** | Active, Expired, In Negotiation, Pending Signature |77| **Effective Date** | When the agreement started |78| **Expiration Date** | When it expires or renews |79| **Auto-Renewal** | Yes/No, with renewal term and notice period |80| **Key Terms** | Liability cap, governing law, termination provisions |81| **Amendments** | Any amendments or addenda on file |82 83### Step 4: Gap Analysis84 85Identify what agreements exist and what might be missing:86 87```88## Agreement Coverage89 90[CHECK] NDA -- [status]91[CHECK/MISSING] MSA -- [status or "Not found"]92[CHECK/MISSING] DPA -- [status or "Not found"]93[CHECK/MISSING] SOW(s) -- [status or "Not found"]94[CHECK/MISSING] SLA -- [status or "Not found"]95[CHECK/MISSING] Insurance Certificate -- [status or "Not found"]96```97 98Flag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data).99 100### Step 5: Generate Report101 102Output a consolidated report:103 104```105## Vendor Agreement Status: [Vendor Name]106 107**Search Date**: [today's date]108**Sources Checked**: [list of systems searched]109**Sources Unavailable**: [list of systems not connected, if any]110 111## Relationship Overview112 113**Vendor**: [full legal name]114**Relationship Type**: [vendor/partner/customer/etc.]115**CRM Status**: [if available]116 117## Agreement Summary118 119### [Agreement Type 1] -- [Status]120- **Effective**: [date]121- **Expires**: [date] ([auto-renews / does not auto-renew])122- **Key Terms**: [summary of material terms]123- **Location**: [where the executed copy is stored]124 125### [Agreement Type 2] -- [Status]126[etc.]127 128## Gap Analysis129 130[What's in place vs. what may be needed]131 132## Upcoming Actions133 134- [Any approaching expirations or renewal deadlines]135- [Required agreements not yet in place]136- [Amendments or updates that may be needed]137 138## Notes139 140[Any relevant context from email/chat searches]141```142 143### Step 6: Handle Missing Sources144 145If key systems are not connected via MCP:146 147- **No CLM**: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems.148- **No CRM**: Skip CRM context. Note the gap.149- **No Email**: Note that email was not searched. Suggest the user search their email for "[vendor name] agreement" or "[vendor name] NDA".150- **No Documents**: Note that document storage was not searched.151 152Always clearly state which sources were checked and which were not, so the user knows the completeness of the report.153 154## Notes155 156- If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere157- For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group158- Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.)159- If an agreement is approaching expiration (within 90 days), highlight this prominently