GUIDELINES FOR BETA READING

Positivity: while we’re not here to falsely boost a writer’s confidence, we’re not here to destroy it either. Supportive, kind words should be sprinkled throughout the report to encourage the author in the right direction. Anyone can find things that are wrong – criticism is easy. Taking the time to observe an author’s strengths takes more energy and talent.

Language: Try to keep in mind your feedback is a subjective opinion and not absolute; therefore, it might differ from other readers:

• Use words such as “I thought” and “I felt”, rather than making statements.
• When making suggestions use words like: “Perhaps, might, consider.”
• Avoid blanket statements such as “all, always, everything”, try softening with “often, most, quite”.

Brevity: Yes or no single sentence answers are not sufficient. Please support your views with reasoning.

Wordiness: The expected report length is 12 pages, no more than 14. While you are expected to answer each question fully, please don’t venture beyond a maximum of two paragraphs per question – be succinct with a couple of examples of an issue, rather than pointing out every instance. This guideline is in place to stop readers from overdelivering, which then devalues the reports of other readers who follow the guidelines. If an author requires a more detailed report with editorial advice, they can book a full assessment. I don’t want to set word counts, but let’s say 120-150 words per question is a fair limit.

Cut and paste: Apart from answering a question, you may additionally include one or two examples pasted from the manuscript to illustrate your point. You should not be keeping a tally of every occurrence of an issue and the relevant page numbers to include in your report. This applies to things like writing style, spelling or punctuation errors – that job belongs to an editor.

Core theme: Please pay attention to answering the actual question – what does the story mean? What big life question/s are asked and answered or addressed?

Opening scene questions: This is not a place for a rehash or summary. Think about whether the scene will hook readers or not  and why. Do not just report what happens in the scene. The author knows – they wrote it.

Editorial advice:  This is not a beta reader’s domain. A beta reader’s task is to give big-picture feedback on how they felt about the story and characters, not to tell an author how to write. You may refer the author to the links I have included in the reports, but no other links, and no other advice is to be given apart from answering the questions asked.

Genres: Please do not tell an author you don’t usually read the genre you are giving feedback on. If you apply for a read, you should be familiar with the genre. I have no issue with readers extending their genres, but you first need to read widely first so you are knowledgeable of readers’ expectations of a particular genre.

Ratings: if you feel the need to give a reader a rating of 1 or less, please simply put that you don’t think that aspect of the manuscript is ready to be rated (or something similar without being cutting).

State of manuscripts: Please do not tell an author their manuscript is not ready for a beta read. I do not subscribe to the notion that beta reads are a final step in the writing process before submitting to publishers. We accept manuscripts at any stage so anyone from beginners to seasoned writers may obtain feedback. You are always provided with a sample of the manuscript to judge whether you feel you are prepared to take on the read or not.

Contact with the author: Readers are not to try to make contact with authors, or request a copy of their book. If the author offers as such, I will ensure you receive the book. If the author requests a review on publication, I will pass this information on too.