How to Write a Previously-On Recap for a Serialized Audiobook

Serial fiction goes out a chapter at a time, and the audio version reaches people weeks apart. A reader who has lost the thread flips back four pages in ten seconds. A listener cannot. Scrubbing backward through an MP3 hunting for the scene where the lieutenant was introduced is unpleasant enough that most people keep listening and hope it comes back to them. A previously-on recap closes that gap. Here is how to write one for a serialized audiobook without it becoming a second job every week.

What the recap is doing in audio

The job is narrower than a summary. You are not catching a new listener up on the whole story. You are putting one returning listener back into the state of mind they were in when the last episode ended, so the first scene of this one lands.

That shows up in what you include. A summary is organized around what happened. A recap is organized around what the listener is about to need. If chapter nine opens on a betrayal by a character last seen two episodes ago being helpful, the recap needs that character and almost nothing else. Everything past that point dilutes the thing you wanted remembered.

The length that works, and the length that gets skipped

Thirty to sixty seconds is the range that holds up. At a normal narration pace that is roughly 80 to 150 words. It looks short on the page and it is close to the maximum a returning listener will sit through.

Going long has a cost that outlasts the episode it happens in. Once a listener has skipped past one recap, they have learned that recaps are skippable, and they will skip the one in episode fourteen you needed them to hear. A practical ceiling: recap the trailing two episodes, three if the gap between drops is long. Anything older is exposition, and it belongs inside a scene where a character has a reason to say it.

Write it from the listener's memory, not your outline

The common failure is writing the recap from your notes, which are complete and ordered and nothing like what a person remembers eleven days later. What survives is people, voices, and one or two images. Plot mechanics do not. Names sometimes do not either, because a listener has heard a name and never seen it spelled.

Two habits fix most of it. Reintroduce a character by role before the name, so "the harbormaster, Vale" rather than "Vale." It costs three words and rescues the listener who remembers the person and lost the name. And write the recap after drafting the next chapter rather than before, when you know which two threads that chapter actually leans on.

Give the recap its own voice

The recap sits outside the story, and the listener should hear that in the first second. In AudioProducer.ai, narration is assigned by speaker: you tag lines in the editor to a speaker, and each speaker gets a voice you choose from the Voices page, where you can preview candidates before committing. A recap in a distinct voice is a second speaker that your recap lines are tagged to.

Auto-Assign Characters is worth running on a chapter, but know how it behaves on this block. It keys off dialogue and attribution, so it finds people who speak and get named. Recap narration has neither, and it will be swept into your default narrator with the rest of the prose. Plan on tagging those lines by hand.

If the recap quotes an actual line from an earlier episode, tag that line to the original character's speaker rather than the recap voice. The callback then arrives in the voice the listener already has stored, which is why you quoted it. Per-line dialogue emotion is there if the original delivery mattered. On the wider casting decision, see choosing an AI narrator for serialized fiction.

Where it sits, and the pause that separates it

The workable order is recap, a real pause, the chapter label if you use one, then the story. AudioProducer gives you pauses at more than one level: a project-wide default under Edit Project, a per-paragraph override, and an inline pause you can place inside a line. The seam after the recap wants the per-paragraph override, noticeably longer than your default. A paragraph-length gap there reads as the recap continuing, and the listener spends the first line of the scene still in summary mode.

AudioProducer will not score that seam. Auto-Assign Sounds places effects the text itself implies, so it will catch a door or rain in your prose, but there is no way to lay a music bed under the recap the way a podcast would. If you want one, build the audiobook here, download the MP3, and add the bed in whatever editor you already use. AudioProducer exports MP3 and does not distribute, upload, or list your audiobook anywhere. For what goes on either side of the block, see chapter intros and outros and whether to read chapter titles aloud. If the serial is heading toward a full cast, serializing a novel as an audio drama goes further into that shape.

Keeping it cheap as the serial grows, and when to stop

The recap has to stay a five-minute job or it becomes the reason you miss a drop. Keep one running file with a single line per episode, written the day you publish it while the chapter is fresh: who moved, what changed, what is now hanging. Each week you build the recap from the last two lines instead of rereading your own book.

Recaps also have an end date. When the serial gets collected into an omnibus, a listener going straight through hears the same recap every forty minutes and it turns into an accidental running joke. Build the collected version without the blocks. Writing each recap as its own section from the start makes that a deletion rather than an edit, which matters at thirty episodes. Producing in chapter-sized units is what makes it practical, and making an audiobook chapter by chapter as you write covers that workflow. If the serial is already published as text, turning a web serial into an audiobook is the starting point.

You can test the seam cheaply. The free tier covers 1,200 words with no card, enough for a recap plus the opening page of the chapter after it, and that join is the part you cannot judge from the manuscript. Build it, cast the recap speaker, set the pause, and listen to the handoff. Paid plans start from $39.99/month. If you want a cloned voice for the recap, cloning requires your own material or documented consent from the voice owner.