You cannot proofread a document you can still recite
By the final draft your brain supplies what you meant rather than what is on the page. That is not carelessness, it is how reading works. Every technique here is a way of making familiar text unfamiliar enough to actually see.
First, make it unfamiliar
Everything else depends on this. The goal is to disrupt the fluency that lets you skim.
Change the font and the size. Switch to a different typeface at a larger size; it reflows every line and the text stops looking like the document you have been staring at.
Change the device. Read it on your phone, or print it. Different line lengths break the visual memory of where things sit on the page.
Change the setting. Read somewhere you did not write it.
Leave it as long as you can. Time is the strongest version of all of these, and the least available.
Read it aloud, properly
Not muttering. Out loud, at speaking pace, pronouncing every word.
This is the single most effective technique available for self-proofreading and almost nobody does it, because it takes as long as speaking the document does. It catches missing words, doubled words, sentences that run out of air, and awkward phrasing that the eye slides over.
Where you stumble, mark it. A sentence you cannot read smoothly aloud is usually a sentence a reader will stumble on too, even silently.
Run separate passes for separate things
Looking for everything at once means finding very little. Four passes, each with one job, catches far more than one careful read.
Structure. First sentences of every paragraph, read in order. Does the argument follow?
Sentences. Read aloud, looking for clarity and flow.
Surface. Grammar, spelling, punctuation.
Mechanics. Citations, references, headings, numbering, formatting.
Running them in this order matters, because fixing a sentence in a paragraph you later delete is wasted work.
Search for your own errors
Everyone has a personal set of recurring mistakes. Keep a list from the feedback you receive, and search for each one rather than hoping to notice it.
Common items worth searching regardless: its and it’s, their and there, affect and effect, double spaces, double words such as “the the”, and every opening bracket having a partner.
Search is more reliable than reading for anything that can be searched. Reserve reading for the things that cannot.
Read backwards for surface errors
Start with the last sentence, then the one before it, working up the document.
This strips out meaning and momentum, so you see each sentence as a physical object. It is good for typographical errors and bad for anything else, so it belongs at the end rather than at the start.
Check the mechanics against a list
These are the errors most likely to survive every reading pass, because they are not in the prose.
Every in-text citation has a reference list entry. Every reference list entry is cited. Every table and figure is numbered and mentioned in the text. Headings are at consistent levels. Page numbers are present. The file is named sensibly. The word count is within range.
None of this requires reading the document, which is why it is worth doing as a separate checklist at the very end.
Knowing when you are done
You are not proofreading when you start making changes and then changing them back. That is the point at which more passes stop adding anything, and it is usually the point at which another reader becomes the only way to improve the document further.
Frequently Asked Questions
As long as your deadline allows. Twenty-four hours makes a noticeable difference; a few days is better. If you have an hour, change the format instead, which produces some of the same effect much faster.
Yes, more than almost anything else. It forces you to process every word rather than skimming, and it catches missing words, repetition and sentences that run out of breath. It is slow, which is exactly why it works.
As one pass among several. It reliably catches agreement, spelling and some punctuation. It misses dangling modifiers, ambiguous pronouns, tense drift and anything requiring knowledge of what you meant, and it occasionally suggests changes that are wrong in academic context.
Reading the last sentence first, then the one before it, and so on. It removes the argument's momentum so you see sentences as objects rather than as meaning. It is effective for surface errors and useless for structure, so it belongs late in the process.
Because you are reading your intention rather than the text. Your brain autocorrects, and it does so more reliably the better you know the document. Anything that disrupts fluency, such as a different font, a different device or reading aloud, reduces the effect.
It is enough to catch most surface errors and it will not catch everything, particularly sentences that are clear to you because you know what they mean. For work that carries real consequences, another reader is worth having.
Out of distance from your own document?
Send it to someone who has never seen it. Every change tracked, with the reason beside it, so the next draft needs fewer.
Get My Free Quote