The message I would least like any host to have to write is some version of "my old editor says I can have the project files, but it will cost me", because by the time that sentence gets written, right, the host has usually already lost a few weeks of publishing, has a back catalogue they cannot touch, and is negotiating with someone who knows exactly how stuck they are. And the frustrating part is that almost every one of those situations was predictable, there were small signs early on, a vague answer about turnaround, an invoice line nobody explained, a deadline that slipped without a word, and each one was easy to forgive on its own.
So this is the list of red flags I would personally walk away from, written from the seat of someone who runs Pixel Samy Podcast, where a lot of the hosts who get in touch have just come out of one of these situations, so I have heard the stories from the other side more times than I would like. Some of them show up before you hire anyone, some only show up after a few episodes, and I will be honest about which ones are worth forgiving, because not every editor with a rough edge is a bad editor, and sometimes a solo freelancer with a few quirks is still the right hire for you.
What is the biggest red flag before you hire a podcast editor?
The biggest one is an editor whose whole process is an automatic tool, where silence detection makes the cuts and a person only skims the result, because that edit will never sound like a real conversation.
You can usually spot it in the sample work, right, the answers feel slightly rushed, every breath is gone, a guest starts a sentence half a beat too early, and the whole thing has that nervous, choppy rhythm that listeners feel even if they cannot name it. I wrote about why on the post about why auto-cut podcasts feel wrong, and the short version is that a pause is often the most honest moment in a conversation, and a tool cannot tell an honest pause from dead air. Ask directly who listens to the whole episode, and if the answer goes vague, that is your sign.
To be fair to the tools, they are genuinely useful for some jobs, and the page on human podcast editing vs AI tools is honest about where they make sense, for instance a very low budget internal show where nobody minds the rhythm. On our own team the rule is that a person hears everything and the software stays in its lane, syncing angles and cleaning audio, because for a public show the cut is the product.
Why is a vague turnaround a warning sign?
Because "usually pretty quick" gives you nothing to plan around, and an editor who will not commit to a number before you hire them will not hit one after.
If you publish on a schedule, every episode has a date it needs to be ready, and the whole point of hiring an editor is that you stop worrying about that date. A good editor gives you a specific turnaround and tells you the exceptions in advance, a very long episode, a four camera setup, heavy graphics. A vague one leaves you guessing every week, and what happens in practice is that you start uploading earlier and earlier to protect yourself, which quietly eats the time the editor was supposed to save you.
The other version of this flag is a turnaround that changes depending on who you ask, the website says one thing, the call says another and the first delivery says a third. That is not flexibility, it is a sign nobody is actually managing the schedule, and the fix on your side is simple, write the turnaround you were promised into your first message and see whether the first delivery matches it.
What does it mean when an editor will not talk about file handoff?
It usually means that, if you ever leave, your project files will be difficult or expensive to get, and you should know that before you record a single episode with them.
Ask, before you hire, exactly what leaves with you if you go, just the finished episodes, or the original recordings and the editing projects as well. A good editor answers instantly, because the answer is simple. A worrying one says "we will sort that out if it comes up", or explains that project files are their intellectual property, and to be very honest, for most podcast editing that is a stretch, since the footage, the voice and the show are all yours. The post on who actually owns your podcast files covers what to check in a contract, and it is worth reading before you sign anything.
If an editor gets uncomfortable when you ask about leaving, you already know how leaving is going to go.
How do per-revision charges turn into billing surprises?
They turn into surprises when the price you agreed covers one round of changes, nobody mentions it, and the invoice arrives with extra lines for every note you sent after that.
There is nothing wrong with charging for extra revisions, it is a reasonable way to price, and plenty of good freelancers do it. The red flag is when it is not stated up front, so you find out by invoice, and secondly when "revision" is defined so tightly that fixing a misspelled guest name counts as a paid round. Ask exactly how many rounds are included, what counts as a round and what each extra one costs, and if the answer changes between the call and the contract, that tells you how the rest of the relationship will feel. The page about hourly vs flat rate podcast editing explains why a fixed price per episode makes this much easier to see.
Red flags that only show up after you hire
Some warning signs only appear once you are a few episodes in, and they matter more than the early ones, because by then your schedule depends on the editor.
The first is quality drift, where the early episodes were careful and the later ones slowly get sloppier, a lower third in the wrong font, music that does not match, a cut that clips a word. That is usually an editor who took on more work than they can carry, right, and your show became the one they get to last. The second is the sponsor read handled carelessly, a disclosure cut short or dropped, which matters because platforms and regulators expect paid promotions to be disclosed, and YouTube explains its own expectations on its paid promotion disclosure page. And the third, which is the subject of the next two sections, is how they behave when something goes wrong.
Silence when a deadline slips
An editor missing a deadline once is normal, life happens, but an editor who misses it and says nothing, so you only find out because you went looking, is a red flag I would not forgive twice.
The reason is simple, right, a late episode is a problem you can work around if you know about it, you can move the release, tell your guest, swap in a clip, and a late episode you discover at 9 pm the night before is a problem you cannot. What you want is an editor who warns you the moment they know, gives you a fresh delivery time, and never needs chasing. If you have to message twice to get a reply about a missing episode, that is the moment to start looking quietly, and the post on switching podcast editors without missing an episode explains how to move without a gap.
When your files become a bargaining chip
The worst red flag is an editor who uses your files as leverage, charging a release fee, slowing the handoff or holding project files until some dispute is settled.
This is the one I would walk away from immediately and permanently, because it tells you the editor sees your show as something they hold rather than something they serve. It usually starts small, a delay in sending a folder, a vague answer about where the project files are, and then it becomes a negotiation. Always keep your own copy of your raw recordings, whoever edits, so the worst case is losing project files and not your actual footage.
The way to protect yourself is boring and it works. Put it in writing before the first episode, that everything from the source recordings to the edit projects to the final files belongs to you, and that the projects travel with you on the day you leave. Ask for the project files of one early episode as a test, not because you are leaving, but because a smooth handoff on episode two is the best evidence you will get that the handoff on episode forty will be smooth too. And if an editor reacts badly to that request, honestly, you have learned something very very useful for the price of one email.
Are any of these red flags fair to forgive?
Some are, a single missed deadline that was flagged early, a revision policy that was explained clearly even if you dislike it, or a solo editor who takes a day to reply, because those are trade-offs rather than warning signs.
Here is the honest part. A solo freelancer will often be slower to reply than a team and may have no backup when they are sick, and that is not a red flag, it is the structure of working with one person, and for a small show on a tight budget it can be absolutely the right choice. The page on agency vs freelancer goes through when each one fits. What I would not forgive is anything involving honesty, hidden charges, hidden delays or hidden files, because those do not get better with time, and so on, they get worse as you depend on the editor more.
How Pixel Samy Podcast handles each of these
It is only fair to hold us to the same list, so here is how each flag maps to how we actually work.
On the billing flag specifically, the price of each episode is set before we start, for instance 199 dollars for an hour on our single camera plan, with the other plans on the pricing section, and because every episode is paid for separately there is no retainer to escape from if we ever stop being the right fit. If you want to run a full interview on any editor, us included, the list of questions to ask a podcast editor is the script I would use, and if you want to try it on me, the easiest place to start is a 15 minute call in which I go through your recent work and quote it, or an email to samy@pixelsamy.com that opens with the awkward question about leaving. You get the idea, I think, the red flags are mostly about honesty, and honesty is the one thing you can check cheaply before you sign and only expensively after. So yeah. That's my way of saying it.