Editorial Calendar

Content is work nobody chases you about. An outage has to be fixed today and a contract has a signing date, but a blog post that doesn't go out this week causes nothing to happen. So it slides. This week there's an event to prepare; next week there are ad creatives to make.

The harder part is that the sliding stays invisible. Everyone carries two or three topics in their head, ideas are scattered across chat threads, and it all feels like motion — while nothing actually ships. The quarterly review is where someone pulls the list and discovers two posts went out in three months.

The conversation that follows is the same every time. Someone asks what happened to the comparison piece planned for last month, the answer is that a draft exists but never got reviewed, and the person meant to review it never knew it had arrived. Topics weren't missing. Writers weren't missing. What was missing was any record of who owed what by when.

An editorial calendar fills that gap. The moment a date and a name attach to a piece, it stops being something to do eventually and becomes something Mia owes on Thursday.

One row is one piece of content, and the row carries seven columns. Work stalls wherever a column is blank, so each one earns its place.

1. Publish date — when readers see it, not when writing starts. Mixing the two meanings in one column means the deadline lands differently for different people.
2. Topic and working title — what the piece covers, written narrowly enough to show its boundaries. "Onboarding" is a category; "five places a new teammate gets stuck on day one" is a piece. Without that boundary, the writer has to call another meeting before starting.
3. Channel and format — where it goes and in what shape. A blog post, a newsletter issue and a short video carry different effort and different lead times.
4. Audience and target keyword — who it's meant for, and what search phrase it needs to rank against. Dropping the phrase from keyword research into this column means the writer has it in hand when choosing a headline.
5. Owners — the writer and the reviewer, listed separately. List only the writer and everything stops once a draft exists.
6. Status — one of planned, drafting, in review, scheduled, published. The value is seeing where work has piled up. Six pieces stuck in review means the answer is more review capacity, not more writing.
7. Published link and results — the URL, plus traffic a month later. With this column filled, next quarter's topics get picked from a record instead of a hunch.

Trimming columns beats adding them. Build twenty of them covering production cost, reference links and approval state, and nobody fills any of them, so a month later the whole table is empty. Seven columns get maintained because each one answers a question somebody actually asks during the week.

One marketer owns the table. Split ownership across several people and the same topic shows up twice, or a row appears that nobody considers theirs. Deciding what to write about belongs to content strategy; this table takes that plan and attaches dates and names to it. Filling it is closer to scheduling a known list than to inventing topics in a meeting.

Four groups read it.

1. Writers — checking which rows carry their name this week. Handing a piece to a freelance writer means sharing that one row and little else.
2. Designers — seeing which rows need cover art or diagrams, and when. The request that lands two days before publication mostly disappears once this table exists.
3. Sales — knowing what ships next month means having material ready for customers ahead of time.
4. Founders and leads — comparing the quarterly plan against what actually went out. Two posts against a plan of twelve is a staffing conversation, not a writing one, and the table is what makes that visible without anyone assembling a report.

Weekly updating is enough. Touching it daily turns maintenance into its own job; touching it monthly means slippage goes unnoticed until it's too late. Thirty minutes on Monday spent scanning the status column and re-dating the rows that slipped is the rhythm that survives.

"Fill in next month's calendar. Three slots still have no topic."

Publishing slots exist, topics don't, and someone needs to propose them.

"This week's piece slipped to next week — review is backed up."

The publish date moved, which means the date column changed.

"If it isn't on the calendar, it isn't getting written this quarter."

Being in the table is the condition for starting at all, which also means late requests get scheduled rather than squeezed in.

Pagedeck fills the table once a quarter. Ravi opens twelve slots for the coming quarter and places the agreed topic list into them: eight pieces of evergreen content aimed at search traffic, four tied to feature releases. The evergreen pieces get locked to dates because they'll still be read a year from now; the release pieces get loose dates because ship dates move.

A month in, the table stops matching the plan. A release slips two weeks, so its post moves wholesale and an evergreen piece pulls forward into the gap. One post that did well goes through content repurposing and comes back as two videos with their own rows. Ravi makes all of these adjustments in one pass on Monday.

The most common mistake is expecting the table to make publishing happen. The plan is visible, which feels like being halfway done, and building it takes two hours. But a table shows what slipped; it doesn't write anything. Unless writing time sits in someone's weekly schedule, the calendar becomes a document nobody opens within a month. The thing to settle before filling it in is how many hours a week go into this. At four hours a week, one piece a month is the honest plan, and the table should hold one row a month rather than four. A calendar that promises more than the available hours produces the same two posts a quarter as no calendar at all, with the added cost of everyone watching the dates slip.

Reading "denser is better" into it has the same shape. Publishing three times a week looks three times better than once a week, but a blog post needs a certain depth before search picks it up at all. Cut depth to hit a count and all three go unread, while the writer burns out and publishing stops two months later. Set the cadence at a level that holds, and spend whatever capacity is left improving pieces that already shipped.