Every author who has been through a serious editorial process knows the feeling of reading a note that makes something click. A paragraph you'd been uneasy about for months, suddenly explained. A structural problem named so precisely that the solution becomes obvious. That is what a great edit feels like — not a correction, but a clarification of what the work is actually trying to do.
A good edit is something different. A good edit is thorough, attentive, and technically sound. It catches errors, questions inconsistencies, and improves the prose at the surface level. These things matter. But a great edit goes further: it engages with the work on its own terms, understands what the author is reaching for, and helps them get there.
What a good edit looks like
A good editor reads carefully. They notice when a character's eye colour changes between chapters, when a timeline doesn't add up, when a sentence has one too many clauses. They query passive constructions, flag clichés, and push back on dialogue that sounds written rather than spoken. They do the technical work that a manuscript genuinely needs before it can be published.
This is valuable, and it shouldn't be minimised. Many manuscripts that reach readers have not had this level of attention, and it shows. The baseline of a good edit — rigorous, comprehensive, technically sound — is the minimum standard a published book should meet.
A great editor doesn't try to make your book better. They try to make your book more itself.
What a great edit looks like
A great edit begins in the same place as a good one — with close, careful reading — but it asks a different question. Not "what is wrong with this manuscript?" but "what is this manuscript trying to be, and what is standing in the way?"
This distinction sounds small. It is not. An editor who approaches a manuscript looking for problems will find problems. An editor who approaches it looking to understand it will find something else entirely — the gap between what the work is and what it could be, and the specific, concrete steps that close that gap.
- They read for intention before they read for execution
- Their notes explain the reasoning, not just the verdict
- They distinguish between what should be changed and what should be left alone
- They ask questions as often as they make suggestions
- They make the author feel seen, not corrected
How to tell the difference — before you start
The distinction between a good and great editor is usually visible before a single note is written. It is present in the initial conversation. Does the editor ask about your intentions, your influences, your sense of what the book is for? Or do they move straight to process — turnaround times, track changes, style guide preferences?
Neither approach is wrong. But an editor who wants to understand the work before they touch it is more likely to engage with it on the level where great editing happens.
- Ask them what they look for in a first read — the answer reveals their priorities
- Ask how they handle notes the author disagrees with
- Ask for a sample edit on a few pages before committing to a full manuscript
- Read their notes on the sample as carefully as you read the edits themselves
The sample edit is everything
If you are working with an editor for the first time, a short sample edit — on one or two of your most challenging pages — will tell you almost everything you need to know. A good editor will improve those pages. A great editor will make you understand them differently.
That is, ultimately, the simplest test: after reading the notes, do you feel that someone has fixed your work, or that someone has understood it? The first is useful. The second is something you will carry through every draft that follows.