A finished photograph still has work to do after it leaves the editing software. Someone needs to choose the right file, place it in a layout, attach the correct caption and understand any limits on its use. A confusing handover can make a good selection unnecessarily difficult to publish.
I aim to make the delivery understandable without a long explanation on the phone. The recipient should be able to tell what is approved, which files suit which uses and where to ask if something is missing.
Deliver a selection, not your working process
Keep the approved images separate from test exports and unfinished edits. If the recipient is choosing from proofs, label that stage clearly. A folder of near-identical files with different treatments makes it easy to publish a version you did not intend to supply.
Check the final set against the brief. Are the required people, activities or product details present? If something could not be photographed, say so directly. A beautiful replacement image does not automatically fulfil the missing requirement.
Name files so people can distinguish them
Use a stable naming system that identifies the job or collection and the image. Add a clear suffix for an agreed variant, such as a wide banner crop or a smaller preview. Avoid relying on “final”, “new final” and “use this one” as the only differences.
The filename should remain stable after approval. If a file must be replaced, make the new version identifiable and explain what changed. That helps the recipient avoid mixing an old crop with a new caption or accidentally returning to an earlier edit.
Make the variants match the actual need
Supply the formats and dimensions agreed for the job. If a print supplier or publisher has a specification, work from that rather than guessing. A large source file and a small ready-to-use copy can both be useful when their roles are clear.
Do not assume that an image which opens on your computer is correct for every destination. Check pixel dimensions, the intended colour profile and whether the export has introduced visible artefacts. Keep your working master separately so that another variant can be made cleanly if needed.
Include a short delivery note
I would explain the folder structure, identify the approved selection and point out any important crop choices. Include the agreed credit wording and refer to the written usage agreement rather than leaving the recipient to infer it from file access.
For an imagined event delivery, the note could distinguish a concise press selection from a larger internal gallery, identify the requested group photograph and link the caption list. It should describe the actual files supplied, not copy a generic checklist that mentions folders which do not exist.
Test the handover as a recipient
Open the download through the route the recipient will use. Check that access works, the files arrive intact and the folder names remain clear. If a link expires, tell them when and agree how they will retain the delivery.
Open representative files from each variant and match them with the caption list. Check at least one less obvious filename as well as the first image. A quick glance at the folder's cover thumbnail does not establish that the whole export is usable.
Keep the record clear afterwards
Record what was delivered and when, along with any agreed changes. Retain the relevant working files according to your agreement and your own documented process. Do not promise indefinite availability unless you intend to provide it.
A useful final question is whether someone unfamiliar with the shoot could publish the intended images without guessing. If the answer is no, fix the missing explanation before sending. The best handovers make the photography easy to use while preserving the choices that made it work, from the planned crop to the accompanying caption.