How Do I Turn Continuity Findings Into Edits?

Turn a continuity finding into an edit by moving through five decisions: Is the conflict real? Which fact should be canon? What depends on it? What is the smallest sufficient change? How will you verify the result? Do not correct the nearest sentence before understanding the causal chain.

Verify the finding

Open every cited passage and read the surrounding scene. Identify the speaker, viewpoint, time layer, and degree of certainty. A line may be a lie, joke, mistaken belief, hypothetical plan, dream, or intentional contradiction.

Label the finding confirmed, ambiguous, intentional, or false positive. Only confirmed problems enter the edit queue. Ambiguous findings can become clarity questions if readers are receiving the wrong effect.

Suppose a report says Mara carries the silver key after losing it. In the later scene, “the key” might refer to a brass key introduced nearby. The edit may be a clarifying adjective, not a plot repair.

Choose canon before wording

When two facts genuinely conflict, decide which supports the book’s chronology, characterization, world rules, and future scenes. Do not assume the earliest mention must win. A later fact may be central to the climax and easier to establish earlier.

Write the decision plainly: “Mara loses the silver key in chapter nine and never recovers it; chapter fourteen must use the brass archive key.” Add the reason if collaborators or future books may revisit it.

Map dependencies

Search for every mention of the fact and every action that relies on it. Dependencies are often indirect. Changing an arrival date can alter weather, sleep, meals, message delivery, alibis, injuries, and who can attend a meeting.

Create a short impact list:

• establishment scenes;
• later uses or references;
• character knowledge;
• emotional consequences;
• timeline and location;
• story-bible entries;
• future-volume callbacks.

Rank the impact. A cosmetic description may need two edits. A changed parentage can affect the whole book.

Edit from cause to effect

Fix the earliest point that should establish the chosen canon, then move forward in narrative or event order. This prevents later patches from preserving a broken cause.

Imagine a character reaches the capital on Tuesday in one chapter and remembers a Wednesday arrival later. If the Tuesday arrival enables a meeting that night, changing the first date may break the plot. Keep Tuesday, correct the memory, and inspect all references to nights spent in the city.

Prefer the smallest edit that makes the intended truth and reader experience clear. Sometimes that is a word. Sometimes a bridge scene, altered decision, or reordered chapter is necessary. Do not use a line of explanation to hide a structural gap.

Recheck the sequence

Read the edited scene, the scene before it, and every dependent scene. Check continuity domains together: time, place, knowledge, state, motivation, and relationships. A technically corrected fact can still produce an emotional jump.

If the edit changes a repeated term or name, search the entire manuscript again. If it changes structure, update chapter references and rerun the relevant focused check after saving a stable version.

Mark the finding resolved only when the text and supporting records agree.

Prioritize a queue

Use impact and dependency rather than discovery order. A practical order is:

1. errors that break causality or the ending;
2. identity, knowledge, and chronology conflicts affecting several scenes;
3. relationship or physical-state gaps;
4. local description and terminology;
5. optional clarity improvements.

Limit active work. Completing one dependency chain is safer than partially fixing five unrelated findings.

Common mistakes

Do not edit before verification. False positives can destroy intentional complexity.

Do not change both conflicting facts toward a vague compromise unless ambiguity is the goal.

Do not fix the later symptom while leaving the earlier cause untouched.

Do not update only prose and forget timelines, character records, or series canon.

Do not close a ticket because a sentence changed. Reread the downstream result.

Do not treat all findings as equally urgent. Protect the logic that readers need first.

A finding is finished when the story agrees

The endpoint is not a clean report. It is a manuscript in which the chosen fact, its causes, and its consequences form one coherent version. Record that canon, preserve the draft version, and move to the next bounded issue.

Use How to Use LoreVia During a Revision Week to fit this process into a practical cadence, or revisit What Is a Continuity Checker for Fiction? to distinguish useful flags from editorial decisions.

Before you close the finding

Write the corrected fact as one plain sentence and name the manuscript version. Search that version again, then read the affected sequence without your editorial notes. If a new reader would encounter one coherent truth—and every intentional exception is signalled—the finding can be closed.

Keep the evidence with the decision for future revisions.

Broader guide: How to Use LoreVia During a Real Revision Week