Separate Source Evidence From Editorial Approval Records

Store source evidence and editorial approval as related but separate records. A citation identifies support to examine, while an approval records a decision about a specific version and scope. Connect both to the accepted passage or asset so later revisions can show what was checked, by whom, and which changes require another review.

Define the questions each record answers

A source record identifies where information came from and what it is intended to support. An editorial approval identifies what a reviewer accepted and under what scope. These records can refer to the same passage without proving the same thing. Keeping them distinct prevents a workflow from treating the presence of a citation as confirmation that someone checked it.

For example, a practical guide may cite an official instruction page beside a draft paragraph. The citation shows a proposed source relationship. It does not establish that the paragraph accurately represents the page, that the source is current, or that the final wording was accepted. Those questions need their own evidence and decisions.

Link the source to the actual claim

Record the claim or passage the source supports, along with enough detail to locate the relevant evidence. Avoid attaching a broad source label to an entire chapter when it supports only one part. The relationship should remain understandable after the chapter is reorganized or split into smaller sections.

Keep qualifications from the source visible in the working record. A reviewer may accept a narrow statement but reject a broader interpretation. If both versions simply carry the same citation, later editing can obscure that decision. Preserve the accepted scope so a stronger-sounding rewrite does not inherit an approval that belonged to different wording.

Record what the reviewer actually reviewed

Identify the version, passage or asset, review purpose, and result. A proofreader checking punctuation has not necessarily verified technical claims. A subject reviewer may assess content without approving the final layout. Describe the scope accurately rather than reducing all review activity to a single generic approved label.

Keep unresolved findings separate from accepted work. A reviewer can accept most of a chapter while leaving one source question open. The workflow should preserve that distinction through assembly. Otherwise, a summary status can make a partial approval look complete and allow an unresolved claim to enter the release without a deliberate decision.

Treat substantive revisions as new review questions

When wording changes, compare the revision with the scope of the previous approval. A spelling correction may leave the reviewed claim intact, while a new conclusion or removed qualification can change its meaning. Record the appropriate follow-up instead of either redoing every review automatically or assuming all edits are covered by the original sign-off.

For example, replacing a conditional statement with an unconditional one should trigger another look at the source relationship. The citation may still be the same, but the claim being made is different. A useful workflow makes this dependency visible so the author can direct attention to changes that affect substance rather than relying only on file dates.

Preserve records when tools or contributors change

If the manuscript moves to another tool, test whether source links, comments, and review decisions remain available. Keep an independent record where needed rather than assuming that an export includes every annotation. The author should still be able to explain why a passage was accepted after the original editing interface is no longer in use.

Preserve content-origin information separately as well. KDP distinguishes generated and assisted content, and that creation history is not established by a citation or an editorial approval. A passage can be sourced, generated, and reviewed, with each fact answering a different question. Keep those relationships clear instead of collapsing them into one status that hides important distinctions.

Reconcile the records with the final publication package

Before release, compare the accepted manuscript and assets with the source and approval records. Check that retained material has the required evidence and that approvals identify the actual versions used. Remove obsolete alternatives from active assembly while preserving useful history. A record for a discarded draft should not be used as proof about a replacement passage.

Save a concise release view showing the accepted files, the relevant reviews, and any remaining decisions. The purpose is not to create paperwork for its own sake. It is to make the book's evidence and judgment traceable when someone asks what supports a claim or why a revision was accepted. Clear separation lets each record do its own job without being mistaken for a broader guarantee.