KadrentaAll chapters

Review

Review is where work gets judged. A version comes off a shot (or is uploaded straight in), it lands as a draft, your studio looks at it, and when you decide the moment is right it is published, so the people holding a link can see it, comment on it, draw on the frame, and approve it. Those are three separate acts: sending, publishing, and telling somebody. Nothing here happens by itself.

Two letters is enough, and it reads every chapter.

Tracks, rounds and versions

A shot's work travels through review on a track: one continuous conversation, either internal (your studio only) or client (the people outside it). The first time you send a shot's work anywhere, you are asked which. After that, every later version follows the same answer. A shot can end up with two tracks, an internal one and a client one, if it was sent both ways at different times, and the shot page always shows which review chains already exist, so you are never asked a question that has already been answered.

Each version you send opens a new round, and rounds are never overwritten. Round 2's approval never quietly covers round 3. The product never stops you from publishing a fourth round after three were agreed: going past what was agreed usually means something needed fixing, and it is never blocked. If your project has a number of rounds agreed with the client, the review page says where you stand against it ("Round 2 of 3 agreed") and, once you are past it, "Publishing is fine."

A round can be made from an upload with no shot behind it, or from a shot version. So review keeps two numbers apart: the round is the moment, the version is the work. A round's own count restarts at one on every new track. The version number shown beside it is the shot's own, so a shot whose only surviving upload is v005 shows exactly that, rather than a track counter that has restarted from v001.

Publishing is not sending

Send to review always lands as a draft, visible only to your studio. Nothing about it reaches anyone outside until you publish it. On the review item's own version, the button reads Publish this version (or, in the compact dock, Show), and confirms with a plain sentence: "Anyone holding a link to this review can see it from that moment. It does not send them anything."

Taking a round back is called Withdraw, and it asks nothing first. Showing unfinished work to a client is the risky direction; taking it back is not. So only one of the two directions interrupts you.

If a review is still internal, showing a version to the client moves the whole track over in the same press. The popup says so, because it is the heavier of the two things that press does. Publishing on its own is never offered on an internal track. The review has to be pointed at the client first, in that order, or a round could go straight back offline the moment it went out.

Sending a client a link is a further, separate act. Open The client's link, then People with a link. Everybody there holds their own address, and pressing Email link on a row puts it in their inbox; tick several and send the lot in one go. You can also copy a link and hand it over yourself. Nothing is mailed on its own, and correcting a typo and re-saving never mails your client twice.

Approving, and why there's no reject button

A client can only ever set one verdict: approved. There is no reject button. A rejection with no reason gives the studio nothing to act on, while being unhappy is exactly what a comment is for. Approving posts a visible comment of its own ("Approved v2.") so the decision is recorded in the conversation, not only in a hidden column nobody reads back.

A client's approval counts as an approval only while two things are both true: the round is published, and nothing newer has been sent since. A round somebody marked "approved" internally, before anyone outside had seen it, is not an approval the client gave. It is the studio agreeing with itself, and review never shows the two as if they were the same badge.

The dock: everything you might need beside the video

A collapsible rail beside the player is where every version of this review lives, grouped by round, newest first. Beneath it sits everything else in the project's other reviews, grouped by film. It is the same dock on the studio's own review page and on the client's share page, so a client's experience matches a colleague's. The two sides never see the same rows, though. What the dock shows is decided on the server, per side, before it reaches the page.

Switching between versions through the dock keeps your place on the page. The player swaps without a scroll jump, so you can be halfway down a page reading comments and reach over to compare against v001. There is no separate side-by-side comparison view. Comparing two versions means switching between their tiles in the dock, which stays open and keeps your scroll position while you do it.

Once a review has more than one round, a small chooser sits above the dock's own list so you can lift out one round at a time. It tells you how many rounds are hidden by the pick, so the filter never hides anything silently.

Comments, and drawing on a frame

Comments can be pinned to a moment in a video, and a drawing on the frame is part of the same remark rather than a separate thing. The moment a comment is pinned to is picked up the instant you draw a stroke or start typing, without you having to press anything first. Once you have pinned or cleared the moment yourself, nothing overrules you again.

Drawings are stored as plain coordinates (0–1 of the frame) and a name from a fixed set of ink colours. Never as an image, and never as a raw colour value. So a stroke survives being viewed on a different screen size, and nothing a stranger behind a share link submits can carry anything through beyond a list of numbers. A drawing only shows while the frame it was drawn on is on screen. While the clip is playing, or when the file itself cannot be shown (an unsupported video codec, say), a card says so rather than stretching the ink over whatever happens to be underneath.

Sending a round ahead of time

Beside the ordinary Send on a link's row sits Schedule the release, for when you want a round to go out, with the mail to go with it, at a specific future moment rather than right now. You pick a day and time, name who it goes to, and nothing is scheduled until you press the button. Nothing is pre-filled, so a release only goes out because somebody set it up for this review, these people, and this moment.

The decision is still made by a person, with a name and a moment attached; it is made ahead of the deadline instead of at it. It can be called off with one press right up until the moment it fires, and nothing goes out if the round has since been removed or the review has gone back to internal.