A content calendar for small business should make the next publishing decision easier. If you open a spreadsheet and still have to work out who a post is for, what it will help them do, and what must happen before it goes live, the calendar is only a list of dates.
For someone running a business alongside the marketing, a useful calendar has to be small enough to maintain. It should also hold enough information that you can stop work on Tuesday and pick it up on Thursday without rebuilding the plan. Here’s a complete, deliberately lightweight version you can copy into a spreadsheet, adapt to your own business, and review after four weeks.
What a content calendar for small business must decide
Before assigning dates, decide three things: who each piece helps, what job it does, and how much work you can realistically finish. A post that sounds interesting but has no audience or useful next step stays in the idea bank. A topic you can’t verify adequately stays in research.
I would give content only four possible jobs: answer a concrete question, support a purchase decision, demonstrate a usable workflow, or express a distinctive editorial point of view. This keeps a small publication from filling every slot with variations on the same general advice. The same discipline applies whether the output is a blog article, video, or short email.
There’s no universal number of posts per week. One carefully reviewed resource can be worth more to readers than several thin summaries. When work is tight, reduce volume before reducing factual checking, examples, or editing. This is a planning principle, not a claim about rankings.
Copy this six-column calendar template
Start with one sheet and six columns. You can paste the header and blank example row into Google Sheets, Excel, or a Notion table. No automation, subscription, or elaborate board is necessary to begin.
Week | Reader question / topic | Content job | Format and destination | Status | Next concrete action Week 1 | [specific question] | Solve / Compare / Show / Perspective | [blog, newsletter, video] | Planned | [who does what, by when]
Here’s what each field is responsible for:
- Week: a rough commitment window, not a promise to publish on a particular day. Add a date only when you can confidently make it.
- Reader question / topic: the problem in the reader’s own language. “Marketing tips” is too broad; “What should a client send before a website project begins?” is actionable.
- Content job: choose just one primary job. A comparison can also answer a question, but deciding its main purpose guides the structure.
- Format and destination: where the finished piece belongs. One complete website article might also supply an email excerpt; those don’t need separate research projects.
- Status: use Planned → Drafting → Review → Published. “Blocked” is an exception, with its blocker written in Next concrete action.
- Next concrete action: write a verb, an object, and a definition of done: “Check three official pricing pages and record access dates,” not “Research.”
Keep the idea bank on a separate tab or document. A calendar is a commitment; a backlog is a place to save possibilities without committing to them. If planning decisions keep expanding, see AWL’s guide to prioritizing tasks when everything feels important.
A filled four-week example: a fictional bookkeeping studio
Imagine a one-person bookkeeping studio that serves independent service providers. It has time for one substantial article in each of the first two weeks, one short email in week three, and a maintenance session in week four. This is a constructed example to show how the fields work; the business, outcomes, and schedule are not a client case study.
| Week | Reader question / topic | Job | Format | Status | Next action |
|---|---|---|---|---|---|
| 1 | What records should I send my bookkeeper each month? | Solve | Website checklist | Planned | Draft a precise document checklist; flag advice that varies by jurisdiction |
| 2 | Spreadsheet or bookkeeping service: when does DIY stop making sense? | Compare | Website comparison | Planned | Write decision criteria; check claims against current official sources |
| 3 | Three recurring bookkeeping handoff mistakes | Show | Newsletter, linked to week 1 | Planned | Use generic examples, not fabricated client anecdotes |
| 4 | Fix broken links, revise weak examples, review search questions | Maintain | Existing website pages | Planned | Check published links and note specific corrections |
Notice what is missing: a daily posting mandate. This example spends part of the month improving what already exists, not continuously generating new URLs. It also puts the checklist before the comparison. A reader who arrives with an urgent practical question can get help without meeting a sales pitch first.
For a business with no newsletter, replace week three with a short FAQ section on the existing checklist page. The calendar is allowed to change when the channel is not useful.
Make every planned article earn its place
When several topics look equally promising, use a quick editorial filter. Give each criterion 0, 1, or 2 points. These are decision aids, not measured search scores.
| Criterion | 0 | 1 | 2 |
|---|---|---|---|
| Specific reader problem | Unclear | Recognizable | Can be stated as a concrete question |
| Useful answer available | Only generic advice | Some steps | Complete example, decision aid, or working template |
| Evidence you can check | Unsupported claims required | Some credible sources | Primary sources or genuine firsthand material available |
| Fit with current site | Isolated | Adjacent | Builds on an existing useful article |
| Can be finished responsibly | Not this month | Needs more work | Fits current capacity |
An idea scoring 8–10 deserves consideration; 5–7 stays in the backlog until a clear weakness is fixed. Anything that requires made-up experience or unsupported facts fails regardless of its total. A score is a reminder to use judgment, not permission to publish mediocre material.
Check that you’re not competing with your own pages. If you already have a clear answer to the question, update it rather than writing a near-duplicate. In a small site, a new section, better visual example, or clearer internal link often serves readers better than another post with a slightly different headline.
Build the calendar in one focused session
- Write the capacity boundary. Decide how many hours you can really spend on planning, verification, writing, image creation, and review. A calendar that assumes the review work is free is already overloaded.
- Collect questions, not keywords alone. Start with support conversations you genuinely have permission to use, public FAQs, your own notes, or documented search queries. Keep exact customer information private.
- Audit existing answers first. Search your site for the topic. Mark it “update” if a relevant published article exists; don’t split one answer across competing near-duplicates.
- Assign one content job. Choose solve, compare, show, or perspective. The job determines whether the reader needs a checklist, criteria, a worked walkthrough, or an argument.
- Schedule the evidence work. Write down the sources or artifacts you still need before drafting. “Verify current pricing” is a task; “add statistics” without a source is not.
- Put one next action in each row. Do not let vague statuses hide unfinished work. “Add two screenshots” is valid only if you can legally capture real screenshots; never manufacture product evidence.
- Reserve review capacity. If all hours are assigned to writing, you’re not budgeting for accessibility, broken links, metadata, and final editorial decisions.
The workflow resembles a production line only superficially. Its real purpose is to make editorial judgment visible. An AI tool may help turn notes into a first outline, but it should not decide what experience you had, invent a result, or publish before verification. For the safeguards, see AWL’s AI blog automation workflow.
How to budget for one article without pretending time is unlimited
Consider a hypothetical six-hour weekly content allowance. The exact allocation will vary with your topic and familiarity, but recording the whole job prevents writing from consuming all available time.
| Work | Example allocation | Definition of done |
|---|---|---|
| Question, intent, and existing-page check | 45 minutes | One precise question and no obvious duplicate |
| Evidence and outline | 75 minutes | Claims mapped to credible sources; unknowns identified |
| Draft and examples | 2 hours | Reader can follow the steps without guessing |
| Edit, links, accessibility, visual | 90 minutes | Accurate headings, useful internal links, checked image alt |
| Final review or carryover | 30 minutes | Published with approval or returned to a clearly named next step |
If a technical review takes longer than planned, release the time by publishing less often. Don’t replace source checking with a confident-sounding paragraph. The value of the article is what a reader can actually accomplish, not whether the calendar cell turns green.
A ten-minute weekly review and a monthly reset
At the end of each week, open the calendar and answer four questions: What became useful and public? What is blocked? Which item should be improved rather than expanded? Which next action can realistically be completed next week?
Keep the record short. For a stalled item, write the reason, not merely “delayed.” Examples: “Needs source for legal claim,” “Duplicate angle; merge with existing page,” or “Example needs a clearer step.” Those notes make the next session easier because you no longer have to reconstruct the problem.
Once a month, compare the calendar with actual reader signals. The Google Search Console Performance report can help you inspect the queries and pages receiving impressions and clicks. That is directional input for deciding what to clarify or expand, not proof that a calendar entry caused a result. New pages may not have enough data to interpret yet; leave the cell blank rather than inventing a number.
Look for a pattern you can act on. If an existing checklist appears for queries about a missing subtopic, consider a useful section on that page. If an article earns attention but readers still need an example, make that the next update. Don’t mechanically celebrate higher impressions without checking whether the query matches the article’s purpose.
The publish-or-update decision
Before opening a new draft, use this simple test:
- Update: the current page targets the same reader question but lacks a template, current source, complete example, or clear answer.
- New page: the reader’s goal is materially different and would make the existing page confusing or too broad.
- Combine: two published posts each answer half of the same question and neither stands well alone. Plan the merge carefully; don’t change live URLs or redirects as a casual editorial step.
- Skip: the topic offers nothing beyond established explanations and you cannot add a sound example or new analysis.
This decision protects the reader from an archive of nearly identical answers. It also gives maintenance an explicit place in the calendar, instead of treating revisions as work to do only after everything else is finished.
Copy-and-use weekly review checklist
Paste this into a note at the bottom of your calendar. The fields are intentionally plain, so a person using paper, a spreadsheet, or a task app can use the same process.
Week of: __________ This week's one most useful reader problem: __________ Publish or update? __________ Existing page checked for overlap? YES / NO Reader outcome (what they'll be able to do): __________ Source or first-hand evidence still needed: __________ Finished example/template included? YES / NO Internal links checked? YES / NO Image/alt and mobile layout checked? YES / NO Human review completed? YES / NO Final status: PLANNED / DRAFTING / REVIEW / PUBLISHED / BLOCKED One next action: __________
For each piece, ask a tougher quality question than “Did we finish the draft?” Ask, “Can a reader use this page to solve the stated problem without immediately searching for a more complete answer?” Google’s guidance on helpful, people-first content frames quality around originality, completeness, evidence, and a satisfying reader outcome, not target word count.
Common ways a content calendar fails
Every entry is a broad subject
“Productivity,” “marketing,” and “AI” don’t tell you what to write. Turn each into a question with a specific audience and a visible outcome. “How can a one-person business approve an AI-written blog draft safely?” is a much better starting point than “AI tips.”
Dates are treated as proof of progress
Schedule pressure may push a half-finished page live. Keep status separate from publish date and permit a planned week to move. A missed slot is a planning problem; an inaccurate published answer is a reader problem.
The calendar has no maintenance lane
Old pages with outdated tool features, broken links, or incomplete instructions quietly become less useful. Assign at least one review task in each monthly cycle, even when no new article is due. The example calendar reserves week four for this.
Metrics become a story you want to believe
An uptick in impressions does not establish a cause, and an affiliate click does not establish a satisfied reader. Record only what your analytics actually show. Treat ambiguous changes as questions for the next review, not success stories.
Questions worth settling before you scale
Do I need a different calendar for each channel?
Not at first. Keep one master row for the main asset. Add a distribution note only when it changes someone’s next action. Separate calendars are useful when independent teams or approval processes genuinely require them.
What if I can only publish twice a month?
Plan twice a month and include checking and updating in the same capacity budget. Consistency should mean a reliable editorial process, not constant output.
Should every blog idea start from SEO research?
No. Practical reader questions, genuine operating knowledge, and important corrections belong in a strong editorial plan too. Search data can help prioritize them when available, but it cannot substitute for useful evidence.
Should I buy a content calendar tool?
Only if a specific limitation of your current spreadsheet or task system is costing you meaningful time. For one operator, six fields and a ten-minute review are often enough to test the process before paying for software.
One useful week is a better start than a perfect year
The calendar’s job is not to make a small business look like it has a large marketing department. It is to preserve judgment between work sessions. Choose one real question, build the answer thoroughly, put its next action in the calendar, and leave space to revise it later. If that works, copy the process for the following week. If it doesn’t, simplify the system rather than filling more cells.
