Every interviewer knows the split-screen problem. Half your attention is on the guest. The other half is running a background process: Have we covered the origin story? Did they answer the second part of that question? How much time is left and how many questions am I behind?
That background process is expensive. It is also the reason so many interviews feel slightly mechanical. The host is managing a list instead of following a conversation.
A rundown that checks itself off removes the background process. This guide covers how to build one, how the auto-checkoff works, and how to structure questions so the whole thing actually helps.
What a Rundown Is
A rundown is your ordered list of questions or segments for the episode. In Podmod it lives in the session, and it is organized into three parts:
- Opening. How you get in. The framing, the first question, the thing that establishes what this conversation is.
- Core. The substance. Most of your questions live here.
- Closing. How you get out. The wrap, the forward-looking question, the where-to-find-them.
You draft the items, order them, and reorder them as your thinking changes. This part is ordinary list-making. The useful part is what happens during the recording.
Auto-Checkoff: The Part That Matters
Turn on the Rundown agent in the Agents panel before you record. Its description in the interface is exact: Auto-checks your planned interview questions as the conversation covers them.
During the take, the rundown watches the transcript. When the conversation genuinely covers one of your items, that item gets checked off and marked as automatically handled. Your rundown card shows a live count:
Interview rundown 2 / 5 ~~Origin story~~ ~~First product flop~~ auto How they found product-market fit Hardest hire so far Advice for first-time founders
The count is the point. At a glance you know where you are without holding it in your head, and you know it accurately, because it is based on what was actually said rather than what you meant to ask.
This changes the failure mode of interviews in a specific way. The common one is not forgetting a question. It is asking a question the guest already answered fifteen minutes earlier as a tangent, which makes you look like you were not listening. Auto-checkoff catches exactly that case: the item was covered, so it is checked, even though you never formally asked it.
Drafting the Rundown
You can write items yourself, or have Podmod generate a draft from the material you loaded into the session.
Generation reads your session context, including guest bios, and produces a starting set of questions across opening, core, and closing. It is a starting point, not a finished rundown. Treat the generated version as a first pass to react against: it will surface obvious questions you would have asked anyway, which is useful because it lets you spend your editing time on the questions nobody else would ask.
The workflow that works best:
- Load your session context first. Guest bio, source material, your notes.
- Generate a draft rundown from it.
- Delete half of it. The generic half.
- Add the three questions you actually care about.
- Reorder so the conversation has a shape.
Writing Questions That Work
The rundown is only as good as the items in it, and interviewing craft applies regardless of the tooling.
Write open questions. Journalism guidance is consistent that open-ended questions beginning with how, why, or "tell me about" produce detailed responses, while over-reliance on yes/no questions produces thin material. A rundown full of closed questions produces an episode of confirmations.
Write topics, not scripts. "First product flop" is a better rundown item than "Can you tell me about the time your first product failed and what you learned from that experience?" The short version leaves room for you to ask it in whatever way the conversation has earned by the time you get there. It also matches more reliably when the conversation covers the ground.
Keep the list short. Five to eight items for a standard interview. A rundown with twenty items is a script, and a script is the thing you were trying to escape. The whole point is to hold structure loosely.
Order for momentum, not chronology. The instinct is to walk the guest's story from beginning to end. Better episodes usually open somewhere more interesting and fill in the background as needed.
Using It During the Take
Once recording starts, the rundown sits in the research panel with your other agent cards. Two habits make it useful:
Glance, do not read. The count tells you most of what you need. Check it at natural breaks, not mid-answer.
Let items go. If the conversation has gone somewhere better than your list, follow the conversation. An unchecked rundown at the end of a great interview is not a failure. The rundown exists to stop you losing things you wanted, not to force you through a checklist.
Watch the closing section. This is where the rundown earns its keep most reliably. Hosts routinely run out of time and skip the closing they planned, because they were tracking the core section and lost the clock. Seeing your closing items still unchecked is a useful prompt to start steering.
Pairing the Rundown With Producer Coach
The rundown handles the questions you planned. The Producer Coach agent handles the ones you did not.
Its role in the interface: Follow-up questions, fresh angles, and devil's-advocate notes for the host. During the take it surfaces suggestions tied to what the guest just said. A card might read:
Producer Coach Ask what the first week without a paycheck felt like. Money anxiety lands harder than the resignation story.
Running both is the useful combination. The rundown holds your structure so you do not lose it. Producer Coach pushes against that structure with the follow-up the moment actually calls for. Interview research is clear that follow-up questions are often where the best material emerges, and follow-ups are precisely what a fixed list cannot contain, because they depend on an answer that has not happened yet.
Rundowns for Formats Other Than Interviews
The three-part structure is not interview-specific.
Solo episodes. Use the rundown as your outline. Opening hook, core points, closing call to action. Auto-checkoff tracks whether you actually made the argument you planned to make, which is a real problem in unscripted solo recording.
Panel shows. Use core items as discussion topics rather than questions. The checkoff tells you which topics the panel has genuinely covered versus circled around.
News and recap shows. Each story is an item. The rundown becomes a stack, and the count tells you how much of the stack you have cleared against your target runtime.
Why This Is Worth the Setup Time
Prep work that does not survive into the recording is the most common wasted effort in podcasting, and the workload is a genuine attrition problem. Forbes has documented how many shows fail, and creator surveys point to unsustainable production time as a core cause.
A rundown is maybe ten minutes of work. What it buys is not just the questions. It is the attention you get back by not running a tracking process in your head for ninety minutes, and the tail end of the episode not collapsing because you lost the clock.
After the Recording
The rundown persists with the session, so you can see what was covered and what was not. That matters for two things:
Follow-up bookings. The items you never got to are the outline for a second conversation.
Show notes. A covered rundown is a rough table of contents. It is not a replacement for generated show notes and chapters, but it tells you what the episode is actually about, which is useful when you sit down to write the description.
Common Rundown Mistakes
Writing the rundown before doing the research. The list should come out of the material, not the other way around. If you draft questions first, you get the questions anyone would ask. Load your session context, read it, then write.
Treating unchecked items as failures. A rundown is a safety net, not a quota. Some of the best interviews end with three items untouched because the conversation found something better.
Making items too long. Long items match poorly against a live conversation and lock you into phrasing you wrote before you knew how the interview would feel. Short topic labels work better on both counts.
Never reordering. The order you drafted is the order that made sense before you had spoken to the person. Reorder between the green room and the record button if the pre-chat changed your sense of where to start.
Building the closing last and thinking about it least. The closing section is the one you are most likely to skip under time pressure and the one listeners remember. Give it the same attention as the opening.
Build One for Your Next Episode
Draft five or six open questions, let Podmod check them off as you go, and spend the recording listening instead of tracking.
Set up your rundown at app.podmod.ai.