A guest who shows up unprepared is usually a host who sent one line and a link.

I've booked people who run companies, publish books, and speak for a living. Almost none will set aside an hour to prepare for your show, and you shouldn't want them to. The over-prepared guest recites. What they will do is skim one email on a phone, probably the morning of.

So what to send a podcast guest before recording is really a sequencing question: which few messages, and when each one lands. Here's what I send, what each piece is for, and the well-meant extras that quietly make episodes worse.

What to send a podcast guest before recording, at a glance

If you send nothing else, send two things: a brief with themes on it, and a calendar invite with the join link inside the invite. Those two prevent most of what goes wrong.

When What you send What it prevents
Within an hour of "yes" Confirmation: date, time in their timezone, duration, format The slot quietly evaporating
7 days out The guest brief + the calendar invite A guest who arrives with nothing to say
24 hours out Tech note, five bullets Audio you can't fix in post
10 minutes before "I'm in the room" The mis-set timezone

Four messages. None of them long.

Confirm it before they close the tab

Send the confirmation within the hour, while agreeing to be on your show is still a thing they remember doing. It needs four facts: the date, the start time written out in their timezone, how long you'll record, and what format the episode is.

Spell the time out. "Tuesday 14 October, 10:00 in New York (16:00 Berlin)" survives being read on a phone; "10am ET" gets converted by a human who is tired and gets it wrong. It is the most common near-miss in booking, and it costs nothing to prevent.

Format matters more than hosts expect. Audio or video, edited or live, one guest or a panel, published where. Someone who believed they were doing an audio interview and joins on camera in a paint-stained T-shirt will be irritated for the first ten minutes of tape. That one is your fault, not theirs.

Seven days out: the brief that does the real work

This is the artifact. Keep it under 300 words: one phone screen, no attachment, no PDF.

Six things go in it:

  1. Who listens. One line. "Mostly solo founders in B2B software, technical, allergic to hype."
  2. The angle of this episode. Not the topic. The angle. "Why your pricing rewrite failed the first time."
  3. Four to six themes, phrased as prompts rather than questions — "the moment you knew the first pricing model was wrong" reads like an invitation, "what made you change your pricing?" reads like a form.
  4. One thing to bring. A number, a document, a story they haven't told publicly. This is the highest-yield line in the whole brief.
  5. The bio ask. Name as they want it said, role and company, the one URL they want plugged, and phonetics if there's any doubt at all. Collect it now. Doing it later means chasing someone for a link on the day you publish, which is a genuinely annoying way to lose an afternoon. They're the same details you need when you write the show notes.
  6. What you won't do. "No gotchas, nothing about the lawsuit unless you raise it." Guests relax when the fence is visible.

What you don't send is the question list. Send themes and they arrive oriented; send twenty numbered questions and they arrive with twenty answers already written, which is the flattest tape you will ever record. There's a longer version of that argument in how to prepare for a podcast interview, and NPR's own interview prep guidance lands in the same place: know your outline, don't hand over the script.

The calendar invite is a document, not a timestamp

Put the join link in the invite body. Not in the email that mentions the invite. Not in a doc linked from that email.

Ninety seconds before the recording, your guest is looking at a calendar notification on a phone. Whatever isn't in that notification doesn't exist. So the invite body gets the join link, the duration, one line from the brief, and your mobile number — because when something breaks, it breaks in the four minutes when nobody is reading email.

One more thing: send the invite from the account you'll actually record from, and check the invite's own timezone field rather than trusting the time you typed. Calendar apps are extremely happy to schedule your recording at 10:00 in a timezone neither of you lives in.

Twenty-four hours out: the tech note

One message. Five bullets. No attachment, and no setup PDF, because the PDF does not get opened.

  • Headphones. Any wired pair beats none. Without them your voice comes out of their speakers and back into their mic, and that echo cannot be removed afterward. This is the one bullet worth being pushy about.
  • A quiet room with the door shut. Windows closed, A/C off, phone on silent. NPR's audio problems checklist is a good inventory of the things that ruin a take before it starts.
  • Wired internet if they have it, otherwise a seat near the router.
  • Close Slack, mail, and notifications. Every ding lands in the recording, always in the middle of the best answer.
  • Join five minutes early for a level check.

If your show is video, or the stakes are high enough to justify it, Adobe's remote recording guide covers recording each side locally instead of relying on the call — a "double-ender." It's real work for the guest, so save the ask for the interviews that deserve it.

Ten minutes before

One line: "I'm in the room whenever you're ready — here's the link again."

Eight seconds of typing, and it rescues the guest who converted the timezone wrong. If the start time comes and goes with no reply, you're not in prep anymore; you're in a different situation with its own minute-by-minute protocol.

What not to send

  • The full question list. Covered above, but it's the mistake nearly everyone makes at least once.
  • A welcome packet. Two thousand words about your show's mission is a document written to make the host feel professional. Nobody reads it.
  • Legal paperwork at the last minute. A release form landing 24 hours before recording reads as a warning sign no matter how routine it is. Send it at booking, with a sentence explaining why, or don't send it at all.
  • Their bio, rewritten by you. Ask for it. Don't improve it and hope they agree.
  • Anything that arrives after the tech note. By then the guest has stopped reading, and a late message only adds noise to the one thing you needed them to remember.

What the brief becomes once you're recording

The brief isn't only prep. It's the first draft of your run-of-show: themes become segments, the "one thing to bring" becomes the moment you build the episode around, and the bio you collected becomes an intro you don't have to improvise.

That handoff is what Liyam AI is built for. Its prep call agent turns what you already know about a guest into a plan, you drop your research in beforehand, and the on-screen script keeps that run-of-show and your questions visible while you record, organized by topic. When the conversation goes somewhere the brief didn't anticipate — which is the point of the good ones — it generates follow-up questions in real time from what's actually being said, so a guest who wanders off the plan becomes an opportunity instead of a scramble.

FAQ

How far in advance should I send podcast interview questions?

Send themes rather than questions, about a week before recording. A week gives a busy guest time to think without enough time to script answers. If you booked more than three weeks out, still send the brief a week before — anything sent at booking is forgotten by recording day.

Should I send the full list of questions to my guest?

No. Send four to six themes plus one specific thing you'd like them to bring: a number, an example, a story. Full question lists produce rehearsed answers, and rehearsed answers are why so many interviews sound identical. Keep your follow-ups for the live conversation.

What should I send a podcast guest right after they say yes?

A short confirmation with the date, the start time written out in their timezone, the recording duration, and the format — audio or video, edited or live. Add one sentence on the episode's angle. That's all; the detailed brief comes about a week before you record.

Do I need a pre-interview call with every guest?

No, and for most shows it isn't worth the hour. A good brief covers what a pre-interview would. Save the call for guests who are nervous, guests you've never heard speak, or episodes where one wrong assumption would waste the whole recording.

Bottom line

Four messages, none of them long: confirm within the hour, brief them a week out with themes instead of questions, send the tech note the day before, say hello ten minutes early. Most guest problems are logistics problems in a costume.

Then use what you sent. The brief is your run-of-show — and if you want it on screen while you record, with follow-up questions generated from what your guest is actually saying, start a free trial of Liyam AI.