Weekly Supply Risk Brief — Annotated Example for Leadership

Operations leaders rarely open dashboards on their own time. They open emails, briefs, and documents that arrive at a predictable hour. A weekly brief is the artifact that closes the gap between the operations team that sees risk daily and the leadership team that needs to know about it before it becomes a customer call.

The brief is written for a single audience: people accountable for outcomes who don't run the system day-to-day.

• VP Operations / COO — wants the one paragraph that changes their week.
• VP Procurement — wants to know which suppliers moved and which ones are about to.
• CFO — wants revenue exposure attached to risk, not abstract scores.
• CEO occasionally — wants confidence that operational risk is being run.

The brief is always the same shape. That's a feature, not a limitation — readers learn where to find the section they care about and stop reading the rest.

1. 1Headline — the one sentence that summarizes the week.
2. 2What moved — the deltas vs last week, in plain language.
3. 3Top exposures — the suppliers, materials, or lanes that need attention.
4. 4Recommended actions — what would close the gap, with a named owner.
5. 5Look-ahead — what the next two weeks will likely surface.

One sentence. Specific. Quantified. Leads with operational impact, not signal noise.

That sentence does three jobs at once: names the exposure, attaches a number, and points at the action.

Deltas only. Not a full status. Not the same suppliers as last week unless something changed.

• New high-severity risk events: count, category, where.
• Risk score deltas ≥ 5 points on critical suppliers.
• Closed mitigations from last week — what was done.
• New single-source dependencies surfaced this week.

Three to five rows. Each row is one supplier or lane, with one metric, in one line:

If you have more than five real exposures, the brief is wrong about what "top" means. Five is the number leadership can hold in their head between meetings.

Each action has four fields and nothing else: action, owner, by-when, expected risk reduction.

• Action — concrete, not aspirational. ('Qualify Hanoi Forge for housing 21340-A.')
• Owner — a named person, not a team.
• By-when — a date, not 'this quarter.'
• Expected risk reduction — a number on the same scale as the exposure.

Two or three sentences on what's coming. The look-ahead is the section that earns the next week's open rate.

Leadership briefs fail in predictable ways. The fixes are also predictable:

• Cut the methodology. No one needs to know how the score was calculated in a weekly brief. Link it; don't explain it.
• Cut hedging. "Potentially could possibly" is operational throat-clearing. State the exposure, attach a number, recommend an action.
• Cut decoration. No banners, no emojis, no "great work team!" The brief is a working document, not a newsletter.
• Keep the rhythm. Same time, same day, every week. A brief that sometimes arrives is a brief that gets unsubscribed.