Working With an Editor: A Practical Guide

Working with an editor can make your writing clearer, more accurate, and easier for readers to follow. The best results come from treating editing as a collaboration: share a clear draft, explain your goals, consider feedback thoughtfully, and agree on the scope and schedule before work begins. This guide covers how to prepare, communicate, review edits, and handle problems. It applies to books, articles, reports, and other written projects; the details may vary by editor and publication.

What You’ll Need

• A complete or clearly labeled draft, in the format your editor requests.
• A short description of the intended audience, purpose, tone, and any relevant style requirements.
• A realistic deadline, plus time to review revisions and ask questions.
• An agreed scope of work, fee, deliverables, and payment terms. For a substantial project, confirm these in writing.
• A way to exchange files and comments, such as a shared document or word-processing file with Track Changes enabled.

Step-by-Step

1. Identify what kind of editing you need. Editing services vary. Developmental or structural editing looks at the overall argument, organization, pacing, and content. Line editing focuses on clarity, flow, and sentence-level style. Copyediting addresses grammar, consistency, usage, and house style. Proofreading checks a near-final version for remaining errors. Ask the editor to define the service, since labels can overlap. If you are unsure, describe your concerns and request a recommendation.
2. Choose an editor who fits the project. Look for relevant experience with your subject, format, audience, and language variety. Read samples or ask for references when appropriate, and discuss how the editor handles sensitive material or technical claims. A brief introductory conversation can clarify working style, availability, and expectations. Do not assume an editor will fact-check every claim unless that is included in the agreement.
3. Request a sample edit if useful. A short paid sample can show how the editor communicates and how much intervention your prose may need. Agree on the sample’s length, price, and turnaround first. Treat it as a way to assess fit, not a guarantee that every page will receive identical treatment. Avoid asking multiple editors to edit substantial unpaid samples.
4. Agree on scope, schedule, and terms. Confirm which files or word counts are covered, what the editor will deliver, how many rounds are included, and what counts as additional work. Set milestones for the edit, your review, and any follow-up. Clarify the fee, payment timing, confidentiality expectations, and cancellation terms. If the deadline is fixed, leave room for your own review; an edit is not finished simply because the editor has returned the file.
5. Prepare and send a clean draft. Resolve obvious placeholders, mark sections that are incomplete, and use consistent filenames. Include a concise project brief with the intended reader, purpose, preferred tone, spelling convention, style guide, and any terminology or formatting rules. Flag passages that must not be changed and explain why. Do not send a new draft midway through the edit without first checking how that affects the schedule and fee.
6. Give the editor room to work. Be available for questions, but avoid making untracked changes in the file while the editor is editing it. Agree on how urgent questions will be handled. If you must update the draft, tell the editor exactly what changed and when. For a large project, ask whether staged delivery is possible so you can discuss direction before the entire manuscript is edited.
7. Review the edited document systematically. Use Track Changes, comments, or another agreed method to distinguish edits from the original. Read the manuscript in context, not just the list of changes. Accept straightforward corrections, but check any revision that affects meaning, voice, facts, or technical details. If you reject a change, consider leaving a brief comment explaining your reason so the editor can understand the decision.
8. Ask focused questions and resolve disagreements. Group related questions and point to specific passages. Ask what a change is intended to fix, or offer an alternative that preserves your meaning. You retain responsibility for the content and final decisions; the editor contributes expertise but may not know your intent unless you explain it. Agree on how unresolved issues will be handled rather than silently undoing many edits.
9. Complete a final consistency check. After resolving comments, review the clean version for missing text, inconsistent names or terms, formatting changes, and errors introduced during revisions. If the work will be typeset or published elsewhere, clarify whether proofreading of the final laid-out version is included or requires a separate pass. Keep a dated copy of the original, edited file, and approved final version.

Common Mistakes

• Hiring before defining the need: A proofreader may not restructure a confusing argument, and a developmental editor may not correct every final typo. Match the service to the problem.
• Sending an unfinished or changing draft: Major additions can invalidate previous edits and increase cost. Agree on what qualifies as a stable draft.
• Expecting the editor to read your mind: Explain your audience, voice, and non-negotiable choices rather than relying on unstated assumptions.
• Accepting every change automatically: Editors can misunderstand context or make an incorrect suggestion. Check meaning and facts before accepting edits.
• Rejecting changes without discussion: If a recurring edit feels wrong, explain your preference. A clear conversation can prevent the same issue across the project.
• Leaving too little review time: Rushed approval makes it easier to miss errors or overlook an important question. Build a review window into the schedule.

Tips

• Write a one-page brief. Include the project’s purpose, audience, tone, spelling preference, and any style guide or reference documents.
• Share a few representative pages if the project is long, and agree on the editorial direction before proceeding with the full edit.
• Use comments for questions and Track Changes for revisions, unless the editor’s workflow calls for a different method.
• Keep a short style sheet of agreed spellings, capitalization, hyphenation, names, and recurring terms. Ask who will maintain it.
• Separate editorial feedback from personal judgment. A note about clarity or structure is about how a passage may read to an audience, not a verdict on you as a writer.
• Protect confidential or unpublished material by discussing file access, storage, and confidentiality before sharing sensitive documents.

Troubleshooting

• The edits do not sound like you: Point to specific changes that feel too formal, casual, or intrusive. Share a short example of the voice you want, then agree on a consistent approach.
• You disagree with a proposed change: Ask what issue it addresses and explain what meaning or effect you want to preserve. If both versions are valid, choose based on the audience and style requirements.
• The editor has misunderstood a passage: Clarify the intended meaning and supply any necessary context. Ask for a revision to the affected section, and check whether similar passages need the same treatment.
• The deadline is slipping: Contact the editor as soon as the risk becomes clear. Identify the remaining work, agree on a revised delivery date or staged return, and update any related commitments. Avoid assuming that faster delivery is possible without affecting cost or quality.
• You find errors after the edit: Mark each issue in the agreed file and notify the editor promptly. Check the contract for included follow-up or correction terms. If the errors come from later changes or layout, establish whether a new proofreading pass is needed.
• Communication has stalled: Send a concise message listing the open questions, required decision, and date by which you need an answer. If the project cannot continue, refer to the written terms and agree on what work has been completed and what files will be handed over.

Frequently Asked Questions

When should I hire an editor?
Bring one in when you have a clear enough draft to show your needs. For structural feedback, an early draft can be appropriate; for copyediting or proofreading, the text should be close to final.

Should I edit my own work before sending it?
Yes, make a reasonable revision first. Fix known issues and remove placeholders, but do not delay indefinitely trying to make the draft perfect. An editor needs to see the version you are ready to improve.

Can an editor guarantee publication or success?
No. Editing can improve a manuscript, but it cannot guarantee acceptance, sales, readership, or a particular response. Be cautious of anyone promising those outcomes.

Who is responsible for factual accuracy?
Unless fact-checking is specifically included, you are responsible for verifying claims, quotations, citations, permissions, and technical details. Ask the editor what they will check and what remains your responsibility.

Can I reject an editor’s changes?
Yes. The author or client makes the final decisions. Review changes carefully and explain important preferences so the editor can apply them consistently.

Do I need a separate proofreader?
Often, especially after typesetting, formatting, or substantial revisions. Confirm whether proofreading is included; a proofread of a manuscript file may not catch errors introduced in the final layout.