Coordinate Text and Image Revisions With Change Requests

When a revision affects both words and artwork, write one change request that names the reader problem, the affected text, the affected images, and the acceptance checks. Assign the work by component but review the resulting combination. This prevents separate text and image updates from solving different versions of the same problem.

Describe the shared reader problem first

Start with what the reader cannot understand or do in the current version. A craft guide might describe an assembly step correctly while its illustration shows the parts in a different order. Naming that mismatch is more useful than issuing two disconnected requests to improve the paragraph and redraw the figure. The shared problem gives both contributors the same outcome to work toward.

Include the accepted starting versions of the passage and image. If a writer reviews yesterday’s diagram while an illustrator follows an older paragraph, both can produce reasonable changes that remain incompatible. Attach enough surrounding context to show how the affected step relates to the preceding and following instructions. A change request should narrow ambiguity before generation or editing begins.

Identify dependencies beyond the obvious pair

List the caption, labels, references, and neighboring images that depend on the revised material. Changing the name of a component in one paragraph may also affect a parts list and a later troubleshooting section. Replacing a diagram can alter what the caption needs to explain. These dependencies are easy to overlook when each tool presents only its own current input and output.

Use stable working identifiers for the affected assets and sections so the request remains understandable if pagination changes. Record which components need editing and which only need verification. That distinction keeps the work bounded. It also prevents unnecessary regeneration of accepted material simply because it appears near a revised element in the manuscript.

Decide the order of work before generating replacements

Identify which decision must be settled first. If the instructional sequence is changing, accept the revised sequence before asking for final illustrations. If a physical detail in the artwork reveals that the proposed explanation is impossible, resolve that detail before polishing the prose. The order should follow the dependency, not whichever generation tool happens to be easiest to run.

Separate exploratory outputs from accepted replacements. A draft image can help the writer evaluate a spatial explanation without being ready for publication. Label it accordingly and preserve the current accepted asset until a replacement passes review. This allows experimentation without making a temporary concept look final when it is imported into the working manuscript or passed to another contributor.

Review the combined result against explicit checks

Define the acceptance checks in terms of the reader’s task. The paragraph should name the same components shown in the diagram; the sequence should show a result the instructions can produce; and the caption should clarify rather than contradict the image. Add project-specific details such as a required orientation or a visible connection. Avoid a single approval question about whether the new version looks better.

Place the revised components together and have a reviewer follow the task without relying on the change discussion. Check each dependent location listed in the request. If the image is accepted but the caption still uses an old label, keep the request open. Component-level approval is useful, but the work is complete only when the combined presentation resolves the original problem.

Carry the accepted change into the release record

Record the accepted text and asset versions, the reviewer, and the checks performed. Update the manuscript’s links to the assets so the next export uses the correct files. Retain rejected alternatives outside the accepted asset set. Otherwise, a later collaborator may select a visually similar draft and reintroduce the mismatch without realizing that the issue had already been resolved.

Inspect the exported pages after integration, using the relevant format-preparation guidance. Layout changes can separate a caption from its image or reduce a meaningful detail below a useful reading size. Close the request against the reviewed output, not just the generation results. For a later revision, the record should explain why the change was made and what relationships must remain consistent if the text or artwork changes again.