That's okay, you’re allowed to. Not every book is for every brain.
If you do review, be honest without being cruel — focus on what didn’t work for you and why. If you can find something positive to say, mention it.
If you DNF, it’s totally okay to skip reviewing (or send the author a quick private note if you want).
Ideally during launch week (or within the first 1–2 weeks after release).
That’s when reviews help the most. If life happens, no guilt — just do your best, darling.
Common places: Amazon, Goodreads, BookBub, and sometimes social media (Instagram / TikTok / Facebook).
The author will usually tell you which ones matter most for their launch.
Please don’t. ARC files are for the approved reader only.
If your friend wants in, send them the sign-up link — easy.
That said, reviews are the whole point of an ARC team — so only sign up if you think you’ll be able to leave an honest review around launch week. If life happens, it happens.
Generally, it is not cost effective for authors to send a physical copy:
The cost of printing the book
The cost of delivering it to readers
It's laborious with no guarantee of a review
DNF is allowed. Sometimes the vibes just aren’t vibing.
If you DNF, you can simply not review — or, if you feel comfortable, send the author a quick private note (one sentence is fine). No drama, no guilt.
Usually not on Amazon — Amazon generally doesn’t allow reviews before release day.
Other platforms (like Goodreads) may be more flexible, but the safest rule is: post during launch week unless the author says otherwise.
Yes. Most authors deliver ARCs through BookFunnel (or similar), which lets you Send to Kindle in a couple of clicks.
If you can read on a phone/tablet too, that’s a handy backup when Kindle decides to be… Kindle.
Short quotes are usually fine (and appreciated!) as long as you credit the author/book.
Just don’t upload the file, don’t post full chapters, and don’t share the download link.
It is usually safest to make the disclosure, but don't make a big deal of it. A simple statement like the one that Goodreads adds automatically to pre-release reviews is enough: ARC Reader Review
No—
Don’t share the ARC file or big chunks of text.
Keep it to your opinion + maybe a very short quote (a line or two).
Check your timing.
If it’s an ARC, many authors prefer reviews/posts on or after release day (or whatever date they gave you). If you’re not sure, message the author and ask.
You'll have to post a video on social media of you doing the chicken dance.
Okay, not really, but that would be fun, wouldn't it?
Life happens. If you’re going to miss the review window, a quick heads-up to the author is kind — but not mandatory.
If you can still review later, great. If not, no shame.
Honest, specific, and fair. A couple of sentences is enough, usually better. You got the book for free but that does not obligate you to like it.
Mention what you liked, what didn’t work for you, and who the book is (or isn’t) for. Critique the book, not the author.
About 30 good, vetted ARC readers is a good achievement. If you can get more, there is no reason not to.
Expect about 50% to result in a review.
How to vet? Always confirm that the social media links that they provided or legitimate, and have some history.
Common sweet spot: 4 weeks before release.
Close enough that readers remember it, far enough that they have time to finish it. If your book is long, perhaps add a week.
EPUB is the default (works on most devices and with BookFunnel).
Optional extras: PDF (some readers prefer it) and MOBI (mostly outdated now). If you only choose one, choose EPUB.
BookFunnel (or similar) because it handles device issues and “help, my Kindle is possessed” emails.
If you deliver manually, expect more admin and troubleshooting.
You can’t force reviews, and you shouldn’t try.
What you can do is set clear expectations: “If you sign up, please leave an honest review around launch week if you’re able.” Keep it friendly, not threatening.
Careful here. It can come across as manipulative, and some platforms don’t love it.
Safer approach: encourage honesty, and invite DNFs or critical feedback privately if they’d rather not post publicly.
Nothing fancy. One line is enough:
“By accepting this ARC, you agree not to share, upload, or distribute the file.”
Add it as a required checkbox on the form and you’re covered for normal purposes.
A simple, low-stress version:
4 weeks before: recruit readers
Launch week: send one gentle reminder + review links
1 week after: A gentle nudge to those who have not posted a review, and a “thank you” to those who have. (Yes, even if you don't like the review)
The risk is minimal and manageable.
Use a trusted delivery method
BookFunnel is popular because it handles delivery nicely and makes it harder to “accidentally” share files around.
If you email files directly, they are easier to share.
Keep your ARC team curated
The biggest risk isn’t “readers,” it’s random sign-ups with no review history.
Before approving someone, check: Do they actually review (Amazon/Goodreads/StoryGraph/blog/BookTok)? Do they review in your genre?
If you’re unsure, start them on a smaller sample (first 3–5 chapters) or put them on a “waitlist” until they show activity.
Use a simple ARC agreement
Clear expectations in a friendly tone:
“Personal use only”
“Please don’t upload/share the file”
“Reviews are appreciated but not required / or requested by X date”
“If you can’t finish, no worries—just tell me”
Technically, that's not an ARC — it’s just a review copy (RC). But the answer is: Totally! ARC readers love to read and are not fussy about whether it is a new release or not.
Caveat: Reviews alone won’t drive traffic to an older book. They help once people arrive on the page (social proof), but awareness usually comes from promotion.
If your goal is visibility for an older title, recruit readers who can help you spread the word, such as those who:
have an active following in your genre (even small-to-mid is fine if engagement is real)
post reviews consistently (Amazon/Goodreads/BookBub/magazines and/or socials)
are happy to share a post, reel/story, or newsletter mention during your relaunch window
That is typically not the best fit — the effort level is different.
ARC readers expect an enjoyable complete read and a light ask: Please review if you can.
Beta readers expect work: a draft that may be messy, specific questions to answer, and permission to point out plot holes, confusion, pacing issues, and weak bits.
Best approach: use a small beta team first (5–12), revise, then send the polished version to your ARC team for launch.
*Not hard fact, but a general rule. Some ARC readers might be up for it, but it isn't the norm. Don't ask for it, look out for readers offering it.
