Edit by defect class, not by page number.
Reading from page one and fixing whatever catches your eye mixes incompatible jobs. You may rewrite a paragraph whose chapter is later removed, correct punctuation around an unsupported claim, or miss that six chapters end with the same conclusion expressed in different words.
A pass gives the editor one question and one stopping rule. Structure asks whether the book is the right book. Evidence asks whether readers can trust important assertions. The line edit asks whether the accepted meaning reaches the reader clearly. Keeping those questions separate makes decisions easier to audit and hand off.
Freeze a review copy
Preserve the manuscript you received, duplicate it for editing, and record the date, version, known sources, intended audience, destination, and decision-maker. Without a stable baseline, later reviewers cannot distinguish an original defect from an editorial change.
Use visible symptoms to choose the first investigation.
| Symptom | Likely defect | Fast test | Do not start with |
|---|---|---|---|
| Chapters sound polished but interchangeable. | No distinct chapter jobs or progression. | Summarize each chapter’s reader change in one sentence. | Rewriting introductions one by one. |
| The same advice appears under new headings. | Semantic repetition hidden by paraphrase. | Build a concept-by-chapter grid from a sample of three chapters. | Searching only for repeated phrases. |
| Claims feel specific, but references are thin. | Unsupported numbers, citations, or borrowed authority. | Trace five high-consequence claims to original sources. | Standardizing citation punctuation. |
| Advice is agreeable but hard to apply. | Missing actors, constraints, thresholds, and demonstrations. | Ask what a reader should physically do next and how success is observed. | Adding another list of general tips. |
| The book promises confidence everywhere. | Uncertainty and scope limits have been flattened. | Mark every universal, causal, and “best” statement in one chapter. | Making the tone more authoritative. |
Audit a representative slice before estimating the edit.
Select the introduction, one evidence-heavy chapter, one procedural chapter, and the conclusion. Record defects instead of silently fixing them. The sample should tell you whether the manuscript needs developmental editing, source reconstruction, substantive rewriting, line editing, or all four.
- Count chapter-level issues: missing premise, repeated job, sequencing problem, absent conclusion, or scope drift.
- Count claim issues: no source, wrong source, source not opened, quotation mismatch, outdated rule, or confidence beyond evidence.
- Count usefulness issues: generic example, missing step, untested instruction, undefined term, or no decision criterion.
- Count voice issues: generic authority, unexplained recommendation, false certainty, repeated rhetorical pattern, or abrupt tone change.
- Count production issues separately; formatting defects should not inflate the estimate for intellectual repair.
Report the sample and its limits. Four selected sections cannot prove that the rest of the book has the same defect rate, but they can reveal whether a quick proofread would be professionally misleading.
Seven passes, each with one approval question.
- Pass 01
Reconstruct the book
Purpose: Test whether the manuscript delivers one identifiable promise in a deliberate sequence.
Method: Write a one-sentence job for every chapter without using its title. Place those jobs beside the reader promise and look for detours, missing prerequisites, duplicate jobs, and a conclusion the chapters have not earned.
Pass when: Every surviving chapter changes what the reader knows, decides, or can do, and its position can be defended.
- Pass 02
Compress repetition
Purpose: Find repeated ideas that surface wording changes can hide.
Method: Track concepts, examples, definitions, cautions, and conclusions across chapters. Choose one primary home for each important idea; elsewhere, remove it, shorten it, or explicitly build on it.
Pass when: Repetition is intentional reinforcement or navigation—not accidental regeneration.
- Pass 03
Audit claims and attribution
Purpose: Separate supported fact, interpretation, personal experience, and unresolved assertion.
Method: Mark numbers, quotations, comparisons, causal claims, superlatives, medical/legal/financial implications, and statements about current platforms. Trace each to the original or rewrite it to match what is actually known.
Pass when: Every consequential claim has appropriate support, a truthful boundary, or has been removed.
- Pass 04
Replace generic examples
Purpose: Make guidance testable in a situation with real constraints.
Method: For each major recommendation, add an observed case, a reproducible demonstration, or a clearly hypothetical scenario with named conditions. Include the difficult choice, not only the successful outcome.
Pass when: A reader can see what the advice looks like, when it applies, and where it may fail.
- Pass 05
Restore the author’s judgment
Purpose: Remove language that sounds complete while avoiding a position.
Method: Highlight recommendations, caveats, transitions, and conclusions. Ask who is making each judgment and on what basis. Rewrite interchangeable summaries with the author’s reasoning, experience, limits, and criteria.
Pass when: The manuscript reflects accountable choices rather than averaged plausibility.
- Pass 06
Repair continuity and sentences
Purpose: Make the book consistent at both long and short range.
Method: Check terms, names, chronology, examples, promises, cross-references, and chapter handoffs before the line edit. Then cut throat-clearing, stacked qualifiers, empty conclusions, vague pronouns, and sentences that hide the actor or action.
Pass when: Definitions stay stable, references resolve, and each paragraph advances a clear job.
- Pass 07
Proof the reader’s artifact
Purpose: Catch defects introduced by formatting, conversion, and distribution preparation.
Method: Inspect the exported edition outside the editor. Navigate from the table of contents, follow links, review image alternatives and captions, change screen or type size where possible, and inspect page behavior appropriate to the format.
Pass when: The exact file readers will receive has passed a recorded release check.
Find repeated meaning with a concept map.
Phrase matching catches copied wording. It does not catch the same point regenerated with different nouns and sentence shapes. Build rows for the book’s recurring concepts and columns for chapters, then note the job each appearance performs.
| Concept | Chapter 2 | Chapter 5 | Chapter 8 | Editorial decision |
|---|---|---|---|---|
| Start with one outcome | Full explanation and first example. | Explained again with a new metaphor. | Restated as a conclusion. | Keep the teaching in Chapter 2; turn Chapter 5 into a brief cross-reference; test the idea in Chapter 8 instead of restating it. |
| Interview the reader | Mentioned without a method. | Five-step method and sample questions. | No appearance. | Foreshadow the need in Chapter 2 and keep the usable method in Chapter 5. |
| Measure before changing | Presented as a universal rule. | Presented as a general best practice. | Case shows an exception. | Define the conditional rule once, then use the exception to refine it. |
Some repetition is necessary. A definition may need a short reminder, and a complex process may need a checkpoint. The map forces the editor to name the second appearance’s job. “The model said it differently” is not an editorial purpose.
Give every risky claim an owner and a disposition.
A comment that says “fact-check” only moves uncertainty to another person. A claim ledger captures the passage, risk, required source, reviewer, deadline, and final decision. Prioritize by possible harm and decision impact, not by how easy a statement is to search.
| Claim type | Required check | Unacceptable shortcut | Possible disposition |
|---|---|---|---|
| Number or percentage | Open the original data, inspect population, method, date, and unit. | Citing an article that repeats the number without showing its source. | Support with context, qualify, replace, or remove. |
| Direct quotation | Compare the exact words, speaker, date, and surrounding context. | Assuming quotation marks in the draft prove the quotation exists. | Confirm and cite, convert to accurate paraphrase, or delete. |
| Current platform rule | Check the platform’s live official documentation near release. | Using an undated forum answer or an older generated explanation. | State with review date and direct source, or avoid the claim. |
| Personal result | Confirm records and describe the exact conditions and author. | Presenting one person’s outcome as a typical guarantee. | Use as a bounded case, strengthen with evidence, or exclude. |
| High-stakes instruction | Obtain suitable expert and primary-source review for the domain. | Adding a disclaimer while leaving unsafe guidance unchanged. | Expert-review, narrow, redirect to professional help, or remove. |
Replace general approval with an observable decision.
Draft under review
“Effective client onboarding is essential for project success. Clear communication, aligned expectations, and regular feedback help teams build trust and achieve better outcomes.”
What is missing
No actor, moment, artifact, threshold, conflict, evidence, or next action. Almost any services chapter could contain the paragraph without changing the reader’s behavior.
Revision with a job
“Before the kickoff call, send the client a one-page decision sheet: named approver, deliverables, exclusions, review dates, and the action that counts as approval. If the client cannot name the approver, resolve that first; more status meetings will not repair an absent decision owner.”
What the editor must still ask
Is this the author’s tested method? Does “will not repair” overstate the evidence? Is a one-page sheet suitable for every project described? The revision is more useful, but specificity still requires verification.
Maintain a continuity sheet outside the manuscript.
Long drafts can change vocabulary, assumptions, chronology, and promises without producing an obvious local error. Record the canonical form of details that must remain stable, then check every occurrence.
- Terms: preferred name, first definition, allowed shorthand, and terms deliberately avoided.
- People and cases: spelling, role, pronouns, permissions, chronology, and what the example is allowed to prove.
- Numbers: unit, time period, calculation source, rounding rule, and every downstream use.
- Promises: outcomes introduced in the opening and where each is fulfilled or explicitly limited.
- Cross-references: chapter names, section destinations, figure numbers, links, and references to material that may have moved.
- Instructions: prerequisite, action order, expected result, exception, and recovery step when the result does not occur.
A score can locate a review task; it cannot make the editorial decision.
Grammar and style checks
Useful for possible mechanical defects and patterns. They cannot determine whether the sentence is true, necessary, fairly attributed, or appropriate for this reader.
Similarity searches
Useful for locating matching language for human review. A match still needs context, source, rights, quotation, and attribution analysis.
AI-origin detectors
Do not use a single score as proof of who authored a passage. Evaluate process records and the manuscript itself against the required standard.
Automated citation checks
Useful for broken identifiers and missing fields. The editor still has to open the source and confirm that it supports the exact claim in context.
Use a stop/go release gate, not “looks finished.”
| Area | Go when | Stop when |
|---|---|---|
| Purpose | The title, opening, chapters, and conclusion deliver the same bounded promise. | A surviving chapter cannot explain its contribution to that promise. |
| Evidence | High-risk claims have documented review and lower-risk facts were checked systematically. | A material quotation, citation, statistic, or current rule remains unresolved. |
| Authorship | The named author has supplied or approved the substantive examples, reasoning, limits, and recommendations. | No accountable person can explain or defend important advice. |
| Rights and rules | Permissions, licenses, disclosures, and destination requirements are documented. | Ownership, confidentiality, permission, or required disclosure is still unclear. |
| Artifact | The final file has working navigation, readable content, valid links, and format-appropriate behavior. | Only the editable source—not the reader-facing edition—has been reviewed. |
Use current standards and destination rules during final review.
Editing can identify a decision, but the applicable platform or technical authority defines rules that may change. Record when those sources were checked and return to them immediately before release.
- NIST AI 600-1: Generative AI Profile — risk-management context for false or confidently stated content and other generative-AI risks.
- Amazon KDP Content Guidelines — current publisher responsibilities and platform content requirements.
- W3C EPUB 3.3 — the normative specification when the reviewed delivery artifact is EPUB.
- W3C WAI image tutorials — purpose-based guidance for reviewing alternatives to informative, functional, complex, and decorative images.
Set expectations before the manuscript enters production.
How do you edit an AI-generated book?
Edit from the book level downward. First test the reader promise and chapter sequence; then review repetition, claims, examples, author judgment, continuity, sentences, and the exported artifact. Starting with grammar can polish material that should be cut or rewritten.
How much editing does an AI-assisted manuscript need?
There is no reliable percentage. The work depends on the sources, subject risk, instructions, model output, author contribution, and publication standard. Estimate from a representative sample and track defects by type instead of assuming a fixed amount of cleanup.
Can an AI detector prove who wrote a book?
A detector score should not be treated as proof of authorship or misconduct. Use production history, source notes, version records, interviews with the author, and direct manuscript review to evaluate how the work was made and whether it meets the required standard.
What should an editor fact-check first?
Prioritize claims that could cause harm or materially change a reader’s decision: health, legal, financial, safety, technical, current-platform, numerical, causal, comparative, and attributed statements. Then review lower-risk factual details systematically.
Write the chapter-job map before changing a sentence.
Duplicate the manuscript, summarize each chapter’s contribution, and mark any pair that performs the same job. That single map reveals whether the next action is restructuring, merging, or a closer evidence review. If the drafting process itself is still being designed, begin with how to write a book with AI. Before final production, use the EPUB, PDF, and DOCX guide and the ebook image review guide.