Choose the edit by the size of the problem
- Developmental editing changes the manuscript's structure and delivery of its promise.
- Line editing changes how paragraphs and sentences create meaning and voice.
- Copyediting corrects language, facts, references, and consistency after structure settles.
- Proofreading checks the nearly final designed or converted version.
- Use a sample and written scope because service labels vary between editors.
Developmental, line, copy, and proof
- Developmental editing
- Manuscript-level editing of purpose, structure, argument or narrative, evidence, pace, omissions, and reader journey.
- Copyediting
- Sentence-level correction and consistency work covering grammar, usage, style, facts, references, and a manuscript style sheet.
- Proofreading
- The final quality check of stable text in its intended layout or output format, including errors introduced during production.
Developmental editing tests the whole
A developmental editor examines purpose, audience, argument or narrative arc, chapter order, pace, evidence, omissions, repetition, and whether the manuscript delivers its promise. The usual output is an editorial letter plus comments or a proposed structure - Not a perfectly corrected file.
Use it when the draft is complete enough to reveal its shape but still open to large change. If you already know chapter four may disappear, paying to copyedit its commas first is paying twice.
A developmental editor may recommend removing a chapter, changing the intended reader, moving the central claim, or gathering missing evidence. Those choices can make polished pages obsolete, which is why this pass comes first. The useful deliverable is usually an edit letter plus a map of the manuscript's current and proposed movement. It should explain reader problems and priorities, not prescribe a replacement sentence for every page.
Line editing works at paragraph and sentence level
A line edit improves how the prose creates meaning: emphasis, rhythm, clarity, transitions, tone, point of view, and unnecessary distance from the reader. It can recast sentences substantially while preserving the writer's intent and factual content.
The boundary between line and copyediting varies by editor, so ask for a sample and a written scope. One editor's ‘heavy copyedit’ may be another's ‘line edit’. The label matters less than seeing what kinds of changes are included.
Line editing asks how the thought reaches the reader. It checks paragraph movement, emphasis, rhythm, transitions, point of view, and the balance between scene, explanation, and evidence. A line editor may rewrite examples to demonstrate an option, but the author still decides what sounds true to the work. This pass is most valuable after the structure is stable enough that its improved paragraphs are likely to survive.
Copyediting makes the manuscript correct and consistent
Copyediting addresses grammar, syntax, spelling, punctuation, usage, internal consistency, factual queries, references, and an agreed style guide. The editor builds or applies a style sheet for names, numbers, capitalisation, hyphenation, and recurring choices.
Copyediting assumes the structure and most wording are stable. It may flag a logic problem, but it is not commissioned to redesign the argument. Send a manuscript still changing weekly and many corrections will land on sentences that no longer exist.
A copyeditor works against an agreed authority and records project choices in a style sheet. The sheet may settle spelling, capitalization, numerals, citation form, character names, abbreviations, and intentional exceptions. Copyediting also queries inconsistency and possible factual trouble, but it is not a substitute for specialist fact-checking. Its goal is a correct, consistent manuscript whose remaining departures are deliberate.
Proofreading checks the final form
Proofreading happens after copyediting and usually after layout. It catches remaining typographical errors, bad line breaks, missing elements, inconsistent headings, page references, captions, and mistakes introduced during design or file conversion.
Proofreading is not a budget version of copyediting. Its narrow scope depends on earlier editorial work being complete. Asking a proofreader to solve unclear chapters days before publication puts responsibility in the wrong stage and leaves no time for the resulting changes.
Proofreading belongs to the actual delivery form. A proofreader checks page numbers, headings, captions, line breaks, tables, cross-references, headers, and errors introduced during layout. The same words can be clean in an editable file and broken in a typeset PDF. Limit changes at this stage. A broad rewrite can alter pagination and create new errors that no longer receive a full copyedit.
The right edit is the earliest unresolved problem in the manuscript, not the cleanest service name on a quote.
Matching the problem to the editing stage
The author requests proofreading because the draft feels rough. The editor corrects punctuation in 80,000 words, but beta readers still cannot explain why chapters five through seven are there.
An editorial assessment identifies a missing causal step and two repetitive chapters. The author restructures and cuts 12,000 words, then commissions a line and copyedit on the stable manuscript. Proofreading happens only after layout.
The second sequence spends the deepest editorial attention on the earliest unresolved problem and avoids polishing material later removed.
Diagnose the manuscript before buying an edit
Read the first chapter, a middle chapter, and the ending against the brief. If the promise, order, audience, or argument remains uncertain, start with an editorial assessment or developmental edit. If readers understand the structure but stumble over the prose, consider line editing. If meaning is stable and the problem is correctness, copyedit.
A paid sample of representative pages tests fit and scope. Choose difficult, ordinary pages rather than your polished opening. Compare not only how many changes appear, but whether the editor understands what the work is trying to do.
Diagnose with a sample before commissioning the whole manuscript. Ask an editor to mark several representative pages and explain which level of change dominates. If comments repeatedly question the promise, order, or missing support, begin developmentally. If the argument holds but paragraphs feel heavy, consider line editing. If readers follow the piece and the remaining issues are correctness and consistency, it is ready for copyediting.
Prepare a clean handoff and revision sequence
Send the manuscript version you want edited, a short brief, intended reader, genre or publication context, word count, known concerns, style requirements, source or reference expectations, and the decisions that are closed. Agree how queries, tracked changes, and follow-up questions will work.
After a developmental edit, revise the structure before discussing sentences. After line or copyediting, review changes in batches by type so you learn the pattern rather than clicking accept repeatedly. Freeze the text before proofreading and record any post-proof change separately.
State the scope, file format, editorial authority, deadline, and expected deliverables in writing. Resolve known structural questions before the handoff and flag passages that require specialist review. When the edit returns, revise large issues first, then accept or adapt line changes, then update the style sheet. A clean sequence prevents a later structural decision from undoing paid sentence work.
Buying the wrong pass at the wrong time
Choosing by price alone
A cheaper late-stage service cannot solve an earlier-stage problem. Diagnose what remains unsettled and compare like-for-like scopes before comparing quotes.
Assuming labels are standard
Editors divide line and copy work differently. Ask what will change, what will only be queried, what deliverables arrive, and review a paid sample.
Sending a moving target
Parallel rewrites create conflicting versions and wasted edits. Agree a handoff date, freeze the manuscript for the pass, and log urgent later changes.
Accepting every tracked change automatically
Edits are recommendations within a scope, not transferred authorship. Review patterns, resolve queries, and preserve intentional choices you can explain.
Diagnose before hiring or editing
- Write the manuscript's intended reader, promise, and current state.
- Identify the earliest unresolved level: structure, prose, correctness, or final form.
- Ask editors for scope, deliverables, schedule, and a representative sample.
- Freeze and label the exact manuscript version being handed over.
- Provide the brief, style requirements, sources, and known concerns.
- Revise large issues before moving to smaller editorial passes.
- Freeze text again before proof and log every post-proof change.
Getting a draft read by someone else?
Apply this guide to a real writing project
- Copy the editorial review brief template and put this method into a working document.
Questions about editing levels
Do I need every kind of edit?
+
Not always. A short, low-risk piece may combine stages. A book or high-stakes report benefits from separating them because structural changes make sentence-level work obsolete.
Can the same editor do several stages?
+
Yes, if the schedule includes separate passes and the editor is suited to each. Fresh eyes at proof can still help because familiarity makes small errors easier to miss.
When should beta readers be involved?
+
After a complete, self-revised draft but before expensive sentence-level editing. Ask them reader questions rather than expecting professional editorial diagnosis.
What should an editorial sample include?
+
A representative section, the proposed type of edit, visible changes and queries, and enough explanation to show how the editor thinks - Not only a page of easy corrections.