Most hosts judge their editor the way they judge a restaurant, right, on a feeling, the episode looked nice, or it felt a bit slow, or the intro seemed off this week, and that feeling is not useless, but it is a terrible way to make a decision about someone you are paying every single week, because your mood on a Tuesday night, how tired you were when you watched the cut and whether you liked the guest all leak into the verdict.
I run an editing team, so I am obviously on one side of this, but I also hire and review editors all the time inside our own company, and the questions I ask about them have very little to do with whether I personally liked an episode. They are about patterns that show up across weeks and months, the number of notes, the dates, the drift, the way problems get handled. So here is how I would judge any podcast editor, including us, with signals that hold up better than taste.
Why is taste a weak way to judge an editor?
Taste changes week to week and mixes the editor's work with the guest, the topic and your own mood, so it tells you how you felt about an episode rather than whether the person editing it is getting better or worse.
A boring guest edited brilliantly still feels like a boring episode, right, and a fantastic guest can make a lazy edit feel exciting. If you only go on how you felt, you end up rewarding or blaming the editor for things they did not control. That does not mean taste is irrelevant, the style of a show matters, but style is something you agree once, write down, and then measure against, rather than something you re-litigate every week.
That written agreement is the foundation for every other signal in this post. If you do not have one, our post on the one page podcast style guide shows what to put in it, and it takes an afternoon to write.
How many notes per episode should a good editor need?
Expect several notes on the first few episodes while the editor learns your show, then a clear decline, so that by around the third month most episodes come back needing a small handful of notes or none at all.
This is the single most useful number you can track, and it costs nothing. Write down how many notes you send on each episode and, separately, whether any of them repeat something you already said before. The first number should fall over time, right, and the second should sit close to zero. An editor who keeps needing you to fix the same lower third, the same intro timing or the same pronunciation is not learning, and that is far more important than whether any individual episode was good.
For instance, say you send eight notes on episode one, five on episode two and three on episode four, with nothing repeated. That is an editor absorbing your show. If you are still sending eight notes on episode twelve, and three of them are the same three from episode two, the problem is not taste, it is process. How you send notes matters too, one merged pass works far better than a trickle of messages, which I go into in the revision round that actually works.
Does keeping deadlines really matter that much?
It matters more than most hosts admit, because a show that publishes late or irregularly trains its audience to stop expecting it, and an editor who misses dates quietly costs you listeners no matter how good the edit is.
Track promised date against delivered date, every episode, in the same simple sheet as your notes. You are not looking for perfection, the occasional honest heads up about a very long episode or a complex multi-camera shoot is normal and fine. You are looking for surprises, cuts that arrive late without warning, or a pattern where the delivery date slips by a day and then two. The difference between an editor who tells you in advance and one who goes quiet is pretty much the difference between a professional and someone you will eventually have to replace.
Our own promise is the first cut within 48 hours of your upload and revisions the day after your notes, so that is the bar I would hold us to, right, and if we ever started drifting from it, you would be entitled to ask why.
How do you tell if the edit is helping retention?
Compare retention across your own episodes over time rather than against other shows, and watch the specific points an edit controls, the first minute, transitions between topics and the stretch after any sponsor read.
Retention depends on far more than editing, the topic, the guest, the title and the thumbnail all play a part, so a single episode's graph is a weak verdict on anyone. What an editor does control is pace. If your graph shows a steep fall in the first minute week after week, the open is too slow. If there is a cliff at every sponsor read, the transition into it needs work. Our guide on reading a podcast retention graph without panicking explains what those shapes mean, and the podcast analytics guide covers which metrics are worth editing for at all.
Keep clicks separate from retention, because they measure different jobs. Whether people click an episode in the first place is mostly about packaging, and YouTube's own explanation of impressions and click-through rate makes that distinction clear. If clicks are the issue, that is a title and thumbnail problem, which our sister studio handles through thumbnail design for podcasters, rather than something to blame on the person cutting the episode.
Judge the editor on what the editor controls, and judge the packaging on what the packaging controls.
What does consistency over months actually look like?
It looks like episode twenty sounding and looking like episode two, the same loudness, the same intro timing, the same lower thirds and the same colour, without you having to remind anyone.
Drift is the quiet failure, right, and the hardest one to see from inside the weekly routine. It rarely shows up in one episode, it shows up when you put three episodes from different months side by side and notice the music got louder, the captions changed font or the colour on the second camera wandered. Every quarter, pull three episodes and watch the first two minutes of each back to back. It takes ten minutes and it catches drift better than any weekly review. For the audio side, Apple publishes its podcast audio requirements, and a consistent editor should be landing your episodes at a steady loudness every time.
This is also why we run every episode through a fixed check before it comes back, which is described in the quality check every episode gets before delivery. Whoever edits your show, ask what their check is. An editor who cannot describe it probably does not have one.
How does your editor handle problems they find?
A good editor tells you about problems in the footage before you find them, a camera that dropped out, a guest's audio that clipped, a sentence that might be sensitive, and proposes a fix rather than either hiding it or dumping it on you.
This one is harder to count but easy to notice. Think back over the last few months. Did your editor ever flag something, ask a question about a name, point out that a section ran long and suggest a cut? Or did every episode just arrive, silently, with whatever problems it had baked in? The second kind of editor may be competent at cutting, but they are not looking after your show, right, and the difference shows up the first time something genuinely goes wrong.
What should a simple editor scorecard include?
Three columns per episode are enough, the date the cut was promised against the date it arrived, the number of notes you sent, and how many of those notes repeated something you had already asked for.
I keep it that small on purpose. Hosts who build a twenty column review sheet stop filling it in by week three, and then they are back to judging on feeling. Three columns take thirty seconds after each episode, right, and after a couple of months they give you something very rare in this business, an honest picture of your editor that does not depend on how you felt on any particular night.
You can add a fourth column if you publish clips, noting whether the moments the editor chose were the ones you would have picked. That is closer to taste, so treat it as a conversation starter rather than a grade. Over time it tells you whether the editor understands what your audience reacts to, which is a skill worth paying for. Share the sheet with your editor too, because a good one will want to see it, and the way they respond to it is one more signal in itself.
When is it time to switch editors?
Switch when notes are not falling after a few months, deadlines slip without warning, or the same mistakes return after you have corrected them, because those patterns rarely fix themselves with more feedback.
Before you switch, have one direct conversation with the numbers in front of you, notes per episode, dates missed, repeated mistakes. Plenty of editors improve once they see the pattern laid out plainly. If nothing changes after that, move on without guilt. Make sure you can leave cleanly, which means getting your project files back, and our guide to switching podcast editors without missing an episode covers the handover. For warning signs that should end things faster, see podcast editor red flags I would walk away from, and if you are starting the search again, how to choose a podcast editor is the place to begin.
Holding Pixel Samy Podcast to the same standard
Everything in this post applies to us. At Pixel Samy Podcast we work per episode with no lock-in, so if your notes are not falling or our dates slip, you can stop at any time and take your project files with you. Studio clients get unlimited revisions, which means the notes count is a fair measure of how well we have learned your show rather than a cost you are rationing. You can see the plans in our pricing section.
At the end of the day, a good editor is one whose work you stop thinking about. You upload, the cut arrives when promised, the notes get shorter, the episodes stay consistent, and your attention goes back to the conversations themselves, which is where it should have been all along. If you can feel that happening over a few months, you have the right person, and if you cannot, a simple sheet with three columns will tell you why faster than any amount of gut feeling. So yeah. That's my way of saying it.