Use physical file facts
Record channel count, sample rate, sample format, duration, and the relationship between files. A two-channel export might be a stereo mix, duplicated mono, or a split-speaker recording. Write the actual interpretation in the manifest instead of allowing downstream teams to infer it from an extension or a channel count.
Separate identity from routing
Channel labels should describe the recording layout without unnecessarily exposing participant information. A stable local speaker key can connect a track to session metadata. When channel routing changes during a session, mark the change explicitly. A single label for the whole file can otherwise turn a technical routing event into an apparent speaker change.
Put the decision in the brief
For a practical channel manifest for podcast audio, 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 channel manifests 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: channel manifests.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.