Audit intermediate Works with: Any AI

Content Calendar Audit: Gaps, Repetition and Balance

Table output Has example

Check whether your plan covers your goals without burning you out.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Audit my content calendar. The planned items for the next eight weeks with date, topic, format, and platform: [CALENDAR]. My content pillars: [PILLARS]. Weekly time available: [WEEKLY_HOURS].

Count items per pillar and per format with percentages and the arithmetic. Identify topics repeated too often, gaps, weeks that are overloaded (estimate hours per item and total against my time), and dependencies (an item that needs another to be finished first). Make a table with Week, Items, Estimated hours, Load versus capacity, and Risk. Propose a rebalanced calendar, a batching plan, a buffer, and a rule for dropping items. Include a review of what to repurpose.

Hours are my estimates; ask me where they are uncertain.

Add a worked load check: eight weeks with 3 pieces a week at an estimated 3.5 hours each is 10.5 hours a week, against 8 available, so two weeks are over capacity by 2.5 hours; show a rule for which item to drop (the one with the lowest link to a pillar or goal) and how a single repurposed piece can replace a new one. Count pillars: education 11 of 24 items (46 percent), stories 6 (25), offers 3 (12.5), behind the scenes 4 (16.5), and say what imbalance this may signal.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Pillar | Items | Share
Education | 11 | 46 percent
Stories | 6 | 25 percent
Offers | 3 | 12.5 percent
Behind the scenes | 4 | 16.5 percent
Total 24. Weeks 3 and 6 need about 2.5 hours more than I have (10.5 vs 8). Drop the item with the weakest link to a pillar, repurpose one piece, and keep a buffer.
Gaps: no offer content in weeks 2 and 5, and two near-identical tutorials in weeks 3 and 6. Swap one tutorial for a customer story, keep one empty slot as a buffer, and batch-record the weeks with the highest workload.

• worksheet