Define your manuscript goal, reader, and draft stage first, then hire for one editing level only. For how to find a book editor, filter candidates by service and genre, run the same sample excerpt across finalists, and compare them on a fixed 1-5 rubric. Reedsy can speed first outreach by letting you contact up to five professionals at once, but you still need written scope boundaries. Sign only after the agreement spells out exclusions, revision limits, file format, and payment events.
To find a book editor, start by defining what the manuscript needs to do, who it is for, and what stage it is in. Hiring an editor is not a creative scavenger hunt. It is a buying decision tied to a clear outcome. If you cannot yet say what the manuscript must do, for whom, and at what stage, you are not ready to compare editors. This playbook shows you how to find the right fit without wasting time on polished profiles that solve the wrong problem.
Do not browse first. Source editors only after you can state what the manuscript must do, who it serves, and what kind of intervention it needs. A lot of hiring advice starts with profiles. You will usually make better decisions if you start with a brief and use it to control every comparison that follows.
Before you start: keep your intake brief concise and reuse the same core details in each inquiry. More detail can improve matching and quote quality, and consistency helps you compare responses to the same job.
Step 1: Write the brief like a buying document. Include practical fields such as manuscript goal, target reader, draft maturity, edit depth sought, and success signal. Add word count and the type of editorial service you think you need, because editors need both to estimate realistically. A useful brief sounds like this: "This book should help X reader do Y. The draft is complete but structurally uneven. I think it needs developmental help. Success means the argument is clear to first-time readers." Verification point: if someone can read your brief and still not tell whether the problem is structural, sentence-level, or final cleanup, the brief is too vague.
Step 2: Match the draft stage to the service label, then get the label in writing. This matters because editing terminology is fluid. One editor may use "developmental" and "substantive" interchangeably. Another may separate them. If you are not sure what the manuscript needs, a manuscript assessment or critique can be a sensible first buy. It gives you a broad view of strengths, weaknesses, and next steps without pretending to fix everything at once.
| Service label | Best use case | What to confirm in writing | Common mismatch risk |
|---|---|---|---|
| Developmental editing | Big-picture issues with content, organization, or genre fit | Whether the editor will focus on structure, argument, pacing, reader experience, or all of these | You expect sentence polish, but receive high-level guidance only |
| Substantive editing | Use only if the editor defines the term clearly, since labels vary | Exact depth, whether it overlaps with developmental work, and what is excluded | You assume a standard meaning that the editor does not use |
| Copyediting | The structure is settled and you need correction of spelling, grammar, usage, punctuation, cross-references, and consistency | Whether style-sheet work is included and whether facts or references are out of scope | You hire too early and pay to polish text that later gets rewritten |
| Proofreading | Final quality check before publication, after editing and layout | Whether it is on a laid-out file or near-final manuscript and what counts as a correction | You use it as a substitute for earlier editing and deeper problems remain |
If you cannot decide between structural work and sentence-level work, ask each candidate what they would fix first and why. A clear answer helps. A promise to "do it all" without boundaries is a red flag.
Step 3: Build a shortlist on purpose. Filter by service and genre first, then look at names. Reedsy explicitly supports filtering by service, genre, and search, and its request flow lets you contact up to five professionals at once. That can also work off-platform: send inquiries in small batches, wait for replies, refine your brief, then continue. Plan for attrition from the start because availability and fit can shrink your list.
Directory trust signals are not the same. CIEP says listed members have demonstrated its membership criteria through evidence of experience and training. Editors Canada says it does not vet directory profile accuracy. Use those signals as context, not as guarantees.
Step 4: Vet finalists with the same rubric every time. Start with portfolio relevance. Then use the same representative sample for each viable candidate, because editors often use one to estimate realistically. After that, check references and run a short fit call focused on your reader, outcome, and scope.
Score each finalist on a simple 1 to 5 scale for:
Ask references what changed in the manuscript, whether the scope stayed stable, and how the editor handled questions or delays. On the call, listen for sharp questions about your reader and draft stage. If the conversation stays generic, that can signal a weaker fit.
Step 5: Set risk controls before you move to contracting. Require each finalist to state service boundaries, deliverables, exclusions, and timing in writing before you compare quotes. Keep one backup option alive until someone confirms availability and estimate. You are ready for Phase 2 when one candidate clearly wins on your rubric, can restate the manuscript goal in plain language, and has defined exactly what is and is not included.
You might also find this useful: How to Get an ISBN for Your Self-Published Book. If you want a quick next step, browse Gruv tools.
Treat the contract as part of delivery quality, not admin. Before you sign, use it to remove scope drift, payment ambiguity, and cross-border execution risk.
Do this first: compare your brief, sample, quote, and contract line by line, and fix any mismatch before you sign. Edit labels must be explicit because developmental editing, copyediting, and proofreading are not interchangeable, and proofreading is a late-stage check rather than a substitute for earlier editing.
| Item | What to specify |
|---|---|
| Scope boundaries | Name the service, manuscript version, word count, and exclusions |
| Revision handling | State included rounds, what counts as a revision, and whether post-delivery questions are capped |
| Deliverable format | Specify file type and feedback method, such as tracked changes, comments, editorial letter, or style sheet |
| Acceptance criteria | Define what counts as delivered, such as a marked manuscript plus editorial letter for the agreed draft |
| Payment triggers | Tie each payment to a dated milestone or defined deliverable, not vague progress language |
| Ownership and licensing | Keep manuscript rights explicit; if transfer or license language appears, require written, signed terms |
| Termination | State how either side can end the contract, what happens to partial work, and what is owed |
| Dispute path | Define first-step resolution and whether platform procedures apply |
Use this checklist and write each item so a third party could verify it:
Verification check: after reading the contract, you should be able to answer without guessing what will be edited, what files you will receive, and what event releases each payment.
Pick a payment structure that matches your need for verification control and your cash-flow limits. Once scope is locked, payment mechanics should reinforce that scope.
| Structure | Best when | Verification control | Cash-flow exposure | Collaboration risk |
|---|---|---|---|---|
| Deposit-led | You are reserving time and trust the defined scope | Lower early unless terms are very specific | Higher for you at the start | Medium if scope shifts later |
| Balanced milestones | The project has clear checkpoints (sample, pass, follow-up queries) | Strong when each milestone has defined outputs | Shared across the project | Usually lowest when both sides respond on time |
| Deliverable-led | Scope is narrow and you want proof before each payment | Highest for you | Lower early; increases after receipt | Higher for the editor, so availability may narrow |
Platform workflows are useful design references, not default contract law. For example, Upwork ties fixed-price payments to funded milestones and submitted work, with a 14-day no-response auto-release flow and a five-day security hold; the practical takeaway is to define your own review window and silence rule in writing.
For cross-border work, validate execution details before signature, not after invoicing.
| Checkpoint | Confirm | Note |
|---|---|---|
| Party identity | Legal name, country, and that contract party details match tax and invoice details | Validate execution details before signature, not after invoicing |
| Tax form | For U.S. payer workflows, W-9 is provided to the requester and name/TIN consistency matters; for non-U.S. individuals in U.S. withholding or reporting contexts, confirm whether W-8BEN is the correct certificate and track its validity period | Use the correct certificate for the workflow |
| Invoice/payment | Payment rail, currency, transfer-fee allocation, and expected net receipt | Confirm the expected net receipt |
| Transparency | Fees, exchange-rate treatment, taxes, and amount received | Spell out the amount received |
| Legal | Get qualified legal review when ownership, termination, governing law, or dispute terms are material | Use review when those terms are material |
Pause negotiations if edit labels are undefined, revision limits are missing, exit terms are unclear, or payment is requested without a defined deliverable.
For a step-by-step walkthrough, see How to Write a Book Proposal for a Nonfiction Book.
You get the most value when each round is used only for the job that round was purchased to do. If you paid for copyediting, do not reopen chapter order, argument gaps, or plot logic in that pass.
Step 1: Run one controlled workflow. Keep one source manuscript file, one feedback format, and one owner with final approval on each change. In Microsoft Word, Track Changes shows edits by contributor; in Google Docs, Suggesting mode keeps original text until suggestions are accepted or rejected. If comments stack up, keep a simple decision log: chapter, issue, decision, owner.
Verification checkpoint: you should always be able to identify the current file, open comments, and who changed what. Word revision marks and Google Docs version history support that check.
Step 2: Triage comments by purpose. Use three buckets: clarity, audience fit, and style.
Implement now: clarity fixes, and audience-fit changes that strengthen the promise to your intended reader.Defer: audience-fit ideas that would change positioning, examples, or scope beyond this round.Reject: style changes that are only preference and weaken your voice.Terminology can vary. Some editors use substantive as another label for developmental editing, while others treat it as a separate step, so confirm scope in your contract before revising.
Step 3: Match issue type to edit level, then escalate when needed. Editing and proofreading serve different purposes, and proofreading is a final quality check after editing and layout.
| Edit level | What it can realistically improve | What it will not fix | Escalate when |
|---|---|---|---|
| Developmental or structural | Core content, argument, structure, plot, chapter order | Final polish, mechanical consistency, last-pass typos | Big-picture issues still dominate comments |
| Substantive or line level (as defined in your contract) | Paragraph flow, sentence clarity, tone, language at reading level | Broken structure or missing logic across chapters | Sentence-level edits keep exposing structural problems |
| Copyediting | Grammar, spelling, punctuation, consistency of language and formatting | Unresolved structure, weak positioning, major rewrites | You are still moving sections or rewriting heavily |
| Proofreading | Final pre-publication error check after editing and layout | Structural problems, argument gaps, incomplete copyediting | Layout is done but content-level issues still appear |
Step 4: Verify results in the manuscript, not by comment count. Evaluate each pass by visible draft outcomes: clearer chapter logic after developmental work, smoother flow after line-level work, stronger consistency after copyediting, and a cleaner laid-out file after proofreading.
Then test a few excerpts you plan to repurpose (for example, in a newsletter, proposal, or sales material). If those still need structural repair, escalate to a deeper edit stage instead of running another proof pass. One pair of eyes is not enough, so keep a separate final review before publication.
If you want a deeper dive, read What to Do If You've Been Misclassified as an Independent Contractor.
Treat your next move as three pass-or-fail gates. If the manuscript stage, edit scope, deliverables, and workflow checkpoints do not match, stop there and fix the mismatch before you spend more time or money.
| Gate | Pass only if | Mismatch to stop |
|---|---|---|
| Source against the actual draft problem | You can name the editing level first and every finalist confirms the same scope in writing | Do not use sentence-level editing to solve structure problems |
| Contract the job you discussed | The written agreement reflects the exact edit, deliverables, fees, deadlines, and conditions before work begins | Pause if full edit is used but deliverables are not clearly defined |
| Manage to checkpoints, not hope | Your checkpoints are explicit and tied to manuscript stage and agreed scope | Do not send a manuscript to proof while chapters are still moving |
Step 1: Source against the actual draft problem. Pass only if you can name the editing level first. Developmental editing is for content, organization, and genre fit; copyediting handles spelling, grammar, usage, punctuation, and consistency; proofreading is one of the last checks before publication. Your verification point is simple: every finalist should confirm the same scope in writing. Where relevant, they should also show fit through a sample edit so you can see the level of intervention on real pages.
Step 2: Contract the job you discussed. Pass only if the written agreement reflects the exact edit, deliverables, fees, deadlines, and conditions before work begins. This is where vague promises create expensive confusion. If an editor says "full edit" but the deliverables are not clearly defined, pause. If the contract language drifts from the quote or sample, do not sign yet.
Step 3: Manage to checkpoints, not hope. Pass only if your checkpoints are explicit and tied to manuscript stage and agreed scope. Avoid mismatches like using sentence-level editing to solve structure problems or sending a manuscript to proof while chapters are still moving. If quotes are hard to compare, use the same manuscript word count and scope assumptions for each estimate, since rates can vary by project and editor.
If your goal is authority building, your optional next read is How to Write a Book to Establish Your Freelance Expertise. If your goal is compliance support around the engagement itself, contact Gruv before you hire.
Related: How to Find Beta Readers for Your Book and Use Their Feedback Well. Want to confirm what's supported for your specific country/program? Talk to Gruv.
Put the agreement in writing and make it match the editing stage you are actually buying. Editors work within a contractual framework that protects both parties, so the contract should clearly define the scope and deliverables for that stage. Before you sign, check that the document names the exact edit level and that nothing in it quietly expands the job.
Developmental work is usually most useful when your draft has structure problems, not sentence-level polish issues. If chapters are out of order, the reader promise is fuzzy, or the argument does not build cleanly, a developmental editor can help shape the book into a coherent flow. Your checkpoint is simple: after the proposal, you should be able to name the structural decisions this edit is meant to fix.
Treat vague role labels as a warning sign. If someone offers to be just "your editor" but cannot tell you whether they work as a developmental editor, copyeditor, or proofreader, you cannot compare scope reliably. Also pause if their approach sounds like a rewrite in their voice rather than an improvement to the manuscript while keeping yours.
No single channel wins by default. What matters is whether you can vet candidates using the same role-specific questions and the same deliverable check across every source. Your next step is to ask each finalist which of the four editing levels they handle and what you will receive at the end.
Do not compare prices until the scope matches. Compare quotes by edit level, manuscript portion covered, deliverables, and the revision outcome you should expect. If one quote is much lower but stays vague on scope, treat it as incomplete, not efficient. The practical check is to put quotes side by side and mark every missing deliverable or exclusion.
Often, yes, once the manuscript is stable. Because editing is usually handled as a staged continuum, many authors use proofreading as a final pre-publication pass after other editing work. If you are still moving chapters or rewriting heavily, you are likely not ready for proof.
Do not assume that, because book editing is usually a four-part continuum and specialization is normal. Working with one person through all four levels is described as rare and inadvisable, so ask where they are strongest and where they refer out. Your verification step is to get that boundary in writing before you hire.
A successful freelance creative director, Sofia provides insights for designers, writers, and artists. She covers topics like pricing creative work, protecting intellectual property, and building a powerful personal brand.
Includes 3 external sources outside the trusted-domain allowlist.
Educational content only. Not legal, tax, or financial advice.
Treat this as a protection problem first, not a label debate. If your work was treated as an independent contractor arrangement even though the relationship functioned differently, your first goal is to protect pay, rights, and records while you choose the least risky escalation path. You can do that without making accusations on day one, which often keeps communication open while you document what happened.
Treat the book as a business asset with boundaries, not a creativity test. In this cycle, give it one job: either support your client book services, or strengthen your own authority book so your niche, offer, and sales conversations become clearer.
The real problem is a two-system conflict. U.S. tax treatment can punish the wrong fund choice, while local product-access constraints can block the funds you want to buy in the first place. For **us expat ucits etfs**, the practical question is not "Which product is best?" It is "What can I access, report, and keep doing every year without guessing?" Use this four-part filter before any trade: