Most posting schedules do not fail because the strategy was wrong. They fail because the strategy required a good week every week, and nobody has those. The calendar looked realistic on a quiet Monday; by Thursday a launch, a support fire and a meeting had eaten the drafting hour, and three grid cells were empty.

The fix is not more discipline. It is a routine: a small set of repeating blocks with fixed jobs attached, sized so they still fit in a bad week. This guide lays out the blocks, gives you a sample week to copy, and shows where a calendar and a queue carry the load so the routine does not depend on you having a free afternoon.

Decide the output before you design the week

Write down one number: the minimum number of posts you will publish every week, forever, without negotiating. For most small teams that number is three to five, not fifteen. Pick it honestly, because a floor you keep for six months beats a ceiling you hit twice.

Everything else follows from that number. Five posts across two platforms is roughly two writing sessions and one queueing session a week. Twenty posts across five platforms is a different job, and if that is genuinely your output you need a second person in the routine rather than a longer Tuesday.

Two decisions belong with the number:

• Which platforms are primary. One or two where the audience actually concentrates. The rest are distribution, not destinations, and they get the adapted version of the primary post rather than their own production line.
• What kind of posts count. If the floor counts only original content, a week where you reshared three things is a failure. If it counts anything published with intent, the floor is much easier to hold. Decide which, in writing, the first week.

The five blocks

A weekly routine is not a list of tasks. It is five named blocks that recur in the same order, so you never have to decide what to do next.

• Plan (45 minutes, Monday). Look at what is happening this week — launches, events, replies worth surfacing, anything seasonal. Choose the topics. Do not write anything.
• Draft (one or two sessions, Monday or Tuesday). Write everything in one sitting with the same voice brief open. One post at a time costs a context switch each; seven cost one.
• Queue (30 minutes, Wednesday). Move the drafts into slots, attach media, set per-platform overrides, and send anything that needs a second pair of eyes into review.
• Watch (15 minutes, Thursday). Read the queue, not the metrics. Confirm every scheduled post still points at a connected account and that nothing failed overnight.
• Review (20 minutes, Friday). Six numbers, three sentences, one decision about next week. The block that gets cut first and matters most.

If you only keep two of the five, keep Draft and Review. A routine without a drafting block produces improvised posts; a routine without a review block never improves.

A sample week you can copy

Here is a week built for one person doing five posts across two platforms. Shift the days if your audience peaks at the weekend — the order matters more than the calendar dates.

• Monday, 45 min: plan. Read the week, pick five topics, note which one is the anchor.
• Tuesday, 90 min: draft. Write all five captions, decide the media for each, flag the one that needs approval.
• Wednesday, 30 min: queue. Assign slots, apply per-platform variants, submit the flagged post for review.
• Thursday, 15 min: watch. Check the queue and the failures list before anything else.
• Friday, 20 min: review. Pull the six numbers, write three sentences, set next week's topics while the context is fresh.

Total: about three hours a week, and the hours are predictable. You can defend a fixed 90-minute block in a way you cannot defend "some time to write posts".

Size the drafts for the week you will actually have

Draft 150% of what you need. If the floor is five posts, write seven. Two things happen: the queue gets a small buffer that absorbs an unexpected Tuesday, and you stop treating every draft as precious because there are spares.

The buffer only works if it is visible. Keep the spare drafts as drafts rather than deleting them, and watch the queue's fill indicator so you can see how far ahead you are. A queue that is always three days from empty is a routine operating without a safety margin, and it will eventually empty on the day you have least time.

The other half of sizing is refusing to draft in the queue. Writing directly into a scheduling box produces posts shaped by the box — shorter, flatter, more generic. Draft in a document or a scratch pad, then move finished copy into the composer. The content calendar playbook covers the planning side of this in more detail.

Let the calendar hold the plan, not your memory

The single most expensive habit in social media is remembering. Remembering that the post goes out Thursday, remembering which draft is approved, remembering that LinkedIn still needs its own first line. Every one of those is a small open loop, and a week is only as calm as the number of loops still open.

Put the plan somewhere with a visual week and let it be the authority:

• A week or month view with drag-and-drop, so moving a post when the day changes is a drag rather than a re-edit. PostHub's calendar has month, week and list views and reschedules by dragging, which is what makes a Thursday reshuffle cost four seconds instead of four minutes.
• Status you can read at a glance — draft, scheduled, published, failed — so the question "is Wednesday covered?" is answered by looking, not by opening five posts.
• One place for notes on the day, so the idea you have on Friday night is attached to the day it belongs to rather than living in a notes app you will not reopen.

The calendar's job is to make the plan visible. Your job is to keep the routine.

The minimum viable week

Design the bad-week version of the routine in advance, on a good week, because you will not design it during a bad one.

The minimum viable week is the smallest version that still counts as keeping the floor: two posts from the buffer, scheduled Monday morning, plus a five-minute Friday check. Fifteen minutes total, no new writing, and the streak does not break.

Three rules make it work:

• The buffer must exist before the bad week starts. A minimum viable week with an empty queue is just a missed week with extra steps.
• Publishing from the buffer is not a failure. Teams that treat reused or lightly refreshed posts as cheating eventually stop maintaining the buffer entirely.
• The review still happens, even if it is five minutes. Skipping it once is fine; skipping it three weeks running is how a routine quietly stops being a routine.

Where PostHub fits, and where it does not

PostHub carries the mechanical half of this routine. The calendar and queue hold the plan and its statuses, drag-and-drop reschedules a slot without re-editing the post, groups give each set of accounts its own timezone so Wednesday 09:00 means the right 09:00 for that audience, and labels give every post a colour tag so the planned mix is visible rather than remembered. Approvals handle the one post in the week that genuinely needs a second pair of eyes, off the chat thread.

What it does not do is run the routine for you. It will not pick next week's topics, notice that your last three posts all led with the same angle, or tell you that the Friday review has been skipped for a month. The blocks — plan, draft, queue, watch, review — are still yours to hold, which is exactly why they are worth writing down.

Common routine mistakes and fixes

• Mistake: the routine is planned in ideal conditions. Fix: run it for two weeks, then cut the longest block until it survives a normal week.
• Mistake: every block happens on a different day. Fix: collapse drafting and queueing into one session where possible; context switches cost more than the tasks do.
• Mistake: the queue is always empty. Fix: draft 150% of the floor and treat the spare posts as inventory, not leftovers.
• Mistake: the review block reports on feelings. Fix: six numbers, three sentences, one decision — anything longer stops happening.
• Mistake: one person holds the whole routine in their head. Fix: write the five blocks into a shared doc and put the calendar where the rest of the team can see it.

Key takeaways

• Set a weekly floor you can keep in a bad week, and decide in writing whether reshared posts count toward it.
• Build the week from five blocks: plan, draft, queue, watch, review. Keep drafting and review even when time is short.
• Draft 150% of what you need and keep the spare posts visible as a buffer.
• Let a visual calendar be the display of the plan, never the plan itself, and design a minimum viable week in advance.
• The tool automates slots, statuses and approvals; the judgement about what to post stays with you.

FAQ

How often should I actually post each week?

There is no honest universal number; any figure without your platform, audience and format attached is a guess. What is measurable: pick a floor you can hold for a quarter, publish at it for four weeks, and read whether reach and engagement per post moved before changing it. Frequency that forces quality down usually costs more than it buys.

Should the routine be different for a team than for one person?

The blocks stay the same; the ownership changes. With two or more people, drafting and review separate — one person drafts, another approves — and the queue becomes the shared surface rather than one person's list. PostHub's approval queue and per-group settings exist for exactly that split, and the team approval workflow covers how far to take it.

What if my audience is global and my week is not?

Anchor the routine to your own clock and let the scheduling slots carry the audience's. Groups hold their own timezone for scheduling, so a Tuesday 06:00 slot for one region and a Tuesday 18:00 slot for another both come out of the same Tuesday drafting session. The best time to post guide covers how to choose those windows without guessing.