How to collect photos from everyone after an event or trip

The way to collect photos from everyone after an event is to give people one destination, one link, and one deadline: a single shared collection, a link that takes two taps to act on, and an ask within 48 hours while the event is still fresh. Miss any of the three and you’ll get a fraction of the photos.

Why the photos never show up on their own

After a tournament weekend or a week-long trip, the photos exist. Hundreds of them. They’re just distributed across every phone that was there, and each person quietly assumes their photos aren’t the good ones, or that someone else is handling it. Nobody is handling it. A month later the event is three camera-roll screens deep and effectively gone.

Collecting photos is not a technology problem so much as a logistics problem, and the logistics are simple once you name them.

The system

1. Create the destination before you ask

Make one collection for the event, named the way people think of it: “Spring Tournament 2026,” “Week 3: Lake Day,” “Grandma’s 80th.” One event, one collection. If you send an ask without a destination, everyone defaults to texting you photos, which puts you back where you started.

2. Send one link, not instructions

The ask should be a single link that opens the destination, plus one sentence: “Drop your photos from this weekend here.” Every additional step, creating accounts, finding the right folder, reading a how-to, costs you contributors. In Fika, members are already in the space, so the link just opens the collection and they add from their phone in a couple of taps. New people can join through a shareable invite link first.

3. Ask within 48 hours

Enthusiasm for an event has a half-life of about two days. Send the link the evening of the event or the morning after, while people are still showing each other their photos. An ask a week later reads like homework.

4. Remind exactly once

One reminder, two or three days later, ideally with social proof: “34 photos in so far, add yours before Friday.” A gentle deadline works because it gives permission to do it now rather than someday. More than one reminder and you’re nagging.

5. Close it out

Some groups want to prevent modification to collections so they aren’t confused with something else in the future. In Fika, an admin can lock the collection, which freezes it while keeping everything viewable, a nice signal that this event’s story is told. If someone needs a keepsake copy, a whole collection can be downloaded as a ZIP archive.

Make it a rhythm, not a project

For groups that meet all the time, teams, troops, camps, youth groups, the real win is when collecting stops being a special effort. A collection per game or session, the same one-line ask each time, and within a few events people start adding photos without being asked, because there’s an obvious place where they go.

That’s the habit Fika is built around: a private space the group owns, a collection for every event, and every member able to add from their phone. See how groups like yours run it in the use cases, or start with how to share photos with a group privately.