---
id: guide-01
family: guide
pillar: P1+P4
title: The November Notebook — a small guide to writing a novel in a month with a life around it
slug: the-november-notebook
target_query: novel writing month
surface: site
proof_source: 04_produit_verite.md §2 (untitled capture, story bible/codex, %% notes, version history, daily plain-text export, trial); 06_expertise_ecriture.md §1-3 (vocabulary, structure concepts, five moments); McKee, Story (1997); Truby, The Anatomy of Story (2007); Vogler, The Writer's Journey (1992)
expires: 2026-11-30
words: 3305
status: draft
---

# The November Notebook

A small guide to writing a novel in a month, with a life around it.

Ten chapters, each short enough to read on a break and act on the same day. Read them in order, or skip straight to the one this week actually needs. None of them assume you have more time than you have, or more certainty about your book than you have either. Some of them are about the writing itself, and some are about the plain mechanics of getting words down and keeping them safe while a life keeps happening around you.

The long thing being written here is a novel, because November is a novel's month. The ten chapters don't especially care: an essay, a screenplay or a run of articles wants the same small habits, in roughly the same order.

## 1. The promise sentence

Before the first scene gets written, most people can already say what their book is about, the way you'd say it out loud to a friend who asked over coffee. Robert McKee calls the version of this that has to survive the whole draft the controlling idea: the story's meaning, stated as cause and effect, not a summary of events (Story, 1997). You don't need McKee's precision on day one. You need a working promise, one sentence naming what this book gives a reader that made them pick it up in the first place.

Write it down somewhere you'll see it again. Not to pitch anyone with it, just to hold the thread when you lose it, which you will, probably around week three. It will also be wrong, or at least incomplete, and that's not a sign you planned badly. A month in, you'll know things about your own book that you didn't know when you wrote the sentence, and it will need a second draft of its own. Writing a wrong promise sentence first is usually how you find the right one; very few people get it in one try, and nobody needs to.

A useful promise sentence names a value and a direction, not a plot. For a heist story, that might read: loyalty, pushed past its limit, breaks toward one side or the other. That's not what happens on page one, it's a claim about what the whole book is testing. Once you have a sentence like that, even a rough one, you get a fast way to check any scene: does it serve that claim, or does it just fill space between the ones that do.

## 2. Where a stray line goes

The idea that shows up on a train, in a queue, half asleep, doesn't arrive with a chapter number attached. It shows up as a line, sometimes half a line, and the only thing that matters in that instant is getting it down before it's gone. Any ceremony at all costs you the idea: opening the right document, deciding which folder it belongs in, deciding whether it's even good enough to keep before you've finished writing it.

This is what an untitled page is for. You open it, you type, you close it. No title to invent, no folder to pick, no judgment required. In Scrin, that blank page lives inside the same project as your manuscript, not in a separate notes app you'll forget to check. So the scrap you left on the train two weeks ago is already sitting where it belongs when you come back to it: not exported, not copied, not rebuilt by hand into the outline. Just there.

None of this depends on the scrap turning into anything. Most stray lines don't. The point of an untitled page isn't that every fragment earns its place in the manuscript, it's that you never have to decide that in the moment you're catching it. Deciding later, with the whole project in front of you, is a much easier decision to make.

Naming things too early is its own kind of procrastination, dressed up as organization. A folder called "ideas" still asks you to judge the idea before you've finished having it. An untitled page asks nothing at all, which is exactly the right amount to ask of something that showed up uninvited on a train.

## 3. Enough plan, not a full one

A working outline needs less than most people assume before they start one. Somewhere between five and twelve events, the ones you're fairly confident will happen, is usually enough to begin from. Fewer than that and you're guessing at everything as you go; a great deal more and you've quietly written a second draft's worth of decisions before the first draft exists.

Name three people while you're at it: whoever the story follows, whoever stands in their way, and one more who hasn't decided whose side they're on yet. John Truby argues that a real antagonist has to want the same thing as the protagonist, not merely block them, or the two of them are just walking past each other instead of fighting over something (The Anatomy of Story, 2007). Two people are rarely enough: a protagonist and an obstacle tends to collapse into a single mood rather than a conflict, since there's no one in the room to want something different out loud. The third person, undecided, gives the middle of the book somewhere to apply pressure that isn't just the antagonist pushing harder. Then write down an ending, even a rough or a wrong one, on the clear understanding that you're allowed to change it later. Christopher Vogler adapted a version of this arc from Joseph Campbell into the stages screenwriters now call the hero's journey: useful for noticing the shape a story is already taking, and genuinely dangerous the moment it turns into a checklist you're filling in instead of a book you're writing (The Writer's Journey, 1992). Treat the plan as a flashlight for a dark room you already own, not a contract you signed before you'd seen the room.

The three-act shape, situation, complication, resolution, tends to describe itself after the fact more often than it gets planned in advance. It's less a mold to pour a story into than a pattern that shows up once enough scenes exist for a shape to be visible at all: worth knowing it's there, not worth forcing a plan into thirds on day one just because the shape has a name.

The same goes for a beat sheet, in the tradition of screenwriting's save-the-cat method: a list of turns positioned at specific points in a book. It's the most mechanical of these tools, and the easiest one to misuse, because a list of positions invites treating it as a set of instructions rather than a set of things to watch for.

## 4. The real daily number

The tradition behind writing a novel in a month settled long ago on fifty thousand words as the finish line: short for a novel by most standards, long enough to feel like one. Divide that by thirty days and you land on roughly sixteen hundred and sixty, the number that shows up in every pep talk written for the occasion. It's arithmetic, not a rule, and it describes an average month for an average writer, a person who does not exist and whose week looks nothing like yours.

Your real daily number is the smallest one you can hit on a genuinely bad day, not your best day dressed up as a target. Some days you'll write four thousand words because a scene finally cracked open on its own. Some days you'll write forty, on a day you weren't sure you'd write at all, and that forty matters exactly as much, because it kept the habit alive. A few writers do better counting by the week instead of the day, since a week absorbs one bad Tuesday far more gracefully than a daily streak ever does. Either way, the number worth knowing about yourself isn't the one you hit when everything goes right. It's the one you can still hit when it doesn't.

A zero-word day still counts as a day you stayed in the project, as long as you open it and read the last page before you close it again. That's a smaller commitment than writing, and it keeps the thread warm for tomorrow, which is often the only job a bad day actually has. Nobody needs a chart of averages to know if they're behind. One number does the job: how many days out of the last seven did you show up at all. If that number is low, fix that first. The word count usually follows.

## 5. Four weeks, and what stalls in each

The first week mostly runs on its own fuel. New project, new momentum, the promise sentence still fresh enough to feel exciting rather than like a decision you're now stuck with. Almost nobody stalls here. The main risk in week one isn't stalling, it's polishing a paragraph you'll rewrite twice more before the book is finished, at the cost of the next scene you haven't started yet.

The second week is where the rest of a life reasserts itself, usually without any single dramatic event. A deadline at work, a kid who gets sick, one skipped morning that quietly becomes three. This is where the plan from chapter three earns its keep, because a plan on paper is much easier to return to than a feeling you've lost. This is also the week worth telling the people around you, plainly, that you're mid-project and the month is short, not a big announcement, just enough that a rescheduled dinner doesn't feel like a crisis to either of you.

The third week is where the middle gets long, past the point where the whole shape fits comfortably in your head. This is the moment a plan, or a wall of index cards you can step back and look at, earns its keep for a second time: not because it tells you what happens next, but because it lets you see the entire shape at once, which memory alone can no longer manage. McKee describes a story's tension as the gap between what a character expects and what actually happens (Story, 1997); the middle is usually where that gap needs the most deliberate attention, because it's also the part everyone, writer included, is most tempted to assume will coast along on its own.

The fourth week runs on fumes and momentum in roughly equal measure. The end is close enough to see, which helps enormously, and everyone involved is tired, which doesn't help at all. Lower the bar on quality here before you lower it on showing up; a rough scene written is worth more this week than a perfect scene postponed. If a scene refuses to come together, write the version where nothing goes wrong and move on. A working ending you can revise later beats a beautiful fragment that stops the month cold.

## 6. Day twelve

Ask enough people who've done this and you'll hear the same story, almost word for word: somewhere around the twelfth day, the gap between the plan and the actual week catches up with you all at once. It rarely feels like a crisis. It feels like an accounting problem, because it is one. The days you meant to write and didn't have quietly added up, and the number of words left now looks larger than the number of days left to write them in.

This is a scheduling problem, and it responds to scheduling solutions, not to willpower or to reconsidering the whole month. Recalculate a smaller, realistic number for the days that remain. Look plainly at which day this week is actually free, rather than which day should have been. Writers who finish the month aren't the ones who never fall behind partway through it. They're the ones who treat falling behind as a math problem to solve on Tuesday, not as evidence about whether they can write at all.

The math is small enough to do in your head. If you're at day twelve with fourteen thousand words instead of the twenty thousand a steady pace would suggest, the gap is six thousand words over eighteen remaining days, not six thousand words tomorrow. Written out like that, it usually stops looking like a wall and starts looking like a Tuesday with a slightly longer to-do list. None of this requires catching up to the original plan exactly. A month that ends at forty-four thousand words because day twelve got recalculated instead of ignored is a better month than one that ends at zero because day twelve got treated as proof the whole thing was a mistake.

## 7. The place where facts live

Every manuscript accumulates facts that have to stay straight over time: a character's eye color, the year a war ended in the story's history, which of two sisters is older. Practitioners call this running record a story bible, and it's easy to mistake for a folder of research, but it isn't the same thing. Research is what you gather before you know what you'll need. A story bible is what you've already decided is true inside the book, the kind of fact a careful reader would notice you getting wrong on page two hundred if you'd said something different on page forty.

Scrin builds this record as you write instead of asking you to maintain a second document for it. Mention a place or a person once with a link, and every later mention connects back to that same entry, so the detail you settled on early is one click away later, not a memory you're quietly trusting to hold for months.

The habit is worth building even without software to help: the moment you invent a name, a date, or a rule about how something works in your story, write it down somewhere you'll actually look again. A story bible isn't a sign of an overly organized mind. It's a hedge against the ordinary fact that nobody remembers, on page two hundred, every small decision they made on page forty. Genre fiction leans on this hardest, since a reader who catches a contradiction in a mystery's timeline or a fantasy's rules tends to say so, loudly and in the review. But every book has a version of this problem, even a quiet one: somebody's age has to add up, and a season has to match the one three chapters earlier.

## 8. Notes that never leave the draft

Some of what you type while drafting isn't for the reader at all. A reminder to fix a timeline error two chapters back. A question about whether a character would really say that line. A flag that this paragraph is a placeholder for a scene you haven't written yet and don't want to stop and write right now. These notes matter, and they don't belong in the manuscript anyone else will eventually read.

In Scrin, marking a note this way keeps it visible while you're writing and invisible everywhere else: it never appears in an export, and it never counts toward your word count. You get to leave yourself a note in the middle of a sentence without skewing your own progress tracker, and without stopping to decide whether the thought is important enough to interrupt the sentence for. Most of the time, it is; that's exactly why it needs somewhere safe to go that isn't the sentence itself.

This is a different problem from the comment feature in a word processor, which was built for someone else to read your margin notes, not for you to talk to yourself. A comment like that tends to leak into a shared file at the worst possible moment. A note meant only for you needs a place built with that one job in mind, not borrowed from a feature meant for an editor.

## 9. What "safe" means for a manuscript

A manuscript carries however many months of somebody's actual life inside it, the way a cut tree trunk carries every year it stood in rings, and what "safe" means for it is a specific set of facts, not a feeling you're supposed to have. It means two sessions working on the same scene don't overwrite each other: the changes merge, word by word, instead of one version simply winning. It means every version you mark along the way stays somewhere you can return to, so a regret from three days ago is exactly as recoverable as a regret from this morning. It means a plain-text copy of the whole project writes itself to your own disk once a day, automatically, in a format you could open and read with nothing but a text editor, whether or not the software that made it is still around.

The specific worry underneath most writers' caution is usually some version of three questions: is the text still there, which copy is the real one, does the tool actually follow my hand when I type fast. None of the answers above are a promise about how you should feel. They're a description of what happens, checkable the first time something goes wrong and you go looking for what you wrote yesterday.

It's worth naming what this isn't. It isn't a promise that nothing will ever feel uncertain, or that you'll never think twice about a file before you check it. It's a specific, testable set of mechanics, the kind you can verify for yourself on an ordinary Tuesday rather than take on faith on the day it would matter most. Most writers who've been doing this a while have already built some version of a safety net by hand: a copy here, a backup there, a habit of emailing a draft to themselves before closing the laptop. That instinct is a reasonable one. The point isn't to talk anyone out of it. It's to make the instinct unnecessary, by building the same caution into the place where the writing already happens.

## 10. What to do with 41,000 words on day thirty

Forty-one thousand words on the last day of the month is not fifty thousand, and it is also a novel with a beginning, most of a middle, and a writer who understands that book far better than they did thirty days earlier. That understanding is the actual prize the month hands you. The word count was only ever how you earned it.

Revision is a different job from drafting, and knowing which job you're doing at any moment helps more than any amount of extra willpower. Practitioners keep three passes separate on purpose: revision remakes choices, line editing remakes sentences, and proofreading corrects errors, and a manuscript that still needs new choices doesn't need new commas yet. Read what you actually have, not what you meant to have. Update the promise sentence from chapter one now that you know things about this book you didn't know when you wrote it. And decide, properly this time, the ending you're finally choosing instead of guessing at.

None of this requires starting over in December, and none of it requires the story bible or the version history you built in November to go anywhere either. They hold exactly what they held on day thirty: every fact you decided, every draft you marked, all still there, still yours, whenever you're ready to open the file again. A finished first draft and an unfinished one both eventually need the same second act: distance, then a clear-eyed read, then the slower work of turning a working draft into a book someone else will read. Forty-one thousand words gets you to that second act with less distance to make up than you'd think.

The month gave you a draft. What you do with it next is a longer, calmer project, and it starts whenever you're ready, on nobody else's deadline.

Try Scrin early — leave your email and we'll open the web version to you.