Before resuming a research-based manuscript, identify every completed passage and queued request that depends on a replaced source. Review the affected claims, update the approved reference material, and resume only the work whose inputs and revision status are understood.
Describe why the source changed
A source can be replaced because it is outdated, unsuitable for the audience, contradicted by stronger evidence, or simply cited incorrectly. These reasons create different revision tasks. Record the specific problem before removing the old reference, so the team knows whether the underlying claim changed or only its supporting citation did.
For a practical guide, an updated manual might describe a changed procedure, while a better introductory source might explain the same procedure more clearly. The first case can require substantive rewriting. The second may require checking the explanation and attribution without discarding every approved paragraph. The reason for replacement guides the scope of the review.
Find dependencies beyond the reference list
Search the manuscript, notes, outlines, and pending generation briefs for the source's title, identifier, and distinctive claims. A citation search alone may miss a paraphrase or an example derived from the old material. Inspect likely sections even when they no longer contain an explicit reference after earlier editing.
Create a dependency record that separates completed text, approved text, unreviewed drafts, and queued work. Include illustrations or tables whose labels or values depend on the source. This map shows where a resumed process could reproduce the old information and where existing content needs a human decision before it remains part of the book.

Compare claims rather than replacing citations mechanically
Read the old claim and the proposed replacement evidence together. Confirm that the new source actually supports the statement at the level of certainty used in the manuscript. A related source does not necessarily establish the same conclusion, and a newer publication is not automatically a substitute for every detail in an older one.
Revise the claim when the support changes. That may mean narrowing its scope, explaining a condition, changing an example, or removing the statement. Do not retain a confident sentence and merely attach a new citation to make the reference list look current. The reader needs a supported explanation, not just a recently dated source entry.
Update pending requests before resuming them
Inspect the actual saved inputs for queued generation work. A current research folder does not guarantee that an existing request contains the updated material; it may carry an older excerpt or summary prepared before the change. Replace the affected inputs and record the reference version that the resumed request will use.
Keep the old and revised request records distinguishable. If an earlier response arrives after the replacement decision, it should not silently become the current chapter draft. Review it against the updated evidence before accepting any useful material. The resume point should identify both the task's progress and the approved information on which it depends.

Preserve unaffected editorial work
A source change does not necessarily invalidate the whole manuscript. Use the dependency map to isolate affected explanations while retaining unrelated approved prose. If a chapter combines several sources, mark the specific passages that need revision instead of overwriting the complete chapter with a newly generated version by default.
Review transitions and examples after the targeted change. A corrected claim can leave a nearby conclusion unsupported or make an illustration irrelevant. The narrow edit is successful only when the surrounding argument still works. Save the revised section with a note explaining the source change so later editors can understand why the text differs from the earlier approved draft.
Complete the review before closing the source issue
Check that the manuscript, reference list, queued briefs, and relevant visual materials now use a consistent interpretation of the approved evidence. Preserve any unresolved claim as an open issue rather than marking the source replacement complete merely because the old file has been deleted from the active folder.
Keep generated-content provenance with the revised material. KDP's content guidance leaves responsibility for accuracy and rights with the publisher, and replacing a reference does not erase how a passage was produced. Resume the remaining workflow with clear inputs and review states, then verify the exported book against the completed source-change record.
Frequently asked questions
Clear answers for this publishing decision.
Does a newer source mean every related paragraph must be rewritten?
No. Compare the actual claims and identify what changed. Some passages may remain supported, while others need narrower wording, new explanations, or removal.
Why inspect queued requests if I already updated the research folder?
A saved request may contain copied excerpts or summaries from the old source. Verify the inputs that will actually be sent rather than assuming they refresh automatically.
Can I delete the old source record after replacement?
Retain enough history to explain the revision and trace earlier claims, while keeping superseded material out of active drafting inputs. The project should distinguish historical evidence from currently approved references.
How do I get from an idea and a brief to an editable manuscript I can finish?
Write the brief first, generate a structure you can edit, then draft and revise the manuscript in reviewable sections so one change never overwrites work you already approved.
Start a book project from a brief