An Airtable podcast guest intake workflow can turn scattered biographies, headshots and topic notes into a clear preparation packet for each episode. Use miniExtensions to collect and revise guest contributions, then let a producer decide what is ready for the host. Keep recording, calendar invitations and publication in the tools your team already uses.

Consider the fictional show Working Notes. Producer Maya is preparing an interview with Jordan Lee about improving team handoffs. Jordan appeared last year, so the show already has a biography. This episode still needs a new story, an updated introduction and clarification about which examples Jordan can discuss. Reusing the person’s record is useful; reusing last year’s editorial preparation without checking it is not.

Separate a guest from an episode appearance

The goal is not merely to collect a complete profile. It is to give the host a usable plan for one conversation. A returning guest may discuss a different topic, appear with a co-host or ask the producer not to repeat an old anecdote.

Use these suggested Airtable tables:

  • Guests: Name (single line text), Email (email), Preferred Introduction (long text), Pronunciation Notes (long text), Biography (long text), Headshot (attachment), and Website (URL).
  • Episodes: Working Title (single line text), Episode Number (autonumber), Producer (collaborator), Recording Date (date with time), Editorial Goal (long text), and Preparation Stage (single select).
  • Appearances: Guest (linked record to Guests), Episode (linked record to Episodes), Proposed Angle (long text), Current Role (single line text), Topics to Avoid (long text), and Guest Questions (long text).
  • Preparation Items: Appearance (linked record to Appearances), Guest (direct linked record to Guests), Request (single line text), Guest Response (long text), Supporting File (attachment), Review State (single select), and Producer Notes (long text).

One appearance joins one guest to one episode. Preparation Items hold follow-ups such as “Which example can you describe without naming a client?” Their direct Guest link supports the guest-facing view; the Appearance link preserves editorial context. These are workflow structures you create, not a built-in podcast template.

Ask for contributions the host can actually use

Keep the initial intake short. Ask for a two-sentence introduction, the intended listener takeaway, one specific example and questions the guest hopes to address. Request a headshot only if the show needs one. Explain whether it will be considered for episode artwork; an upload should not imply a broader permission agreement.

For Jordan, the proposed takeaway is “Spot an ownership gap before a handoff fails.” A useful example explains what changed, who needed the information and what the team learned. A list of company achievements does not answer those questions, even if every required field is filled.

Store reusable biography information on Guests and episode-specific material on Appearances. When a guest returns, the producer asks them to confirm their current role rather than silently treating an old biography as current. Keep any formal release process separate from this editorial checklist.

Provide a focused place for revisions

A portal is useful when guests need to return to several preparation requests. Use Guests for login records and connect each exposed data table directly to its guest through the documented users-table relationship. Do not assume the Episode or Appearance relationship supplies that link automatically.

For guest-private views, follow the personal-record filtering instructions. Under each view’s Filter and Sort settings, use the personal-record option in Choose Records to Display. Review every view, not just the first one.

Configure email-verification login with one valid address per guest. In the editable preparation form, expose Guest Response and Supporting File while keeping producer decisions and internal notes out. Staff should create the follow-up requests and assign the correct guest.

The document collection walkthrough covers the detailed upload-and-review pattern. Apply that pattern to episode preparation rather than building a general file library. Review record-creation and editing routes separately before sharing access.

Turn received material into a producer-ready packet

Use Preparation Stage values such as Collecting, Editorial Review, Ready for Host and Recording Complete. Staff advances the episode after reviewing its material. A populated attachment field is evidence of receipt, not proof the contents are useful.

Maya reviews Jordan’s example, notices it overlaps with a previous episode and creates a narrower follow-up. Jordan supplies a different story. Maya then writes a host-facing outline containing the agreed introduction, three conversation beats, a possible opening question and unresolved caveats.

Keep the producer’s proposed running order separate from guest contributions. Guests can suggest topics without editing the host’s outline or marking their own preparation accepted. An internal Airtable view can show episodes awaiting review and outstanding requests; this design does not automatically send reminders or generate a production packet.

Handle changes without losing the editorial context

If a recording moves, change the scheduled date on the same episode rather than creating another intake record. If the show decides to record an entirely different conversation, create a new appearance with its own preparation items. Retain the earlier material as context instead of overwriting the history.

For a two-guest episode, create separate appearances and verify each person sees only the material intended for them. Do not expose a shared episode table just to make its title convenient. Present only the necessary episode context in the guest-facing experience.

Agree on a preparation cutoff. After the producer marks the packet ready, late changes should be flagged for review rather than assumed incorporated into the host’s notes. A “Ready” label represents your team’s review decision, not an automatic promise that every downstream recording document has changed.

Check the workflow before inviting guests

Use fictional guests to check that each sees the right requests, can revise an answer and cannot change staff decisions. Confirm the producer sees the saved revision on the original item. Check that a returning guest’s new episode does not overwrite their earlier appearance.

This workflow fits small production teams that need structured editorial preparation without replacing their recording stack. Unlike a speaker proposal review process, it starts with an invited guest and ends with a prepared host, not a selection decision. Its useful outcome is a specific, reviewed conversation plan with remaining questions clearly owned.