What Proofreaders Actually Do (And Why It’s Not the Same as Light Copyediting)

Ask ten people what a proofreader does and you’ll get ten versions of the same answer: They check for typos, catch grammar mistakes, and give a document one final look before it goes out the door. That description isn’t wrong, exactly, but it’s incomplete enough to send a new editor’s career in the wrong direction before it’s really begun. Very few people outside the editorial industry know what proofreaders actually do.

Proofreading is a specific, skilled, production-stage service. It’s not a catch-all term for light editorial review, and it’s not something you do to a Word document that hasn’t been edited yet. Understanding what professional proofreading actually involves—what the proofreader is looking at, what she’s responsible for catching, and where she sits in the editorial process—will help you offer this service accurately, price it correctly, and recognize when a client is asking for something other than what they think they’re asking for.

The proof: What proofreaders actually work on

The word “proofreading” contains its own definition, if you know where to look. A proofreader reads a proof—and a proof is not the same thing as a manuscript.

In traditional publishing, after a manuscript has been copyedited and approved by the author, it goes to a designer or typesetter. The typesetter takes the edited Word file and pours it into a layout program, applying the fonts, spacing, margins, running heads, page numbers, and all the visual specifications that transform a text document into a designed artifact. The result—a PDF of the laid-out document as it will actually appear in print or as a final digital file—is the proof.

That’s what the proofreader receives. Not the raw manuscript. Not the Word file. The fully designed document, ready for one last review before it goes to press or is uploaded for distribution.

This matters because the proofreader’s job is defined by that object. She’s not re-editing the text from scratch; the copyeditor already did that. She’s reviewing the designed document to confirm that the typesetter captured every correction accurately, and she’s catching any problems the typesetting process itself introduced.

What proofreaders are actually looking for

There are two categories of errors that a professional proofreader is responsible for catching.

The first is typesetter error: Mistakes that didn’t exist in the approved manuscript but were created during conversion from Word file to designed document. A word correctly spelled in the manuscript but garbled in the layout software. A dropped paragraph. A correction the copyeditor marked that the typesetter missed or accidentally reversed. A heading that appears twice because of a production glitch. These are the proofreader’s primary quarry.

The second is surviving errors—serious mistakes that made it through the copyedit. Every copyeditor, no matter how skilled, will miss things. The proofreader is the last line of defense, catching errors significant enough to warrant correction even at this late stage, when every change costs time and money.

What she is not doing is making stylistic judgments, reconsidering the author’s word choices, or applying the style guide from scratch. That ship has sailed. Her job is error detection at the level of the final document, not editorial improvement of the prose.

The production skills required to be a professional proofreader

What separates professional proofreading from a careful read-through is that a proofreader needs to understand the physical document she’s reviewing—not just the words in it.

That means knowing what widows and orphans are. A widow is a single line stranded at the top of a page, separated from the paragraph it belongs to. An orphan is a single line left at the bottom, cut off from what follows. Both are visual problems the proofreader is expected to flag.

It means checking running heads—the line at the top of each page that typically repeats the book or chapter title—to verify they’re correct and consistent throughout. It means confirming that page numbers are sequential and that the table of contents matches the actual pages. It means noticing when line spacing is inconsistent, when a font has shifted unexpectedly, or when a design element has broken in a way that will look wrong in the final product.

None of that is grammar. None of it is style guide application. It’s a trained eye for how designed documents hold together—a skill that takes time to develop and is easy to underestimate.

Cold proofing versus comparison proofing

As you develop your proofreading practice, you’ll encounter two terms describing different approaches to the work. It’s worth knowing them before you run across them in a job posting or client conversation.

Cold proofing—also called blind proofing—is what most freelance proofreaders do most of the time. The proofreader works from the proof alone, without a copy of the original manuscript to compare against. She reads the designed PDF carefully, catching errors through trained attention rather than direct comparison. Because today’s editorial workflow is largely digital—manuscripts move from author to editor to designer as computer files, each pass cleaning up what came before—cold proofing is standard practice in most contemporary publishing contexts.

Comparison proofing, sometimes called reading against copy, is the alternative. The proofreader works with two documents at once: the typeset proof and the copyedited manuscript. She checks one against the other line by line and flags any divergences. This method is more reliable for catching typesetter errors, but it’s slower and requires access to the marked-up manuscript—something freelancers working outside a publisher’s production pipeline often don’t have. You’re most likely to encounter it in high-stakes print contexts: academic presses, legal publishing, or books with complex tables where a single transposed number matters.

Cold proofing is more common these days, but neither method is inherently superior. What matters is knowing which one a project calls for and being clear with your client about which you’re doing.

Why professional editors don’t “proofread” a Word document

If you’ve spent any time in online editing communities, you’ve seen some version of this question: “A client wants me to proofread their manuscript. It’s a Word document, never been edited. What should I charge?”

You should be able to spot the problem immediately: What the client is describing isn’t proofreading. It’s copyediting—or possibly copyediting plus some light developmental feedback, depending on the state of the manuscript.

A raw Word document is not a proof. It hasn’t been typeset. There’s no designed document to read against. The service the client needs is fundamentally different from what “proofreading” means in its professional sense.

This creates a real practical challenge for new editors, because you can’t simply correct the client’s terminology and move on. You need to find out what they actually have, what it actually needs, and what they expect you to deliver—then describe the service in terms they’ll understand and agree to, even if those terms differ from what they originally asked for.

That kind of clarity in client conversations starts with your own understanding of what these services are. When you know precisely what proofreading involves, you can recognize when a project fits that description and when it doesn’t—and you can have that conversation professionally, without underselling what you’re doing or overpromising what you’ll deliver.

For the full picture of how proofreading fits into the editorial process alongside developmental editing, line editing, and copyediting, see our post on the four levels of editing. And for a closer look at exactly where the line falls between copyediting and proofreading—and why so many people get it wrong—see our recent post.