Six mistakes that quietly kill an ARC campaign

A failed ARC campaign rarely fails loudly. There's no error message — just a number on launch day that's lower than you hoped, and no clear reason why. The six mistakes below account for most of that gap, and every one of them is a process problem rather than a writing problem.

1. Opening requests with no deadline

Without a fixed review date tied to release, "later" reliably becomes "never." This isn't a character flaw in your readers — only around 22% of even highly engaged readers leave reviews often, and 30% do so sometimes.Written Word An open-ended request is competing against every other thing in an adult's week, and losing.

Set the review deadline three to seven days before release, state it in the first line of the invitation, and repeat it in every subsequent message. See the launch timeline by genre for how far ahead to open the window.

2. Sending to an unvetted, wide-open list

A public link with no gate produces downloads, which feels like progress and isn't. A hundred downloads at a 20% completion rate is a worse campaign than thirty at 70% — fewer reviews, more copies in circulation, more risk, and a contact list full of people you've learned nothing useful about.

The goal was never maximum distribution. It's the maximum number of readers who finish and post before your launch date.

3. Ignoring your own list in favour of platform strangers

This is the most expensive mistake on the list, and the best evidenced. In a documented cross-platform campaign, readers invited from the author's own list reviewed at 93% — on the same platform, in the same window, where organic requesters reviewed at 72%.Illene Roughly two-thirds of her ARC readers came from that direct list.

Platform readers are a supplement, not a foundation. If you don't have a list yet, that's the actual project — start with building an ARC team from zero.

4. Treating all platforms as interchangeable

Posting a literary memoir to a high-volume romance-focused pool produces exactly what you'd expect: readers who bail halfway and reviews that don't fit the book. Worse, in categories where reader mismatch is common, the reviews you do get can misrepresent what the book is.

The trade-versus-consumer distinction catches people out too. NetGalley and Edelweiss+ are aimed at librarians, booksellers, and retail buyersNetGalleyEdelweiss — genuinely valuable, and not the same product as a pile of launch-day Amazon ratings. We break the options down in the platform comparison and by category in the playbook by genre.

5. No reminder sequence

A single ask at the start of the campaign, with nothing before the deadline, is the most common structural reason completion rates stay low. The reader who genuinely meant to review and forgot is your cheapest available win, and they are a large share of everyone who hasn't posted.

Two messages: one at the midpoint, one three to five days before the deadline. Segment them — the person who never downloaded needs a different email from the person who downloaded three weeks ago and went quiet.

It's worth noticing that this is a large part of why the managed platforms in the measured data outperform typical self-run campaigns. They send the reminders whether or not the author remembers to.

6. No tracking system, so nothing carries forward

The quietest and most costly one. If you can't tell which platform, which reminder, or which reader pool actually worked, you repeat every mistake on the next launch — and re-invite the same people who took a copy last time and delivered nothing.

At minimum, keep in one place, for every reader:

• Name and platform handle — the same person is a different identity on every service, which is why reconciliation matters
• Date approved
• Date downloaded
• Date reviewed, if ever

That's enough to compute your real completion rate, work out which channel earned its cost, and build a re-invite list that gets better every book. If you want to start on a spreadsheet, ours is free and needs no email. Its honest limitation — and every spreadsheet's — is that it forgets between books, which is precisely the thing that makes launch four easier than launch one.

The one that isn't on this list

Writing a bad book. It's the first explanation most authors reach for and almost never the operative one. Every failure above produces the same symptom — a low review count — and none of them has anything to do with the manuscript. Fix the process before you rewrite the prose; see why ARC readers ghost for the version of this argument aimed squarely at that 3am thought.

ArcRoster exists to make most of the above structurally difficult: deadlines and campaign tracking built in, reminders scheduled against your deadline and sent automatically to everyone who hasn't reviewed yet, a roster that remembers across launches, and a reliability score so the readers who deliver rise to the top of your next invite list.