How to remove ARC readers who don't review (without the drama)

Every ARC list collects readers who download and never review. Keeping them costs you more than a file: they take spots a reviewing reader could have, they make your campaign numbers look worse than they are, and sending them copies increases the number of files out in the world.

Most authors know who these readers are and keep them anyway, because removing someone feels rude. It doesn't have to be. A clear rule, applied the same way to everyone, and a short, kind email is all it takes.

Decide on a rule first

Removing people one by one, by feel, is what makes it awkward. Decide the rule once, put it in your sign-up page, and apply it to everyone. A rule that works for most teams:

Readers who download two ARCs in a row without posting a review are moved off the team. They're welcome to reapply.

Two things make this fair. It only counts copies the reader actually downloaded - someone who never opened the email didn't take a copy. And it looks at a streak, not one slip, because one missed review is usually just life.

If you track a review rate per reader, the same idea in numbers: under 25% of downloaded ARCs reviewed, across at least two books. (Here's how to read a reader's review history.)

The reason you can never use

Remove readers for not reviewing. Never for the review they wrote. Dropping a reader after a 2-star review turns your ARCs into a reward for positive reviews. Amazon allows free review copies only if the author doesn't try to influence the reader's opinionAmazon, and in the US the FTC prohibits incentives conditioned on a review's sentiment.FTC rule An honest 3-star reader who reviews every book is worth more to you than a 5-star reader who reviews one in four.

The same goes for your wording. Don't tell readers they "owe" you a review or got the book "in exchange for" one - Amazon doesn't allow requiring a review in exchange for a free book.Amazon Talk about team spots instead: they're limited, and they go to readers who are able to post.

Three emails, in order

Most removals never need the third email. A check-in after the first missed review often brings a late review or an honest "I'm swamped this year".

Send the goodbye once, then stop. Don't argue, don't list the books they missed, and don't remove them from your newsletter unless they ask - a reader who wasn't a good ARC reader can still be a good customer.

Make the rule visible from day one

The easiest removal is the one the reader saw coming. Put a line in your sign-up form and in the email that delivers each ARC:

Spots on the team are limited. If you download two ARCs in a row and aren't able to post a review, I'll free up your spot for someone else - no hard feelings, and you can always reapply.

Our ARC reader agreement templatehas this and the rest of the team rules in one page.

Keeping the list clean automatically

The work here isn't the emails. It's remembering, two books later, who downloaded and didn't review. ArcRoster tracks downloads and submitted review links for every campaign and keeps each reader's reliability tier across launches. A reader who keeps collecting ends up Unreliable, so you can leave them off the next invite list without digging through old spreadsheets. Pruning is half the job; the other half is who gets on the list in the first place.