Writing Tools

Notion for Novel Writers: A Complete Workspace Setup

You don't need another writing app. You need a command center. Here's how to build one in Notion that tracks every character, scene, and plot thread in your novel.

Somewhere around chapter eight, every novelist hits the same wall. You can't remember if the blacksmith's daughter was introduced in chapter three or chapter five. Your protagonist's eye color changed somewhere between the opening and the midpoint. The subplot you planted in Act One has vanished without payoff. Your manuscript is growing faster than your ability to track what's in it.

Notion fixes this. Not by replacing your writing tool (write your manuscript in Scrivener, Word, Google Docs, whatever you prefer), but by giving you a single workspace where every piece of your story's scaffolding lives in connected databases. Characters link to the scenes they appear in. Scenes link to the plot threads they advance. Plot threads link back to the characters they affect. Change a character's name, and it updates everywhere.

This walkthrough builds a complete novel workspace from scratch. By the end, you'll have four interconnected databases and a dashboard that shows your entire novel at a glance.

Why Databases, Not Pages

Most writers open Notion and start creating pages. A page for the protagonist. A page for the magic system. A page for Act One. This works until you have forty pages and no way to see the relationships between them.

Notion's databases change the game. A database is a collection of entries (called "items") that share the same set of properties. Think of it as a spreadsheet where every row can expand into a full page. You define the columns once (name, role, motivation, first appearance), and every new character entry inherits that structure.

The real power is in relations. A relation property connects two databases. Your character database can link to your scene database, so each character entry shows every scene they appear in. Your scene database can link to your plot thread database, so you see which threads each scene advances. These connections create a living map of your novel that updates as you write.

Pages are static. Databases are dynamic. For tracking a novel, you want dynamic.

Database 1: Characters

Create a new full-page database. Name it "Characters." Add the following properties:

Inside each character entry's page body, write the prose details: physical description, speech patterns, backstory, relationships. The properties handle the structured data you need to query. The page body handles the messy, generative material.

Set up three views of this same database:

Table view shows all characters with their properties in columns. Sort by First Appearance to see who shows up when. Filter by Role to see only your supporting cast.

Gallery view displays each character as a card. If you add cover images (character art, reference photos, even color swatches), the gallery becomes a visual cast list. Pin this view to your dashboard for quick reference during writing sessions.

Board view groups characters by a property you choose. Group by Faction to see who belongs where. Group by Status to separate living characters from dead ones. Group by Role to check whether your cast is balanced.

The Character View That Catches Mistakes

Create a filtered table view called "Underdeveloped Characters." Set filters to show entries where the Arc property is empty OR the Wound property is empty. This view surfaces every character you've added to the database but haven't fully thought through. If someone appears in twelve scenes but has no arc, that's a problem you want to catch before revision.

Database 2: Scenes

Your scene database tracks every scene in the manuscript. This is where Notion earns its place in your workflow, because scene-level tracking in a Word document or even in Scrivener's outliner gets unwieldy past fifty scenes.

Create the database with these properties:

Inside each scene's page body, write your scene notes: key beats, dialogue fragments, research details, revision notes.

The views that matter most:

Timeline view (Table sorted by Chapter number) shows your entire novel in order. Scan the Tension Level column. If you see five consecutive "High" scenes with no "Low" scene between them, your readers won't have room to breathe. If you see three "Low" scenes in a row in Act 2, that's where your beta readers will say the story drags.

Board view grouped by Act shows the distribution of scenes across your structure. Most novels need roughly 25% of their scenes in Act 1, 50% in Act 2, and 25% in Act 3. The board makes imbalances visible.

Board view grouped by Status tracks your progress. Drag scenes from "Outlined" to "Drafted" as you write. The shrinking pile of unfinished scenes is surprisingly motivating.

Database 3: Plot Threads

A plot thread is any narrative line that spans multiple scenes: the main plot, a romance subplot, a mystery that unfolds over the first half, a character's internal arc. Tracking these prevents the most common structural failure in novels: subplots that start strong and disappear.

Create the database with these properties:

The view you need most: a table filtered to show threads where Status is "Active" and Resolved is empty. These are your open narrative promises. Every thread on this list needs to close before your final chapter, or readers will notice.

Sort this filtered view by the Introduced column. Threads introduced early and still unresolved late in the book are either building toward a satisfying payoff or have been forgotten. The database won't tell you which. But it will force you to answer the question.

Database 4: Worldbuilding

If you're writing fantasy, science fiction, or anything with invented settings, a worldbuilding database prevents contradictions.

The page body of each entry holds the full description. The properties keep it queryable.

The "Established In" field prevents a specific problem: inventing a worldbuilding detail during revision that contradicts something you wrote 200 pages earlier. When you know exactly where each detail first appears, you can check for consistency before introducing changes.

Gallery view works well here, especially for locations. Add cover images (maps, reference art, mood boards) and the gallery becomes a visual encyclopedia of your world.

Connecting the Databases

The databases above reference each other through relation properties. Here's the connection map:

When you set up a relation in Notion, both databases gain a property. Link a scene to a character, and the character's entry automatically shows that scene. You only enter the connection once.

This network of relations is what makes the workspace more than a collection of lists. Open any character and see every scene they appear in, every plot thread they drive, and every worldbuilding element they're connected to. Open any scene and see which characters are present, which threads it advances, which world details it introduces. The connections reveal gaps that linear reading misses.

The Dashboard

Create a new page called "Novel Dashboard." This is your home base. Add linked views of each database, choosing the views most useful for daily reference:

Open the dashboard at the start of each writing session. Check your scene status board. Review which plot threads are active in the chapter you're about to write. Glance at the characters present in your next scene. Then close Notion and write. The workspace supports the manuscript. It doesn't replace it.

Fill Your Notion Databases with Story Structure

The 7 Essential Arcs gives you seven complete story structures to import into your Notion workspace. Map each arc's beats to your scene database and build your outline from proven patterns.

Get the 7 Essential Arcs

Free resource. One of 75+ storytelling frameworks on Loreteller.

Templates: Build Once, Use Forever

Every Notion database supports templates. These are pre-filled entries you create once and reuse every time you add a new character, scene, or worldbuilding entry.

For the character database, create a template with placeholder text in the page body: sections for Physical Description, Speech Patterns, Backstory, and Key Relationships. Every new character starts with this structure. You fill in the blanks instead of staring at an empty page.

For the scene database, create a template with prompts: "What does the POV character want in this scene?" "What goes wrong?" "How has the situation changed by the end?" These questions force you to define the scene's purpose before you draft it. Scenes without clear purposes are scenes that get cut in revision.

For worldbuilding entries, create templates by category. A location template might include sections for Geography, Population, Economy, History, and Sensory Details (what does it smell like, what do you hear, what's the light quality). A magic system template might include sections for Source, Cost, Limitations, Social Perception, and Known Practitioners.

Rollups: The Hidden Weapon

Rollups are a Notion property type that calculates data from related entries. They answer questions about your novel that would take hours to figure out manually.

Add a rollup to your Characters database that counts the number of related scenes. Suddenly you can see that your protagonist appears in 45 scenes while your antagonist appears in only 6. That's a story where the threat feels distant and abstract, because the reader barely encounters the source of conflict.

Add a rollup to your Plot Threads database that shows the chapters of all related scenes. Now you can see the distribution of each subplot across the manuscript. If your romance subplot clusters entirely in the first third and disappears after the midpoint, the rollup makes that visible without you having to reread the entire draft.

Add a rollup to your Scenes database that counts the characters present. Scenes with one character are introspection. Scenes with two are dialogue. Scenes with five or more are ensemble sequences. Scanning this column reveals whether your novel has enough variety in scene scale.

What Notion Can't Do (and What to Use Instead)

Notion is a planning and tracking tool. It is not a writing environment. The editor handles short-form content well, but it lacks the focus features, distraction-free modes, and manuscript management that long-form writing demands. Write your actual manuscript in Scrivener, Google Docs, or Word. Use Notion as the brain that sits beside it.

Notion also struggles with the kind of organic, associative linking that fiction brainstorming requires. If you want to type a character's name anywhere in your notes and automatically see every other mention, Obsidian handles that better. Notion requires you to manually create relations between database entries. The connections are more structured but less spontaneous.

Offline access remains a limitation. Notion caches recently viewed pages, but if you write at a cabin with no wifi (and you should, at least once), your planning workspace won't be available. Export your key reference pages to PDF before disconnecting.

A Workflow That Works

Here's the daily routine that makes this workspace useful rather than decorative:

Before writing: Open your Notion dashboard. Check the scene board for where you left off. Open the next scene's entry. Read your notes on its purpose, the characters present, and the plot threads it needs to advance. Close Notion.

During writing: Write in your manuscript tool. Don't switch to Notion mid-scene. If you realize you need a new character detail or a worldbuilding fact, jot a quick note in the scene entry after the session. Switching between tools during creative flow kills momentum.

After writing: Update the scene's status. Log the word count. Add any new characters or worldbuilding details you invented during the session. Link the scene to the relevant plot threads. This takes five minutes and keeps the workspace current.

During revision: This is where the workspace pays off. Filter your scenes to show only those in "Drafted" status. Sort by chapter. Read through the Purpose column. If three consecutive scenes serve the same purpose ("advance the romance subplot"), you have redundancy. If a scene's Purpose field is blank even after drafting it, that scene may not belong in the book.

The workspace is a mirror held up to your manuscript. It shows patterns you can't see while you're inside the prose. Build it, use it, and trust what it reveals.

75+ storytelling frameworks, organized by category, free forever.

Browse All Resources

or

No password needed. Just check your inbox or use Google.

Check Your Email

We sent a magic link to

Didn't get it? Check spam, or .