Your content runway is how long a website can keep to its release schedule before it runs out of new content. Knowing it turns a vague worry ("are we going to run dry?") into a date you can plan around.
The calculation is simple, but it is easy to get wrong if you count the wrong things. This guide shows how to work out a realistic runway for each site and content type, with worked examples and the warning signs to look out for.
The basic formula
For one website and one content type:
- Count the unreleased eligible content - finished items that match the site and have not been released there yet.
- Subtract the protected reserve - the minimum the site always keeps back.
- Divide by how much the schedule releases per period (per week is usually easiest).
So: (unreleased eligible - reserve) / releases per week = weeks of runway.
Example: 120 unreleased sets, a reserve of 20 and a schedule of 10 a week. That leaves 100 available sets, which is about 10 weeks.
Worked examples
Here is the example site "Puppy Obedience Club" with three content types:
| Type | Unreleased eligible | Reserve | Available | Schedule | Per week | Runway |
|---|---|---|---|---|---|---|
| Image sets | 260 | 20 | 240 | 5 every 2 days | 17.5 | about 13 weeks |
| Videos | 30 | 10 | 20 | 2 every week | 2 | about 10 weeks |
| Stories | 15 | 5 | 10 | 1 every 3 days | about 2.3 | about 4 weeks |
The image sets look healthy, but stories will run short in about a month. That is the type to focus on: write more, slow the story schedule, or allow rotation for stories while you catch up.
Converting schedules to a weekly rate
Schedules are rarely written per week, so convert them:
- 5 every 2 days = 5 x 7 / 2 = 17.5 a week
- 1 every 3 days = 7 / 3 = about 2.3 a week
- 4 every 14 days = 2 a week
- 10 every month = about 2.3 a week (a month is roughly 4.3 weeks)
What to count, and what not to
Most runway mistakes come from counting the wrong stock.
- Do count content that is finished, published and matches the site's categories and content types.
- Don't count drafts, content still being processed, or anything excluded from that site.
- Don't count content already released on that site, even if it is still unreleased elsewhere.
- Don't add up sites as if they had separate stock. Two sites that match the same categories may be drawing on the same sets, which is fine because each site keeps its own release record. See our guide on reusing content across sites.
- Be careful with filler. If the site accepts partial matches, only count filler up to the maximum share you allow.
With and without rotation
If you allow older content to be featured again, your effective runway is longer, because rotation can fill some slots when new content is short. It is worth looking at both numbers:
- Without rotation: how long until the site has nothing new to release.
- With rotation: how long the site can keep something appearing in each release, using older items after their cooldown.
The first number is the one to plan production around. The second is your safety net. Our guide on rotating older content honestly explains cooldowns and repeat limits.
Warning signs to watch
- A runway that gets shorter every time you check, even though you are uploading regularly. Your schedule is faster than your production.
- One content type with a much shorter runway than the others.
- Available stock close to zero, meaning releases are about to start touching the reserve.
- A new site added with the same categories as an existing one, which changes both sites' outlook.
- Recent category changes that quietly made fewer sets eligible.
Keep the forecast current
A forecast is an estimate, not a promise. It is based on today's stock and today's schedule. Every new published set that matches a site extends its runway; every change to categories, exclusions or schedules moves it. Re-check it after any of these changes, and at least once a month.
Factor in new production
The basic formula assumes no new content arrives, which makes it a cautious "worst case". To get a more realistic figure, compare your weekly production with your weekly releases. If you add 12 matching sets a week and release 17.5, the stock shrinks by about 5.5 sets a week rather than 17.5. In the example above that stretches image sets from about 13 weeks to well over 40.
Use the cautious figure for planning, and the realistic one to judge whether your production is keeping pace. If the two are far apart, your forecast depends heavily on uploads continuing on time.
A useful habit is to set a minimum runway you are comfortable with, for example eight weeks, and act whenever a site drops below it.
How Members CMS handles this
Members CMS includes a Content Forecast screen under the Content Drip menu. For each website and content type it shows eligible, released and unreleased content, the protected reserve, the release quantity and frequency, the estimated runway, the expected shortage date and the rotation stock, with figures both with and without rotation.
The forecast uses the site's real matching and schedule settings, so it changes as you upload, categorise or adjust schedules, and it is clearly labelled as an estimate. Each release reaches the site's members area and tour through the connector, so the runway is really a forecast of how long members will keep seeing new content.
Frequently asked questions
How is content runway calculated?
Take the unreleased eligible content, subtract the protected reserve, and divide by how much the schedule releases in each period. 100 available sets at 10 a week is about 10 weeks.
Does new content change the forecast?
Yes. Each new published set that matches a site adds to that site's supply, so forecasts should be re-run as content is added.
Is a forecast a guarantee?
No. It is an estimate based on the current schedule and stock. Changes to categories, schedules or uploads all move it.
