Social content: a post is an announcement, not a document

This page is filed under content marketing rather than under social media management, and the filing is the argument. The article on managing social accounts describes a cadence; this one describes what travels through it and where that has to be kept.

The distinction fits in a sentence: a post is an announcement, never a document. It draws attention to something, and that something has to exist elsewhere — on a page, in a record, in a file — or it does not exist at all three weeks later.

That is why very active accounts produce so little. They manufacture announcements every week with nothing to announce, and the work evaporates at the speed of the feed. The effort is real, the result is nil, and nobody understands why.

So this article describes the part nobody sees: where the material lives, who holds it, how one answer takes five shapes, and what approval circuit still allows something accurate to be published on the day it is useful.

Here is the point nobody anticipates and everybody discovers at the wrong moment: you will not find your own posts. A feed is scrolled, not searched, and the tools the platforms provide change almost nothing about that.

The concrete case is always the same. A customer asks for the specification of an item posted in November. Whoever replies knows it exists, scrolls for four minutes, does not find it, and ends up retyping the information from memory — or asking the workshop, which costs twice.

The consequence is an organisational rule rather than editorial advice: the source material never lives in the account alone. Texts, images, figures, ready-made replies: all of it is filed at your premises, by the logic set out in the content-creation article — reference, then number.

That applies to the texts as well. A post written directly in the app is a text that exists only there. Write it in a file, publish afterwards, and you keep a reusable library instead of a history nobody can interrogate.

And it applies at the moment of changing supplier, which happens more often than anybody plans for. An agency that hands back an account without handing back the files hands back nothing: it leaves you a wall of posts that nobody, itself included, can reuse.

The article on social media management establishes a structural limit: an agency cannot know your facts, because they live with you and expire daily. This page draws the organisational consequence, which is rarely drawn.

The bottleneck in a content service is never the writing. It is access to the person who knows: the storeman who knows the stock, the workshop head who knows the real lead time, the owner who decides the discount. The writing waits, and the waiting is what misses the date.

The correction is not a monthly meeting. It is a short, permanent channel — a message thread with two named people — where "what does this one cost" gets an answer within the hour. Every other part of the arrangement is secondary to that.

An unpleasant consequence has to be accepted too: if nobody on your side can answer within the hour, the service cannot be daily. It will be weekly, and it is better to decide that than to suffer it in the form of vague posts that avoid facts.

Vague posts are in fact the diagnostic symptom. When an account talks about values, passion and quality without ever giving a price or an availability, it is almost never an editorial choice: it is access to information that was never organised.

The article on social media management establishes that every editorial calendar dies around the sixth week because it assumes the material will exist. This page draws the storage method rather than restating the argument.

What replaces the calendar is a reserve: ten to fifteen pieces ready, undated, usable at any time. They come from the photography session, from the recurring questions, and from the repeatable formats — the delivery, the instructions, the prepared order.

That reserve has a precise function: it protects the days when nothing arrives. Without it, an empty day produces either silence or a filler post, and the filler post costs more than the silence because it teaches the reader to stop looking.

Fixed dates exist and there are few of them. Ramadan and Eid, the school year, the regulated sales periods, and the one or two dates specific to your trade — the building season, the university term, the wedding peak. About five, and they get prepared three weeks ahead.

Everything else has to be attached to an event that already happens on your premises. It is the only arrangement that survives a busy quarter, because it asks nobody to invent a subject on a day when the workshop is behind.

What we will refuse: running social content for a business that cannot name anybody to answer a question of fact within the day. That is not a comfort requirement — without that access the service produces vague posts, and we would be paid to manufacture the symptom described in section 5.

We will refuse to publish towards a page that does not yet exist, or towards a record with no price. An announcement that sends people into a void spends your credit with people who were ready to buy, and it is the hardest expense to recover.

We will also refuse to keep the texts and files. They live at your premises, in a named and filed library, and the account is never the storage — including when that makes changing supplier easier for you.

What we do: the document written before the announcement; one main surface and a second only if it asks for no new trade; a short channel with two named people on your side; ready-made replies prepared before publication; and a reserve of ten to fifteen undated pieces that protects the empty days.

And what you can do this week without us: open your last twenty posts and note, for each, what it points at. Count the ones that point at nothing. That number is the whole diagnosis, and it is free.