Prepare a delivery

A delivery is what you hand back. It is the only flow in Kalepio that goes from the studio to the client: everywhere else, files travel the other way.

Files and links

A delivery can carry both, and often does.

• Files, up to twenty, a hundred megabytes each, uploaded directly.
• Links, up to five: a gallery, a staging address, a shared folder, a repository.

Links are not a fallback. A developer delivers a URL and a photographer a gallery: what you hand back is not necessarily a file, and a delivery that only carried files would serve half the trades.

A delivery can also be published with no file and no link at all, if what you want to say is simply "it is done".

Assemble, then publish

Two actions, and the separation is the point of the feature.

You put a delivery together over several visits: you name it, you upload four files, you paste a link, you notice one is missing. For all of that time, your client sees nothing.

You publish when it is ready, and everything appears at once on their tracking page. A notice is posted in the conversation and they are notified.

Without that separation they would watch your work arrive one file at a time, and write to ask whether that was all of it.

Several deliveries on one order

That is common and expected. A proof first, the print-ready files afterwards. The mock-ups, then the sources.

Each has its own condition for opening, which is exactly the point: the proposal goes out immediately, the final files wait until you have been paid. The next page covers that.

Storage

A delivery's files count against your studio's storage. When it is full an upload is refused, with a message telling you where to go and make room: the My files page lists everything you are using and lets you delete.

Links cost nothing. That is one more reason to hand over a large video as a link rather than as a file.