We utilize Frame.io as our review tool. When exporting files for Frame.io, ensure that you exports are in the CLIENT_WIPS folder within you project on the server.

Frame.io

Client WIPS

Please ensure to create subfolders as needed (for example, 'TVC', 'Product-film', etc) and always move old exports to a folder named '_OLD'.

Consult with the post-producer or team lead in advance to understand the different categories that will exist while working on this project.

Example of categories within the CLIENT-WIPS folder.

• Client Work in Progress (WIPs) must always be exported from Premiere Pro or Media Encoder.
• Do not export directly from After Effects or Davinci Resolve.
• Additionally, the export version number must match the version number in Premiere. Do not rename the version number of the export.
• When you have multiple options for a specific asset, append '_A', '_B', etc., after the version number. Do not use alternatives like '_ALT'.

✅ Do this:

2052_FB_Nutrilon-DuoBalans_TVC_20s_16x9_V019_A

2052_FB_Nutrilon-DuoBalans_TVC_20s_16x9_V019_B

❌ Don’t do this:

2052_FB_Nutrilon-DuoBalans_TVC_20s_16x9_V019

2052_FB_Nutrilon-DuoBalans_TVC_20s_16x9_V019_ALT

Frame.io

Frame.io

Internal and Client Links

Essentially, Frame.io should mirror the client's WIPS folder. It always contains an 'Internal' section and a 'Client' section. We upload exports for internal review to the 'Internal' section. You can share these links with your producer, specifying that they are for internal use. We should avoid sending clients links containing our internal feedback. Once everything is finalized, we also upload the video to the 'Client' section and share a new link, which the producer can then forward to the client.

• Whenever we have a new version for a client, we can stack the videos. By uploading the new version and dragging it on top of the old one, we can keep all versions of an asset in one place. This allows both the client and us to track all versions and the associated feedback.
• An exception to this method is when dealing with large batches of socials. In such cases, we use version folders to upload all assets in each round. This is because using the stacking function in these instances would be time-consuming.