At a race, a party or a tournament, the value of the photos falls with every day that passes. The next day, participants are still sharing the moment, commenting on times and tagging friends — that is when they look for photos. A week later, they have moved on to the next event. For an event photographer, delivering quickly is not a luxury: it is a core part of the business.

The good news is that delivering within 24 hours does not require working all night. It requires a process. This guide describes a workflow in Adobe Lightroom Classic designed for events with hundreds or thousands of photos, from the moment you switch on the camera to the last batch published. Command names are in English (the most-used interface), with the explanation in plain language.

Before the event: what saves hours later

Most of the time lost in editing is decided before the first shot.

  • Set the clock on all cameras. If you shoot with two bodies, or with a second photographer, sync the time to the second. With the right times, photos from several cameras sort chronologically without effort and you can find "the finish at 10:42" in an instant. On FomoShoot this has an extra effect: the capture time (EXIF) is used to group sequences — when the selfie search finds a photo of an athlete, it also shows the other photos from the same burst, even those where the face was still too small to be recognised.
  • Shoot RAW, or RAW + JPEG. RAW gives you room to correct exposure and white balance in batch. If the card and camera can handle it, a parallel JPEG is insurance.
  • Fix the white balance instead of using auto, especially indoors. Photos with the same colour base sync far better in editing.
  • Take a reference photo whenever you change light zone (start in the sun, finish in the shade, indoor hall). It will serve as the starting point for each preset.

Import: let Lightroom work while you rest

When you get home, import is the first step — and it can run while you have dinner.

  • Use Copy (not Add) to copy the files from the card to the disk, with a folder structure by date and event (for example, 2026/2026-10-03 Race X).
  • Activate Make a Second Copy To to an external drive. A failed drive on delivery day is the worst possible scenario.
  • In the File Renaming section, use a template with the date and event name plus the original sequence. It makes cross-referencing files from several cameras easier.
  • In Apply During Import, apply a base preset (camera profile, lens correction, moderate sharpening). It is work you no longer have to do photo by photo.
  • In Build Previews, choose Standard or 1:1 and activate Build Smart Previews if you will edit on a laptop. The import takes longer, but the culling that follows is much faster — and culling is what consumes the most time.

If you shot with two cameras and one had the wrong time, fix it before continuing: select the photos from that camera and use Metadata > Edit Capture Time to shift the time by the right amount.

Culling: be ruthless and quick

Culling is where the 24-hour deadline is won or lost. A few rules:

  • Work in the Library module, in loupe view (E key) and with Auto Advance active (Caps Lock), so that each decision moves on to the next photo.
  • Use only two decisions: P to pick and X to reject. Stars and colours can wait, if you really need them.
  • In bursts, compare photos side by side (C key) and keep the ones with a sharp face, open eyes and expression. At a sports event, you do not need every photo in the burst — but you also do not need to cut too much: two or three good variants of the same athlete give them a choice and can end up in a pack.
  • Reject without mercy: out-of-focus, closed eyes, someone blocking the lens, photos in which nobody is identifiable.
  • At the end, filter by Flagged and pass only the picks to editing. With Photo > Delete Rejected Photos you clean the catalogue.

For an event with many participants, think like the buyer: each person wants to find themselves. It is better to have an acceptable photo of every participant than ten perfect photos of the first five.

Batch editing: presets and syncing

At an event, you do not edit photos — you edit light zones.

  • Take the reference photo for each zone (start, course, finish, indoor) and edit it carefully: exposure, white balance, contrast, shadows, highlights.
  • Save each edit as a preset (Develop > New Preset), for example "Race X — finish shade".
  • Select all the photos from that zone and apply the preset in one go. Alternative: edit one photo, select the rest and use Sync (or Auto Sync, which applies each change to all selected photos in real time).
  • To copy only part of the settings, use Copy Settings and Paste Settings (Ctrl/Cmd + Shift + C and V) and choose only the panels you want.
  • Run through the photos in quick view and fix only those that stray far (someone backlit, a flash that failed). Straightening and cropping are the individual adjustments most worth the time.

Avoid heavily stylised "signature" edits on event photos. Participants want to recognise themselves, with natural colours. A clean, consistent style sells more than a strong filter.

Export: the right settings for publishing

Create an export preset for events and always use it:

  • JPEG format, sRGB colour space (it is what browsers and phones display correctly).
  • Quality between 80 and 90: visually indistinguishable from 100 and much lighter.
  • Size: on FomoShoot, full files are stored at up to 3000 pixels on the long side; a JPEG that already comes within that size (and under 12 MB) is uploaded exactly as you exported it, without further compression. So exporting at Long Edge 3000 px is the sweet spot: the upload is faster and you control the final quality.
  • Metadata: keep at least the capture information (EXIF), rather than Copyright Only. It is where the time of each photo comes from, used to sort the gallery and group the bursts.
  • Activate Output Sharpening for screen, at a low or medium amount.
  • In Post-Processing, you can choose to open the export folder at the end — handy for dragging straight to the upload.

Publish in batches (and notify at the right moment)

Do not wait for the last photo to start publishing. A strategy that works well:

  • Batch 1, the same night: the finish or the high point of the event, which is what most people look for.
  • Batch 2, the next morning: the rest of the course or the night.
  • Batch 3, within 24 hours: leftovers, groups, atmosphere.

On FomoShoot, you upload the photos to the event in the dashboard and the watermarked previews are generated automatically in your browser during the upload; the full files stay locked until someone buys. Participants can ask to be notified when the photos are ready, and you decide when to notify them with the "Photos ready — notify" button. Note: each album has one free notification. If you use it after the first batch, later notifications have a cost — so the best thing is to save it for when all batches are uploaded.

If you are new to the platform, count on one extra step: on a newly approved account, the first batch of photos is reviewed before you can upload in volume. Do this calmly, before a big event, and not on the night you have a thousand photos to publish.

A realistic timetable for 24 hours

For a Sunday-morning race, one possible plan:

  • Sunday, 1 pm-3 pm: import with backup copy and previews generating.
  • Sunday, 3 pm-6 pm: complete culling.
  • Sunday, 6 pm-8 pm: presets by zone, syncing and quick review.
  • Sunday, 8 pm-9 pm: export and upload of the finish batch.
  • Monday morning: remaining batches and notification to participants.

Times vary with volume and your computer, but the order is always the same: copy, cull, edit by zones, export, publish in batches.

To go further

A good workflow only pays off if the photos reach those who are looking for them. If you are still thinking about how to turn this work into income, read how to sell event photos online and how much an event photographer can earn. And if you do not have an account yet, the partnership with photographers page explains how to start publishing your events on FomoShoot.