Define a technical acceptance pass
A file existing in storage does not show that it can be decoded throughout its duration. Include checks for readable picture, expected audio, plausible dimensions, and the media properties your import path needs. Record the tool or workflow used for inspection and keep technical results separate from content and source review so one pass is not mistaken for all three.
Inspect the whole duration
Corruption, freezes, missing sound, and broken endings may occur after an apparently normal start. Review representative full files and use systematic checks appropriate to the collection. Distinguish intentionally still scenes or silence from technical failures. Ambiguous cases need playback and context rather than automatic rejection based only on a simple low-motion or low-volume signal.
Check declared and observed properties
Compare manifest duration and track information with the delivered files. Confirm that labels do not extend beyond the playable timeline and that referenced tracks are actually present. Preserve a record of rejected assets and reasons. If a repair or re-export is supplied, treat it as a traceable version so downstream annotations can be rechecked against the changed media.
Plan the response to failures
Agree whether failed items are replaced, repaired, excluded, or reviewed individually. Report accepted duration after exclusions instead of retaining an original headline runtime. A technically valid file may still lack useful events or acceptable source documentation. Fiund reviews these dimensions separately when discussing proposed footage, samples, project scope, and commercial terms for a potential delivery.
Review checklist
- Check expected picture, sound, and import properties.
- Review beyond the opening seconds.
- Compare manifests and labels with playable media.
- Report accepted duration and traceable corrections.