Back to Page & Provenance
For Editors
Edit with judgment, structure, and a clear process.
This page is a working guide for editors who want to improve manuscripts, communicate more clearly with authors, manage scope well, and deliver stronger editorial outcomes from first read to final handoff.
Editing is not one job
Editing is not a single pass and it is not a single skill. Strong editorial work depends on knowing what kind of intervention a manuscript actually needs, applying the right level of editing at the right time, and communicating that work in a way the author can use. Macro editing and micro editing solve different problems, and editors stand out when they know the difference.
The strongest editors do more than correct prose. They diagnose issues, improve clarity, preserve voice, define scope, manage process, and leave the writer with a stronger manuscript and a clearer path forward.
- Identify the right kind of edit
- Improve the manuscript in the right order
- Protect the writer's voice while strengthening clarity
- Give useful feedback, not vague reaction
- Deliver a process the client can trust
Where are you in your editorial work
Editors face different challenges at different points in a project. Start with the area that matches what you need most right now.
Clarify what kind of edit you offer, what is included, and what is out of scope.
Focus on diagnosis, pattern recognition, clean communication, and consistent decisions.
Focus on editorial letter quality, query clarity, file cleanup, and next-step guidance.
Focus on style sheets, intake systems, contracts, timelines, and version control.
Focus on workflow, boundaries, scope language, and a clean client experience.
The main levels of editing
Different editorial passes solve different kinds of problems. Good editors know when a manuscript needs big-picture intervention and when it is ready for sentence-level work.
A high-level read that diagnoses strengths, weaknesses, and likely next steps before a deeper edit begins. Often the right starting point when an author is not yet sure what type of editing is needed.
Big-picture editing focused on structure, plot, pacing, organization, character, argument, clarity, and book-level effectiveness. Often includes chapter-by-chapter feedback and an editorial letter.
Sentence-level editing focused on rhythm, clarity, tone, transitions, and style. This is where prose gets stronger without becoming someone else's voice.
A correctness and consistency pass: grammar, usage, spelling, punctuation, capitalization, style-guide application, and continuity. Often relies on a style sheet.
The final prepublication check, usually after layout or formatting. Used to catch last remaining errors rather than reshape the manuscript.
A workflow editors can trust
Strong editorial work depends on a repeatable process — pre-edit planning, defined scope, stage-appropriate review, and a clean handoff.
- Manuscript title
- Genre and category
- Word count
- Current draft stage
- Author goals
- Deadline expectations
- Requested level of edit
Decide what kind of edit the manuscript actually needs. An author may ask for proofreading when the real need is developmental work or a full manuscript assessment.
- Type of edit
- Deliverables
- Software and file format
- Timeline
- Revision rounds
- Follow-up expectations
- Fee and payment structure
- Version naming
- Backup copy
- Style sheet
- Editorial checklist
- Reading notes or issues log
Work at the agreed level of edit and avoid accidental scope drift. If the manuscript reveals deeper issues, flag them clearly instead of silently expanding the job.
- Edited manuscript
- Editorial letter or summary notes
- Style sheet if relevant
- Explanation of next steps
Answer agreed questions, clarify patterns, and close the engagement cleanly.
How to give feedback authors can actually use
Editors are not just changing text. They are conducting an editorial conversation. Concise, direct, usable queries work better than overexplaining or burying a writer in commentary.
Principles
- Be concise — long, fuzzy comments weaken clarity
- Explain the issue, not just the symptom
- Group repeated issues into patterns so the author learns faster
- Use collaborative language when possible
- Focus on changes that improve meaning, structure, or readability
Helpful query examples
What to avoid
- Vague comments like "awkward" with no explanation
- Harsh phrasing that creates defensiveness
- Fixing everything silently without helping the writer see the pattern
- Overcommenting on every line when the bigger issue is structural
Consistency is part of the craft
A style sheet helps editors keep decisions consistent across a full manuscript. Applying a style guide for capitalization, hyphenation, numbers, and recurring usage decisions is a baseline editorial standard.
A basic style sheet should track
Standards mindset
Editors should have a default system even when a project is informal. That system may draw from Chicago style, house style, or project-specific conventions — but the key is consistency and documented decisions.
Tools editors actually use
Editors need tools that support markup, consistency, terminology control, workflow visibility, and clean communication. The point is not to automate judgment, but to reduce friction around the work.
Core editing tools
- Microsoft Word — track changes, comments, manuscript editing
- Google Docs — collaborative commenting and lighter edit workflows
Standards and reference tools
- Chicago Manual of Style — editorial style reference
- Merriam-Webster — spelling and usage reference
- PerfectIt — consistency checking for spelling, hyphenation, capitalization, and style patterns
- ProWritingAid — optional support for surfacing patterns, not replacing editorial judgment
Workflow and organization
- Trello — status boards and editorial pipeline management
- Notion — client notes, checklists, and project dashboards
Protect the work by defining it well
A large share of editorial problems are actually scope problems. Clarity around deliverables, word count, editing level, timeline, revision rounds, and payment terms prevents most of them.
Every editing agreement should clarify
- Exact service type
- Manuscript length or word count
- Delivery format
- Turnaround time
- Fee and payment schedule
- Number of follow-up rounds
- Whether calls are included
- What is outside scope
Important boundary reminders
Strong editing is a partnership
Editors do their best work when they remember that the manuscript belongs to the writer. The final call remains with the author — the editor's role is to assist, advise, and strengthen the work rather than take ownership of it.
Best practices
- Learn the writer's goals before prescribing solutions
- Respect genre and audience expectations
- Preserve voice where possible
- Help the author prioritize revisions
- Make next steps feel achievable, not crushing
A strong editor handoff should leave the writer with
- Clarity about what changed
- Clarity about what still needs work
- Confidence about the next revision stage
- A sense that the edit improved the book, not erased it
Before you send the manuscript back
Professionalism shows up in the final pass before delivery. A clean handoff builds trust and reduces confusion.
- ✓Are track changes and comments clean and intentional?
- ✓Are repeated issues summarized somewhere central?
- ✓Is the style sheet updated?
- ✓Are filenames clear?
- ✓Are comments concise and readable?
- ✓Have you accidentally edited beyond the agreed scope?
- ✓Did you leave the writer with next steps, not just marks?
Suggested handoff package
- Edited manuscript
- Editorial letter or summary
- Style sheet
- Invoice or closeout note if relevant
Common editor questions
What is the difference between developmental editing and line editing?
Developmental editing focuses on big-picture structure, pacing, organization, and book-level effectiveness, while line editing focuses on sentence-level clarity, flow, and style.
Can one editor do every type of edit?
Sometimes, but not always well. Many editors specialize because macro and micro editing require different forms of attention.
Should editors create a style sheet for every book?
For book-length work, usually yes. A style sheet supports consistency and better quality control.
What should an editorial letter include?
A clear diagnosis of major strengths and weaknesses, recurring patterns, and the most important next steps for the writer.
How detailed should editorial comments be?
Detailed enough to be actionable, but concise enough to stay readable. Overly long comments can muddy the issue.
How do editors avoid scope creep?
By defining the edit level, deliverables, word count, revision policy, and follow-up terms in writing before the project starts.
Public resources editors use often
Useful public tools and references for editorial work, consistency, workflow, and standards.
Edit with clarity, not chaos.
Use this page as a professional reference for stronger workflow, cleaner communication, and better editorial outcomes from first read to final handoff.