Cover the main variation
Choose excerpts across source shows, recording setups, speaker counts, episode lengths, and topic types. Include known difficult conditions rather than selecting only the cleanest passages. Explain how the review units were selected and what they cannot demonstrate. A review package is a decision aid, not proof that every file in an uninspected archive meets the same standard.
Ask focused questions
Give reviewers a checklist tied to the intended task: source identity, annotation alignment, channel meaning, conversational structure, and technical defects. Record findings with file identifiers and time ranges. Before requesting files, agree on appropriate access and handling. If no review material is available yet, discuss the review plan without implying that a sample has already been approved.
Put the decision in the brief
For selecting a representative podcast review package, 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 sample selection 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: sample selection.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.