Video Feedback Best Practices from Managing 6 YouTube Channels

TL;DR

ELBA Corp ran 6 YouTube channels and 140+ ad campaigns annually. They learned painful lessons about video feedback. This post distills 5 years of production experience into actionable practices: timestamp every comment, separate creative feedback from technical, batch review sessions instead of async chaos, use approval workflows instead of “looks good,” and measure revision metrics to improve. Real examples from ELBA’s channels (1min, ELBA Podcast, etc.) show what works.

Lesson 1: Timestamp Everything

The Problem: Feedback arrives like “The opening feels off” or “The color grade is weird.” Without timestamps, reviewers don’t know which opening (if there are two scenes) and which shots (the entire video is color graded).

ELBA’s Approach: Every piece of feedback must include a timestamp:

• “At 0:15-0:45, the pacing feels slow. Consider cutting to 25 seconds.”
• “Frame 1200 (around 1:42) has a focus issue. Can we re-shoot or use a different take?”
• “The background music is too loud from 2:00-2:30.”

Why it matters:

• Editor doesn’t have to watch entire video to find the issue
• Same issue is recognizable across versions (even if it moves to different timestamp, it’s about the same shot)
• Easier to track “did they fix it?” (just check the new timestamp to see if the issue is gone)

Tool-based approach: YouViCo forces timestamps. Comment on video → timestamp is auto-recorded. No way to submit vague feedback.

Lesson 2: Separate Feedback Types

The Problem: Comments come in all flavors:

• Technical (“Audio peaks here”)
• Creative (“The tone feels off”)
• Brand (“Doesn’t match our new brand guidelines”)
• Procedural (“We need a subtitle for accessibility”)

Without separation, creatives treat brand notes as creative suggestions (and resist them) or treat technical notes as optional.

ELBA’s Approach: Three feedback buckets:

Bucket 1: Technical (Must Fix)

Audio issues, color inconsistencies, video artifacts, sync problems.

Example: “Audio clipping at 2:15-2:30. Can we turn down the background track?”

→ These block approval. Video cannot move forward if it has technical issues.

Bucket 2: Brand/Compliance (Must Fix)

Brand guideline violations, legal requirements (disclaimers, claims substantiation), accessibility issues.

Example: “Legal says the health claim needs substantiation. Add a disclaimer: ‘Results not typical. Individual results vary.’”

→ These also block approval.

Bucket 3: Creative (Consider)

Tone, pacing, emotional impact, performance.

Example: “The opening feels slow. Consider cutting 5 seconds.”

→ Creative director has authority to override these. But they should consider them thoughtfully.

Implementation: YouViCo’s feedback types feature lets you tag comments:

[TECHNICAL] Audio clipping at 2:15
[BRAND] Color doesn't match Pantone 1234C
[CREATIVE] Opening feels slow, consider faster cuts

Clear labeling prevents arguments about “should we revise this?”

Lesson 3: Batch Review Sessions, Not Async

The Problem: Team uploads video Tuesday. Comments trickle in (Tuesday 2 PM, Tuesday 4 PM, Wednesday 9 AM, Wednesday 3 PM, Thursday 10 AM…). By the time all feedback arrives, creatives have already started revisions on incomplete information.

ELBA’s Approach: Formal review sessions, not continuous async feedback.

The schedule:

• Monday 5 PM: Rough draft uploaded
• Tuesday 2 PM: Review session (team + stakeholders watch together, take notes)
• Tuesday 3 PM: Feedback deadline (all comments submitted by this time)
• Wednesday morning: Creatives implement feedback
• Thursday 2 PM: Review session 2 (updated version)
• Friday: Final approval or another round

Why it works:

• Everyone sees the same version at the same time
• Live Q&A (“What did you mean by ‘tone’?” resolved in real-time)
• Feedback is concentrated, not scattered across days
• Clear deadline prevents endless commenting

The YouTube channel angle: ELBA’s 1min channel uploads 3x per week. They schedule review sessions:

• Monday review (Tues-Wed uploads)
• Wednesday review (Thurs-Fri uploads)
• Friday review (weekend uploads)

Consistency matters for creator teams.

Lesson 4: Use Approval Workflows, Not “Looks Good”

The Problem: Feedback includes “Looks good to me” comments. But “good” is ambiguous. Does it mean “approved” or “no major issues but I didn’t scrutinize”?

ELBA’s Approach: Explicit approval statuses:

Version 1.0
├─ Internal Creative Review
│  ├─ Creative Director: Approved
│  ├─ Sound Designer: Approved
│  └─ Color Grader: Needs revision (color timing issue)
├─ Overall Status: BLOCKED (color grader didn't approve)
├─ Next Step: Recolor, then re-submit
Version 1.1
├─ Internal Creative Review (repeat)
├─ Client Review
│  ├─ Client Brand Manager: Approved
│  ├─ Client Legal: Approved with notes ("Add disclaimer text")
│  └─ Client Procurement: Approved
├─ Overall Status: APPROVED with comments
├─ Next Step: Implement legal comments, then FINAL APPROVAL

Key insight: Approval is explicit, not implicit. “Looks good” doesn’t equal approval.

Lesson 5: Measure Revision Metrics

The Problem: ELBA doesn’t know how many revision rounds are typical. Are 3 rounds normal or excessive? Is their feedback process efficient or does it loop forever?

ELBA’s Approach: Track metrics:

Why it matters:

• Baseline expectations (new team members know “3 rounds is normal”)
• Improvement tracking (“Last quarter we averaged 3.5 rounds, now it’s 2.1 - we got better!”)
• Problem detection (“Wait, this video took 8 revision rounds? Why?”)

Tool-based tracking: YouViCo tracks these metrics automatically. Dashboard shows trends over time.

Real Example: ELBA’s 1min Channel

The 1min YouTube channel (shorts format, 30-60 seconds) is optimized for speed.

Process:

1. Script (Monday morning) - Uploaded to Google Docs
2. Feedback (Monday 2 PM) - CEO Juwon Gu reviews, leaves comments (timestamps + type tags)
3. Filming (Monday 3-5 PM) - Records 3-4 takes
4. Rough edit (Tuesday morning) - Uploaded to YouViCo
5. Review (Tuesday 2 PM) - Juwon watches, approve/revise
6. Revisions (Tuesday 3-4 PM, if needed) - Quick color grade, sound design fix
7. Final (Tuesday 5 PM) - Approved, scheduled for Wed upload

Cycle time: 24 hours from script to upload

Why so fast?

• Clear feedback types (Juwon doesn’t say “feels off,” he says “[CREATIVE] Pacing is 2 seconds too slow”)
• Timestamps (editor knows exactly what to fix)
• Approval workflow (not “Juwon likes it,” but explicit “APPROVED”)
• Regular cadence (team knows Tuesday 2 PM is review time)

For Your Team: Implementing These Practices

Week 1: Add Timestamps

• Train team: “Every comment must include HH:MM:SS”
• Use tool that enforces it (YouViCo does this automatically)
• Document in your review SOP: “Vague comments are rejected”

Week 2: Define Feedback Types

• Create 3-5 categories (technical, creative, brand, etc.)
• Document what goes in each
• Start tagging comments

Week 3: Schedule Review Sessions

• Pick 2-3 fixed review windows per week
• Communicate to stakeholders (this is when you submit feedback)
• Enforce deadline (no feedback after 3 PM Tuesday, period)

Week 4: Implement Approval Workflow

• Define approval statuses (approved, needs revision, rejected, approved with conditions)
• Train team on when to use each
• Track that each reviewer explicitly approves

Week 5: Measure

• Export data from your tool (YouViCo’s analytics dashboard)
• Calculate revision rounds, approval time, feedback volume
• Set targets for next month