How to Build a 13-Week Supply Plan

Thirteen weeks is a common horizon in supply planning for a good reason: it's usually long enough to cover most lead times end to end, short enough to stay genuinely actionable, and it maps neatly onto a quarter, which makes it easy to talk about with the rest of the business.

Here's how to actually build one.

Why 13 weeks specifically

If your total lead time — raw material procurement plus production plus any transport — is, say, 8 weeks, a 13-week plan gives you that full lead time plus a few weeks of buffer to see problems coming and still act on them. Too short a horizon and you're planning blind to your own lead time; too long and the far-out weeks are so uncertain they're not worth the detail.

If your lead times are much shorter or longer than this, adjust the horizon accordingly — the principle matters more than the specific number 13.

The structure

One row per SKU (or product family, if you're managing at a higher level), one column per week, with these calculated rows:

• Opening inventory
• Demand (pulled from your demand plan)
• Planned supply / production
• Closing inventory (Opening + Supply − Demand, rolling forward)
• Weeks of cover
• Capacity utilisation, if you're tracking against a specific line or supplier limit

This is the same core mechanic as any supply plan — the 13-week version is really about applying it with discipline over a specific, consistent horizon rather than an ad hoc window that shifts around.

Divide the horizon into zones

This is what separates a genuinely useful 13-week plan from a spreadsheet that just happens to have 13 columns.

Weeks 1-4 (frozen) — inside your core lead time. The plan here should be close to locked. Changes are expensive and disruptive, and should require a real reason.

Weeks 5-9 (slushy) — still adjustable, but changes have real cost and should be weighed deliberately, not made casually.

Weeks 10-13 (liquid) — genuinely just an estimate. This is where you're stress-testing the plan against demand scenarios and deciding whether early action (an extra purchase order, a capacity booking) makes sense, not where you're committing to specifics.

Visually distinguishing these zones in the spreadsheet — different shading, a clear column break — makes it obvious at a glance which numbers are safe to question and which ones aren't.

Build in your key exception flags

With 13 weeks across potentially hundreds of SKUs, you need the plan to tell you where to look, not just what the numbers are. At minimum, flag:

• Any week where closing inventory goes negative
• Any week where capacity utilisation exceeds a set threshold
• Any SKU where weeks of cover swings sharply between adjacent weeks, which usually signals a demand spike or a supply gap worth a second look

Refresh it on a consistent rhythm

A 13-week plan that isn't refreshed regularly quickly becomes fiction. Most businesses refresh weekly, rolling the horizon forward by a week each time — week 14 becomes the new week 13, and the oldest week drops off or converts into an actuals record.

The discipline of refreshing on a fixed cadence, even when nothing dramatic has changed, is what keeps the plan trustworthy. A plan that only gets updated when there's a problem stops being a planning tool and becomes a firefighting log.

What good looks like

A working 13-week supply plan should let you answer, at a glance: where are we short, where are we long, what needs a decision this week, and what's already locked in versus still flexible. If it takes more than a few minutes to answer those questions from the spreadsheet, the structure needs simplifying — not more detail added.

Next: Why most S&OP processes don't work — the 13-week plan is usually the backbone of the supply review inside that process. Or build one yourself using the Nerd Foods dataset, which includes 104 weeks of demand and production data ready to slice into a rolling 13-week view.