A multi-event combines several races or disciplines in a single event — for example, a trail run offering distances of 15 km, 30 km and 50 km, or a triathlon with different categories. Here’s how to organise your albums and imports to manage this type of event effectively.

---

Create an album by proof or a single album? #

Both approaches are possible depending on your context:

One album for all events

• Easier to manage and distribute — just one link to share with participants
• Use tags to distinguish between events (e.g. "15km", "30km", "50km") — participants can filter by tag to find their photos.
• Recommended if bib numbers are unique throughout the event

One album per event

• Recommended if race numbers are repeated from one event to another — otherwise, two participants from different races could have the same number and see their photos mixed up.
• Allows independent management of rates, confidentiality and imports per proof
• Requires a different link to be provided for each test

---

Managing imports with tags #

If you opt for a single album, organise your imports by proof by assigning a tag to each batch:

1. Import the photos from the first event with the corresponding tag (e.g. '15km').
2. Import photos from the second event with their own tag (e.g. '30km').
3. Repeat for each test
4. Participants can filter the gallery by tag to access photos from their race.

See the article “Adding a tag during import” for detailed instructions.

---

The correction script #

If you are using a recognition algorithm, wait until all imports for all tests are complete before running the correction script. A script run too early will not take into account photos imported after its execution.

⚠️ Only run the script once, after the last event import — see the article “When to run the correction script”.

---

Managing the multi-event photocall #

If you are organising a photocall, ideally:

• Place it before the start of the first event to cover as many participants as possible.
• If the events have staggered starts, organise a separate photocall for each wave of starters.
• Import all photocall photos before action photos, and run the script last — see the article "Using photocalls".

---

Special case: identical bib numbers between events #

If two participants from different races have the same bib number, you must create a separate album for each event — a single album would generate incorrect identifications by associating the photos of both participants under the same bib number.

---

💡 For an event with multiple races, the most effective combination is: a single album + tags per race + unique bib numbers for the entire event. Coordinate with the organiser in advance to ensure that bib numbers do not repeat between races.