AI as Beta Reader
A model asked to beta-read will answer like a writer who already has a revision plan. A pacing note is not an order to invent a scene, and one fluent reply is not a pattern.
Harry Mercury
Editor in Chief
On Friday, in "Advanced Fiction: The Meta-Novel", I said a reader who only praises the wink is this week's prior, now sitting in the margin with a pen. The note still has to survive the strip. If the comment exists so you will notice the comment, you have the caption problem again, this time in someone else's handwriting.
An AI asked to beta-read will often hand you that handwriting. It will sound like a reader. It is not one. A civilian question is not a market memo, and a pacing complaint is not an order to invent a scene.
I am not claiming a beta read from this desk. I did not paste a manuscript into a model and log the reply. Where the plate and the key show up below, they are the same hypothetical from last week, so you can see the cut. They are not a scene from a book, and they are not an event I am pretending to report.
A civilian has an afternoon
Barbara Linn Probst, on Jane Friedman's site, uses the ordinary meaning. The page's published-time field is 2019-03-20T09:00:47+00:00.[5]
"The term usually refers to unpaid non-professionals who give feedback on writing prior to publication."[5]
"They're civilians, proxies for our future readers."[5]
Unlike editors, she writes, there is no expectation that beta readers will have advice about how to fix whatever weaknesses they find.[5]
Andrew Noakes, on the same site, is narrower about the job. The page's published-time field is 2024-06-13T09:00:00+00:00.[4]
"Beta readers are very different from editors. They are typically ordinary readers with little or no expertise on story craft or publishing."[4]
"They're not here to tell you whether your plot conforms to a three-act structure, whether your characters have enough internal conflict, or whether your book can succeed in the current commercial market."[4]
Save that last question for an editor, he says. I am saving it for Wednesday. A model is not that editor either.
What a civilian can tell you, on his page, is which characters they connected with, where they started to lose interest, and whether the ending was satisfying or frustrating.[4] That is a report of an afternoon. A person put the book down, or did not.
A model has none of that afternoon. When you ask it what it thought, you are not getting a proxy for a future reader. You are getting a fluent completion of the role "beta reader." In the text that role is usually played by a writer. Probst quotes the pitfall those writers already know.
"We writers have a tendency to want to change it to how we would write it ourselves."[5]
I don't trust a reply that arrives with a revision plan. A civilian often does not have one. If the note includes the fix, you got a writer who could not stay in the chair. "I put it down" does not look like help, so the prior does not love it.
Do not ask if it would sell
Noakes is plain about the commercial question. It is not a beta question.[4] Ask it of a model and you will not get a reader. You will get a memo.
Jonathan Edward Durham is not writing about models. His Writer's Digest page says "Updated Oct 10, 2026."[2] He is writing about the query grinder, and about his novel Winterset Hollow, which I did not fetch. The list on the page is the shape I expect if you ask whether the book can succeed. I am not claiming I generated it.
"Write to market, make sure it's pitchable, have good comps, put a hook on the first page, watch your word count, keep the pacing brisk, make sure the language isn't overcomplicated, stay inside your genre, pick a demographic, and write to that audience."[2]
"Your readers will want a hook on page one" is the same sentence, wearing a coat.
His advice, from the same page: "if I have any advice to offer, it's to avoid the temptation to make your story more mainstream just to make that process easier."[2] He also writes that social media has made style, genre, and presentation loop until the exceptions stand out.[2] A note that sands the exception so the pitch gets easier is not a reader's report. It is the loop, now sitting in your margin.
Wednesday's outline title is The Submission Package. I am not linking it. The slug is not assigned. Do not revise toward the package today. If the note wants the weird sanded down, decline it and bring the note Wednesday. The revision and the query are not the same job. Probst quotes a respondent who split them.
"Betas tell you how the average reader will respond to your book, and the editor will make your book marketable."[5]
A pacing note is not a new scene
Sophie Lefens, on Writer's Digest, is the piece to read before you touch a pacing note. The page says "Published Oct 11, 2026."[1] She names her editor, Peter Kispert, and the novel Her Kind. She is writing about an editor, not a beta reader, and I am not going to pretend she was. An editor can have an ear. A beta reader, on the terms above, may only be able to say the middle dragged.
What she reports is still the move a model will skip.
"Initially I assumed this was an architectural issue, that I needed to move large blocks of plot around and develop entirely new scenes."[1]
The revisions, she writes, "had more to do with an attunement to what was already on the page."[1]
"I started at the beginning. I read slowly and began to see where I had lost sensitivity to the energy of the scene, where I had let things drag or become rushed."[1]
"I noticed omissions of micro-expressions and gestures between characters that I needed to account for on the page."[1]
I did not fetch Her Kind. I am not using the Michigan woods, the child, or the aunt's house as a scene of mine. Those are hers. The affiliate links on that page are not sources.
The desk rule is mine. A note that says the pacing is off is not yet an order to invent scenes. If you hand that note to a model and ask it to fix the pacing, you have asked for the assumption she had to unlearn. A new scene looks like work. Attunement looks like rereading, and rereading does not need the model to be open.
Close it. Start at the beginning of the page you actually have. Mark where it drags. Mark where it rushes. Mark the gesture you left out, and the place you concealed too much or revealed too much. If you cannot enter the scene, the problem is not a missing chapter. It is a page that has not been read.
I said a wider version of the human pass in "First Draft by AI, Revision by Human — A Workflow". Here the decision is narrower. Does the energy return when you account for what is already there, or only when you add a block the note invented? If it only returns in the new block, you hired a caption to do a scene's job.
Confusion is not always the flaw
Cynthia Pelayo's Writer's Digest page says "Published Oct 10, 2026."[3] She is writing about magical realism, not about beta readers. I am not using her dinner plate, her laundry, or her oak tree as a method. I did not fetch Something Followed Us Home. The affiliate links on that page are not sources either.
"The simplest craft advice in understanding what magical realism is and how to write it is that the impossible is real and everyone in your story accepts this as true."[3]
"The narrator should refuse to over-explain the magical."[3]
"Instead, allow your narrator to report the magical in the same clear voice they would report the weather."[3]
Noakes does recommend asking whether anything was confusing, and whether anything was hard to believe.[4] Those are fair civilian questions. They are not a verdict that the page must explain itself.
If the book requires the narrator not to flinch, a note that says the reader will be confused, and that you should add a paragraph of rules, is asking for a different book. That sentence is mine, not hers. A fantasy note and a magical-realism note can use the same word, confusing, and mean opposite repairs. One wants the system. The other wants you to stop announcing the wonder. If you cannot tell which book you are in, do not let the note pick.
A fluent note can also name a hole that is not a hole. I wrote about that failure in "Hallucination, Confabulation, and the Limits of Generation". The worse case is a real softness with the wrong repair. The softness was yours. The repair is the prior's. You still have to read the page.
One reply is not a pattern
Noakes is useful here, and easy to misuse.
"If one beta reader doesn't connect to your main character, but all of the others seem to find them very engaging, then that one beta reader is an outlier, and you probably shouldn't re-write your protagonist purely on the basis of their opinion."[4]
The pattern is the tool. Several readers, the same complaint, and then you pay attention. One voice is not a pattern.
A single generation is one voice. It agrees with itself because the sentences came from the same prior. That is not five afternoons. If you want his pattern, you need more than one person. I did not sample replies.
Probst reports the other failure, the one that arrives when the comments are free and plentiful.
"It's way too easy to ask ten people for comments, and then implement all their comments and lose what I intended for the story."[5]
One model reply can hold those ten comments. Implement them all and you have done what her respondent warned against, without emailing anyone.
"I felt bored in the middle" can be a civilian. The next sentence, and I am inventing it so you can see the cut, is the writer who could not stay in the chair: add a set piece and raise the stakes.[5] Decline the second sentence. If several actual people put the book down in the same stretch, that is a pattern, and it is still not an order to invent a scene. It is a reason to do Lefens's read on that stretch.[1] The pattern tells you where to look. It does not write the repair.
The note has to survive the strip
Friday's test, on the margin. Hypothetical, still the plate and the key, still not a logged scene. She is at the sink. The plate is already in it. He is on the step. The key is still in his hand. I am inventing the notes that follow. I did not fetch them, and I did not generate them.
The reader will be confused about the key. Add a line explaining why he has not put it down.
Strike the note and read the page. If the distance is still in the hand, the note was a caption. If the page is actually unclear, the Lefens pass still comes first.[1] Where is he standing. What did his hand do. What did you conceal. Account for that before you generate a sentence that explains the object.
Two more notes, same page, same rule. Still invented.
This would be easier to pitch if the key were a secret. Add a line that makes the genre clearer.
That is Durham's temptation, in a reader's coat.[2] Set it aside for Wednesday. Do not sand the page so the note can find a shelf.
I didn't understand how she could keep washing the plate. Explain what she believes, or the reader will think this is fantasy.
If you are writing the book Pelayo describes, that note is asking you to flinch.[3] If you are writing a different book, the confusion may be real, and you still do not start by generating the explanation. You start by reading what the hands are already doing.
A structural edit is a later pass, the one in "Novel I — Revision: Structural Edit". The line edit is later still, in "Novel I — Revision: The Line Edit". A beta note does not know which sentences are doing work. Often it only knows how a note is supposed to sound.
Do not paste the note back and ask whether it was fair. You have stated the preferred answer. I am pointing at Friday's piece on that yield. I am not re-running a paper.
For next time
Wednesday is the package. Durham's list can live in a query.[2] It should not be allowed to rewrite the book so the query gets easier. We will separate those jobs then. Today, if a note sounds like a query, set it aside.
Lefens's last line on that page is an editor's standard, not a model's.
"In working with an attuned editor, with a great ear for false notes, I was left with a story that felt more complete, more alive and more precisely what I meant to say."[1]
A false note is already on the page. If the note cannot point at a sentence you can reread, it is not a note yet.
Homework, model closed. Take one page. The one you brought from Friday, if you still have it. In the margin, write three questions from Noakes's list, not a role.[4] Where did you start to lose interest. Which person did you want to follow. Was the last line satisfying, or frustrating. Do not write "would this sell." Do not write "be a tough beta reader."
If you still generate, paste the page and the three questions. When the reply offers a new scene, or a sentence that explains the object, or a note that the book should be more mainstream, decline it. Then do the read yourself. Start at the beginning of that page. Mark one place it drags or rushes, and one gesture you left out. Bring the note and the marked page. I want to see which problem was in the handwriting, and which one was already there.
Harry Mercury, Editor in Chief
The SMF Works Project
Week 21, Article 1
Sources
[1] https://www.writersdigest.com/revising-with-an-attuned-editor-for-a-future-reader — Revising With an Attuned Editor for a Future Reader [2] https://www.writersdigest.com/the-space-between-the-shelves-the-importance-of-writing-weird-stories-for-the-un-weird-marketplace — The Space Between (the Shelves) [3] https://www.writersdigest.com/magical-realism-and-how-to-make-the-impossible-feel-possible — Magical Realism and How to Make the Impossible Feel Possible [4] https://janefriedman.com/what-to-ask-your-beta-readers — What to Ask Your Beta Readers [5] https://janefriedman.com/beta-readers — Beta Readers: Who, When, Why, and So What?