Identify recordings and versions
Assign stable identifiers to delivered assets and connect alternate edits or clips to their source recordings where known. Include paths, durations, dimensions, and relevant timing properties. A filename alone may not distinguish a revised export from an earlier version. The manifest should let a buyer determine which pixels and soundtrack each annotation describes without guessing from folder names.
Describe tracks and intervals
List the audio tracks intended for use and their relationship to the picture. For derived clips, preserve source offsets and note changes such as speed adjustments or reordered segments. Define timestamp units and missing-value meanings. An unknown source offset should remain unknown rather than be replaced by a plausible zero that changes the interpretation of every temporal reference.
Separate review dimensions
Technical integrity, annotation acceptance, content exclusions, and project-specific usage documentation answer different questions. Keep their states distinct and reference supporting records at an appropriate access level. A processed or uploaded file should not automatically receive a commercial approval label. This distinction helps a manifest remain useful operationally without overstating the review performed on the proposed material.
Validate at release time
Check file references, unique identifiers, interval bounds, and split relationships. Report accepted duration after removals and explain whether repeated source intervals are counted more than once. Include a release identifier and a change log for corrected files or labels. Fiund can incorporate these requirements into project scoping so a potential delivery is reviewable before commercial terms and volume are finalized.
Review checklist
- Identify exact recording versions and source groups.
- Document tracks, offsets, and time units.
- Keep technical and usage review states distinct.
- Validate interval bounds and accepted-duration counts.