Plānot un publicēt nedēļas sociālo tīklu ierakstus

Kad izmantot

Every week, for the company's own social channels. Not for one-off campaign or launch content — use growth.launch-website or a project task when a launch needs coordinated posts. Not for the newsletter — use growth.newsletter; a newsletter may reuse a week's best post, but it is planned and approved separately. If a post mentions a competitor's moves, first check growth.competitor-scan so the claim is current.

Pirms sāc

• The channel list is fixed: which networks the company maintains, and the norm per channel (e.g. LinkedIn
• The owner's off-limits list exists and is current.
• The agent has write access to each channel (or to the scheduling tool the company uses) and to the content log.

Ko izpilde pieprasa1

Ceļš7 soļi

1. S1

   Collect the week's materialaģents

   Pull last week's results from the content log, anything new from tasks and goals (a shipped feature, a finished job, an open role), and questions customers actually asked this week.

   Izdarīts, kad a short list of candidate topics exists, each with its source.

2. S2

   Draft the postsaģents

   For each channel, draft the posts for the week: text per channel's norm, image or asset where the channel expects one, link target, and the planned day. Mark every factual claim with its source.

   Izdarīts, kad a draft set exists — typically 2–4 posts per maintained channel — with each post labelled by channel and day.

3. S3

   Approveīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S3 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Show the draft set in one view: post, channel, day, claim sources. The owner edits or strikes posts and names anything newly off-limits.

   Izdarīts, kad the owner has approved each post or struck it, and the off-limits list is updated if it changed.

   ⛔ A post with a price, a legal claim, or a customer's name is never published on the agent's judgement alone.

4. S4

   Schedule and publishaģents

   Load the approved posts into the scheduler or publish them on their planned days, exactly as approved — no wording changes after approval.

   Izdarīts, kad every approved post is live or scheduled, and the live links are recorded in the content log.

5. S5

   Watch and answer within boundsaģents

   Check comments and messages on the posted items. Answer factual questions using approved wording; forward complaints, negotiation, and anything about a specific customer to the owner the same day.

   Izdarīts, kad every comment or message is either answered or handed to the owner, with the handover noted in the log.

   ⛔ Do not argue with a critical comment in public — ops.customer-complaint owns that path.

6. S6

   Record resultsaģents

   At the end of the week, enter per post: reach, engagement, clicks, and one line on what the numbers say compared with the trailing four weeks.

   Izdarīts, kad every published post has a results row in the content log.

7. S7

   Feed the next cycleaģents

   Propose 2–3 topics for next week based on S6 (what worked, what did not), and open a task for anything the owner must supply (a photo, a customer quote).

   Izdarīts, kad next week's S1 starts with a candidate list ready.

Pārbaudes — kā zinām, ka izdevās

• Every post published this week traces to an approved draft in S3 — nothing extra went out.
• Each live post's link opens and shows the approved wording, on the channel it was planned for.
• The content log has a results row for every post, with real numbers, not estimates.
• Zero unanswered comments or messages older than one working day on company posts.

Ja noiet greizi

Ko atstāj katrs solis

1. S1a short list of candidate topics exists, each with its source.
2. S2a draft set exists — typically 2–4 posts per maintained channel — with each post labelled by channel and day.
3. S3the owner has approved each post or struck it, and the off-limits list is updated if it changed.
4. S4every approved post is live or scheduled, and the live links are recorded in the content log.
5. S5every comment or message is either answered or handed to the owner, with the handover noted in the log.
6. S6every published post has a results row in the content log.
7. S7next week's S1 starts with a candidate list ready.

Ko saglabāt

The approved draft set (who approved, when) · live links per post · the content log rows with metrics and dates · the off-limits list version in force that week · any comment handed to the owner and its outcome.

Kā šī procedūra uzlabojas

After every 8 runs ask: planned vs published — where did weeks fall short, and was it missing material or missing approval? Which post formats beat the four-week average, and should the channel norms change? Did any post go out unapproved or with an unsourced claim? A new version changes the step that failed and says so in its change note.