Use one folder per event
Create a root folder with the event name and date. Separate music, videos, documents and backups. Use stage numbers if they help reflect the running order. Do not mix two clients’ files because their names look similar.
Use names that explain the purpose
Replace names such as “latest_final_2” with a purpose and version, such as “03_awards_approved”. Preserve file extensions. Agree on naming with colleagues and notify the operator before renaming delivered materials.
File Manager and projects
File Manager is a Qventa Live direction. The hero folder illustrates an event project. Automatic collection of all resources and project portability depend on implementation and must be checked in the build.
An example event folder structure
Create an event folder with subfolders named 01_audio, 02_video, 03_presentations, 04_documents and backup. Use meaningful names such as 02_entrance_approved.mp3. After copying to a different drive, open files from the new location. Check whether the project stores copies or links to original paths. Until that is confirmed for your workflow, preserve the folder structure and backup.
event/ 01_audio/ 02_video/ 03_presentations/ 04_documents/ backup/
Quick checklist
- Create a dedicated event folder.
- Group materials by purpose.
- Mark approved versions.
- Copy the set to backup storage.
Does the project automatically collect every file?
Do not assume this behavior. Check whether the build copies media or stores links to original paths before moving a project.