The analysis is done. You know which supplier to recommend, which risks are real, and what the mitigation plan looks like. But now you have to write the RFP narrative, the sourcing decision memo, the supplier scorecard summary, the risk register update, and the category strategy presentation — all before the steering committee on Thursday. That's not supply chain work. That's documentation work.
Before anything else, a clear statement about what Claude is and isn't: Claude cannot access your ERP. It cannot query SAP Ariba, pull from your supplier database, read live inventory feeds, track shipments, price commodities, or connect to your spend analytics platform. It has no visibility into your contracts, your approved vendor list, or your procurement workflows. It is strictly a drafting and communication tool. You bring the data and the decisions — Claude handles the structure and the prose.
That distinction matters for this audience. If you're in procurement or supply chain, you've seen enough AI demonstrations that overpromise system integration to be appropriately skeptical. Claude doesn't sit in your tech stack. It sits next to you while you write. You paste in your evaluation criteria, your risk notes, your scorecard data — and Claude turns your raw inputs into polished documents. That's the scope. Nothing beyond it.
For adjacent context on how AI supports financial analysis and operations reporting, Claude AI for Finance and Accounting and Claude AI for Operations Managers cover the documentation layer for those functions.
1. RFP Narrative and Scope of Work
The RFP is the most time-consuming procurement document most teams produce. The requirements are known — you've gathered them from stakeholders, reviewed the category, and know what you need from a supplier. The problem is turning that knowledge into a structured formal document that suppliers can actually respond to: Background, Scope of Work, Technical Requirements, Evaluation Criteria, Submission Instructions, Timeline, and the fifteen other sections your legal and finance teams will review.
Paste your requirements bullets. Claude produces a complete RFP.
I'm writing an RFP for [category]. Here are my requirements: [paste bullets — technical specs, service requirements, volume, geographic coverage, key constraints, preferred timeline].
Write a complete RFP document including:
- Background (company context and why we're issuing this RFP)
- Scope of Work (detailed, specific)
- Technical Requirements (organized by must-have vs. preferred)
- Evaluation Criteria (with weighting structure)
- Submission Instructions (format, deadline, point of contact)
- Key dates (RFP issue, questions deadline, submission deadline, award date)
Use formal procurement language. Structure each section clearly with numbered sub-sections.
The instruction to separate must-have vs. preferred requirements is load-bearing — it's the structure that makes your evaluation process defensible later. Paste in your stakeholder requirements bullets and any relevant category context. Claude will not fabricate technical specifications or regulatory requirements; if your bullets are thin on a section, it will flag that rather than invent plausible-sounding requirements.
2. Sourcing Decision Memo / Business Case
After an RFP evaluation, finance and legal need a document that justifies the supplier selection before any contract is signed. This is the sourcing decision memo — and it follows a structure that procurement teams and general counsel recognize: who you evaluated, how you scored them, why you selected the recommended supplier, what the risks are, and what the mitigation plan looks like. Writing it from scratch takes two to three hours. Writing it from a paste of your evaluation data takes ten minutes.
I evaluated 4 suppliers for [category]. Here's my scoring: [paste evaluation data — supplier names, criteria, scores, and your rationale bullets for each].
Write a sourcing decision memo for CFO and Legal approval. Include:
- Executive Summary (3 sentences: what we evaluated, who won, why)
- Evaluation Methodology (criteria and weighting used)
- Vendor Comparison (table format: supplier vs. criteria vs. score)
- Recommended Supplier with rationale (2-3 paragraphs)
- Risks and Mitigants (for the selected supplier)
- Clear Recommendation paragraph
Formal business language. This is a legal and finance document.
The table request for Vendor Comparison is intentional — a well-formatted comparison table is what CFOs and legal teams want to see, and it's what Claude will produce when you explicitly request it. Business analysts who support sourcing teams on the quantitative evaluation side will recognize this structure; the prompt picks up where their scoring output ends.
3. Supplier Scorecard and Performance Review Narrative
Every procurement team has quarterly supplier scorecards. Most of them live in a spreadsheet. Turning a spreadsheet of scores into a supplier relationship document — something you can actually use in a business review meeting with the supplier's account team — is the documentation gap. It's not the analysis that takes time. It's the narrative.
Here's our quarterly scorecard data for [supplier]: [paste data — categories, scores, targets, trend vs. last quarter, any qualitative notes].
Write a formal supplier performance review document for our business review meeting. Include:
- Performance Summary (overall relationship health, 2-3 sentences)
- Key Metrics Table (category / score / target / trend)
- Key Themes — Positive (3-4 strengths with specifics)
- Key Themes — Improvement Areas (2-3 issues, framed constructively)
- Agreed Action Items (with owners and deadlines — I'll fill in owners)
- Next Review Date
- Summary recommendation on the relationship (strategic / maintain / develop / at-risk)
Tone: professional and direct. This is shared with the supplier's account team.
The "Summary recommendation on the relationship" field gives the document a clear conclusion — something most performance review templates omit and procurement leaders consistently want. Paste your scorecard data; Claude builds the narrative around it. For data analysts who support supply chain teams with performance dashboards, this prompt takes the output of that analysis and turns it into the review document.
4. Supply Chain Risk Register Update
Risk register entries should be formal, precise, and structured in a way that communicates clearly to a board audit committee. In practice, they're often written in shorthand — risk notes in a spreadsheet, bullet points from a briefing, a paragraph from an analyst report. Translating that shorthand into a board-ready risk register entry is exactly the kind of structured drafting work Claude handles well.
I need to add a new supply chain risk to our risk register. Here's my assessment: [paste notes — risk event, affected categories or regions, likelihood reasoning, potential business impact, any existing controls or mitigation already in place].
Write a formal risk register entry with:
- Risk Title
- Risk Description (2-3 sentences, precise)
- Root Cause
- Likelihood (1-5 scale with reasoning)
- Impact (1-5 scale with business impact framing)
- Current Controls
- Residual Risk (post-control likelihood × impact)
- Mitigation Actions (numbered list with owners and deadlines — I'll confirm owners)
- Escalation Trigger (the specific condition that escalates this to executive attention)
Formal language. This is a board-level document.
The Escalation Trigger field is the one most risk register templates omit and most board audit committees ask for. When you're writing an entry for a geopolitical supply disruption, a single-source dependency, or a logistics concentration risk, being specific about what triggers escalation is what separates a useful risk entry from a compliance checkbox. Paste your assessment notes; Claude structures the entry.
For finance teams who use risk register data in board reporting, Claude AI for Finance Professionals covers the adjacent reporting and financial narrative workflows.
5. Category Strategy Presentation Narrative
Category strategy presentations combine market analysis, spend data, supplier landscape, and strategic priorities into a coherent narrative for CPO and senior leadership review. You have the content — the spend analysis is done, the strategic priorities are decided, the supplier landscape is mapped. What you need is the storyline that ties it together for a 30-minute CPO meeting.
I'm presenting our [category] strategy to the CPO. Here are my key points: [paste bullets — market context, current spend and coverage, strategic priorities, supplier landscape, identified value opportunities, planned initiatives and timeline].
Write the narrative sections for my presentation:
- Market Context (2-3 paragraphs: what's happening in this market that affects our strategy)
- Our Current Position (where we are today — spend, supplier concentration, gaps)
- Strategic Priorities (3-4 priorities, each with a clear rationale paragraph)
- Supplier Strategy (segmentation approach and rationale)
- 12-Month Roadmap Summary (key milestones in prose, not just bullets)
Audience is the CPO and two business unit VPs. Language should be strategic but grounded — no filler.
"No filler" is explicit because category strategy presentations frequently read like consulting decks — structured but hollow. The prompt gives Claude your bullets; the instruction shapes the register. Specifying "CPO and two business unit VPs" as the audience calibrates the technical depth: strategic enough for the CPO, specific enough for the VPs who will own the implementation.
6. Supplier Negotiation Briefing Document
Before a major contract renewal or renegotiation, most procurement teams prep verbally. The negotiation strategy lives in the lead negotiator's head — the walk-away position, the BATNA, the supplier's likely pressure points, the term-by-term playbook. Writing that up as a formal internal briefing document is the step that turns individual expertise into a team-aligned negotiating position. It's also the document that protects you if the lead negotiator changes between sessions.
I'm going into a renewal negotiation with [supplier] for [category]. Here's my context: [paste notes — current contract terms, spend volume, contract expiry, supplier's market position, our alternatives, key terms to negotiate, any recent relationship issues, leverage we have].
Write a negotiation briefing document including:
- Negotiation Objectives (ranked: must achieve / should achieve / nice to have)
- Our BATNA (what we do if negotiations fail)
- Supplier Profile (their likely priorities, their pressure points, their market position)
- Key Leverage Points (our strongest negotiating levers)
- Term-by-Term Playbook: for each of [price, volume commitments, payment terms, SLAs, contract length] — opening position / target / walk-away
- Red Lines (the terms we will not accept)
Internal document. Direct language. This is for our negotiation team, not for the supplier.
The Term-by-Term Playbook structure is what turns a negotiation strategy into a usable briefing. Paste your context notes — current terms, alternatives, leverage — and Claude builds the structured document your team needs to enter the negotiation aligned. The "Internal document. Direct language." instruction matters: without it, negotiation briefings tend to come out too diplomatic. This one needs to be honest about walk-away positions and leverage, not polished for external consumption.
Why Claude Over ChatGPT for Procurement Work
If you've experimented with other AI tools for procurement documentation, here's the practical difference:
100K+ context window. Paste a full category spend report, three supplier proposals, your evaluation matrix, and a risk register into one session. Claude reads all of it without losing context midway through. This is the feature that matters most for sourcing decision memos and category strategy work, where the background material is substantial. For a detailed tool comparison, Claude vs ChatGPT for work covers the differences.
Conservative by default. Claude will not fabricate supplier names, commodity prices, regulatory requirements, or compliance details you didn't provide. For procurement documentation — where invented facts create real legal exposure — this is the most important behavioral difference. It asks for clarification rather than filling gaps with plausible-sounding details.
Projects per category or supplier relationship. Create one Claude Project per major category or key supplier. Your market intelligence, supplier history, previous RFPs, and scorecards live there permanently. Every new document picks up where the last one left off. By the third RFP cycle, Claude has context that would take a new analyst weeks to build.
Structured output fidelity. Complex procurement documents — RFPs with eight sections, risk registers with weighted fields, multi-vendor comparison tables — come out properly structured, not as flowing paragraphs. Claude handles document architecture; you handle the procurement judgment.
4 Practical Tips for Supply Chain and Procurement Teams
1. One Project per category. Create a Claude Project for each major spend category — IT, facilities, logistics, professional services, raw materials. Your market intelligence, supplier relationship notes, and strategic context accumulate in that Project over time. Every new RFP or sourcing cycle builds on the last one.
2. Numbers and decisions in, narrative out. Claude's job is to write the document around your analysis — not to do the analysis. Paste your evaluation matrix, your scorecard data, your risk assessment. Claude writes the business case. Don't ask it to derive conclusions from raw data; bring the conclusions and ask it to communicate them.
3. Specify the reader. "Write this for our CFO" produces a very different document than "write this for our operations team." Finance executives want financial framing and risk quantification. Operations leaders want practical clarity. Always tell Claude who's reading it before you ask it to write.
4. End-of-quarter documentation sprint. At the end of each quarter, open one Claude session and batch your supplier performance reviews, risk register updates, and category strategy refreshes. What would take four hours of individual document production takes 45 minutes. The structure is the same every quarter — you're just updating the data.
The Complete Claude Playbook
If you want 50+ prompts built for every stage of your workflow — not just procurement — The Complete Claude Playbook ($27) covers it all. Instant PDF download, organized by professional workflow. The prompts in this post are a starting point. The Playbook is the full toolkit.