The 9:16 cutdown, the 15-second teaser, the version without the logo. Every project produces these, and every team hesitates over where they go. One question settles it: can the client approve this on its own?
If it is the same deliverable changed after notes, upload it to the same task and it becomes the next version. If it has its own approval, its own deadline and maybe its own invoice line, give it its own task and its own video code.
Why it matters more than filing tidiness
Comments belong to the version they were left on, and the comment box is locked on anything that isn’t the latest cut. Pile three unrelated deliverables into one task and their feedback stacks on one timeline, where a note about the vertical cut sits between two notes about the master.
Approval works the same way. A client approving a task approves what is in front of them, so if the 9:16 lives inside the master’s task, nothing in the history ever says the 9:16 was signed off.
The numbers follow the same split. The delivery email counts versions and resolved comments for that task, and Metrics counts finished tasks, so six deliverables hiding inside one task read as one video that took six times too long.
In practice
| Situation | Where it goes |
|---|---|
| Colour pass after the client’s notes | New version |
| Same cut, music replaced | New version |
| 9:16 cutdown approved separately | New task |
| 15-second teaser with its own deadline | New task |
| Same video, subtitled in another language | New task |
| Export fixed because the render failed | New version |
Let the upload help you
If you upload a file whose name resembles one already in the workspace, RecReview asks before deciding: Similar Versions Detected, with Add as Version 2 or Create separate project. Read that dialog instead of clicking through it, since it is the same question asked at the only moment when answering is cheap.
Tip: When two deliverables genuinely belong together but need separate progress, keep one task and use subtasks. Subtasks track work, versions track cuts, and tasks track approvals.
What’s next
Versions and comparison covers stacking cuts and playing two of them side by side.