Among the greatest gifts one writer can give another is that being a beta reader. A beta reader is a volunteer who reads over a rough manuscript and offers feedback on what’s working and what’s not. This feedback can span the gamut from simply a general reaction to a full-on critique. But not all beta readers are created equal. Just as you can learn to be a better writer, you can also learn to be a better beta reader.

Earlier this year, I receive the following email from Archie Kregear:

I have been doing a lot of beta reading lately. I was looking for a guide/checklist to help folks like me to be a better beta reader. The critique group I’m a part of is prolific, a beta read a month. I’ve searched through your site and nothing on the details, just etiquette.

He’s right. I haven’t written much about beta reading for the same reason I don’t write a whole lot about editing in general, and this because the foundational principles of both are no different from those of good writing. If you know how to write a solid story, you’ll know how to edit one. Indeed, much of the trial and error of learning how to write solid first drafts begins in the trenches of troubleshooting our sloppy first drafts and figuring out how to fix them.

Creating Character Arcs (Amazon affiliate link)

The simplest answer to “how to edit” is “learn about story structure, character development, good prose, pacing, etc.” The same rules apply in beta reading. However, because of the extra accountability we bear in taking on a beta-reading job, it does deserve some extra forethought.

Most writers will learn some of their most valuable lessons thanks to beta readers. My own early experiences with beta readers transformed the way I approached story, as well as boosting my confidence. But most writers will also encounter a beta reader or two who, despite their best intentions, do more harm than not—either by offering faulty advice or by undercutting confidence. The entire writing community benefits when we all try to become the best beta readers possible.

To that end, here are my top thirteen tips for improving your editing game and becoming a better beta reader. Most of these tips will help you in editing your own stories as well!

Set the Ground Rules

1. Get Very Clear on What Kind of Critique the Author Is Asking For

The first and foremost rule of beta reading is that you are there to serve the story. If it’s important to put your ego in your back pocket and sit on it when you’re editing your own stories, it’s even more important to do so when editing for someone else. The first step toward that end is to make sure both you and the author are on the same page by making sure you understand exactly what kind of critique the author is asking for.

• Do they want you to simply read the book over and offer a general opinion at the end: like or dislike?
• Do they want you to offer a detailed content edit—a commentary throughout on what works and what doesn’t?
• Do they want a structural edit that critiques plot, pacing, and character arc?
• Do they want you to get down and dirty with a full-on comprehensive line edit that offers suggestions not just about the story but about the prose?
• Do they want you to note typos or leave them alone?

It is also incumbent upon the author to be clear (and get clear) about their wishes. Nothing is worse for a beta reader than spending weeks thoroughly editing a piece only to realize the author was hoping for something more lightweight.

2. Communicate About How to Mark Suggested Changes

You’ll want to discuss the best way for you to mark your suggested changes. Track Changes is still the best method I know of. As long as both parties have access to Microsoft Word, you can use this tool to easily share your deletions, edits, and comments. The author can then just as easily decide which changes to incorporate or bypass.

However, you might agree that you both prefer working in a Google Doc. You might even ask for an epub you can read (or a doc you can convert to epub) on your Kindle. You can read at your leisure, making notes as you go, then copy/paste them from Kindle Highlights on your computer for sharing with the author.

Don’t be afraid to ask for what’s best for you. At the end of the day, you’re the one doing the favor here. Within reason, it’s fine to ask for whatever setup will be most convenient for your needs.

3. Agree on a Reasonable Deadline

This one is important for both the author and the beta reader. Depending on the length of the story and the depth of the edit, beta-reading can represent a significant time investment. You’ll want to realistically assess how much time you can put into the project every day and figure out about how long it will take you. Then do your best to honor that.

Many a writer can attest to the frustration and disappointment of trusting a beta reader who never comes through or who keeps fobbing off the deadline. Obviously, life happens, and beta-reading is probably not going to be your highest priority at any time. But once you’ve agreed to help out a fellow writer, do your best to honor that commitment. If you can’t, at least make a point to reach out and let the writer know you’re not going to be able to fulfill the agreement.

Pro Editing Tips

4. Be Specific

Now we get down to the actual beta-reading. How can you respond to someone else’s story in the way that will most benefit them? Perhaps the single most important offering you can make to another writer is simply that of being specific. If you don’t like something in the story, try to figure out why you don’t like. If you feel making a big change would benefit the story, try to figure out why you feel that way.

To some degree, any level of editing will always be subjective. But try to get clear on when the suggestions you’re making are based on logical reasons and your own understanding of story—and when they’re based on nothing more than your personal preferences. Your preferences as a reader are absolutely still valid and can be usefully shared with the author, but they should be noted as your preferences, not as universal rules.

Bottom line: always try to be clear with yourself about why you’re making suggestions. Not only will doing so better serve the author, it will also help you further hone your own storytelling instincts and skills.

5. Map Out the Ideal Structural Timing Based on Page Count

Structuring Your Novel (Amazon affiliate link)

If the author has asked for a plot edit, one of the key things you can examine for them is how well the story’s structure works.

When beta-reading for someone, one of the first things I do is find the total page count of their story. I divide that into eighths to find the ideal timing for each of the structural turning points, then scroll through the document and add a comment as a reminder to myself to check how well the story’s structure is holding up.

For example, if the book’s Word doc is 300 pages, I would make notes as follows:

Inciting Event: p. 37

First Plot Point: p. 75

First Pinch Point: p. 112

Midpoint (Second Plot Point): p. 150

Second Pinch Point: p. 187

Third Plot Point: p. 225

Climax: p. 263

These comments are just for my own purposes, and I will delete them as I go. It’s also important to note they are indicating the ideal structural timing. Very few stories will line up page-perfect. But the reminders will help you keep track of whether or not the story includes all the important structural turning points, how close they are to the ideal timing, and how much the pacing is affected one way or the other.

6. Don’t Just Point Out Problems, Offer Solutions Where Appropriate

Writers don’t need (and won’t always appreciate) if you try to brainstorm solutions for every problem you point out. You want to give them clues and nudges to help them fix their story’s problems in their own unique way. But simply pointing out problems with no explanation or suggested solution can also be less than helpful. Simply saying, “The female lead’s emotional reaction doesn’t ring true here” might not always be enough. You could instead go on to suggest, “Maybe this would be a good place for her to express a little confusion and vulnerability.”

7. Point Out Scenes That Don’t Move the Plot

This one is always helpful. Particularly in first drafts, writers aren’t always aware they’ve included scenes that really don’t do much. If you find yourself bored when reading a scene or feeling you’ve already read this scene several times before, be sure to note that and note why. If you’re familiar with scene structure, you can also examine that to discover any broken or missing pieces that may be interrupting the forward movement of the story.

8. Make Note of Any “Tic” Words That Pop

No need to go overboard on this one, but if you start to notice the author consistently uses one particular word, make note of that and suggest they run a search to discover how often they really do use it. However, don’t ding someone for using words that are your pet peeves or that you’re noticing only because you know you have a tendency to overuse them.

9. Create an “Edit Letter” to Address Major Issues

At the end of editing, professional editors will send clients a document summarizing all the major issues they’ve found in the story. While in the midst of your beta-reading, you can keep a running list of issues you wish you discuss with the writer by the end.

I find it most helpful to divide the letter into broad sections with headers, particularly focusing on major areas such as “Plot Structure,” “Character Development,” “Dialogue,” etc., as well as any issues that are specific to the story.

You can also use the following list to ask yourself helpful and thorough questions about your reaction to the story. You don’t necessarily have to share every answer with the author, but scanning through the list may help you clarify your own reactions to the story.

>>Click here: 17 Questions for Critique Partners

General Guidelines

10. Explain Your Reasoning Wherever Necessary

Although you don’t want to preach at the author, don’t assume he knows what you know and will understand why you made a particular change. For example, if you edit a sentence to make it more active, you may want to make a little note, explaining your reasoning. Beta-reading is often a mutual learning experience in which writers help each other improve their craft. Don’t necessarily assume you know more than the author, but don’t be afraid to offer helpful tips where appropriate.

11. Try to Interact With the Story Simultaneously as Reader and Editor

Beta-readers wear multiple hats. Not only are you (probably) a fellow writer who is approaching the editing of this story as if it were your own, you’re also interacting with it as both an objective reader and an editor. Try to balance those last two identities. Don’t get so consumed by the fiddly work of ruthlessly editing that you don’t occasionally pull back and interact with the story as if you were a random reader who had purchased it. As a beta reader, you’ve volunteered to look under the story’s hood, but the ultimate test of whether or not a story works is whether or not it works for a reader. If you’re able to give your fellow author your perspectives as a writer, an editor, and a reader, you’ll have all the more to offer them.

12. Honor the Author’s Vision for the Story

This one is super-important. Respect the author at all times. This is their story, not yours. They have their own vision for it, which may entirely different from the vision you would have had. What they want the story to be may also be different from what you, as that random reader, would prefer to read. As a beta reader, you’re not here to mold their story to your preferences; you’re here to help them realize their best vision for the story.

One of the surest ways to do this is to outright ask the author: What’s your intention for this story?

If they can provide a story summary in the beginning, that can often help you determine what type of story they intend this to be.

13. Don’t Forget to Point Out Things You Like

If you’ve ever been on the receiving end of a critique, you know how brutal it can sometimes be. Even the best of critiques (and often exactly because they are really good critiques) can leave the author feeling overwhelmed. As a beta reader, your primary job is to help the author make the story better by pointing out all the things that don’t work. But pointing out the things you do like can be just as helpful in the long run. Anytime something makes you smile, laugh, cry, or experience any other strong reaction, be sure to make a note. And when it comes time to comment on the story as a whole, try the “compliment sandwich” method. Start by telling the author what you liked best about the story, then share your suggestions for improvement, then end on a final encouraging note.

***

The most important guideline for being a better beta reader is simply the old Golden Rule: Critique other authors exactly how you would like to be critiqued yourself. Respect their hard work and their passion, honor the story they’re trying to tell, be honest but also kind, keep your deadlines and commitments, and enjoy sharing with someone else your deep love of storytelling.

Wordplayers, tell me in the comments! Are there any other suggestions you would add about how to be a better beta reader? Tell me in the comments!

Click the “Play” button to Listen to Audio Version (or subscribe to the Helping Writers Become Authors podcast in Apple Podcast or Amazon Music).

___

Love Helping Writers Become Authors? You can now become a patron. (Huge thanks to those of you who are already part of my Patreon family!)