Published October 2, 2026
Podcast guest preparation
A podcast invitation can look like a single calendar entry while creating a surprisingly varied collection of work. Someone must confirm the format, understand the audience, gather background on the host, check the recording arrangements, and track anything promised afterward. An assistant can organize those tasks while the founder remains responsible for the substance of the conversation.
The most useful preparation packet does not script a personality. It reduces avoidable uncertainty so the guest can listen and respond naturally. Start by identifying what the founder needs to know before the recording, what the assistant may coordinate independently, and which requests require a new decision.
Confirm the shape of the appearance
Ask the assistant to establish whether the conversation is recorded, live, edited, or part of a larger event. Confirm the expected duration, participants, audience, topic, and publication arrangements. A calendar invitation alone rarely answers all those questions.
Preserve the host's actual answers. If the host says the discussion is exploratory, do not rewrite that as a promise that particular questions will be asked. The founder should understand the difference between a confirmed format and a likely direction inferred from earlier episodes.
Keep additional promotional requests visible. A request to supply a biography differs from a request to endorse a sponsor, join a paid campaign, or share a particular message with customers. The assistant can collect the details without accepting those commitments.
Research the host with a specific purpose
Review a small, relevant sample of episodes or written material. The goal is to understand the audience and conversational style, not to produce a complete history of the show. Note whether the host tends to ask for examples, challenge assumptions, or explore a guest's personal experience.
For each observation, distinguish evidence from interpretation. “The last two episodes opened with a practical example” is an observation about a sample. “The host always expects a case study” overstates what that sample establishes and may lead the founder to prepare too narrowly.
Do not collect personal details that have no bearing on the professional conversation. The assistant's research should help the guest participate respectfully and usefully. It should not turn an ordinary interview into an exercise in demonstrating how much private information can be found.
Build a brief around the guest's decisions
Put the essential logistics first, followed by the audience, topic, and a short list of questions the founder may want to consider. Include links to the original host material so the founder can inspect anything that affects preparation. Label unanswered questions clearly.
| Brief section | Assistant prepares | Founder supplies |
|---|---|---|
| Audience and format | Confirmed organizer information | Intended value for listeners |
| Topic background | Relevant source notes | Position and boundaries |
| Examples | List of previously approved examples | Permission for new disclosures |
| Promotion | Requested assets and dates | Approval of new commitments |
A compact packet should make the founder's remaining work obvious. If the guest needs to choose one example and confirm a topic boundary, say so directly. Hiding those decisions inside several pages of background defeats the purpose of delegation.
Prepare examples without inventing stories
The assistant can locate previously approved examples, organize notes the founder provides, and identify where an explanation needs more context. The founder should confirm that any story is accurate and appropriate to share. Do not turn a rough note into a named customer success story without evidence and permission.
If the founder wants to use a hypothetical example, label it as hypothetical in preparation notes. A scenario can explain a decision without claiming that the company achieved a particular result. Keep assumptions modest and avoid numerical outcomes that have no supporting record.
Review sensitive boundaries before recording. The founder may decide not to discuss unreleased plans, customer details, negotiations, or another person's performance. The assistant can preserve that boundary list, but the guest must understand it well enough to apply it during a live conversation.
Rehearse the practical setup
Check the recording instructions against the founder's actual equipment and location. Confirm the joining link, microphone selection, headphones, power, and an appropriate place to speak. If the organizer offers a technical check, coordinate it rather than assuming an earlier video meeting proves everything will work.
Prepare a recovery contact and a simple plan if the connection fails. The assistant should know who to notify and where to find any revised joining instructions. This is a coordination task, not a reason to create complicated backup arrangements the founder has never tested.
Avoid making changes immediately before the session unless they solve a real problem. A new microphone, recording application, or account can introduce uncertainty. Prefer a setup the founder understands and has successfully tested with the organizer's requirements.
Keep communication brief and specific
Organizer messages should answer the question asked and identify any decision still pending. The plain language guide is a useful communication reference. For example, send the approved biography with a clear file name and separately state that sponsor participation remains under review.
After recording, create a short list of promises made during the conversation. These might include sending a resource, checking a reference, or introducing someone. Confirm them with the founder before contacting third parties, especially if the recording changed the context of an earlier plan.
When the episode is released, review any promotional request against the founder's agreed scope. An assistant can prepare a draft announcement and the correct links. The founder should approve new claims, quotations, or endorsements attributed to them.
Improve the packet after the appearance
Ask which preparation helped and which material was unnecessary. If the founder never used a long host biography but relied heavily on the audience note, shorten the next packet accordingly. The objective is a useful conversation, not a large preparation document.
You can include this workflow within executive assistance, alongside scheduling and recurring follow-up. To define the preparation work you want to delegate, bring an example invitation to a free consultation.
Frequently asked questions
Should an assistant write my answers?
An assistant can organize your notes and suggest questions to consider. Your answers should reflect your knowledge and judgment. A script may be useful for an opening statement, but it should not substitute for understanding the topic.
What if the host will not provide questions?
Prepare around the confirmed topic and audience instead. Ask about the format and any excluded subjects, then identify a few examples you can discuss accurately. Do not treat the absence of a question list as permission to invent the likely conversation.
Who checks the published description?
The assistant can compare it with the approved biography and report factual differences. The founder decides how to address changes that affect positioning or claims. Keep the correction request specific and grounded in the agreed information.