← All field guidesStrengthen the manuscript

Editing & revision

Practical methods for structural editing, useful feedback, shared drafts, and revision without losing the writer's intent.

6FIELD
GUIDES
What this covers

Turn feedback
into actual revisions.

This cluster sits at the point where a draft stops being private. Someone reads it, has reactions, and leaves them behind as comments. What happens next decides whether the piece improves or merely changes. The four guides here treat editing and collaboration as one problem, because in practice they are: a revision decision is usually also a decision about whose reading to act on, which comment blocks publication, and which copy of the file is the one being edited. The logistics are not separate from the editing. They are what makes editing possible at all.

Length makes this harder. A reviewer of a book chapter cannot hold the whole argument in mind, so comments arrive scoped to paragraphs while the real problem may be the order of the sections. Meanwhile the draft keeps moving, and a note written on Tuesday can address prose that no longer exists. After these guides you will be able to give each reviewer a decision rather than a general invitation, ask for feedback that names problem and priority instead of preference, keep one canonical draft whose status means something precise, and close review in defined windows so revision has a starting point.

What these 6 guides answer

A suggested path

Where to start, and why

  1. How to edit a long-form draft with collaborators

    Start with who decides what. Roles defined by decision are what let later feedback resolve instead of pile up unowned.

  2. How to give writing feedback writers can act on

    Then the comments themselves: specific, prioritized, tied to the reader, and phrased so a writer can act without guessing.

  3. Keep one source of truth for a long manuscript

    Revision needs one current draft. This settles which document is canonical, what each status promises, and how old versions retire.

  4. How to revise a long draft with async reviewers

    Last, the timing. Handoffs that carry their own context, and review rounds that close so edits land instead of drifting.

Side by side

Which guide answers what

GuideWhat it answersWho it is forTime
How to edit a long-form draft with collaboratorsHow to divide editorial roles by decisionTeams with tangled review cycles7 min
How to give writing feedback writers can act onWhat makes a comment a writer can act onEditors, experts, and reviewers7 min
Keep one source of truth for a long manuscriptHow to keep one draft canonical across versionsAnyone losing track of versions7 min
How to revise a long draft with async reviewersHow to revise across time zones and schedulesDistributed teams and part-time reviewers7 min
Vocabulary

Terms used across these guides

Decision owner
The one person accountable for a particular call on a draft, such as domain accuracy or final approval, even when several people contribute opinions.
Severity label
A marker on a comment showing whether it blocks publication, matters but is negotiable, or is optional, so the writer knows what must be resolved.
Canonical draft
The single document agreed to hold the current approved prose, kept distinct from source notes, archived versions, and the published copy.
Review window
A defined period in which named reviewers comment, after which the round closes, comments are resolved, and anything deferred is written down.
Where to go next

Related topics

Put it to work

Getting a draft read by someone else?

Before you pick a guide

Editing & revision questions

What is the right order for revision?

+

Structure, then argument and evidence, then paragraphs, then sentences, then proofreading. Polishing a sentence inside a section you later cut is the most common wasted hour in revision.

How do I get useful feedback instead of praise?

+

Ask for a specific level of read and name the decision you are stuck on. 'Does section three earn its place?' gets a better answer than 'What do you think?'

Should I accept every edit?

+

No, but you should be able to say why not in one sentence about the reader. Defending a line because you like it is different from defending it because it does work.

How do we avoid two versions of the same draft?

+

Name one file the current one and make every other copy obviously historical. Version history is safer than a second file with a hopeful name.

Free to start — no card required

Projects, notes, versioned drafts, imported sources, and careful AI assistance in one private workspace.