30 Claude Prompts for Vendor Management

You are a vendor manager who runs quarterly business reviews that stay on time and end with owners. <context> I have a 60 minute QBR with a key supplier next week and I need an agenda that covers performance, risk, and next quarter without turning into a sales pitch. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Meeting length: [MEETING LENGTH] - Attendees on both sides: [ATTENDEE LIST] - Must cover items: [MUST COVER ITEMS] - Open actions from last QBR: [OPEN ACTIONS] </inputs> <task> Build a timed agenda with owners for each block, a slot to close last quarter actions, and a last 10 minute decision block. </task> <constraints> Do not give the supplier more than 15 minutes of unsolicited product updates. Every block needs a time box and an owner. Keep the agenda to one page. </constraints> <format> Return a timed table with columns Minute range, Topic, Owner, and Desired outcome, then a short pre-read list. </format>

You are a category lead writing the performance section of a supplier QBR pack for an executive audience. <context> I need a two page performance narrative that an executive can skim in three minutes before sitting down with the supplier. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Quarter dates: [QUARTER DATES] - Scorecard summary: [SCORECARD SUMMARY] - Incidents or SLA misses: [INCIDENT LIST] - Savings or cost overruns: [COST MOVEMENT] </inputs> <task> Write a performance narrative that covers delivery, quality, cost, and relationship health, then ends with the three questions the executive should ask in the room. </task> <constraints> Under 350 words. No marketing language. If an input is thin, say so instead of filling the gap with adjectives. </constraints> <format> Return four short labeled sections plus a final numbered list of three questions for the executive. </format>

You are a commercial manager preparing talking points for a QBR where the relationship is strained. <context> The last two quarters were poor and I need talking points that stay factual, hold the supplier to the contract, and still leave room to recover. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Specific misses: [SPECIFIC MISSES] - Contract levers we can use: [CONTRACT LEVERS] - What we still need from them: [NEEDED OUTCOMES] - Internal appetite to switch: [SWITCH APPETITE] </inputs> <task> Write talking points for opening, the performance block, the ask, and the close, including one line for if they get defensive. </task> <constraints> Do not threaten termination unless the switch appetite input supports it. Keep each talking point to two sentences. No sarcasm. </constraints> <format> Return four labeled blocks of talking points, then a short fallback line if the meeting goes off track. </format>

You are an operations coordinator who turns messy QBR notes into a clean action log both sides will accept. <context> The QBR just ended and I have rough notes. I need an action log I can send within two hours while people still remember what they agreed. </context> <inputs> - Meeting date and supplier: [MEETING DATE AND SUPPLIER] - Rough notes: [ROUGH NOTES] - Named attendees: [ATTENDEE LIST] - Due date default if none was set: [DEFAULT DUE DATE] - Items we explicitly parked: [PARKED ITEMS] </inputs> <task> Turn the notes into an action log with owner, due date, and success criterion for each item, and list parked items separately so they do not look like commitments. </task> <constraints> Do not invent owners. If an owner is unclear, mark it as unassigned. Keep each action to one sentence. Maximum 12 actions. </constraints> <format> Return a table with Action, Owner, Due date, Success criterion, then a short parked list. </format>

You are a chief procurement officer chief of staff writing a one page briefing before a supplier QBR the CPO will attend. <context> The CPO is joining a supplier QBR and has ten minutes of pre-read time. I need one page that is enough to walk in prepared. </context> <inputs> - Supplier name and spend: [SUPPLIER NAME AND SPEND] - Contract end date: [CONTRACT END DATE] - Current score and trend: [SCORE AND TREND] - Decision needed in the room: [DECISION NEEDED] - Political or relationship notes: [RELATIONSHIP NOTES] </inputs> <task> Write a one page briefing with the situation, the decision, the recommended stance, and two risks if the meeting goes badly. </task> <constraints> Under 200 words. No background history older than 12 months unless it changes the decision. Lead with the decision. </constraints> <format> Return labeled lines for Situation, Decision, Recommended stance, and Risks, suitable to paste into an email. </format>

You are a third party risk analyst who maps supplier risk so a category team can see where to spend review time. <context> I need a heat map style writeup for the suppliers in one category, ranked by impact and likelihood, before our quarterly risk committee. </context> <inputs> - Category name: [CATEGORY NAME] - Supplier list with spend: [SUPPLIER LIST WITH SPEND] - Known incidents last 12 months: [KNOWN INCIDENTS] - Single points of failure: [SINGLE POINTS OF FAILURE] - Residual controls already in place: [EXISTING CONTROLS] </inputs> <task> Rank the suppliers on impact and likelihood, explain the top five in two sentences each, and name the one review that would reduce the most risk this quarter. </task> <constraints> Do not invent incidents. If a supplier has no data, mark it high uncertainty, not low risk. Keep the whole writeup under 400 words. </constraints> <format> Return a ranked table with Impact, Likelihood, and Uncertainty, then five short supplier notes and one recommended review. </format>

You are a procurement risk lead writing a concentration risk memo when too much spend or capability sits with one supplier. <context> I suspect we are over-concentrated with one supplier and I need a memo that finance and operations will both take seriously. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Share of category spend: [SHARE OF CATEGORY SPEND] - Services that only they provide: [UNIQUE SERVICES] - Time to replace if they fail: [TIME TO REPLACE] - Current backup options: [BACKUP OPTIONS] </inputs> <task> Write a concentration risk memo that states the exposure, the failure scenario, the time to recover, and a recommended dual-source or buffer action. </task> <constraints> Under 280 words. Quantify where the inputs allow it. Do not recommend an immediate cutover unless the inputs show a live incident. </constraints> <format> Return labeled sections for Exposure, Failure scenario, Time to recover, and Recommended action. </format>

You are a vendor due diligence analyst who reads public and commercial signals for supplier financial stress. <context> I have limited financial signals on a supplier and need a structured health check I can file before we renew or expand the contract. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Public or provided financial signals: [FINANCIAL SIGNALS] - Payment behavior we have seen: [PAYMENT BEHAVIOR] - Staffing or service quality changes: [STAFFING CHANGES] - Contract remaining term: [REMAINING TERM] </inputs> <task> Produce a financial health check with a green, amber, or red stance, the three strongest signals, and what extra evidence to request before we expand spend. </task> <constraints> Do not claim insolvency. Base the color only on given signals. If evidence is thin, default to amber and list what is missing. Under 250 words. </constraints> <format> Return a color stance line, three numbered signals, and a short request list for extra evidence. </format>

You are a third party risk manager reviewing how much of a supplier's work is actually done by someone else. <context> I just learned this supplier uses subcontractors for part of our scope and I need a risk note before we accept that setup in writing. </context> <inputs> - Prime supplier name: [PRIME SUPPLIER NAME] - Known subcontractors: [KNOWN SUBCONTRACTORS] - Scope they cover: [SUBCONTRACTED SCOPE] - Data or access they would have: [DATA OR ACCESS] - Contract language on flow-down: [FLOW-DOWN LANGUAGE] </inputs> <task> Write a fourth party risk note that maps who does the work, what they can access, whether flow-down terms cover us, and what we should require in writing. </task> <constraints> Do not assume the subcontractors are approved. Flag any access to personal data or production systems as a hard stop until reviewed. Keep it under 300 words. </constraints> <format> Return a who-does-what table, a list of access risks, and a short list of written requirements to send the prime. </format>

You are a vendor risk lead running a same-week review after a supplier incident, outage, or breach notice. <context> A supplier just had an incident and I need a structured risk review I can send to legal, security, and the business owner by end of week. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Incident summary: [INCIDENT SUMMARY] - Services we run on them: [SERVICES IN SCOPE] - Customer or data impact we already know: [KNOWN IMPACT] - Contract notice and audit rights: [NOTICE AND AUDIT RIGHTS] </inputs> <task> Write an incident-triggered risk review with immediate containment questions, residual risk, and a recommended hold, watch, or exit stance. </task> <constraints> Do not wait for a perfect fact set. Separate confirmed facts from open questions. Under 320 words. This is internal, not a letter to the supplier. </constraints> <format> Return sections for Confirmed facts, Open questions, Residual risk, and Stance, plus three questions to send the supplier today. </format>

You are a supplier performance manager who writes improvement plans that have dates, owners, and a clear fail path. <context> This supplier has missed the same commitments more than once and I need a written improvement plan before we escalate to a formal notice. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Repeated misses: [REPEATED MISSES] - Contractual targets they missed: [CONTRACTUAL TARGETS] - Review window length: [REVIEW WINDOW] - Consequence if they miss again: [CONSEQUENCE IF MISSED] </inputs> <task> Draft a vendor improvement plan with the problem statement, three corrective actions, weekly check-ins, and what happens if the window closes without recovery. </task> <constraints> Every action needs an owner and a date. Do not use soft words like try or hope. Keep the plan under 300 words so both sides will sign it. </constraints> <format> Return labeled sections for Problem, Actions, Check-ins, and Consequence, ready to paste into a shared document. </format>

You are a service delivery analyst writing a root cause note after a supplier missed a service level. <context> We had an SLA miss and I need a root cause writeup that separates what the supplier caused from what we contributed, before the credit conversation. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Missed service level: [MISSED SERVICE LEVEL] - Timeline of the incident: [INCIDENT TIMELINE] - Our own contributing actions: [OUR CONTRIBUTING ACTIONS] - Credit or remedy already claimed: [CREDIT STATUS] </inputs> <task> Write a root cause note that states the miss, the most likely cause, our contribution if any, and whether a credit claim is still justified. </task> <constraints> Do not invent a cause. If the timeline is incomplete, say so. Keep it under 250 words. This is an internal note, not the claim letter. </constraints> <format> Return sections for Miss, Cause, Our contribution, and Credit stance, then two facts still needed. </format>

You are a commercial contracts manager drafting a formal escalation note that is firm and still usable if legal later needs it. <context> Informal chases have failed and I need a written escalation that cites the misses and asks for a named recovery plan by a date. </context> <inputs> - Supplier name and contract reference: [SUPPLIER AND CONTRACT REF] - Misses already raised: [MISSES ALREADY RAISED] - Prior informal attempts: [PRIOR ATTEMPTS] - Required recovery date: [REQUIRED RECOVERY DATE] - Copy list on our side: [INTERNAL COPY LIST] </inputs> <task> Draft a formal escalation note that recites the facts, states the required recovery, and names the next step if the date is missed. </task> <constraints> No threats you cannot execute. Cite only misses listed in the inputs. Keep it under 220 words. Tone is firm and professional, not angry. </constraints> <format> Return a subject line and a letter body with short paragraphs, plus a one line note on who internally should be copied. </format>

You are a vendor analytics lead turning four quarters of scores and incidents into a trend readout for a steering group. <context> I have four quarters of supplier data and need a trend readout that tells the steering group whether this account is recovering, flat, or getting worse. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Score by quarter: [SCORE BY QUARTER] - Incident count by quarter: [INCIDENT COUNT BY QUARTER] - Spend by quarter: [SPEND BY QUARTER] - Any one-off events that distort a quarter: [ONE-OFF EVENTS] </inputs> <task> Write a trend readout that states the direction, names the quarter that changed the story, and recommends hold, recover, or exit planning. </task> <constraints> Do not average away a bad quarter if a one-off is not listed. Keep it under 200 words. The recommendation must match the direction of the scores. </constraints> <format> Return a four-quarter mini table, a two sentence trend statement, and a one sentence recommendation. </format>

You are a vendor operations lead designing the meeting cadence between our team and a supplier so issues get handled before they hit the QBR. <context> We only talk to this supplier at the QBR and problems sit for weeks. I need a weekly and monthly cadence that both sides can staff. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Our team roles available: [OUR TEAM ROLES] - Supplier team roles available: [SUPPLIER TEAM ROLES] - Recurring issue types: [RECURRING ISSUE TYPES] - Current meeting load we will not add to: [CURRENT MEETING LOAD] </inputs> <task> Design a joint operating cadence with a weekly ops huddle, a monthly performance check, and a rule for what gets saved for the QBR. </task> <constraints> Do not add a meeting that has no owner. Keep the weekly huddle to 30 minutes. State what is out of scope for each forum. </constraints> <format> Return a cadence table with Forum, Frequency, Length, Owner, and In scope, then three rules for escalation between forums. </format>

You are a vendor lifecycle manager who writes offboarding checklists that do not miss access, data, or money. <context> We are ending a supplier relationship and I need a checklist that covers access removal, data return, final invoices, and knowledge transfer before the last day. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Last service date: [LAST SERVICE DATE] - Systems and access they hold: [SYSTEMS AND ACCESS] - Data they store for us: [DATA THEY STORE] - Open invoices or credits: [OPEN INVOICES OR CREDITS] </inputs> <task> Build a dated offboarding checklist grouped by access, data, commercial close, and knowledge transfer, with an owner for each item. </task> <constraints> Every item needs an owner role and a due date relative to the last service date. Do not assume legal has already issued notice. Keep items to one sentence. </constraints> <format> Return four grouped checklists as tables with Item, Owner, Due date, and Done when, plus a short day-zero list. </format>

You are a transition manager writing a knowledge transfer plan so the outgoing supplier cannot leave us with undocumented work. <context> The outgoing supplier holds process knowledge we never wrote down and I need a transfer plan before they stop answering mail. </context> <inputs> - Outgoing supplier: [OUTGOING SUPPLIER] - Incoming owner, internal or new vendor: [INCOMING OWNER] - Processes they run today: [PROCESSES THEY RUN] - Transfer window in weeks: [TRANSFER WINDOW] - Known documentation gaps: [DOCUMENTATION GAPS] </inputs> <task> Write a knowledge transfer plan with artifacts to collect, live walkthrough sessions, and an acceptance test that the incoming owner signs. </task> <constraints> Fit the plan inside the transfer window. Do not rely on a single workshop. Name the artifacts, not just topics. Under 320 words. </constraints> <format> Return a week by week plan, an artifact list, and a short acceptance checklist the incoming owner can sign. </format>

You are a commercial contracts specialist drafting the wind-down notice to an outgoing supplier for counsel to review. <context> We have decided to end the contract and I need a first draft notice that states the end date, remaining obligations, and what we expect during the wind-down. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Contract reference and notice clause: [CONTRACT AND NOTICE CLAUSE] - Intended last day of service: [LAST DAY OF SERVICE] - Remaining obligations we still need: [REMAINING OBLIGATIONS] - Governing notice method: [NOTICE METHOD] </inputs> <task> Draft a wind-down notice that cites the clause, states the last day, lists remaining obligations, and asks for written confirmation of receipt. </task> <constraints> This is a draft for attorney review, not final legal language. Do not waive any rights. Keep it under 250 words. No emotional language. </constraints> <format> Return a subject line, the notice body, and a short list of attachments counsel should confirm before sending. </format>

You are a privacy and vendor operations lead writing data return and destruction instructions for an outgoing supplier. <context> The supplier holds our data and I need written instructions covering what they return, what they destroy, and the certificate I will accept as proof. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Data types they hold: [DATA TYPES] - Return format we can accept: [RETURN FORMAT] - Destruction standard we require: [DESTRUCTION STANDARD] - Deadline for certificate: [CERTIFICATE DEADLINE] </inputs> <task> Write instructions that list what to return, what to destroy, how to prove both, and what happens if the certificate is late. </task> <constraints> Do not accept a verbal confirmation as proof. Be specific about formats and backups. Keep it under 280 words. This will be attached to the offboarding letter. </constraints> <format> Return numbered instructions, a certificate template outline, and a one sentence late-certificate consequence. </format>

You are a transition lead planning the cutover from an outgoing supplier to a replacement without a service gap. <context> We have a replacement vendor selected and I need a cutover plan that covers parallel run, freeze window, and rollback if the first week fails. </context> <inputs> - Outgoing supplier: [OUTGOING SUPPLIER] - Incoming supplier: [INCOMING SUPPLIER] - Services in the cutover: [SERVICES IN CUTOVER] - Overlap days we can pay for: [OVERLAP DAYS] - Hard stop date on the old contract: [HARD STOP DATE] </inputs> <task> Build a cutover plan with a parallel run, a freeze window, go-live checks, and a rollback trigger, fitted inside the overlap days. </task> <constraints> Do not plan past the hard stop date. Name who declares go or no-go. Keep the plan under 350 words. Call out any service that cannot run in parallel. </constraints> <format> Return a day by day outline, a go-live checklist, and a three-line rollback trigger. </format>

You are a category strategist who segments suppliers so the team spends review time in the right places. <context> We treat every supplier in this category the same and I need a segmentation that tells us who gets a QBR, who gets a scorecard only, and who we should exit. </context> <inputs> - Category name: [CATEGORY NAME] - Supplier list with spend: [SUPPLIER LIST WITH SPEND] - Business criticality notes: [CRITICALITY NOTES] - Current review load we can staff: [REVIEW LOAD] - Known poor performers: [POOR PERFORMERS] </inputs> <task> Segment the suppliers into strategic, operational, and transactional, assign a review cadence to each segment, and name any supplier that should move toward exit. </task> <constraints> Do not put more than five suppliers in strategic unless spend and criticality force it. Match the cadence to the review load we can staff. Keep it under 300 words. </constraints> <format> Return a segmentation table with Segment, Suppliers, Cadence, and Rationale, then a short exit candidate list. </format>

You are a procurement governance lead writing the rationale for adding or keeping a supplier on the preferred vendor list. <context> I need a written rationale for the preferred vendor list so the next request from the business does not reopen the whole panel. </context> <inputs> - Supplier name: [SUPPLIER NAME] - Category of the list: [CATEGORY OF THE LIST] - Score and risk stance: [SCORE AND RISK STANCE] - Commercial terms that justify preferred status: [COMMERCIAL TERMS] - Who asked for the addition: [REQUESTOR] </inputs> <task> Write a preferred vendor rationale that states why this supplier belongs on the list, what would get them removed, and how long the status lasts before review. </task> <constraints> Do not grant preferred status on relationship alone. Cite score or terms. Keep it under 220 words. This is an internal governance note. </constraints> <format> Return labeled sections for Why on the list, Removal triggers, and Review date, suitable to file with the panel. </format>

You are a sourcing advisor writing a stay, switch, or dual-source memo for a supplier the business wants to replace on instinct. <context> The business wants to switch suppliers and I need a memo that weighs stay, switch, and dual-source against switching cost and residual risk. </context> <inputs> - Current supplier: [CURRENT SUPPLIER] - Proposed alternative: [PROPOSED ALTERNATIVE] - Switching cost and time: [SWITCHING COST AND TIME] - Performance gap that triggered the ask: [PERFORMANCE GAP] - Residual risk if we stay: [RESIDUAL RISK IF WE STAY] </inputs> <task> Write a memo that scores stay, switch, and dual-source against cost, time, and risk, then recommends one path with the condition that would change it. </task> <constraints> Do not recommend a switch if switching cost is unknown. Keep it under 280 words. State the condition that would flip the recommendation. </constraints> <format> Return a three-option comparison, a recommended path, and a one sentence flip condition. </format>

You are a category operations lead writing the brief for running two suppliers on the same scope without them colliding. <context> We have decided to dual-source and I need an operating brief that splits volume, sets a primary, and says how we will compare them each quarter. </context> <inputs> - Primary supplier: [PRIMARY SUPPLIER] - Secondary supplier: [SECONDARY SUPPLIER] - Scope that can be split: [SPLITTABLE SCOPE] - Volume split we can start with: [VOLUME SPLIT] - Shared scorecard we will use: [SHARED SCORECARD] </inputs> <task> Write a dual-source operating brief covering volume split, who is primary for incidents, how we compare them, and the rule for shifting volume. </task> <constraints> Do not split a process that cannot run in two places. Keep the volume rule simple enough to apply without a committee. Under 300 words. </constraints> <format> Return labeled sections for Split, Incident primary, Comparison, and Volume shift rule. </format>

You are a head of vendor management writing the annual portfolio review for a leadership offsite. <context> I need an annual portfolio review that covers spend concentration, performance outliers, upcoming exits, and where we should add a second source next year. </context> <inputs> - Portfolio spend and supplier count: [SPEND AND SUPPLIER COUNT] - Top ten by spend: [TOP TEN BY SPEND] - Red and amber scorecards: [RED AND AMBER SCORECARDS] - Contracts ending in 12 months: [CONTRACTS ENDING IN 12 MONTHS] - Known single points of failure: [SINGLE POINTS OF FAILURE] </inputs> <task> Write an annual portfolio review with concentration findings, the five suppliers that need a decision this year, and three portfolio moves for next year. </task> <constraints> Leadership has 10 minutes. Keep the body under 350 words. Do not list every supplier. Decisions first, then supporting numbers. </constraints> <format> Return a one paragraph snapshot, a five-row decision table, and three numbered portfolio moves. </format>