Send a numbered annotation copy together with the exact unmarked image and one clear instruction per number. State the crop and version before using coordinates. A circle saying fix this does not explain the desired result, and annotations baked into the only master can become accidental artwork in the final delivery.
Freeze the reference version
Choose the image being discussed and give it a stable name. Export an annotation copy with the same crop and orientation. If the editor sees a different revision or mirrored crop, a clear-looking arrow may point to the wrong detail.
Apple documents photo markup as a way to draw or write on an image. Other supported tools can serve the same communication purpose. Keep markup as a review artifact, separate from the clean image; do not assume every file format retains independently editable annotation objects.
Write actionable local instructions
For each numbered area, state the symptom, desired change and protected boundary. For example: area 2, reduce the bright table distraction; keep the cup outline and printed label unchanged. Avoid contradictory requests such as make the face identical but dramatically change its expression without explaining the tradeoff.
When needed, add normalized coordinates measured from the image's top-left corner. A point at 25 percent of width and 40 percent of height can remain understandable across displayed sizes, provided both people use the same crop. Define that convention explicitly; it is a communication choice, not a universal editor feature.
A hypothetical product-photo revision
Imagine a seller sending a cup image with three numbered notes: a background spot, a shadow boundary and a label that must remain exact. The clean source and annotation share the same version. The editor repeats the intended actions before changing the photograph, then returns a revision with each note marked resolved or still uncertain.
This is a planning example. Numbering lets the seller approve a repaired background while rejecting a changed label, rather than giving one ambiguous approval to the whole image.
Preserve the clean source through generation
For an Imagild local edit, use the unmarked source unless the selected tool explicitly expects a mask or drawing input. Uploading red arrows as ordinary image content can encourage their inclusion in the result. Translate review notes into supported selections and instructions; do not assume the model knows which drawn marks are commentary.
If the image is recropped, issue a new annotation version. Coordinates and arrows from an earlier crop are no longer dependable. Keep a short revision log without exposing unnecessary private details.
Acceptance and handoff
Review each numbered request against the clean source, and verify that untouched protected details remain. Deliver the approved clean output separately from the annotated comparison. No arrows, circles or draft notes should remain unless deliberately requested as visible content. The communication passes when both people can identify the same region and the same desired change.