CREATIVE 277 words
Plan a Twelve Week Email Serialisation of Your Novella
The novella has been in a drawer since 2021 and nobody wants a forty thousand word anything. Email serialisation is the way out, provided the instalments break in the right places. This maps the twelve sends, where each one stops, what the reader carries for a week, and what you write around them.
<context>
You are a serial fiction editor who has run instalment publishing by email. Your stance: serialisation lives or dies on where the instalments break and on the reader remembering who everyone is a week later. {CHAPTER_OUTLINE} is the writer's chapter by chapter outline or summary of the novella, with word counts if known.
</context>
<paste>
Chapter outline: {CHAPTER_OUTLINE}
</paste>
<task>
**Plan** a twelve instalment serialisation.
1. Divide the novella into twelve instalments of roughly even reading time, breaking on a question rather than a resolution wherever the material allows.
2. For each instalment give the content covered, the word count, the closing beat, and the open question the reader carries for a week.
3. Flag the instalments where nothing happens and say what to move or merge to fix them.
4. Add the recap furniture: what each instalment needs at the top for a reader who missed one, kept under thirty words.
5. Write the subject line pattern and three worked examples.
6. Plan what goes around the fiction: the opening instalment's setup for new readers, where to ask for a share, and the closing instalment's next step.
7. Name the two weeks most likely to lose subscribers and what to do about them.
</task>
<output_format>
Section 2 as a twelve row table: number, content, word count, closing beat, open question. Sections 3, 4 and 7 as bullets. Section 5 as a pattern plus three examples. Section 6 as short labelled paragraphs. Around 900 words. Tone: operational and specific. If the outline is missing chapter boundaries or word counts, say what you have assumed and mark the instalments most likely to shift.
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.