What Is The Difference Between A Book Editor And A Proofreader

Gary Smailes | 3 November 2025

Editor vs. Proofreader: Core Focus

Two different jobs, one shared aim. A strong book. An editor shapes content. A proofreader hunts final surface errors on designed pages.

What an editor focuses on

Editors work in levels, from big picture to line-by-line detail.

• Developmental editing solves structure and story logic. Scenes in the wrong order. Flat middle. A character who vanishes for five chapters. The editor maps the arc, tests stakes, fixes pacing, and proposes cuts or moves.
• Line editing tunes sentences for flow and tone. Wordy openings. Repetitive phrasing. A voice that slips from scene to scene. The editor trims filler, sharpens verbs, and guides rhythm while keeping your sound.
• Copyediting enforces correctness and consistency. Grammar, punctuation, capitalization, numbers, hyphenation, spelling choices, citations, and basic fact checks. A style sheet guides these decisions across the book.

Think of an editor as the partner who helps the book say what you mean, with clarity and intent. Big things first, then smaller things, all while protecting voice.

What a proofreader focuses on

Proofreading happens after layout. The book has page numbers, running heads, a table of contents, and chapter openings on real pages. A proofreader reads those pages and fixes surface errors and layout glitches.

Common targets:

• Typos and punctuation slips.
• Wrong or inconsistent spacing.
• Bad line breaks, awkward hyphenation, ladders of hyphens in a paragraph.
• Widows and orphans, single words stranded at the top or bottom of a page.
• Mislabelled figures and tables.
• Wrong page numbers in the table of contents or cross-references.
• Repeated words across a line break.
• Missing headers or mismatched fonts.

No rewriting. No new scenes. A proofreader guards accuracy and presentation so the final file reads clean and professional.

A quick side-by-side example

Raw sentence from a history book:

“By 1979 the movement was losing steam and the leadership were divided, the protests kind of fizzled out, which upset many of the younger members.”

What an editor changes, step by step:

• Developmental view: clarify timeline and stakes. Are we tracking one movement or several. Where does the decline begin. Which event signals the turn.
• Line edit: “By 1979 the movement had lost momentum. Leaders split over strategy, and protests dwindled. Younger members felt betrayed.”
• Copyedit: check verb forms, plural agreement, and date references. Confirm “leaders” not “leadership.” Standardize “1979” usage across the chapter. Note source for the claim.

What a proofreader marks on the final page:

• Correct a double space after a period.
• Fix a line break that leaves “1979” at the end of a line and “the” alone at the start of the next.
• Flag a hyphen in “dwindled-” at a page turn.
• Confirm the footnote number matches the note on page 312.
• Fix a widow, a single word at the top of a page.

Same sentence, different aims. The editor improves meaning and voice. The proofreader polishes presentation and catches strays after design.

How to choose the right help today

Ask a few blunt questions.

• Are you still moving scenes, rewriting chapters, or shaping argument. Hire an editor.
• Does the book need tighter sentences, cleaner tone, or consistency across spelling and terms. Hire a line editor or a copyeditor.
• Do you have a designed PDF with final page layout. Hire a proofreader.

Not sure which level fits. Try this short exercise:

1. Open a random chapter and mark three places where the story or argument stumbles. If you see structure problems, you need developmental help.
2. Read one page aloud. If your mouth trips on wordiness or clunky rhythm, a line edit will help.
3. Scan for serial commas, numbers, and hyphens. If choices shift without reason, a copyedit comes next.
4. Open the PDF. Look for bad breaks, wrong running heads, or a one-word last line. If you spot those, schedule a proofread.

What you receive from each role

From editors:

• An editorial letter with diagnosis and a plan.
• Tracked changes and margin notes with reasoning and options.
• A scene map or outline with structure notes.
• A style sheet covering names, places, spelling, numbers, and hyphenation.

From proofreaders:

• Marked-up page proofs, usually in a PDF with comments or standard proof marks.
• A query log for anything unclear or inconsistent.
• Corrections for spacing, punctuation misses, wrong breaks, and layout errors.

Different toolkits, different endpoints, shared goal.

A short story from the trenches

A thriller arrived full of verve and plot twists, plus a draggy middle. The author wanted a proofread. The pages were still in Word, not laid out. We talked scope and timing. The book needed structural help first.

Two weeks of developmental and line work trimmed three chapters from the middle, pulled a reveal forward, and tightened dialogue. After copyediting, the book moved to design. Proofreading then picked up page glitches, fixed a few bad breaks, and caught a mismatched page number in the contents. Same manuscript, three stages, each one suited to the moment.

Bottom line for your schedule

• Draft and self-revise.
• Developmental edit for story or argument.
• Line edit for voice and flow.
• Copyedit for correctness and consistency.
• Layout.
• Proofread of page proofs.
• Final files.

Skip editing and a proofreader will chase symptoms on the surface while deeper problems stay put. Skip proofreading and small errors sneak into print. Respect the sequence and the book earns trust from page one.

Place in the Publishing Workflow

Books move through a sequence. Skip a step and problems ripple forward. Fix the right tier at the right time and the whole project tightens.

The standard sequence

1. Self-revision and beta readers

   You shape the draft. You cut repeats. You fill gaps. A few trusted readers flag confusion and boredom. Notes at this point save later money.

2. Developmental editing

   Big-picture work. Structure, stakes, and logic. Where does the story bog down. Where does the argument drift. Scenes get moved. Chapters merge. Some sections go to the shredder. New beats appear.

3. Line editing

   Sentence-level polish. Tone, rhythm, and clarity. Verbs sharpen. Filler disappears. Repetition fades. Voice stays yours, only cleaner.

4. Copyediting

   Correctness and consistency. Grammar, punctuation, numbers, hyphenation, references, and basic facts. A style sheet records decisions so choices stay steady across the book.

5. Typesetting and layout

   Text enters design software. Pages gain line breaks, fonts, running heads, page numbers, and spacing rules. Paragraphs reflow. Tables and images land in place. This step creates the version readers will hold or view.

6. Proofreading of page proofs

   A quality check on designed pages. Typos, punctuation slips, bad breaks, widows and orphans, wrong page numbers, and layout glitches. Queries for anything odd.

7. Final files

   Proof corrections get applied. The output leaves for printers and digital platforms. No more changes.

Why proofread last

Proofreading works on pages, not raw Word files. Layout introduces new problems. A clean sentence in Word might split across a line in the worst spot. A table might nudge a paragraph onto a new page and leave a single word hanging. Hyphenation rules kick in and trip a name. None of this shows before design.

So proofreading waits for page proofs. PDF or printed proofs both work. The proofreader marks the pages, and only surface errors get touched. No rewrites. No new scenes. The goal is accuracy and polish on the final form.

What goes wrong when steps get skipped

A memoir hits my desk. The author asks for a quick proofread. No beta reads, no edit passes. The middle sags. Dates jump. Names shift spelling. If I mark only typos, the book still stumbles. If I flag structure problems, we are back at stage two and the budget balloons.

Another case. A business book moves from copyedit straight to print without layout checks. The index links break, tables wrap in odd places, and three cross-references point to empty pages. Fixing this after print means a second run and a new invoice from the printer. Fixing during proof would have taken a day.

A fast test to place your project

• Are you moving chapters or rethinking the order of ideas. You are at developmental stage.
• Are you smoothing sentences and trimming wordiness. You are at line stage.
• Are you standardizing numbers, titles, or terms. You are at copyedit stage.
• Do you have a designed PDF with page numbers and running heads. You are ready for proof.

Timing and handoff tips

• Book the proofread only after final page proofs exist. PDF or print, both fine.
• Freeze content before layout. New scenes or large rewrites during design trigger reflow. Reflow introduces new errors.
• Keep a single change list for proof. Group small fixes. Fewer rounds, fewer misses.
• If a late change touches more than a line, flag the ripple. Page numbers in the table of contents, running heads, cross-references, and the index might shift.
• Expect two passes for proof when schedules allow. First pass to mark. Second pass to verify corrections on updated pages.

What each stage protects

• Developmental saves readers from confusion.
• Line saves voice from bloat.
• Copyedit saves facts and logic from drift.
• Layout saves readability and brand look.
• Proof saves trust on the final page.

Honor the order. Editing builds the book. Proofreading protects the package. Time each step with care and the last file leaves your desk in fighting shape.

Scope of Work and Deliverables

Before you hire anyone, know what shows up in your inbox at the end. Editors, copyeditors, and proofreaders hand over different tools. Each tool serves a different stage of the book.

What you get from a book editor

• Editorial letter

  A focused report on how the book works. Expect a few pages, often more. It covers structure, stakes, point of view, pacing, argument flow, and audience fit. You might see notes like, “Chapter 3 repeats the reveal from Chapter 1. Merge or raise the new stakes.” Or, “Your narrator flips from past to present on pages 42 to 50. Pick one and hold it.”

• Tracked changes with comments

  The working file returns with edits and comments in Word or Google Docs. Edits fix clutter and nudge clarity. Comments explain the why. For example, “Tightened for rhythm,” or “Do we need this backstory now,” or “Term defined here, then used differently in Chapter 7.”

• Scene or outline map

  A list of scenes or sections with purpose, POV, and word count. This reveals saggy middles, thin subplots, and chapter bloat. It also helps you plan a clean revision path.

• Style and structure guidance

  Notes on tense, person, chapter order, recurring motifs, and how to handle back matter. Think of it as your user guide for the next pass.

• Style sheet

  A living document that records decisions. Spelling choices, hyphenation, capitalization, numbers, time and date formats, character names and traits, place names, product names, and any special terms. This prevents “e-mail” in Chapter 2 and “email” in Chapter 18.

Format to expect: one edited manuscript with Track Changes on, a separate editorial letter as a PDF or doc, a style sheet, and any maps or checklists as spreadsheets or simple docs.

What editors do not deliver by default: full rewrites of every chapter, interior design, ebook conversion, or cover copy. Ask if you need those, and price them as separate work.

What a copyeditor adds

• Line-by-line correction

  Grammar, punctuation, syntax, and clarity. Wordiness gets trimmed. Awkward phrasing gets smoothed. “Due to the fact that” becomes “Because.” Repetitions get flagged.

• Consistency control

  Names, titles, terms, timelines, and number treatment. Is it “US” or “U.S.” Is it “health care” or “healthcare.” Is your protagonist’s mother Anne or Ann. The copyeditor locks these choices and updates the style sheet.

• References and citations

  Formats your notes to the agreed style. Flags missing entries and mismatched sources. Checks URLs and obvious math.

• Queries

  Questions and brief notes for anything unclear. “Do you mean 10,000 here, not 1,000,” or “Chapter 9 says July, earlier chapter says June.”

Format to expect: one manuscript with tracked edits and comments, a cleaned version with edits accepted if requested, and the updated style sheet. Copyeditors work in Word or Google Docs. Some supply a short query log listing questions in one place.

What copyeditors do not deliver by default: heavy rephrasing that changes voice, legal review, sensitivity reads, or permissions. Those are separate services.

What a proofreader delivers

• Marked-up page proofs

  Proofreaders work on designed pages, not on the Word draft. You receive an annotated PDF that marks typos, spacing glitches, wrong page numbers, broken hyphenation, awkward line breaks, widows and orphans, bad running heads, and cross-references that point nowhere. If you are working on paper, you get traditional proof marks on printed pages.

• A query log

  A simple list of questions to confirm before final files go out. Sample entries:

  • “TOC lists Chapter 12 on page 183. The page shows 185. Which is correct.”
  • “Figure 4 caption says 2022 revenue. Graph shows 2021. Confirm.”
  • “Your name uses a middle initial on the title page only. Remove or add elsewhere.”

• A checklist of global fixes

  If the proof shows a recurring issue, you get a list for the designer. For example, “Replace all double spaces after periods,” or “Apply small caps to all AM and PM.”

Format to expect: annotated PDF or marked print pages, a query log, and sometimes a brief summary of global corrections. Proofreaders do not rewrite sentences or restructure paragraphs. Any change must respect the layout.

Clarify boundaries early

Editors and proofreaders fix words. They do not design covers, write jacket copy, build your website, format your ebook, source permissions, or index a monograph, unless the contract says so. Be clear on word count, number of passes, file formats, and the exact handoff point. Boundaries prevent scope creep and surprise invoices.

If you need extras, list them. Back cover copy. A press kit. A second pass after you revise. An index once pagination is locked. Price each one.

Ask for proof of approach before you commit

Request a sample edit on 1,000 to 2,000 words. Use the same passage for each candidate. You will learn a lot in a few pages.

What to look for:

• Are the comments specific and respectful.
• Do edits preserve your voice while improving clarity.
• Does the style sheet look organized and complete.
• Are queries crisp and few, not vague and many.
• Do you feel taught, not scolded.

Also ask for a list of deliverables in writing. Format, number of rounds, timeline, review windows, and how you will approve changes. A good editor sets expectations early. A good proofreader loves checklists. You want both.

Skills, Tools, and Standards

You hire skill, not software. The right pro sees structure, sense, and surface. Different eyes, different jobs. Here is how to tell.

What strong editors bring

Editors shape meaning. They look at:

• Story architecture and stakes. Does each chapter earn its place. Does the midpoint turn the screw.
• Character arcs and point of view. One lens per scene, or head hopping. Who wants what, and why now.
• Pacing and clarity. Long passages slow the pulse. Short ones clip along. Balance matters.
• For nonfiction, argument logic. Premises, evidence, order, and payoff. Are claims supported. Do terms stay stable.

Expect them to hear tone. They flag stiff phrasing, filler, and repetition. They refine without sanding off your voice.

Quick self-test:

• Write a one-line purpose for Chapter 4. If nothing comes, an editor will help you focus.
• List each scene’s driver. If you reach for “and then,” structure needs attention.

What meticulous proofreaders bring

Proofreaders defend accuracy on the page. They work on designed files, not Word drafts. They hunt:

• Typos, spelling, and punctuation misses.
• Inconsistent forms. Email versus e-mail. U.S. versus US. Toward versus towards.
• Bad breaks and spacing. One space becomes two. No space before a comma. Weird line wrap.
• Layout snags. Widows and orphans. Stacked hyphens. Ladders in narrow columns.
• Wrong folios and heads. Wrong chapter title in the running head. Page numbers out of order.
• Broken links and cross-references. TOC mismatches. “See page 144,” but the figure sits on 146.

They do not rewrite. They respect layout. Every mark aims to fix the surface without shifting the text.

Tools of the trade

Editors work in:

• Word or Google Docs with Track Changes and comments. Expect queries in the margin with reasons, not mystery edits.
• Styles and Outline View. Useful for spotting nested subheads, long sections, and repeat patterns.
• PerfectIt and clean-up macros. Great for consistency sweeps across long files.
• Readability checks. Not to control voice, to spot dense spots.

Proofreaders work in:

• Annotated PDFs. Highlights, callouts, stamps, and pinned notes. Clear symbols, clear intent.
• InDesign notes for projects in layout. Short flags to the designer, page by page.
• Traditional proof marks for print runs. BSI or Chicago symbols, neat and legible.
• Comparison tools. Old proof versus new proof, to ensure fixes landed and nothing else shifted.

A good workflow includes version control, backups, and a log of global changes.

Style guides and dictionaries

Standards keep a book steady from page one to the end.

Common choices:

• Chicago Manual of Style for most US books.
• New Hart’s Rules for UK publishing.
• House style for a press or imprint when provided.
• A project style sheet that records decisions unique to your book.

Dictionaries:

• Merriam-Webster for US spelling.
• Oxford for UK spelling.
• Macquarie for Australia.
• Add a specialist source for jargon or regional usage when needed.

What a style sheet covers:

• Spelling and hyphenation. Decision on e-mail versus email. Decision on decision making versus decision-making.
• Numbers and dates. Words for one to nine, numerals for 10 and up, or another scheme. Date format for the market you want.
• Capitalization. Job titles, headings, and branded terms.
• Punctuation choices. Oxford comma policy. Ellipsis style. Quote style.
• Names, places, and timeline notes. Character ages by chapter. Street names and spellings. Historical dates locked in.
• Formatting rules. Small caps for AM and PM. Bold in heads only. Italics for internal thoughts.

Ask to see a sample style sheet by the first round. You should spot order, clarity, and enough entries to guide future work.

Credentials worth noting

Training helps, but results matter most. Still, membership and coursework show commitment to standards and ethics.

Look for:

• CIEP, EFA, ACES, Editors Canada, or IPEd membership.
• Formal editing courses or certificates.
• Genre or subject experience close to yours.
• References you can contact. Ask for two.

One short trial beats a long résumé. Give two candidates the same five pages. Compare edits, comments, and tone.

Questions to ask before you hire

• Which style guide will you use. Which dictionary.
• Will you create or update a style sheet. When will I receive it.
• What tools do you use for comments and markup.
• How do you handle queries and unresolved issues.
• Do you keep a change log for global fixes.
• How many passes are included. What triggers an extra fee.
• Do you work on PDFs, Word files, or both. Which version.

Listen for precise answers. Vague promises hide weak process.

A quick sample test you can send

Use a short paragraph with common snags. For example:

• “The team are meeting on June 3rd, 2024. Email me at editor@site.com. In chapter two we said July.”

Ask for:

• Correct verb agreement.
• Date style consistent with the guide.
• Email styled per house rules.
• A query on the June versus July mismatch.
• A style sheet entry for date format and email.

You want clean edits, a note on the timeline error, and entries on the sheet. No voice shift. No flourish.

Strong skills, the right tools, and shared standards give you a steady book. Hire for judgment. Ask for receipts in the form of samples, style sheets, and clear methods. Your future pages will thank you.

Choosing the Right Professional for Your Manuscript

Hiring help works best when the service matches the stage of the book. Pick with purpose, not hope.

Start with a quick diagnosis

Ask three questions.

1. Where does the book wobble.

   • Structure and stakes feel muddy. Characters drift. Middle sags. Argument jumps or repeats. Readers report confusion.

     Hire a developmental editor.

   • Sentences sound off. Repetition, awkward phrasing, tonal whiplash, clunky transitions.

     Hire a line editor.

   • Grammar slips. Inconsistent hyphenation. Wobbly citations. Terms change from chapter to chapter.

     Hire a copyeditor.

   • Pages are already designed. You need a final check for typos, spacing, hyphenation, bad breaks, widows, orphans, and cross-references.

     Hire a proofreader.

2. What format sits on the desk.

   • A Word or Google Docs draft needs editing.
   • A typeset PDF needs proofreading.

3. What kind of feedback feels most useful right now.

   • Big-picture notes and a plan for revision.
   • Line-by-line tuning of rhythm and tone.
   • Consistency and correctness checks.
   • A last pass for surface errors after layout.

A short exercise helps. Write one sentence for the purpose of Chapter 5. Then list the main action in three bullet points. If focus slips, developmental work comes first. If meaning stands strong yet sentences feel flat, line or copy work will help. If the PDF looks great but tiny errors pop up, schedule proofreading.

Budget and timing reality

Editing often takes multiple rounds. Each round needs time for feedback and revision. Build room for both. Editors book out weeks or months ahead. Early contact saves stress.

Developmental work moves in long arcs. Plan for an editorial letter, a call, and revision time. Then a second pass to check new pages. Line and copy work move faster, yet still need a slot on the calendar and time for author queries.

Proofreading runs near the finish. Only schedule after the designer delivers stable page proofs. A proofreader needs the exact pages that will go to print or e-book. New sentences after proofreading introduce new errors, so hold off on fresh content changes. If a major change becomes unavoidable, plan for a second proofread of affected pages.

Ask each professional for a schedule with milestones. Examples help. Delivery of first pass. Author review window. Delivery of second pass. Final check. A clear plan protects budget and sanity.

Lock the contract before the work starts

A solid agreement reduces friction. Include:

• Scope. Developmental, line, copy, or proofreading. Name the service.
• Number of passes. One pass, two passes, or more.
• Word count or page count used for pricing.
• File formats. Word, Google Docs, PDF, or InDesign notes.
• Style guide and dictionary. Chicago with Merriam-Webster, New Hart’s with Oxford, or another pair.
• Deliverables. Editorial letter, tracked changes, margin queries, style sheet, query log, proof marks.
• Deadlines and response windows. Dates for delivery and dates for author replies.
• Revision policy. What triggers an extra fee. How new chapters or new sections get handled.
• Final QA. Whether a quick spot check follows layout changes.
• Payment schedule and cancellation terms.

Ask for a sample page from a past style sheet. Review for order, clarity, and consistency. A good style sheet reads like a map for the whole team.

Red flags worth heeding

• Promises of publication, agent interest, or bestseller status.
• “One pass covers everything” offers.
• Heavy rewrites that erase your voice.
• Refusal to name a style guide or dictionary.
• No contract, or a contract with fuzzy scope.
• No sample, no references, no portfolio.
• Full payment demanded before any work begins.
• Sloppy communication, missed emails, or files returned with hidden changes.
• Silence on version control and backups.

A professional editor or proofreader values process. Precision shows up before the first edit.

Run a short paid trial

Two candidates. The same 5 to 10 pages. Pay both for a small test. Use content with a mix of needs. A scene with dialogue, a short exposition passage, and a paragraph with dates or terms that require consistency. For a proofread test, send a short PDF with obvious spacing glitches and a widow on the first page.

What to ask for in the trial:

• Clear queries that explain reasoning.
• Respect for voice, even while tightening.
• Specific style sheet entries for spelling, hyphenation, numbers, and names.
• A list of global changes.
• For proofreading, standard proof marks or clean PDF comments.

How to judge the results:

• Are edits precise, purposeful, and easy to accept.
• Do queries invite decisions rather than bulldoze.
• Does the style sheet reflect the actual text.
• Any missed errors that readers often spot.
• Tone of feedback. Direct, helpful, and professional.

Score both trials on the same points. Clarity. Accuracy. Fit with your goals. Turnaround time. Communication.

Matching expertise to genre and goals

Experience in the right corner of publishing saves time. A romance editor understands beats and reader expectations. A history editor checks dates, sources, and notes. A proofreader with technical layout experience catches ladders, rivers, and cross-reference oddities. Ask for two titles in your lane. Read a few pages. Look for steady voice and clean pages.

Ask about tools as well. Word with Track Changes for editing. PDFs with proof marks for proofreading. InDesign notes when a designer wants feedback inside the layout. Version names for files. A naming convention signals care.

A simple decision grid

• Story and argument need reshaping. Hire a developmental editor.
• Meaning is solid, prose needs lift. Hire a line editor.
• Voice works, rules wobble. Hire a copyeditor.
• Text is final, pages are designed. Hire a proofreader.

Choose based on the manuscript in front of you, not a wish for speed. Right help at the right time saves money, preserves voice, and leads to a book readers trust.

Frequently Asked Questions

Download FREE ebook

Claim your free eBook today and join over 25,000 writers who have read and benefited from this ebook.

'It is probably one of the best books on writing I've read so far.' Miz Bent

Leave this empty

Get free book