Close a Photo Delivery with a Manifest

Make the final set, purpose, and revision path unambiguous.

The decision

A delivery manifest answers what was sent and how to request a correction. It should distinguish a draft review set from an approved or published set.

A practical sequence

Count the actual exported files and compare them with the selected list. Check filenames, sequence, and expected format. Write the output purpose and delivery date. State any pending permission, caption, or quality issue honestly. Keep a source-to-export mapping privately so a revision request can return to the correct original. Avoid including unnecessary private folder paths in a recipient-facing note.

Worked example

A twelve-image community-garden set could include a note listing garden-01 through garden-12, web use, JPEG format, and two captions still awaiting confirmation. If only ten files reached the destination, the manifest reveals the mismatch. A note calling the set “approved” would be misleading unless the relevant person actually approved it.

What can go wrong

Do not use delivery as a reason to discard originals or editing records. Retention decisions depend on your project responsibilities and agreements. This guide does not prescribe legal retention periods or grant distribution rights. Verify permissions and recipient requirements independently.

Your completion record

Finish by opening one file from the delivery destination and recording where the revision source lives. Mark the session complete for that specific output. If another use is requested later, begin a new requirement check rather than silently reusing the old export.

Before continuing, check the record against the actual files rather than relying on memory. Keep uncertain decisions labeled as uncertain. The next useful step is the specific task named in your completion record, not a fresh pass through the entire archive.

Keep the recipient-facing note brief enough to use: file range, purpose, pending issues, and revision contact. The private project record can carry longer technical details. This separation makes the delivery clear without exposing the structure of your personal archive.

Sources checked