A realistic timeline from a finished draft to launch day runs about four to six months: roughly a month for beta reading and revision, a few weeks for editing and proofreading, and then several weeks of overlapping work on your professional review, ARC outreach, and cover and formatting before publication. Reviews take longer than most authors expect, which is why they need to start well before the date on your calendar.
This article threads together two of our guides: the Complete Guide to Beta Reading and the Book Reviews 101. Your own timeline will vary, but the order and the lead times below are worth planning around.
Skipping ahead costs you. If a beta reader finds a plot hole, revising after editing wastes the editing money. If you order a professional review before the manuscript is truly finished, you'll be reviewed on a weaker draft than the one you publish. Reviews, in particular, have fixed lead times you can't compress by rushing.
Send your revised, complete manuscript to beta readers. Budget two to three weeks for their reports, then time to revise based on what they find. See Is Your Manuscript Ready for Beta Readers? and How Many Beta Readers Do You Need?
This is where structural problems get fixed. Give yourself real time here; rushed revisions after beta feedback often need a second look before they're ready for an editor.
Line editing and copyediting come next, once the story itself is settled. See Beta Readers vs. Critique Partners vs. Editors for how these stages differ.
Standard reviews take 5 to 8 weeks, so this is close to the last safe moment to order one and still have it back before launch. A rush review (3-4 weeks) buys you a little more room if you're behind.
Final proofreading and interior/cover formatting happen once the text is locked. Your manuscript should be print-ready before your professional review arrives, and definitely before you start ARC outreach.
Send advance copies to readers, bloggers, journalists, and librarians. Give them a clear publication date and enough time to read before launch. See What Is an ARC?
Get your book pages ready on the retailers you're using, and set up a pre-order if you're using one. If your professional review has arrived, add it to your listing as an editorial review.
Send a friendly reminder that launch is close, with a direct link to where they can post a review once the book is live.
Ask readers directly, post everywhere you can, and remind your own audience. Reviews on Amazon (and most retailers) can only post on or after this date, so this is when the ARC groundwork pays off.
Reviews trickle in. Follow up once, gently, with ARC readers who haven't posted. Keep your request visible in your back matter and newsletter.
Reviews don't stop after launch. Keep the request in your book and your marketing indefinitely, and keep sending ARCs to new readers as you find them. See How to Get Your First 10 Book Reviews.
If you're working with less time, the parts that compress most easily are editing and formatting, if you have help available. The parts that don't compress well are beta reading (rushing it defeats the purpose) and your professional review (the turnaround is fixed by the service). If your launch date is firm and getting close, order a rush review and consider trimming your ARC list rather than your ARC lead time.
Building in buffer time at each stage is the simplest way to avoid all four.
Start the Clock on Your Launch
Beta reading and a professional review both take weeks, so the earlier you start, the more options you have at launch. Get your manuscript beta read, then order your review with plenty of runway.
At least 8 weeks before you want it in hand, since standard turnaround is commonly 5 to 8 weeks. A rush review can shorten that to 3 to 4 weeks.
Four to six weeks before launch is a common window, giving readers time to finish and be ready to post as soon as the book is live.
The manuscript should be through beta reading, revision, and editing, and ideally proofread, so the review reflects the book you're actually publishing.
You can, but it's the step least worth skipping. Beta readers catch problems that reviewers, and eventually customers, will otherwise be the first to point out.