An annotated preview should make feedback easier to locate without covering the artwork needed to understand it. Heavy arrows, opaque boxes, and long comments placed over faces can obscure the very relationship under review. Keep a clean image available, use concise numbered markers, and attach explanations in a way that preserves both context and the exact location of each issue.
Separate the artwork from the explanation
Export a clean preview of the reviewed revision and retain it unchanged. Create an annotated copy with the same revision identifier so reviewers can compare them. A clean reference prevents markup from being mistaken for part of the illustration and lets someone inspect an area hidden by a comment. Do not use an earlier clean version that differs from the annotated image.
Use small markers near the relevant area rather than large opaque text blocks across it. Number the markers and place the corresponding notes in a margin or accompanying list. Each note should describe one visible issue or decision. A comment containing several unrelated requests becomes difficult to track when only one part is resolved in the next revision.
Keep directional lines short and unambiguous. If a marker refers to a hand behind a prop, end the line close enough that ownership is clear without crossing the entire composition. Use a consistent markup color that remains visible against the image, but avoid excessive visual emphasis that makes secondary comments look more important than the main unresolved decision.
Make the preview support an actionable review
Write notes that distinguish observation, proposed solution, and question. Hand merges with bag is an observation; separate the wrist contour is one possible solution; should the bag remain in this position is a decision request. Keeping these meanings clear helps reviewers respond appropriately. Otherwise, a speculative suggestion may be interpreted as a mandatory instruction or a problem statement may receive only a cosmetic answer.
Include a full view and targeted detail crops when necessary. A close crop can reveal a small label problem, while the full image shows whether the correction affects hierarchy or space. Keep crop scale and location identifiable. Do not let the review become a collection of enlarged fragments whose local improvements cannot be assessed against the composition as a whole.
Provide the preview in a format the agreed reviewers can open and comment on reliably. Check that exported markup is legible at ordinary viewing size and that no hidden draft note appears. If using a shared review tool, confirm which version the comments attach to. A comment floating across several updated versions can become ambiguous even when its original placement was precise.
After review, consolidate the markers into a revision list and preserve the annotated preview as evidence of that round. Remove markup from delivery files unless explicitly requested as documentation. A useful annotated preview helps people locate, discuss, and close specific decisions while leaving the underlying artwork visible enough to judge the consequences of the proposed changes.