Core features

Understanding the checklist

How the AI-structured revision checklist is organized, including scope-creep flags.


The checklist is the AI-cleaned version of your client's feedback: short, actionable items, each with a timestamp and a category.

Grouping and order

Items are grouped by category, visual, audio, pacing, text, and ordered along the video timeline within each group. That means you can batch similar work instead of jumping around the cut.

Scope-creep flags: how NEW REQUEST is decided

Every checklist item is labeled either a fix or a NEW REQUEST. The AI makes that call item by item, from the wording of the client's note, using one rule: is the client asking to change something that is already in the cut, or asking for something that was not in the work you delivered?

  • New request: something that was not in the delivered cut. Examples: add new footage or B-roll, make an extra version or cut-down, deliver another format, or add new content such as a name, a social handle or a whole new section.
  • Fix: a change to something already in the cut. Examples: lower the music, trim the intro, correct a caption, smooth a transition, regrade a shot. Tweaks count as fixes, however many there are.

What the AI can see: the client's note plus the project and client name. It does not see your contract, brief or quote, so it cannot know exactly what you agreed to deliver. Treat the flag as a prompt to check, not a verdict.

Where the flag shows up: on the item card, in the suggested work order (fixes first, new requests last), and, on projects with a set number of included revision rounds, in the extra-round warning, which counts fixes and new requests separately so you have a clean record for a billing conversation.

Confidence

Low-confidence items, where the client was vague, are marked so you know which notes might need a quick clarification before you spend time on them.

Ready to try it? Start free no credit card.