PAPERBOAT / REVISION ROOM
Manuscript Revision Map
Put every chapter on the table. Name its job, the question a reader brings in, what the chapter delivers and what must change before the next revision round.
By Robert Urban. Free to use, with no email gate.
A chapter can be good and still be in the wrong book.
Sentence-level polish can make a chapter pleasant to read while leaving its structural problem untouched. The chapter may repeat work already done, depend on an idea the reader has not met, arrive before its evidence, or finish without creating a reason to continue.
This map makes those relationships visible. Each card asks for a purpose, an entry question, what the chapter actually delivers, the preparation it needs, the handoff it creates and one decision for the current revision round. The export keeps the board order and creates a separate queue for decisions that are still open or blocked.
The page does not judge the manuscript, grade a chapter or replace an editor. It gives an author a disciplined way to see the whole draft before spending another week improving sentences that may move or disappear.
Work on a copy of the manuscript. This page does not upload or save your entries. Avoid private client material, confidential records or identifying details you are not authorized to handle.
Start with one chapter.
Prepare the map to create an exportable structural brief.
The fictional river book begins with a bridge and ends with a choice.
Load the example and read only the entry and exit questions. Chapter one begins with a current bridge debate and leaves the reader with an older bargain. Chapter two explains how maps and records made that bargain possible. Chapter three shows who became less visible. Chapter four returns to the bridge with a different question.
That sequence is not a formula. It is a test of movement. If the cards can be shuffled without changing anything, the manuscript may be a collection rather than a cumulative argument. That can be exactly right, but it should be a choice the author can name.
The third card is marked combine and blocked. Those are different facts. Combine is the editorial decision. Blocked describes the state of the work because two accounts still need to be reconciled. The map keeps a decision from masquerading as completed revision.
Name the job before defending the chapter.
A chapter purpose is not a summary of its subject. “This chapter is about the early years” names territory. “This chapter shows why the partnership looked stable before the first public disagreement” names a job in the reader’s experience.
When two cards have the same purpose, the tool flags the duplication. That does not prove one should be cut. One chapter may establish the rule while another tests its exception. Write the distinction. If you cannot, a combine or cut decision may be more honest than inventing a new title for repeated work.
A chapter can also do too many jobs. If its purpose needs a paragraph full of “and,” decide which movement belongs here and which belongs elsewhere. The board works best when every card can answer one question: what would the book lose if this chapter vanished?
Revision is larger than proofreading.
The UNC Writing Center guide to revising drafts distinguishes rethinking argument, evidence, purpose and organization from the later work of proofreading. That distinction matters here. A move, combination or cut should be settled before commas receive the attention of a final pass.
The same guide recommends taking large issues in focused revision sessions instead of trying to solve everything at once. The revision-round field puts a boundary around this board. “Structural pass after reader feedback” is more useful than “make the book better.” It gives decisions a shared frame and prevents a chapter from being reopened for every possible concern at once.
This tool records the author’s choices. It does not claim that an unchanged chapter is strong or that a reviewed card is finished forever. “Reviewed for this round” means exactly that.
Dependencies are promises made in both directions.
The dependency field asks what the reader must already know. A technical chapter may require a definition. A memoir scene may require a relationship to be established. A mystery reveal may require a clue to have been noticed without being explained. A business book may need the reader to accept a premise before applying a method.
The exit field asks what the chapter hands forward. It may answer the entry question, complicate it or replace it with a better one. A chapter that ends only because the page count has become respectable probably has not yet named its handoff.
Purdue OWL’s guidance on revising for cohesion focuses at the paragraph level on how familiar information and topic progression help readers move. The same editorial question can be asked at chapter scale: what does the reader recognize on arrival, and what new understanding carries them onward?
Decisions belong to a round, not to a mood.
Keep and clarify means the chapter retains its structural job but needs a sharper expression of that job. Reshape changes the internal order, emphasis or evidence. Move changes the sequence. Combine merges work now split across cards. Cut removes the chapter from this manuscript while allowing useful material to live elsewhere.
Decision still open is not a failure. It is a warning against polishing by inertia. Write the evidence needed to decide, then place that question in the exported queue. If another chapter must change first, mark the status blocked and say why in the next-action field.
Do not create a fake score to avoid the judgment. A chapter with three scenes, six sources and perfect mechanics can still be unnecessary. A short, rough chapter can still be the hinge on which the whole book turns.
Questions before the cards become a new outline
Does every chapter need to answer its entry question?
No. It can deepen, redirect or complicate the question. The exit should make that movement legible.
Should the dependency field list every earlier chapter?
No. Name the specific knowledge, relationship, clue or claim required. “Chapter 2” is less useful than “the planning boundary introduced in Chapter 2.”
Can I use this for fiction?
Yes. Replace argument and evidence with the scene, revelation, pressure or change the chapter delivers. Do not turn every narrative effect into an explanation for the reader.
Does reviewed mean finished?
Only for the revision round you named. Later structural, line, copy and proof passes have different jobs.
Can this replace developmental editing?
No. It can prepare an author for a developmental conversation and preserve the decisions that follow. It cannot provide the independent reading the manuscript may need.
Where is my work saved?
It is not saved by this page. Download the text map when you want a copy and store it with your manuscript files.
The board should make the next read more exact.
Once the structure is visible, read the manuscript against the map. Ask whether each chapter performs the job you assigned, whether its evidence can carry that job and whether the promised handoff actually occurs. Change the map when the manuscript teaches you something better.
For the earlier work of defining a reader, promise and evidence architecture, read Book Development and Editorial Strategy. Browse Writer’s Notes for craft, or explore book publishing services when the manuscript needs an independent assessment and a production path. The map remains free whether or not we work together.
Once the manuscript is ready for production, use the Book Production Schedule Builder to connect editing, design, proofing and release tasks with dates, dependencies and buffers.