Why a blog needs an editorial calendar that runs on numbers
If you run a company blog, a food site, a shop journal or any publication with more than one writer, you already have an editorial calendar: a list of what should go live and when. Many calendars stop there. They say what is planned, but nobody checks what really happened, how long each post took, what it cost, whether the mix of topics matches the plan or which old posts are quietly going out of date. The calendar becomes a wish list.
An editorial calendar operation is the habit of measuring the calendar itself. It does not judge whether a post was good or how many readers it earned; that is the job of content marketing ROI and analytics, and a separate course covers it. This course is about the machinery behind the posts: cadence (how often you publish), capacity (how much your writers can really produce), turnaround (how long a post takes), cost per post, the content mix by funnel stage, the on-time rate and the update cycle of old posts.
The good news is that you need no special software. A spreadsheet with a few columns answers most operational questions, and the maths is simple: sums, ratios, a few lookups and counts. The skill is knowing which ratio to calculate, which base to divide by and how to read the result without fooling yourself. This free first lesson starts with the most basic control number of all: planned versus published.
The example is Larchmoor Kitchen, a fictional cookware shop with a recipe and how-to blog. Its team planned posts for twelve weeks and kept a simple log of what was published. All companies, people, posts and numbers are invented for learning. You will use exactly the same twelve weeks as in the lab above.
The core idea: attainment against the plan
A publishing cadence is a promise: three or four posts per week, one newsletter feature every Friday, one big guide per month. The promise is made to readers, who return when they expect something new, and to the rest of the company, which plans promotion, newsletters and social posts around the dates. A promise can be kept or broken, and you can measure how often it was kept.
The measure is the attainment rate: published posts ÷ planned posts. If you planned 3 posts and published 2, the attainment is 2 ÷ 3 = 66.7 %. If you planned 3 and published 3, it is 100 %. Posts published beyond the plan would push it above 100 %, but that is rarely a goal in itself: unplanned posts usually mean that something else was dropped or that the plan was too timid.
The worked example: 12 weeks at Larchmoor Kitchen
Here is the full log. In 12 weeks the team planned 38 posts and published 33. Weeks in bold are weeks where fewer posts went live than planned.
| Week | Planned | Published | Attainment | Cumulative published |
|---|---|---|---|---|
| Wk 1 | 3 | 3 | 100 % | 3 |
| Wk 2 | 3 | 2 | 66.7 % | 5 |
| Wk 3 | 3 | 3 | 100 % | 8 |
| Wk 4 | 4 | 4 | 100 % | 12 |
| Wk 5 | 3 | 2 | 66.7 % | 14 |
| Wk 6 | 3 | 3 | 100 % | 17 |
| Wk 7 | 3 | 3 | 100 % | 20 |
| Wk 8 | 3 | 2 | 66.7 % | 22 |
| Wk 9 | 4 | 4 | 100 % | 26 |
| Wk 10 | 3 | 3 | 100 % | 29 |
| Wk 11 | 3 | 1 | 33.3 % | 30 |
| Wk 12 | 3 | 3 | 100 % | 33 |
| Total | 38 | 33 | 86.8 % |
Two things stand out at once. First, 8 of the 12 weeks were kept in full, and 4 weeks (weeks 2, 5, 8 and 11) fell short. Second, week 11 was the worst: one post instead of three. A look at the picture below makes the pattern clearer than the table does.
Step 1: the weekly attainment rate
The first column to build is the attainment rate per week. In the lab, planned posts are in column B, published posts in column C, and the rate goes in column D. In D4 you type =C4/B4 and copy the formula down to D15. Excel adjusts the row numbers for you, so D5 becomes =C5/B5, which gives 2 ÷ 3 = 66.7 % for week 2.
Format the column as a percentage, otherwise you will see 0.667. The order matters: published goes on top, planned below. Reversing it (=B5/C5) gives 150 %, which looks like a great week but is only an upside-down fraction. If a planned value could be 0 (a week with no plan), protect the formula with =IF(B4=0,"",C4/B4) so that you do not divide by zero.
Step 2: the running total
Weekly numbers jump around. A single sick day can turn a week of three posts into a week of one. To see whether the blog is falling behind for good, build a running total (also called a cumulative total). In E4 you type =SUM($C$4:C4) and copy down. The first reference has dollar signs: it is an absolute reference that stays on C4 when you copy the formula. The second reference has none, so it moves down one row at a time: in E5 you get =SUM($C$4:C5), in E9 =SUM($C$4:C9).
The running total after week 6 is 17 posts. After week 12 it is 33. You can build the same running total for the plan and compare the two lines. That comparison is more honest than any single week, because it shows the accumulated shortfall.
Step 3: totals and the overall attainment
Now summarise the whole period. In B17 add up the published posts with =SUM(C4:C15). The result is 33. For the overall attainment divide by the total planned posts: =B17/SUM(B4:B15) gives 33 ÷ 38 = 86.8 %.
You may be tempted to average the twelve weekly percentages with =AVERAGE(D4:D15). That gives 86.1 %, close but not the same, because it treats a week with 3 planned posts like a week with 4. The correct approach is to add up first and divide afterwards. This rule returns in almost every lab of the course, for cost per post, on-time rate and mix shares.
| Cell | What it shows | Formula | Result |
|---|---|---|---|
| D5 | Attainment of week 2 | =C5/B5 | 66.7 % |
| E9 | Running total after week 6 | =SUM($C$4:C9) | 17 posts |
| B17 | Total published | =SUM(C4:C15) | 33 posts |
| B18 | Overall attainment | =B17/SUM(B4:B15) | 86.8 % |
How to read the result
An overall attainment of 86.8 % means that for every ten promised posts, about nine arrived. Is that good? It depends on the promise. For a team that publishes three posts per week with part-time writers it is a decent start; for a newsroom with a daily schedule it would be a worry. The number only becomes useful when you compare it with your own history and with the reasons behind the gaps.
- Level: 86.8 % overall, with 8 of 12 weeks fully kept.
- Pattern: shortfalls of one post in weeks 2, 5, 8, and a bigger one in week 11.
- Trend: the cumulative gap grew from 1 post after week 2 to 5 posts at the end.
- Next question: was the plan too ambitious for the capacity, or did individual posts get stuck? Lessons 3 and 4 answer this.
A good habit is to write one sentence under every attainment report: what happened, why, and what you will change. A number without that sentence rarely leads to action.
Common mistakes with planned-versus-published numbers
These errors appear in real calendars again and again:
- Dividing the wrong way round. Published ÷ planned is attainment; planned ÷ published is not.
- Averaging percentages. Add up first and divide afterwards, so that bigger weeks count for more.
- Forgetting the dollar signs. A running total written as
=SUM(C4:C4)and copied down turns into a list of single weeks. - Changing the plan afterwards. If the plan is edited every time something slips, the attainment is always 100 % and tells you nothing. Keep a frozen version of the original plan.
- Counting drafts as published. A post counts when it is live, not when it is finished.
- Mixing different units. Count full posts; do not mix posts, newsletters and social snippets in one column unless you really treat them as the same.
The whole operation in one picture
Planned versus published is the first of many numbers. Every post passes through the same steps, and each step has a control number. The rest of the course follows this chain:
In short: the plan sets the cadence and the content mix; the brief hands work to writers whose capacity is limited; the draft takes a certain turnaround; review adds time and cost; the post goes live on time or late; and later it needs an update to stay useful.
What the rest of the course covers
After this free lesson, the course continues with 19 more labs, each with a different data set of the same fictional company:
- Lessons 2 to 5: publish dates and gaps, writer capacity, turnaround time and the full cost per post.
- Lessons 6 to 8: content mix by funnel stage, the on-time rate and update cycles for evergreen posts.
- Lessons 9 to 14: a volume plan from a target mix, in-house versus freelance cost, the pipeline and its stuck items, the content buffer, turnaround by writer and a Pareto chart of delay causes.
- Lessons 15 to 19: mix scenarios, deadlines in working days, refresh versus new posts, a turnaround forecast and a budget grid.
- Lesson 20: a final 12-month operations dashboard that combines the skills.
Along the way you will use SUM, AVERAGE, MEDIAN, IF and IFS, COUNTIF and COUNTIFS, SUMIFS, AVERAGEIFS, XLOOKUP, SUMPRODUCT, RANK.EQ, WORKDAY, SLOPE and FORECAST.LINEAR, always explained when they first appear. You also build charts and conditional formatting rules, the two tools that turn a table into something a team can discuss in five minutes.
Practical tips for your own calendar
You can apply today what you learned here, even before you do the later labs:
- Export or copy your calendar so that every planned post has a planned week and a status.
- Freeze the plan at the start of the month. Keep the plan columns and the published columns separate.
- Calculate attainment per week and as a running total. Add one sentence of explanation to every shortfall.
- Review the numbers in a short weekly meeting. Fifteen minutes with the table and the chart is enough.
- Only then change the plan: lower the cadence if it is unrealistic, or add capacity if the topics matter.
Summary
Planned versus published is the first control number of an editorial calendar. The weekly attainment rate is =C4/B4, the running total uses a locked start such as =SUM($C$4:C4), and the overall attainment divides the total published by the total planned. At Larchmoor Kitchen 33 of 38 planned posts were published, an attainment of 86.8 %; 4 of 12 weeks fell short and the cumulative gap grew to 5 posts.
Now scroll up to the lab and build the sheet yourself. It takes about fifteen minutes, the Coach checks each step, and you will end up with a first honest view of your own publishing promise.
Frequently asked questions
What is a blog editorial calendar?
An editorial calendar is a schedule of the posts a blog plans to publish, with dates, topics, owners and status. Used as an operational tool, it also records what was actually published, how long each post took, what it cost and when it should be updated.
How do I calculate the attainment rate of my publishing plan?
Divide the number of published posts by the number of planned posts for the same period, for example =C4/B4 in a spreadsheet. For several weeks, add up the published posts and the planned posts first and divide the two totals, instead of averaging the weekly percentages.
How many posts per week should a blog publish?
There is no universal number. The right cadence is one your team can keep with its real capacity and that readers can rely on. Measure your writers' net hours, the hours per post and the share of weeks in which the plan was kept before you raise the cadence.
How do I build a running total in Excel?
Use a SUM with a locked start and a moving end, for example =SUM($C$4:C4) in the first row, and copy it down. The dollar signs keep the start on C4, while the end reference moves one row at a time.
Is a 100 % attainment rate always the goal?
No. It shows that the plan was kept, not that the plan or the posts were good. A plan that is edited whenever something slips will always show 100 %. Keep the original plan frozen and read attainment together with turnaround, cost and quality checks.
Do I need special software to run an editorial calendar operation?
No. A spreadsheet with planned and published posts, dates, writers, costs and statuses is enough to calculate cadence, capacity, turnaround, cost per post, mix and on-time rate. Many teams also export the same columns from their content or project tools.
Keep going: Blog Editorial Calendar Operations: Publishing Cadence, Writer Capacity, Turnaround, Cost per Post & On-Time Delivery
This free lab is lesson 1 of 20. Unlock the other 19 hands-on labs, the final exam and your certificate for a one-time $9.90.
- Publish Dates: Days Between Posts, Weekdays, Average and Longest Gap and Posts per Month
- Writer Capacity: Net Writing Hours, Posts per Week per Writer and Team Utilisation against the Plan
- Turnaround Time: Writing Days, Total Days from Brief to Publication, Average, Median and Share within Target
- Cost per Post: Writer Fee, Editor Time and Design, Total Spend, Average Cost and Average Cost per Content Type
- Content Mix by Funnel Stage: Counting Posts per Stage, Actual Share against Target and the Gap in Points
- On-Time Rate: Status against the Due Date, Days Late, Overall and per-Writer Rate and Highlighting Late Posts
- Update Cycles: Content Age, a Refresh Interval per Type and the Posts Due for a Refresh
- Volume Plan: From a Target Mix to Posts, Hours and Budget per Month
- In-House or Freelance: Cost per Post by Month, the Cheaper Option and the Blended Cost per Post
- Pipeline Status: Items per Stage, Average Days in Status, Stuck Items and a Bottleneck Chart
- Content Buffer: Approved Posts in Stock, Weeks of Cover and a Thin-Buffer Signal
- Turnaround by Writer: Average, Slowest Post, Posts over Target and a Ranking
- Delay Causes: Days Lost per Reason, Share, Cumulative Share and a Pareto Chart
- Mix Scenarios: Weighted Cost and Hours per Post, Monthly Budget and the Change against the Current Mix
- Calendar Dates: Brief and Draft Deadlines in Working Days, Calendar Days of Lead Time and Slot Clashes
- Refresh or New? Allocating Limited Refresh Hours by Expected Gain per Hour with a Rank and a Cut-Off
- Turnaround Trend: Moving Average, Slope and a Straight-Line Forecast for the Next Three Months
- Budget Grid: Monthly Budget for Different Cadences and Costs per Post, with a Spending Cap
- Final Project: Editorial Operations Dashboard with Attainment, On-Time Rate, Cost per Post, Funnel Mix and a Trend Chart