A content reserve is a stock of finished, unreleased content that a website always keeps back. It is not part of the next few releases. It sits there quietly so that, when production slows down or a photographer goes on holiday, the schedule can keep going while you catch up.
Without a reserve, one quiet month can leave your members with nothing new. This guide explains how to size a reserve for each content type and what to do when it starts running low.
Why a reserve matters
Production is rarely perfectly steady. Shoots get cancelled, editing takes longer than planned, seasons change. If your release schedule takes everything you have as soon as it is ready, any hiccup shows up immediately on the site.
A protected reserve gives you:
- Time to react. You see a shortage coming weeks ahead instead of on the morning a release fails.
- A steady experience for members. They keep getting new content at the usual pace.
- Room for choice. You are not forced to release something before it is ready just to fill a slot.
The key word is "protected". A reserve only works if scheduled releases are not allowed to dip into it without you deciding so.
How big should a reserve be?
A simple way to think about it is: how many weeks of releases would you want to cover if production stopped completely? Multiply that by what the schedule releases per week.
| Content type | Schedule | Per week | Weeks of cover | Suggested reserve |
|---|---|---|---|---|
| Image sets | 5 every 2 days | about 17 | 2 | about 35 |
| Videos | 2 every week | 2 | 5 | 10 |
| Stories | 1 every 3 days | about 2 | 3 | about 5 |
The numbers above are only a starting point. Adjust them for your own situation:
- Slower to produce means more cover. Videos and long stories take longer to replace, so it is worth holding more weeks of them.
- Unreliable supply means more cover. If you depend on one creator or one seasonal shoot, keep a bigger buffer.
- Bigger libraries can afford more. If you have hundreds of unreleased sets, a larger reserve costs you nothing.
- A new site may start smaller. At launch you might not have enough for both a generous launch and a large reserve. Build the reserve up over the first few months.
Reserves are per website, not shared
If you run several websites from one library, each site needs its own reserve for each content type. The same image set can be released on one site and still be sitting in another site's reserve. That is normal: the release state belongs to the website, not to the content.
It also means you should not add up reserves across sites as if they were separate stock. Two sites that both match "Dogs" and "Obedience" may be counting the same sets. If you share content between sites, our guide on reusing content across sites without duplicates explains how to think about overlap.
What to do when a reserve runs low
When unreleased stock gets close to the reserve, a well-behaved schedule should release what it can without breaking the reserve, and tell you about the shortage. Then you have a few options:
- Add more content. Upload and publish new sets that match the site's categories.
- Widen the match. Allow more categories, or some filler content, if it still suits the site.
- Slow the schedule. Release 4 sets instead of 5, or every 3 days instead of 2.
- Turn on rotation. Bring older content back as featured items while new content catches up. See our guide on recycling older content honestly.
- Override the reserve, deliberately. Sometimes it is right to dip into the reserve for a special occasion. That should be a conscious decision, not something that happens by accident.
Watch the trend, not just the number
A reserve that is full today can still be in trouble if your unreleased stock is shrinking every week. Look at how much is available above the reserve and how quickly it is being used up. That is the real early warning.
Many owners pick a trigger point, such as "four weeks of releases left above the reserve", and treat it as the moment to act. Acting at that point usually means a small change is enough, rather than an emergency.
Common reserve mistakes
- Setting a reserve once at launch and never revisiting it as the schedule changes.
- Counting Draft or unfinished content as part of the reserve. Only content that is ready to go should count.
- Using one reserve figure for every content type, when videos and image sets behave very differently.
- Letting releases quietly eat the reserve because nobody is told when stock is short.
How Members CMS handles this
In Members CMS each website has its own minimum reserve for each content type, for example 20 image sets, 10 videos and 5 stories. Each item is tracked per site as eligible, reserved, scheduled, released, in rotation or excluded. A scheduled release will not go below the reserve unless an admin overrides it, and shortages are reported so you can act early. Reserves are set under Content Drip > Content Reserves.
Each schedule also has a shortage behaviour setting, so you decide in advance what happens when content runs short, and rotation can be set to step in only when new content is short. The Content Forecast shows how much stock sits above the reserve and roughly when it will run out. Content held in reserve stays out of that site's members area and tour; only released content appears there, through the connector.
Frequently asked questions
What is a protected reserve?
A minimum number of unreleased items a website always keeps back. A scheduled release will not dip below it unless you deliberately allow it.
Is the reserve shared between websites?
No. Each website has its own reserve for each content type, and the same set can be in one site's reserve while already released on another.
What happens when there isn't enough content for a release?
The release takes what it can without breaking the reserve, and the shortage is reported so you can add content, adjust the schedule or allow rotation.
