A 4-week content calendar you can actually keep

Most content calendars collapse for one reason: "post every day" is a schedule, not a plan. Every morning becomes a decision, and decisions are where consistency goes to die. This is a calendar built to survive that. It decides the kind of post ahead of time so that filling any given day is a small task instead of a blank page. You'll get the five buckets it runs on, a filled four-week example you can copy, notes for adapting it per platform, and a template to reuse each month.

What a content calendar actually is

A content calendar is a plan that assigns each posting slot a job before you write a word. Not the exact caption, and not a rigid script. Just the type of post that goes there: a teaching post, a proof post, a personal one. The value isn't the grid. It's that you never sit down to "do social" and instead sit down to "write today's proof post," which is a task small enough to actually finish.

A good calendar does three things: it stops you repeating the same note two days running, it removes the daily "what do I post" decision, and it leaves room to react when something real happens.

The five buckets

Rotate every post through five recurring types. Each does a different job for your audience.

1. Expertise & frameworks. Teach one thing you know well. Example: "The three questions I ask before taking on any client." These build authority.
2. Industry take. React to something happening in your field. Example: a short, opinionated post on a competitor's pricing change. Timely, and it shows you're paying attention.
3. Proof. A result, a case, a before-and-after. Example: "How we took a client from 200 to 2,000 followers in eight weeks." This is what convinces buyers.
4. Build in public. What you're working on, what broke, what you learned this week. Example: "We changed our onboarding and support tickets dropped by half." Honest and relatable.
5. Human. A moment, a story, something that isn't strictly business. Example: "What running taught me about shipping work." This is what makes people remember you, not just your feed.

Across four weeks you touch all five repeatedly without ever running two of the same in a row.

A filled example: four weeks

Here's the rotation as a real grid, Monday to Friday. The bucket is the job; the note is a sample angle you'd swap for your own.

Twenty slots, five buckets, no two the same twice in a row. You can shift the order to fit your week; the point is that every day already has a job.

Adapt it per platform

The buckets stay the same across platforms; the format changes.

• LinkedIn. Longer posts work. Lean into Expertise, Proof, and Human, and open every one with a strong first line (how to write a hook that earns the click).
• X (Twitter). Shorter and faster. Industry takes and Build-in-public fit best, and longer points become threads (thread structures that get read).
• Instagram. Visual-first. Proof (before/after) and Human (behind-the-scenes) translate best to images and carousels.
• Newsletter. Depth. One Expertise or Proof piece a week, expanded, with the shorter social posts feeding it.

Run the same five-bucket rotation, and let each platform take the version of the bucket that suits it.

Map the month in one sitting

Don't plan day by day. Sit down once, open the grid, and drop bucket labels across four weeks. You're not writing yet, just assigning jobs. That's twenty small decisions made together, when you have context, instead of twenty decisions made cold at 8am.

Batch the writing

Once the slots have jobs, write in batches by bucket. Three "proof" posts back to back is far faster than one of each, because you stay in the same headspace and reuse the same raw material. Block an hour, pick a bucket, and draft everything of that type for the fortnight.

Leave room to react

Keep one or two slots a week loose. When something real happens (a launch, a news moment, a customer win), it goes there. A calendar that's 100% pre-planned can't respond to the present, and the present is usually your best material. The loose slots are where the calendar meets real life.

A reusable template

Copy this and refill it each month:

• Buckets: Expertise, Industry, Proof, Build, Human.
• Grid: 4 weeks × your posting days, one bucket per slot, no repeats back to back.
• Loose slots: 1–2 per week, left open for reactive posts.
• Batch blocks: one writing session per bucket, per fortnight.
• Feed loop: at month's end, note which posts landed and make more of that bucket next month.

Frequently asked questions

How many times a week should I post? Whatever you can keep up without dropping quality. Five weekdays is a full rotation; three is fine and beats five you can't sustain. Consistency matters more than frequency.

How far ahead should I plan? Plan the buckets for four weeks; write one to two weeks ahead. Planning the jobs far out is cheap and stabilizing; drafting the exact words too far ahead means rewriting when the moment shifts.

What if I run out of ideas for a bucket? That's usually a capture problem, not a creativity one. Keep a running note of raw ideas as they hit you, and shaping a week's posts becomes selection instead of invention. See the idea-to-published pipeline.

Do I need a tool for this? A spreadsheet and a notes app run it fine for one brand. Across several clients, each needing its own grid, buckets, and drafts, keeping it all straight becomes its own job. That's where SelfSM takes over: it plans the month, drafts each slot in the brand's voice with the AI tells stripped, and ships the posts, with Chloe running the calendar alongside you like a brand manager.

The goal is simple: never face a blank page cold. Give each day a job, batch the work, and leave a little space for real life to interrupt.