Editing & Revision

How do I create a revision roadmap for a novel?

By the WriteLoom editorial teamUpdated 2026-06-02
Key facts
  • A roadmap converts scattered feedback into an ordered sequence of revision passes.
  • Step 1: pool every note (editorial letter, beta feedback, your own) into one list.
  • Step 2: cluster notes into 4-8 themed problems, not 60 line items.
  • Step 3: assign each cluster to a layer — structure, scene, or sentence.
  • Step 4: sequence passes biggest layer first; one pass per week is sustainable.
Direct answer

You build a revision roadmap by pooling all feedback into one list, clustering the dozens of individual notes into four to eight themed problems, assigning each cluster to a layer (structure, scene, or sentence), and then sequencing those clusters into passes — biggest layer first. The roadmap turns a pile of contradictory comments into an ordered plan you can execute one pass at a time.

Chapter i·Why it matters

An editorial letter plus beta feedback can land as sixty disconnected comments, and writers who try to address them in the order received produce tangled, inconsistent revisions. Clustering reveals that twelve separate notes are really one structural problem. A roadmap also defuses overwhelm by replacing "fix everything" with "this week, fix one layer" — the difference between finishing revision and abandoning it.

Chapter ii·What to include

  • A single pooled list of every note from every source.
  • A clustering step: group notes into 4-8 named problems (e.g., "midpoint sags," "antagonist is unclear").
  • A layer tag per cluster: structure, scene, or sentence.
  • A priority order: structural clusters first, line clusters last.
  • A pass schedule: one themed pass per week, dated.
  • A disagreement column: notes you have evaluated and chosen not to act on, with reasons.

Chapter iii·Example

A novelist receives a 14-page editorial letter and feedback from six beta readers — 58 comments total. She pools them and clusters into five problems: weak midpoint (structural), antagonist underdeveloped (scene/character), two saggy subplot threads (structural), stiff dialogue (sentence), and timeline confusion (scene). She orders them structure-first and schedules five weekly passes. What felt like an unmanageable mess becomes a five-week calendar she can actually follow.

In WriteLoom

WriteLoom's Edit studio clusters editorial and beta feedback into themed passes and sequences them biggest-first — your roadmap, built from the notes.

See the Edit studio