How to Make Raw Interviews Ready for Publication
A practical guide to How to Make Raw Interviews Ready for Publication, including workflow, costs, timelines, quality checks, sourcing options, and project decisions.
On this page
- Who this is actually for
- The words people will use at you
- How the work actually runs
- What to send us
- How to check what comes back
- Three situations you might recognize
- What it costs in the US
- How long it takes
- In house, freelance, studio, or a model?
- The US rules worth knowing
- Questions to ask anyone quoting for this
- Working with a studio you'll never meet
- Putting this guide into practice
- More useful paths
How to Make Raw Interviews Ready for Publication is a practical question with consequences for budget, schedule, quality, and the people responsible for approving the finished work. This guide treats it as a real project decision rather than a keyword: what the work involves, where the trade-offs sit, what information changes the answer, and what to check before anything is published or delivered.
The details below are written for business owners, marketing teams, producers, and practitioners working with audio editing & production. Use the workflow, cost ranges, review checks, examples, and questions as a working brief. The right answer depends on the material, audience, channel, volume, and deadline, so those variables stay visible throughout instead of being hidden behind a universal recommendation.
Who this is actually for
Most people who end up on a page about How to Make Raw Interviews Ready for Publication got here for a practical reason. A project is about to start, a deliverable came back wrong, or a quote landed and nobody in the room could tell whether it was fair.
Any of those is a fine reason to be here. What follows covers the whole thing: what the work involves, what it costs in the US, how long it takes, what we need from you, and how to tell whether what comes back is any good. Skip to whichever part you need.
When occasional turns into ongoing
There's usually a moment when audio editing & production stops being something you handle between other things and starts being a job. It tends to look like this:
- The work is landing on someone whose actual job is something else, and their actual job is slipping.
- Volume has stopped being occasional and started being weekly.
- Quality varies depending on who happened to be free that day.
- You are turning down opportunities because production cannot keep up.
- The same fix keeps getting made because nobody wrote down how to do it right.
- You are paying for software seats that get used a few days a month.
If two or three of those are true, the question isn't really whether to get help. It's whether to hire, to use a freelancer, or to work with a studio — and there's a section further down that lays out the trade-offs honestly, including the cases where hiring us is the wrong answer.
The words people will use at you
Every field has vocabulary that gets deployed as a shortcut and lands as a barrier. Here's what the common terms in audio editing & production actually mean, in plain English. You shouldn't need this to buy the work, but it makes the conversation shorter.
- LUFS / LKFS
- Loudness Units relative to Full Scale. How loud something actually sounds, rather than how high the peaks are. LKFS is the US broadcast name for the same measurement.
- True peak
- The real peak level after digital-to-analog conversion, which can exceed the sample peak. Holding it at −1 dBTP keeps encoders from clipping.
- Normalization
- Platforms turning playback up or down to a house target. It is why mastering louder than the target gains you nothing and costs you dynamics.
- Room tone
- The sound of a silent room. Recording thirty seconds of it gives an editor something to patch gaps with.
- Stems
- Separate mixed groups — dialogue, music, effects — delivered alongside the master so changes are possible later.
- M&E
- Music and effects without dialogue. What you need if the piece will ever be dubbed into another language.
- De-esser
- A processor that tames harsh sibilance on voices without dulling the whole track.
- Plosive
- The thump when a hard P or B hits the microphone. Prevented with a pop filter; fixable, but never as cleanly.
- Dynamic range
- The distance between the quietest and loudest parts. Compressing it all away is what makes audio tiring to listen to.
- Sample rate
- How many times per second the audio was measured. 48 kHz for anything going with video; 44.1 kHz is the music convention.
There's a fuller reference library if you want to go deeper on any of these, and everything in it is written the same way — plainly, with sources.
How the work actually runs
Below is the actual sequence for audio editing & production work. Some of it looks like overhead until you've seen what happens without it.
1. Intake and assessment
We listen to everything first and tell you honestly what can be fixed and what cannot. Some problems are cheaper to re-record than to repair, and you should hear that before the invoice.
2. Edit
Structure, pacing, removing false starts and long pauses. On a conversation this is most of the work, and it is what separates a recording from a program.
3. Clean
Noise, hum, room tone, mouth clicks, plosives. Aggressive cleanup causes worse artifacts than the noise it removes, so there is a point where we stop and say so.
4. Level and balance
Every voice sitting at a consistent level relative to every other voice, and to the music.
5. Sound design and music
Beds, stings, transitions and effects, where the brief calls for them. Placed to support the content rather than to prove somebody had a library.
6. Mix
The whole thing balanced as one piece and checked on more than one set of speakers.
7. Master
Final loudness and true-peak limiting set to the destination target, because every major platform normalizes playback and mastering louder than the target just costs you dynamics.
8. Deliver
Masters, stems where useful, and a corrected transcript if that is in scope.
Where does How to Make Raw Interviews Ready for Publication fit? Usually somewhere in the middle of that sequence, and it inherits every decision made before it. That's the argument for settling scope early: a change at stage two is a conversation, and the same change at stage seven is a rebuild.
What to send us
A brief doesn't need to be long. It needs to be specific about a handful of things, and vague about everything else is fine.
What belongs in the brief
- Who it is for
- The audience, in one sentence, in your own words. Not a persona document — a sentence.
- What it has to do
- The action you want someone to take, or the decision you want them to be able to make.
- Where it will live
- Every placement, at every size. This is the single most common omission, and it is the one that causes reshoots and recrops.
- What already exists
- Brand guidelines, prior work, the files nobody likes. Especially the files nobody likes, and why.
- What is fixed
- Colors, typefaces, legal copy, platform requirements, anything that is not up for discussion.
- What good looks like
- Two or three references, plus one example of something you actively dislike. The dislike is more useful than the likes.
- The real deadline
- The date something has to be live, not the date you would like to see a draft. Say which one you are giving.
- Who signs off
- One name. A brief with four approvers and no decider is a brief that will cost you two extra revision rounds.
Two of those deserve emphasis, because they're the ones that cost money when they're missing. Where it will live — every placement, at every size — is the omission that causes reshoots and recrops. And who signs off is the one that quietly adds revision rounds: a project with four approvers and no decider will always cost more than one with a single name on it.
If you've got files ready now, you can send them straight over — they go to private storage rather than to an inbox, and nothing is public. If you'd rather see the standard before committing to anything, try us on a couple of files first. No card, no commitment, and if it's not what you need you've lost nothing but an afternoon.
How to check what comes back
You don't need technical expertise to review this well. You need a method, and it takes about ten minutes to learn.
- Check it where it will live
- Approve a web asset in a browser, a print asset on paper, an audio mix on a phone speaker. Approving a deliverable in the tool that made it is how problems reach the public.
- Check the edges, not the middle
- The middle is almost always fine. Look at the corners, the smallest size, the longest string, the darkest area, the last ten seconds.
- Check one thing at a time
- Color, then type, then spacing, then content. A review that tries to see everything at once sees the loudest thing and misses the rest.
- Collect feedback before you send it
- One consolidated list beats six emails. Contradictions inside your own organization are cheaper to resolve on your side than on ours.
- Be specific about what is wrong
- "Make it pop" costs a revision round. "The headline is hard to read against the sky, can we darken the area behind it" costs ten minutes.
- Say what is right too
- Not out of politeness. If you only flag problems, the next round can lose the thing you liked without anyone knowing it mattered.
The bar we hold ourselves to
So you know what you're measuring against, here's what gets checked on our side before anything reaches you. None of it is optional, and none of it is charged as an extra.
- Integrated loudness measured against the destination target, not set by ear
- True peak held at or below −1 dBTP so lossy encoding does not clip on playback
- Checked on a phone speaker, earbuds and monitors — three very different reproductions
- Noise reduction backed off to the point where the artifacts stop being audible
- Every speaker at a consistent level relative to every other speaker across the whole runtime
- Transcripts proofread against the audio rather than trusted from the machine
You can see how we present finished work — including the before and after — in the portfolio. Anything marked as a sample is our own demonstration piece rather than a client project, and it says so on the item.
Three situations you might recognize
Abstract advice is easy to agree with and hard to use. These are the shapes this kind of problem actually arrives in, and what we'd do about each one.
A podcast where one host was always too quiet
Both hosts were recorded to a single track, so their levels could not be adjusted independently. We got what we could out of it, then set them up with one track per speaker. Episode nine onward needed half the work of episode eight.
A video rejected by a broadcaster
Mixed to −23 LUFS by a studio working to the European standard. US delivery wanted −24 LKFS under ATSC A/85. A remaster, not a remix, but it cost a week nobody had.
Audio recorded next to an air conditioner
Noise reduction strong enough to remove the hum turned the voices watery. We backed it off to where the artifacts disappeared, accepted a quiet floor of room noise, and advised re-recording the three worst sections. Two of them were re-recorded; nobody has ever noticed the third.
None of those needed heroics. They needed somebody to look at the right thing early, which is most of what experience buys you in this field.
What it costs in the US
Here's what this generally costs in the United States. Treat it as a sanity check rather than a price list: the honest number depends on the job, and anyone who gives you a firm price without looking at the work is guessing.
| Type of work | Typical range | What that buys |
|---|---|---|
| Podcast episode | $75 – $400 per episode | Edit, cleanup, levels, music, mastered to a podcast target. Priced per finished episode. |
| Commercial and corporate audio | $400 – $2,500 | Voice-over finishing, sound design, mixing to a broadcast or platform spec. |
| Audio post for video | $50 – $300 per finished minute | Dialogue editing, effects, music and a mix delivered against the video's loudness target. |
Those are wide ranges, and they're wide for a reason. Here's what moves a job from one end to the other.
What actually drives the price
- Runtime and raw material
- Three hours of recording for a thirty-minute episode is an editorial job, not a cleanup job.
- Recording quality
- One track per speaker in a quiet room is straightforward. Four people on one microphone in a reverberant room is expensive, and the ceiling on the result is lower.
- How much repair is needed
- Noise reduction, de-reverb and clip repair are slow, and past a point they stop helping.
- Sound design
- Music editing, effects and custom beds are creative work with their own hours.
- Number of versions
- Different loudness targets, stems, an M&E version for localization — each is a deliverable.
- Transcript accuracy
- A raw automatic transcript is cheap. A corrected one with names and jargon right is a person's time.
How the money is usually structured
Separately from how much, there's the question of how. Five models cover almost everything in this industry, and the right one depends on how well the job can be described before it starts.
- Per unit
- A fixed price per image, per minute, per page, per asset. Best when the work is genuinely repeatable and you can describe one unit precisely. It is the easiest model to budget and the easiest to argue about, because everything hinges on whether your idea of one unit matches ours. Settle that on a sample before you settle it on an invoice.
- Hourly or day rate
- You buy time, and the output is whatever that time produces. Honest when nobody can scope the job yet — a rescue, an unknown archive, an exploratory phase. Ask for a not-to-exceed number anyway. An open hourly arrangement with no ceiling is a budget with no floor.
- Fixed project fee
- One number for a defined scope, usually with a stated number of revision rounds. The model most clients prefer and the one that punishes a vague brief hardest. The fee is only fixed if the scope is, so expect the scope document to be more specific than feels comfortable. That specificity is what protects you.
- Monthly retainer
- A set amount of capacity reserved for you every month. Worth it once the work is continuous rather than occasional — a catalog that refreshes, a channel that publishes weekly, a site that keeps changing. Below roughly ten to fifteen hours a month it usually costs more than buying the work as it comes.
- Value or outcome based
- Pricing tied to a business result rather than to effort. Rare, and rarely as clean as it sounds. It works where the outcome is unambiguous and attributable, and falls apart where it is neither. Treat an outcome-based proposal with the same scrutiny you would give any other claim about attribution.
If you want a real number rather than a range, the fastest route is to send us the actual brief — scope, volume, deadline, and a couple of sample files if you have them. That's usually enough for a fixed price rather than an estimate.
How long it takes
How long should this take? Here are the usual durations, with the caveat that every one of them assumes decisions get made when they're asked for.
| Phase | Usual duration |
|---|---|
| Assessment | Same day for most material |
| First edit | 2–4 business days |
| Revisions | 1 business day per round |
| Mix and master | 1–2 business days |
| Rush | Overnight, priced accordingly |
One thing worth saying plainly: the most common cause of a late project isn't production. It's waiting — for content, for a decision, for one person to look at something. If you want a project to move quickly, the highest-leverage thing you can do is name one person who can say yes and make sure they're available. That single change is worth more than any amount of chasing.
Rush work is possible and it's genuinely more expensive, because it means real people working real overtime or a job jumping a queue somebody else is in. We'll always tell you what a rush actually costs before you commit to it.
In house, freelance, studio, or a model?
This is the decision underneath "how much does it cost", and it deserves a straight answer rather than a pitch. There are four ways to get audio editing & production work done, and we're only the right choice for some of them.
Keep it in house
Someone on your payroll does it.
What's good about it: Fastest feedback loop there is, deepest product knowledge, no briefing overhead for small changes.
What's not: You are buying a person, not a job: their vacation, their sick days, their ceiling, and the software. It stops making sense the moment demand is spiky, because you pay for the peak all year.
Hire a freelancer
One specialist, engaged directly.
What's good about it: Cheapest way to buy real expertise, and you get the actual person who does the work.
What's not: One person is one point of failure. No cover, limited throughput, and if they move on mid-project you inherit their files and their conventions.
Use a studio
A team with a process, a review layer and cover.
What's good about it: Handles volume and variety, carries the QC step, and does not disappear when one person is sick.
What's not: More expensive per hour than a freelancer, and you are one client among several. Worth it when consistency across a lot of output matters more than the lowest rate.
Use a model
Generative or automated tooling, with or without a person checking.
What's good about it: Genuinely fast and genuinely cheap on the parts it is good at, and it does not get tired on page four hundred.
What's not: It is confidently wrong in ways that are hard to spot at a glance, and the parts it fails at are the ones a client notices: hands, text, counts, edges, continuity. Nothing should ship without a person having looked at it, which is why our AI work is priced with the review included rather than as a discount.
The short version: if the work is constant and central to what you do, hire. If it's spiky, or it needs a range of skills you can't justify employing, use a studio. If it's one specialist thing and you've found the right specialist, use them. We'd rather tell you that up front than take on a job we're the wrong shape for.
The US rules worth knowing
This isn't legal advice and we're not lawyers. It's a list of the American rules that come up often enough in this kind of work that not knowing about them gets expensive. If any of it applies to you, it's worth twenty minutes with someone who is a lawyer.
The CALM Act and ATSC A/85
The Commercial Advertisement Loudness Mitigation Act directs US broadcasters to control commercial loudness, and the technical standard it points at is ATSC A/85 — target −24 LKFS. This is the US number. EBU R 128's −23 LUFS is the European one, and defaulting to it for US broadcast delivery is a rejection waiting to happen.
Podcast targets
Podcast platforms are not broadcasters and do not enforce A/85. Apple Podcasts publishes guidance around −16 LUFS for stereo, and −19 LUFS is the common mono convention. Ask where it is going before you master it.
Music rights
A US sync license covers the composition; a master use license covers the specific recording. You generally need both, and a library subscription covers only what its terms say it covers. Read the tier, not the marketing.
And the general commercial stuff
Whatever the discipline, buying professional services in the United States raises the same handful of questions. These are the ones clients ask us most.
- Contracts and statements of work
- A statement of work that names the deliverables, the number of revision rounds, the ownership terms and the payment schedule is worth the hour it takes to read. Most disputes in this industry are not about quality; they are about two people having understood "done" differently.
- Ownership and work made for hire
- Under US copyright law, work created by an independent contractor generally belongs to the contractor unless there is a written assignment or it falls into one of the narrow statutory work-made-for-hire categories. That surprises a lot of buyers. Get the assignment in writing; any studio that hesitates is telling you something useful.
- Paying an outside supplier
- A US business paying a US contractor normally collects a Form W-9 and may need to file a 1099-NEC; paying a non-US supplier usually means a W-8BEN or W-8BEN-E instead. Your accountant will want these before the first invoice, not after the last one.
- Sales tax on services
- Whether a creative or digital service is taxable varies by state, and several states tax some digital deliverables and not others. It is worth one question to your accountant before a large engagement rather than one letter from a state revenue department after it.
- Advertising claims
- The Federal Trade Commission holds advertisers responsible for claims made in their marketing, including claims made in images. A retouched product photo that no longer represents the product is an advertising problem before it is a design one, and the liability sits with the advertiser rather than the retoucher.
- Accessibility
- Title III of the Americans with Disabilities Act has been read by US courts to cover websites in many circumstances, and federal agencies and their contractors are bound by Section 508, which points at WCAG. Accessibility is cheaper designed in than litigated out.
Our own terms are published rather than sent on request: you can read the terms and conditions, the payment terms, the refund policy and the confidentiality and NDA position before you talk to anybody. If something in them doesn't work for you, say so early — most of it is negotiable and all of it is better settled before the work than after it.
Questions to ask anyone quoting for this
Including us. If a supplier gets cagey about any of these, that's the answer to the question you were actually asking.
- Who is actually doing the work?
- Ask whether it stays with the person you are talking to, moves to a team, or gets subcontracted. None of those is wrong. Not knowing is.
- What exactly is a revision?
- Ask what counts as a revision versus a new brief, and how many are included. This is the single most common source of a bill you did not expect.
- Who owns the output?
- Get it in writing, including the working files. "You own the final" and "you own everything" are very different positions, and the second one costs more for a reason.
- What happens if it is wrong?
- Ask what a redo costs and how fast it happens. A studio with a clear answer has had the conversation before.
- Can I see work like mine?
- Not a showreel — work in your category, at your volume, with the constraints you have. A beautiful portfolio in another category proves taste, not fit.
- How do you handle my files?
- Where they are stored, who can reach them, how long they are kept, and what happens at the end. If you are sending anything unreleased, get this in the contract.
- What do you need from me?
- A supplier who cannot answer this has not thought about your side of the job, and you will discover that at the deadline.
One more, and it's the one people are most embarrassed to ask: what would make you turn this job down? A studio that has never turned work away is a studio that takes everything, and that tells you something about how carefully it's going to be handled.
Working with a studio you'll never meet
Most audio editing & production work now happens between people in different places and often different time zones. That's fine — it's been fine for years — but it rewards a few habits and punishes a few others.
- Overlap, not coverage
- What matters is not whether a supplier is awake at 2pm Eastern, but whether there is a predictable window when you can both talk. Ask for the window and put it in the calendar.
- Batch your feedback
- Across a time difference, three rounds of one comment cost three days. One round of twelve comments costs one. This is the single biggest lever you have on turnaround.
- Send files once, properly
- A clean handoff with originals, a written brief and named files saves more time than any amount of chasing. Half of all "slow" projects were slow at the start.
- Agree what "urgent" means
- Everyone says urgent. Agree in advance what a rush actually triggers — a different queue, a different price, a different set of hands — so the word keeps its meaning.
- Keep one thread
- A decision made in a direct message is a decision nobody else on either side can find. One channel, one thread per job.
Our hours overlap the US business day, and we'd rather agree a standing window with you than promise round-the-clock availability nobody can actually sustain. If you want to talk it through before committing to anything, get in touch — there's no pitch deck and nobody will chase you.
Putting this guide into practice
Start with the decision named in the title, write down the outcome you need, and collect one real example of what success and failure look like. Then use the workflow and review criteria above to compare options consistently. If the scope still cannot be stated clearly, a short discovery step is more useful than asking several suppliers to guess at a fixed price.
For help applying this to a live project, review our Audio Editing & Production services or send the brief for a scoped recommendation.
More useful paths
Use these paths to continue with the closest practical topic, service, or decision guide.
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.