How Do I Get Someone To Edit My Book
Table of Contents
Decide what kind of edit you actually need
You do not need every edit at once. You need the right one for the draft in front of you. Pick by problem, not by panic.
Match stage to service
Use these four, in this order.
- Developmental editing. Big picture work. Structure, plot logic, pacing, character arcs, POV, stakes, worldbuilding, theme. Notes arrive as an editorial letter with margin comments and a plan for revision.
- Line editing. Voice and flow. Sentence rhythm, word choice, clarity, tone across POVs, and where a paragraph lands.
- Copyediting. Grammar, punctuation, spelling, and style consistency. Continuity for names, timelines, and terms.
- Proofreading on designed pages. Typos, layout glitches, bad line breaks, widows and orphans, odd hyphenation. Final eyes on the book in layout.
Think of it as building a house. Frame first, then walls, then paint, then a last walk‑through before opening the door.
Quick diagnosis: where does the pain live
Use reader feedback. Listen for the problem behind the note.
- “I got lost in the middle.” “Why did she do this.” “The ending felt flat.” Start with a developmental edit.
- “Sentences feel clunky.” “Too many filter words.” “Voice wobbles.” Go to a line edit.
- “Typos everywhere.” “Comma drama.” “Is it email or e‑mail.” Book a copyedit.
- “Looks fine in Word, but weird on the page.” “A few stray errors.” Schedule a proofread on designed pages.
No feedback yet. Run this five‑minute test.
- Write a one‑sentence summary for each act. If those summaries fall apart, you need developmental help.
- Read one scene aloud. Stumble on phrasing or hear repetition. You need line work.
- Search your manuscript for a name across chapters. Find spelling shifts. You need copyediting.
- Export a sample chapter to a print‑style PDF. See odd breaks or missing words. You need proofreading at layout stage.
A hard rule worth taping above your desk. If the note touches scenes or beats, fix structure. If the note touches style or meaning at sentence level, fix lines. If the note touches commas or consistency, fix copy. If the note touches pages, proof in pages.
Consider a manuscript assessment
Not ready for a full developmental edit. Try an assessment. Think of it as a diagnostic read with a shorter letter and no deep margin edits. You receive priorities, risks, and a revision path. Good for early drafts, tight budgets, or a stuck middle where you want a second set of eyes before a heavy spend.
What to expect
- A read‑through with notes on structure, POV, stakes, and genre alignment.
- A concise letter, often 4 to 8 pages, sorted by priority.
- A scene‑level hit list. Keep, cut, combine, or move.
- A short call or Q&A window.
Use the assessment to set the order of operations. If the letter says “two POVs weaken the spine,” address that before you ask for sentence polish.
Set goals and success metrics
Editors work best with a clear brief. Define success before you hire.
- Target audience. Who you want reading this book.
- Comps. Two or three recent titles your readers love, with a sentence on fit.
- Word count target. A range works. Name trims or expansions you expect.
- Heat or scare level. Be concrete. “Closed‑door kisses,” “on‑page intimacy level 3,” “no gore,” “psychological tension over splatter.”
- Non‑negotiables. Voice, theme, representation, or plot elements you will not change.
- Definition of done. What you need to feel ready for agents or launch.
Mini exercise. Write a one‑paragraph pitch. Hook, core conflict, stakes, and where the story lands. Share this with your editor. If you cannot write it without hedging, structure needs attention.
Plan the sequence
Respect the order. Structure first → prose polish → consistency → proof.
- Developmental first. Lock the spine. Do not pay for sentence work on scenes you might cut.
- Line next. Shape voice, rhythm, and clarity once scenes hold steady.
- Copyedit after line edits. Fix grammar and style once wording sits in place.
- Proof last on designed pages. Typos hide in layout. So do bad breaks and odd italics.
Skipping steps burns time and money. A writer I worked with paid for an immaculate copyedit, then moved three chapters, added a new midpoint beat, and revised two POV voices. We copyedited again. Twice the fee. One avoidable mistake.
Two quick paths based on draft stage
- Early draft with holes and a soft middle. Book a manuscript assessment or a full developmental edit. Build a revision plan. Re‑read comps to align stakes and pace. Then line edit.
- Late draft with strong structure. Book a line edit. Follow with copyediting. Proof on pages. Ship.
One last filter before you book. Read ten pages from the middle of your manuscript. If you feel proud of the sentences, hire structure help. If you feel sound on structure, hire sentence help. If you feel solid on both, hire a copyeditor and plan a proof.
Where to find reputable book editors
Good editors gather in a few reliable places. Go where they list services, show proof of work, and speak your genre.
Start with professional directories
Begin with hubs built for editors and authors.
- Editorial Freelancers Association. Browse by service and genre. Profiles include rates, tools, training, and availability. Post a job with word count, genre, timeline, and needed level of edit.
- Chartered Institute of Editing and Proofreading. Strong on credentials. Search by subject, service, and region. Look for Advanced or Professional grade for heavier lifts.
- ACES. Useful for nonfiction and journalism‑leaning projects. Filter for book specialists.
- Reedsy. A curated marketplace. View portfolios, sample projects, and reviews. Request quotes from a shortlist, not a blast list.
How to read a profile
- Services listed. Do they offer the edit you need now.
- Genre fit. Do they name your lane, not a vague "all genres."
- Evidence. Before and after samples, titles, or a case study.
- Clarity. Specific deliverables and timelines, not fluff.
- Tools. Word with Track Changes, Google Docs, or both.
Ten‑minute search sprint
- Pick one directory.
- Search your genre and needed edit.
- Open five profiles that feel close.
- Star two who show projects like yours.
- Draft one inquiry.
Tap genre networks
Genre groups keep private lists of trusted editors. Ask members who edits romance, SFF, horror, kidlit, or indie nonfiction well.
- Romance Writers of America.
- Science Fiction and Fantasy Writers Association.
- Horror Writers Association.
- Society of Children's Book Writers and Illustrators.
- Alliance of Independent Authors.
Sample forum post
"Seeking a line editor for adult fantasy, 110k. Comps: The Unspoken Name and The Ember Blade. Looking for voice‑savvy edits, light worldbuilding queries, and timeline checks. Budget range and timeframe available by DM. Recommendations welcome."
Notice the details. Genre. Word count. Comps. Scope. The right names will surface fast.
Work your community
Referrals beat cold searches. Ask where writers you trust found help.
- Critique groups. Query members who write near your lane.
- Discord or Slack spaces. Post in channels for editing resources.
- Conferences. Grab cards during hallway chats. Follow up within a week.
- Local writing centers and MFA programs. Many host vetted lists.
Social proof trick. Pull three books like yours off the shelf. Scan acknowledgments for "editor," "copyeditor," or "proofreader." Add those names to your list. If the editor works in‑house, ask for a freelancer they trust.
Shortlist smart
Do not chase twenty names. Aim for three to five. Then dig.
- Match on genre. Look for explicit mention of romance suspense, space opera, epic fantasy, memoir, or business.
- Match on service. Some focus on dev only, others on line and copy.
- Review samples. Ask for an editorial letter excerpt, a style sheet page, or a sample with Track Changes.
- Scope clarity. Deliverables listed in concrete terms, for example, word count limits for letters, number of passes, call length.
- Tone in samples. Notes read as precise and respectful, not snide or heavy‑handed.
Quick website audit
- Do they explain process in steps you understand.
- Do they show timelines and response windows.
- Do testimonials name genre and service.
- Do they show pricing ranges or a rationale for quotes.
Budget‑friendly paths
Full edits cost money. You have options that still move work forward.
- Manuscript assessment. A global read with a shorter letter and a priority map. Useful before a full dev edit, or when money is tight.
- Chapter critique. Pay for one or two chapters at line level. Learn the edit's approach, then apply across the book.
- Mentorship programs. Many regional SCBWI groups run them. ALLi lists services for indie authors, including audits and coaching. RWA chapters host editor office hours.
- University presses and writing centers. Some maintain rosters of experienced freelancers seeking side work.
- Beta readers and sensitivity readers. Use a clear brief. Ask targeted questions on stakes, pacing, clarity, and representation. Do not ask them to serve as unpaid editors.
Where to spend first
- If structure wobbles, buy an assessment or dev diagnostic.
- If sentences trip readers, buy a chapter line critique.
- If consistency slips, book a limited copyedit sample, then scale.
Make first contact count
A precise inquiry earns better responses. Keep it short and specific.
Subject: Inquiry for copyedit, 82k, historical mystery
Hi [Name],
I found your profile through CIEP. I am seeking a copyedit for a historical mystery, 82,000 words. Comps include The Thursday Murder Club. Timeline target, mid June. I will send the first chapter, a synopsis, and a style note if you are open to a sample edit of 1,000 words and a quote.
Thanks,
[Your Name]
[Link to site or socials, optional]
Swap details to fit dev or line work. The structure holds.
One last filter
When replies arrive, read between the lines. Look for clear steps, boundaries, and questions about goals. An editor who asks smart questions before quoting will likely guide you well once the work begins.
How to vet and choose the right editor
Choosing an editor calls for proof. Skill, process, respect for your voice. Test for all three before you sign.
Start with a sample edit
Ask for a sample edit of 1,000 to 2,000 words using Track Changes. Send the same pages to two finalists. Pick a scene with dialogue, movement, and interiority. Include a brief note on goals.
What to ask for
- Level of edit requested, for example, line or copy.
- A short deadline for the sample.
- A quote range for the full project.
- A sentence on your voice and audience.
How to read a sample edit
Look past red and blue markup. Read the thinking behind the changes.
- Clarity. Do comments name the issue and propose a path forward. Example: “POV jumps from Ava to Ben in this paragraph. Suggest staying with Ava until the scene break.”
- Story sense. Do queries show awareness of stakes, timeline, and character goals.
- Voice preservation. Read one paragraph aloud before and after. Does your rhythm remain. Word choices should feel like your own, only cleaner.
- Restraint. Light recasts are fine. Heavy rewriting shifts voice. If whole sentences appear in the editor’s voice, pause.
- Consistency. Look for notes on hyphenation, capitalization, numbers, and character names. A pro keeps track.
Two comment styles
- Weak: “Awkward.”
- Strong: “Two prepositional phrases slow the beat. Suggest cut one. Example below.”
A quick test
- Highlight three edits you love. Name why.
- Highlight three you reject. Name why.
- If reasons line up across both finalists, you have clarity on fit.
Review the artifacts
Ask to see real work products. Not the whole thing, a page or two.
- Editorial letter sample. Look for headings, priorities, and next steps. A good letter frames problems, ranks them, then offers options.
- Style sheet example. Spelling choices, hyphenation rules, numbers, dates, character names, places, timelines, oddities. A living record you will carry through copyediting and proof.
- Testimonials. Prefer notes that name genre and service. “Line edit for historical fantasy, debut author.”
- Before and after pages, shared with permission. You want focused edits, not a total rewrite.
Interview well
Set a short call. Twenty minutes works. Bring three questions and one sticky page from your book.
Good prompts
- Experience in your genre. Ask for two recent projects and the role played.
- Comps. Share yours. Ask how those examples handle voice, pacing, or structure.
- Approach to feedback. Do they push hard, or guide with questions. How do revisions flow.
- Tools. Word with Track Changes. Google Docs for collaboration. PDFs for proof stages.
- Timeline and availability. Start date, handoff dates, response windows.
- Follow up. One call after delivery. Email support for two weeks. Whatever the policy, clarity matters.
During the call, listen for curiosity. Editors who ask smart questions write smart edits.
Assess fit beyond price
Price matters. Fit matters more.
Signals of strong fit
- Clear rationale. Edits come with reasons, not vibes.
- Actionable notes. You leave with tasks, not fog.
- Respectful tone. Firm, specific, never snide.
- Voice protection. Sentences sound like you, only tighter.
- Scope awareness. The editor stays within the level of edit agreed.
A quick rubric
- Would you hand this person your messiest chapter.
- Did the sample make pages stronger without changing your sound.
- Do you understand the plan and timeline.
If you pause on any point, keep looking.
Spot red flags
Walk away when you see these.
- Bestseller guarantees.
- Pressure to skip proofreading.
- Refusal to provide a sample or references.
- Vague contract, no scope, no dates, no deliverables.
- No genre familiarity, yet big promises.
- Heavy rewriting in the sample, with voice drift.
- Rock bottom rates tied to rushed schedules.
A quick comparison exercise
Print two sample edits of the same scene. Grab a pen.
- Circle every change that improves clarity.
- Box every change that shifts voice.
- Star every comment that leads to a concrete action.
- Tally the stars. Pick the editor with more stars and fewer boxes.
Say yes when
- You see proof of genre fluency.
- The sample honors your voice while lifting clarity.
- The letter and style sheet samples show order and consistency.
- The call leaves you calm, not confused.
- The contract locks scope, dates, deliverables, and payment terms.
A good editor saves time, reduces guesswork, and supports your goals. Choose with care, then commit to the process. Your future readers will feel the difference.
Budget, scope, and contracts
You are not buying a vibe. You are buying time, judgment, and a defined set of deliverables. Put numbers on all three.
Know how pricing works
Editors price work in a few common ways. Each one suits a different stage.
- Per word. Common for copyediting and proofreading. Transparent, easy to budget.
- Per hour. Useful for uncertain scope, messy files, or audits. Harder to predict.
- Flat project fee. Typical for developmental edits, manuscript assessments, or line edits on full books.
Ask what drives the quote. Word count, complexity, genre, and deadline all matter. A clean 60,000-word romance reads faster than a 160,000-word historical epic with five timelines.
A quick estimator
- Take your word count.
- Multiply by the quoted per-word rate.
- Add a buffer for extras, for example a second pass or a rush.
Example: 85,000 words at 0.02 equals 1,700. Add 10 percent for wiggle room, total 1,870.
For hourly quotes, request a range with assumptions. “Estimated 20 to 25 hours based on 3,500 words per hour, includes a style sheet and a 30-minute follow up call.” Then ask for a cap.
If money is tight, ask about phased work. Assessment first, then a lighter pass on pages most in need. Or a paid sample chapter to set the approach before a full booking.
Define scope and deliverables
Ambiguity burns budget. Spell out what you expect, and what you will receive.
Decide the level of edit
- Developmental. Structure, plot, character arcs, stakes, pacing.
- Line. Voice, flow, sentence rhythm, clarity.
- Copyedit. Grammar, usage, consistency, fact flags.
- Proofread. Final typos on designed pages, page-level corrections only.
Agree on the passes
- One pass, or two.
- What triggers a second pass. New chapters, or revisions within the agreed plan.
- What falls outside scope. Heavy rewrites, new subplots, layout fixes.
List the deliverables
- Editorial letter length and focus. For example, 8 to 12 pages with priority list, examples, and next steps.
- Margin comments. Define an approximate density, for example, “query heavy scenes, note patterns, avoid rewriting.”
- Style sheet. Spellings, hyphenation, numerals, dates, names, places, timelines, voice notes.
- Follow up support. One call after delivery, or two weeks of email Q and A.
- Response windows. “Replies within two business days.”
- File format. Word with Track Changes, or Google Docs with Suggestions.
Clarify what the editor will not do. No heavy rewriting. No formatting for print. No layout fixes in PDF unless you hire a proofreader for designed pages.
Mini exercise
- Write a one-paragraph brief with your goals.
- List three pain points by order of priority.
- Paste a 200-word sample that shows typical writing, not a polished outlier.
Send this with your inquiry. Faster quote, better fit.
Set a schedule you both respect
Editors book out weeks or months ahead. Get dates in writing.
Milestones to lock
- Start date for the edit.
- Handoff date for files.
- Delivery date for the letter and marked pages.
- Review window for you.
- Follow up call date.
- Second pass dates, if included.
Build in buffer. Life happens. Give yourself a week between delivery and your follow up call. Leave a gap between development work and line editing. Fresh eyes help.
Ask about vacations, blackout periods, and response time during your revision window. You want no surprises.
Put terms in a contract
No contract, no edit. A simple one-page agreement works if it covers the essentials.
Include
- Scope. Level of edit, number of passes, deliverables.
- Schedule. All dates, time zone noted.
- Payment. Total fee, deposit amount, installment schedule, payment method, late fee policy.
- Cancellation and rescheduling. What happens if you pull the plug, or miss a handoff. Typical language: “Client rescheduling within 14 days of start moves to the next open slot. Deposit becomes nonrefundable.”
- Confidentiality. A short clause that protects your manuscript and author data.
- Rights. You retain copyright. The editor receives no rights to the work.
- Credit. Whether the editor receives an acknowledgment. Optional.
- Liability limits. Editors are human. No one guarantees a typo-free book.
Read before you sign. Ask questions. If a clause feels murky, ask for plain language or an example.
Prevent scope creep
Scope creep drains time and goodwill. Head it off with simple rules.
- Freeze the manuscript at handoff. New chapters wait for a later round.
- Keep questions in one thread. Weekly summary works well.
- Use a change log. Date, chapter, action taken, open question.
- Decide how new needs get priced. Extra chapters, new scenes, rush turnarounds.
A check before sending revisions
- Does this change align with the original goals.
- Does it affect earlier chapters.
- Do we need to adjust dates.
Email one note with answers. Editors love clarity.
Align on style from day one
Style choices shape every page. Lock the basics early.
Pick references
- Dictionary. Merriam-Webster or Oxford, specify edition.
- Style guide. Chicago Manual of Style for most books. AP for journalism-adjacent work.
- Regional spelling. US or UK. Keep it consistent.
- Series rules. Number formatting, dialogue tags, italics, capitalization for world terms.
Share your preferences
- Hyphenation choices for common compounds.
- Capitalization for ranks, titles, ships, or magic systems.
- Treatment of internal thoughts. Italics or roman with tags.
- Sensitivity notes. Words, tropes, or portrayals you want flagged.
Ask the editor to start a style sheet on page one. You will carry that document through copyedit and proof. It saves money and headaches.
A quick template you can swipe
Copy and paste, then edit.
Project summary
- Title, genre, word count, target audience, comp titles.
Scope
- Level of edit, one pass with a short check pass on revised chapters 1 to 3.
Deliverables
- Editorial letter, 10 pages with priorities and examples.
- Margin comments across full manuscript.
- Style sheet, two pages minimum.
- One 45-minute call within 10 days of delivery.
- Two weeks of email support, replies within two business days.
Schedule
- Files due 3 March.
- Edit starts 10 March.
- Delivery 31 March.
- Follow up call by 10 April.
Payment
- Total fee 2,400.
- Deposit 30 percent on booking.
- Balance in two equal installments, 50 percent on start, 20 percent on delivery.
- Late payments accrue a 2 percent monthly charge.
Terms
- Manuscript freezes on 3 March.
- Work performed in Word with Track Changes.
- Confidentiality and copyright remain with the author.
Put this in a signed agreement. Sleep better. Then do the work.
Prepare your manuscript for editing
You want your editor focused on story and sense, not chasing double spaces. A tidy handoff buys sharper notes and fewer back-and-forths. Do some prep, then hand over with confidence.
Self-edit first
Reverse outline
- Read each chapter. Write one sentence on what changes by the end.
- Note POV, location, timeline tick, and the scene goal.
- Drop all of this in a simple table or doc.
- Mark any chapter with no turn. Those are risks for cuts or combines.
Trim filler
- Meals with no conflict.
- Travel with no new information.
- Repeated arguments that restate old ground.
- Flashbacks that slow momentum.
Test: remove the scene in your outline. If nothing breaks, fold the beat into a stronger scene or delete.
Hunt easy fixes
- Run spellcheck.
- Search for double spaces, straight quotes, inconsistent ellipses.
- Cull habitual tics, for example “suddenly,” “began to,” “a bit.”
- Standardize names and terms before anyone builds a style sheet around errors.
Format for reading
- Word .docx.
- 12 pt, double spaced, 1-inch margins.
- Times New Roman or another legible serif.
- Indent paragraphs with styles, not tabs.
- Scene breaks as three asterisks.
- One space after a period.
- Header with last name, book title, and page number.
Ten-minute polish
- Read page one aloud. Fix any tongue twisters.
- Read the last page aloud. Endings deserve clean lines.
- Save a new version before sending.
Provide a brief
This anchors the edit. Keep it short and factual.
Include
- Pitch paragraph. One sentence on premise, one on stakes, one on tone.
- Synopsis, one to two pages, single spaced. Present tense. Spoil the ending. Cover main plot and key subplots only.
- Character list. Name, role, age, one-line want, a note on relationships.
- Content notes. Violence, self-harm, slurs, on-page intimacy, anything you want flagged.
- Goals and questions. Three to five prompts, for example “Is the midpoint weak,” “Does the antagonist’s plan make sense,” “Where does pacing sag.”
Tip: clarity beats style here. Editors do not grade briefs for prose.
Mini exercise
- Write your book’s jacket copy in three sentences.
- Write your ending in one sentence.
- Compare. Do promises in the jacket show up at the end.
Share market context
Help your editor see your lane.
- Target reader. Age, reading tastes, tolerance for heat or scare level, appetite for subplots.
- Genre and core tropes. List three. Keep it honest.
- Comps. Two or three books from the last five years. One line on why each is a match.
- Desired word count. Note where you sit against norms.
- Publishing path. Querying agents or going indie. This shapes the edit plan and timeline.
Avoid blockbuster comps from decades ago. Recent and specific helps more.
Build a story bible and a style sheet
Think facts and choices. Two small files beat one messy brain.
Story bible basics
- Names, nicknames, pronouns, titles.
- Ages and birthdays.
- Map of locations, distances, travel times.
- Timeline of key events with weekday and date.
- Rules for magic, tech, law, or institutions.
- Nonfiction writers, list sources for claims and quotes.
Style sheet basics
- Dictionary and style guide preferences.
- US or UK spelling.
- Hyphenation choices, for example fieldwork, e mail, email. Pick one.
- Numbers and dates, for example 1960s, not 1960’s.
- Capitalization for ranks, ships, factions, gods, invented terms.
- Formatting for thoughts, texts, foreign words.
Start both before you hire. Your editor will expand them. You will pass them to copyedit and proof.
Send representative pages for samples
Samples help you compare editors on the work you need.
Pick pages with
- Dialogue.
- Action or physical business.
- Interiority, the character’s mind on the page.
- A spot where you feel things wobble.
Avoid prologues if tone or POV shifts in chapter one. Skip a heavily polished chapter if the rest sits rougher. Include a short note with where the sample falls in the story.
A good size for a sample edit runs 1,000 to 2,000 words. Ask two finalists to mark the same pages. You will see differences in approach, clarity, and respect for voice.
Name files and keep versions straight
Do yourself a favor. Create a simple system now.
- Use versioned file names. Title_V01_2025-03-03.docx.
- Keep a folder for received edits. Do not overwrite.
- Turn on Track Changes for anything you revise during the round.
- Remove old beta-reader comments unless they frame a question you want addressed.
Share a list of abbreviations, custom fonts, or special characters if you use them. Flag any charts or images and how you handle permissions.
A quick checklist before you hit send
- Reverse outline done. Dead scenes trimmed or marked.
- Spellcheck run. Tics culled. Names and terms consistent.
- Standard formatting in place.
- Brief attached. Synopsis spoils the ending.
- Market context attached.
- Story bible and style sheet started.
- Representative pages picked for a sample edit.
- Files named with versions. Backup saved.
Do this, and your editor walks in with a clear map and a sharpened pencil. You get notes that move the book forward, not invoices for preventable cleanup.
Collaborate through the edit and plan next steps
You hired an editor for judgment and clarity. Now make the partnership work. Set rules, share context, keep momentum.
Kickoff alignment
Start with a short call or a clear email thread. Cover the nuts and bolts.
- Priorities. Name top three. Examples, fix pacing in the middle third. Strengthen the antagonist’s plan. Sharpen voice in dialogue.
- Scope. Confirm level of edit, number of passes, and the form of feedback. Editorial letter length, margin comments, a follow-up call.
- Communication. Preferred channel, response window, and meeting cadence. For big-picture rounds, a weekly check-in helps.
- File names. Agree a version system. Title_V01_AuthorDate. Editor returns Title_V02_EditorDate.
- Queries. Who resolves them, where they live, and how to close them. Decide on comment threads or a shared questions doc.
A sample kickoff agenda
- Goals for this round.
- Risks or sensitive areas.
- Timeline checkpoints.
- How to flag emergencies.
- Tools and settings, Word with Track Changes, or Google Docs in Suggesting mode.
End with a recap email so both sides share the same map.
Work the plan
Start with structure. Leave sentence polish for later. Do not rearrange chapters while hunting commas.
- Read the editorial letter once. Walk away for a day.
- Read again. Highlight global notes in one color. Local notes in another.
- Triage into three lists, must fix, nice to improve, park for later.
- Pilot changes on two or three chapters. Share one for a quick gut check if timing allows.
- Roll out across the manuscript once the approach works.
- Keep a change log. Date, chapter, action taken, open questions.
A change log entry might look like this
- 2025-03-03, Ch 12, moved reveal to end of scene, cut 300 words of backstory.
- 2025-03-04, Ch 19, raised stakes in midpoint argument, new beat where Jess risks her job.
- Open question, Does the mentor feel too wise now, tone check requested.
Hold your questions until patterns form. One well worded query saves five scattered ones.
Use tools effectively
You want transparency with minimal friction.
- Turn on Track Changes for revisions. Accept formatting changes first to reduce noise.
- Use margin comments for questions. Start with a tag, for example QUERY or CHECK TIMELINE, so both sides scan fast.
- Reply in the same thread to keep context.
- Do not paste new scenes over old without a note. Leave a comment, Replaced paragraphs 2 to 5 with new beat.
- In Google Docs, stay in Suggesting mode during active rounds. Resolve comments only when both sides agree.
Version control
- Name files with version numbers and dates.
- Keep an archive folder for earlier drafts.
- Back up to cloud and local.
- Avoid working in two live files at once. Decide on one source of truth.
Handle feedback without spiraling
Edits sting. That happens to pros too.
- Read the letter. Take a walk.
- Mark praise. Those choices stay.
- List changes you agree with right away. Momentum helps morale.
- For notes you resist, try a small test. If a tweak helps, great. If not, explain your reasoning and propose another route.
- Separate taste from error. Voice ticks are choices. Timeline gaps are not.
A useful script for sticky notes
- I see the concern. My goal for this beat is X.
- Here are two ways forward. Option A keeps the current scene order. Option B swaps chapters 7 and 8.
- Preference, B, due to cleaner setup for the twist in 9.
Validate revisions
Before moving to line or copyediting, seek targeted reads. Not a full beta swarm, a few focused readers.
- Pick two or three people who read the genre.
- Send a short brief. Page range, what to look for, deadline.
- Ask specific questions, Where did you skim, Which moment surprised you, Did you trust the timeline, Did the romance feel earned, Any representation notes.
- For sensitivity reads, provide context, themes, and any prior guidance you received. Pay and credit the reader per agreement.
Keep a feedback tracker. Note source, page, issue, action taken. This prevents collisions between notes.
Map the pipeline
Editing moves in stages. Respect the order. Money stays in your pocket when you stop polishing what might be cut.
- After structural work, book line editing for voice, rhythm, and clarity.
- After line editing, book copyediting for grammar, usage, and consistency.
- Proofreading comes last on designed pages. The goal is to catch final typos and layout glitches, widows, orphans, bad breaks.
- Carry the style sheet through every stage. Each editor adds to it. The proofreader relies on it.
Scheduling tips
- Book slots early. Popular editors fill months ahead.
- Build buffer time between rounds.
- Share your hard dates, launch plans, or submission windows.
- Confirm who delivers what at each handoff, revised manuscript, updated style sheet, clean file for layout.
Etiquette that keeps the work smooth
- Keep emails short, with a clear subject line.
- Bundle questions in one message rather than drip feeding.
- Acknowledge receipt of files within a day.
- Flag vacations or blackout days in advance.
- Pay invoices on time. Close the loop with a thank you. Good manners buy goodwill and speed.
A quick collaboration checklist
- Kickoff agenda covered and recapped in writing.
- Priorities ranked. Scope and deliverables clear.
- File naming and versions agreed.
- Change log and questions doc in place.
- Track Changes or Suggesting mode active. One source file.
- Structural fixes piloted on a few chapters, then rolled out.
- Beta or sensitivity readers lined up with briefs.
- Next-stage editors booked, timeline mapped.
- Style sheet updated and ready for the next handoff.
Do this and your edit runs like a clean relay. Fewer surprises. Better pages. A finished book that reads the way you meant it to.
Frequently Asked Questions
How do I decide which kind of edit my manuscript actually needs?
Match the edit to the problem, not to panic. If readers say “I got lost in the middle” or your act summaries fall apart, you need developmental editing; if sentences trip you or voice wobbles, choose a line edit; if names flip or commas are wild, book a copyedit; and if layout introduces odd breaks, schedule proofreading on designed pages.
Use quick tests — one‑sentence act summaries, read a scene aloud, search for name inconsistencies, or export a chapter to PDF — to diagnose needs before you pay for full rounds.
What should I include in the brief when I contact an editor?
Keep the brief short and specific: genre, word count, target reader, two or three comp titles, the book promise in one line, three revision goals, and any non‑negotiables (voice, representation, content limits). Attach a one‑page synopsis and a 1,000–2,000‑word representative sample for a sample edit request.
This approach answers the practical question of "how to prepare a manuscript for editing" and helps editors give accurate quotes, timelines and a clear sense of fit.
How do I vet and choose the right editor from a shortlist?
Ask for a 1k–2k sample edit and compare approach, tone and restraint. Read any editorial letters and style sheet examples they share, then hold a short interview to test genre fluency, process and communication style. Prioritise candidates who protect your voice and explain changes clearly rather than rewrite in their own voice.
Watch for red flags (no sample, vague contract, bestseller guarantees) and prefer editors who ask smart questions up front — that’s a reliable signal when you search for "how to vet and choose the right editor".
How should I prepare and format my manuscript before sending it to an editor?
Do a focused self‑pass: create a reverse outline (scene goal, conflict, outcome, POV), cull filler, run spellcheck, standardise names and terms, and start a simple story bible and style sheet. Format in Word .docx, 12pt serif, double spaced, scene breaks clearly marked and Track Changes enabled for revisions.
Provide a short brief (pitch, synopsis, character list, goals) and representative pages. These steps maximise the value of a paid editorial round and address common questions about "how to prepare a manuscript for editing".
What are realistic budgets and timelines for a developmental edit?
Pricing models vary: per‑word (common for copyedit/proof), hourly (for audits) or flat project fees (typical for developmental edits). Cost depends on word count, complexity and deadline — a 70–100k novel may take several weeks for a diagnostic and letter, plus months for revision cycles. Ask editors for a range and a cap if quoted hourly.
Plan phased spending: an assessment first if budgets are tight, then a full developmental pass only when you’re ready to act on the letter. Build buffers between rounds to avoid rushed, costly re‑edits.
What should be in the contract to protect both sides and prevent scope creep?
Include clear scope (level of edit, number of passes), deliverables (letter length, margin comments, style sheet), schedule with dates, payment terms (deposit, instalments, late fees), cancellation policy, confidentiality, copyright retention, and who owns the style sheet. Specify file formats and response windows to avoid misunderstandings.
To prevent scope creep, freeze the manuscript at handoff, keep a change log (date, chapter, action), and agree how extras (new chapters, rush requests) will be priced before work begins.
How can I collaborate effectively with an editor once the work starts?
Begin with a kickoff: agree priorities, file names, communication channels and a call schedule. Read the editorial letter once, let it sit, then triage notes into must‑fix, likely, and park lists. Pilot changes on a couple of chapters before scaling, answer margin queries in the document, and maintain Track Changes and a versioned file system.
Use a simple change log and tag comments (QUERY, DECISION) so both sides scan quickly; this keeps the developmental editing workflow efficient and reduces rework when you move on to line editing, copyediting and final proofing.
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