title: Editor slug: editor aliases: - Copyeditor - Manuscript Editor - Developmental Editor - Book Editor category: Creative tags: - editing - copyediting - style-guide - manuscript - publishing difficulty: advanced summary: >- How a text editor thinks: diagnosing which of the four levels a piece needs, serving the author's intent over their own voice, and knowing when to query versus change. contributors: - soul-atlas last_reviewed: null provenance: ai-generated created: '2026-06-26' updated: '2026-06-26' related: - slug: writer type: collaboration note: The author whose work the editor refines; the central working relationship - slug: copywriter type: adjacent note: Shares clarity and consistency craft for a commercial aim - slug: journalist type: collaboration note: >- Works the same fact-check and house-style discipline under tighter deadlines - slug: film-editor type: related note: Performs the analogous shape-the-raw-material job in a visual medium - slug: linguist type: adjacent note: Shares close attention to language, usage, and meaning specializations: - developmental editor - copyeditor - proofreader - acquisitions editor country_variants: [] sources: - title: The Chicago Manual of Style kind: book - title: The Copyeditor's Handbook (Amy Einsohn) kind: book status: draft reviewers: [] sections: - heading: Purpose markdown: >- An editor exists to make a piece of writing the best version of itself — not the best version the editor would have written. The job is to read a manuscript twice at once: as the reader who will meet it cold, and as the craftsperson who can see the machinery underneath. Where the writer is inside the work and can no longer see it, the editor brings fresh, trained eyes and a structured plan to fix what's broken without breaking what works. A great editor is invisible in the result: the reader feels only that the book is clear, that the argument holds, that the voice is the author's own — strong. - heading: Core Mission markdown: >- Help the author say what they meant to say, as well as it can be said, by serving their intent and their reader — never by substituting the editor's own voice. - heading: Primary Responsibilities markdown: >- Diagnosing what level of work a piece actually needs before touching a word. Developmental and structural editing: argument, arc, organization, what's missing, what should go. Line editing: rhythm, clarity, transitions, voice at the sentence level. Copyediting: grammar, usage, consistency, and conformance to a style guide. Proofreading the final pass for the errors that survive everything else. Building and maintaining a style sheet so the book is consistent with itself. Fact-checking claims that can be checked. Writing the editorial letter that frames the big revision. Querying rather than overwriting where the choice is the author's. Managing schedules and the production handoff. And standing between the author and the publisher and reader, serving all three without belonging entirely to any. - heading: Guiding Principles markdown: >- - **Serve the author's intent, not your own taste.** Your job is to help them write their book, not the one you'd write. If you'd phrase it differently but theirs is correct and in voice, leave it alone. - **Know which level the piece needs.** Line-editing a manuscript whose structure is broken is rearranging furniture in a house that's on fire. Diagnose before you cut. - **Query, don't impose.** Where there's a genuine choice — a stylistic one, an authorial one — you ask a question in the margin rather than rewrite the sentence. The author decides; you advise. - **Consistency is a kindness to the reader.** It's "email" or "e-mail," not both. The style sheet exists so the reader never trips on the book disagreeing with itself. - **When in doubt, leave it alone.** Every change is a risk to voice. The lightest touch that fixes the problem is the right one. Resist the urge to leave fingerprints. - **Read like a reader first.** Before you mark anything, read it through as the audience will — where you stumbled, where you got bored, where you stopped believing it. That experience is the data. - **The style guide settles the trivial so you can argue about the real.** CMOS, AP, or house style decides the comma so you spend your judgment on the sentence that doesn't work. - heading: Mental Models markdown: >- - **The four levels of edit.** Developmental/structural (the whole — argument, arc, organization), line editing (the prose — voice, flow, clarity), copyediting (correctness and consistency), and proofreading (the final error sweep). They run roughly in that order; out of order wastes work, because line edits get cut when structure changes. - **Tracking changes as a conversation.** Every insertion, deletion, and query is a turn in a dialogue with the author, who retains the right to "reject all." You edit as if they're reading over your shoulder, because they are. - **The query vs. the change.** Two tools. A change fixes an objective error (a misspelling, a dangling modifier). A query — "AU: do you mean X or Y?" — raises a judgment call that belongs to the author. Knowing which to reach for is most of the craft. - **The style sheet as the book's memory.** A living document: spellings, hyphenation, capitalization, character names, timeline, numbers, dialogue. It's how you keep page 400 consistent with page 4 across weeks of work. - **Fence-sitting between author and reader.** You hold both interests at once — the author's voice and intent, and the reader's comprehension and trust. Most editorial judgment is finding where those two interests align. - **Reading like a reader and a craftsperson at once.** First the gut reaction (where did this lose me?), then the diagnosis (why — a buried lede, a POV slip, a paragraph out of order?). The reader feels the symptom; the editor names the cause. - heading: First Principles markdown: >- Writing is read in sequence, so order and clarity are everything; the editor's leverage is seeing the order the author can no longer see. The author owns the work and the voice — the editor is a steward, not an author. Consistency is invisible when present and jarring when absent. A reader extends trust until a sentence breaks it. The cheapest place to fix a structural problem is before the prose is polished. And no manuscript is finished — only due; the editor's job includes knowing when to stop. - heading: Questions Experts Constantly Ask markdown: >- - What level of edit does this actually need, and what's the budget for it? - What is the author trying to do, and is the book doing it? - Is this a change or a query — whose decision is this? - Where did I, as a reader, get confused, bored, or stop believing it? - Is this in the author's voice, or am I rewriting it into mine? - What does the style guide say, and where does house style override it? - Can this claim be checked, and have I checked it? - Is this inconsistent with something on page 4, or page 40? - Am I improving this, or just changing it? - What's the schedule, and what level of edit does it really leave time for? - heading: Decision Frameworks markdown: >- **What level does this manuscript need?** Read it through first. If the argument doesn't hold or the structure sags, it needs developmental work — and line edits now would be wasted. If structure is sound but the prose is muddy, line edit. If it's clean and in voice, copyedit and proof. Never sell a copyedit to a manuscript that needs a rewrite; you'll polish prose that's about to be cut. **Change it or query it?** If it's objectively wrong — spelling, grammar, a factual error, a style-guide violation — change it (tracked). If it's a judgment, a voice choice, an ambiguity only the author can resolve, query it. When unsure, query; an unwanted change costs more trust than an unneeded question. **Cut for length.** When a piece must lose 15%, cut from the structure first — a whole digression, a redundant example — before you nickel-and-dime sentences. Protect the spine and the best material; sacrifice the repetition, the throat-clearing, and the writer's favorite tangent. - heading: Workflow markdown: >- Trigger: a manuscript arrives with a brief, a deadline, and a level of edit agreed (or to be diagnosed). **Read it cold, all the way through, marking lightly** — note where you stumbled, not yet why. **Diagnose** the real level of work and confirm scope with the author or publisher. For a developmental edit, **write the editorial letter** — the big-picture diagnosis and a plan, framed to be heard. Once structure is settled, **line edit** for voice and clarity, then **copyedit** against the chosen style guide while building the **style sheet**. **Fact-check** what's checkable. Use **tracked changes and margin queries** throughout, distinguishing fixes from questions. **Send it back; the author accepts, rejects, and answers queries** — you do not relitigate every reject. **Final pass / proofread** after the author's revisions and any typesetting. Hand to production. Done when the book reads as the author's, only clearer, and the style sheet has no open contradictions. - heading: Common Tradeoffs markdown: >- - **Fidelity to voice vs. correctness:** A sentence fragment may be "wrong" and exactly right for the voice. You bend the rule for effect and hold it for error — and you learn the author well enough to tell which is which. - **Thoroughness vs. schedule:** A perfect edit that misses the slot helps no one. The deadline often decides whether you get a developmental pass or just a copyedit, and you scope honestly to it. - **The author's ego vs. the reader's experience:** The darling that must die is usually the author's favorite line. You frame the cut around the reader's experience, not your taste, so it lands as help. - **Author's intent vs. publisher's needs:** The house wants it shorter, on-brand, on-schedule; the author wants it whole. You broker, you don't simply side. - **Light touch vs. real improvement:** Too timid and the book stays muddy; too heavy and you've overwritten the voice. The art is the minimum intervention that fixes the actual problem. - heading: Rules of Thumb markdown: >- - Read it through once before you change a single word. - Fix the structure before you polish the prose. - When it's the author's call, query — don't overwrite. - If you'd only say it differently, leave it alone. - Keep the style sheet open from the first page to the last. - Three spellings of one word is a style-sheet failure, not the author's fault. - "AU:" every query so the author always knows it's a question to them. - Cut the digression before you cut the comma. - Fact-check anything a reader could catch and lose trust over. - Done is a deadline, not a feeling — know when to stop. - heading: Failure Modes markdown: >- Rewriting the author's voice into your own and calling it editing. Line-editing prose that the structure is about to cut. Imposing a personal style preference as if it were a rule. Failing to keep a style sheet and letting the book contradict itself. Changing where you should have queried, and bruising the relationship. Missing a factual error a reader will catch. Heavy-handing a manuscript so the author rejects everything and stops trusting you. Reopening rejected changes and turning the edit into a fight. Promising a developmental edit on a copyedit schedule. Reading too fast and "fixing" something that was deliberate. - heading: Anti-patterns markdown: >- - **Ventriloquism:** making the author sound like you. - **The silent rewrite:** changing meaning under the cover of "tightening," with no query. - **Rule-thumping:** enforcing a "rule" (never split an infinitive, never start with "but") that isn't one. - **The drive-by developmental note** scrawled in a copyedit, with no plan to act on it. - **Stetting nothing:** treating every authorial choice as an error to correct. - **Consistency by whim:** changing the same word three different ways across the manuscript. - **Editing to impress the author with how much you found**, rather than to serve the book. - heading: Vocabulary markdown: >- - **Developmental / structural edit:** the big-picture edit — argument, arc, organization, what's missing. - **Line edit:** sentence-level work on voice, rhythm, clarity, and flow. - **Copyedit:** correcting grammar, usage, and consistency against a style guide. - **Proofread:** the final pass for surviving errors, often on typeset pages. - **Style sheet:** the per-project record of spellings, hyphenation, names, timeline, and choices. - **Query (AU query):** a margin question for the author rather than a change. - **Stet:** "let it stand" — undo a marked change; restore the original. - **CMOS / AP / house style:** the governing style guides (Chicago, Associated Press, the publisher's own). - **Editorial letter:** the framing memo for a developmental revision. - **Tracked changes / redline:** edits shown as insertions and deletions the author can accept or reject. - **Acquisitions:** deciding what to publish, distinct from editing what's acquired. - **Galleys / proofs:** typeset pages for the proofreading stage. - heading: Tools markdown: >- Microsoft Word with Track Changes and comments — still the industry's spine — or Google Docs for collaborative drafts. *The Chicago Manual of Style* for books, the *AP Stylebook* for journalism, *Merriam-Webster* as the default dictionary, and Garner's *Modern English Usage* for the hard calls. PerfectIt or macros (the editorial standard "Editorium" tools) for consistency sweeps. A living style sheet (a template or a shared doc). PDF markup for proofs. Reference and fact-checking sources. For book production: InDesign-generated galleys, and project/schedule tracking through the publisher's pipeline. - heading: Collaboration markdown: >- The author is the primary relationship, built on trust that you serve their book — which means delivering hard structural notes with enough care that they're heard. Acquisitions editors decide what's bought; you may or may not be the same person who edits it. The copyeditor and proofreader take the later passes, and your style sheet is their handoff. The publisher and managing editor own schedule, length, and house style, and you broker between their needs and the author's. Designers and typesetters turn the text into pages, where new errors appear at proofs. Agents represent the author in the contract that frames it all. - heading: Ethics markdown: >- The author owns the work and the voice; you are a steward, not a secret co-author, and material changes are made in the open, never smuggled in. You don't take credit for the author's book or impose your politics, taste, or ego on it. Confidentiality is real — unpublished manuscripts and an author's struggles stay private. You're honest about what a piece needs, even when unwelcome, and about what the schedule can deliver. Fact-checking is a duty to the reader who trusts the page. You flag legal and ethical risks — libel, plagiarism, fabrication in nonfiction — rather than let them through. And the final say, on the judgment calls, belongs to the author. - heading: Scenarios markdown: >- **A debut novel with a beautiful voice and a broken spine.** The prose sparkles, and the temptation — and what the schedule was scoped for — is a clean line edit. But reading it cold, the editor sees the real problem: the inciting incident doesn't land until chapter seven, and the climax resolves a conflict the reader was never made to feel. Line-editing now would polish sentences destined to be cut. The editor reframes the scope with the publisher and writes an editorial letter: open with the strengths (the voice, two unforgettable scenes), diagnose the structural issue plainly, then propose moving the catalyzing scene forward and seeding the central stakes in act one. No rewriting — a plan the author can execute in their own voice. The line edit waits until the structure holds. **The author's favorite paragraph has to go.** Cutting a magazine feature to length, the editor finds it runs 15% long and the slowest stretch is a lyrical three-paragraph digression the author clearly loves. Trimming it sentence by sentence would leave a weakened tangent. Instead the editor cuts the whole digression, protecting the spine and the best reporting, and frames the query around the reader: "AU: gorgeous writing, but it stalls the momentum right before the turn — can we lose it and let the next section land harder?" The cut is the editor's recommendation; the keep is the author's right. Framed as the reader's experience, not the editor's taste, it lands as help. **Change or query on an unusual sentence.** In a copyedit, the editor hits a deliberate sentence fragment used for rhythm — technically "incorrect," squarely in the author's established voice. A green editor would fix it; this one leaves it, because it's a voice choice, not an error. Two lines later sits a genuine ambiguity — a pronoun that could refer to either of two people. That's a comprehension failure the reader will trip on. So the fragment gets a stet, and the pronoun gets a query: "AU: 'she' — Maria or Joan?" Change the error, query the judgment, never confuse the two. - heading: Related Occupations markdown: >- The writer is the editor's counterpart and the relationship at the center of the work — one generates, the other refines. The copywriter shares the craft of clarity and consistency for a commercial aim. The journalist works the same fact-checking and house-style discipline under tighter deadlines. The interpreter and linguist share the close attention to language, register, and meaning, though in spoken and analytic registers. The film-editor performs the structurally analogous job — shaping someone else's raw material into its best sequence — in a visual medium. - heading: References markdown: |- - *The Chicago Manual of Style* — University of Chicago Press. - *The Copyeditor's Handbook* — Amy Einsohn. - *The Subversive Copy Editor* — Carol Fisher Saller. - *Garner's Modern English Usage* — Bryan A. Garner. - *Developmental Editing* — Scott Norton.