Skip to content
Convokast

How to Build a Podcast Pitch Evidence Packet

Build a podcast pitch evidence packet that lets a producer verify the guest, proposed topic, public proof, speaking boundaries and ready-to-use assets without searching across several folders.

Research this article with AI

Follow Convokast on Google

Add Convokast to your Preferred Sources.

How to Build a Podcast Pitch Evidence Packet

Build a podcast pitch evidence packet by collecting the proposed interview premise, the guest's direct experience, claim sources, approved examples, credentials, speaking limits and current media assets in one reviewable place. Keep a concise host-facing version separate from internal approval records. The packet should help a producer verify the pitch, not ask them to discover the story for you.

A polished biography cannot carry a weak premise. A folder full of reports cannot prove that the guest can explain the subject. The packet works when every item supports a specific editorial decision: whether this guest can deliver this conversation for this show's audience.

Start with the decision the producer must make

Write the proposed episode in one sentence before gathering documents. Name the listener, the decision or problem, and the guest's connection to it. For example: an operations leader can explain how a team decided which customer requests belonged in a standard process and which required an exception.

That sentence becomes the filter for the packet. A credential, source or example belongs only if it helps verify the guest, the premise or the usefulness of the conversation. Company history, unrelated awards and broad market reports stay out.

The podcast pitch angle guide can help narrow a broad area of expertise into an interview premise. Finish that work first. Evidence gathered around "leadership," "innovation" or "the future of business" will produce a large packet with no editorial center.

Add a short scope note beneath the premise. State what the guest can cover, what evidence is public and which nearby subjects are unavailable. This protects the producer from planning an interview around a customer name, unreleased result or private project that the guest cannot discuss.

Build a claim-and-source sheet

List the claims the pitch makes about the guest and the subject. Give each claim a source, owner and status. The sheet is useful even when the final email includes no external citation because it forces the team to distinguish a checked statement from remembered copy.

ItemWhat to recordHost-facing treatment
Guest identityCurrent name, title, company and approved biography sourceShow in the packet
Direct experienceThe guest's actual role in the decision or workState briefly with a public source when available
Topic claimThe factual point that supports the proposed discussionLink the best primary or public source
ExampleThe event, decision and result the guest may discussInclude only approved public detail
CredentialA qualification that matters to this topicInclude the issuing body or verification page
BoundaryA claim, name or subject that cannot be usedKeep the instruction internal or describe the topic limit without exposing the fact

Prefer the organization that created the information. A company announcement can verify the company's own announced event. A regulator can verify its own rule. A standards body can verify its standard. A guest's personal profile may establish how they describe their role, but it does not independently prove a disputed result.

Open every source and read the supporting passage. A relevant page title is not enough. Record the exact point it supports and remove links that only gesture toward the subject.

Match proof to the guest's actual role

Producers need to know what the guest did, saw or decided. "Worked on" can hide the guest's actual level of involvement. Replace it with a precise description that the guest and the record support: led the review, owned the implementation, advised the decision, conducted the research or observed the outcome from a named role.

Do not promote proximity into authority. An executive may speak for the company without having run the project. A consultant may know the method without permission to name the client. A founder may understand the product while a specialist owns the technical judgment. The packet should establish the guest's lane and leave adjacent claims with their real owners.

Use relevant credentials with the same restraint. A qualification matters when it helps the producer assess authority for the proposed subject. A long award list can make the packet look impressive while telling the producer little about the planned interview.

If the guest has no public biography, create a short approved one and identify the internal source used to check it. The podcast guest one-sheet guide covers the host-facing summary. The evidence packet sits behind that summary and records why each line is safe to use.

Separate public, approved and restricted material

Maintain an internal evidence record and a smaller host-facing packet. Mixing them creates two problems. The host may receive confidential review notes, while the internal team may lose the approvals and source context needed to defend the public copy.

The internal record can contain source notes, approval owners, expiry conditions, rejected wording and links to controlled documents. The host-facing packet should contain only material the producer may read, store and use for editorial preparation.

Classify each item:

  • Public: available from a current source and safe to share in the stated context.
  • Approved: cleared for this pitch or interview by the person who owns the information.
  • Restricted: unavailable for outreach, recording or promotion.
  • Unresolved: missing a source, owner or permission and therefore excluded until reviewed.

Do not hint at restricted proof. "We have confidential data that will amaze your listeners" gives the host nothing usable and creates pressure for a reveal. If the public evidence cannot support the premise, choose a different premise.

Commercial relationships also need clear handling. The FTC's endorsement guidance says an expert spokesperson should disclose a connection when promoting products in programming consumers would not recognize as paid advertising, including a talk-show appearance. The FTC's Endorsement Guides are the primary rule behind that guidance. Put relevant employer, client, investor, affiliate or sponsor relationships in the review record and prepare a plain disclosure when the appearance requires one. The podcast guest disclosure template provides a working format.

Choose examples that can survive follow-up

A pitch often sounds stronger after an example is added. The example must remain accurate when the host asks who decided, what changed, what evidence contradicted the first view and where the lesson stops applying.

For each proposed example, record the context, guest's role, decision, evidence available for discussion, outcome and limit. Remove examples that rely on a protected customer, an unverified result or a composite that never happened. An anonymized story can still identify the subject through industry, timing and detail.

Prepare the less flattering part of the example too. A producer may ask what failed, what the guest would change or who disagreed. A packet containing only the approved success line may pass initial review and collapse during the interview.

Do not turn one experience into a universal rule. State the conditions that shaped the choice. A practical episode becomes stronger when the guest can explain where the method may fail.

Make the host-facing packet quick to scan

Use a stable page or lightweight document with clear sections:

  • proposed conversation and intended listener;
  • guest name, current role and short biography;
  • direct connection to the subject;
  • approved examples and source links;
  • relevant relationships or disclosures;
  • topics that are outside the proposed scope;
  • headshot and pronunciation notes; and
  • campaign contact information.

Keep the pitch email self-contained. It should name the show fit, premise, guest and proof without requiring a click. The packet gives the producer a clean next step when they want to verify the case or pass it to a colleague.

Avoid expiring file links, account-required folders and attachment bundles with unclear filenames. Check the packet as an outside reader. Confirm that permissions work, assets download, source links reach the supporting page and old versions are no longer exposed.

Review the packet before every outreach batch

Assign one owner for the packet and an owner for each claim that can change. Review the guest's title, company description, public examples, source status, permissions, headshot, contact details and speaking boundaries before a new batch begins.

Use the campaign readiness checklist to connect the evidence packet with target approval, scheduling and interview preparation. Record the review date and withdraw disputed material instead of quietly replacing it. The old wording may already exist in an email draft or producer note.

A producer should be able to see the conversation, verify why the guest can have it and understand what is available on air. If that requires a guided tour of the folder, reduce the packet. Once the evidence is checked, turn the premise into a concise host-specific email with the podcast pitch generator.

Common questions

What belongs in a podcast pitch evidence packet?

Include the proposed interview premise, the guest's direct connection to it, a claim-and-source sheet, approved examples, relevant credentials, speaking boundaries, a current biography, a headshot and contact details. Keep internal approvals and restricted material out of the host-facing version.

Should the evidence packet be attached to a podcast pitch?

Usually a stable link is easier to review than several attachments. The email should still state the premise and fit on its own. Use the packet for verification and assets, not as a substitute for writing a clear pitch.

How much evidence does a podcast producer need?

Provide enough evidence to verify the guest's authority and the central claims behind the proposed conversation. Curate the strongest relevant sources rather than sending an archive that makes the producer decide which documents matter.

How often should a podcast pitch evidence packet be updated?

Review it before each outreach batch and whenever the guest's role, proposed topic, public claims, permissions or biography changes. Give each item an owner so disputed or stale material can be withdrawn quickly.

podcast pitch evidence packetpodcast guest pitchpodcast outreach

Work with us

Want to be the guest, not the reader?

We pitch, book, and prep you for the shows your buyers already listen to.

Book a discovery call

Free 20-minute call. If we are not a fit, we will say so.