Problem
A production folder contains multiple exports with the same filename but different codecs, and the upload operator selects one without a reliable technical identifier.
Solution
Root Cause / Diagnostic:
Relying on generic export filenames without embedding technical specifications (codec, resolution, color space) creates ambiguity, causing uploaders to publish low-quality web rips instead of master deliverables.
Actionable Fix:
1. Mandate Technical Identifiers in Export Tokens: Require export filenames to include technical tags (e.g., [ProjectID]_[Title]_[Resolution]_[Codec]_[ColorSpace]_[Version]).
2. Standardize Export Presets Across Editorial Teams: Distribute locked NLE export presets that automatically generate technical tags via metadata tokens.
3. Segregate Review Copies from Delivery Masters: Save web review copies (1080p_H264) and delivery masters (4K_ProRes422HQ) into distinct, dedicated subfolders.
Pro Tip:
Example export string: P26-104_Intro_4K_ProRes422HQ_Rec709_v01.mov vs P26-104_Intro_1080p_H264_v01.mp4; technical naming removes all doubt during publishing.
Relying on generic export filenames without embedding technical specifications (codec, resolution, color space) creates ambiguity, causing uploaders to publish low-quality web rips instead of master deliverables.
Actionable Fix:
1. Mandate Technical Identifiers in Export Tokens: Require export filenames to include technical tags (e.g., [ProjectID]_[Title]_[Resolution]_[Codec]_[ColorSpace]_[Version]).
2. Standardize Export Presets Across Editorial Teams: Distribute locked NLE export presets that automatically generate technical tags via metadata tokens.
3. Segregate Review Copies from Delivery Masters: Save web review copies (1080p_H264) and delivery masters (4K_ProRes422HQ) into distinct, dedicated subfolders.
Pro Tip:
Example export string: P26-104_Intro_4K_ProRes422HQ_Rec709_v01.mov vs P26-104_Intro_1080p_H264_v01.mp4; technical naming removes all doubt during publishing.