THE SHORT ANSWER
A live runbook should define actions at seven days, 24 hours, 60 minutes, during the stream and after close. Include platform and account, technical test, product and stock, offer and links, host and brand roles, disclosure, content boundaries, comment moderation, incidents, live metrics, replay rights and reporting. Give each checkpoint one owner and backup. During the stream, protect factual accuracy, user safety and experience rather than adding unapproved promises for short-term metrics.
Rehearse the full viewer journey
Test network, picture, audio, account access, product link, code, inventory sync, payment and support. Complete the real device journey from view to purchase.
Record delays, regional restrictions and backup links. Complex failures need conditions to stop sales or switch content.
Assign live roles and decision rights
Assign host, product expert, technical owner, moderator, inventory or offer owner and final decision maker. One person should not host, moderate and approve emergency claims simultaneously.
Prepare simple actions for price error, low stock, network failure, product fault and harmful comments instead of asking the creator to improvise.
Use live metrics for operational decisions
Monitor concurrent viewers, average view duration, clicks, cart actions, valid orders, inventory and technical errors. A temporary peak should not trigger an unplanned discount or extension.
YouTube frames live performance through appeal, engagement and satisfaction and recommends comparing the same format. Live data detects issues; final performance waits for stabilized reporting.
Close rights and orders after the stream
Save replay, cutdowns, comments, snapshots, cancellations and return window. Confirm replay term, editing and advertising rights, and offer end.
Review technical, content, audience, sales and support issues. Move high-priority actions into the next QuickKOL runbook instead of leaving them only in a summary.
Track concurrency, retention and actions together
YouTube live analytics includes concurrent viewers, chat messages and other live-specific signals. Do not report peak concurrency alone: a giveaway may produce a peak without product understanding or action. Align the stream timeline with first product appearance, demonstration, offer, Q&A and technical failures.
For a 60-minute live stream with 8,400 peak and 4,900 average concurrent viewers, 72,000 total views, 3,600 link clicks and 420 valid orders, label the correct viewer denominator for click rate; order rate by clicks is 11.7%. If audio fails for four minutes at minute 22, do not treat that interval as creator explanation performance.
Live campaign timeline
Assign owners and backups before going live.
| Stage | Key action | Record |
|---|---|---|
| T-7 days | Script, product, disclosure, technical rehearsal | Issues and owners |
| T-30 minutes | Access, links, inventory and backup network | Pass / blocked |
| During live | Timeline, incidents, Q&A and calls to action | Timestamps |
| T+24 hours | Snapshot, order reconciliation, asset archive | Final status |
CHECKLIST
Twelve checks before going live
Use this concise runbook in the pre-live meeting.
- Account and live access verified
- Primary and backup equipment work
- Product, price and inventory align
- Links, codes and UTM are tested
- Script beats and demo order are clear
- Disclosure appears at opening and key moments
- Prohibited claims and escalation path are clear
- Host, moderation and technical owners are present
- Incident and stop conditions are defined
- Recording, edits and rights are confirmed
- Analytics snapshot timing is scheduled
- Review meeting and owner are set
Sources and further reading
- 01YouTube Help: Analytics tips for live content
- 02Google Analytics Help: Custom campaign URL builders
External pages can change. Recheck platform rules, contracts and local law before launch.