Observed Studio data
Start with a video-level Studio report, its review window, and the audience or traffic context instead of a guessed benchmark.
Turn an observed YouTube Studio audience-retention graph into timestamped notes, context, and one clear follow-up for the next edit or upload.
This free template does not connect to Studio or predict viewer behavior. It helps preserve the evidence behind one careful decision.
Free working template
Edit the fields from one observed Studio report, then copy the review into a production or experiment record.
Edit any field before copying. Nothing is saved, connected, or sent from this page.
A reviewable retention note
YouTube's key-moments report can surface useful places to inspect. A useful follow-up records what the viewer was promised, what changed at that moment, and what other context could explain the response.
Choose one published video and record the video-level report, review window, and filters before interpreting a graph.
Note the format, length, traffic source, viewer context, and comparable uploads so a difference is not treated as a universal rule.
Capture the timestamp, observed graph shape, and the video change worth inspecting. A graph is evidence to investigate, not proof of one cause.
Write one next change and the Studio context that will be reviewed after the next comparable upload or edit.
Start with a video-level Studio report, its review window, and the audience or traffic context instead of a guessed benchmark.
Record what changed in the video at an intro, flat section, decline, spike, or dip before assigning a cause to the graph shape.
Keep the title, thumbnail or first frame, opening, and payoff next to the retention note so the viewer promise is reviewable.
Choose one specific edit, opening, payoff, or packaging change, then record the comparable context for the next review.
Interpret before reacting
A dip can mark a skip or an exit. A spike can reflect more watching, rewatches, or shares. Those are useful prompts to inspect the timestamp, not evidence that one edit or audience condition produced the result.
Compare a video with uploads that share a meaningful format, length, traffic surface, audience context, and review window. Keep those details in the note before you carry an observation into a different topic or series.
Connected workflow
Record comparable Studio context, the original promise, observed response, and one controlled next test after publishing.
Open the performance reviewUse Virality Lab for separate paid pre-publish planning signals and connected-data retention comparison when available.
Explore Virality LabTurn the finding into an original audience, evidence, opening, packaging, and production brief before editing again.
Open the content briefQuestions
A YouTube retention review records what a video-level Studio report showed, what changes at the relevant timestamps, the viewer promise, and one follow-up worth testing. It keeps the graph attached to the format, audience, traffic source, and review window that make an observation interpretable.
YouTube describes dips as moments viewers skipped or stopped watching and spikes as moments with more watching, rewatches, or shares. Log the exact moment and investigate the surrounding video before deciding why it happened; the graph alone does not prove a cause.
Yes, as a record for the Studio context available for that Short. Keep Shorts-specific viewing context separate from long-form intro and retention comparisons instead of assuming the reports or viewer behavior are interchangeable.
No. This browser-only template does not connect to YouTube, read Studio data, save your notes, diagnose a graph, or predict recommendations, views, retention, or revenue. You enter and interpret your own observed context.
Official sources
This template organizes an observed review. Use YouTube's current documentation before relying on a report definition, graph label, comparison, or metric.