The strongest material an HR team will ever put on a podcast is also the most fragile, because it belongs to somebody else, the warehouse lead who talks about coming back after a long illness, the engineer who describes what changed when she got a manager who actually listened, the new parent explaining how flexible hours kept him in the job, and every one of those stories, right, was given to you in trust before it was ever given to a microphone.
So when people leaders ask me what is different about editing their show compared with a sales podcast or a founder interview, my answer is that the craft is mostly the same and the responsibility is not, and most of what follows is about how we handle that responsibility on the edit so the person who told the story still recognises it, and still feels fine about it, a year after it goes out.
What makes an HR podcast different from other company shows?
The guests are employees rather than customers or experts, so every editing decision affects someone who still works with you on Monday, and the show has to serve culture, candidates and leadership at the same time.
A marketing show can afford to cut a guest down to their sharpest ten minutes and nobody minds, but when the guest is a colleague, a cut that changes the shape of what they said can feel like a betrayal even if every word is technically theirs. On top of that, the audience is mixed, current staff listen for whether it feels honest, candidates listen for what the job is really like, and executives listen, right, for whether anything in it could become a problem. A good edit has to hold all three of those listeners in mind at once, right, and that changes small decisions constantly, like whether a joke about a long week stays in or whether a guest's job title should appear on screen at all.
If your show is purely internal, only heard by employees, the post on internal company podcasts covers the distribution and access side, so here I will stay with the editing judgement that applies whether the episode is internal or public.
How should consent work when employees share their own stories?
Consent should be specific, written and repeated at the right moments, meaning before recording, after the guest hears the edited version and before anything is published to an audience wider than the one they agreed to.
The pattern I see go wrong is that someone agrees to "be on the podcast" in a hallway, records an emotional conversation, and only discovers what the episode contains when a colleague mentions it. What works far better is a simple sequence. That is one, the guest knows in advance where the episode will appear and who will hear it. Secondly, they get to listen to or watch the cut that includes them before release, not just the full rough recording. And the third part, they know how to ask for something to come out, and they are told honestly that it will.
None of that is legal advice, I should be clear, and your own policies and counsel decide what written consent needs to cover. What I can tell you is how the edit supports it. Our editors on Pixel Samy Podcast listen to every minute, so when a guest names a colleague who is not in the room, mentions a health condition, or says something about pay or a manager that they may regret, we flag it in the first cut with a timestamp rather than quietly deciding for you.
What happens if an employee changes their mind after recording?
You take it out, and because you keep the project files, the episode can be re-cut cleanly without that part instead of being patched or abandoned.
This is more common than people expect, and it is completely reasonable, someone feels differently about a story once they hear it played back, or their circumstances change, or they simply get nervous. Treat that as a normal part of running a people show rather than a crisis, and tell guests up front that pulling a section is allowed, because people who know they can withdraw tend to speak more openly in the first place, right, which ironically means fewer withdrawals later. Removing a section from a conversation and making the joins feel natural is ordinary editing work, and the turnaround on revisions is quick enough that a withdrawal a day before release does not have to sink your schedule.
The harder case is withdrawal after publication, right, and that is a policy decision on your side about takedowns and replacements, but practically, the project files belong to you, so a revised version can be produced without starting from scratch. My older post on contracts and file ownership for podcasters explains why that ownership matters so much in situations exactly like this.
If an employee would wince hearing their own episode a year from now, the edit is not finished yet.
Which policy topics belong in a public episode?
Topics where you can explain the reasoning and the experience behind a policy belong on a public show, while anything involving individual cases, active disputes or legal interpretation is better kept internal or left out entirely.
Parental leave, flexible work, learning budgets, how promotion decisions get made, right, these can make really really good episodes, because candidates want the honest version and employees appreciate hearing leadership explain itself. The risk sits in the details: a policy explained casually can sound like a promise, a throwaway line about how a past case was handled can identify a person, and an opinion about employment law can read as the company's legal position.
For anything in that territory, I recommend a review by whoever owns the policy, and where it touches law, by your legal team, before the episode goes anywhere. We will build that review into the timeline rather than treat it as an afterthought, and we mark the exact moments the reviewer needs to hear so they do not have to sit through the whole hour.
Employer brand that does not sound like a recruiting ad
The quickest way to lose candidates is a podcast that sounds like a careers page read aloud, so the edit should keep the texture of real work, the laughter, the honest complaint, the moment someone admits a project went badly.
People leaders are often nervous about leaving those moments in, and I understand why, but trust me on any level, a show where everyone agrees the company is wonderful convinces nobody, while a show where a team lead admits the first year was hard and explains what got better is the one a good candidate finishes. The editing job is to keep that honesty while removing anything that is unfair to a named person or genuinely confidential, and that line is a judgement call we discuss with you rather than make silently.
If your main goal is hiring, the recruiters page covers how episodes and clips get used in candidate outreach, and for a culture show at an employee owned company there is a good example of the angle in our Lakeland culture shows post. One more thing for public shows, right: if employees end up talking about the company's own products, the FTC guidance on endorsements is worth reading alongside your legal team, since staff speaking about their employer is a situation it addresses. Short vertical clips of a single honest answer often do more for an employer brand than the full episode ever will, and those come captioned at 25 dollars each.
The review step before anything goes out
Every people show needs a clear review path, and the simplest version has the guest, the HR owner and, where needed, legal each seeing the cut once before release.
What makes this manageable rather than painful is doing it in a fixed order with clear jobs, so nobody is reviewing the same hour three times for different reasons. The guest checks that the story is still theirs, right, the HR owner checks tone and policy accuracy, and legal only hears the flagged sections. Captions belong in this pass too, because colleagues with hearing loss are part of your audience, and the W3C overview of captions is a sensible checklist for what accessible episodes need. Then all the notes come to us in one batch, which keeps the revision tight, and the corrected episode arrives a working day after we receive them.
Our four step process shows the general flow, and you will notice that the review sits naturally in the gap between the first cut and the revision, so it does not stretch the schedule more than it has to.
How much should a people team budget for a first season?
For most HR shows, a single camera conversation of up to an hour on our Starter plan, bought as a four episode pack, comes to 170 dollars an episode, which suits a first season you want to test before committing further.
A four episode run is a good size for a pilot, it is enough to see whether employees actually volunteer stories, whether leadership is comfortable with the review step and whether candidates mention the show in interviews. If the show is filmed with two or more cameras in a proper room, the Studio plan fits better, and everything else is laid out on the pricing section. You pay per episode with no retainer, which matters for HR budgets that get reviewed every quarter.
When an outside editor is not the right answer
If your organisation's rules say employee recordings must never leave company systems, then an in-house editor or your internal comms team is the honest answer, because no outside service can meet that requirement, however careful it is. If you only plan two or three episodes a year, a freelancer hired per project is likely enough. And if the show is mostly a leadership broadcast with no guests, a simpler recording workflow may serve you better than a full edit. Is your show closer to one of those, or to a regular series built on employee voices?
Many people teams also work across several sites or countries, and recording happens wherever the guest is, which is fine, because the files come to us through a shared folder from any office and the edit pulls a remote interview and a studio conversation into one consistent show. We fit best when the show is regular, the stories are real, the review path is clear and you want an editor who treats each guest's words with the same care you do.
The person in the episode is the measure
At the end of every episode, the real test is not downloads or how polished the graphics look, it is whether the employee who shared their story would happily send the link to their own family. Build consent into each stage, edit for honesty rather than gloss, and let review happen before release instead of after a complaint. If you want help thinking through a first season, send me a recording you already have, even a rough internal one, and I will tell you how we would handle the sensitive parts and what it would cost. So yeah. That's my way of saying it.