Lesson Content

Single source of truth for brand assets.

Establish one designated location for current approved brand assets (logo files, approved backgrounds, brand palette reference) that all team members use – rather than individual copies distributed across personal drives or email attachments that may be outdated. When assets are updated, update them at the source rather than distributing new versions through ad-hoc channels.

Preventing version confusion.

Common version confusion scenarios: a producer uses an older logo file saved locally rather than the current brand kit version; two team members independently edit the same script file without coordination; a reviewed-and-approved video is inadvertently overwritten by a regenerated version. Clear file naming with version indicators (v1, v2-reviewed, final-approved) and communication about who has what file open for editing reduces these collisions.

Script version control.

For scripts going through multiple revisions, maintain clearly named version files (script-v1.docx, script-v2-reviewed.docx) rather than overwriting a single file with each revision – allowing comparison with earlier versions if needed and providing a clear record of what changed between drafts.

Archiving completed projects.

Completed, published projects should be archived clearly – marked as final/published and not inadvertently modified for subsequent projects. Using a new project for each video rather than modifying published project files prevents the risk of inadvertently altering a completed project when starting a new one from similar settings.