Writva
Register
Guide

How to edit a book from structure to sentences

The short version: leave the draft alone long enough to read it as a stranger, decide what the book is actually for, then edit in passes from the largest decisions to the smallest — structure before chapters, chapters before paragraphs, paragraphs before sentences, and proofreading last of all.

Put distance between writing and editing

While a draft is fresh you cannot read it. You read your intention instead — the chapter you meant to write sits on top of the one you wrote, and your eye slides over the gap. Every writer believes they are the exception. None are.

Distance is what makes editing possible, and time is the cheapest way to buy it. Failing that, change the conditions: read it in a different typeface, on a different device, printed, or out loud. Anything that stops your brain autocompleting from memory.

Decide what the book is trying to do

Before changing anything, write down — in a sentence or two, for yourself — what this book is for and what a reader should come away with. Not the blurb. The honest version.

Every later decision depends on it. “Should this chapter stay?” is unanswerable in the abstract and straightforward once you know what the book is doing. Without that sentence you will spend the revision improving individual chapters while the book stays the same shape.

If you cannot write it, that is the finding. The revision starts there rather than in chapter one.

Edit in passes, not all at once

Trying to fix everything on one read produces a manuscript edited unevenly: the first chapters polished to a shine, the last ones barely touched, and structural problems untouched throughout. One kind of problem per pass.

  1. Pass 1 — Purpose and reader promiseWhat is this book for, and what does it promise a reader?
  2. Pass 2 — StructureDoes the shape of the book serve that purpose? What is missing, and what should go?
  3. Pass 3 — Chapter or section functionWhat is each chapter for? Does anything do the same job twice?
  4. Pass 4 — Flow, argument or sceneDoes the thread hold in order — the reasoning, the tension, the explanation?
  5. Pass 5 — Paragraphs and sentencesOnly now: the prose, one section at a time.
  6. Pass 6 — Facts, continuity and citationsNames, dates, timelines, quotations, sources, numbers.
  7. Pass 7 — Read-through and outside reviewRead it whole, in order, then give it to someone who is not you.
  8. Pass 8 — ProofreadingTypos and mechanics, on text you are no longer changing.

The exact process varies by genre. A thriller’s structural pass is about escalation and information order; an academic book’s is about whether the argument survives its own evidence; a memoir’s is often about what to leave out. Adapt the passes. Keep the direction of travel.

Working from the top down

The structural pass is the one writers skip, because it is the one that can cost you months of work. Read the manuscript with a notebook and change nothing. Note what each chapter does, what is missing, what arrives too late, and what you kept only because it was hard to write. Then decide before you edit a word.

The chapter pass asks one question of each chapter: what is this for? If two chapters give the same answer, one of them is doing nothing — merge them or cut one. If a chapter has no answer, that is not a prose problem you can fix with better sentences.

The flow pass is where you follow the thread in order: does the argument earn each step, does the tension rise, does the explanation introduce things before it needs them? Problems here are almost always about sequence, not wording.

The sentence pass comes last because it is the only one whose work survives being cut. Do it on text that has earned its place.

A worked example

From The Fog Line, a fictional mystery novel, used here to show the difference between a structural edit and a sentence edit.

The problem, found in the structural pass

In chapter nineteen the detective realises the ferry timetable is the key to the alibi. It lands flat with readers. Reading the whole manuscript in order, the author sees why: the timetable is mentioned once, in chapter four, as scenery — a poster on a wall nobody looks at. The reader has no reason to have retained it, so the reveal arrives as an assertion rather than a click.

The tempting fix — and why it fails

The obvious move is to rewrite the reveal so it explains itself more clearly. But the reveal is not unclear; it is unearned. Explaining it harder makes the detective sound like she is addressing the reader rather than solving a case, and the scene gets worse the more it is polished.

The structural edit

The fix is in chapter four and chapter eleven, not chapter nineteen. The author gives the timetable a second appearance — a minor character complains about the last ferry being moved — so it becomes a fact the reader holds rather than a detail they scanned. Chapter nineteen is barely touched. It now works because of something fifteen chapters earlier.

The sentence edit, later and separately

In pass five the author returns to the reveal and finds the paragraph is forty words too long and buries its turn in a subordinate clause. That is a real problem too — but it is a different problem, and fixing it earlier would have polished a scene that was structurally broken.

What this demonstrates

A chapter that reads badly is often not where the problem is. That is why the structural pass comes first: if you edit prose at the site of the symptom, you can spend a week making a scene worse.

Facts, continuity and the read-through

Once the prose is stable, check what the prose asserts. Timelines and ages, names and their spellings, quotations against their originals, statistics against their sources, and every citation you promised to record. Fiction has continuity; nonfiction has evidence; both punish an author who assumed.

Then read the manuscript in order, at something close to reading speed, in as few sittings as you can manage. Pacing problems and accidental repetition are invisible chapter by chapter and obvious in sequence — you notice you have explained the same thing three times because you meet it three times.

After that, other people. You cannot review your own book for the question that matters most, which is whether it works. Outside readers, then a professional editor if the book warrants it, then proofreading — on text you have stopped changing, because every new sentence is an unproofread sentence.

A self-editing checklist

Worth confirming before you call the revision done

  • I can state in one sentence what this book is for.
  • Every chapter has a job, and no two chapters have the same one.
  • Nothing important arrives before the reader has what they need to understand it.
  • I cut at least one thing I was attached to.
  • The sentence-level work happened after the structure was settled.
  • Names, dates and timelines are consistent throughout.
  • Every quotation has been checked against its original wording.
  • Every factual claim is traceable to the source it came from.
  • I have read the whole manuscript in order since the last structural change.
  • Someone who is not me has read it and told me what they thought it was about.
  • Proofreading happened last, on text I am no longer rewriting.

Common mistakes

What goes wrong

  • Editing the day after finishing, while you can still only read your intentions
  • Starting at chapter one every time, so the opening is rewritten forty times and the ending twice
  • Polishing sentences in a chapter you will later cut
  • Treating a flat scene as a prose problem when it is a setup problem
  • Fixing everything at once and finishing with an unevenly edited manuscript
  • Proofreading before the text has stopped moving
  • Confusing “I am tired of this book” with “this book is finished”

What helps instead

  • Real distance, or artificial distance — print it, change the font, read it aloud
  • Entering each pass with one question and refusing to answer the others
  • Keeping a decisions list so you stop relitigating the same cut
  • Reading whole before editing anything
  • Working on a copy, or in a system where the previous version is recoverable
  • Giving the book to a reader before you are ready to hear about it

Where software and AI genuinely help

Software is good at the bookkeeping that makes a long revision survivable: keeping the manuscript in pieces you can work on, keeping earlier drafts recoverable, letting you read the whole thing in order, and helping you find where you covered something.

AI can be useful at a narrow scope — tightening a paragraph you have already diagnosed, offering a second reading of a passage that is not landing, surfacing repetition worth checking. It is least useful exactly where revision matters most: deciding what the book is for and what has to go.

The failure mode is handing over a whole manuscript and accepting what comes back. A change you cannot review is a change you have not made — you have simply agreed to a different book.

What no tool can decide for you

  • Whether the book fulfils its intellectual or artistic purpose.
  • Whether a fact, quotation, statistic or citation is actually correct.
  • Whether a character's decision is emotionally convincing.
  • Whether the argument persuades a reader who disagrees.
  • Whether the manuscript is ready to be published.
  • Whether this book needs a professional editor.

No software replaces developmental editing, copyediting, proofreading, fact-checking, sensitivity reading, legal review or subject-matter review. Those are separate jobs done by people.

Doing this in Writva

If you want the process above supported rather than fought: Writva keeps a book in a Binder whose order is the manuscript order, with each chapter as its own writing unit you can open on its own. A revision lands in an Edited Version beside the approved Stable Version, so you can see the differences and Promote only when you mean it — and every promotion leaves the previous version in your history to restore.

Preview Flow reads the whole manuscript in Binder order for the read-through pass, and you can export a review copy as a Word document, Markdown or plain text, or produce a review PDF through your browser’s print dialog, when it is time for other people to read it.

Questions about editing a book

How long should I wait before editing?

Long enough that you read sentences you do not remember writing — for most people somewhere between two weeks and two months. The point is not the calendar, it is losing your memory of what you intended so you can see what is actually on the page.

Do I have to do the passes in order?

The order matters more than the number. Working from structure down to sentences stops you polishing prose in a chapter you later cut. But real revision loops — a structural pass often reveals that chapter four needs rewriting, and rewriting it changes the structure again.

How do I know when to stop editing?

There is no reliable signal, which is why deadlines and outside readers exist. A practical test: if your last three passes have been swapping words back and forth rather than fixing identifiable problems, you are finished with what you can see yourself and it is time for someone else to read it.

Should I hire an editor if I self-edit well?

Self-editing and professional editing do different jobs. Self-editing removes the problems you can see. A developmental editor tells you whether the book works, which is the one question you are structurally unable to answer about your own manuscript.

Start with the pass you have been avoiding

For most manuscripts that is the structural one — read it whole, change nothing, and write down what each chapter is for.

Try Writva freeSee pricing

Related