We needed a content calendar that wasn't just a static table. The goal was to integrate brainstorming directly into the planning phase and track it. Here's how we built it using Notion AI and database relations.
**Core Database Structure:**
You need two linked databases: `Content Calendar` and `AI Headline Ideas`.
**1. AI Headline Ideas Database**
This is your raw material table. Create it with these properties:
* `Title` (Page property): The seed topic (e.g., "Q3 Cloud Cost Report").
* `Status` (Select): "New", "Approved", "Used".
* `Tone` (Select): "Technical", "Casual", "Provocative".
* `Generated Headline` (Text): This is where you'll use the AI.
You populate a new page with a topic. Then, in the `Generated Headline` property, you use the Notion AI context menu (`Ctrl/Cmd + J`) with a prompt like:
```
Based on the page title "{Page Title}" and for a {Tone} audience, generate 5 compelling blog post headlines. Return them as a bulleted list.
```
Example output in the property:
* A Technical Deep Dive into Our Q3 Cloud Spend
* How We Slashed Cloud Costs by 22% in Q3: The Numbers
* Beyond the Bill: Analyzing Our AWS & GCP Infrastructure Efficiency
* Kubernetes Cost Allocation: Lessons from Q3
* The Real Price of Scale: Interpreting Our Cloud Financial Data
**2. Content Calendar Database**
This is your execution table. Key properties:
* `Publish Date` (Date)
* `Topic` (Relation -> `AI Headline Ideas` database)
* `Final Headline` (Text)
* `Status` (Select): "Idea", "Assigned", "In Progress", "Published".
* `Assignee` (Person)
**The Workflow:**
1. Team adds seed ideas to the `AI Headline Ideas` DB and runs the AI prompt.
2. In a planning meeting, you view the `AI Headline Ideas` DB filtered by `Status: New`.
3. Drag and drop a page from the `AI Headline Ideas` DB into a new row in the `Content Calendar` DB. This auto-creates the relation.
4. Select the best AI-generated headline from the source page, paste it into `Final Headline`, and tweak if needed. Update the source idea's status to "Used".
5. Fill in the date, assignee, and move on.
**Why This Works:**
* It separates brainstorming (which can be messy) from the fixed calendar.
* The AI output is captured as data, not just ephemeral text, so you can audit what was generated versus used.
* The relation ensures you never lose the source context for the final piece.
The bottleneck shifts from "what do we write about" to "which of these good options do we schedule." It quantifies the ideation phase.
shift left or go home