Module 14 — Production Efficiency and Asset Management

Category: Professional Delivery | Duration: ~45 min | Prerequisites: Module 13

Learning Objective

By the end of this module, you will be able to establish a standardized folder structure, apply consistent filename conventions, manage asset versions and rejected takes, organize backups, resolve review comments, and package a completed campaign so that another editor can continue the work without verbal instructions.

1. Principle: Make Quality Repeatable

Rule: Any editor must be able to identify which script, prompts, generated clips, project file, and final export belong together — and continue the work without verbal instructions.

The folder structure, filenames, and documentation are as important as the creative work itself. If a new editor can't pick up your project and continue, you haven't finished the job.

The Standardized Workspace

/Campaign-ID_Book-Slug/
├── 01_Brief/
│   ├── campaign-brief.md
│   ├── creative-brief.md
│   ├── source-check-sheet.md
│   └── approval-email.pdf
├── 02_Source-Metadata/
│   ├── cover-approved.png
│   ├── book-metadata.md
│   ├── publisher-synopsis.txt
│   ├── author-bio.txt
│   └── license-docs/
├── 03_Scripts/
│   ├── BOOKSLUG_VIDEO01_SCRIPT_v01.md
│   ├── BOOKSLUG_VIDEO01_SCRIPT_v02.md
│   └── verification-log.md
├── 04_Storyboards/
│   ├── BOOKSLUG_VIDEO01_STORYBOARD_v01.md
│   └── shot-variety-check.md
├── 05_Symphony-Prompts/
│   ├── BOOKSLUG_VIDEO01_SCENE01_v01.txt
│   ├── BOOKSLUG_VIDEO01_SCENE01_v02.txt
│   └── prompt-revision-history.md
├── 06_Broll-Generated/
│   ├── BOOKSLUG_CONCEPT01_SCENE01_TAKE01.mp4
│   ├── BOOKSLUG_CONCEPT01_SCENE01_TAKE02.mp4
│   └── BOOKSLUG_CONCEPT01_SCENE01_TAKE03.mp4
├── 07_Broll-Approved/
│   ├── BOOKSLUG_CONCEPT01_SCENE01_TAKE02.mp4
│   └── BOOKSLUG_CONTINUITY-NOTE_S01.md
├── 08_Editing-Project/
│   ├── BOOKSLUG_VIDEO01_PROJECT_v01.gvid
│   └── asset-inventory.md
├── 09_Exports/
│   ├── BOOKSLUG_VIDEO01_MASTER_v01.mp4
│   ├── BOOKSLUG_VIDEO01_TIKTOK_APPROVED.mp4
│   ├── BOOKSLUG_VIDEO01_IGREELS_APPROVED.mp4
│   ├── BOOKSLUG_VIDEO01_YTSHORTS_APPROVED.mp4
│   └── BOOKSLUG_VIDEO01_THUMBNAIL_APPROVED.jpg
└── 10_QA-and-Approval/
    ├── BOOKSLUG_VIDEO01_QA-CHECKLIST_v01.md
    ├── BOOKSLUG_VIDEO01_QA-CHECKLIST_v02.md
    ├── reviewer-comments.md
    └── approval-status.md

2. Visual Demonstration

Professional Example — Well-Organized Workspace

/CAMPAIGN01_paramedic/
├── 01_Brief/
│   ├── campaign-brief.md      ← Complete, all fields filled
│   ├── creative-brief.md      ← 3 angles, selected angle justified
│   ├── source-check-sheet.md  ← All facts verified, gaps logged
│   └── approval-email.pdf
├── 02_Source-Metadata/
│   ├── paramedic_cover_approved.png
│   ├── book-metadata.md
│   └── license-docs/
├── 03_Scripts/
│   ├── PARAMEDIC_VIDEO01_SCRIPT_v01.md
│   ├── PARAMEDIC_VIDEO01_SCRIPT_v02.md  ← Revision after review
│   └── verification-log.md
├── 04_Storyboards/
│   ├── PARAMEDIC_VIDEO01_STORYBOARD_v01.md
│   └── shot-variety-check.md
├── 05_Symphony-Prompts/
│   ├── PARAMEDIC_VIDEO01_S01_v01.txt
│   ├── PARAMEDIC_VIDEO01_S01_v02.txt  ← Revision after take 1 rejected
│   └── prompt-revision-history.md
├── 06_Broll-Generated/
│   ├── PARAMEDIC_C01_S01_TAKE01.mp4  ← rejected
│   ├── PARAMEDIC_C01_S01_TAKE02.mp4  ← approved
│   └── PARAMEDIC_C01_S01_TAKE03.mp4  ← rejected
├── 07_Broll-Approved/
│   ├── PARAMEDIC_C01_S01_TAKE02.mp4  ← copy of approved
│   └── PARAMEDIC_CONTINUITY-NOTE_S01.md
├── 08_Editing-Project/
│   ├── PARAMEDIC_VIDEO01_PROJECT_v01.gvid
│   └── asset-inventory.md
├── 09_Exports/
│   ├── PARAMEDIC_VIDEO01_MASTER_v01.mp4
│   ├── PARAMEDIC_VIDEO01_TIKTOK_APPROVED.mp4
│   └── PARAMEDIC_VIDEO01_THUMB_APPROVED.jpg
└── 10_QA-and-Approval/
    ├── PARAMEDIC_VIDEO01_QA-CHECKLIST_v01.md
    ├── reviewer-comments.md
    └── approval-status.md

Why it works: Every file is traceable. Version numbers are sequential. Rejected takes preserved. Continuity notes written. Review comments tracked. Another editor can pick up any folder and continue.

Weak Example — Disorganized Workspace

/my-videos/
├── video.mp4
├── script.txt
├── cover.jpg
├── takes/
│   ├── take1.mp4
│   ├── take2.mp4
│   └── take3.mp4
├── final_final.mp4
├── final_final_REALLY_FINAL.mp4
├── notes.txt
├── comments.docx
└── stuff/
    └── (random files)

Why it fails:

• No folder structure (everything in one directory)
• No naming convention (generic names like "video.mp4")
• Version confusion ("finalfinalREALLY_FINAL")
• Rejected takes not documented
• No continuity notes
• No review comments tracked
• Another editor would need verbal instructions

3. Filename Convention

BOOKSLUG_CONCEPT01_SCENE03_TAKE02.mp4

Export Files

BOOKSLUG_VIDEO01_MASTER_v01.mp4
BOOKSLUG_VIDEO01_TIKTOK_APPROVED.mp4
BOOKSLUG_VIDEO01_IGREELS_APPROVED.mp4
BOOKSLUG_VIDEO01_YTSHORTS_APPROVED.mp4

Script and Document Files

BOOKSLUG_VIDEO01_SCRIPT_v01.md
BOOKSLUG_VIDEO01_STORYBOARD_v01.md
BOOKSLUG_VIDEO01_QA-CHECKLIST_v01.md

4. Common Mistakes and Corrections

5. Version Control

Step-by-Step Workflow

1. Check the naming convention — verify your filenames match the patterns above
2. Version all scripts and documents — keep every revision

Every revision gets a new version number:

• v01 — Initial draft
• v02 — After Module 05 review
• v03 — After stakeholder feedback

Rejected-Take Handling

1. Keep all rejected takes in 06_Broll-Generated/
2. Document why each was rejected in 05_Symphony-Prompts/prompt-revision-history.md
3. Move approved takes to 07_Broll-Approved/ (copy, don't move)
4. Write a continuity note for each approved scene

Asset Reuse

Before generating new B-roll:

1. Search 07_Broll-Approved/ for reusable assets
2. Check if an existing take can serve the new scene (with different prompt parameters)
3. Document reuse in the prompt log
4. Never overwrite a take that's already approved

6. Backup Discipline

Backup Rule

Three copies, two locations, one offsite.

Every production workspace must exist in:

1. Local project folder (your working copy)
2. Shared team drive (for collaboration)
3. Cloud backup (for disaster recovery)

What to Back Up

• ✅ All source metadata and approved covers
• ✅ All scripts and storyboards
• ✅ All prompt text and revision history
• ✅ All generated and approved B-roll
• ✅ All editing project files
• ✅ All exports and platform versions
• ✅ All QA checklists and reviewer comments
• ❌ Do NOT back up: temporary renders, cache files, system files

7. Review Comment Management

Comment Tracking

## Reviewer Comments — VIDEO01

| Comment ID | From | Date | Description | Status | Resolution |
|------------|------|------|-------------|--------|------------|
| R01 | Reviewer-J | 2026-10-20 | CTA too aggressive | OPEN | — |
| R02 | Operator | 2026-10-21 | Caption timing on S03 | RESOLVED | Adjusted timing, re-exported |

Resolution Protocol

1. Read every comment — no comment skipped
2. Categorize — critical (must fix) vs. suggestion (consider)
3. Assign an owner — you or the reviewer
4. Document the resolution — what was changed and why
5. Mark status — OPEN → IN PROGRESS → RESOLVED → VERIFIED
6. Get sign-off — reviewer confirms resolution

8. Quality Gate — Package Completeness

Before declaring a campaign "packaged":

• [ ] All 10 folders present and non-empty (where applicable)
• [ ] All filenames follow the convention
• [ ] All versions are sequential (v01, v02, ...)
• [ ] All rejected takes preserved with rejection notes
• [ ] All approved takes copied to 07_Broll-Approved/
• [ ] Continuity notes written for each approved scene
• [ ] Project file saved and linked to source assets
• [ ] All platform versions exported and named correctly
• [ ] QA checklist completed and passed all four gates
• [ ] Reviewer comments resolved and signed off
• [ ] Approval status documented

9. Hands-On Exercise

Package the completed campaign from Module 08–13 (the construction-disputes video) so that another editor can continue the work without verbal instructions.

Requirements

1. Create the 10-folder structure exactly as shown
2. Move/rename all files according to the filename conventions
3. Write continuity notes for at least 3 approved scenes
4. Document 2 rejected takes with reasons
5. Create the asset inventory in 08_Editing-Project/
6. Track 3 reviewer comments with resolution status
7. Document backup locations

Deliverable

A complete Campaign-ID_Book-Slug/ folder structure with everything an editor needs to pick up and continue.

10. Assessment

Scored assessment (30 points total):

Pass threshold: 25/30

Submission Requirement: Submit the folder structure listing (file tree), the continuity notes, the rejected-take documentation, the asset inventory, and the reviewer comment log.

11. Weekly Credit Budget for TikTok Symphony

Use these planning assumptions supplied by the course owner:

• Weekly TikTok Symphony allowance: 400 credits.
• Initial batch: 15 videos.
• Assumed initial generation cost: 10 credits per video.
• Initial generation allocation: 150 credits.
• Reserved correction allowance: 250 credits.

Verify the actual balance, current allowance, and per-generation cost before starting. The 400-credit allowance and 10-credit cost are planning inputs and must not be presented as independently verified platform guarantees.

Credit Arithmetic

• 15 x 10 = 150
• 400 - 150 = 250

Credit Tracking

Track all of the following:

• Opening balance.
• Initial generation allocation.
• Actual generation expenditure.
• Corrections and regeneration expenditure.
• Remaining balance.
• Outstanding corrections.

Use remaining credits for necessary visual corrections and failed generations. Fix text, narration, timing, and assembly errors in the editor when possible rather than unnecessarily regenerating footage. Prioritize factual accuracy, narration relevance, and unusable visuals over cosmetic experimentation.

Never exceed the verified available balance or silently assume that failed generations receive refunds.

12. Standard 15-Video Batch Workflow

The standard production unit is one batch of 15 videos. Do not invent a new process for each video.

1. Select and verify the book's metadata and source material.
2. Prepare all 15 video briefs together.
3. Assemble the entire approved production brief in a Google Doc before generating the videos.
4. Generate the corresponding vertical B-roll using TikTok Symphony.
5. Import the document into Google Vids and edit the automatically generated material into the intended videos.
6. Replace incorrect automatic narration with the approved voiceovers.
7. Assign multiple suitable voices across the 15 videos.
8. Perform final quality assurance on every export.
9. Release only videos that pass all acceptance checks.

13. Deliberately Faulty Example: Voiceover Does Not Match Visual

A 10-second video for A Siren Sings shows attractive storm footage while the voiceover claims an unsupported plot event. The footage is generic and does not support the narration.

Detection and rejection:

1. Compare the footage and narration against the master brief.
2. Reject the video for factual and relevance defects.
3. Set status to FAILED / CORRECTION_REQUIRED.
4. Correct within the credit reserve and re-run all 12 release checks.

Downloadable Resources

• Asset Organization Checklist
• Production Report Template
• Batch Production Template