When my office hires at the entry level, there’s a proofreading and copyediting test. My preference has been to give the test in person, on paper. That levels the playing field by eliminating access to e-mail and online sources. It shows how a person will mark up copy on the job (a frequent chore for the new kid). It isolates proofing and editing skills from word-processing skills.
Results vary.
So in the interests of helping young editors in search of employment, I’d like to talk about the second-most common* fatal error that candidates make on the test: that is, their failure to understand the concept of proofreading. Every time we hire, I rewrite the test instructions in the hopes of making them flunk-proof, but there is inevitably at least one smart, promising candidate who in spite of alleged experience proofreading and copyediting still manages to miss the point of the exercise.
In the proofreading test, the candidate is given two versions of a document: The first is a typed page, double-spaced and covered with corrections handwritten by a copyeditor. This is typically called the manuscript. The second is a typeset page—it looks like a photocopy of a page of a published book. The second was typeset from the first, and if all has gone well, the hand-marked corrections will have been incorporated into the typeset (final) version.
The test instructions say to proofread the typeset version, not to mark on the manuscript, and to query anything that isn’t clear. Experienced proofreaders know to read the typeset version against the manuscript very closely, comparing the two, looking at every letter and space and punctuation mark to make sure that the two versions are identical and that no text has been added or deleted by accident. In the olden days, two people would share the task: one would read the original aloud, including punctuation and corrections, while the other followed along in the typeset version.
Naturally, the typeset version has errors in it—after all, it’s a test. The errors are of three main types: (1) the typesetters failed to make a requested correction, (2) the typesetters introduced a new error in a place where no correction was marked, and (3) the typesetters followed the editor’s marking accurately, but the editor’s marking was incorrect. The third type should be rare.
IMPORTANT: The idea is to correct the first two kinds of errors without querying, and query only the third kind.**
Here is a table demonstrating the idea behind proofreading. The first column shows what is on the original manuscript; the second column shows how the manuscript was typeset; the third column shows what the proofreader should do.
Simple enough? Evidently not quite, for job candidates go wrong in two ways. First, they fail to compare closely enough, so in passages where all seems well in the typeset version, they miss the second type of error.
Worse, they query all three types of errors, instead of only the third. This is profoundly unhelpful in real life. It virtually defeats the purpose of proofreading, which is to flag unresolved issues—and only unresolved issues. Flagging nearly everything the editor marked for correction is tantamount to asking “Did you really mean to correct this?” when it is obvious that she did. It makes extra work, since she will have to check in each case. She might as well have proofread the thing herself.
Perhaps the concept of proofreading is trickier for a generation brought up in the digital age of typesetting, but fortunately, once it is understood, proofreading is the easiest of all editing tasks. And fortunately for proofreaders seeking work, there are still plenty of ways typesetting can go wrong.
______
*The most common error is sloppy handwriting. I feel hypocritical mentioning this, because I know I would never hire myself for a job that required neat writing. But even so, when I write something that I know must be read by colleagues, I take care over it. I make a habit of writing in pencil, and I often erase and rewrite. Bottom line: if a potential employer can’t read your test, and part of the job involves marking up copy for typesetters, you’re toast. So if you are going to be tested, and if you know your usual markings look like the paper in your gerbil’s cage after a week, take a couple of sharpened pencils and an eraser with you. If you forget, ask for them. (Yes, you’ll look like a loser in the moment, but it’s better than making a mess in ink. And depending on the competition, you might still have a chance.)
**In real life, proofreaders are not always charged with querying anomalies, and excessive querying that amounts to second-guessing the copyeditor is not the goal.
The inability to separate copy editing from proofreading is one of the biggest problems we face where I work, I think. Proofreading here is basically just copy editing on a typeset page, which means that everyone feels free to make fairly substantial changes. It tends to draw out the typesetting process and introduce unnecessary errors fairly late in the process. So far my efforts to try to differentiate the two have been pretty fruitless.
Posted by: Jonathon Owen | 03/05/2013 at 12:44 AM
When I was a copy editor, I was "promoted" to a hybrid copy/proof editor, and we did everything on the computer. This kind of notation is unusual to me because of that.
That was a heck of a lot of work for one person to do though, so it's good to see that traditional companies won't give me as much of a load of work when I find one to hire me.
Thanks for the blog post. I really thought it was just going to rehash what I already knew, but it's added to it instead.
Posted by: Jacqueline Kathleen | 03/05/2013 at 09:21 AM
I am also one of the hybrid variety, and recently my company decided that project management would be a nice complement to my editorial skills. Now I route things to myself, copy edit them, put them into production, and proofread them. It does cut down on arguments between the three people, but that line of differentiation you described so well has become even more fuzzy and I believe quality has suffered because of it. Your post may help me explain the problem to management.
Posted by: Sheeshdbq | 03/05/2013 at 01:50 PM
I wanted to say that this is proofreading against copy. The only times I've proofread against copy have been the proofreading course I took and an interview test. The few proofreading jobs I've had (I'm more of a copy-editor) have been proofreading blind, and the proofs I've seen other that other people have read have been proofread blind as well.
Posted by: Amlees.wordpress.com | 03/11/2013 at 04:13 AM
As someone who has had to go through these tests, I'm glad reading this that I am not the only one who ever had an issue with proofreading tests!! :)
Posted by: McKinneyPR | 07/15/2013 at 09:07 AM
There is another distinction to be made in the age of ebooks. That is the kind of errors made by the electronic encoding of existing copy -- photographic process -- for translation of published books to the Amazon Kindle electronic format (Mobi). An existing book, that has been copy edited and proofread, is photographed by a camera. The images are then "understood" by a computer as text, using OCR, Optical Character Recognition. There are many errors that stem from the inability of the computer-linked camera to understand the language of the text. The process produces ludicrous and fairly frequent errors. It is apparently not very familiar to readers, who blame the author or the publisher of the original print book, judging from reviews of these botched books. It is sad, when a good author goes unread because the Kindle text is unreadable electronically, thought the Dead Tree Book was nicely produced.
I wind up buying the book twice, once in Kindle format, and once in its published version. As long as the published version is still in print, that is. Some of the errors of the eye are difficult for humans to pick up unless they are alert to the kind of mistakes made by the machine reader -- for example, "stlll" for "still," or, even easier for the machine to do, "fiill, from "full." Often this latter misreading becomes "fill" instead of "full."
I got two or three books like this in my first batch of Kindle reading, and compulsively went through them, using the tool for marking errors in the text "Report Content Error" which allows for the error to be called "Typo", "Formatting", "Image", or "Other." I used "Other" to indicate OCR mistakes. I gradually, for self-protection, checked the negative reviews for comments on "proofreading," and when in doubt downloaded only a sample. Unfortunately, sometimes only the samples are properly proofread against the printed versions.
Amazon is now issuing "updated editions" of some of these, as free replacements for those who bought the books with uncorrected OCR text. And a month ago they were advertising for copy editors/proofreaders. I doubt that there were errors on the same scale in the production of Nook pdb books, as I read many well-produced pdb editions obtained through Fictionwise.
Yes, there a good Kindle editions, as well. Some top publishers have good Kindle editions; a few do not. Books that have gone from publisher to publisher to Amazon's Kindle Division are most likely to be flawed in this way. At a guess, the typesetting was done once, and discarded.
Any insights here would be appreciated.
Posted by: Sigrid Peterson | 07/28/2013 at 05:25 PM
Nice patronising and stereotypical judgements about the younger generation there. Too bad your own article is published online and also has its own grammatical errors. Or is that errers? I'm just a young digital ideeot and totally inept at this sort of thing.
Posted by: Brighton87 | 10/01/2013 at 05:02 AM
Brighton, would you like to be more helpful and specific?
Posted by: Carol Saller | 10/01/2013 at 08:56 AM
Great post :) I'm a proofreader myself, although in a past "life" I've hired employees and always required a test for grammar and spelling :) I did catch an error, though -- you have "rain" being changed to "reign" and it should actually be changed to "rein".
Posted by: Caitlin Pyle | 06/19/2014 at 10:40 AM
Caitlin, thanks, but the mistake was intentional, to show how a proofreader would query the mistake. Please look at the third row in the third column of the table.
Posted by: Carol Saller | 06/19/2014 at 10:56 AM
Tnx
Posted by: Mithila Akter | 11/28/2014 at 05:58 AM
I was finding Wannabe Editors! Thanks for some good guides! In fact i got some better reviews of Proofreading Test from- http://proofreading-guide.org/
Posted by: Mithila Akter | 11/28/2014 at 06:04 AM
Nice reading. I recently joined www.eangel.me it's an online proofreading service for emails mainly.
Posted by: Sigal Cohen | 02/26/2015 at 08:05 AM
Cool article, Carol! As displayed in some of your readers' comments, I can see there are always those who challenge someone who is the local authority on grammar and punctuation (often making their own mistakes in the process).
Try maintaining a relationship with someone who finds out you're in Mensa and then addresses you as "Mensa Boy" every time you make a mistake! Oy!
Posted by: J Henry Harrison | 08/30/2015 at 01:13 AM
when i started blogging i had issues with proofreading until i came across a good proofreader fiver.com/anniewrites4u. she did a perfect job and i still use her till date. thanks for the write up
Posted by: MareeamG | 06/28/2016 at 07:43 AM
Thanks for getting this info out there! Proofreading is for verifying the final copy is ready to publish--nothing more!
If only this were conveyed in public school or otherwise made public knowledge.... It seems like such a small thing, but considering the excessive amount of time my grade school curriculum spent on English Proofreader's Marks, it should have been addressed.
Is there another way, besides informative blogs like this one, to reach more people? Maybe if all proofreaders gave Google feedback on its definitions for words like 'proofread'? And promoting such a collaborative effort on National Proofreading Day? What do you think, Carol?
Posted by: Cato Alexerratus | 10/22/2016 at 10:37 PM
Cato, I appreciate your enthusiasm!
Posted by: Carol Saller | 10/23/2016 at 08:42 PM
This is a valuable insight into the editing process. I have recently finished my English degree, and I have always had the intention to become an Editor, yet I find myself with very little clue on how to go about it. I bought myself a few books, including Copyediting and Proofreading for Dummies. I hope that these books will shed some light on the work involved in being an editor. I have even tried to take a few online tests. Is there any advice on how to have recognizable skills and how to look for work as an editor?
Posted by: Daniel Brennan | 07/12/2017 at 11:51 PM
thanks for sharing this
Professional Document Editing
Posted by: Professional Editing | 02/24/2022 at 04:56 AM
Dear Carol,
I am a member of ACES and a huge fan of yours. One of my favorite books is "The Subversive Copy Editor." I am interested in proofreading tests and wasn't aware of any that compare a manuscript to the final layout, as you described in your blog. Can you recommend a test that would evaluate that? I can only find "cold" proofreading tests and multiple choice online. Any insight you have would be much appreciated! Thank you for your time.
Posted by: Lisa Rinkus | 06/24/2022 at 08:52 AM