How to get a register of every video in a project

Last updated 2026-09-04 · 7 min read

What is the short version?

By the end of a real project there are eleven files, four of them are supersedeed, two need a voiceover, and only one person knows which. A register is the document that stops that knowledge living in someone's head.

1. Go to Vizard Agent once the videos are made.
2. Ask for a register of every final version.
3. Say what each row should record, and ask for it as a page.

What do you need before you start?

Finished work and a sense of who reads the register. Vizard Agent already knows what it produced, so the only real decision is what a row should contain — and that depends entirely on whether this is your own note or a handover to a client.

• The finished videos. All versions.
• What a row records. Duration, link, status, script.
• What "done" means. Approved, or delivered.
• Any outstanding work. Voiceovers, captions, approvals.
• The format. A document, a page, or both.

What do you type into Vizard Agent?

Ask for the assessment, not just the list. A list of files is something you could get from a folder; the value is in the column that says what each video still needs before it can go out.

Prompt

Variants worth knowing:

• "And what it still needs." The column that earns the document.
• "As a clickable page." Easier to hand over than a file.
• "Mark the superseded ones." Otherwise everything looks current.

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in across a real multi-video project that ended with eleven deliverables. The register itself is the last thing built, and the checking of it afterwards is the part that makes the document worth handing to anybody.

1. Writes a content map document early, and uploads it.
2. Listens to the source clips to verify exact wording and names.
3. Records what each cut actually contains as it is made.
4. Keeps the off-limits list of material that may not be used.
5. Lists every real interview soundbite used in each reel.
6. Reviews its own footage region notes across the project.
7. Lists every final video with its duration and its link.
8. Writes and uploads the full register.
9. Checks how the register file is served.
10. Converts the register into a clickable web page.
11. Verifies that every link in the register exists.

Step eleven is the one that separates a register from a list. A document full of links that quietly 404 is worse than no document, because it looks authoritative — so every link is resolved before the register is handed over.

Step one is the other half, and it happens at the beginning rather than the end. A register assembled purely from memory at the close of a long project is a reconstruction; one built from notes kept as the work happened is a record.

What does the result look like?

A page listing every final video — duration, link, what it says, what it still needs — that someone who was not in the project can read and act on. Superseded versions are marked as such rather than sitting alongside the current ones looking equally finished.

The links work. That sounds trivial and is the single most common failure of handover documents, which is why it is worth asking for the check explicitly.

When does this not work well?

A register describes what actually exists at the end of a project. It cannot tell you what should have existed but never got made, and it is only ever as honest as the notes Vizard Agent kept underneath it while the work was happening.

• A project with no notes kept. The register becomes a guess.
• Files outside the project. It lists what it can reach.
• Approval status it was never told. Say who approved what.
• Very early in a project. There is nothing settled to register.
• Links that expire. Check the register again before you send it on.

How do you fix a result that came back wrong?

Say which row and which column is wrong rather than describing the document again. Vizard Agent keeps the register as structured data rather than as prose, so correcting one status or adding a whole column rebuilds the page without any of the other rows being rewritten.

• "That one is superseded." Marked, and moved down.
• "Add a column for approval." Added across every row.
• "This link is dead." Re-uploaded and re-verified.
• "Include the drafts too." Listed separately from the finals.

How does Vizard Agent compare to doing it yourself?

By hand, a register is a spreadsheet somebody starts in week one and quietly stops updating in week two. None of the information is hard to record on its own; the hard part is continuing to record it while the actual work of making the videos is still happening.

Common questions

When should I ask for it? At the end, though Vizard Agent keeps notes throughout either way.

Can it include drafts? Yes. Ask and Vizard Agent lists them separately from the finals.

Does it mark superseded versions? Yes, if you ask Vizard Agent to. Otherwise everything reads as current.

Can I get it as a spreadsheet? Yes. Vizard Agent produces a table as well as a page.

Will it say what is missing? Yes — that is the column worth asking Vizard Agent for.

Does it check the links? Yes. Vizard Agent resolves every one before handing the register over.

Can it include the scripts? Yes. Vizard Agent takes them from the transcripts rather than from the briefs.

What about the music licensing? Vizard Agent records what was used and where it came from.

Can it list what may not be used? Yes. Vizard Agent keeps the off-limits list in the same document.

Does it record who approved what? Only if you tell it. Vizard Agent cannot see approvals that happened elsewhere.

Can it flag the ones still waiting on me? Yes. That is usually the first thing anyone reads.

Does it work across several projects? One at a time, unless you point Vizard Agent at the others.

Can I add my own columns? Yes. Name them and Vizard Agent fills what it can.

Will it update the register later? Yes. Ask again and Vizard Agent rebuilds it from the current state.

Is this the same as a posting schedule? No. A schedule says when things go out; a register says what exists.

Why does the link check matter? Because a handover document nobody can follow is worse than none — it looks complete, so nobody checks.