Locate the source failure
A silent export, a truncated download, and a microphone dropout require different investigation. Compare the file with a source manifest or reference recording where one exists. Preserve the original before attempting repair. Converting the container may make a file playable while leaving missing conversation unchanged; successful decoding alone does not establish completeness.
Decide the unit of exclusion
A short dropout may justify excluding a segment, while a missing participant track can affect the whole session. Keep the reason and source time ranges in a rejection log. If repaired material is retained, identify the processing applied and confirm that its artifacts are acceptable for the specific training or evaluation use.
Put the decision in the brief
For triage for damaged or incomplete podcast recordings, 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 damaged recordings 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: damaged recordings.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.