Separate Art Feedback From Manuscript Corrections

When an illustration conflicts with a book passage, identify where the problem originates before revising either asset. Separate art-direction feedback from factual or narrative corrections to the manuscript. Give each issue a clear owner and affected version, then verify the text and image together after the chosen change is made.

Describe the mismatch before proposing a fix

Record what a reader sees and what the manuscript says. For example, the text may describe three objects while the image shows four, or the image may depict an action that the instructions never introduce. State the discrepancy without assuming that the image is always the incorrect side.

Include the relevant passage, image version, and caption in the issue record. A reviewer looking at an older draft can create a false conflict or request a change already made. Identifying the actual pair of artifacts is the first step toward a useful correction.

Classify the source of the problem

An artwork issue may involve composition, visibility, continuity, or an inaccurate detail. A manuscript issue may involve an incorrect description, missing step, or outdated scene. A connection issue may arise because a correct image was placed beside the wrong passage or paired with an old caption.

Keep the classification provisional until the evidence supports it. Some problems require changes to both text and image. The purpose is to route the investigation clearly, not to force every issue into one exclusive category when the book's content has genuinely changed.

Identify the authority for the correction

Use the approved manuscript, source records, scene plan, or subject review to determine what should be depicted. Do not let the most polished artifact become the authority merely because it looks finished. A beautiful illustration can be wrong, and an approved-looking paragraph can still contain an unresolved error.

Assign the decision to the person or role responsible for the relevant content. A designer can assess visual clarity, while a subject editor may need to resolve the underlying explanation. Keep those contributions connected so a visual adjustment does not silently make a new factual claim.

Write a bounded revision request

Specify the change, the reason, and the elements that should remain stable. If the manuscript is correct and only an object count is wrong, request that correction without inviting a new composition, character design, and background. A focused brief reduces the chance that the repair introduces unrelated differences.

If the text needs correction first, update the source passage and approve the new meaning before regenerating the illustration. Otherwise the image request may encode a tentative explanation that changes again immediately. Record the source version used for the revised artwork.

Keep review states distinct

Track whether the content decision is resolved, whether the revision has been produced, and whether the combined result has been checked. Those are separate milestones. A completed generation request should not automatically close the editorial issue if nobody has compared the result with the corrected passage.

Retain rejected variants with an appropriate status when their history is useful, but keep them outside the selected release assets. Clear states help a resumed workflow avoid accepting an older image simply because it is available and visually similar to the approved one.

Verify the repaired relationship in context

Review the final image, passage, caption, and any cross-reference at their actual location in the book. Confirm that the original mismatch is resolved and that the change has not created a new one elsewhere. A corrected figure may also appear in a contents preview or companion resource that needs updating.

Save a concise resolution note identifying the accepted versions and the basis for the decision. This gives later editors a way to understand why the pair changed without reopening the same question. The workflow should finish with a coherent reader experience, not merely a record that someone edited both files.