🧠 AI Learning Hub

Hub › Lessons › Content planning, lesson 7

Lesson 7 · AI for your content planningAbout 10 minutes a week

A 10-minute weekly content review with one AI prompt

Most content plans fail quietly. A post slips a week, a customer asks the same question twice, and nobody looks at the numbers until the month is over. This lesson gives you one short check to do every week. You copy three things into one prompt: your plan, last week's numbers and the questions customers asked. You get back what needs attention, what your numbers can and cannot tell you, and a plan for next week that fits the time you really have. It brings lessons 1 to 6 of this series together, but you can use it on its own.

What you will be able to do: in about 10 minutes a week, see which posts are late or undated, read last week's numbers without guessing at causes, decide where new customer questions belong, and leave with a plan for next week that is no bigger than you can make.

Step 1: Pick a fixed slot

Step 2: Copy in three things (5 minutes)

Before you paste: remove customers' names, phone numbers and email addresses. The AI needs the question, not who asked it.

Step 3: The weekly review prompt

Fill in each line, add one line per post under the dashes, then paste it into your AI tool.

Prompt: weekly content review
Help me do my weekly content review. Use only what I write below.

Today's date:
How many posts I can make next week:
Posts on my plan (title, platform, stage, due date or "no date"):
-
Posts published this week (title, platform, date published, and the numbers I copied from the platform's insights):
-
Customer questions I got this week (in their words, and how many people asked):
-
The change I tried this week, and whether I did it:

Return these parts:
1. Needs attention: posts on my plan that are late, due in the next 7 days but not Ready, or have no date. For each, one next action: finish it, move it to a new date, or drop it.
2. This week's numbers: a short table of the published posts with my numbers, unchanged. Then up to 2 observations. Only compare posts on the same platform. Say plainly when there are too few posts to tell why one did better.
3. This week's change: did I do it, and what my numbers can and cannot say about it.
4. Customer questions: for each question, say whether a post on my plan already answers it. If none does, suggest a new post idea with a working title. Mark any fact I would need to answer it as [ASK].
5. Next week's plan: no more posts than I said I can make. For each: title, platform, due day, and the next step (write a brief, repurpose a published post, edit with my voice guide, or check the title against search results). Put late and nearly ready posts first.
6. One change to try next week, small enough to do in under 15 minutes, and how I will know I did it.
7. Not checked: one line on what this review cannot tell me.

Rules:
- Keep the review short: under 400 words, not counting the table in part 2.
- Use only my notes and numbers. Do not add posts, numbers, percentages, benchmarks or facts I did not give.
- Do not say that a change caused a result. One week of numbers only shows what happened.
- Do not predict followers, reach, traffic or sales.
- If I listed no published posts, write "Nothing published this week" in part 2 and do not judge the change in part 3.
- If I listed no planned posts and no published posts, say there is nothing to review yet and stop after part 1.

Step 4: Decide, then update your calendar (3 minutes)

Worked example

We used the same made-up web designer as in lesson 5 and lesson 6, who builds simple websites for small cafes and home food businesses in Singapore. The business, posts, numbers and questions are illustrative. Two of the planned posts use titles from lesson 6.

Input (illustrative)

Sample input
Today's date: Friday 30 October 2026
How many posts I can make next week: 2
Posts on my plan (title, platform, stage, due date or "no date"):
- Before and after: a home bakery's new menu page | LinkedIn | Drafting | Tue 27 Oct
- Should a cafe website menu show prices? Yes, and here's why | Blog | Drafting | Mon 2 Nov
- Instagram or a website for your home bakery: when DM orders are enough | Blog | Ready | Wed 4 Nov
- 3 photos every cafe menu page needs | Instagram | Idea | no date
Posts published this week (title, platform, date published, and the numbers I copied from the platform's insights):
- Put your opening hours at the top of your page | Instagram carousel | Mon 26 Oct | 412 views, 9 likes, 2 comments, 11 saves, 1 DM asking about price
- Put your opening hours at the top of your page (same post as text) | LinkedIn | Tue 27 Oct | 180 impressions, 4 reactions, 0 comments
- How long does a simple cafe website take? | Blog | Thu 29 Oct | 23 visits so far, 0 enquiries
Customer questions I got this week (in their words, and how many people asked):
- "Can I change the menu myself or do I have to pay you each time?" (2 people)
- "Do you do online ordering?" (1 person)
- "How much is a one-page website?" (1 person)
The change I tried this week, and whether I did it: post the Instagram carousel on Monday morning instead of Thursday night. Yes, I did it.

Output (as returned)

Shown word for word from our test with Claude, without its title line; only the formatting was converted for this page.

1. Needs attention

2. This week's numbers

This week's numbers, as given. On a phone, scroll the table sideways.

PostPlatformPublishedYour numbers
Put your opening hours at the top of your pageInstagram carouselMon 26 Oct412 views, 9 likes, 2 comments, 11 saves, 1 DM asking about price
Put your opening hours at the top of your page (text)LinkedInTue 27 Oct180 impressions, 4 reactions, 0 comments
How long does a simple cafe website take?BlogThu 29 Oct23 visits so far, 0 enquiries

3. This week's change

You did it: the carousel went out Monday morning. Your numbers show what the carousel got. They can't show whether Monday morning beat Thursday night, because you gave me no Thursday-night post to compare. One week and one post can't show the timing made a difference.

4. Customer questions

5. Next week's plan (2 posts)

  1. Before and after: a home bakery's new menu page, LinkedIn, due Mon 2 Nov. Next step: edit with my voice guide.
  2. Instagram or a website for your home bakery: when DM orders are enough, Blog, due Wed 4 Nov. Next step: check the title against search results.

The prices post doesn't fit in two slots, so it moves to a later date.

6. One change to try next week

Add one closing line to the "How long does a simple cafe website take?" post that invites readers to message you for a one-page website price (about 10 minutes). You'll know you did it when the line is live on the post.

7. Not checked

This review can't tell you why any post did what it did, or how these numbers compare with earlier weeks.

What we checked

What we would do with this: the questions about menu changes and price are worth answering, because they came from real conversations and one matches the DM. But the web designer has to fill in each [ASK] first. Part 4 is a list of questions for the owner, not finished posts.

A quiet week

We also tested a week with nothing published, one undated idea and one question. Every run wrote "Nothing published this week", did not judge the change, and planned one post because the input said one. With an empty plan and nothing published, every run said there was nothing to review yet and stopped after part 1, as the prompt asks.

What we changed after testing

The prompt above is the third version. We ran each version on the same three inputs:

Where the other lessons fit

When the review points to a job, this is the lesson for it.

When the review saysUse
New customer questions keep comingLesson 1: customer questions to content ideas
Next step: write a briefLesson 2: a one-page content brief
Next step: repurpose a published postLesson 3: one post into four short posts
Posts are late or have no dateLesson 4: a Notion calendar with a "This week" view
Next step: edit with my voice guideLesson 5: a voice guide from your own posts
Next step: check the title against search resultsLesson 6: search intent check

Watch out for

Next step

How we checked this lesson