A sponsor read should be clear enough to trust, authentic enough to fit your show, and documented enough that nobody has to reconstruct the approval history later. The safest process is to review the script, claims, disclosure, and delivery before recording—not after the episode is assembled.

This checklist focuses on independent podcasters producing their own sponsor reads. It does not replace legal advice or the rules that apply to broadcast radio or television. For those broadcasts, the Federal Communications Commission’s sponsorship-identification rules can require an announcement at the time of broadcast that material was paid for, furnished, or sponsored, together with the sponsor’s identity.

The direct answer: what should you check before recording?\n

Before you record, confirm seven things:

  1. The ad is clearly identified as sponsored material.
  2. The final wording has been approved by the sponsor and by the person who owns the episode.
  3. Every factual claim, offer, deadline, and price has a source or an expiration date.
  4. The language will be understandable to your audience.
  5. The read sounds like a real host speaking, not a legal notice read at speed.
  6. The recording plan identifies every script, take, and final audio file.
  7. A final review happens after assembly but before publication.

If any of these checks is unresolved, pause the recording or publication. The purpose of the checklist is not to make every sponsor read sound identical. It is to prevent avoidable mistakes and preserve a clean approval trail.

A repeatable sponsor-read approval workflow

Use one working document or project folder per campaign. Assign a name that includes the sponsor and episode so files do not become ambiguous later.

A practical folder structure is:

2026-03-ep-42_Acme-Sponsor/
├── 01_brief_and_offer_terms/
├── 02_script_versions/
├── 03_claims_and_evidence/
├── 04_approved_script/
├── 05_recordings/
├── 06_approved_final_audio/
└── 07_publication_record/

The numbers are an editorial suggestion, not a required standard. The useful principle is separation: working material, approved material, and published material should never look identical.

1. Record the brief before approving copy

Create a short campaign brief with these fields:

  • Sponsor name\n- Product or service\n- Campaign objective\n- Target audience\n- Host instructions\n- Required talking points\n- Prohibited claims\n- Offer details and expiry date\n- Landing-page URL or promo code\n- Required disclosure wording\n- Final approval deadline\n- Per-read fee or agreed compensation terms\n This becomes the reference for every later decision. If a detail matters but is missing from the brief, flag it before reviewing the script.

2. Keep a deliberate script-version history

Name each draft with a date and revision number:

Acme_ep42_script_v01_2026-03-08.docx
Acme_ep42_script_v02_2026-03-10.docx
Acme_ep42_script_approved_2026-03-12.pdf

Do not overwrite the approved copy without preserving the prior version. A shared document can work, but use its comment or version history rather than asking everyone to exchange files named “final.”

In the approval record, capture:

  • Which script version was approved\n- Who approved it on the sponsor side\n- Who approved it for the show\n- The date and time of approval\n- Any conditions attached to the approval\n- The deadline by which changes can still be made\n “Approved” should mean the full read, including the offer code, URL, pronunciation notes, and disclosure—not merely the first paragraph.

3. Review the script in layers\n

Do not read the copy only for grammar. Review it for the following in sequence.

Accuracy and evidence\n

Highlight every claim that could be checked:

  • Performance figures\n- Prices or discounts\n- “Free,” “unlimited,” or “best” language\n- Eligibility conditions\n- Availability claims\n- Health, financial, or performance implications\n- Comparisons with other products\n- Superlatives such as “the safest” or “number one”\n- Named certifications, awards, or endorsements\n Ask the sponsor for the evidence behind each claim and record where it is stored. If the evidence is a URL, a PDF, or an email, save it in the claims-and-evidence folder with a meaningful name.

The host should not have to guess what a claim means. If it is ambiguous, request a precise replacement or remove it. Avoid weakening a legally risky statement simply by adding “some people say.” The surrounding tone does not cure an unsupported claim.

Offer mechanics\n

Check every part of the redemption path:

  • Promo code\n- URL\n- Expiration date and time zone\n- Eligibility rules\n- Whether a purchase is required\n- Shipping or service limitations\n- Whether the offer is new, returning, or excluded for existing customers\n

If an offer expires soon, add an “offer valid through” line even if the landing page displays it. Podcast listeners may hear the read long after the page is viewed. Set a date by which the offer should be removed from the episode or replaced with fresh approved copy.

Disclosure placement\n

Use a clear spoken disclosure, such as “This episode is sponsored by Acme.” Put it before the sponsor’s sales message so listeners encounter the commercial relationship before the persuasive copy.

Avoid burying the disclosure inside a sentence that could sound like ordinary show content. The wording should be unmistakable when heard without looking at a transcript. If the sponsor requires a specific phrase, treat that as an instruction to verify rather than a reason to skip your own review.

For a general independent podcast, the disclosure should at least make clear that the segment is paid or sponsored. Broadcast stations have additional obligations under the FCC rules, including announcing sponsorship at the time of broadcast and identifying the sponsor. If your content may be carried by a broadcast station, ask that station or its legal adviser what it requires.

Audience understanding\n

Read the script aloud as though you are speaking to one listener, not reciting a sales page.

Ask:

  • Can a first-time listener tell what is being offered?\n- Are product names pronounced consistently?\n- Are there acronyms that need expansion?\n- Would the claims sound credible in your show’s format?\n- Does the host sound comfortable rather than unusually promotional?\n- Does the script include jargon your audience would not recognize?\n A useful editorial test is to rewrite each claim as a plain sentence. If the rewrite becomes vague, the problem may be the claim rather than the rewrite. Ask for a clearer fact instead of adding more promotional adjectives.

Host fit and delivery\n

Ask the sponsor to supply talking points, not only finished copy. A strong brief usually tells the host what must be said, what can be said, and what cannot be said. That gives the read a natural structure while preserving the sponsor’s requirements.

Mark pronunciation, emphasis, and required phrases in the script. Do not add personal claims or endorsements that the host has not verified. If the host’s genuine experience supports a statement, it should still survive the same accuracy check as any supplied claim.

A copyable script-review record

Use this template for each sponsor campaign:

Campaign:
Sponsor:
Episode:
Script version reviewed:
Reviewer:
Review date:
\nRequired talking points checked: Yes / No\nRequired disclosure included: Yes / No\nOffer code and URL verified: Yes / No\nExpiry date verified: Yes / No\nAll factual claims have evidence: Yes / No\nAudience terminology is understandable: Yes / No\nPronunciation notes resolved: Yes / No\nSponsor approval received from / on:\nShow approval received from / on:\nOutstanding issues:\nFinal approved script location:\nFinal approved audio location:\n```

This record creates a simple answer to the most common post-production question: “Which version of the script is in this episode?”

## Prepare the recording without losing the approved copy

At the start of the session, confirm which file is the approved script. If the sponsor changes a word or offer detail on the call, pause and create a new version. After the change is accepted in writing, record from that version.

Label takes clearly:

```text
Acme_ep42_take01_master.wav
Acme_ep42_take02_master.wav
Acme_ep42_take03_preferred.wav

Do not overwrite earlier takes. They provide a fallback if the preferred read has a pronunciation error, an incorrect code, or a poor edit.

For the final read, check:

  • The disclosure appears before the commercial message.\n- The sponsor and offer are named correctly.\n- Every number and code is read accurately.\n- No placeholder text remains.\n- No stray pre-roll or off-mic conversation appears.\n- The read does not imply a personal endorsement beyond what the approved script permits.\n Save a copy of the final approved audio separately from working takes. If your team uses a shared drive, confirm that the copy can be accessed by the person responsible for episode assembly.

Review the ad after episode assembly\n

The pre-publish review is not a substitute for reviewing the script. It catches problems created by context, trimming, transitions, or mixing.

Listen to the complete ad segment in the assembled episode—not only to the isolated file. Confirm that:

  • The disclosure is still intact after editing.\n- No sentence was cut in a way that changes the offer or qualification.\n- Music or effects do not obscure the sponsor name, code, URL, or expiry.\n- The host’s tone matches the episode.\n- The segment starts and ends cleanly.\n- The episode notes, transcript, and visible ad information agree with the audio.\n- Any transcript uses the same sponsor name, offer details, and disclosure meaning as the recording.\n For a broader production check, use the Podcast Ad Break Workflow: A Practical Checklist for Mid-Roll Ads and the Podcast Episode Publishing Checklist.

File tracking: use a simple manifest\n

A spreadsheet is enough for a solo creator. A shared sheet can also prevent a sponsor from approving one episode while the team publishes another.

Track at least:

| Field | Purpose |\n|—|—|\n| Episode | Links the campaign to the published episode |\n| Sponsor | Prevents naming confusion |\n| Script version | Establishes the exact approved words |\n| Sponsor approver | Records responsibility |\n| Show approver | Records editorial acceptance |\n| Final audio filename | Identifies the read to use |\n| Placement | Marks pre-roll, mid-roll, or post-roll |\n| Offer expiry | Determines when the read must be replaced |\n| Publication status | Prevents an unapproved cut from going live |\n| Published URL | Provides the final reference |\n Do not rely on memory, chat history, or the newest file’s timestamp. A manifest is more valuable because it connects a spoken promise to an exact script and final audio file.

A practical pre-publish decision\n

Before publishing, answer these questions in writing:

  • Did I read the final assembled ad from the episode timeline?\n- Can I point to the approved script version?\n- Does the disclosure make the paid relationship clear?\n- Can I verify every price, claim, code, deadline, and qualification?\n- Is the offer still valid on the planned publication date?\n- Does the transcript and episode notes match the audio?\n- Do I know where the final audio and approval record live?\n If the answer to any question is no, hold the episode or place a clearly responsible owner and deadline next to the issue. Do not rely on a vague promise to “check before upload.”

Frequently asked questions\n

Should the sponsor approve every version of the ad script?\n

Yes. At minimum, approve the exact final wording and any required disclosure. If the sponsor changes the script after approval, create and record a new version and obtain approval for it. If only the host’s delivery varies while the words stay the same, confirm that the sponsor permits the host to perform the approved copy in your normal style.

Is a verbal disclosure enough?\n

For an independently produced podcast, a clear spoken disclosure is the practical baseline for this workflow, though legal and platform requirements can vary. Check any applicable requirements, and consider adding a visible disclosure in the episode notes or transcript when appropriate. Do not assume a transcript entry alone makes an audio disclosure clear.

Can I rewrite awkward sponsor copy to sound more natural?\n

Often, yes—but only within an agreed boundary. Minor host-read improvements should preserve meaning, claims, offer details, and required language. If you rewrite a claim, an offer, or a legally important phrase, send the revised version for approval before recording.

What if the offer expires after the episode is published?\n

Keep the published episode in your records, but stop presenting the expired offer as current in new materials. If the episode contains a time-sensitive claim that becomes misleading, follow your platform’s correction or removal process and decide whether an update is warranted.

Do I need the same workflow for free products or gifted episodes?\n

Treat the same review process as a good editorial safeguard. Even without cash payment, free access or gifts can affect what a creator is able to say. The exact disclosure requirement depends on the relationship, content, and applicable rules.

The minimum viable checklist

If time is tight, complete this abbreviated version before publication:

  • The segment is clearly disclosed as sponsored.\n- [ ] The sponsor approved the exact final script.\n- [ ] The episode owner approved the read for the show.\n- [ ] Claims have supporting evidence.\n- [ ] Prices, codes, URLs, dates, and conditions are verified.\n- [ ] The offer remains valid at publication.\n- [ ] The final audio filename is recorded in a manifest.\n- [ ] The assembled episode and transcript have been reviewed.\n The goal is not paperwork for its own sake. It is a sponsor read your audience can understand, your team can reproduce, and you can stand behind after publication.

Sources