
I’m not going to give you a percentage. I know that’s the number you came for, and I know the Facebook groups hand it out freely (ten percent, thirty percent, sixty if you’re lucky), and I’ve stopped quoting one because across the ARC campaigns I’ve run the spread between the best and the worst is so wide that any single figure would be a lie for most of the books it was applied to.
What I can tell you is what moves the number, because the same handful of things move it every time, in every genre, and most of them are inside your control. If you fix those, your rate lands at the top of whatever range your genre allows. If you don’t, no benchmark will save you.
Why the published benchmarks disagree with each other
Every rate you’ve seen quoted measures something different. Some count reviews against signups, some against downloads, some against readers who confirmed they got the book. Some close the count on release day and some leave it open for three months. A campaign with 200 signups, 120 downloads and 40 reviews is a 20% campaign or a 33% campaign depending on which line you divide by, and both authors are telling the truth in the group thread.
So before you compare yourself to anyone, decide what you’re measuring. I count reviews posted against copies delivered, and I keep the count open for six weeks after release, because retail sites only let readers post once the book is live, and a reader who finishes on release day and posts a week later is a reader who did exactly what was asked. Measure the same way every campaign and you’ll learn more from your own three books than from anyone else’s screenshot.
Genre decides the range
Across the campaigns I’ve run, the pattern by genre is consistent enough to plan around, even without a number attached. Romance readers, and especially readers of dark, paranormal and romantasy subgenres, are the most reliable reviewers I work with: they read fast, they read in a community that expects reviews, and they treat an ARC as a small job they signed up for. Contemporary and small-town romance sits close behind. Cozy mystery readers are loyal and slower. Thriller and literary fiction ARC teams are the hardest to move, because their readers review less as a habit and the books take longer to finish.
Length matters inside every genre. Readers get through a 60,000-word romance in a weekend, and a 140,000-word epic fantasy has to compete with everything else in their month. If your book is long, your window needs to be longer, and your reminder sequence needs to be gentler, because the reader who is still on chapter twelve when release day arrives hasn’t failed you. She’s reading.
The signup form is where most of the rate is decided
The single biggest lever I’ve found is who gets on the team in the first place, and that’s decided at the form. Getting sign-ups is easy; getting readers to post on release day is where a form turns into a spreadsheet of ghosts. A form that asks only for an email address recruits everyone who likes free books. A form that asks where the reader posts reviews, how many ARCs they’ve reviewed this year, and whether they’re comfortable with your content warnings recruits people who have thought about the commitment before they made it.
Readers who’ve reviewed for the same network before post at a rate that the general signup pool never reaches, which is why I keep a separate list of proven reviewers and invite them first. If you’re building your own team, the equivalent move is keeping the readers who posted last time and inviting them ahead of the open call. Building an ARC team that reviews at launch is mostly this: recruiting the right people, then keeping them.
Delivery timing and the reminder sequence
Copies go out two, sometimes three, weeks before release. Earlier than that and the book gets buried under the reader’s other ARCs; later and there isn’t time to finish. Within that window the thing that moves the rate is what arrives with the book. A bare BookFunnel link gets downloaded and forgotten. A toolkit email that arrives with it, with the release date, the review links for Amazon and Goodreads, the content notes, and a line saying that release week is ideal and later is completely fine, gets acted on, because the reader now knows what to do and when.
Then the reminders. One around the halfway mark, one the day before release, one on release day with the live review links, and one a week after for the readers who are still going. Four touches, every one of them warm and none of them guilt-shaped. The readers who go quiet are almost never the readers who took your book and ran. They’re people with jobs and families who meant to, and a reminder that assumes the best of them gets far more reviews than one that sounds like an invoice. If your rate is low and you’re sending one email at delivery and nothing else, this is where I’d start.
Where you ask readers to post
The retail sites only accept reviews after release, which means a reader who finishes early has nowhere to put the review that counts. Ask for Goodreads early, then Amazon once the book is live, and say so plainly in the toolkit. A team that’s only ever pointed at Amazon loses every early finisher who forgot by launch day.
And ask for one platform, whichever the reader already uses. A request for Amazon and Goodreads and BookBub and Instagram reads as a workload, and the reader who would have posted a two-line Amazon review skips the whole thing. The review is requested, never owed, and one honest review anywhere is the win. Why ARC readers don’t post covers the delivery gap in more detail, and the answer is nearly always in the sequence rather than the readers.
What I’d measure instead of chasing a benchmark
Three numbers from your own campaign tell you what to fix next. The download rate (copies claimed against copies sent) tells you whether the delivery email is being opened; if it’s low, the subject line or the sender is the problem. The release-week review count against the six-week count tells you whether your reminders are working; a team that posts mostly in week three had the reviews in them and needed the nudge. And the split by platform tells you whether you asked for the right one.
Run three campaigns, measure them the same way, and you’ll have a benchmark for your own readers that beats anything I could print. Mine is built from 185+ campaigns and it still changes every time a genre shifts, a platform tightens its review rules, or a reader base gets tired. I’d rather hand you the levers than a number you’ll measure yourself against and lose to.
If your last ARC round ended with a spreadsheet of ghosts and you’d rather not build the form, the sequence and the reminders yourself, that is the whole of my ARC management service: recruitment from a network of 4,000+ readers who already know me, the toolkit, the reminders, and the tracking through release week. Tell me the book and the date and I’ll tell you what’s realistic.
Frequently asked questions
What percentage of ARC readers leave reviews?
It varies by genre, book length and campaign setup too widely for one figure to be useful, and the published benchmarks measure different things. Romance and romantasy teams post at the highest rates in my experience; thriller and literary fiction teams at the lowest. Measure reviews against copies delivered, over six weeks after release, and compare your own campaigns to each other.
How far before release should ARC copies go out?
Two weeks, sometimes three. Earlier and the book gets buried under the reader’s other commitments; later and there isn’t time to finish before release. Longer books need the longer end of that window and a gentler reminder schedule.
Where should I ask ARC readers to post reviews?
Goodreads before release, since retail sites only accept reviews once the book is live, then Amazon on release day. Ask for one platform, whichever the reader already uses, and make it clear the review is requested rather than required.