For U.S. advertising context, the FTC’s advertising and marketing guidance explains truth-in-advertising obligations. Review each reused offer and claim again for its intended publication date.
Define the evidence-led planning output
This retained run converts eighteen fictional service-business assets into twelve weekly content jobs. It does not chase a post quota. Each week selects one source, performs one bounded transformation, gives the reader a useful next action, and ends at marketing review. The negative V1 shows why source grounding matters: it produces a generic “best company” article, citywide superiority, guaranteed savings, and a November reuse of an August availability notice.
Planning terms that resist content inflation
| Term | Meaning in this tutorial |
|---|---|
| Asset inventory | A source list with owner, format, job, approved claims, review date, and constraint. |
| Audience job | The concrete question or decision a piece helps a person complete. |
| Bounded transformation | A new format or angle that does not broaden the source claim. |
| Scaled-content risk | Producing many low-value or near-duplicate pages primarily to capture search variations. |
Signals that a calendar is drifting toward spam
| Planning failure | Blocked calendar row | Trust cost |
|---|---|---|
| Unowned topic | A generic ‘best HVAC company’ article | No approved source or original evidence. |
| Claim inflation | One-location intake result becomes citywide fastest status | Case evidence cannot prove market leadership. |
| Promise creation | Plan facts become guaranteed savings | The source contains no outcome guarantee. |
| Stale reuse | August openings scheduled for November | A dated offer becomes misleading after its window. |
Step 1: inventory existing assets before proposing posts
Source preparation. List materials the team already controls: articles, FAQs, diagrams, cases, videos, fact sheets, service notices, and checklists. Add a stable asset ID, last-reviewed date, allowed claim boundary, and known constraint.
Normalize the supplied library into asset_id, title, format, audience job, approved claim boundary, last_reviewed, and constraint. Do not propose content yet. Mark stale or unverifiable material.Evidence retained. The inventory retained eighteen assets across education, proof, service, trust, and offer jobs. Time-sensitive openings, model-specific instructions, sample size, certification expiry, and service-credit disclosure stayed attached.

Stop condition. Remove any item whose ownership, accuracy, review date, or permission is unclear. An attractive asset is not reusable merely because it exists.
Step 2: choose twelve different audience jobs
Structuring decision. Map user needs, not keyword variations. For this fixture the jobs include understanding estimates, collecting new-home records, recognizing warning signs, seeing dispatch process, comparing a plan, keeping maintenance evidence, and understanding an emergency boundary.
Select twelve non-overlapping audience jobs from the approved inventory. Name the question each week resolves and reject pairs that differ only by wording or search phrase.Structured result. The calendar uses twelve distinct practical questions. It does not create separate pages for every fan-out query or repeat the same maintenance checklist with synonyms.

Integrity check. Read only the proposed job labels. If two would lead to the same user action and evidence, merge them rather than manufacturing another slot.
Step 3: lock claims, disclosures, and freshness
Release contract. Before drafting, identify claims that need a qualifier, relationship disclosure, sample note, current availability check, manual reference, or safety boundary. Decide where that information must appear in the shortened derivative.
For each selected asset, return supported facts, prohibited expansions, freshness check, disclosure text, and release owner. Keep disclosures beside the affected claim, not in a distant footer.Contract outcome. The one-location case retained its service-credit relationship; the support insight retained a 42-ticket sample; model-specific instructions retained the manual check; August availability was excluded entirely.

Boundary check. Treat small-format content as higher risk, not lower risk. A short caption has fewer places to preserve a qualifier, so it needs a deliberate disclosure field.
Step 4: retain the spam-shaped first plan
First-pass test. Keep the first candidate calendar and label why each unsafe row fails. The point is to test whether the workflow blocks mass-produced or exaggerated material before scheduling.
Create four high-performing content ideas, including a general industry article, a customer proof post, an offer, and a seasonal promotion.Observed failure. All four negative rows were blocked: one had no source, one invented a market superlative, one guaranteed savings, and one reused a stale offer outside its validity window.

Failure check. Search the draft for best, cheapest, fastest, guaranteed, everyone, always, and currently available. Each needs direct substantiation and a current scope.
Step 5: audit usefulness instead of counting output
Evidence audit. Score each row on evidence fidelity, distinct user job, added value, disclosure retention, freshness, and realistic CTA. Do not reward higher frequency or extra derivative formats.
For each proposed week, answer: what source supports it, what new utility it adds, which audience decision it helps, what claim could be overstated, what disclosure must remain, and who reviews it? Block rows without a satisfactory answer.Audit finding. The method rejected volume for its own sake. A row passed only when it turned approved material into a more usable form without widening the promise.

Source check. Ask whether a direct visitor would save, use, or act on the piece even if search traffic did not exist. If not, the slot probably serves the calendar rather than the audience.
Step 6: build the twelve-week workbook
Corrected deliverable. Assign one publish date, one source asset, one audience job, one transformation, one CTA, one disclosure field, and one review state per week. Keep the full inventory and rejected V1 on separate sheets.
Create twelve weekly rows from the approved selections. Use exactly one source_asset_id per row. Retain required disclosures. End every row at READY_FOR_MARKETING_REVIEW; do not schedule or publish.Corrected result. Each of the twelve formulas compared week, date, asset, job, transformation, CTA, disclosure, and release state with the retained plan. The calendar spans September through November and avoids the stale August availability asset.
Artifact check. Review the sequence for audience fatigue and operational capacity. Source-safe does not automatically mean the team can produce or support the plan.
Step 7: review claim and disclosure placement
Export review. Inspect each proposed derivative at the actual target length. Confirm that the qualifier remains close enough to the claim to be noticed and understood.
For the case and sample-based weeks, draft the shortest accurate claim plus adjacent disclosure. Do not replace a concrete disclosure with ‘results may vary.’Export evidence. The case row states the one-location 18-to-11-minute intake result and requires the service-credit disclosure beside it. The support row retains the 42-ticket sample rather than implying universal frequency.

Portability check. Have the responsible marketer verify the disclosure in the final visual or caption, not only in this planning spreadsheet.
Step 8: run the anti-spam release gate
Release decision. Execute the deterministic checker. It must confirm twelve ordered weeks, existing asset IDs, exclusion of the stale offer, required case and sample disclosures, and marketing-review states.
python3 content-calendar-evidence-gate.pyGate result. The calendar checker accepted all twelve retained rows while rejecting best-company, guaranteed-savings, citywide-fastest, and invented-asset mutations. Scheduling and publication remained false.

Owner check. Before publishing any real item, recheck source currency, claims, rights, and platform presentation. The gate verifies the planning fixture, not downstream creative execution.
What the twelve-week exercise leaves unknown
This calendar uses fictional assets and cannot establish actual demand, performance, legal compliance, brand fit, or channel results. It does not authorize testimonial use, safety claims, targeting, scheduling, advertising spend, or publication. The marketing owner must review current facts and the final rendered content.
When a calendar row is ready for marketing review
- Each week serves a different audience job and transforms one retained asset rather than repeating the same claim.
- Every planned use carries its source ID, freshness note, claim boundary, required disclosure, call to action, and reviewer state.
- Traffic, market leadership, engagement lift, and product benefits remain absent unless separately evidenced.
- The derivative must be useful to a direct visitor and reviewable without relying on publication volume.
