A filled plan and a blank starting point
The sample describes a fictional issue-tracking product. It has ten posts across two weeks beginning 2 November 2026. Dates and owners are examples; use the calendar builder to change them before exporting.
The blank CSV has fields for the publishing date, channel, topic, format, owner and review state. It opens in spreadsheet software. It is a planning document and does not schedule or publish anything.
The campaign story
Scroll the table horizontally if all columns are not visible.
| Part | Reader question | Assets |
|---|---|---|
| Introduce | What makes a report actionable? | A synthetic report and a short checklist |
| Demonstrate | What happens after submission? | A screen recording and assigned issue |
| Clarify | What are the requirements and limits? | Guest-access FAQ and missing-context example |
| Reinforce | Can I repeat this myself? | A copyable checklist and recap |
Replace these fields first
- Use the campaign's real start date and leave enough production time.
- Replace every fictional feature with something your product actually supports.
- Assign owners who can finish the next action.
- Choose review states your team understands.
- Keep the campaign's learning question in your own planning notes so the sequence has a purpose.
Before a row becomes a post
Open the required asset, check its claims and review the exported result on a small screen. A spreadsheet row marked Ready is an organizational label, not proof that the creative has been checked. If an asset is unavailable, use a different useful example or leave the slot open.


