Use Case

One story budget for radio, web, social, and TV with zero copy-pasting

A public media nonprofit uses Airtable as the editorial hub for Digital Video, Newsroom, Podcasts, and TV Production. Every piece of content is pitched, tracked, assigned, and scheduled in a single base, eliminating the manual copy-pasting and fragmented workspaces that previously drove status meetings.

The problem

Five production teams each managed editorial planning in separate workspaces. Story assignments, pitch approvals, and season logistics lived in disconnected tools, and cross-workspace sharing was clunky enough that status meetings became the default coordination method.

Season-based TV show management required copying data by hand between seasons. Production field pre-fills had to be entered manually on every new record, and there was no consolidated view of what was launching across platforms in a given week.

What they built

A shared Airtable base serves as the organization-wide story budget, tracking every piece of content across radio, web, and social media from initial pitch through final assignment. Interfaces give each team a tailored view without duplicating data.

Season-based TV show management is handled inside the same base, covering show logistics, production tracking, and air date scheduling. Automated field pre-filling replaces manual data entry between seasons, and a cross-team launch calendar surfaces what is publishing across all platforms in one view.

The outcome

Five teams work from one editorial base. Pitches flow through intake and approval without leaving the tool, production fields pre-fill automatically, and the story budget gives editors a real-time view of what is in progress, assigned, or ready to publish.

Status meetings to reconcile what each team is working on have been replaced by shared Interface views. TV show season management no longer requires copying data by hand, and the cross-team launch calendar is the single place where all platform releases are visible.

Inside the solution

Editorial Planning & Content Production

Content Production & Localization

  • Story budgeting across radio, web, and social platforms
  • Pitch tracking and approval routing
  • Season-based TV show management including logistics and air date scheduling
  • Cross-team launch calendaring for multi-platform releases
  • Fragmented workspaces and data silos across five production teams
  • Manual copy-paste between seasons creating data duplication
  • Clunky cross-workspace sharing driving reliance on status meetings
  • Eliminated status meetings with shared Interface views per team
  • Automated default field pre-filling replacing manual production data entry
  • Single editorial source of truth for all content across platforms
  • Digital Video
  • Newsroom
  • Podcasts
  • Content Operations
  • TV Production
  • Interfaces
  • Automations
  • Linked records
Build out this use case

Editorial Planning & Content Production

One shared editorial base where pitches, assignments, story budgets, TV show seasons and every platform release live together, so newsroom, podcast, digital video, TV and content operations teams all work from the same record instead of separate workspaces. Approved pitches open themselves in the story budget, new episodes inherit their season's production defaults automatically, and a cross-team launch calendar shows everything publishing on a given day across radio, web, social and broadcast.

Use this template
Editorial Planning & Content Production - Overview dashboard
How it works

From fragmented workspaces to one editorial base for five teams

Consolidate into a shared editorial base

Start from the content calendar template, then extend it with tables for pitches, assignments, and platform-specific fields. Migrate each team's existing content list into the shared base so all teams are working from one source instead of separate workspaces.

Set up pitch tracking and automated pre-filling

Add a pitch intake form that routes submissions into the shared story budget. Configure automations to pre-fill default production fields when a pitch is approved, eliminating the manual data entry that slowed season-to-season handoffs.

Build team Interfaces and the launch calendar

Create an Interface for each team showing only their relevant content in the shared base. Add a cross-team calendar view that surfaces all platform releases by date, giving editors and production coordinators a single place to see what is publishing across radio, web, social, and TV.

FAQ

Frequently asked questions

Each team gets a dedicated Airtable Interface view scoped to their content, so editors see only their assignments and production staff see only their tasks. The underlying base is shared, but record ownership and field-level permissions keep teams' data organized without collision.

Pitches come in through an intake form or are entered directly into the pitch table. They move through approval stages tracked by a status field, and when approved, automations pre-fill default production fields and notify the assigned team. No external tool or email handoff is needed.

Yes. The base uses linked record tables to separate show season logistics from the daily story budget. TV production teams manage episode tracking, restaurant or subject lists, and air dates in their own linked table while sharing the same base with news, podcast, and digital teams.

The launch calendar is an Interface view that surfaces every content item scheduled to publish on a given date, across all platforms and teams. Editors use it to spot conflicts, coordinate coverage, and ensure no two major pieces drop on the same day without coordination.

No. The deployed editorial planning and production workflow runs entirely on Interfaces, Automations, linked records, and forms. AI capabilities are in use on a separate survey analysis workflow within the same organization.

Reading document head…