Content calendar
A calendar is a set of decisions, not a grid of dates
Most calendars are a grid someone fills in on a Friday. This one is generated from the plan above it, and every slot can tell you which decision put it there.
Availability: Available
What it does
- Lays out a month of work with the reasoning attached to each slot
- Layers observances — holidays, awareness days, industry events — rather than pasting a single global list
- Runs a brand-safety filter before anything is surfaced, so unsuitable slots never reach the grid
- Offers month, week and day views for the different people who need each
- Regenerates on request: ask for a change and the calendar updates rather than being rebuilt
- Carries continuation context, so the next calendar builds on the last one instead of starting fresh
In practice
The observance system is layered on purpose. A global holiday list produces the same four posts every company publishes; a layered one lets an industry event outrank a generic awareness day for a brand that cares about it.
The brand-safety filter runs before generation output is shown, not after. That ordering is the difference between a calendar you review and a calendar you have to clean.
Calendar generation moved onto asynchronous jobs in April 2026. The request returns a handle in under a second, progress streams over a websocket, and a polling fallback keeps the interface honest if that connection drops.
Where it sits in the loop
- Reads from
- Brand and positioning, Planning, Signals and trends
- Feeds
- Production, Publishing, Review and export
What this does not do
- It plans slots and reasoning. It does not publish anything — that is a separate, explicit step.
- The observance layers are only as local as the sources behind them. A regional moment nobody has recorded will not appear because the calendar guessed at it.
- Continuation context makes the next calendar aware of the last one. It does not make it aware of work that happened outside Obelo.
What we claim, and what backs it
Each statement below is a governed record with an owner, a review date and its supporting evidence. Nothing on this page asserts a customer outcome, because no customer evidence has been approved for publication.
Obelo produces a content calendar in which each slot carries the reasoning it came from, blending strategy-led generation with a layered observance system and a brand-safety filter that runs before anything is surfaced.
Evidence
- The public launch-state registry publishes the content calendar as generally available.
- A dated, shipped release adding the layered observance system and the pre-surface brand-safety filter to calendar generation.
- A dated, shipped release moving calendar generation, SEO audits, bulk SEO suggestions and document upload onto asynchronous jobs with progress reporting.