WordsmithWordsmith

Acting on the edit

How to prioritize developmental feedback without revising everything at once

Prioritize developmental feedback by grouping comments under root manuscript problems, then ordering those problems by dependency. Start with decisions that can change structure, causality, point of view, argument sequence, or the ending, because they make later sentence and scene work obsolete. For each diagnosis, record the reader effect, the manuscript evidence, the chapters affected, and the decision it requires. Repeated comments are not automatically more important; they may be several symptoms of one cause. Finish with a short queue of decisions, not a page-by-page list of edits.

By the Wordsmith team · Last updated

Collapse symptoms into root problems

Copy each major note into a table with four columns: reader effect, manuscript evidence, chapters affected, and the decision the note appears to require. Then group notes that describe the same loss of momentum, confusion, weak causality, or missing setup.

A repeated comment can be one problem appearing in many places. Treating every instance separately hides the manuscript-level decision and creates unnecessary work.

Order decisions by dependency

Work first on choices that can invalidate other work: premise, structure, argument sequence, character causality, point of view, and the ending. Revisit pacing, continuity, scene purpose, and language after those decisions settle.

Do not use severity alone. A modest structural decision can come before a painful line-level problem because the structural choice determines whether that line survives.

Turn the letter into a bounded revision queue

Name the next three to five manuscript decisions and the evidence you will use to test each one. Keep local notes attached to their root decision instead of letting them become a second unordered list.

A bounded queue gives the revision a stopping condition. When one decision is resolved, reread the affected span before opening the next dependency.

Frequently asked questions

Should I start with the easiest editorial note?

Only when it does not depend on a larger decision. Easy work can become waste when a later structural change removes or rewrites it.

Should I fix every repeated comment separately?

No. First test whether several comments are symptoms of one manuscript-level cause that can be resolved with one coherent decision.

Sources and product facts

Keep reading

Browse every guide

Put your manuscript in front of Fred

Fred reads the whole manuscript and marks up a sample before you pay.

How to prioritize developmental feedback without revising everything at once | Wordsmith