Your template planned it.Now the book can check it.

What Notion does well for writers

Notion is a flexible workspace of pages and databases. Writers use it to build a character database with a property for every trait, a board of chapters by status, a timeline of the world’s history, and a dashboard that links them all. Templates are easy to share, so many people begin a novel inside someone else’s planning system and adapt it as they go.

It is also good at the rest of a writer’s life: research clippings, a submissions tracker, a calendar for a newsletter. If you already run your days in Notion, putting the book there feels natural, and for planning it often works very well indeed.

Its sharing is good too: a co-writer can work from the same plan, and a page can be published to show a project to a writing group. Those habits carry over in a different shape here. Co-authors share the project live, and a published story gets reader pages of its own, chapter by chapter.

Where a database meets a draft

The trouble starts once the chapters are written. A character database records what you typed into its properties, not what the manuscript says. When chapter fifteen gives her a new title, a new ally and a reason to lie, the database won’t know until you go back and edit three properties. Multiply that by a cast of forty and the plan quietly stops matching the book.

Drafting long prose in a page tool has its own friction. A novel spread across dozens of pages is hard to read straight through, and moving a scene between chapters means opening two pages side by side. Neither problem is a flaw in Notion: it’s a general workspace, and a novel is a very particular kind of document.

A board has a limit as a check, too. It can show which chapters are drafted, but it can’t tell you that chapter nine contradicts chapter four, or that a promise from the opening has gone unpaid for twenty chapters. Those answers are in the prose, and only something that reads the prose can give them.

One place for the plan, the draft and the bible

In Authrot the plan isn’t a separate system beside the book. Arcs have a goal, an opposition, stakes and an outcome, chapters sit under the arcs they serve, and each chapter has a plan with the moments to land as a checklist. The Overview puts the logline, premise, arcs and chapters on one page, and shows whether the chapters are on track.

The bible is filled from the text. Read a chapter and its characters, places, items and events are recorded with every reference, and importance (main, supporting, minor, once) is worked out for you. The bible browser filters by kind and importance and sorts by story order, so the database view you once built by hand is there without the data entry.

Planning stays optional, and it doesn’t have to come first. There are eight ways to start a project, from a spark, a character, a genre starter or the premise dice to your existing draft or a blank page, and anchors lock any decision you have made so the Co-writer never redrafts it.

• Chapter status from idea to final, with a progress bar per book
• Story structures to plan against: three acts, the hero’s journey, 15 beats and more
• Kinds of entry of your own beyond the built-ins
• Reminders on an arc to bring a thread back at the right place

Moving your Notion pages

Export the pages you want from Notion as Markdown. Notion gives you a zip, and Authrot opens zips in your browser, so you can drop it straight into the import dialog. Pages arrive as sections you can send to the manuscript, the story bible, the outline or notes, and nested pages come across as folders, read in order. Notion adds an id to each file name, so check the titles in the review step; each one can be edited before you import.

A database comes out as a CSV spreadsheet, which the importer skips and lists, alongside a Markdown page for each row that has one. Those pages are read like any other, and a character page made of “Label: value” lines is recognized as bible material. Send it to the story bible and it becomes an entry, which chapter readings add to from then on.

Before importing, say what the files are: your manuscript, your notes and ideas, or both. For a planning workspace that answer matters, because a page of maybes filed as a chapter would have its guesses recorded as facts. Filed as notes they stay notes, and ✦ From your notes can later show where they fit in the story.

• Export as Markdown, then drop the zip
• CSV files are skipped; the pages are read
• Edit titles and check the reading order before importing
• Build bible entries with the AI, or keep the material as notes

When Notion is the better home

If the book is one part of a larger system (a newsletter, a course, a team wiki), or you mostly want a planning dashboard and draft somewhere else, Notion may suit you better. It is also more flexible: you can design any database you like, where Authrot gives you a set shape for books, chapters, plans and a bible.

Many writers keep Notion for their life admin and research and move only the novel. Nothing about the import is all or nothing: bring one book, or just its characters, and leave the rest where it is.