Collect approvals on a cut

An Approve button on the review page turns "looks good" into a recorded decision, stamped to the exact cut it was given on.

The revision loop only really ends one way: a yes. Every review link that allows comments carries an Approve button under the player, so "looks good" becomes a decision the link records instead of a phrase buried three replies deep in a thread.

How a reviewer approves

Your reviewer clicks Approve under the player. The first time, HoldFast asks for their name and email so the sign-off has a name on it (no account, no login). The button turns green and reads Approved.

Screenshot: collect-approvals-1
One click under the player: Approve turns green and the decision is on record.

Clicking again removes the approval, so a client who spots something after the fact can honestly withdraw the yes, and you are told either way.

Approvals are per cut, per file

An approval is stamped to the exact version the reviewer was watching. Approve the current cut, upload a revision, and the new cut arrives unapproved: the yes stays pinned to the cut that earned it, which is precisely what you want on record.

On a link with several files, each one collects its own approval. "The hero is approved, the cutdown still needs work" is a state the link holds, not something you reconstruct from a thread.

Where you see the yes

The moment a reviewer approves, you get an in-app notification and an email naming the reviewer, the file, and the link. A ✓ Approved entry also lands in the comment stream, pinned to the approved version, so the paper trail lives with the feedback. Approval emails are capped per reviewer and file, so a client toggling the button does not fill your inbox.

Requesting changes

There is no reject button, by design. "Not yet" always comes with a reason, and the reason belongs on the frame it is about: a timecoded comment says what to fix and exactly where. Approval is the period at the end of that conversation.

Next steps

• Ship the fix on the same URL: Send a new cut without breaking the link.
• The reviewer-side walkthrough you can paste to a client: Approve a cut or request changes.