Coming from Wiredrive: review and approvals

Where the Wiredrive review workflow lands: one link per cut, notes pinned to the frame, approvals that stay attached to the version they were given on.

Wiredrive's Projects side is where cuts went out for feedback and came back approved. That workflow moves to HoldFast review links, with one structural difference worth knowing up front: nobody you send work to needs an account.

Projects become review links

A review link is a page at its own address holding one cut or several, with your branding on it. You create it from an asset, decide who can open it, and send the address. There is no seat to assign, no invitation to accept, and no app to install. See How to send a video for review.

Control the door with a password, an expiry date, or an email gate, and turn a link off later without touching the asset behind it. See Password-protect a review link and Set a review link to expire.

Feedback lands on the frame

Comments are timecoded. A reviewer types at 00:01:14 and the note stays pinned to that second, so nobody has to write "around the middle" again. They can also draw straight on the frame to circle the logo sitting too low, and replies thread under the original note.

See Timecoded comments and annotations and Draw on the frame.

Approvals are per version

An approval attaches to the version it was given on, not to the asset in general. Upload a new cut and the earlier approval stays where it belongs, on the cut it actually described. That keeps the record straight when a client signs off on Monday and you deliver something different on Friday. See Collect approvals on a cut.

Version identity is the filename, never an invented ordinal. Whatever your file is called is what your reviewer sees, so the label in the browser matches the label in the edit suite. See How versions work.

Save your history before you move

This part applies wherever you are going. The sanctioned Wiredrive to MediaSilo migration is one way, and it does not carry over legacy presentations or asset-level approvals and comments. The assets travel; the conversation around them does not.

So while you still have access:

1. Export or capture the approval trail for anything a client might question later.
2. Save the comment threads on projects still in flight, or paste the outstanding notes into your own tracker.
3. Record what each presentation contained, so you can rebuild it wherever you land.
4. Pull down masters you cannot regenerate from your own storage.

None of that is an argument for a particular destination. It is the same advice for anyone leaving any platform: files usually survive a migration, and the history around them often does not.

What running review here looks like

• One link per cut, or one link holding several cuts for a single client.
• Reviewers open it, comment, and approve, with no account and nothing to install.
• New cut, same link: replace the version and the address you already sent keeps working. See Send a new cut without breaking the link.
• Everything stays in the project the asset lives in, so the feedback sits next to the work rather than in a separate system.