We asked our parliament of wise owls, all Advanced Professional Members, about editing speeds: how long does it take to edit or proofread something? What’s fast or slow, and is that even the right question?
Few topics in the editorial world are more prone to oversimplification than editing speeds. I suspect some of this comes from clients, for whom a supposedly ‘standard’ speed might be either (more positively) a helpful starting point for fee negotiations or (more negatively) a crude tool used to push back against requests for fee increases. The most extreme example of the latter I ever encountered was when years ago, as a very new proofreader struggling with hideously messy proofs, I told the client how quickly I was working – a speed I now know with experience was reasonable – and was informed that they ‘knew children who could read more quickly than that’ (and yes, they did say ‘read’ rather than ‘proofread’). I was far too timid to respond with any fortitude at the time, so please forgive me the self-indulgence of this delayed public catharsis.
So, clients may have an idea of how quickly we should be working, and that idea may or may not be based on sound knowledge of what professional editorial work entails. However, as editors and proofreaders, we care about this too. We naturally want to know how our speed compares to that of our colleagues. And speed = time and time = money, so knowing how quickly we edit is vital to ensuring we are quoting appropriately.
Looking back at my records of over 600 projects, I’ve clocked up editing speeds between 250 words per hour and (very occasionally) 10,000. Clearly, then, it would be nonsensical to refer to ‘my editing speed’ in the singular, but it would also be pointless to think of either extreme as ‘slow’ or ‘fast’. For example, 500 words per hour seems slow on the face of it, but it might be fast for especially complex editing of text by someone writing in their second (or third or fourth) language with structural changes.
Thinking about your editing speed is crucial, but ‘fast’ and ‘slow’ are only relevant as far as you can contextualise them within your own work – its difficulty, detail, workflow and so on. And, equally, before you compare your speed with that of another editor, make sure you understand what you’re comparing yourself against – in essence, what kind of work the other editor does.
There are two ways of looking at speed: how many words per hour you can deal with, and how intensively you can keep going. Do you spread a five-hour job over two days, a week, or get it all done in one day? Nor will your speed be consistent over all the stages of a job. I take longer per word checking and fixing bibliographies than the running text.
My own belief is that the right speed is the fastest speed you can safely go while fulfilling the brief, giving good customer service and maintaining your own equilibrium.
It’s pretty obvious that speed is dependent on four things:
- the condition of the manuscript
- what the client wants you to do to it, and how many times
- your own expertise, and
- everything else, by which I mean the way that life gets in the way of work and sometimes work gets in the way of other work.
Because of these four factors, it’s not usually sensible to try to compare your speed with other people’s except in the most general way. What you can usefully do, though, is keep records of your own speeds. If you’ll pardon me a plug for the Going Solo Toolkit for CIEP members (you’ll need to be logged in), the Work record spreadsheet helps you to collect all the information about a job that will give you a feel for your range of speeds for a given type of work, as influenced by those four factors.
Finally, don’t be seduced by the idea of an average – my fastest is three times my slowest, so I need to discover factors 1 and 2 in order to be able to give a decent quote.
In my experience, it’s helpful to be able to think two things at once about editing speeds. First, it is definitely useful to have an idea of how long it takes you to proofread or copyedit a particular number of words. This will be an average figure, depending on the state of the original text, but having such a figure to refer to will help when it comes to quoting for work.
But at the same time as it’s useful to have benchmark figures in mind, it’s also important to remember that they mean nothing. Every project is different, every author is different, every brief is different, every budget is different (unless you’re working on a series of similar documents for the same client). Crucially, every editor is different. Faster editing isn’t necessarily better editing, although very slow editing is likely to cost either your client or you dearly.
When I’m mentoring editors, I tell them that in the beginning, it’s better to focus on accuracy than speed. You don’t ever stop focusing on accuracy, of course, but the speed does improve of its own accord over time – and of course there are all sorts of things we can do to increase it further. But that’s another story.
Asking how long it will take to edit or proofread a document is akin to asking what it will cost. As with pricing, it depends. I know from experience that my average editing speed is around 2,500 words per hour. If I’m given a text that is very clean, which is to say the writer has already gone through it to check for typos, errors and other possible issues, and for clarity, I could work as fast as 3,000 words per hour.
However, I have a number of clients outside the UK whose first language is not English. I’m likely to receive a file from them that has either been written by them or badly translated. For those clients, I will probably have to do a lot of rewriting and thinking through what they actually mean, and my speed will be more like 1,000 to 1,500 words per hour. And I could be as slow as that even when editing for someone who does speak English as their first language, if the text needs a lot of work, or if there are a lot of tables.
I log all this data on a spreadsheet that also records my time for each client, so I have a good idea of my range of speeds for different proficiency levels in English and the condition of the text. The data acts as a good comparison chart when I’m approached by new clients. I always ask for a sample of the text, as I can assess my likely speed and that will form part of the pricing. My speed includes everything: hours spent on the actual editing or proofreading, plus time reading the style guide if there is one and other prepping, plus all the time taken to administrate the job – that’s the number of words divided by the total time spent on the job.
As with so many aspects of editorial work, the simplest way to sum up the answer to a question about editing speeds is ‘it depends’. Each editor, client and project combination is different, and thus so is the time the edit or proofread will take.
What are your experiences of editing and proofreading speeds? Do you see yourself as ‘fast’ or ‘slow’, or somewhere in the middle? Let us know in the comments below.
Increasing editing and proofreading efficiency
If you are looking for ways to use your working time more efficiently, there are plenty of CIEP resources to help.
- Efficient Editing: Strategies and Tactics (course – webcast)
- Increase your editing efficiency in Word (fact sheet)
- Word for Practical Editing (online course)
- Getting started with macros (fact sheet)
- Sue Littleford’s Flying solo column (on the CIEP blog)
- Andy Coulson’s What’s e-new? column (on the CIEP blog)
The Chartered Institute of Editing and Proofreading (CIEP) is a non-profit body promoting excellence in English language editing. We set and demonstrate editorial standards, and we are a community, training hub and support network for editorial professionals – the people who work to make text accurate, clear and fit for purpose.
Find out more about:
Posted by Abi Saffrey, CIEP blog coordinator.
The views expressed here do not necessarily reflect those of the CIEP.