Original publication · 2026-09-20

Fast Photo Delivery and Easy Photo Search Are Different Problems

After an event, two reasonable expectations often get folded into one: can the photos be ready sooner? And once they are ready, can I find the one I need sooner?

Both sound like questions about speed. They are different problems.

In Field Notes, I use Time to Photo for the first and Time to Find for the second. These are working terms for examining an event-photo workflow—not established industry KPIs or validated standard measures.

Time to Photo: when is an image ready for the next stage of work?

Time to Photo begins when an image is captured and ends when it is ready for delivery as a usable asset.

The steps between may include selection, editing, export, upload and quality checks. Different events require different levels of completion. A press release may need a small selection of key images first; a complete event record may need the full collection processed.

“Getting the photos ready quickly” is therefore primarily a production-time question.

That is the value of on-site quick edits: they can shorten the gap between capture and a usable image for a particular set of photos.

However quickly that part moves, it does not automatically answer the next question.

Time to Find: the photos exist, but who can find them?

Suppose the photos have already been finished and uploaded.

A liaison familiar with the programme may know that the awards are in the second segment and the large group photo is at the end. A speaker just wants images of their appearance on stage. A participant may not even know when they were photographed.

The bottleneck is no longer editing:

Once the photos exist, what must the person who needs one do to find and obtain it?

That is the question behind Time to Find.

It can be affected by entry points, categories, recognisable thumbnails, search, permissions, notifications and the download process. A gallery or search feature may improve some of these steps. It cannot make an unfinished image ready sooner.

One can be fast while the other is slow

Separating the two makes vague complaints easier to diagnose.

Photos are ready quickly but difficult to find

The photographer may have delivered promptly, yet the recipient faces a complete catalogue they do not understand. The problem is locating and recognising the image, not editing speed.

The route is clear, but the photos are not ready

An interface may be well organised, with entry points for different people or programme segments. If selection and editing are not complete, however, a good search experience cannot produce usable photos out of nothing.

A small urgent selection may not need a search interface

If the immediate need is five press images for one designated recipient, sending that person the selected files may be quicker than setting up a full gallery.

The tool should address the actual bottleneck, not make every event follow the same process.

Find the step that is holding things up

To improve the speed of an event-photo workflow, I would first separate its stages:

Capture → Selection and editing → Upload → Notification → Find → Download and use

Then ask: where are people actually waiting?

If editing is the bottleneck, better search will not fix it.

If the photos are ready but people keep asking the liaison to find them, shaving a few minutes off editing will not remove the underlying difficulty.

If permissions or downloading are the problem, renaming folders is not the answer either.

The point of this distinction is not to introduce two more terms. It is to stop treating every “I still haven’t got my photos” as evidence of slow delivery by the photographer.

One event can have several different time requirements

Press distribution, internal review, participant access and long-term preservation do not necessarily follow the same timetable.

The liaison may need a set of press-ready images before the event ends. Participants may care more about finding their own photos afterwards without asking someone for help.

The first requirement mainly concerns Time to Photo; the second mainly concerns Time to Find.

They can support one another, but they should not be bundled into one promise.

“600 Photos Delivered. The Next Problem Is Finding Them.” and “Folders Are Good for Delivery. Finding Photos Is a Different Job.” distinguished files existing from users being able to find them. Here, I have added a time perspective: the speed of preparing an image and the speed of reaching it both deserve attention.

Time to Photo asks when the photos are ready. Time to Find asks when the people who need them can actually obtain them. Identify which part is slow before deciding what to change.

This article offers general guidance on planning photography and using images. Practical arrangements vary with the event, venue, timetable and individual needs. It does not define a service scope, quotation, delivery specification or commitment. Actual services are governed by the proposal, quotation or contract agreed by both parties.