Things I Look For When Beta Reading

Since my most recent project is in the querying trenches, and I’m not quite ready to start my next project, I let a friend who’d asked a while back know that I had time to beta read their current project. While I know every beta reader has their own process, these are some of the things I like to look for when beta reading.

Different authors want different things from their beta readers, and what an author needs can vary wildly depending on where in their writing process they are. I typically work with finished and edited manuscripts, but some people use early readers — sometimes known as critique partners or alpha readers — to get feedback early in the drafting stage.

Obviously, if an author only wants feedback on certain things, that’s what I’ll give them. But, while I’m working on becoming more of a dev (developmental) editor (someone who helps with story and pacing), I naturally do a fair amount of line edits (wording choice and sentence flow), and even a touch of copy edits (punctuation and grammar).

What I look for when beta reading

1. Plot holes – Did a character disappear? Did the setting change? Do the plot decisions make sense? (dev)
2. Plot pacing – All scenes typically exist for one of three reasons: plot, world-building, or character-building. If your scene isn’t doing at least two of the three, you usually need to either add to it or remove it. (dev)
3. Resolutions – If we’re focused on fixing a problem, the problem needs to be resolved — either in a good way, or mad worse, or intentionally back-burnered, but not skipped over. (dev/line)
4. Page pacing – I find it best to switch between dialogue, narration, action, and description regularly. If you linger too long on any one thing, readers’ minds start to wander. (line)
5. Clarity in who is saying/doing an action – Pronouns are handy, but remember they refer to the last person (of that gender) referenced in the sentence or paragraph. I try to use names (or descriptive titles) at least once a page, but definitely during the first reference in a chapter. (line)
6. Smooth phrasing – If I have to read a sentence more than once, I check to see if it’s me or the sentence. If it takes me more than 2 reads to parse out what it means, I flag it for re-wording, often offering suggestions. If a sentence reads clearly, but the phrasing doesn’t sound natural for the character or setting, I’ll flag it. (line)
7. Word choice – Not all characters should talk the same or reason the same. I am broadly read, so if I have to look up a word for the meaning, I’d suggest either making it clear in the first usage, or finding a different word. Obviously, industry-specific jargon, especially in dialogue, would be the exception. But maybe describe the word in the narration. (line)
   
   Note: My librarian mother called me out on using big words when smaller words would do. (After a fair amount of incredulity and sulking) I realized I had a bad habit of sacrificing readability and accessibility in my pursuit of precisely the right word. I’m working on it.
8. Factual errors – Whether it’s wolves on the savannah or the sun rising in the West, while I don’t know everything, if something sticks out to me, I’ll note it.
9. Characters acting out of character – Sure, we’re not all consistent with our behaviors, even if we subscribe to certain moral codes. But, if a character acts outside of my expectations, I’ll want a reason.
10. Characters being true to themselves – Whether I can see exactly why they made that choice, or I’m celebrating their wins, you’ll see me start to forget I’m editing and start talking to the characters in the comments. That means that part is WORKING.

Have you done any beta reading? Are there other things you look for in the writing?