What Does a Proofreader Actually Do? (And What They Don't)

Proofreading is one of the most misunderstood roles in the editorial process – partly because the word gets used loosely to mean almost any kind of correction, and partly because it's genuinely the last thing that happens before a book goes out into the world, which makes it feel like it should catch everything.

It doesn't. And it isn't meant to. Here's what proofreading actually involves – and just as importantly, what it doesn't.

What a Proofreader Does

Proofreading is the final polish before publication. By the time a manuscript reaches a proofreader, it should already have been through developmental editing and copy editing – the proofread is the last checkpoint, catching anything that slipped through earlier stages or crept in during formatting.

•       Corrects spelling, grammar, and punctuation errors – the small mechanical slips that remain after copy editing.

•       Checks for typos, double spaces, or missing words.

•       Ensures consistent use of hyphens, dashes, and quotation marks.

•       Reviews formatting and layout issues – headings, italics, paragraph breaks.

•       Verifies that style sheet decisions have been applied correctly and consistently throughout.

•       Double-checks page numbers, headers, and footers.

•       Spots any inconsistencies that survived copy editing.

A proofreader works with a genuinely keen eye for detail. But that detail is narrow and specific by design – which is exactly what makes the next part so important.

What a Proofreader Doesn't Do

This is the part that surprises a lot of authors – particularly those hiring an editorial professional for the first time. A proofread is not a rewrite, and it isn't a substitute for copy editing. Specifically, a proofreader will not:

•       Restructure sentences or paragraphs for flow, clarity, or style – that's copy editing's job, and it should already be done.

•       Rewrite awkward phrasing or improve weak dialogue  – proofreading assumes the prose itself is already in good shape.

•       Address plot holes, pacing issues, or character inconsistencies at a story level – that's developmental editing territory, and far earlier in the process.

•       Build a style sheet from scratch – a proofreader checks that an existing style sheet has been followed, rather than creating editorial preferences at this late stage.

•       Fact-check content or verify references in detail – some light flagging may happen, but thorough fact-checking sits outside a standard proofread.

This is precisely why sending an unedited or lightly self-edited manuscript straight to a proofreader rarely gives you the result you're hoping for. A proofreader is working on the assumption that the heavy lifting has already happened – so if it hasn't, a great many things will simply be outside their brief, however sharp their eye.

A Word on Overlap

In practice, no proofreader with a genuine care for your manuscript will read straight past an error just because it technically belongs to an earlier stage. If something glaring is spotted – a real inconsistency, a sentence that clearly doesn't work – most proofreaders will flag it, even if fixing it outright falls outside the scope of the job.

But that's different from proofreading being designed to catch those things. Understanding the distinction helps you commission the right service, budget accurately, and get the most out of the editorial process – for both stages.

If your manuscript is nearly ready for its final polish, I'd love to hear about your project.