Outline the archive
Describe the shows, languages, approximate recording periods, production workflow, and kinds of source files retained. Separate estimates from an actual file inventory. Note whether you hold mixed releases, isolated tracks, video, transcripts, or edit projects. This lets a sourcing conversation focus on the material that exists rather than an assumed ideal recording package.
Identify review dependencies
Explain who created the recordings and which contributor or contractual questions still need review. Do not attach sensitive participant records to an initial email. A project can begin with a high-level description and a plan for appropriate review. Neither a publisher relationship nor possession of files establishes that every proposed use has been cleared.
Put the decision in the brief
For what podcast publishers should include in a data inquiry, make the expected treatment visible in the written project brief. Include one acceptable example and one case that needs a decision. Ask the source owner which supporting records exist and mark missing information explicitly. Review the assumptions before applying a rule to an entire archive.
Keep a reviewable handoff
Carry the agreed policy, source identifiers, and unresolved questions into the delivery manifest. A later recipient should be able to connect a finding about publisher intake to the exact file and version reviewed. Discuss project fit with Fiund before sending source recordings or sensitive contributor information.
Review checklist
- Define the project decision: publisher intake.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.