What is a Podcast Production Agreement?

This template is written for producers, audio engineers, voice artists and their clients, so that both sides can see what was promised, what it costs, and what happens if circumstances change.

There are 19 fields here, grouped into 6 areas — parties and contact details, scope and deliverables, payment and financial terms, dates, timing and duration, confidentiality and intellectual property, and legal protections and risk. Each is a term that causes argument when left unstated, which is why the generator asks for it rather than leaving a gap in the document.

Where these agreements go wrong, it is usually music or samples cleared for nothing wider than a demo rather than a defect in the boilerplate. Most freelance disputes come down to three things: work that grew beyond what was quoted, invoices that were never chased, and a client assuming they own copyright that was never actually transferred.

The preview updates live as you complete each field, so you can review the exact language before downloading it as PDF or Word. Treat the result as a well-organised first draft: sound in structure, but worth an attorney's review where the sums involved are significant or the situation is unusual.

What matters most in a podcast production agreement

Music and clip clearances

Any third-party music, footage or sample needs a licence. Make clear who is responsible for obtaining and paying for clearances.

Usage determines the fee

A voice recording for internal training is priced very differently from one used in a national advertising campaign. Define media, territory and term in the licence.

Session versus post-production

Separate recording time from editing and mixing time. Clients often assume a one-hour session means one hour of total work.

When you need a podcast production agreement

  • When someone else is paying: Where a third party funds or guarantees the arrangement, they should be named and their obligations spelled out. A guarantee that is only implied is not a guarantee.
  • When money changes hands: Record what the client owes, when each finished episode falls due, and what follows a late payment. These are the clauses relied on most often and left vague most often.
  • When sensitive information is shared: Confidentiality terms should be signed before disclosure, not after. Information already shared without protection is very difficult to claw back.
  • When replacing an earlier arrangement: Issue a fresh podcast production agreement when the original terms no longer reflect what the parties actually do. Amending informally leaves two inconsistent records of one relationship.
  • When more than one person is involved: Where several people share the obligation, the podcast production agreement should say whether they are liable together, separately, or both. That single word decides who can be pursued for the whole amount.
  • When the counterparty is new to you: With no track record between the parties, the written terms do the work that familiarity would otherwise do. That is exactly when precision pays for itself.

What to include in a podcast production agreement

This generator collects 19 details. Here is what each group covers and why it matters when the document is relied on.

Parties and contact details

Get these right before anything else. A dispute over the finished audio is unwinnable if the document names a party that does not legally exist.

Client Name
The full legal name of the client commissioning the work. Use the registered company name rather than a trading name so the party is identifiable if the agreement is ever enforced.
Client Address
The client's registered or principal business address. This is the address used for formal notices, invoices and any legal service of documents.
Contractor Name
The full legal name of the contractor or business performing the work, matching the name on invoices and tax records.
Contractor Address
The contractor's business address for notices and payment correspondence.

Scope and deliverables

Measure the finished audio rather than describing it. A scope stated in finished episodes can be checked at delivery of the master; one stated in adjectives cannot.

Project Name
A short reference name for the project so invoices, change orders and correspondence can all be tied together.
Description of Services
What the provider will actually do, described specifically enough that a third party could judge whether it was delivered.
Scope of Work
A precise description of what is included — and, just as importantly, what is not. Scope creep is the leading cause of disputes on service contracts.
Deliverables
The tangible outputs to be handed over, with formats, quantities and acceptance criteria.
Revision Policy
How many rounds of revision are included and what is chargeable beyond that. Without a cap, revisions become unlimited.
Client Approval Process
Who signs off, how long they have to respond, and what happens if they do not respond in time.

Payment and financial terms

Tie each payment to something observable — a delivered finished episode, a date, or delivery of the master — rather than to a general sense that enough has been done.

Service Fee
The total fee or rate for the services. State whether it is fixed, hourly or milestone-based, and whether tax is included.
Payment Schedule
When each payment falls due, tied to dates or milestones. A clear schedule is the most effective protection against slow payment.

Dates, timing and duration

Diarise every date in this section on the day the document is signed — particularly any notice deadline, which works exactly once against the party who forgot it.

Effective Date
The date the agreement takes effect. This can differ from the signature date, and it is the date obligations start running from.
Start Date
When performance begins. Tie this to a calendar date rather than a vague trigger such as 'on approval'.
Completion Date
The date by which the work must be finished, and whether that date is a firm deadline or a target.

Confidentiality and intellectual property

Ownership does not pass because money changed hands. If rights in the finished audio are meant to move, this section has to say so expressly.

Intellectual Property Ownership
Whether ownership transfers on final payment or the client receives a licence only. Silence usually leaves ownership with the creator, which surprises many clients.
Confidentiality Obligations
The duty to keep information private, who it may be shared with internally, and the standard of care required.

Legal protections and risk

Set a liability cap that reflects the real exposure rather than the fee, and carve out the things that should never be capped.

Termination Notice
How much notice is required to terminate and how that notice must be given.
Governing State
The state whose law governs the agreement. Choose a state connected to the parties or the work, as a wholly unconnected choice may not be respected.

Completing this podcast production agreement

Describing the finished audio

The strongest version of this podcast production agreement describes the finished audio in terms someone outside the deal could check — quantities, finished episodes, dates and standards. Write it so a reader who was not in the room can tell whether it has been done.

Checking the consents

Where a landlord, lender, insurer or licensing body has to approve the arrangement, obtain that approval before delivery of the master rather than assuming it will follow as a formality.

Attaching the session notes and approved rough cut

The session notes and approved rough cut carries most of the evidential weight here. Attach it as a schedule and refer to it by name in the body, rather than leaving it as an email nobody can find later.

Filling in every blank

Unfilled placeholders are read against whoever produced the document. If a field genuinely does not apply, write "not applicable" rather than leaving a gap.

Making the counts checkable

Where the price depends on finished episodes, keep a contemporaneous record as they are delivered. A count reconstructed at invoice time invites a challenge that a running record would have prevented.

Common mistakes to avoid

  1. Assuming the other side has authority. Check that whoever signs can bind their organisation. A signature from someone without authority is a defence waiting to be raised.
  2. Pricing only for the smooth version. Estimates are built on everything going to plan. Where music or samples cleared for nothing wider than a demo is a live possibility, build it into the timetable and the fee rather than absorbing it later and resenting it.
  3. Leaving confidentiality out. Both sides usually see something they should not repeat. A short confidentiality clause that expressly survives the end of the agreement covers it.
  4. Copyright assumed to pass on payment. The creator owns copyright by default. If the client is to own the finished audio, the agreement needs an express written assignment, normally conditional on payment clearing.
  5. No kill fee. If the client cancels midway, the producer should be paid for work completed plus an agreed percentage. Without it, a cancellation lands entirely on the supplier.

How to use this podcast production agreement generator

  1. Fill in the form. Complete the 19 fields above. The producer and the client both need naming in full, and the finished audio should be described in enough detail that a stranger could tell whether it had been delivered. Nothing is sent to a server — the document is assembled in your browser.
  2. Read the preview. Check the preview against the session notes and approved rough cut. Where the two disagree, the document is the version that will be relied on, so fix it here.
  3. Download and sign. Take the PDF for signing or the Word version for further edits. Make sure the signed copy reaches everyone named, since a document held by only one side is hard to rely on.

Podcast Production Agreement — frequently asked questions

Who owns the finished recording?

Usually the client owns the final produced master once it is paid for, while the producer retains their own project files, stems and any pre-existing material they brought to the session. If the client expects the raw multitrack files, that needs to be stated expressly — it is not normally included.

What usually goes wrong with a podcast production agreement?

Music or samples cleared for nothing wider than a demo. It is the recurring failure in this kind of arrangement, and it is rarely addressed in the document because both sides assume it will not happen to them. Name it, say who bears the cost, and the negotiation happens now rather than from a weak position later.

How detailed does the podcast production agreement need to be?

Detailed enough that someone who was not part of the conversation could read it and tell whether each side has done what it promised. That is the standard a court applies, and it is a useful test to run over your own draft before signing.

Which state's law should govern this podcast production agreement?

Choose a state with a genuine connection to the parties or the subject matter — where a party is based, or where the work or property is located. A choice with no connection at all may not be respected, and for property or employment the local state's rules will often apply regardless of what the contract says.

Who owns the work produced under this agreement?

Whoever the agreement says owns it — and if it says nothing, the creator generally does. Paying for work does not transfer copyright by itself. If ownership is meant to pass to the client, the assignment clause needs to say so expressly, and it is common to make the transfer conditional on payment in full.

How long do the confidentiality obligations last?

Ordinary commercial information is usually protected for a fixed period of two to five years after the agreement ends, while genuine trade secrets are often protected for as long as they stay secret. Whichever you choose, state expressly that the confidentiality clause survives termination — otherwise the protection ends with the contract.

How is notice properly given under this agreement?

Follow the notice clause exactly: use the stated method, send it to the address named in the agreement, and keep proof of delivery. Notice given informally — a text message, or an email to the wrong person — is frequently challenged, and a defective notice can leave the agreement running on.

Can I reuse the same contract for every client?

You can reuse the structure, but the scope, fee, timeline and deliverables must be rewritten for each engagement. Those are the clauses that actually get litigated, and a copied scope from a previous client is worse than no scope at all.