Loading tutorials…
Loading tutorials…
Most content calendars die in week six because they were built as a list, not as a workflow. This walks the Airtable setup that gives writers, editors, and the CEO each a view of the same data — and stays alive past the first quarter.
Who this is forContent leads, marketing managers, and founders who already publish content and are tired of tracking it in a spreadsheet that nobody updates. If you have ever asked 'what is shipping this week?' and gotten three different answers, this tutorial is for you.
What you'll need
Step 1
A content calendar is one table with the fields that drive editorial decisions: Title, Type, Status, Owner, Publish Date, Channel, Brief, Score.
In your marketing base → bottom of base → "+ Add or import" → "Create empty table" → name it "Content."
Primary field: rename "Name" to "Content Title" (Single line text). This is what shows in every linked picker.
Add: Content Type (Single select: Blog / Video / Podcast / Social / Email / Landing Page / Webinar — color-coded), Status (Single select: Backlog → Briefed → Drafting → In Review → Approved → Scheduled → Published — locked colors greys/yellow/green), Owner (User field), Reviewer (User field), Publish Date (Date, with time enabled for scheduled social), Channel (Multiple select: Website / YouTube / LinkedIn / Twitter / Newsletter / Substack / Apple Podcasts).
Add: Brief (Link to another record → Briefs table, if you have one — otherwise Long text), Asset Links (Long text or Attachment), Score (Number 1-10 for content priority), Days to Publish (Formula: DATETIME_DIFF({Publish Date}, TODAY(), "days")).
Optional but powerful: Theme (Linked record → Themes table for the quarter), Funnel Stage (Single select: Awareness / Consideration / Decision / Retention), Campaign (Linked record → Campaigns table).
Step 2
Grid view is the default workspace for writers and editors. Filter, sort, and hide fields so the daily-driver view shows exactly what matters.
Open the Content table. The default view is "Grid view" — rename it "Editorial — All Content."
Sort by Publish Date ascending (Sort icon → Publish Date → ascending).
Group by Status (Group icon → Status). This creates collapsible sections — Backlog, Briefed, Drafting, In Review, Approved, Scheduled, Published.
Hide rarely-used fields from this view: Score, Funnel Stage, Theme. Keep the workhorse fields visible: Title, Type, Status, Owner, Publish Date, Channel, Days to Publish.
Right-click Days to Publish → Conditional formatting (or Color row by field) → red if negative, yellow if 0-7, green if 7+. This makes overdue content visually obvious without filtering.
Add a "My Content" view: duplicate the Editorial view, filter Owner = current user. Each writer's daily-driver view.
Step 3
Calendar view shows content laid out by Publish Date. Critical for spotting empty weeks and over-loaded days.
Click "+ Create new view" → "Calendar" → name it "Editorial Calendar."
Choose the date field: Publish Date. (Calendar view requires at least one Date field on the table.)
Toggle "Color records by field" → Status — published green, in-review yellow, drafting orange, backlog grey.
Switch between Week and Month views with the toolbar buttons. Month is the strategic view; Week is the operational view.
Click an empty date to create a new record inline → the date field is pre-filled. Useful when planning the next quarter from a blank calendar.
Filter: hide "Backlog" status from the calendar (filter Status is not Backlog). The calendar should show committed content, not ideas.
Step 4
Kanban groups records by Status — drag-and-drop between columns to move content through the workflow. This is the view editors live in.
"+ Create new view" → "Kanban" → name it "Editorial Workflow."
Stack by: Status (the field that defines the columns).
Card preview fields: Owner, Publish Date, Type. Keep cards visually scannable — 3-4 fields max.
Filter: Status is not Published AND Status is not Archived. The Kanban is for in-flight work; published items belong on the Calendar or Grid.
Sort within columns by Publish Date ascending — most urgent at the top of each column.
Train the team to drag cards between columns when status changes. Combined with an automation (next tutorial) that notifies the next owner on status change, this becomes a real workflow.
Step 5
On Team+ tier, Gantt view shows content as bars on a timeline — useful for seeing how pieces overlap and where the team is overloaded.
"+ Create new view" → "Gantt" (Team+) or "Timeline" (similar, more flexible) → name it "Q2 Content Timeline."
Configure: Start date = a Draft Start Date field (add this to the Content table if you do not have one), End date = Publish Date.
Color by: Channel or Theme — visualizes channel mix across the quarter.
Group by: Owner — surfaces who is overloaded. If one writer has 8 overlapping bars in May, that is a capacity problem the Grid view hides.
Show dependencies (Team+): if Piece A must publish before Piece B, link them via a Linked record field "Depends On" and Gantt visualizes the chain.
Use the Timeline view to drive quarterly capacity planning meetings — looking at a Grid does not show overload; a Timeline does.
Step 6
Execs want a one-glance answer to "what shipped this month?" Build a locked, filtered view they can bookmark.
"+ Create new view" → "Grid" → name it "Exec — Shipped This Month."
Filter: Status is Published AND Publish Date is within the current month.
Sort: Publish Date descending — newest first.
Hide: Owner, Brief, Asset Links — fields that are operational, not strategic.
Show: Title, Type, Channel, Publish Date, Funnel Stage. Optional: a Lookup field pulling key metrics (views, conversions) once they exist.
On Business+ tier, lock the view → Share button (top right) → "Create a shareable view link" → restrict to specific users or password-protect.
Send the link to execs as the canonical "what shipped" answer. They never need to ask again.
Step 7
The calendar is data; the automation is the workflow. One trigger-action automation closes the handoff gap.
Automations panel (top right) → "+ Create automation" → name "Notify on status change."
Trigger: "When record updated" → Table: Content → field watched: Status.
Add a condition: Status = "In Review."
Action: "Send Slack message" (or "Send email," or "Send Microsoft Teams message") → recipient: dynamic from the Reviewer field → message: "{Content Title} is ready for your review. View: {RECORD_URL()}."
Test it: change a record to In Review → confirm the message lands.
Turn it on. Repeat the pattern for each handoff (Drafting → In Review, In Review → Approved, Approved → Scheduled).
Common mistakes
Building the calendar as one long list, no views
What goes wrong: Writers, editors, and execs all stare at the same 200-row Grid. Writers cannot find their work. Execs cannot answer 'what shipped?' Within 8 weeks, half the team is back on a spreadsheet. ~$3-6K in lost editorial time per quarter.
How to avoid: Build 4-5 named views: Editorial Grid, My Content, Editorial Calendar, Kanban Workflow, Exec Shipped. Each audience has their entry point.
Free-text Status field (or no Status field)
What goes wrong: Writers type 'WIP,' 'In progress,' 'drafting,' 'almost done' as different statuses. No automation can trigger reliably. Filtering surfaces inconsistent results. The Kanban view becomes useless. Editorial throughput drops 20-30%.
How to avoid: Single select Status field with locked options. Define each status in the conventions doc. Restrict edits to Owner.
No Publish Date field, or treating it as optional
What goes wrong: Half the content rows have no Publish Date. Calendar view is empty. Gantt view is broken. Forecasting next month's publishing volume is guesswork — and missed publishing slots cost ~$2-5K in unfulfilled audience expectation per quarter.
How to avoid: Publish Date is mandatory before Status moves past Briefed. Use a Required field automation (Trigger: Status changed AND Publish Date empty → revert and notify).
No automation on status changes
What goes wrong: Status moves to 'In Review' but the reviewer never gets notified. Drafts sit for 4-7 days waiting for someone to notice. Publishing slips. ~3 hrs/week of manual chasing per editor — $600-1,200/mo of editor time wasted.
How to avoid: One automation per major status change. Slack/Teams/email to the next owner with a record link. 10 minutes to set up, saves 10 hrs/month.
Letting everyone customize views in place
What goes wrong: Writer A re-sorts the Editorial Calendar view. Now everyone sees it sorted by Title alphabetically. Confusion follows. Bug reports start: 'why does my calendar look wrong?' Editor spends 30 min/week resetting views.
How to avoid: Use Personal views (each user has their own) for ad-hoc customization. Lock shared views on Business+ tier (Owner can edit, others view only). Pin the 4-5 canonical views at the top of the view list.
No Theme / Campaign / Funnel Stage tagging
What goes wrong: Content lives in the calendar but you cannot answer 'how many pieces did we ship for Awareness this quarter?' or 'how much content backed the Q2 campaign?' Strategy decisions get made on intuition. Misallocated content effort costs $5-10K/quarter.
How to avoid: Add Funnel Stage (Single select), Theme (Linked record), and Campaign (Linked record). Tag every piece on briefing, not on publish. Rollup on Campaign shows piece count automatically.
Recap
Done — what's next
How to set up an Airtable base for marketing without rebuilding it in month two
Read the next tutorial
Hand it off
A content calendar that holds up past quarter one needs Status discipline, view governance, and at least one well-wired automation — none of which are obvious on day one. A vetted Airtable specialist will build the Content table, set up 4-6 views, wire 3-5 automations, and document the workflow for your team in one engagement — typically $200-500 one-shot. Ongoing content-ops support runs $400-1,200/mo at $14-16/hr.
See specialist rates
Free tier supports Grid, Kanban, and Calendar views — enough for a 1-person operation up to ~1,000 records. Team ($20/user/mo) adds Gantt, Timeline, Calendar with multiple date overlays, automations (50K runs/mo), and Sync. Business ($45/user/mo) adds view locking, page designer, custom branded forms, and 100K records per base. For a 3+ person editorial team, Team is the right starting tier.
One Content table with a Type field. Splitting Blog / Video / Podcast into separate tables means you need a separate calendar view per type, separate automations per type, and cross-type reporting becomes impossible. The Type field gives you the same separation with a fraction of the maintenance.
Add a Campaign field on Content (Link to another record → Campaigns table). On the Campaigns table, add a Rollup field showing Count of linked Content (or COUNTIF Status = Published for 'pieces shipped'). Now every Campaign row shows how many content pieces backed it — instantly visible without manual reporting.
Yes for Slack (native Airtable Automation action). For LinkedIn or a CMS like WordPress, you can use a webhook automation + Zapier/Make as the bridge, or use the Make integration directly. Native Airtable does not publish to LinkedIn or WordPress — you need a middleware tool (covered in tutorial 9).
Two paths: (1) Create a personal view for each writer filtered to Owner = themselves — easy, but writers can still see others' content if they switch views. (2) On Business+ tier, use record-level permissions (Owner = User field controls edit access). For most teams under 10 people, path 1 is enough.
Airtable
Airtable is fast to spin up and easy to wire wrong. Most marketing bases hit a wall at 3,000 records or 10 linked tables because the schema was built around the first idea, not the second year of data. This walks the base structure that holds up.
Airtable
Views are why Airtable beats Google Sheets — but most bases have 40 views across 5 tables, half of them stale, none of them documented. This walks the view discipline that keeps a base usable past month three.
Airtable
Airtable automations are powerful, native, and brittle if you wire them wrong. Most bases past 20 automations have 5-8 that silently fail every week. This walks the patterns that hold up.
Airtable
DIY Airtable is a great idea — until it isn't. This is the honest framework: when the cost of self-managing a base exceeds the cost of hiring help, and how to tell which side you're on.