A social media workflow is the fixed path a post takes from idea to published, with a named owner and a deadline at every step. Without one, every post is negotiated from scratch and the bottleneck moves around unpredictably.
Below is a six-stage workflow with time estimates, the rules that make handoffs work, and the three places these break.
The six stages
| # | Stage | Owner | Time (per 10 posts) | Deadline |
|---|---|---|---|---|
| 1 | Ideas | Everyone, one place | Ongoing | Continuous |
| 2 | Plan | Social lead | 30 min | Thursday, week -2 |
| 3 | Produce | Writer + designer | 2 hrs | Monday, week -1 |
| 4 | Review | Approver | 20 min | Wednesday, week -1 |
| 5 | Schedule | Social lead | 15 min | Thursday, week -1 |
| 6 | Respond and measure | Community + lead | 15 min/day, 45 min/month | Daily, then month end |
The “week -1” notation means the week before publication. Everything is drafted and approved a week ahead, which is the single change that removes most of the stress from a social calendar.
Stage 1: ideas (continuous)
One inbox for ideas, and only one. A channel, a doc, a board, it does not matter which, as long as there is exactly one and everyone knows it.
The rule that makes it work: ideas are captured without judgment and evaluated only in stage 2. If ideas get debated the moment they are posted, people stop posting them.
Stage 2: plan (30 minutes, fortnightly)
The social lead reads the idea inbox, picks the posts for the next cycle, assigns each a pillar, a format, a channel and a slot, and writes one line describing each. Output is a numbered list, not drafts.
Half an hour is enough because the decisions are small and the material already exists. If this stage takes two hours, the strategy is missing and you are writing it here. Fix that with an actual strategy document.
Stage 3: produce (2 hours per 10 posts)
Captions written back to back, then media produced in one pass. This is the batching stage, and it is where the workflow either saves time or does not.
Handoff rule: a post is not “produced” until the caption and the media are both attached to the same item. Half-finished items are what makes stage 4 miserable.
Stage 4: review (20 minutes per 10 posts)
The approver gets the whole batch at once, on a deadline, and returns it approved or with specific changes. Not “some thoughts”. Specific changes.
Three rules keep review from becoming the bottleneck:
- One approver. Two approvers means two rounds and contradictory notes.
- A deadline with a default. If review does not happen by the deadline, the batch publishes as drafted, or it is held and the slots are lost. Pick one and write it down. Silent indefinite waiting is what kills calendars.
- Two rounds maximum. Round three is a new brief.
For agency work, the deadline and the consequence should be in the contract, not just the workflow doc.
Stage 5: schedule (15 minutes per 10 posts)
Approved posts go into the queue with times set. This should be the fastest stage. If it is not, the tooling is wrong: loading approved posts one at a time through a single-post composer costs about two minutes each, which is most of your stage-5 budget.
Before you close the tab, read the queue in order as a reader would. Three product posts in a row is only visible in the queue view, never in a document.
Stage 6: respond and measure (15 min/day, 45 min/month)
Replies get a fixed daily window rather than a permanent open tab. Notifications all day is the largest single time sink in social media work and it is invisible because it never looks like work.
At month end, one reporting session. The report template is the deliverable, and its “next period” section feeds back into stage 2.
Where workflows break
Between produce and review. The batch is sent and then nothing happens. This is the most common failure by a wide margin, and it is always fixed the same way: a deadline plus a stated consequence.
Between review and schedule. Approved posts sit in a document because moving them into the scheduler is manual and tedious, so it gets postponed to Friday and then to Monday. This gap is pure tooling.
Between measure and plan. The report gets written and never read at the next planning session. Fix it by opening last month’s report at the start of stage 2. That is the whole fix.
A one-person version
Solo, the workflow compresses but the stages stay:
| Stage | When | Time |
|---|---|---|
| Ideas | Continuous, one note app | Ongoing |
| Plan + produce | One fortnightly session | 2 hrs 30 min |
| Review | Next morning, fresh eyes | 15 min |
| Schedule | Same session as review | 15 min |
| Respond | Daily window | 10 min |
| Measure | Monthly | 30 min |
The only stage solo operators should not skip is review, and it works only if it happens on a different day from writing. Reviewing your own captions ten seconds after writing them finds nothing.
What most people get wrong
No named owner per stage. “The team” owns a stage means nobody does.
Reviewing post by post. Ten separate approvals cost far more than one batch approval, for the reviewer most of all.
No default for a missed deadline. Ambiguity here is what turns a one-day slip into a three-week gap.
Working in the current week. Producing this week’s content this week means every sick day becomes a publishing gap. Work a week ahead and the gap absorbs itself.
Measuring without a feedback loop. A report nobody opens during planning is a filing exercise.
Treating replies as continuous. Set a window. Two a day if the volume demands it.
Making the handoffs cheap
The two breakages above that are not about discipline are produce-to-review and review-to-schedule, and both are handoff costs.
They get cheaper when the draft never leaves the tool it will publish from. In BulkPublish that means a batch is composed once, sent for approval as a set with a reviewer named on it, and the approved posts are already in the queue: there is no retyping step between stages 4 and 5. The calendar is where you do the read-in-order check, and labels let you see at a glance whether the fortnight is three quarters product posts. If you are running this for several clients, our agencies page covers keeping the workflows separate.
The short version
Six stages: ideas, plan, produce, review, schedule, respond and measure. Work one week ahead. One idea inbox, one approver, one batch review with a deadline and a stated consequence, maximum two revision rounds. Read the queue in order before you close it. Give replies a fixed daily window. Open last month’s report at the start of the next planning session.