GoScript
Back to Blog
GoScript Journal

How to Read the Retention Curve on a Short Clip

·6 min read·GoScript Team /Editorial

The retention curve on a Short is a line that shows how many viewers were still watching at each second. It is the most useful graph the platform gives you, and most creators never zoom in far enough to use it. Read it as a sequence of decisions rather than a single score.

A dip is a person deciding to leave, and it happened because of something on the screen or in the voice. The curve turns writing into something measurable, which is rare in creative work and worth the trouble. I look at this graph before anything else on a clip that lost reach, because it answers the question the views number raises.

A flat line that never drops is the dream, and it almost never happens. What I want is a curve with no surprises in it, where every dip was something I could have predicted while writing. Surprises are the only part worth studying.

The three shapes and what they mean

A cliff at the very start means the hook missed. A long slide through the middle means a beat overstayed. A rise at the end means the loop is pulling people back for a second watch. Three problems, three different repairs.

I label the shape before I touch the script. If I mislabel a middle slide as a hook problem, I can rewrite the opening all week and watch the line keep falling. Naming the shape takes ten seconds and saves the rewrite, which is the whole reason to look at the graph at all.

The curve never lies about where attention died. It only stays quiet about why until you read the sentence beside it.

Matching dips to lines

I time every spoken line and write its start and end second in the margin of the script. When the graph dips, I check which line was running. The answer is almost always a line that repeats something, promises without delivering, or changes subject without warning.

This is why a transcript is worth keeping. The raw words with timestamps line up against the curve, and the culprit becomes visible instead of remembered.

The graph rewards patience with a specific fix. Vague notes like tighten the middle turn into the same clip with a few cuts removed, while a named line turns into a rewritten sentence. One of those two actually changes the number.

What a healthy curve looks like

  • A shallow drop in the first second, since some viewers always leave.
  • A near-flat middle where no single beat bleeds most of the audience.
  • A small rise or plateau at the end that suggests rewatching.
  • No sudden cliff that lands on a line you could not defend.

Use it before the edit, not after

I read the curve before opening the editor. Editing can mask a bad line with a cut or a sound effect, but a masked line is still there, and the viewer still left. Fixing the sentence is cheaper than covering it.

The curve also settles arguments. When a collaborator swears the middle is fine, the graph points at the second and the disagreement ends. I have ended more editing debates with a screenshot than with any explanation of why a beat felt slow.

Key takeaways

  • Zoom into the first seconds when a clip underperforms.
  • Name the shape of the curve before deciding on a fix.
  • Line up every dip with the sentence running underneath.
  • Repair the writing, not just the edit.

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel