Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Social Media Marketing › Social Content

Building a Reserve of Evergreen Social Posts

How to build a reserve of approved evergreen social posts for empty slots: what qualifies, rights and approvals, expiry dates, rules for use and retirement.
Tutorialintermediate16 min readUpdated

Why the calendar needs a reserve it can rely on

The social content calendar tutorial keeps some slots free of a topic until the week itself, so that the team can react. It also says what to do when nothing happens: the empty slot is filled from a backlog of approved evergreen posts, which must be in place before the calendar is switched on. It adds that a team short of capacity should cut slots and not lower the quality of what goes out, so an empty slot is not an invitation to post whatever is to hand.

Other pages assume the same backlog: the TikTok posting guide and the user-generated content guide take it for granted, and so does a beginner exercise in the academy. None says what qualifies, what is kept with a post, how a post is approved, when it may run again or when it stops being used.

A reserve post also meets its audience on a day nobody chose, and an evergreen how-to is read as current whatever the date on which it was written. The facts inside it have to hold on that day, which is why much of the work below is about what goes into the reserve and how it leaves, and only a little is about volume.

For rights, approvals, filing and retirement the steps point to the pages that own them. The steps that are this page's own are the size of the reserve, the test for what qualifies, the rewrite that lets a post outlive its week, the rules for using one and the note that follows. Advice beyond what the site's guides state is labelled general practice. This tutorial gives no figure outside its example, and it says nothing about how any platform treats a repeated or re-run post, when a post should be repeated, what share of a cadence a reserve should fill or what reach an older post can expect.

Before you start

  • A working calendar. The calendar from the tutorial above, with reactive slots, a status for each post and a row that holds each post's assets. The reserve is part of that calendar and not a second system.
  • A record of the gaps. The slots the calendar left empty, or filled in a hurry, over recent months, taken from the account's own calendar. If the calendar is new, a first estimate will do, to be corrected at the first review.
  • A named owner and a deputy. As general practice, the owner decides what enters the reserve, releases a post for use and runs the reviews, and the deputy covers leave, which is one of the occasions the reserve exists for.
  • The approvers. Whoever approves claims, prices and partnerships on the account, and whoever keeps the record of permissions for the people shown, because a reserve post needs the same checks as any other.
  • The account's results by format and pillar. The third step reads candidates against them. Without such a record the reserve can still be built, but the choice rests on judgement, and the first review should replace judgement with evidence.
  • A place to keep it. A labelled section of the calendar or the scheduling tool, where a reserve post carries the same fields as any other row. Finished files and their rights stay in whatever store the business already uses for assets.

The steps

  1. Decide what the reserve is for

    Write down the occasions the reserve covers, because they decide what goes in and when it may be used. As general practice they are a reactive slot where nothing worth reacting to turned up, a quiet week when the planned posts are not ready, a leave period when the owner and the producer are away, and a restart after a pause, when scheduled posts have been removed or rewritten and the person who owns the situation has agreed to resume. Say just as plainly what the reserve is not for. It is not a way to publish more than the team can staff: the calendar's answer to a shortfall in capacity is to cut slots, and a reserve that quietly fills a standing shortfall hides the problem the cut would have shown. It is not an archive of old favourites, and it is not the business's asset library.

    Then size it. As general practice, start from the account's own calendar: look back over recent months, mark each slot that was left empty or filled in a hurry, and group the marks by platform and by occasion. That is the gap the reserve has to cover, and it is a better starting point than a target or a number from somewhere else. The site gives no share of a cadence that a reserve should fill, and this tutorial gives none. Plan each platform separately where its slots differ, because the calendar plans each platform in its own column and a post that suits one may not suit another. Then cap the size by what the owner can keep reviewed: a reserve post still needs checking on its review date, so a reserve larger than the owner can review is a store of posts nobody has checked. Write the intended size, and the gap it was sized from, at the top of the reserve, so that the first review has something to compare against.

  2. Define what counts as evergreen for this account

    Whether a post can wait is decided by the question it answers, which is how the glossary entry on evergreen content frames it. Write a short test that the owner and the deputy can apply in the same way. As general practice, a post qualifies when it answers a question the audience asks, belongs to one of the account's content pillars, is in a format the team can make and check, and would read correctly to someone who found it with no calendar beside it. It fails when its point depends on the week it went out. Keep the test where the owner and the approvers can read it, so that a refused post is refused for a stated reason.

    Name the formats the reserve may hold. The social content formats guide sets out what each format does in the feed and what it costs to make; as general practice, choose from the formats the team already makes well, since a reserve post is one nobody will have time to rework on the day. Then add a refresh rule. The content strategy framework names a refresh rule as part of a complete answer on production and governance, and for the reserve that rule takes the form of the review date given to each post in the filing step and the fixed review at the end.

  3. Find candidates in the account's own posts and in the questions customers keep asking

    Candidates come from places the brand already holds, and each place has its own check.

    SourceWhat to look forWhat to watch for
    The account's own published postsPosts that answer a lasting question and were typical or better for their format and pillarA post that travelled because of a moment, whose result may not repeat
    Questions in the inbox and commentsA question asked by different people, with any answer the brand has already approved for repliesA question that is really about a current offer or a fault
    The people who know the subjectCare advice, how something is made or done, the answers to what customers misunderstandAdvice that depends on one supplier, one model or one method

    Place a candidate from the account's own posts against the account's earlier results, as the social media reporting guide does: keep the middle result for a format and a pillar, and place a post as ordinary, better than ordinary or an outlier. As general practice, choose posts that were ordinary or better for their group and treat an outlier with care. The guide asks for the context behind an outlier, such as a campaign, a news event or a holiday, to be noted, and a post that rode a moment may not hold up as a gap filler. Where no record exists yet, say so in the reserve's notes and choose on judgement.

    As general practice, the inbox is a good source of lasting questions. Where the brand keeps a bank of pre-approved replies for questions that recur, those questions are candidates, and the approved wording is a starting point for the post. Record each candidate with the question it answers, its pillar and format, and where it came from, so that the choice can be reviewed later.

  4. Rewrite each candidate so it carries no date, price, offer or person it cannot outlive

    As general practice, rewrite the text, the image and the link as if the post will be read on a day nobody has picked yet, because that is how it will run. The test is to read the finished post as someone who has just found the account, with no calendar beside it, and to mark each phrase that needs a particular day to make sense.

    What the draft carriesWhy it cannot waitWhat to do
    A date or a time word, such as today, this week, new or nowIts meaning depends on when it ranRewrite without it, or drop the candidate if the timing is the point
    A price, an offer or a codeIt changes, and it needs its own approval each timeTake it out; a post that needs money to make sense is not a reserve post
    An event, a season or a news itemIt belongs to a dated momentDrop it from the reserve and plan it in the calendar
    A named colleague or customerTheir agreement covers stated posts, and they can leave or withdrawRewrite around the work and leave the person out, or confirm the agreement covers later use
    A product, a supplier, a method or a claimFacts change, and the post is only as current as they areRecord what the post rests on in its row, so that the later steps can retire it when that changes

    The guide to featuring employees agrees a colleague's appearance in writing, follows that agreement on existing posts and plans a series for the day its presenter leaves. As general practice, treat a reserve post as a later use of that appearance: check what the agreement says about it and ask again where it is silent. A post that has to be pulled when someone leaves reopens the gap it was filed to cover.

    Write the image description and the caption now, by whoever made the asset, because that person knows what the image shows and, for a post that will wait, the knowledge fades. The description is the alt text for the image, and the accessible social media posts guide sets what it should carry in a post.

  5. Check rights, people and claims and approve at the right level

    The approval workflow tutorial sorts posts into levels by risk, with claims, prices and partnerships checked by the owner of that risk and each approval recorded, much as an approval matrix routes work. Where a post shows a customer, a creator or a colleague, the permission has to be recorded and has to cover this later use; for creator work that is a question of usage rights, meaning which uses, which channels and for how long.

  6. File each post with its asset, text, alt text, tracked link, source and review date

    Give each reserve post a row of the same shape as any calendar post, as the calendar tutorial's step on tracking assets and their sources describes, and, as general practice, add what the reserve needs on top: the review date, what the post rests on, the platform it suits, a status that marks it as reserve and a field for the date it was last used. The asset library tutorial covers the files and their rights fields where the business keeps its assets in a library.

  7. Set the rules for using one and the gap before it runs again

    As general practice, write the rules down before the first post is used, so that a decision on a busy morning is a lookup. They are the business's own rules, set from its own calendar. None of them is a platform rule, and nothing here claims to know how a platform treats a repeated post.

    • When a post may be released. Name the occasions from the first step and who decides on each: the owner or the deputy for a quiet week or leave cover, a point in the week at which an open reactive slot is declared empty, and the agreement of whoever owns the situation before any reserve post runs after a pause.
    • Which post to pick. Choose by what the month needs: the pillar that is short against the shares the calendar already tracks, and the platform the slot belongs to. Do not pick the post that is easiest to reach.
    • What each use requires. The reread in the next step, with no exception for an urgent slot.
    • Who is told. The owner records the use, and whoever answers comments is told which post went out and when, so that replies are ready.
    • What does not come from the reserve. Reactive content answering the week's news is made new and approved on the day, and any post whose claim was not approved when it was filed stays out.

    Then set the gap before a post may run again. As general practice, write it as a rule the calendar can check, either as a length of time or as the posts on the same platform and pillar that must go out in between, and choose it from how the account's own calendar turns over. Record that the gap is the business's judgement, so that nobody later defends it as a platform requirement. A post that has run is marked used and moves to the back of the queue.

  8. Use it: reread, update, publish and note the result

    On the day, reread the post against what is true now. A post's review date and the fixed review of the reserve do not replace this: the reread is a check of one post before it goes out. As general practice, read the post, its image, its description and its link against the questions in the old-post review tutorial. After a pause, the crisis plan tutorial restarts the queue only once each scheduled post has been read against what has happened. As general practice, a reserve post waiting for a slot is read the same way before it is used.

    As general practice, update where needed. A light correction, such as a changed link, can be made and noted. A change that alters a claim, a price or the people shown means a fact the post rests on has changed, so the post is retired under the next step; a post that needs more than a light correction for another reason returns to the rewrite and then through the approval of the fifth step.

    Publish by the usual route and run the social post publishing checklist as the last look at the post, and tag its link as the account's other links are tagged, following the scheme in the naming conventions and UTMs guide; the visits it brings can then be read in analytics beside the rest.

    Then note the result. Mark the post used with its date and slot, move it according to the gap rule and write one line in its row: what happened, what to change and the occasion it filled. One result decides nothing; the notes are read together at the review, by pillar and format.

  9. Retire posts and top the reserve up

    As general practice, retire a post when any fact it rests on changes, and do not edit it quietly back to health: move it out of the reserve, note why and, if it has already been published, sort that copy with the same tutorial, which weighs keeping, editing, hiding and deleting. Top the reserve up from the candidate list of the third step until it is back at the size the first step set.

  10. Review the reserve on a fixed date

    Put the reserve review in the owner's diary at an interval the team chooses, and read each post against today's facts, products, results and people, because evergreen content needs scheduled review. At the same review compare the reserve's size with the slots left empty since the last one, retire what has failed, and record the date and what changed.

Reading the result

The reserve is working when an empty slot receives a post that was approved in advance and the owner decides nothing new that day. Read it at the review, not after each use. As general practice, put these questions to the record:

What the record showsWhat it suggestsWhat to change
A slot was still empty at the cut-off, or filled in a hurryThe reserve is smaller than the gap, or holds nothing for that platform or pillarSize it from the gap again and top up the platform that ran short
Posts were retired soon after they were filedThe candidates rested on a fact that changed, and the test was too looseTighten the test in the second step and the rewrite in the fourth, and record what each post rests on
A post ran after its review date had passedThe review was missed, or the release rule let a post out uncheckedMake the release rule check the date
A reply or comment treated a reserve post as out of dateThe post carried something dated, or the gap before it ran again was too shortRewrite or retire the post, and lengthen the gap
Posts sit unused and past their review dateThe reserve is larger than the calendar needsStop topping up and retire the weakest

Read the result notes together, by pillar and format against the account's own history, and not post by post. A reserve post's result is no verdict on the reserve. The question is whether the gap was covered with something the brand was content to have said, not whether the post beat the planned ones, and this tutorial makes no claim about the reach older posts earn.

A harpsichord workshop fills its quiet weeks (illustrative)

Illustrative example — not a real result

A harpsichord workshop sizes and fills its reserve

Ulvankor Harpsichord Restoration, an invented workshop that repairs and restores harpsichords, shows its work on a photo platform and a professional network. Looking back over the last quarter, the owner finds 7 slots that were left empty or filled in a hurry, 5 on the photo platform and 2 on the professional network, and sizes the reserve at 7 posts: 5 for the photo platform and 2 for the network. She takes candidates from the care and how-it-works posts that were typical or better for their format and pillar, and from questions customers ask when they visit, and drops one post because it shows a former apprentice at the bench. Each of the 7 is rewritten without a date, a price or an offer, filed with its caption, image description, source and a review date, and approved by the owner. When a restoration is delayed and the week's footage is not ready, she releases 2 of them, rereads both against what the workshop offers now, publishes them and writes a one-line result note in each row. At the next review one care post is retired because the workshop has moved to a new supplier of parts and the advice it gave no longer matches; its place is filled from the candidate list and the reserve returns to 7.

The social content hub covers the formats, the calendar and the weekly production routine whose gaps the reserve covers.

Common mistakes

  • Filling the reserve with the best performers. A post that travelled may owe its result to a moment. Choose posts that were ordinary or better for their group and read the context behind an outlier.
  • Calling a post evergreen because its subject is durable. The date, price, offer or person inside it decides whether it outlives the week, and evergreen describes the question and not the page.
  • No review date. A reserve post is read as current whenever it runs, so a post nobody has checked is a post nobody can vouch for.
  • Publishing without a reread. The review date and the fixed review are scheduled looks; the reread is the check of one post against today.
  • Using the reserve to cover a calendar the team cannot staff. The calendar's answer to a shortfall is fewer slots, and a reserve that fills the shortfall hides it.
  • Opening the reserve after a pause without reading it. A reserve post is not yet scheduled, and as general practice it is read against what has happened before it runs.
  • Keeping posts whose people or permissions have changed. A colleague who left or a customer who withdrew takes the post out of the reserve.
  • A gap rule nobody wrote down. Without it nothing checks the gap before a post runs again.
  • Letting the reserve grow past what anyone reviews. Size it from the gap and the owner's capacity, and stop topping up when posts sit unused.
  • Borrowing a platform claim to justify the rules. The gap and the release rules are the business's own judgement, written as such.

Frequently asked questions

What makes a social post evergreen?

The question it answers, not the post itself. As general practice, a post qualifies when it answers something the audience asks and would read correctly to a person who found it on a day nobody chose, which means it carries no date, price, offer, event or person it cannot outlive. Even then, the facts and products it rests on change, so each reserve post carries a review date and is reread before it is used.

How many evergreen posts should a social media reserve hold?

As general practice, as many as the account's recent gaps call for and the owner can keep reviewed, and no more. Look back at the slots the calendar left empty or filled in a hurry in recent months, group them by platform and size the reserve to that gap. The site's guides give no share of a posting cadence that a reserve should fill, so no figure is offered here; resize at each review.

Does a platform treat a repeated or re-run post differently?

This tutorial makes no claim about that, and nothing in the site's guides answers it; a platform's own help pages are the place to look. The gap before a post runs again is therefore the business's own rule, set from its own calendar and written down as such, so that the reserve rests on that rule and not on a claim about any algorithm.

Terms used on this page

Frameworks

Related