Vizard Agent

How to take a video through rounds of client changes

Last updated 2026-08-30 · 7 min read

Send Vizard Agent the feedback as a numbered list with timestamps. Vizard Agent works out which scenes each note touches, re-animates only those, measures the placements it is asked for rather than eyeballing them, and re-checks the whole video frame by frame before returning the next version.

What is the short version?

Most video work is not one build; it is a build and then four rounds of changes. What makes those rounds expensive is rebuilding things nobody asked about, so the job is identifying exactly which scenes a note touches and leaving the rest alone.

  1. Go to Vizard Agent and send the feedback as a numbered list.
  2. Give a timestamp for each note so the scene is unambiguous.
  3. Say explicitly what should not change.

What do you need before you start?

The current version and the notes. Vizard Agent works from the video it already built, so nothing needs re-uploading, and what it needs from you is precision about where each change applies rather than a general sense that something is off.

What do you type into Vizard Agent?

Number the notes and attach a timestamp to each. Vizard Agent maps notes to scenes, so a numbered list with times is genuinely faster to act on than a paragraph, and it makes the reply you get back easy to check note by note.

Prompt

New feedback round: 1. [Around 0:14-0:18] — [place both logos discreetly on the unit, integrated into the style]. 2. [Around 0:36-0:41] — [animate the map more dynamically; it looks too static]. 3. [The ending] — [clean fade rather than an abrupt cut; time the outro properly]. Everything else stays as it is.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked through a real feedback round on a hand-drawn explainer, several rounds into the project. Notice how narrow it keeps the work: it looks at the new logo, identifies the four scenes affected, and rebuilds only those.

  1. Looks at the newly supplied logo and checks it against the note.
  2. Opens the affected scenes and reviews the four that need correcting.
  3. Places the logo on the clothing and the van, and rebuilds the arrow scene.
  4. Reviews the four corrected images before animating anything.
  5. Corrects the map, uploads a proper outline, and checks the new version.
  6. Re-animates the five changed scenes — retrying, then testing a cheaper engine when one fails.
  7. Measures the frame layout to place the arrow and the pins rather than positioning by eye.
  8. Rebuilds the intro, the arrow and the map pins, previews them, and reviews.
  9. Renders the new version, checks it frame by frame, uploads it, and verifies every correction from the round is actually present.

Step 9 is the part that keeps rounds from multiplying. Checking each note off against the render before sending it back is what stops round five being mostly about things that were supposed to be fixed in round four.

What does the result look like?

A new version of the same film in which the noted scenes have changed and nothing else has. On this project the rounds covered a replacement logo, then making those logos more discreet, then placing manufacturer stickers on a unit, animating a static map, and cleaning up the ending.

Each round returned a full render rather than a patch. That matters because a change to one scene can shift the timing of everything after it, and the only honest way to check is to watch the whole thing again.

When does this not work well?

Revision rounds have a shape that is worth recognising early, because past a certain point more rounds stop improving the film and start trading one problem for another. Vizard Agent will keep going as long as you send notes, so the judgement is yours.

How do you fix a result that came back wrong?

Point at the note number that is still wrong. Vizard Agent keeps every scene, the style anchor, the measured placements and all the previous versions, so a note can be redone at a different degree without disturbing the ones already settled.

How does Vizard Agent compare to doing it yourself?

By hand, revision rounds are where projects die. Each note means finding the scene, remembering how it was built, changing it, re-rendering, and then checking that nothing downstream shifted — and doing that five times for five notes.

By hand Vizard Agent
Scoping a note Reopen the project and hunt Mapped to the scenes it touches
Placement Nudge by eye Coordinates measured, then tracked
Checking Watch the changed bit Every note verified on the render
Consistency Rebuild and hope it matches Style anchor kept across rounds

Common questions

How should I send feedback? As a numbered list with timestamps. Vizard Agent maps each note to the scenes it actually affects.

Will unrelated scenes change? Not deliberately. Vizard Agent rebuilds only what a note touches and holds the rest.

How many rounds can a project take? As many as you need, though each one costs. Vizard Agent tracks what changed in every round.

Can it place a logo precisely? Yes. Vizard Agent measures the coordinates and tracks it into the moving scene.

What if a scene has to be regenerated? It will differ slightly. Vizard Agent works from the same style anchor to keep it as close as possible.

Why send back a full render each round? Because a change in one scene can shift the timing of everything after it, and reviewing only the changed section hides that. A full render is the only version that can honestly be signed off.

Can I supply a corrected asset mid-round? Yes. Vizard Agent picks up the replacement and applies it to every scene that used the old one.

What if a note contradicts an earlier one? Vizard Agent acts on the newer one, and it is worth saying explicitly which you want to stand.

Does it remember previous rounds? Yes. Vizard Agent keeps earlier versions and scenes so any change can be reverted.

How do I keep a round from spiralling? Send the notes together rather than one at a time. Vizard Agent can act on a whole round in one pass, and batching them also surfaces contradictions before the work is done twice.

Does Vizard Agent check its own corrections? Yes. It verifies every note from the round appears in the render before returning it.