// HOW-TO · OPERATIONS

Social media workflow checklist (2026): daily, weekly, and monthly

A daily, weekly, and monthly social media workflow checklist for publishing teams: the exact tasks to run each cycle so nothing slips and the feed stays alive.

Last verified · 2026-11-02 · by Moe Ameen

Most social media work does not fail on strategy — it fails on the tasks that go undone because no one wrote them down. A post misses its slot, a comment sits unanswered for two days, last month's numbers never get pulled, and the feed quietly goes dark for a week before anyone notices. A workflow checklist fixes that by assigning every recurring task to a cadence: things you touch every day, things you batch once a week, and the review-and-plan work that only makes sense monthly.

This is that checklist, built as a routine you can actually run rather than an aspirational list. It splits the job into four cycles — a short daily loop, a weekly planning and production block, a monthly review, and a periodic audit of the checklist itself — and tells you exactly what belongs in each. Treat it as a template: trim the items that don't apply to your team size, and keep the cadence even when a given week is quiet, because the discipline is what keeps the feed alive. For the system this checklist sits inside, see [how to build a social media workflow](/how-to/build-a-social-media-workflow); for the cadence math behind it, see [how to create a social media posting schedule](/how-to/create-a-social-media-posting-schedule).

The steps

  1. Build the calendar backbone first (the checklist rides on a plan). A checklist without a content calendar underneath it is just a list of chores. Before the daily loop means anything, you need a planned queue — themes, post types, and slots mapped out at least a week ahead — so "publish today's post" refers to something that already exists. Set your per-platform cadence once, pick the publishing tool or native scheduler you'll use, and agree who owns approvals. Everything below assumes this backbone is in place; if it isn't, start there, not with the daily tasks.
  2. Run the daily loop (community, publishing, and a quick pulse-check). Each working day, in roughly 10–30 minutes: check the inbox across every platform — comments, mentions, DMs — and reply or route the ones that need a human; hide or remove spam and abuse; confirm today's scheduled posts actually went out (don't assume the queue fired); and glance at yesterday's numbers for anything unusual, like a post over- or under-performing. Engage outward too — reply, reshare, or comment on a few relevant accounts — because the algorithm reads your activity, not just your posts. The daily loop is maintenance, not production; keep it short and protect it.
  3. Run the weekly block (plan, produce, and schedule the next week). Once a week, batch the heavy lifting: review last week against the goals you set, then plan and produce the coming week's posts in one sitting and load them into the scheduler so the daily loop stays light. Pull the week's reach, impressions, and engagement rate; identify the top two or three posts and write one line on why each worked, because that note is what makes next week's plan evidence-based instead of a guess. Adjust posting times if the data moved, refresh any running ads, and check that every platform's queue is full through the next seven days before you close the block.
  4. Run the monthly review (report, audit, repurpose, and plan ahead). Once a month, step up a level. Build the previous month's report — growth, reach, engagement, and whatever conversion metric actually matters to the business, not vanity counts — and compare it to the month before. Audit your profiles for stale bios, dead links, and off-brand assets. Plan next month's campaigns and content themes so the weekly block has a map to execute against. And deliberately mine your best-performing posts of the past year to repurpose — the single highest-leverage monthly task, because a proven piece reframed for a new format usually beats a net-new post.
  5. Separate the mechanical items from the judgment items. Go through every item above and mark it M (mechanical) or J (judgment). Mechanical items — publishing on schedule, reformatting one post for each platform, pulling the standard metrics, filling the queue — are repetitive, rule-based, and the first things to automate or batch. Judgment items — deciding what to post, replying to a sensitive comment, reading what a spike actually means, setting next month's direction — stay human. This split is the whole point of the checklist: it tells you where your attention is genuinely needed and where you're just moving files around, which is the line you optimize against.
  6. Audit the checklist itself every quarter. A checklist that never changes slowly stops matching reality. Every quarter (or after any platform change big enough to shift your workflow), re-read the list: cut tasks that no longer earn their slot, add ones you've been doing off-list from memory, and re-time anything whose cadence drifted — a daily task you actually only do weekly, or vice versa. Run a short team retrospective at the same time so the people executing the list get to fix it. The goal is a document that stays true enough that following it is the same as doing the job well.

Common gotchas

  • Treating the checklist as the strategy. A checklist runs the plan; it does not create one. Without a content calendar and clear goals underneath it, you'll execute a tidy routine that goes nowhere.
  • Skipping the daily loop on quiet days. The one time you don't check the inbox is when a question, complaint, or viral moment is sitting unanswered. The discipline is the point — keep the cadence even when it's slow.
  • Assuming scheduled posts fired. Queues fail silently — a disconnected account, a rejected media file, a platform API hiccup. Confirming today's posts actually published is a daily item for a reason.
  • Letting the weekly block slide into daily firefighting. If you never batch a week of content, every day becomes production day and the strategic work never happens. Protect the weekly block on the calendar.
  • Reporting vanity metrics monthly. Follower count and impressions feel good and decide nothing. Tie the monthly report to a metric the business cares about, or the report becomes theater.
  • Never repurposing. Most teams generate endlessly and reuse nothing, leaving their best-proven content to decay. The monthly repurpose pass is where a small team gets leverage.
  • Freezing the checklist. A list written six months ago quietly diverges from what you actually do. If it isn't audited, people stop trusting it and work from memory again — back to square one.

Where Kompozy fits

Run the mechanical/judgment split from step 5 across this whole checklist and a pattern falls out: almost everything that repeats on a cadence — produce the week's posts, reformat each one per platform, keep every queue full, pull the standard monthly numbers, repurpose last year's winners — is mechanical, and it's exactly the work that quietly doesn't get done when a team is thin. [Kompozy](/) is built to carry that mechanical half, so the human hours land on the judgment items instead of the file-moving. It's a full AI content generation and multi-platform publishing engine, not a scheduler bolted onto a calendar.

Map it to the cadences. The weekly block's "produce and schedule the coming week" is where Kompozy earns its place: one source becomes [18 formats](/glossary/output-buckets) — a captioned vertical short, a brand-exact carousel via [HyperFrames](/glossary/hyperframes), a quote graphic, native text posts, a blog, a newsletter — so a week of content comes out of one batch instead of one manual build per platform, every piece held to your [Persona Brief](/glossary/persona-brief) so the voice doesn't drift across surfaces. [Autopilot](/glossary/autopilot) then schedules and fans the queue across the eight social platforms plus blog and email, which turns the daily "confirm today's posts went out" check into reading a status rather than hand-uploading. The monthly repurpose pass — the highest-leverage item on the list and the one most teams skip — is a core workflow here: feed a past winner back in and it re-renders into the formats it never shipped in, including [Clipped Shorts](/glossary/clipped-short) from any long-form source.

Where the checklist stays yours: Kompozy doesn't decide your strategy, answer a sensitive DM, read what a spike actually means, or set next month's direction — the judgment items are the point of keeping a human in the loop, and a per-post review gate in the pipeline keeps one there on everything that ships. What it removes is the production-and-publishing drag that makes the mechanical half slide. Starter ($199/mo for 5,500 credits) fits a solo operator running the full daily/weekly loop for one brand; Pro ($499/mo for 18,000 credits, 9 platforms and full autopilot) sustains a team keeping every platform's queue full on a weekly cadence; Enterprise is available through Contact Sales for agencies running the checklist across many accounts at once.

Frequently asked questions

What should be on a daily social media checklist?

Keep the daily loop short and maintenance-focused: check the inbox across every platform and reply to or route comments, mentions, and DMs; hide or remove spam and abuse; confirm today's scheduled posts actually went out; glance at yesterday's numbers for anything unusual; and engage outward on a few relevant accounts. Planning and producing content is weekly work, not daily — the daily list is about keeping the live feed healthy, which is why most teams can run it in 10 to 30 minutes.

What goes on the weekly versus the monthly list?

Weekly is production and tuning: review last week against your goals, plan and produce the coming week's posts in one batch, schedule them, pull the week's engagement data, flag your top posts, and adjust posting times. Monthly is review and direction: build the previous month's report and compare it to the prior month, audit your profiles, plan next month's campaigns and themes, and repurpose your best content from the past year. A rough rule — if a task needs a week of data to be meaningful it's weekly; if it needs a month, it's monthly.

How long should the daily routine take?

For a maintained account riding a planned queue, the daily loop is usually 10 to 30 minutes — community management, a publish check, and a quick performance scan. It only balloons past that when the weekly block was skipped and you're producing content from scratch each day, or when community volume is genuinely high. If your daily routine regularly runs over an hour, that's a signal the weekly batching isn't happening, not that the daily list is too long.

How often should I update the checklist?

Audit it roughly every quarter, and whenever a platform change is big enough to shift your workflow. Cut tasks that no longer earn their place, add ones you've been doing from memory, and re-time anything whose real cadence has drifted from where the list puts it. Pair the audit with a short team retrospective so the people running the list are the ones fixing it. An un-audited checklist slowly stops matching reality, and once people stop trusting it they go back to working from memory.

Can the checklist be automated?

The mechanical half can — publishing on schedule, reformatting one post for each platform, filling the queue, and pulling the standard metrics are rule-based and repeatable, so a generation-and-publishing engine or scheduler handles them. The judgment half can't: deciding what to post, answering a sensitive comment, reading what a spike means, and setting next month's direction stay human. The useful move is to mark each item mechanical or judgment and automate only the mechanical ones, which is where the checklist frees up real attention.

Related tutorials

← All how-to guides · Get Started