Your three-post week: problem, proof, next step
Editable plain text for Docs, Notion or your own planner. Includes the brief, three slots, approval fields and weekly review. No account or email required.

Week / time zone: ____________________
Audience / one problem: ____________________
Goal / observable signal: ____________________
Channel: ____________________
Voice: two approved examples / preferred wording / avoid: ____________________


MON · Make the problem recognizable
Day / topic / hook: ____________________
Verified fact / source link / limitations: ____________________
Visual / demo data / alt text: ____________________
One CTA / destination link: ____________________
Writer / reviewer / approval date: ____________________
Status: draft → review → approved → scheduled → published (or failed): ____________________
Actual publication URL: ____________________
Observed result / what remains unknown / next decision: ____________________

Hook: ‘The meeting moved. Did everyone get the update?’ Describe one real scheduling problem in the audience’s words. Visual: a recreated example with invented names. Evidence needed: the exact workflow your product supports. CTA: read the checklist for changing a meeting.

WED · Show one useful action
Day / topic / hook: ____________________
Verified fact / source link / limitations: ____________________
Visual / demo data / alt text: ____________________
One CTA / destination link: ____________________
Writer / reviewer / approval date: ____________________
Status: draft → review → approved → scheduled → published (or failed): ____________________
Actual publication URL: ____________________
Observed result / what remains unknown / next decision: ____________________

Hook: ‘One changed date, shown step by step.’ Record the actual date-change workflow using demo data. Explain who can see the change and any notification limits. Avoid a polished mockup that implies a feature exists. CTA: try the same task in the demo, if a public demo is available.

FRI · Answer one buying question
Day / topic / hook: ____________________
Verified fact / source link / limitations: ____________________
Visual / demo data / alt text: ____________________
One CTA / destination link: ____________________
Writer / reviewer / approval date: ____________________
Status: draft → review → approved → scheduled → published (or failed): ____________________
Actual publication URL: ____________________
Observed result / what remains unknown / next decision: ____________________

Hook: ‘What happens if someone misses the update?’ Answer with verified product behavior and a clear limitation. Use one question from real support or label it as a question to test. CTA: view the relevant help page or product tour. Do not invent customer quotes.

Keep the voice consistent without repeating the same post
Before writing, keep two approved examples beside the calendar. Note how you address the reader, sentence length, preferred terms and phrases to avoid. For this example: calm, practical, no hype; one specific action per post; no claims such as ‘never miss a meeting’. Change the evidence and format across the week while keeping these rules stable.

A weekly review that ends in a decision
Before the week starts, check every source, demo screen and destination link. Assign one reviewer and leave uncertain posts as drafts. After publishing, save the actual post link; ‘accepted’ or ‘scheduled’ is not proof that it is live. At the end of the week, record useful replies, demo visits and completed demo tasks if you can measure them. Leave missing data unknown. Keep, revise or drop one topic based on that evidence.

Fabulica editorial resource · AI-assisted · examples are illustrative · reviewed 2026-10-04
https://fabulica.com/en/solutions/social-media-content-calendar/