I often see comments from people who would like to be a beta reader but are not really sure how to go about it. This is to answer some of the most common questions.

How do I become a beta reader?

Just find yourself a writer who needs a beta reader and volunteer. It might be through your local writing group, or through goodreads, or some other place where you can find writers. Good beta readers are always in demand, and writers are usually looking to build up a regular team.

What do I have to do?

The basic idea is to read the manuscript (often a novel, but it could equally be a memoir, or non-fiction), and then tell the writer what you thought of it. The important thing is to be honest and as specific as you can. They might have a list of questions they want answered – are the characters believable? did the setting sound realistic? – or they might just want your overall impression.

How long does it take to do a beta read?

How long do you usually take to read a book? Some beta readers can provide feedback within a couple of days; others take longer. As long as you and the writer understand how long it is likely to take, there is no problem.

Do I have to be honest?

Yes, but you also need to be kind. The writer has put in a lot of work, and you should always bear this in mind when you give feedback. it’s also good to comment on things that you enjoy or feel works well, so that your feedback is not all negative.

Do I have to be a writer myself?

No. You just have to be a reader. Make sure you read genres you feel capable of commenting on, and remember that the writer is looking for feedback to help make their work better. You don’t have to tell them how to fix any problems you find; you just have to point out anything you see as an issue. Is the pace flagging? Do you find the character unlikeable? Is that event unbelievable? Once you’ve pointed out what you see as a problem, it’s up to the writer to consider your feedback and deal with it if they consider it necessary.

Do I have to be good at grammar/spelling/punctuation?

No. It’s not the beta reader’s job to point out errors like that, although some do anyway. You are the test reader, giving the writer an idea of your response. The writer has spent a long time very close to their manuscript; they need someone to look at it with fresh eyes and check the content for them to see how readable it is.

How do I actually read their work?

It’s possible you might be given a printed copy, especially if you know the person offline. It’s more likely that you’ll be provided with an electronic copy. This might be a Word document, PDF, or a format suitable for an ebook reader. You can usually ask for the version that you would find easiest to work on.

Do I do a written report?

Some beta readers provide comments through the manuscript; some provide feedback via a written report. Some do a combination of both.

Do I have to sign a non-disclosure document?

Some writers might ask you to do that, but most don’t. However, it is expected that you’ll keep their work confidential and not pass it on to others. The same goes for discussing it with other people. On the other hand, once the book is published there’s nothing stopping you promoting it to your friends!

Can I charge for beta reading?

Some people do charge for beta reading. The advantage to you is that you get something back for your time apart from the pleasure and experience of helping out, and the advantage to the writer is that they can be pretty sure you’ll provide feedback. On the other hand, there are plenty of people around who offer a free read. Some writers offer a copy of the finished work as a thank-you, or a mention in the acknowledgements. If you want to make a charge, then I would recommend building up a reputation, collecting testimonials and then testing out the waters, but any beta read fee is unlikely to reflect all the time you spend working on it, unless your fee is very high – and then you’d better be very confident that you’re offering a high level of help and expertise.

What if I really don’t like what I’m reading?

It happens sometimes. A manuscript for beta reading can be very rough and unfinished, and can be tough to get through. Just do your best, and at the very least give the writer some feedback to indicate why you found it so hard, whether it was because the writing style was too rough, the main character too unsympathetic or the pace too slow. The tougher the read, the more important your feedback is. If you can’t finish it, then try to explain the problem.

What if real life intervenes and I just don’t have time?

If you take on a read and then find you can’t complete it, for whatever reason, please do let the writer know. The same applies if you find it will take longer than you thought. Communication is key. Remember that you may be the first to read a piece of work apart from the writer, and it is their precious baby. If they don’t hear back from you, they might assume it’s because you found it terrible and can’t bear to tell them, whereas in reality it’s because you’ve had the flu!

Please note that this is how I personally work – it isn’t a rigid way that the job must be done. I suspect there are as many different ways of working as there are beta readers. Also, this service is bordering on an alpha read or critique, rather than just a beta read.

When an author contacts me I’ll book them in and let them know when I expect to get to their project. Sometimes I can take one on immediately, while at other times I’ve run a waiting list of up to six months. When I receive the file, either in  Word or PDF version, I start an Evernote file for the work, giving title, author and page count (with word count if known). I add any synopsis or other information I’ve been given, plus any specific things I’ve been asked to look out for. I put the date I received the file and any deadline or estimate for finishing. I also confirm to the author that I’ve successfully opened the file and saved my own copy to work on. It helps if I also have some information on the writer’s experience and their intentions for the manuscript (generally, seeking an author or self-publishing).

As I read, I make notes in the project file – like a running commentary, on something I don’t understand, something that makes me laugh, something that’s inconsistent… I’ll also add general comments in the Evernote file under heading such as Setting, Plot, Characters, POV.

At the end of a session I’ll note in the Evernote file where I’ve stopped, and I’ll also summarize what’s happened in this session, so it’s easier to pick back up after a day or so away. This is also a good way of assessing the plot – is it easy to say what happened in each chapter? Did too much happen to explain quickly? Did things just drift along with nothing really happening at all? Is it clear at this point what the main character wants and what’s standing in their way?

I try to read at least 50 pages from a project in a session. Any fewer and it takes too long to get through, and it also becomes bitty in my mind and hard to keep straight. Any longer and I lose concentration – although if a book is close to the end of the development cycle and there is less to comment on I can become more involved and get further in the session. I might switch projects and continue if I still have time available, but I have to be aware of other work that has to be done as well, and in order to keep the beta fee as low as I can, I have to prioritise the higher-paying work.

When I’ve finished a project, I’ll wait until the next day to compose a report for the author. This allows my thoughts to gel. Sometimes I’ll go back and re-read the opening, adding a couple more comments – things that were unclear to start with sometimes come clearer on a second read, or things that seemed unimportant are noticed more – or important things are missing.

I’ll then write back to the author, attaching the project file with the comments, and include a general report as well. Sometimes the author has further questions for me, and I’m happy to carry on the conversation with them, and clarify anything. However, it’s entirely up to them what notice they take of my feedback. I also focus on finding and explaining problems, rather than how to fix them.

Beta reading is not like normal reading

For a start, I can only beta read either on my computer or on my laptop, so I can add comments. Beta projects are often unpolished, and therefore do not flow as easily as finished works, and this can slow down the reading considerably. I’ve had projects where I’ve had to train myself to ignore punctuation because, the use of commas, is fairly arbitrary making it, impossible to use it to, help with understanding.

I often have to go back and re-read sections, especially in the first few pages. What have I taken in? What have I missed? Has the author introduced too many characters too quickly? Is there too much background information given, rather than getting straight to action?

I’m constantly questioning what I read, and this means that I have to check facts – what exactly was she wearing? Did we get told she changed clothes? Is it possible she changed but we weren’t told? How many days have passed? What day of the week does this work out as?

This means that beta reading takes far more time and concentration than normal reading. It is not a way to get free books to read! It requires time and patience, and a good understanding of how books should flow. It requires tact and patience in explaining issues to the author. I am not – at that point, at least – the book’s editor or proofreader, and I will not point out every single mistake (more on the different roles in another post) but I will point out consistent errors and issues, and I will point out when a sentence does not get its message across clearly. I can pick up dictation errors if the author has used dictation software. I will point out where punctuation/grammar obscures the meaning. I will also point out general writing weaknesses, such as inconsistent points of view or over-reliance on adverbs, if necessary.

The read is focussed on the structure of the story, and while it is not in the depth required by a developmental or structural edit, it should provide plenty of information to help you identify the strengths and weaknesses of your novel and point you towards how to improve it.

All this makes for an enjoyable but challenging way of helping authors to produce their book. It is also a good way for the author to get to know the way I work, and for me to get to know the author and the story, before discussing any further editorial/proofreading work they may require. Part of the beta fee may be deductible from the final fee.