What should I record before handing a nine-shot TVC to another teammate?

Make one campaign record

A fictional backpack team has a script, four sheets, nine clips and successive film revisions. The nine-shot example is not a system limit: current plans can use 9, 16 or 25 shots, and the handoff must state the saved count. Sending “final.mp4” alone leaves the next person unable to tell which sheet was selected or whether an old buckle defect was repaired. Create a campaign record tying the product revision to the approved script, selected option and current film.

Use task identifiers as internal references but keep private source URLs and account credentials out of a public handoff. An approved public film and confidential supplier images have different sharing scopes. State those scopes before transferring files.

Use a minimal version ledger

This on-page ledger is a manual template with invented entries, not a downloadable file or synchronized task export. Copy the fields into your own record and replace every sample value. It does not transfer task ownership or private account access. A byte hash can distinguish files; it does not prove the product claim or publishing rights.

Example stop condition: a new shot-7 attempt fails while an older MP4 remains available. Label that MP4 as the previous output until the responsible reviewer confirms the accepted version; do not rename it “new approved film.” Keep the failed attempt’s status and the previous film’s decision separate.

Transfer only the needed deliverables

For an editor, include the selected film, relevant source clips, approved copy and unresolved issue list. For a social publisher, include only the final permitted export and publishing instructions. Giving every rejected sheet to everyone increases the chance that an unapproved product view is reused. Retain rejected material internally with a clear status.

Use suitable file-sharing tools with the correct recipients. CartVisual account sharing is not required to communicate a reviewed creative decision. A teammate who needs new generation should use their authorized workflow rather than your credentials.

Verify the recipient’s understanding

Ask the recipient to identify the accepted film revision and the claim they must not add. Check the received file against the approved download. The handoff is complete when both the file and its decision context are clear. Use the account-safe handoff checklist for recipient scope and the source-footage ledger when the next owner also needs to review generation costs. Technical delivery of an MP4 cannot establish publishing approval or permission for every attached source.