The dangerous part of making a fanfiction tracker is the moment you realize you can add another column. Obviously you need title and author. Then fandom. Then ship. Then tropes, word count, completion status, rating, date started, date finished, source, chapter progress, canon era, universe type, download status, reread count, emotional damage level, and whether you left a comment. Congratulations. You have invented a part-time cataloging position.
Start with the questions you ask
Do not choose fields because they look impressive in somebody else’s template. Choose them because they answer a question you genuinely ask. “Where did I stop?” needs chapter progress. “Which of my WIPs updated?” needs update state. “What was that one hockey AU where they fake-dated for tax reasons?” needs fandom, ship, and a memorable note. “How many words did I read this year?” needs word count and date finished, plus a firm opinion about how rereads count. If you never filter by rating, a rating column is decorative homework.
The minimum useful fic record
For most readers, six pieces are enough:
- Link. The source of truth and the quickest route back.
- Title. Because a row of raw URLs is a cry for help.
- Author. Essential when several works share a title or you follow a favorite writer across fandoms.
- Reading state. Try To Read, Reading, Caught Up, On Hold, Finished, and Dropped.
- Where you stopped. A chapter number or the simpler state “caught up.”
- One personal note. The detail that future-you will actually remember.
Story metadata such as word count and completion status can be useful, but it should not always be your job to type it. If a tool can read those details from the story page, let it. The minimum record is supposed to get you back to the fic and restore the important context, not qualify you for a library-science degree.
Fandom, ships, and the tags you will actually use
Fandom and relationship tags are among the best fields for finding something again because they map to how fic readers remember stories. The warning is tag sprawl. If you enter Steve/Bucky, Stucky, James “Bucky” Barnes/Steve Rogers, and sambucky? no wrong one across four records, your filter will not understand that those are supposed to be the same bucket. Pick one form and reuse it. You are not recreating AO3’s volunteer tag-wrangling system in a personal spreadsheet. You just need enough consistency that your past self does not sabotage your future search.
Multifandom readers may want one broad fandom field and one ship field. Readers who stick to one OTP can skip both and use the space for something more useful, like tone. A tracker can also become a private rec list for your exact moods, which is where trope tags shine. Keep the vocabulary small and personal. Maybe you want:
- fake dating
- identity reveal
- time travel fix-it
- hurt/comfort
- case fic
- 5+1 things
- “this will fix me”
- “this made me worse”
You do not need to reproduce every source tag. Save the handful that would make you choose this fic again. AO3 already holds the canonical tags, while your tracker should hold your memory of the work. For help getting more from the source system, our guide to AO3 tags and filters covers the useful distinctions.
Notes beat ratings
A three-star rating means almost nothing six months later. Was it competent but forgettable? Brilliant until the ending? Exactly your trope, written in a style you disliked? Five stars because you read it during a very specific week and it kept you alive? One sentence is better:
Great banter, weak mystery, reread when I need them being idiots in love.
That note can help you recommend the fic, decide on a reread, or remember why you dropped it. A number struggles to do any of those jobs. If ratings are fun for you, keep them, but do not mistake precision for memory. Our look at star ratings in web fiction goes deeper on why a single score compresses too much.
Let the tracker carry changing facts
Some fields are stable. Author and fandom usually stay put. Other fields decay the second you enter them. Chapter count, word count, last update, and completion status can all change while a WIP is active, which makes them the worst fields to maintain by hand and the best fields to let software watch.
Storywatch brings supported stories into one library, keeps current story details together, and shows unread chapters without making you revisit every row. Your custom shelves can hold the personal layer: comfort reads, Yuletide haul, terrifyingly long, Friday-night treat. That division works well. Let the source provide facts, let the tracker notice changes, and save your effort for the notes only you can write.
The urge to make every record perfect is how a useful list becomes a backlog, so add the link, mark the reading state, and write a note only when you have something worth remembering. You can always add a trope later when you find yourself hunting for it. The best fic tracker is not the one with the most metadata. It is the one that gets out of the way before the next chapter.