Independent research · Source-linked guidance
Home / Deliver / Hand off an approved image without version confusion
Practical guide

Hand off an approved image without version confusion

Last materially reviewed 2026-09-25

Quick answerDeliver one clearly identified production version with its specification and keep alternatives outside the delivery folder.
What to know

Make approval refer to a file

A message saying “looks good” is ambiguous when several crops and enhancements exist. Identify the exact filename, dimensions and intended output in the approval record. Keep the unprocessed source and working candidates elsewhere. The delivery folder should make the correct choice obvious without deleting useful history. If a collaborator needs a placement reference, label it as a reference and distinguish it from the high-resolution production object.

What to know

Keep a small manifest

Record the production file, finished size, crop or border instruction, accepted format and any unresolved item. Include the date or version of the printer specification when relevant. Do not collect unnecessary personal details or send them to analytics. The manifest is a practical handoff note, not a legal certification. Its value is that another person can see what was approved and avoid silently substituting a different image or export.

What to know

A changed-crop example

A fictional client approves an 8 by 10 inch crop, then asks for a 12 by 18 inch version. That is not merely a renamed file. The aspect ratio, retained pixels and output requirements can change. Create a new candidate, recalculate the dimensions and review the affected edges and detail. Keep the original approval associated with the original version. Do not claim that the first proof approves every later crop or enlargement.

What to know

Close the loop with the receiver

Ask the printer or collaborator to confirm the intended production file when the workflow permits it. Inspect any order preview for obvious placement errors. Preserve the approved file after delivery according to your retention needs so a repeat order can use the same evidence. If a later issue appears, compare the produced version with that retained file before changing the master. Clear version identity makes a targeted correction possible and prevents unnecessary repeated enhancement.

Continue when useful

Next: Check the downloaded file, not just the preview

Reopen the exact export and verify its properties before sending it to a printer.

Open Check the downloaded file, not just the preview →
Keep exploring

Related guides

Check the downloaded file, not just the previewReopen the exact export and verify its properties before sending it to a printer.The five questions to ask before handing off a print fileConfirm finished size, crop, resolution, file format and color handling with the actual printer.Batch enlargement: approve a sample before scaling the jobGroup similar sources, prove representative files and review exceptions instead of treating a completed batch as an approved batch.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Let's Enhance print-preparation help (September 16, 2026) — Merchant documentation · help.letsenhance.io · Merchant-controlled · checked 2026-09-25
  2. Adobe image size and resolution reference — Merchant documentation · helpx.adobe.com · Merchant-controlled · checked 2026-09-25