Author's notes on serial platforms: the channel between chapters

The author's note is a form that belongs entirely to web fiction: a short block in the author's own voice attached to the chapter itself, published with it, read (or skipped) by the audience the chapter just held. Traditional publishing has no equivalent. There is no established channel in print where a novelist speaks to readers between installments; the note is a web-fiction-native author/reader relationship channel, and serial communities have settled conventions for how to use it.

Those conventions come out of author discussions on the platforms themselves, cited below. They are community norms, not rules any platform enforces, which is also why they are worth knowing: they describe what readers have proven they will tolerate.

The settled norm: after the chapter

End-of-chapter notes are the well-accepted convention, to the point of being invisible infrastructure. What they carry in practice:

• Commentary. A sentence or two on the chapter: what was hard to write, what it sets up, a joke the chapter did not have room for.
• Schedule announcements. The next chapter's date, cadence changes, hiatus news. When something breaks the schedule, say so here, say when you will be back, and come back then (see choosing a release schedule).
• Glossaries and recaps. For long serials with large casts, a pointer to character summaries and terms. The note can link the canon; it should not be where the canon lives, which is the story bible's job.
• Links. Patreon, Discord, the next book. Readers who just finished a chapter are the warmest audience these links will ever get.

Why after the chapter rather than before it? Because it does not sit between the reader and the story. The reader decides whether to read your note after the fiction has already delivered.

The contested edge: before the chapter

Pre-chapter notes are genuinely argued about in author communities, and both complaints recur: they can preview tone (a jokey note in front of a grim chapter lands wrong), and they can feel like a barrier between the reader and "the real content". If you use one, keep it short and structural: a schedule change, a content note, a translation credit. Save the commentary for the end.

What a note is bad at

• Apologizing. An apologetic note every chapter trains readers to expect less. If something went wrong, one plain statement and a date beats a running lament.
• Explaining the chapter. If the note has to clarify what a scene meant, the scene did not do its work, and the fix belongs in the scene, not under it. This is the same discipline as show, don't tell, applied to the author's own commentary.
• Spoiling your own future. Authors running advance chapters have readers at several points in the story at once; a note reacting to chapter forty events under a chapter thirty release splits the room. Write every note for the newest reader.
• Following a strong ending. A note placed directly after a hard chapter ending can blunt it. A beat of silence is a valid choice, and a strong ending with no note at all often lands harder than one followed by three paragraphs of chat.

A working pattern

1. Default to a short post-chapter note. Two or three sentences. A reader who finishes should feel the author is present but not lingering.
2. Link durable information, do not re-paste it. Schedule, glossary, Discord link: put them somewhere stable and point at them, rather than repeating the block every chapter.
3. Use the note when the schedule breaks. What happened, when you will return, then return then. A hiatus with a date is a schedule; a hiatus without one is an ending.
4. Skip the note when the chapter should end in silence. The note is a tool with an off switch, and the strongest chapters sometimes pull it.

None of this is enforced anywhere, and that is the point of the form. The note is the one channel where the author is a person rather than a text, and its conventions grew from what readers accepted. A short, honest, useful note builds that relationship; a long, anxious one spends it.