For Supply Chain Managers ·
What you'll accomplish
Every quarter, the supplier QBR agenda and scorecard commentary get rebuilt from a blank page because last quarter's version is buried in an old email thread. A Claude Project holding your standard scorecard template and a couple of past QBR decks turns each new quarter's numbers into a ready-to-edit agenda and commentary, in the same format every time, instead of a fresh build.
What you'll need
If most of your suppliers get scored on the same metrics, one project can serve all of them. If a few strategic suppliers have unique terms or a more sensitive relationship, consider a separate project (or at least separate chats) for those, so their history doesn't blend into a generic template.
What you should see: A short list telling you whether one project or a couple will serve you better. Troubleshooting: When in doubt, start with one project. You can always split it later if a supplier's context gets crowded.
What you should see: Confirmation that conversation data isn't used for training. Troubleshooting: If your company has a Claude Team or Enterprise account with its own data controls, use that instead of a personal login for anything involving real supplier numbers.
What you should see: An empty project with fields for instructions and knowledge files. Troubleshooting: None expected here; Projects are available on every Claude plan.
I am a supply chain manager running quarterly business reviews with suppliers. When I give you this quarter's scorecard numbers for a supplier, produce two things:
1. A QBR AGENDA: 5 to 7 items, ordered from performance review through to next-quarter asks, matching a typical hour-long meeting
2. SCORECARD COMMENTARY: 3 to 4 sentences per metric (on-time delivery, quality/defect rate, responsiveness, cost performance) that state the number, whether it's trending up or down, and one specific driver if I give you one
TONE: Professional and direct. If a metric is below target, say so plainly and note what needs to change, without being harsh. If a metric is strong, say so without overpraising.
Ask me for anything missing: the metrics themselves, last quarter's numbers for comparison, and any specific incident worth naming.
What you should see: Reference files listed and available across every chat in the project. Troubleshooting: No past materials yet is fine. Run your first quarter off the saved instructions alone and add the output as a reference afterward.
What you should see: An agenda you could paste into a calendar invite and commentary you could paste into a scorecard deck with light editing. Troubleshooting: If the commentary reads too soft on a real problem, tell Claude directly: "Be more direct about the quality miss in Q3."
Standard quarterly run: "Q[X] scorecard for [Supplier]: [metrics vs targets]. Build the agenda and commentary."
Difficult quarter: "This supplier missed on [metric] for the second quarter running. Help me frame commentary that's direct about the pattern without sounding like a final warning, since we're not there yet."
Strong quarter: "This supplier beat every target this quarter. Write commentary that's genuinely positive without setting up unrealistic expectations for next quarter."
New supplier's first QBR: "This is [Supplier]'s first quarterly review since onboarding. Build an agenda that covers baseline performance plus a check on whether onboarding commitments were met."
Multi-supplier comparison: "I'm reviewing three suppliers in the same category this week: [brief metrics for each]. Give me one paragraph per supplier I can use as prep notes before each meeting."