Insights

Delivery is not the end of the asset.

Delivery closes a project, not the record of what was decided. A backup can restore every file years later. It cannot restore which file the client approved, which version went to print, or what the license allowed. Those answers survive delivery only if they were recorded on the work, in the system where the work happened.

A mountain biker leans hard into a turn on a dry trail in Bhutan, throwing a large cloud of dust behind the rear wheel, with dry brush and a rising dirt track behind. Photographed by Martin Bissig in Paro, Bhutan.

Photo: Martin Bissig

Photo: Martin Bissig

After delivery, the question is structure, not storage

The standard advice after delivery is retention: keep the files for two years or five, on a second drive. That answers where the files are. A project's structure is the set of decisions around its images: the feedback, the selection, the approval, the delivered version and the terms of use. A good backup brings back each file byte for byte and none of those decisions, because they were never stored anywhere a backup could reach.

Delivery is where the decisions stop being maintained

While a project runs, everyone knows which version is current, because the work depends on it. Feedback refers to an image, a selection includes it or not, and the delivered file was chosen over the alternatives for reasons that were visible at the time. The project was producing decisions about images, not only images. At delivery the files move to a folder or an archive, and the decisions stay behind in the tools, threads and memory of a project that is now closed.

Delivered work comes back and needs its decisions

A client asks a year later which version they are licensed to use, or a later campaign wants to reuse an image and someone has to establish whether that use was ever agreed. Without the record, each return visit becomes reconstruction: old threads, compared files, whoever might remember. The safe answer is to ask again or leave the image unused, and both cost something the project had already paid for: a clear answer. Access breaks the same way, with links left open and files re-sent as new copies. Delivered is not the same as accessible.

The moodcase library detail view in dark mode showing that same Bhutan photograph, with the Metadata panel open on the right. The panel carries the full record kept on the asset after delivery: title, headline, description and alt text, keywords including theme tags, AI tags, camera and exposure data, the photographer, an Editorial / press use licence and the location Paro, Bhutan.

What moodcase does with this

In moodcase studio, review, selection and delivery happen in one place, so the record they produce stays there. Visual Feedback and Client Selections are recorded on the work, and delivery runs through galleries with Granular Link Permissions and Link Expiration. Closing the project does not close what it established.

The design decision: delivery is a stage of the work, not the end of its record.

Where this fits

When a client asks for last year's final file and the answer starts with searching old threads, the record ended at delivery. In moodcase the project still shows which images were selected, what was delivered and who has access.

Visual assets need more than a folder. See how moodcase handles the full workflow.

Try all features for 7 days. No credit card required.

Delivery

Scattered Assets

Photographers

Studios