Ask three writers what editing means and you will get three answers: a friend's red pen on typos, a structural overhaul that moves chapter four to chapter eleven, and a long argument about whether "said" should be "murmured". These are separate jobs, done with different parts of an editor's brain, and doing them in the wrong order costs time and money. Here is how to tell them apart, and how to work out which one your draft needs next.
Two Jobs, One Word
Developmental editing works on the whole book. Line editing works on the paragraph and the sentence. Both get called editing, which is why so many writers book the wrong one.
There are really four passes a manuscript goes through, and they answer different questions:
- Developmental editing: does this work as a whole?
- Line editing: does this sentence work, and does it sound like you?
- Copy-editing: is this correct and consistent?
- Proofreading: is this clean?
Each pass assumes the one before it has been done. That assumption is the whole reason order matters.
Developmental Editing: The Big Picture
A developmental editor reads the manuscript as a reader first and a mechanic second. They are looking at structure, pacing, stakes, point of view, character motivation, subplots, the shape of the argument if you write non-fiction, and whether the book delivers what the opening pages promise.
What comes back is usually an editorial letter — several pages of analysis — plus comments in the margins or at the end of chapters. Expect questions rather than instructions: Why does Marianne trust him here? What does this scene change? Expect to cut, too. Losing eight or ten thousand words during a developmental revision is normal.
Problems a developmental edit tends to surface:
- A crime novel where the detective solves the case in chapter nine and then spends six chapters driving around.
- A memoir that clears its throat for eighty pages before the interesting thing happens.
- A non-fiction draft whose chapters overlap so heavily that the reader meets the same argument four times.
Line Editing: The Sentence Under the Microscope
Line editing assumes the structure is settled. It works paragraph by paragraph on rhythm, clarity, word choice, tone and voice.
This is the pass where "she nodded her head in agreement" becomes "she nodded", where filter words disappear (she felt the cold wind becomes the wind found the gap in her coat), where three "just"s in one paragraph become one, and where five long sentences in a row get broken up so the reader can breathe. It is also the pass that makes dialogue sound like speech: characters who interrupt, trail off, answer a different question than the one they were asked.
What line editing will not do is rescue a scene that should not exist. You can polish the sentences in a redundant chapter until they shine, and the reader will still skip it. That is developmental territory.
Where Copy-Editing and Proofreading Fit
Copy-editing is the mechanical pass: spelling, punctuation, grammar, consistent capitalisation, house style, and small factual consistencies such as whether your character's eyes are green in chapter two and grey in chapter fourteen. Proofreading is the last look at the typeset pages, catching typos and layout slips before the book goes out.
Both matter, and neither replaces the two passes above. A proofreader is not there to restructure your second act, and a copy-editor should not be rewriting your prose.
Why the Order Is Developmental, Then Line
Think about renovating a house. You do not paint the walls and then knock one down. Editing works the same way. If you pay for a line edit and later realise the middle act needs rebuilding, most of those careful sentence-level improvements vanish with the cut scenes.
The reverse holds as well. A developmental editor will tell you what is wrong with the structure; they are not there to tidy your comma splices. Ask one person to do both in a single pass and you get a strange hybrid: structural notes that skim the surface, and sentence notes on scenes that may not survive.
Do them in sequence, with your own revision in between. That is where most of the improvement actually happens.
How to Work Out What Your Draft Needs
Before you spend anything, run these checks:
- Put the manuscript aside for a fortnight, then read it in one sitting, ideally on paper or a different device. Long gaps hide structural problems.
- Write a two-line summary of every chapter, then read the summaries in order. If the story sags, repeats or loses a thread, you have a developmental job on your hands.
- Ask three honest readers two questions: where did you get bored, and what confused you? Nods to pacing, motivation or the ending point to structure. Quoted sentences and stumbling phrasing point to the line level.
- Check the symptoms. Developmental: you cannot describe the book in two sentences, subplots trail off, the middle drags. Line: you re-read your own sentences to parse them, dialogue is hard to follow, the same words keep appearing.
- Ask an editor for a short sample edit and their recommendation. A few pages of their thinking tell you more than any sales page.
Getting the Most From Either Pass
Send a brief. Say who the book is for, what you are worried about, and which pass you are buying. If a developmental editor offers a call alongside their letter, take it — questions are easier to ask out loud.
Triage the feedback rather than accepting or rejecting it wholesale: yes, no, and let me think about it. Keep every version tucked away, and do your own revision before booking the next stage, so the next editor sees your best work rather than your notes to yourself.
A Rule of Thumb
If you are still deciding what happens, you need developmental editing. If the story is settled and you are choosing between two ways of writing the same sentence, you need a line edit. Most drafts need the first long before the second — and knowing which stage you are in will save you more than any discount.
Photo: cocoparisienne / Pixabay
