Loading BoundHive

Trace Third-Party Material Through a Manuscript Revision

Track third-party material by stable item identifiers as well as page locations during a manuscript revision. Record what each item is, where it came from, how the revised book uses it, and which supporting permission or review record applies. Moving an item to a new chapter should not sever that evidence, and changing its use should trigger a fresh review of the relevant documentation.

Inventory the material before rearranging chapters

List quotations, photographs, illustrations, supplied tables, and other outside material that appears in the current manuscript. Include items in captions, exercises, appendices, and cover assets where relevant. Give each item a stable identifier and link it to the source file or bibliographic record. Page numbers can be included as a convenience, but they are too fragile to be the only connection when the manuscript is about to change.

For a quotation used in a chapter opening, record the exact passage and attribution as well as its location. For a supplied photograph, record the actual asset file rather than only a descriptive filename in a spreadsheet. The inventory should let an editor distinguish two similar images or two excerpts from the same source. It is a traceability tool, not an automatic conclusion that every listed item is cleared for publication.

Connect each item to the available supporting record

Attach the relevant correspondence, agreement, license record, or other documentation the project relies on. Summarize the intended use in plain language and identify any unresolved questions without attempting to settle them through a generic checklist. If the documentation is missing or ambiguous, mark the item for appropriate review. Do not turn an empty field into an assumed approval because the material appeared in an earlier version.

Keep source attribution separate from permission status. A citation can explain where material came from while leaving other questions unresolved. Similarly, a note that an image was supplied by a collaborator does not describe every condition of its intended use. The author needs a record that allows the actual documentation and actual proposed use to be compared. KDP's content guidance places responsibility for publishing rights with the publisher; the inventory supports that responsibility without replacing review.

Symbolic publishing workflow for connect each item to the available supporting record
Connect each item to the available supporting record

Track what changes when the material moves

When a chapter is split or reordered, update the location field for each affected item while preserving its identifier. Inspect surrounding text and captions after the move. A quotation originally discussed critically may now appear as an isolated inspirational statement, or an image may acquire a new crop and a different explanatory role. Those changes matter to the editorial review even if the underlying source file has not changed.

Use a change column to distinguish location-only moves from changes to content, presentation, or intended use. Describe the actual difference instead of writing simply updated. If a revised use requires a decision about the supporting documentation, route that specific question to the person responsible for resolving it. Do not ask an AI assistant to infer permission from the age of the source or from the fact that an earlier editor accepted it.

Reconcile removals and replacements explicitly

Mark removed material as excluded from the current edition and check that it is absent from the final manuscript, captions, and supplementary assets. Keep the historical record where useful rather than deleting every trace. If a new item replaces an old one, assign the new item its own identifier and evidence. Reusing the old approval label for a different asset can make the inventory look complete while concealing the actual substitution.

For rewritten passages, check whether direct quotations became paraphrases or whether an adaptation still depends on an outside source. Document the revision and review the actual result. A wording change should not be treated as a universal shortcut around attribution or other concerns. Where the project cannot resolve an item confidently, choose an appropriate review path or remove the dependency before release instead of burying the uncertainty in a general note.

Symbolic review checklist for reconcile removals and replacements explicitly
Reconcile removals and replacements explicitly

Match the inventory to the final files

At the release checkpoint, inspect the actual interior and cover exports against the current included-item list. Confirm identifiers through captions, filenames, or other reliable project references. Check that required attribution text approved for the project survived layout changes and that excluded alternatives were not reintroduced from an older source file. The final record should describe what the reader receives, not only what the editor intended to include.

Archive the matched inventory, relevant documentation, and release identifiers together. A later revision can then begin with a known set of included material and unresolved questions rather than a search through disconnected email threads. This process does not provide a legal determination about any particular use. It makes the evidence and decisions visible so an author can obtain the appropriate review and avoid losing that review history during ordinary manuscript work.

Frequently asked questions

Clear answers for this publishing decision.

Is a source citation the same as a permission record?

No. Keep the attribution and the supporting permission or review documentation distinguishable so each can be checked against the actual material and intended use.

Should a moved image receive a new inventory identifier?

A location change can retain the existing identifier while updating the location and use notes. A different replacement asset should have its own identity and supporting record.

Can an earlier edition settle every question about a revised use?

Do not assume that it does. Compare the current material and intended use with the available documentation, and route missing or ambiguous points for appropriate review.

Get all of our updates directly to your inbox.
Sign up for our newsletter.

We could not save your subscription.