I once spent three hours editing a “deep dive” interview only to realize the guest had recorded it in a bathroom with the fan running, and they were so nervous they’d spent the first ten minutes apologizing for things they hadn’t even done yet. Most of the gurus online will tell you that you need a thirty-page PDF briefing document to look professional, but let me tell you: a guest who is overwhelmed by paperwork is a guest who is going to freeze up the moment you hit record. Learning how to prepare a guest before recording isn’t about looking like a big-budget production; it’s about preventing the technical and mental collapses that turn a great conversation into a pile of unusable audio.
I’m not here to sell you a masterclass or a template that looks pretty in a Notion board. I’m going to tell you the actual, unglamorous mechanics of what works—from the specific technical checks that save your sanity to the way you frame the conversation so they don’t sound like they’re reading a press release. We’re going to focus on practicality over polish, ensuring that by the time you actually start the session, the hard work is already done.
Why Your Podcast Guest Briefing Document Saves Your Sanity
Look, I’ve spent enough hours staring at a waveform that looks like a jagged mountain range because a guest decided to record in a tiled bathroom or, heaven forbid, while driving their car. You can spend your entire career trying to “fix it in post,” but no amount of EQ or noise reduction can save a recording that was fundamentally broken at the source. A solid podcast guest briefing document isn’t just some polite formality; it is your primary defense against a wasted session.
When you send over a clear set of interview technical requirements, you aren’t being a diva. You are actually managing guest anxiety by removing the guesswork. Most people aren’t audio engineers; they are just nervous about sounding smart. If you tell them exactly which mic to use or remind them to turn off the dishwasher, you take the technical fear off the table. This allows them to focus on the conversation rather than wondering if their laptop fan is drowning them out. It saves you from the heartbreak of a “perfect” interview that you ultimately have to scrap because the audio is unusable.
Setting Recording Expectations Before the Chaos Starts
You need to be brutally honest about the environment. I’ve spent way too many hours in post-production trying to scrub the sound of a neighbor’s leaf blower or a hum from a cheap refrigerator out of a “professional” interview. When you’re setting recording expectations, don’t just ask them to find a quiet room; tell them to turn off the AC, close the windows, and for heaven’s sake, put their phone on Do Not Disturb. If they are recording on a laptop in a kitchen with tiled walls, you aren’t getting a clean signal, and no amount of EQ is going to fix that hollow, boxy sound.
It’s also about the gear. I always include a few specific guest audio quality tips in my outreach, like suggesting they use a dedicated headset rather than their computer’s built-in mic. If they’re using a high-end XLR setup, great—but if they’re on a Zoom call from a coffee shop, you need to know that before you hit record. It’s much easier to reschedule a session than it is to explain to your audience why your guest sounds like they’re underwater.
Five things you actually need to tell them
- Send a technical checklist that isn’t just “use a good mic.” Tell them specifically to avoid using built-in laptop mics or Bluetooth headphones, which are audio death. If they are recording remotely, tell them to use a wired connection if possible and to find a room with soft surfaces—rugs, curtains, a sofa—to kill that hollow, “recording in a bathroom” reverb.
- Give them a “no-go” list for their environment. This means no fans running in the background, no air conditioning units humming right next to them, and for the love of everything, tell them to put their phone on silent and away from the microphone. A vibrating phone on a wooden desk is a sound that will haunt your edit for three hours.
- Outline the structure so they aren’t guessing. Don’t just say “we’ll chat.” Tell them, “We’ll spend ten minutes on your background, twenty on the main topic, and five on lightning round questions.” When people know the map, they don’t wander off into those long, rambling tangents that I eventually have to chop out of the final cut.
- Brief them on the “edit” reality. You need to tell them upfront that you will be cutting for time and clarity. If they think every single “um” and “ah” is going into the final show, they’ll freeze up. If they know you’re going to tighten the phrasing, they might actually relax and speak more naturally.
- Do a dry run of the software. If you’re using Riverside, Zencastr, or even just Zoom, don’t assume they know how to navigate it. Send them a two-sentence instruction on how to join the link and how to check their levels. There is nothing that kills momentum like spending the first twenty minutes of a scheduled session troubleshooting a guest’s browser permissions.
The Bottom Line on Guest Prep
Treat your briefing document like a technical manual, not a polite suggestion; if they don’t know the difference between a built-in laptop mic and a dedicated USB condenser, your edit is going to be a nightmare.
Clear communication on the “no-go” zones—like background noise or interruptions—is better than any post-production plugin; you can’t EQ out a barking dog or a roommate vacuuming.
Set the stage for the actual conversation by telling them exactly what the goal is, so you don’t spend forty minutes of your recording time just trying to find the actual point of the interview.
The Cost of Silence
You can spend three hours EQ-ing a recording to fix a room that sounds like a tiled bathroom, but you can’t edit a guest into being prepared. If you don’t tell them to turn off their phone and move away from the air conditioner before you hit record, you aren’t producing a show; you’re just performing digital triage.
Nadine Okafor
The Long Game of Guest Management
Look, at the end of the day, guest prep isn’t about being a perfectionist; it’s about mitigating the inevitable friction that occurs when two people try to make magic through a piece of hardware. If you’ve sent the briefing doc, set the technical expectations, and clarified the scope of the conversation, you’ve already done more than 90% of the people out there. You’ve built a framework where the guest feels safe enough to actually speak, rather than just reciting a polished press release. You aren’t just checking boxes to look professional; you are actively preventing the kind of technical disasters that turn a forty-minute interview into a three-hour editing nightmare of “can you hear me now?” and “let me re-record that last bit.”
There will still be days when the guest shows up late, the internet drops out, or they give you nothing but one-word answers despite your best efforts. That is just the job. But when you realize that the craft is in the preparation, you stop fearing the chaos and start managing it. Don’t get discouraged by the slow build or the technical hiccups; focus on the process, get your settings right, and keep showing up. The good episodes—the ones that actually make it into my “too good to cut” list—are usually the result of the work you did before the red light ever turned on.
