Proofreading checklist terms
A proofreading checklist is a list of the specific things to check before work goes to a client or to print: for example, the website preset asks you to confirm that no link still points to the staging site and that no lorem ipsum is left on any page, alongside the usual spelling and number checks.
Proofreading is the last check, after the writing and editing are done. It catches what slipped through: a wrong date, a broken link, a client name spelled the old way. A checklist turns "read it again carefully" into a set of boxes someone can actually tick and sign.
- Proofreading
- The final pass for mistakes in spelling, grammar, numbers, names, links and layout. It is not rewriting. If a proofreader starts changing the message, the copy was not ready to proofread.
- Copy editing
- The step before proofreading: making the text clear, consistent and right for the reader. Run the readability checker and agree the tone during copy editing, not on the day of launch.
- Proof
- The version of the work you check, in its final format: the staging site, the print PDF or the test email. Proofread the proof, not the document the text was written in, because layout causes its own mistakes.
- Widow and orphan
- A single word or line stranded on its own: at the end of a paragraph, or at the top or bottom of a column or page. They look like mistakes to clients even when the words are right.
- Second reader
- Someone who did not write the text. Writers read what they meant to write; a fresh reader sees what is actually there. On small teams, the client can be the second reader for names and facts.
- Sign-off line
- The space at the bottom of the sheet where the approver signs and dates. It records that the checks were done on a named version, so a later "who missed this?" has an answer.
What each proofreading checklist preset covers
Each row is one preset from the checklist builder above, counted by the same code the builder uses. Every preset shares the basics (names, numbers, spelling and a final read) and adds the checks that matter for that kind of deliverable.
| Preset | Best for | Sections | Checks | A check only this preset has |
|---|---|---|---|---|
| Website pages before launch | Copy, links and buttons on a staging site. | 6 | 23 | Opening hours, address and contact email match the client’s current details |
| Brochure, poster or print PDF | Anything that goes to a printer. Mistakes cost a reprint. | 5 | 20 | Web addresses and social handles typed out in full and tested |
| Email newsletter or campaign | One send, read by everyone at once. No undo. | 5 | 17 | Offer dates, codes and end times are correct and in the right time zone |
| Social posts and captions | Short copy, many versions, often written late. | 4 | 15 | Tagged accounts and hashtags spelled correctly and belong to the right people |
| App or product interface text | Buttons, errors and empty states across many screens. | 5 | 19 | The same action has the same name on every screen ("Delete" is never also "Remove") |
| Proposal, quote or report | A business document the client will forward to others. | 5 | 20 | The client’s company name and the contact’s job title are correct |
Limits of a proofreading checklist
A proofreading checklist cannot see the work
Ticking a box is a promise that someone looked. The checklist only helps if each check is done on the final proof, line by line. Rushed ticks on a draft give a false sense of safety.
Facts need the client, not the proofreader
You can confirm that a price is the same in two places, but only the client knows if it is the right price. Send the names, numbers and dates to the client to confirm in writing before the final proofread.
Add what is specific to the project
Every project has its own traps: a product name with an odd capital, a legal line the client insists on, a currency that changes by region. Use the project-specific checks box for them, so they are on the sheet next time too.
Spell checkers miss real words
A spell checker passes "form" when you meant "from" and "manger" for "manager". Keep the read-aloud check even when the spelling tool shows no errors.
Questions about proofreading checklists
What should a proofreading checklist include?
The basics for every job: names, numbers and dates, spelling and grammar, consistent style, and a final read by a second person. Then the checks for the format: links and forms for a website, trim and safe area for print, subject line and test send for an email.
When should I use the proofreading checklist on a client project?
At the end of each round, on the version you are about to send, and again before launch or print. Proofreading a draft that will still change wastes the check. Proofreading after the client approves means mistakes go live with their approval on them.
Who should sign the proofreading checklist?
The person who proofread it signs that the checks were done. The client or approver signs that the facts are right and the version is approved. Two names make it clear who checked what.
Can I print the proofreading checklist?
Yes. Use "Print or save as PDF" to get a one-page sheet with tick boxes and a sign-off line, or "Copy text" to paste it into a task or a shared document. Nothing you type leaves your browser.
How is a proofreading checklist different from a launch checklist?
A proofreading checklist covers the words and how they appear. A website launch checklist covers everything else on launch day: hosting, redirects, analytics, backups and forms. Use both on a website project.
How do I proofread my own writing?
Leave a gap first, even an hour. Then change the format (print it, or read it on your phone), read it out loud, and check names and numbers one at a time against the source. Read headings separately: mistakes hide in big text.