For Supply Chain Managers ·
What you'll accomplish
The monthly S&OP meeting itself rarely runs long. What eats 2 to 3 hours every cycle is what comes after: turning a spreadsheet of decisions into two paragraphs your CFO can act on without a follow-up call. A Claude Project loaded with your standing report format and your leadership team's preferences shrinks that writing step, and keeps the tone consistent from one month to the next instead of reinventing the format every cycle.
What you'll need
S&OP numbers touch forecasts, margins, and sometimes customer-level order data. Before uploading anything, confirm your company's AI policy for this kind of internal financial data. If your company has a Claude Team or Enterprise account with data controls, use that instead of a personal account. If not, plan to round sensitive figures and strip customer names from anything you paste in.
What you should see: A clear answer on which account to use. Troubleshooting: If your company has no formal answer yet, default to the cautious path and keep this project working from rounded figures.
What you should see: Confirmation that training on your conversations is off. Troubleshooting: If you can't find the setting, search Settings for "privacy" or "training."
What you should see: A project workspace with a Project instructions field and a Project knowledge upload area. Troubleshooting: If Projects doesn't appear in your sidebar, confirm you're logged into the right account. It's available on every plan, including free, so a missing option usually means an account or app-update issue rather than a plan limit.
I am a supply chain manager at a mid-market [manufacturer / distributor / consumer brand] and I run the monthly S&OP cycle. When I give you this month's S&OP decisions and numbers, write an executive summary for the COO and CFO.
STRUCTURE:
- Lead with the headline: are we on track, at risk, or in trouble this month, and why
- Numbers first for the CFO: inventory turns, fill rate, OTIF, freight cost per unit, versus target
- Risk framing for the COO: what could go wrong in the next 30 to 60 days and what we're doing about it
- Close with the 2 or 3 decisions that need executive sign-off, stated as clear asks, not open questions
TONE: Direct, no filler, 200 to 300 words. Assume the reader has 90 seconds, not a briefing.
Ask me for anything missing: this month's KPI numbers versus target, any disruptions or exceptions, and any decision that needs their input.
What you should see: Uploaded files listed and available to reference in every chat inside the project. Troubleshooting: If you have no past summaries yet, skip this step and let the saved instructions carry the format for your first cycle. Add real examples after your first one or two runs.
What you should see: A structured draft matching the format in your instructions, ready for light editing rather than a full rewrite. Troubleshooting: If the draft runs long or buries the headline, tell Claude directly: "Cut this by a third and put the headline in the first sentence."
Standard monthly cycle: "This month's numbers: [KPIs vs targets]. Key exceptions: [list]. Decisions needed: [list]. Write the executive summary."
Risk-forward month: "This month is mostly on track except for [specific risk]. Frame the summary around that risk and what we're doing about it, keeping the routine numbers brief."
Good-news month: "We hit or beat every target this month. Write a summary that's honest about that without sounding like we're coasting, and flag anything on the horizon worth a heads-up."
Board-level condensed version: "Take this month's executive summary and cut it to 3 bullet points for the board deck."
Tone check: "Read this draft back and tell me if it sounds like it's burying the real issue under too much context."