Nobody to Read Your Draft? What to Do Instead

You finish a chapter and badly want to know whether it works.

So you send it to your closest friend. Three days later: "I liked it!"

You know that tells you nothing, and you don't feel you can push. So you post it to a forum. Two days, no replies. You join a critique group where you have to read someone else's chapter to earn a read of your own. You've read three. Your turn hasn't come.

This is not a popularity problem. Reading a draft is expensive for the other person and pays them very little. A ten-thousand-word chapter takes forty minutes to read properly, and then they have to find words for it while worrying about hurting you. "I liked it" is, honestly, the rational reply.

Here are things you can do without waiting on anyone, ordered from least effort to most.

1. Turn yourself back into a reader

You can't see the problems because you already know what happens next, not because you can't read. The job is to switch that knowledge off temporarily.

• Leave it three days. The cheapest and most effective move on this list. If three isn't enough, seven. Time beats technique.
• Change the container. Print it, change the typeface, read it on your phone, load it onto an e-reader. Your eyes slow down again on an unfamiliar layout.
• Read it aloud. Wherever your mouth stumbles, the rhythm is broken. This one is unusually good at catching dialogue.
• Read only the first 500 words, then ask yourself: if this were a stranger's book in a shop, would I turn the page? Answer honestly.

This stage catches more than most people expect — rhythm, padding, dialogue nobody would actually say. What it can't catch is whether a reader would keep going. That needs someone else.

2. Replace judgement questions with behavioral ones

If you do go and ask someone, what matters isn't who — it's what you ask.

"Is it good?" is a question nobody can answer. It's too large, too abstract, and the other person knows you're hoping for a yes. So you get "I liked it."

Ask about behavior instead:

• Where were you most tempted to keep reading?
• Where did your attention first drift — where did you want to check your phone?
• Whose name do you remember now that you've finished?
• If this were a serial, would you follow it? (No reasons needed.)
• Was there a sentence you had to read twice?
• What would you say this chapter was about? (This checks the things you assume you made clear.)

Two advantages: they're easy to answer — nobody has to be a critic, they just report what happened to them — and the answers can be checked against the manuscript. "I drifted in the third section" points at a place. "The pacing felt slow" doesn't.

3. Pick the right person, and make it cheap for them

• Not your closest friend — your target reader. If you write court-intrigue fantasy, ask someone who reads court-intrigue fantasy. Friends give you warmth; target readers give you information.
• Ask exactly one question. "Could you take a look?" is an open-ended pit. "Could you read just the first three pages and tell me whether you'd turn the page?" is a five-minute request. The acceptance rates aren't comparable.
• Don't explain after they answer. This is the hard one. When they say "I didn't follow this part," replying "well, he's actually…" destroys the feedback you just received — readers don't get your explanation inside the book. Write it down and say thank you.
• Give them a deadline. "Any chance you could look before Sunday? Totally fine if not" gets answered far more often than "take a look when you have time."

A message you can copy:

I finished a chapter and want to check one thing — could you spare five minutes? Just read the first three pages (link here) and tell me two things: (1) whether you wanted to stop anywhere, and (2) whether you'd want to read the next chapter. No review needed, one line is plenty. Any chance before Sunday? If not, just say so — genuinely no problem.

4. Use behavior data instead of opinions

If you're serializing, the platform is already answering you. It just doesn't look like an opinion.

• Completion rate per chapter: whichever chapter drops the most is the problem chapter.
• The chapter after which follows stop growing: that's usually your gate chapter.
• Where comments cluster: readers comment where something landed.

These numbers won't comfort you. They also won't be polite, and they won't lie because they know you.

5. AI beta reading: what it can and can't do

An AI can read your draft when no human is available. But be clear about what it can't do first, or you'll walk away with something that looks professional and contains no information.

Don't ask it for a score. We measured this ourselves across five real manuscripts and roughly a hundred and forty runs: one AI reader gave five completely different manuscripts the same score; a single line in the persona saying it never gives low marks produced a perfect 10; and re-running the same chapter drifts per-passage means by 0.2 to 0.6. The details are in this post.

Do ask about behavior, and make it quote your text. "Where did you want to stop," "which passage made you most want to continue" — those answers can be checked against the manuscript and are actually usable when revising.

Where it doesn't replace people: it has no patience to wait, it won't tell a friend about your book, and it won't message you three months later still thinking about your ending. A real readership is a different thing. What AI can do is turn "nobody has read this" into "at least one voice read it before I revised."

LitMemo's AI beta reader report is designed along exactly that line: the first thing it says is how many readers want to keep going, not a score, and every finding carries your own text so one click puts it back on the manuscript to revise against.

Closing

The cruel part of getting feedback is that you need it most precisely when you don't have readers yet.

Of the five things above, the first (three days, a different container, reading aloud) you can do today, for free. The second (behavioral questions instead of judgement) immediately improves the quality of what you get from anyone — including an AI. The rest can wait.