How to Structure Your Novel in Scrivener

You opened Scrivener for the first time, chose the Novel template, and stared at the Binder. There was a Manuscript folder with one Chapter folder inside it, and inside that, a single document called Scene. Below the Manuscript, a Characters folder with a template called Character Sketch. A Places folder with a Setting Sketch. A Research folder. Front Matter. And that was it.

That was the starting point. From here, somehow, you were supposed to build the architecture for an 80,000-word novel.

If you've been using Scrivener for a while, you probably remember this moment. The software had been described to you as a revelation, a writing environment that would transform how you think about your manuscript. And maybe it already has. But nobody warned you that the first real task wasn't writing. It was deciding how to organize. Folders or documents? One document per chapter or one per scene? What goes in the Research folder? Do you need labels? Status markers? Keywords? Custom metadata? How many of Scrivener's features do you actually need, and which ones will just slow you down?

Most Scrivener tutorials answer these questions by showing you which buttons to click. This article is different. It's about the why behind structural decisions, not just the how. What makes a good novel structure in Scrivener versus a mediocre one? What do experienced authors do differently from beginners? And what happens when you don't have the luxury of starting from scratch because your novel already exists as a flat Word document or Google Doc?

What the Novel Template Actually Gives You

Scrivener's built-in Novel template is deliberately minimal. Literature & Latte designed it as a starting point, not a finished framework. When you create a new project from the Novel template, you get a Manuscript folder containing a single Chapter folder with one Scene document. You get Characters and Places folders, each holding a basic template. And you get a Research folder where you can store anything that isn't the manuscript itself.

The Character Sketch template that ships with Scrivener asks for a handful of details: name, role in story, occupation, physical description, personality, habits, background, internal conflicts, external conflicts, and notes. It fits on less than one page. One forum user on Literature & Latte's community described the default sketches as "rather vague" and mentioned building a custom version that ran nearly forty pages when empty. Another writer on Quora called the built-in character sheets "abysmally inadequate," saying the whole setup process was too time-consuming for a working author producing a book a month.

These are not unusual reactions. The gap between what the template provides and what most novelists actually need is the first thing nearly every Scrivener user confronts. The template gives you a filing cabinet with one drawer and a sticky note inside it. Building the rest is your job.

This is by design. Scrivener's philosophy is flexibility over prescription. The software doesn't tell you how to organize your novel because every novel, and every author, is different. A contemporary romance with a single timeline and two point-of-view characters needs a different Binder structure than a multi-timeline epic fantasy with three magic systems and a cast of forty. The template gives you the skeleton. You grow the bones.

The problem, of course, is that growing those bones takes time. Setting up a properly structured Scrivener project for a full-length novel, with chapter folders, scene documents, synopses on every index card, character profiles in the Research folder, labels configured for your POV characters, and status markers tracking your revision progress, can take a full day or more. For a new Scrivener user still learning the software, it can take even longer. And if you're retrofitting an existing manuscript that you wrote in Word or Google Docs, the setup work multiplies.

The Three Ways to Build Your Binder

When you look at how novelists actually organize their Binders, three basic approaches show up over and over.

The simplest is one document per chapter. Each chapter folder in the Manuscript section contains a single text document with the entire chapter's prose. This is the approach that feels most familiar to writers coming from Word. You're essentially recreating a chapter-by-chapter structure, but now each chapter is its own clickable item in the Binder instead of a heading you scroll past. You can jump to any chapter instantly, drag them to reorder, and see the shape of your novel at a glance. For writers who compose linearly and whose chapters aren't particularly complex, this works fine. It's clean, it's easy to manage, and when you compile, it just works.

The second and most common approach is chapters containing scenes. Each chapter is a folder, and inside it, each scene is a separate document. This is the structure the Novel template hints at with its "Chapter > Scene" hierarchy, and it's the one most Scrivener guides recommend. The advantages are significant. You can rearrange scenes within a chapter without cutting and pasting blocks of text. You can move a scene from one chapter to another by dragging it in the Binder. You can view all the scenes in a chapter as index cards on the Corkboard, each with its own synopsis, and see the internal rhythm of that chapter at a glance. Author Simon K. Jones, who wrote about his process for the National Centre for Writing, described splitting his novel into seven major sections, each containing multiple chapters, and using this structure to see the macro pacing of the entire book from the Binder alone.

The third approach adds another layer: acts or parts above chapters. Your Manuscript folder contains Part One, Part Two, Part Three (or Act One, Act Two, Act Three) as top-level folders, and each of those contains chapter folders, and each chapter contains scene documents. This three-tier hierarchy is most useful for novels with distinct structural divisions, whether those are the traditional three acts, a four-part structure, or named sections like the ones Jones used ("Harbinger," "The Long Descent"). It's also the structure that makes your novel's overall architecture most visible. When you collapse the Binder, you see three or four major divisions. When you expand, you see chapters. Expand further, and you see scenes. The bird's-eye view is genuinely useful during revision.

No approach is objectively better than the others. What matters is whether your Binder structure matches how you think about your novel. If you think in chapters, organize by chapters. If you think in scenes, organize by scenes. If your novel has clear structural acts, use acts. The worst thing you can do is adopt a structure because a tutorial told you to, then fight against it every time you sit down to write.

Labels, Status, and the Metadata Layer You're Probably Ignoring

Most new Scrivener users focus on the Binder's folder-and-document hierarchy and never touch the metadata features. This is understandable. The Binder is visual and intuitive. Metadata sounds like something a database administrator cares about. But for novelists writing anything with multiple POV characters, subplots, or a revision process more complex than "read it once and fix typos," metadata is where Scrivener becomes genuinely powerful.

Scrivener's metadata comes in four forms: Labels, Status, Keywords, and Custom Metadata. Each serves a different purpose, and experienced authors use them in ways that are worth understanding.

Labels are the most visible. Each document in the Binder can be assigned one Label, and each Label has a color. When you turn on "Use Label Color in Binder" or "Use Label Color in Corkboard," your entire project lights up with color-coded information. The most popular use, by a wide margin, is tracking POV characters. You assign a color to each POV character (blue for Elena, red for Marcus, green for the narrator), and suddenly you can see at a glance how your viewpoints alternate across the novel. Are you spending five consecutive chapters in Elena's head while Marcus disappears for eighty pages? The colors make this obvious in a way that reading the manuscript never would. Gwen Hernandez, author of Scrivener For Dummies, has written that the Label field is her favorite piece of metadata precisely because of this visibility. Other authors use Labels for timeline tracking (present-day versus flashback), for revision status (first draft, revised, final), or for subplot identification.

Status is the second built-in metadata type. Like Labels, each document gets one Status value, but Status doesn't have colors. It's purely text: "To Do," "First Draft," "Revised," "Done," or whatever values you define. Writers typically use Status to track where each scene stands in their revision process. When you're editing a 30-chapter novel, being able to filter or sort by Status so you can see which chapters still need work and which are finished is the difference between organized revision and aimless scrolling.

Keywords allow multiple values per document, which makes them ideal for tracking things like which characters appear in a scene, which settings are used, or which thematic threads a chapter touches. You can create keyword hierarchies and search for all documents tagged with a particular keyword, which is invaluable during revision when you need to find every scene where a specific secondary character appears.

Custom Metadata goes further still, letting you create text fields, checkboxes, date fields, and dropdown lists attached to every document. Some authors track scene dates in a custom metadata field and use the Outliner view to see their novel's internal timeline laid out as a column. Others create a custom "Scene Purpose" field to force themselves to articulate why each scene exists in the story.

The common thread is that none of this metadata appears in your compiled manuscript. It's entirely for you, the writer. It's the organizational scaffolding that makes a complex novel manageable, and it's the layer that separates authors who use Scrivener as a fancy word processor from authors who use it as the project management tool it was built to be.

The Research Binder: More Than a Junk Drawer

The Research folder in Scrivener's Binder is the part most tutorials mention and most writers underuse. It sits below the Manuscript section and can hold anything: text documents, images, PDFs, web archives, audio files. Nothing in the Research folder gets compiled into your final manuscript. It's your private workspace, your reference shelf, your brain dump.

What experienced authors put there varies wildly, but a few patterns recur. Character profiles are the obvious starting point. Most writers outgrow the default Character Sketch template quickly and either build their own or download a third-party template with more depth. Shannon Thompson, an author of eighteen novels, has written about keeping a single document with all her characters outlined together rather than using Scrivener's individual sketch templates, because the connections between characters matter more to her than the individual details. Others, like the author at Scrivener Superpowers, maintain separate folders for Characters, Settings, and Research at minimum, adding more as needed.

Worldbuilding documentation lives here for fantasy and sci-fi writers. Maps, magic system rules, fictional calendars, political hierarchies, and cultural notes all go into the Research folder where they can be viewed in split-screen alongside the manuscript. One author described having 14,000 words of research material stored in this section before writing a single sentence of his novel. That's not unusual for speculative fiction.

Some writers store their story's structural analysis here too: beat sheets, act breakdowns, character arcs, and thematic notes. K.M. Weiland, author of Structuring Your Novel, uses a dedicated "Structure" folder within Research to hold notes on each major structural turning point. This approach turns the Research folder into something resembling a story bible, a reference document for the novel's own internal logic and design.

The key insight is that your Research folder should contain whatever you find yourself alt-tabbing out of Scrivener to look up. If you're constantly switching to a browser tab with your character notes, put those notes in Research. If you keep googling the layout of a real city your novel is set in, save the map in Research. If you have a timeline on a Post-it note stuck to your monitor, type it into a Research document. Every time you leave your writing environment to find information, you break your focus. The Research folder exists to prevent that.

Why Synopses Change Everything

Here is the feature that separates Scrivener users who love the software from those who merely tolerate it: the Synopsis.

Every document in Scrivener has an associated index card in the Inspector panel. You can write a brief synopsis on this card, and that synopsis becomes visible in the Corkboard view when you click on a folder. Suddenly, your novel isn't just a list of chapter titles in the Binder. It's a wall of index cards, each summarizing what happens in that chapter or scene, and you can see the entire shape of your story laid out in front of you.

This matters enormously during revision. Reading your manuscript straight through, you experience the story the way a reader would, one scene at a time, linearly. You can't hold the whole novel in your head at once. But the Corkboard with synopses gives you exactly that: the whole novel, visible at once, in summary form. You can see where your pacing sags because three consecutive cards describe low-tension conversation scenes. You can see where a subplot disappears because there's a fifteen-chapter gap between mentions. You can see that your second act is twice as long as your first.

One author who blogs about her process described writing synopses after the fact, since she's a pantser who doesn't outline. She writes each chapter, then goes back and writes a synopsis on its index card. Over time, this reverse outline becomes her revision roadmap. Another writer at the Scrivener Superpowers site described discovering a serious structural imbalance in his novel through the Binder: his male POV character had significantly fewer scenes and chapters than his female POV character, a problem he hadn't noticed while writing but that was immediately obvious in the Binder's visual structure.

The catch is that writing synopses is work. For a 30-chapter novel, you're looking at 30 summaries, each requiring you to step back from the prose and articulate what a chapter actually does in the context of the larger story. It's useful work, arguably some of the most useful revision work you can do. But it's also the kind of task that many writers skip, especially when they're eager to start revising the actual prose.

What Experienced Authors Do Differently

After reading through dozens of blog posts, forum threads, and process descriptions from published authors, a clear pattern emerges. The difference between a beginner's Scrivener project and an experienced author's project isn't the number of features used. It's the intentionality behind the structure.

Beginners tend to recreate Word in Scrivener. They import their manuscript as a single long document, or they set up chapter folders but never write synopses, never use labels, never touch the Research folder. They're using Scrivener as a word processor with a sidebar. It works, but it misses the point.

Experienced authors build projects where the structure itself reveals information about the novel. Joanna Penn, who has written over thirty books in Scrivener, keeps her projects simple but consistent: individual scene documents, daily backups via compile, and a research area for reference material. She uses the software for drafting and organizing, not formatting, and she's written openly about using only a fraction of Scrivener's features. That's the important insight. Mastery isn't about using everything. It's about knowing which features serve your specific workflow and using those well.

The author at Novel Smithy made a related observation: when he first started using Scrivener, he spent more time setting up his files than actually outlining his novel. The solution was building a custom template that matched his outlining process and reusing it for every project. Several other authors described the same trajectory. You spend too long setting up your first project, learn from the experience, and save a streamlined version as a custom template for the future.

Jen Terpstra, who created The Complete Novel Writing Template for Scrivener, built her template specifically because the default one felt too basic. Her template includes detailed character sketch templates, worldbuilding documents, a Save the Cat beat sheet structure, metadata for tracking scene data, and a manuscript folder pre-organized with act divisions. Over a thousand writers downloaded her free version, and five hundred purchased the paid version. The market for better Scrivener templates exists because the default template is a blank canvas, and most writers want something between a blank canvas and a paint-by-numbers kit.

The Retrofit Problem

Everything described above assumes you're starting a new project. You create a fresh Scrivener project, set up your Binder, and start writing. The structure grows organically alongside the story.

But what if you already have a novel?

If you wrote your manuscript in Word or Google Docs, which is the situation described in detail in our articles on switching from Word to Scrivener and switching from Google Docs to Scrivener, you face a different challenge. You can import your .docx file into Scrivener and use Import and Split to break it into chapter-level documents based on heading styles or separator characters. That gets your text into the Binder as individual chapters. But you get nothing else. No synopses on the index cards. No character profiles. No metadata. No labels. No status markers. Just your prose, divided into pieces, in a new tool.

Setting all of that up after the fact, for a completed 80,000-word novel, is genuinely tedious. You have to read through every chapter and write a synopsis for its index card. You have to create character documents from scratch. You have to decide on your label scheme, configure your status markers, and populate whatever metadata you want to track. For a 30-chapter novel, this is several hours of work at absolute minimum, and several days if you're doing it thoroughly.

This is why many authors who try Scrivener end up using it only for new projects. Starting fresh is easy. Retrofitting an existing manuscript feels like homework, and the longer the manuscript, the more homework there is. One forum contributor captured the problem perfectly: she described spending two days building an elaborate Scrivener template instead of writing. The setup is productive procrastination of the highest order, genuinely useful if you finish it, genuinely wasteful if you don't.

And yet the retrofit case is arguably where Scrivener's organizational tools matter most. If you've finished a draft and you're heading into revision, seeing your novel's structure from the outside, through synopses, labels, and metadata, is exactly the bird's-eye perspective you need. The irony is that the authors who would benefit most from a structured Scrivener project are the ones least likely to build one, because building it by hand from a finished manuscript is the worst possible version of the task.

Skipping the Setup

If the manual setup is the barrier between you and a properly structured Scrivener project, it's worth knowing that the barrier can be removed.

BinderCraft was built for exactly this situation. You upload your manuscript (DOCX, EPUB, or TXT), and within about seven minutes you get back a complete Scrivener 3 project file with your chapters organized in a three-act binder structure. But the structure is only the beginning. BinderCraft also reads your novel and generates a full story bible: character profiles with arc analysis and psychological depth, chapter synopses for every index card, a beat sheet mapped to your specific scenes, relationship arcs, a conflict matrix, worldbuilding documentation, and thematic analysis.

When you open the resulting project in Scrivener, it's not empty scaffolding. Every chapter has a synopsis on its index card. Your characters have detailed profiles in the Research folder. Your story's structure is documented and visible. You can switch to the Corkboard and see your entire novel summarized, card by card, without having spent days writing those summaries yourself.

It costs $9.99 per manuscript, takes about seven minutes, and requires no subscription. Your manuscript is processed in memory and deleted immediately — BinderCraft never stores, reads, or trains on your work. For anyone interested in what a story bible actually is and why it matters for revision, our companion article on story bibles covers that in depth.

BinderCraft doesn't write your fiction. It doesn't change your text. It analyzes what you've already written and gives you back the organizational infrastructure that makes Scrivener worth using, the infrastructure that most authors know they should build but never quite get around to building by hand.

Ready to skip the setup? Convert your manuscript for $9.99 — no subscription required.

Making Structure Serve the Story

The best Scrivener structure is one you stop thinking about. It's a system that lets you find any scene in seconds, see the shape of your novel without reading it, track your revision progress without a separate spreadsheet, and keep your research at arm's reach without leaving your writing environment. When the structure works, it disappears. You think about your characters, your scenes, your prose. You don't think about your software.

Getting to that point requires some initial investment, whether you build the structure yourself or let a tool build it for you. But the payoff compounds with every writing session. Every time you click on a chapter instead of scrolling through 300 pages, every time you glance at a color-coded Binder and see your POV balance, every time you check a synopsis card instead of rereading an entire chapter to remember what happens in it, you're reclaiming time and mental energy that belongs to the writing.

Structure isn't the enemy of creativity. It's the container that keeps creativity from spilling everywhere. And in Scrivener, more than any other tool available to novelists, the container can be as simple or as detailed as your novel demands.

The trick is to build it once, build it well, and then forget it's there. Get back to the story. That's the part that matters.