Revisions: who comments, how many rounds, where
Alex, 18 Sep 2026: "sometimes it's the creative strat that does the commenting, sometimes the AM, sometimes me or Junkai. Not very clear, not very clean. Internal revisions, someone does it, then external revisions up to two times for the client, strict, so we can track it closely."
The rounds
| Round | Who comments | Where | Outcome |
|---|---|---|---|
| Version 1, internal | Nigel only. If Nigel is on a shoot, the AM for that client, and nobody else. | Frame.io comments on the video or design | Editor uploads version 2 onto the same asset |
| Version 2, client round 1 | The AM relays the client's notes as Frame.io comments, in the client's words, one comment per change | Frame.io | Editor uploads version 3 |
| Version 3, client round 2 | Same | Frame.io | Editor uploads version 4. This is the last included round |
| Beyond version 4 | Nobody comments. The AM opens a ClickUp task "Change request" under the client and tells Alex or Junkai | ClickUp | Scope or price conversation before any further version |
Alex and Junkai do not comment on videos or designs. If they see something, they tell Nigel or the AM, who decides whether it goes in. One voice per round is what keeps a round a round.
Rules
- Every comment lives on the Frame.io version. Nothing about an edit is said in a ClickUp channel or a WhatsApp group; if it was, the person who saw it copies it onto the version.
- Every new version is uploaded as a new version on the same Frame.io asset, using Frame.io's versioning, never as a second file and never with a
v2in the name. The asset is named with the creative key only. The version count on the stack is the revision count, and it is what the portal reads. - Internal review happens within one working day of upload. Client rounds are sent the same day the internal pass clears.
- A brief change after v1 is a change request, not a revision, whoever asked for it.
- The editor moves the ClickUp task: In progress, Review (each upload), Done when the AM says the client approved.
What is measured, and what is not
Measured: versions per deliverable, days from task open to v1, days from v1 to approval. A deliverable at 4 or more versions is flagged on the editors sheet. Not measured, and not to be inferred: whose fault a revision was. A "Change request" task is the only thing that says the client moved the goalposts, so open one when they do; it protects the editor's record and the agency's margin.