Loading BoundHive

Resume Illustrations After a Shared Character Reference Changes

Before resuming an illustration batch after a character reference changes, identify which requests and accepted images used the previous version. Update affected briefs, separate late results from current candidates, and review a small new sample for consistency. Do not regenerate unrelated artwork or accept old-reference output simply because it finished most recently.

Record the reference change as a specific decision

Identify what changed in the character reference and why. The revision might concern clothing, a distinctive feature, or a visual detail needed for the story. Save the previous and accepted versions with clear identifiers. A note saying “use the new character” is too vague if several reference files exist or only one element of the design changed.

For example, the author may replace a striped scarf with a plain one because the pattern distracts from small illustrations. That change affects scenes where the scarf is visible, but it may not affect a distant silhouette. Describe the scope before reviewing the batch. This helps the author distinguish necessary corrections from work that remains suitable as it is.

Identify requests that depend on the old reference

Review the pending queue and saved briefs for the previous reference version. Include requests that are already running or paused after partial completion. A task can retain old inputs even when the shared folder now contains a replacement file with a familiar name. Inspect the actual request record where available rather than assuming every task reads the latest version automatically.

Mark affected tasks for revision and leave unrelated tasks clearly separate. If a scene does not contain the character, its generation brief may need no change. This scope review preserves useful progress and prevents a small reference update from becoming an unnecessary restart of the entire illustration project. Record uncertain cases for inspection instead of making a blanket decision.

Symbolic publishing workflow for identify requests that depend on the old reference
Identify requests that depend on the old reference

Review accepted artwork according to the visible difference

Compare completed images with the new reference and identify which details matter in each scene. Some images may require correction, while others remain consistent with the accepted design. Keep the decision attached to the image and explain the reason. The author should not need to rediscover why one earlier illustration was retained while another was replaced.

Consider continuity across the reading sequence. A minor difference can become conspicuous when two images appear near each other. A detail that is invisible in one composition may be central in another. Review the artwork in context rather than assigning all images the same status solely because they were generated before or after the reference change.

Keep late results separate from the current batch

A request using the old reference may finish after the new reference has been accepted. Save that result with the request that produced it and review whether it still has a role. Its completion time does not prove it uses the current design. Do not allow an automatic assembly step to replace a reviewed image merely because a newer file appeared.

Update the acceptance record and any assembly controls the workflow actually supports. If the tool cannot enforce the distinction, use a separate candidate area and a deliberate selection process. The important requirement is that the final manuscript uses accepted artwork. Avoid relying on a status label that has no effect on how the publication files are assembled.

Symbolic review checklist for keep late results separate from the current batch
Keep late results separate from the current batch

Resume with a representative sample

Restart a limited set of corrected tasks that shows the changed feature clearly. Compare the outputs with the accepted reference and with retained images from earlier work. Check whether the new brief produces the intended change without introducing unrelated differences in the character's appearance. Resolve those issues before resuming the full affected queue.

Review the surrounding text and captions as well. A visual change can contradict a passage that describes the old feature. If the story deliberately changes the character's appearance over time, preserve that chronology rather than applying the latest design to every scene. The reference record should distinguish an editorial replacement from an in-story change.

Preserve the continuation record for the next pause

Save the accepted reference version, revised requests, retained images, replacement candidates, and unresolved decisions together. Include which images have been checked in the actual manuscript layout. This record gives the next session a concrete starting point and prevents old requests from returning without their review status.

Keep the origin information for retained generated artwork available for the publication review under current KDP guidance. A reference revision changes the design process, not the need to understand how the final images were created. A reliable resumption completes the affected work while preserving accepted decisions, making the illustration set consistent without discarding progress that still serves the book.

Frequently asked questions

Clear answers for this publishing decision.

Must every earlier illustration be regenerated after a reference change?

No. Inspect the visible difference and the scene’s role. Retain suitable artwork deliberately, and record why it remains consistent with the accepted design.

What should happen to an old-reference request that finishes late?

Keep it tied to its original request and review it as a candidate. Do not assume its recent completion makes it current or allow it to replace accepted artwork automatically.

Why resume with a small sample first?

A sample tests whether updated briefs produce the intended change while remaining consistent with retained images. It can reveal new differences before the entire affected queue runs.

Cover and spine

How wide does the full-wrap cover need to be, and how thick is the spine?

The cover width is back cover plus spine plus front cover plus bleed on both sides; the spine width is the final even page count multiplied by the paper-specific factor Amazon publishes, so the cover cannot be sized before the interior page count is final.

Prepare the cover in a book project

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

We could not save your subscription.