Creating a social media editorial calendar: a process from topic idea to approval

Anyone who handles social media for a business knows the problem: there are plenty of ideas, but they are scattered across emails, chats and notes. A social media editorial calendar brings order to this process. It shows which topic should appear on which channel and when, who is working on it, and whether a post has already been approved. In this article we describe a practical process from the first topic idea to approval that also works for small teams without their own marketing department.

What a social media editorial calendar is for

An editorial calendar is not software in the first place but an agreement within the team. It defines where topics are collected, what information a post needs and who makes the final decision. Only once these questions are settled is it worth thinking about tools. Many problems in social media planning are not caused by missing technology but by uncertainty about which version of a text is current or whether management has already seen an image.

With social media for businesses there is another point: every post publicly represents your company. A traceable path from draft to publication is therefore more than a formality. It prevents misunderstandings and takes pressure off the people who look after the channel day to day.

Collecting topics: customer questions and existing material

The best topics are often already inside the company. Questions that customers ask on the phone, by email or in person are a good starting point. If a question comes up several times, the answer probably interests others as well. Record such questions in one fixed place, for example a simple list that everyone on the team can access.

Then there is existing material: photos from everyday work, texts from the website, explanations from quotes, answers to frequent queries, or dates such as trade fairs and company holidays. Much of this can be adapted for social media without starting from scratch. For images and texts from third parties, however, clarify in advance whether you are allowed to use them.

What information every post needs

To make a post plannable, it should always have the same fields. That way everyone on the team can see at a glance what is still missing.

• Text: the draft of the post, if needed in variants for different channels
• Media: image, graphic or video, with a note on where the material comes from
• Channel: the platform on which the post should appear
• Date: the planned publication date, with a time if needed
• Responsible person: who prepares the post and answers questions
• Status: draft, correction or approved

Depending on the company, further fields may be added, such as a reference to the original customer question or a field for internal notes. Keep the list as short as possible, though, so that it actually gets maintained in daily work.

Draft, correction, approved: three separate states

A common mistake is keeping drafts and finished posts in the same document without clear labelling. Separate at least three states. A draft is work in progress and may change at any time. In correction, the post is with the reviewer and waiting for comments. Approved means that text, media, channel and date are confirmed as they are and the post may be published.

This separation sounds trivial, but it prevents an old version from going online by mistake. It also shows where posts get stuck, for example when many drafts are waiting for a correction at the same time.

Content approval: who decides and what happens afterwards

Decide who approves posts. In small companies this is often the owner; in larger teams it may be a specialist department or the communications team. It also matters who decides when that person is absent, so that content approval does not get stuck during a holiday.

Just as important is a rule for changes after approval. If an approved text is adjusted again, it should go back into correction. You can treat small typos differently from changes in content, but this distinction should be agreed in advance rather than decided case by case under time pressure.

Keep using your existing tools

An editorial calendar does not have to be built in a new system. Many teams already work with a spreadsheet, a shared calendar, a project management tool or a cloud folder for images. It is often more sensible to connect these tools properly and use fields and states consistently than to move everything to a new program. What matters is that there is one place where the current status of a post is binding.

Preparing publication

Once a post is approved, publication follows. This can be done manually, with a responsible person posting the approved content at the planned time. It can also run through a checked connection to a platform, provided the platform allows such a connection and access has been set up.

There is no blanket automatic publishing on all platforms. Account access, permissions and the rules of each platform have to be checked individually. Some formats or channels can only be handled manually. A good process takes this into account from the start instead of being surprised by it later.

And who creates the content?

Some teams want not only to organise the process but also support with texts or graphics. This is possible as part of social media management. Before that, however, scope, available material, usage rights and editorial responsibility should be clarified. Responsibility for what appears in your company's name remains with you. Approval is the point at which you exercise that responsibility.

A simple way to start

If you want to get started right away, a few steps are enough:

• Create a shared list for topics and customer questions
• Define the fields every post should have
• Agree on the three states draft, correction and approved
• Decide who approves and who stands in
• Clarify for each channel whether publishing is manual or via a checked connection

Du First helps businesses across Germany set up a process like this. Setup is done once, online, by video call, phone or email, and builds on the tools you already use. As a guide, packages start from 149 euros net per month plus VAT; the exact scope depends on your channels and requirements.

To see which kind of support suits your team, take a look at our pages on services and packages. There you will find an overview of the options and indicative prices.