How to organize a long fanfic (when you are 30 chapters in and counting)

By Brenn and Lindsay, the two writers who built Inkling

Your fic started as a one-shot. Now it is thirty chapters, the chapter count says ?, and a reader in the comments has just asked about a detail from chapter six that you no longer remember writing. You know canon by heart, but you are less sure what your own story has changed, who has been told the secret, and where it all ends. That is not a sign the fic got away from you. It is what happens to every long story, original or not, once it outgrows the writer's memory. Here is how to organize a long fanfic so you can keep posting with confidence, with a tracker you can copy.

First, the thing that should not need saying: fan fiction is real writing. A sixty-thousand-word fic with a slow burn, a subplot, three narrators and a weekly posting schedule is a novel-length project, and the people writing them are novelists who happen to be working in someone else's world. The organizing problems are the same ones any novelist has, with two extra layers: a canon you have to stay true to (or depart from on purpose), and readers who are reading along as you go. Here is how to handle both.

Name your divergence point

Every fic that changes canon has a moment where it stops following the source. Your heroine makes a different choice at a ball. A character who died in canon survives. Two people meet a book early. Write that moment down in one sentence, with the chapter or scene of canon it replaces. Everything before it, you can assume readers know. Everything after it, you have to establish.

This matters more than it sounds, because it tells you which canon events still bind you. If your fic diverges halfway through the second book, the events of the first book happened, and a character who learned something there still knows it. If your fandom's canon is still being written, decide your cutoff too. With A Court of Splintered Harmony published on October 27, 2026, and another book in the series due in January, ACOTAR writers are making exactly this choice right now: is the fic compliant with the new book, does it ignore it, or does it diverge before it? Pick one, write it in your notes, and say it in your author's note so readers are not surprised.

Keep a canon-facts sheet

A canon-facts sheet is a two-column list: what canon says, and what your fic changes. It sounds obvious, but most long-fic continuity errors come from mixing the two up, writing a detail from canon that your story already overturned, or forgetting a change you made twenty chapters ago. Keep it short and specific:

• Characters. Ages, relationships, who is alive, who is where at the divergence point.
• World rules. How the magic works in canon, and any rule your fic bends.
• Events. The canon events your fic keeps, the ones it removes and the ones it moves.
• Your inventions. Original characters, places and history you have added, with the chapter where each first appears.

Add a third column for the chapter where each change shows up on the page. When a reader asks about chapter six, you can check in seconds instead of rereading your own fic.

A chapter list with a posting schedule

Long fics are published while they are being written, which is a real difference from a novel, and it means your chapter list does double duty. It is your outline and your posting calendar. For each chapter, keep:

• a one-line summary of what happens;
• whose point of view it is in, if you rotate;
• its status: planned, drafted, edited, posted;
• the date it went up (or will go up).

Keep a buffer of two or three finished chapters before you post. It means a busy week does not break your schedule, and more importantly it means you can fix a problem you discover in chapter 31 while chapter 30 is still yours to change. Once a chapter is posted, changing it is possible but awkward, because readers have already read the old version. If you rotate between narrators, our guide to writing a multiple POV novel has a rotation tracker that works just as well for fic.

Track who knows what

This is the error readers catch fastest. A character reacts to a secret they were never told, or fails to react to one they learned ten chapters back. In fan fiction it is doubly tricky, because readers know what the characters knew in canon, and your divergence may have changed that. Keep a simple table: each secret or important fact down the side, each main character across the top, and the chapter where they learned it in the box. Our guide to tracking subplots covers the same idea for threads that run across a whole book.

Keep your drafts somewhere safe, off the posting site

AO3 is a wonderful archive for posting and reading. It is not a drafting tool, and it does not try to be. Its own posting and editing FAQ says saved drafts of works are deleted one month after they are created, recommends that you always keep a backup copy elsewhere, and suggests composing in another application and pasting the text in. Its Terms of Service FAQ adds that deleted content cannot be restored, even if you deleted it by accident.

So the safe habit is: draft somewhere you control, keep your own copy of every chapter, and treat the posting site as the place chapters go when they are finished. That copy is also what you will want if you ever revise the whole fic, move it to another site, or decide to rework it into something of your own. Our post on never losing your draft again has the ten-minute backup setup.

Plan the ending before your readers ask

At some point a reader will ask whether you know how it ends. It helps enormously if you do. You do not need a full outline, but by the time you are posting the middle, write down three things: the final image or scene, the last big turn before it, and what each main character has to decide or give up to get there. Long fics most often stall not for lack of ideas but because the writer has too many open threads and no fixed point to steer toward.

Once you know the ending, look back at your chapter list and ask which threads it resolves and which it leaves hanging. Close or cut the hanging ones on purpose. If you plot loosely, our guide on pantser vs plotter has a lighter way to plan an ending without killing the surprise for yourself, and stuck in the middle of a novel is for the chapters where the momentum goes.

Reader comments: enjoy them, do not obey them

Comments are one of the great joys of writing fic. They can also pull a story apart if you try to answer every request. A few ways to keep them in their place:

• Read for confusion, not for requests. If several readers misunderstand the same scene, that is useful information about the writing. If several readers want a different pairing, that is a sign they care, not a plot note.
• Keep the ending fixed. Once your ending is written down, a comment can change how you get there, but think hard before letting it change where you are going.
• Do not promise in replies. "Maybe!" is a kinder answer than a commitment you will regret in chapter forty.
• Note good ideas privately. If a comment sparks something, write it in your notes and decide later, away from the excitement of the comment.
• Protect your writing time. Reply when you have the energy. The next chapter is the best reply most readers can get.

A copyable fic tracker

Copy this into whatever you draft in and fill it as you go. It is deliberately short, because a tracker you update beats a perfect one you abandon.

FIC TRACKER

THE BASICS
Fandom / source:
Canon cutoff (what you are following, what you are ignoring):
Divergence point (one sentence, with the canon scene it replaces):
Pairing(s) and main characters:
The ending (final scene, last big turn, what each lead must decide):

CANON-FACTS SHEET
Canon says              | My fic changes            | First shows in ch.
------------------------|---------------------------|------------------
                        |                           |
                        |                           |

MY INVENTIONS (OCs, places, history)
Name / thing:              First appears in ch.:   Notes:

CHAPTER LIST
Ch. | One-line summary         | POV   | Status (planned/drafted/edited/posted) | Posted on
----|--------------------------|-------|-----------------------------------------|----------
1   |                          |       |                                         |
2   |                          |       |                                         |

WHO KNOWS WHAT
Secret / fact        | Character A | Character B | Character C
---------------------|-------------|-------------|------------
                     | ch.         | ch.         | ch.

OPEN THREADS (close or cut before the end)
-

IDEAS FROM COMMENTS (decide later)
-

BACKUP CHECK
[ ] Every posted chapter saved in my own copy
[ ] Buffer: ___ finished chapters not yet posted

Where Inkling fits

Inkling is a private drafting desk, and that is all it is for a fic writer. It does not import from AO3, it does not post anywhere, and it has no fan fiction features. When a chapter is ready, you copy it over to AO3 or wherever you post. What it gives you is a safe place for the drafts and the references to live together:

• Chapters in order. A story holds its chapters in order: number them, move them up and down and name them. Those titles carry into a Word export and, with Google connected, into a Google Doc export that gives every chapter its own tab, which makes a full backup of the whole fic easy.
• A Notes pad beside every chapter. Keep the canon facts that chapter depends on, the draft of your author's note, or a reminder of who knows what by now. Notes stay private and never go into exports.
• The Character builder. Want, wound, the lie they believe, fears, trait chips and a Notes field. It is useful for original characters, and for writing down how your version of a canon character differs from the source. Tie a character to the story and they appear in the Cast panel beside the page.
• The Storyboard. Give the fic its own board, put scene cards in rows (one per arc, one per narrator, or one per posting month) and link them with arrows. Export it to Word, a Google Doc or a PDF and each linked chain prints as its own numbered storyline. There are no tags or custom fields, so the rows are yours to arrange.
• A word-count goal. Set a goal with a deadline and the desk gives you a daily target, which is handy for keeping a posting buffer.

You get 14 days to experience the full writing desk, build worlds, and be creative. No card to start. During the trial you can start 3 stories, and after that Plus is $9 a month. If you stop, your desk goes read-only, nothing is deleted, and you can still export your chapters to Google Docs. And if you ever want to turn a fic into something of your own, our guide to turning fan fiction into an original novel picks up from here.

Inkling is an independent writing app. A Court of Thorns and Roses and its sequels are works by Sarah J. Maas, published by Bloomsbury. Inkling is not affiliated with, endorsed by, or sponsored by Sarah J. Maas or Bloomsbury.