A project scattered across six places is expensive — the cut on a file-transfer link, the script in someone’s personal Drive, the client’s notes in a voice message, the hours in the editor’s head. Nobody can say which cut is current without asking someone else.
RecReview works from one decision you make first: the task is the project. It is worth settling that with the team before you configure anything else, because every other decision here depends on it.
What belongs on the task
One deliverable gets one task, and everything about it lives there.
| What | Where it goes |
|---|---|
| Each cut | A version on the task |
| The script | Attached to the task |
| Client feedback | Time-coded comments |
| Internal direction | Team-only comments |
| Hours | The timer |
| The dates | Due and Internal deadline |
| The decision | The client’s approval |
The three leaks to close first
The first is the file sent on the side. Once you send a plain download link there are two current cuts in the world, and only one of them collects comments. Send the review link instead. Approving the video emails the client a download link anyway, so nobody needs the raw file early.
The second is feedback that arrives somewhere else. Clients will message you however they like, and arguing about the channel usually costs more than fixing it. Open the video, add their notes yourself as time-coded comments, and answer in the thread. Half a minute of typing gives your editor one list to work from instead of three.
The third is the decision taken on a call. “They approved it on the phone” leaves nothing in the history, so ask for the answer in the portal even when the call already settled it. It takes the client ten seconds, and it is what the delivery email and the metrics are built on.
Why the discipline is worth it
A new editor can open the task and find the brief, the script, the last cut and every note, without a handover call. When the producer who ran an account leaves, the account does not leave with them.
The numbers also stay trustworthy. Versions, resolved comments and hours only mean something if the work happened where they are counted, and those are the numbers your delivery email quotes back to the client.
Tip: The rule is easier to hold if it is easy to follow. Put the review link, never the file, in every message you send about a video, and people stop going looking for the file.
What’s next
Decide what a client, a project and a task mean in your studio: see How to split clients, projects and tasks.