How Long Should It Take To Edit A Book

Gary Smailes | 1 November 2025

What Drives a Book Editing Timeline

Editing time is not guesswork. Timeline follows scope, complexity, and logistics. Nail those, and dates stop slipping.

Length and complexity

Word count sets the floor. More words, more hours. Genre pushes the ceiling. A spare memoir moves quicker than a history with endnotes. Fantasy with invented languages, maps, and lore slows the pace. Academic prose with citations and tables slows it further.

Quick gauge. Read one chapter cold and time that read. Multiply by total chapters. Add a day per five chapters for note-taking. You now hold a baseline for a developmental pass.

Type of edit and number of passes

Each level uses a different gear.

• Developmental work studies structure, argument, and arc. Reading plus analysis dominates the schedule.
• Line work focuses on voice, rhythm, and clarity. Expect slow, sentence-by-sentence attention.
• Copyediting enforces rules and consistency. Faster than line work, slower than a skim.
• Proofreading runs on designed pages. Typos, breaks, and layout glitches only.

Two passes take longer than one. A pass with an author round in between takes longer again. None of this is bad. Time buys quality, not fuss.

Draft quality

Strong drafts move faster. Wobbly structure adds weeks. Heavy line fixes add more. A stable text keeps editors editing, not triaging.

Mini-check before booking.

• Outline each chapter in one line. If the outline wobbles, expect a slower structural pass.
• Read five random pages aloud. Stumbles every few lines signal denser line work.
• Track a character’s timeline or a claim chain across three chapters. Confusion here means deeper intervention.

Nonfiction extras

Fiction rarely needs a permissions chase. Nonfiction often does. Time grows with each extra.

• Fact-checking for quotes and data.
• Citation cleanup and reference list formatting.
• Figures, tables, callouts, and captions.
• Permissions for lyrics, images, and long quotes.
• A detailed style sheet aligned with Chicago Manual of Style or house rules.

Add a few days for even a light stack of sources. Double that for dozens of notes and complex figures.

Workflow realities

Calendar friction is real. Editors book out weeks in advance. Time zones slow response cycles. School breaks, tax season, major holidays, all of these bend schedules. Production adds hard dates. Typesetting needs the copyedited file. Proofreading waits on galleys. One slip cascades, so plan buffers.

Rule-of-thumb speeds

Rates vary by editor, genre, and density. These ranges help with ballpark math.

• Developmental reading and analysis, 5 to 10 thousand words per day.
• Line editing, 1 to 2 thousand words per day.
• Copyediting, 2 to 4 thousand words per day.
• Proofreading on PDFs, 5 to 10 thousand words per day.

Do the math for your word count, then add author time between stages.

Practical ways to keep momentum

• Define scope in writing. Word count, level of edit, number of passes, and deliverables.
• Choose US or UK spelling and a style guide early. Share house rules up front.
• Freeze structure before copyediting. No new chapters mid-pass.
• Reply to editor questions within an agreed window, for example 48 to 72 hours.
• Book with buffers. A few extra days between stages protects the launch plan.

Editing respects preparation. Clarity on scope, stable text, fast responses, and clean files turn a messy timeline into a steady one.

Typical Turnaround by Editing Type

Once you know which stage you are booking, timing gets clearer. Each level moves at a different pace, and your own revision window sits between them. Here is what most authors see for an 80,000 word book.

Developmental editing

Typical editor pass: 3 to 6 weeks.
Typical author revision window: 2 to 6 weeks.

This stage looks at structure, argument, character arcs, and pacing. It often includes an editorial letter, margin notes, and a call to talk through options. Three factors stretch the schedule.

• Complexity. Multiple timelines, large casts, or heavy research take longer to analyze and map.
• Clarity of goals. If your brief is fuzzy, your editor spends extra time testing routes. A strong synopsis shortens this.
• Decision load. The more pathways on the table, the longer your revision window needs.

Quick example. A tight 80,000 word thriller with one point of view might take four weeks for the editor pass. A multi-POV historical novel with sources and a map might take six.

If you are still moving scenes or rethinking the endpoint, book the long end. You want space to make real choices, not patchwork.

How to keep this stage brisk

• Deliver a clean chapter list with word counts and a one line summary per chapter.
• Flag nonnegotiables, for example the ending stays, or the prologue must go.
• Reply to editorial queries within the agreed window, even if the answer is hold for now.

Line editing

Typical editor pass: 2 to 4 weeks.
Typical author integration window: 1 to 2 weeks.

Line work tunes the prose. Sentence by sentence. Clarity, tone, rhythm, and continuity. Two manuscripts of the same length can sit at opposite ends of the range.

• Dialogue heavy text moves faster.
• Dense exposition slows things.
• Shifts in voice between chapters take more checking.

A quick test. Open to a random page and read aloud. If you trip every few lines, expect the longer side. If you glide, expect the shorter.

What helps

• Approve a sample chapter edit before the full pass. It aligns tone and saves rounds.
• Share a style preference note. Oxford comma, serial hyphenation, slang tolerance, profanity levels.
• Freeze chapter order before line editing begins. New scenes mid-pass reset the work.

Copyediting

Typical editor pass: 1.5 to 3 weeks.
Typical author review window: 3 to 7 days.

Here the focus is grammar, punctuation, usage, and consistency. Copyeditors also build or follow a style sheet. That style sheet is not busywork. It keeps decisions consistent across hundreds of pages.

Variables that add time

• Building the style sheet from scratch, for example first pass on a series.
• Specialized terms, foreign words, and invented names.
• Citation and reference checks in nonfiction.
• Heavy rewrites during copyedit. This breaks flow and pushes the deadline.

If your book needs new house rules, add a few days. If you bring an existing style sheet, say from book one in a series, you gain speed.

Ways to avoid slippage

• Pick US or UK spelling and your style guide up front. Chicago Manual of Style and New Oxford Style Manual are the usual anchors.
• Keep your Track Changes responses tidy. Accept, reject, or comment. Avoid rewriting whole paragraphs unless agreed.
• Batch questions rather than drip feed them.

Proofreading on designed pages

Typical proof pass: 1 to 2 weeks.
Typical author check: 2 to 5 days.

Proofreading happens after typesetting. You are reading PDFs or galleys, not a Word file. The focus is on typos, bad line breaks, repeated words, page numbers, running heads, image placement, and table breaks. It moves fast, then slows where the layout is fussy.

Dependencies matter here. Proof starts only when the designer delivers pages. If you change more than a few words per page, layout reflows. Reflow means new pages, which triggers another check. That is why editors ask you to freeze the text before layout.

Tips for clean proofs

• Mark changes clearly. Use the platform your editor requests, for example sticky notes in Adobe or a marked proof list.
• Batch corrections to reduce reflow.
• Keep new copy short. One line in, one line out.

Add-ons and exceptions

Some books live outside the averages.

• Dense academic or technical nonfiction adds 1 to 2 weeks for notes, tables, equations, and references.
• Anthologies with multiple authors need more coordination. Add a week for herding and harmonizing tone.
• Translated manuscripts often need extra line attention. Expect the long side for line edit and copyedit.
• Short forms move fast. A novella or children’s chapter book might clear each stage in days.
• Picture books are short, but art approvals and layout rounds add calendar time. Plan for gaps between copyedit and proof while the designer works.

If your book includes appendices, glossaries, or a large index, raise that at scoping. You will need more time in copyedit and proof.

Read your quote like a producer

Not every quote covers the same ground. Before you book, ask:

• How many passes are included at this stage.
• Whether the editor provides a style sheet and, for developmental work, an editorial letter.
• How many queries you should expect and how you will handle them.
• What the author response window is between passes.
• Whether a brief recheck after your changes is included, or billed as a new pass.

Plan for one or two passes per stage. Confirm whether a second sweep is included. A clear scope protects both schedule and quality.

Sample Editorial Schedule for an 80k-Word Book

Here is a realistic calendar for an 80,000 word manuscript. Adjust the numbers for length and complexity, though the rhythm stays similar. The goal is steady progress, clean handoffs, and no last minute chaos.

Week 0: Kickoff and scope

• Confirm word count, editing levels, deliverables, and milestones.
• Approve a sample chapter edit if offered.
• Choose US or UK spelling and a style guide.
• Share assets, for example synopsis, character list, citations, figures, captions.

This prep trims days from every stage that follows.

Optional diagnostic

Editor review: 1 to 2 weeks.
Author revisions: 1 to 3 weeks.

A manuscript assessment gives a high level read before deep work. Expect an editorial memo, margin notes on a sample, and clear next steps. Use the revision window to fix obvious holes, cut dead weight, and lock the chapter order.

Good signal to proceed: big questions feel answered, and structure holds without wobble.

Developmental edit

Editor pass: 3 to 6 weeks.
Author revision window: 2 to 6 weeks.

Focus: structure, character arcs, plot logic, argument flow, and pacing. Deliverables often include an editorial letter, marked pages, and a call.

What shapes the range

• Multi‑POV or research heavy books sit on the long end.
• A stable outline and a clear brief move the work toward the short end.
• Fast author decisions keep the cycle tight.

Author task list

• Triage the letter. Mark must‑do, should‑do, and nice‑to‑have.
• Move scenes, rewrite broken chapters, fix beats that miss.
• Reply to queries within the agreed window.

A quick reality check: if new scenes enter during this stage, allow time for ripple effects in later chapters.

Line edit

Editor pass: 2 to 4 weeks.
Author integration: 1 to 2 weeks.

Focus: clarity, voice, rhythm, and continuity at sentence level. Expect Track Changes plus comments on habits such as filler words, echo words, or tangled syntax.

What slows things

• Dense exposition.
• Frequent shifts in tense or point of view.
• Inconsistent voice between chapters.

What speeds things

• A sample chapter approved before the pass begins.
• A style note on slang, profanity, hyphenation, and the serial comma.
• No new scenes while line work is active.

Author task list

• Review changes, accept or comment, and keep rewrites surgical.
• Batch questions rather than sending a stream of small notes.

Copyedit

Editor pass: 1.5 to 3 weeks.
Author review: 3 to 7 days.

Focus: grammar, punctuation, usage, consistency, and a style sheet. Nonfiction adds citation checks and terminology control.

Time adds up when

• A style sheet starts from zero.
• The book includes specialized terms or multiple languages.
• Author rewrites during copyedit, which forces rechecking.

Author task list

• Choose between Chicago and New Oxford or confirm house style.
• Respond cleanly in Track Changes. Accept, reject, or comment.
• Avoid new paragraphs unless previously agreed.

Production

Typesetting or layout: 1 to 2 weeks.
Proofreading on galleys: 1 to 2 weeks.
Final fixes: 2 to 5 days.

Once pages exist, proofreading looks for typos, wrong breaks, widows, orphans, repeated words, header and footer issues, figure placement, and table breaks. Large edits here trigger reflow, then another check. Freeze new copy. Keep corrections short.

Author task list

• Mark changes in the requested tool, for example comments in Adobe or a correction list.
• Batch fixes to reduce layout churn.
• Review new pages quickly after each round.

A simple calendar to picture the pace

• Week 0: Kickoff, sample edit, style choices, asset handoff.
• Weeks 1 to 2: Optional assessment.
• Weeks 3 to 5: Author revises from assessment.
• Weeks 6 to 11: Developmental editor pass.
• Weeks 12 to 17: Author developmental revisions.
• Weeks 18 to 21: Line edit.
• Weeks 22 to 23: Author integrates line changes.
• Weeks 24 to 26: Copyedit.
• Days 183 to 189: Author responds to copyedit.
• Weeks 27 to 28: Typesetting or layout.
• Weeks 29 to 30: Proofreading on galleys.
• Days 204 to 209: Final fixes and approval.

Result: about 14 to 16 weeks of editor time plus author windows and buffers. A brisk team with tight files often beats this by a few weeks. A complex book or slow responses stretch the plan.

Buffers and guardrails

• Book at least one buffer week between stages. Sick days, holidays, or a tricky chapter will show up somewhere.
• Freeze structure before line and copyedit.
• Keep version control clean. One master file, clear filenames, and agreed dates.
• Do not overlap a major rewrite with line or copyedit. Rework multiplies and deadlines slip.

What to confirm in your quote

• Number of passes included for each stage.
• Deliverables, for example editorial letter, style sheet, Track Changes.
• Response windows for both sides.
• Whether a brief recheck after author changes is included or billed as a new pass.

Follow this schedule, and the book moves from draft to press‑ready without drama. Slow where precision matters. Quick where momentum helps. Consistent throughout.

Ways to Speed Up Without Sacrificing Quality

Speed comes from preparation, not shortcuts. The fastest edit happens when the editor spends time on real problems instead of fixing preventable ones. Here is how to cut weeks from your timeline without losing precision.

Deliver a stable draft

Lock your big decisions before line or copyediting begins. Plot structure, argument flow, point of view, chapter order, and character names should feel solid. An editor working on a moving target wastes hours rechecking previous chapters every time you shift direction.

What stable looks like in fiction

• Chapter breaks stay put.
• Character motivations hold through the arc.
• Plot holes get filled during developmental work, not during copyedit.
• Flashbacks and time jumps make sense in sequence.

What stable looks like in nonfiction

• Chapter topics and order feel locked.
• Research gaps get filled before line work begins.
• Arguments follow a clear thread without major contradiction.
• Case studies and examples support the points you want to make.

Cut obvious redundancies before handoff. Repeated scenes, circular arguments, and filler paragraphs slow every stage that follows. Trim 5,000 words of dead weight and save days of editorial time.

Warning sign you are not ready: you keep adding new scenes or restructuring chapters during line editing. Those changes cascade through the whole manuscript.

Prepare assets at kickoff

Hand over everything your editor might need on day one. A synopsis or outline helps them understand where the book is headed. Character lists prevent confusion about who is who. Citation notes and figure captions save time during copyedit.

Fiction packet

• One page synopsis or chapter outline.
• Character list with brief descriptions and relationships.
• Timeline if the story jumps between time periods.
• Glossary for invented terms or technical language.
• Style notes on profanity, dialect, or specialized formatting.

Nonfiction packet

• Chapter outline or table of contents.
• Bibliography or reference list.
• Captions for figures, tables, or images.
• Permissions documentation for quoted material.
• Author bio and any house style preferences.

Academic or technical work

• Citation style guide (Chicago, APA, MLA).
• Glossary of technical terms.
• List of abbreviations and how to handle them.
• Figure and table numbering system.

The editor starts focused on your content instead of hunting for missing pieces.

Use efficient collaboration

Consolidate questions instead of sending a stream of small messages. Schedule brief check-ins rather than expecting instant responses to every query. Approve a sample chapter edit to align on voice and style before the full pass begins.

Sample edit benefits

• Confirms the editor understands your voice.
• Reveals style preferences before they mark 80,000 words.
• Catches major misalignments early.
• Sets expectations for both sides.

Good communication rhythm

• Send questions in batches, not one at a time.
• Schedule check-ins at natural break points.
• Respond to editor queries within the agreed window.
• Keep revisions focused on the feedback provided.

Poor communication rhythm

• Asking new questions before the editor finishes the current pass.
• Changing direction mid-edit without discussion.
• Ghosting on queries then expecting the timeline to hold.
• Sending mixed signals about what you want changed.

Maintain clean files

Standard manuscript format saves time at every stage. Consistent heading styles, clean paragraph breaks, and logical filenames prevent confusion. Version control keeps everyone working on the same draft.

File hygiene basics

• Double-spaced, 12-point Times New Roman or similar.
• One-inch margins, left-aligned text.
• Chapter breaks on new pages.
• Consistent heading hierarchy.
• No extra spaces between paragraphs unless scene breaks.

Version control that works

• Clear filenames with dates: "Novel_Draft_2024-01-15.docx"
• One master file per stage.
• Author and editor confirm which version before starting.
• Track Changes turned on for all edits.

Version control that fails

• Multiple files with confusing names.
• Edits scattered across different documents.
• No clear system for incorporating changes.
• Mixed versions with some changes lost.

Respect freeze dates

Avoid mid-pass rewrites and late-stage additions after typesetting. Each change ripples through the work already done. Batch changes to minimize layout reflow and extra rounds.

What freezing means at each stage

• Developmental: structure and major plot points locked.
• Line edit: no new scenes or character changes.
• Copyedit: no rewrites beyond addressing editor queries.
• Proofreading: corrections only, no new content.

The cost of late changes

• New paragraphs during copyedit force rechecking for consistency.
• Plot changes during line edit require rereading previous chapters.
• Content additions after typesetting break page flow and headers.
• Last-minute rewrites often introduce new errors.

Batch your changes. If you need three small fixes, send them together rather than one per day. Your editor handles them faster, and layout stays cleaner.

Communication and deadlines

Agree on response times for both sides. Industry standard runs 48 to 72 hours for author queries, and editors should match that pace for quick questions. Set a change-control plan for anything that might affect the production schedule.

Response time agreements

• Author queries: 2 to 3 business days.
• Editor questions: same window.
• Sample chapter review: 1 week maximum.
• Major revision decisions: discuss timeline case by case.

Change control plan

• Define what counts as a major change.
• Agree on a cutoff date for content additions.
• Set the process for handling urgent fixes.
• Confirm who approves changes that affect the timeline.

The speed bonus

Authors who follow these practices often finish editing 2 to 4 weeks faster than average. The editor spends time improving your book instead of managing chaos. Quality goes up because attention stays on the writing, not the process.

What fast looks like

• Each stage starts on schedule because the handoff is clean.
• Fewer revision rounds because the scope stays clear.
• Quick decisions because the author prepared well.
• Smooth production because the files are ready.

What slow looks like

• Delayed starts while missing pieces get gathered.
• Extra revision rounds because the scope keeps shifting.
• Extended timelines because communication breaks down.
• Production delays because late changes cascade.

Speed and quality work together when the process is right. Preparation on the front end pays dividends through every stage that follows.

Planning, Budgeting, and Booking Editors

Editing moves faster when you treat scheduling like part of the work. Good planning keeps the edit on rails, protects your wallet, and keeps a launch date from slipping. Here is how to line up the right partner and keep the calendar honest.

Book early

Experienced freelance editors often book 4 to 12 weeks ahead. Two peaks fill fast: September through November, and April through June. If you want a summer release, start outreach in late winter. For a holiday push, start in late summer.

Simple approach

• Reach out three months before your target start date.
• Share word count, genre, edit type, and a short excerpt.
• Ask about a sample edit and earliest slots that fit your timeline.
• Expect a deposit to reserve dates, usually 25 to 50 percent.
• Sign the agreement before any work begins.

A quick example

• March 1: inquiry.
• March 5: sample edit returned, quote accepted.
• March 8: contract signed, deposit paid.
• June 3: line edit start.
• June 28: line edit delivery.

Pricing and timeline trade‑offs

Editors price work per word, per hour, or per project. Faster timelines raise cost and reduce breathing room for revisions. Rush surcharges often sit between 20 and 50 percent. Short windows often mean one pass instead of two, limited calls, and fewer back‑and‑forths.

Points to confirm in writing

• Rate structure and total fee.
• What the fee covers, including number of passes.
• Rush surcharge and what service level comes with a rush.
• Business days versus weekends.
• Time zone for delivery and responses.

Sample language for a rush add‑on

• Rush service: deadline June 15.
• Delivery by June 15 for a 30 percent rush fee.
• Evening and weekend work included.
• Scope excludes a second pass.

Nail the scope

Clear scope saves weeks. Vague scope invites rework. Aim for a one‑page brief both sides can follow without guesswork.

Scope checklist

• Word count at handoff.
• Edit level: developmental, line, copyedit, or proofread.
• Deliverables: editorial letter, Track Changes, comments, style sheet, query log.
• Number of passes per stage.
• Style guide and spelling: Chicago, APA, MLA, house style, US or UK.
• Reference system and citation format.
• File types: DOCX for editing, PDF for proofreads.
• Start and delivery dates for each stage.
• Author review window after each stage.
• Communication plan: email, shared docs, scheduled calls.
• Payment terms: deposit, milestones, final payment trigger.
• Reschedule terms and kill fee.

A clean inquiry helps you get a fast yes. Feel free to adapt this note.

Subject: 80k historical thriller, line edit in June

Hello [Name],

I am seeking a line edit for an 80,000‑word historical thriller. US spelling, Chicago style, single pass with Track Changes and a brief style sheet. I can send a 2,000‑word sample for a test edit. Target start date: June 3. Delivery by June 28 works on my side. I will review and respond within 72 hours during the pass.

Please share rate, availability, and whether a sample edit is possible.

Thank you,
[You]

Budget your time, not only your money

Your hours matter as much as cash. Every stage includes author tasks, review windows, and decisions. Build room for them.

Useful time blocks

• Developmental edit response: 2 to 6 weeks for revision.
• Line edit review: 1 to 2 weeks to accept or reject changes and answer queries.
• Copyedit review: 3 to 7 days for queries and small fixes.
• Proofreading fixes: 2 to 5 days, no rewrites.

Protect these windows on your calendar. Block evenings or weekends before each handoff. Travel, big work deadlines, and family events slow responses. Slow responses slow the entire schedule.

Traditional vs. indie paths

Traditional publishing handles most logistics. In‑house schedules drive dates, and an assigned editor guides the process. Your main job, beyond revision, is fast responses to queries, clean page proofs, and meeting house deadlines.

Indie authors manage the pipeline. Editing sits next to cover design, typesetting, ARCs, and upload dates for vendors. Missing one milestone often bumps two more. Build a simple production map and stick to it.

A basic indie map

• Editorial: assessment or dev edit, then line, copyedit, proofread.
• Design: cover development and layout in parallel with copyedit.
• Marketing: ARC distribution, metadata setup, preorder copy.
• Production: ISBNs, files for e‑book and print, upload week.
• Buffer: one extra week between each handoff.

Sample edit and a real calendar

A sample edit prevents misalignment. One chapter, 1,000 to 2,000 words, paid or unpaid depending on policy. Approve the approach before full commitment.

Then ask for a milestone calendar. Dates reduce anxiety and keep everyone honest.

Example calendar for an 80k novel

• May 6: sample edit delivered, go‑ahead given.
• May 10: contract and deposit.
• June 3 to June 28: line edit.
• July 1 to July 10: author review of line edit.
• July 15 to July 31: copyedit.
• August 1 to August 5: author responds to copyedit.
• August 6 to August 16: typesetting.
• August 19 to August 30: proofread on galleys.
• September 3 to September 6: final fixes.
• September 10: files locked for upload.

Money savers that do not hurt quality

• Deliver a stable draft and reduce word count before booking. Fewer words equals fewer hours.
• Approve a style sheet early. Fewer reversals later.
• Bundle meetings. Two short calls beat five scattered ones.
• Batch answers to queries. One response thread saves time for both sides.
• Hold to freeze dates. Late additions during proofing multiply costs.

Quick red flags

• No contract or no scope document.
• Vague promises without dates.
• No style sheet for copyediting work.
• Pressure to skip a sample edit.
• No deposit request, followed by frequent rescheduling.

One last checklist before you book

• Dates align with your life, not wishful thinking.
• Budget covers base rate plus a 10 to 20 percent buffer.
• Scope is clear, in writing, signed by both sides.
• Response windows on your calendar, with reminders.
• Sample edit reviewed and approved.
• Milestone calendar received, with start and end dates for each stage.

Plan well, and the edit moves briskly. Fewer surprises. Better pages. A launch date you feel proud to announce. Your future self will high‑five you.

Frequently Asked Questions

Download FREE ebook

Claim your free eBook today and join over 25,000 writers who have read and benefited from this ebook.

'It is probably one of the best books on writing I've read so far.' Miz Bent

Leave this empty

Get free book