ARC Etiquette—How to Handle Typos Like a Pro

ARCs are a hot topic right now on Threads. The drama? Some reviewers are calling out typos in their ARC copies and claiming that not mentioning them would be dishonest—or worse, damaging to their credibility. Others are stepping in to defend authors, pointing out that ARCs are advance copies, not final ones, and that nitpicking every typo is unfair.

As with most things, the truth lies somewhere in the middle. And a little common sense goes a long way.

The ARC Reality Check

In traditional publishing, ARCs sent to reviewers are often the final version of the draft—edited and polished, just shy of hitting bookstore shelves. That’s the standard most reviewers are used to. But in the self-publishing world? The situation is a bit different.

Why? One word: time.

Self-published authors don’t have the luxury of releasing one book a year if they want to build and keep momentum. In many cases, they need to release 3–4 books annually just to stay relevant and maintain sales. Some readers won’t even start a series until it’s complete, which puts even more pressure on indie authors to write and release quickly.

So, in order to give ARC readers enough time to read and review before release day, many indie authors send ARCs that are mostly finished—but not fully proofread. In my case, they’ve gone through major edits, usually five or six drafts, and have had at least one round of proofreading. But they're not perfect.

While ARC readers are reading, authors are often still combing through their manuscript one or two more times to catch leftover typos. Why? Because reviews on release day matter. And if authors waited until everything was fully polished, the ARCs would go out too late to make any kind of launch impact. So authors aim for "good enough" instead of perfect.

My ARC Process (as an Author)

When I send ARCs, they’re already in their sixth or seventh draft and have had a proofreading pass. But after that, I always go through the manuscript again. And every time, I catch something.

In Ghost in the Attic, for example, I wrote “The dead yelled” instead of “The dean yelled.” Spellcheck didn’t catch it, because “dead” is a real word—it just wasn’t the right one. I'm not even going to mention the homophones I found in my other books. The important thing is that I found them (some were reported by my eagle eyed readers) and fixed them before they hit the shelves. These slip-ups are small, but they happen, especially when your brain already knows what it meant to write.

Clear Communication Goes Both Ways

Now, should authors expect ARC readers to just know their copy isn’t final? No. Communication is key. If the ARC isn’t the fully proofed version, the author should say so—plain and simple. That way, reviewers understand that minor typos may be present and can focus on the story, not the stray comma or wrong word. 

But communication is a two-way street.

If a reviewer finds an unusually high number of errors, or something feels off—like missing chapters or placeholders instead of character names—they should absolutely reach out to the author. I once received an ARC on NetGalley that abruptly ended mid-chapter 15. Turns out the author had uploaded the wrong file. Mistakes happen, and a quick message can save everyone a lot of trouble. I did not jump to conclusion and did not vent on social media. Instead, I contacted the author, who was appaled to realize she accidentally uploaded the first draft. She fixed it and was grateful I reached out to her instead of leaving a scathing review. Sadly, by the time she fixed it, the book had already been bombarded with one and two star reviews. 

And Then There Are the Truly Unedited ARCs…

They’re rare, but they do happen—especially when debut authors confuse beta readers with ARC readers. If you’ve received an ARC that clearly hasn’t been edited (and you’ve confirmed it wasn’t just the wrong file), how you respond matters.

You can be kind and let the author know you don’t review unedited books. Maybe it’s their first time and they’re still figuring things out. Or you can go scorched earth in a review, which says more about you than it does about them. 

The Bottom Line

ARC readers aren’t copy editors, and it’s not their job to report every typo. But mentioning minor errors in a review isn’t a crime either—especially if it’s done respectfully and in context (by that I mean share that you read an advance copy before the final proof reading and it's possible they were corrected)

On the flip side, authors should be upfront about what stage the ARC is in. If it’s not fully proofed, say so. That tiny bit of transparency builds trust.

Ultimately, ARCs are part of a collaborative process between writers and readers. A little grace, a little honesty, and a little communication can go a long way toward making the experience better for everyone.