Keep a season of club moments together
Running club photo sharing for training days and race weekends
Training groups and race-day meetups create photos from different phones and different parts of the route. Give members one event page to contribute selected images, with a named organiser responsible for consent, access and the archive.

A running club's photographs do not all come from a single finish line. Members take pictures after an early training run, on a club trip, at a local race, during a volunteer shift or around a coffee stop. Some are on a captain's phone, some in a group chat and others never leave a runner's camera roll. A shared event collection gives members one route to contribute images from a particular gathering, so the organiser can look through them and save an archive. The useful unit is one named occasion—a race weekend, club anniversary or training day—not an open invitation to upload every image from an entire year without a plan for who can see it.
Choose the purpose and audience for each collection
A club may want to remember a group outing, share photographs with its members or prepare a small selection for a newsletter. Those purposes call for different audiences. Decide who should receive the collection link and who will choose any images for wider sharing. A member who contributes to a private club archive has not automatically agreed to appear on a public page. Tell people what the event collection is for, who will see the files and how to ask the organiser to remove an image. If the club has a photo or safeguarding policy, follow that policy before sharing a link.
Use a separate event for a distinct gathering instead of turning a one-off event collection into an informal permanent directory. Candid stores one collection per event. The host can name the occasion and share its guest page with the club. That keeps the event's scope understandable: a member can see whether the link is for a particular race, club social or training day rather than guessing which files belong there. If the club wants a recurring archive across many activities, name a member who will download and organise each event's files in the club's chosen storage.
Give one organiser responsibility for the archive
A photo link needs an owner. Choose a club captain, event volunteer or committee member who can create the event, share the code or link and download the files afterwards. Agree where the archive will be stored and who may receive copies. A club account that changes hands each season should have a clear handover: the outgoing organiser should not be the only person who knows where the files are. This small decision prevents photographs from remaining attached to a personal account that a future committee cannot access.
Candid guests open the event page in a browser from a QR code or link, provide a name and choose the files they want to send. They do not need an app, account or password. The page remembers who is typing for twelve hours. A club can share the link in an event message and display the QR code at a stationary meeting point. Ask members to upload only from a safe location. A runner should not be expected to scan a code or select files while moving through a group run or crossing a race course.
Make the photo request easy for members
Tell members what kinds of pictures will be useful. A prompt might invite them to share a group portrait, the route scenery, the volunteer team or an informal moment after a race. Avoid requesting photographs of every runner at every point along a course; that can distract people from safe movement and create a pile that is hard to review. The club should make contribution optional and should not imply that a member has to be in a photograph to belong. A short, specific invitation is easier to act on than a broad request to send everything.
A group message can get buried under route maps, meet-up changes and race reminders. Include the event link where members can find it again, and send one follow-up after the activity for anyone who wants to contribute from home. If a QR code is printed, add the short address as a backup. Test the final sign from a member's phone, not only from the organiser's logged-in device. Confirm that the event title is right and that a sample image appears in the host view. A tested process reduces last-minute questions and gives members confidence their files reached the right collection.
Respect safety and consent on the route
Photo sharing must not interfere with a run, a race or a volunteer's responsibilities. Keep signs away from course instructions and ask spectators to remain in designated areas. A volunteer who is responsible for crossings, first aid or route support should not be expected to make photographs while working. Do not invite members to cross a barrier or step into traffic for a better angle. If the activity has an organiser or race director, check where photography is permitted and keep the event collection separate from safety and results systems.
A running club can include people who prefer not to be photographed, children attending with family or members whose workplace or health information should remain private. Tell contributors to ask before sharing a close-up of another person, especially if the image will later be used publicly. If a parent or guardian has a preference about a child's photo, follow it. If someone asks for an image to be removed, make it straightforward to contact the named organiser. A private link or closed club audience does not remove the need to respect the people shown.
Plan for different phones and connections
Members may use different phone types, browser settings and mobile plans. Candid's guest page runs in a browser and accepts a name and file selection; guests do not install an app. The upload itself needs an internet connection, which can be unreliable at a crowded finish or remote route. Do not promise that every image will appear immediately. Tell members they can keep the link and upload later, and make sure the event's online period gives them enough time to get home and choose their pictures.
Video files can be large and may use more data than a still image. Decide whether the collection actually needs videos, and if so, ask for short clips that add a perspective rather than long recordings of an entire run. Candid accepts video uploads on plans that include them, with a stated count and storage allowance. Preview has no video uploads; Gather includes 30 videos, Celebrate 100 and Keepsake 300. Check the package against the club's likely contribution volume and the network available at the meeting place. A still-photo request may be the more considerate option for an event with weak coverage.
Estimate event limits and cost
The club should estimate the number of contributors and the kinds of files members might submit. Preview is free and includes 20 photos, up to ten contributing guests, 500 MB and seven days online. Gather costs $19 once per event and includes 200 photos, 30 videos, 5 GB, unlimited contributors and one month online. Celebrate costs $39 and includes 750 photos, 100 videos, 20 GB and three months online. Keepsake costs $69 and includes 2,000 photos, 300 videos, 50 GB and six months online. These are one-off US dollar prices and plan allowances; check the current pricing page before the club buys a package.
Unlimited contributors does not mean unlimited files or storage. If the club plans to invite a large membership, estimate how many people are likely to send images and how many files each may select. Extra capacity is available as one-off photo and video add-ons. The club should also decide whether standard downloads are enough or whether original-quality copies matter. Gather provides standard downloads; Celebrate and Keepsake provide original-quality downloads; Preview has no downloads. A committee that wants to print a selected photograph or crop an image should choose its plan with the expected use in mind.
Set gallery access and review expectations
Tell members whether they will be able to browse other contributions or only send their own. Candid lets the host switch off the guest-facing gallery to make the page upload-only. The host can also enable approval so files wait until accepted. If the club plans to show photographs on a screen at a social event, choose who will review the gallery and what should be displayed. Avoid putting a screen where it distracts runners or shows an image to people who were not meant to see it. Review should be a named task rather than an assumption that somebody will notice every new file.
A club may want to share a few approved images with the wider membership, while keeping the full archive within the event group. Explain that distinction before collecting files. Ask contributors if a selected picture will be used in a public newsletter or social channel, and follow club policy about identifiable people. Do not use a member's image as promotional material just because they uploaded it to a private event page. A clear audience helps members decide what they are comfortable contributing and reduces the chance of awkward requests after publication.
Download the club collection before it closes
Each Candid plan sets how long the collection remains online from the event date, and the host receives a warning before deletion. Preview lasts seven days, Gather one month, Celebrate three months and Keepsake six months. A club should not treat this as permanent storage. Pick the member who will download the collection, set a reminder and save a second copy in an agreed club location. After the collection is deleted, the host's download is the only copy. If committee roles change during the online period, pass on the reminder and access responsibly.
The host can download individual files or the full event archive as one streamed download. Afterward, open a sample of files and make sure the archive is complete. Separate original files from any resized images prepared for social posts. If several club officers need copies, share the archive through an approved club storage route rather than circulating one person's sign-in details. Naming a backup location and an archive owner keeps the work manageable and makes the collection useful to the club beyond the day the link was created.
A practical setup for a club event
Before sharing the link
Name the event
Create a separate collection for the race, training day or social rather than using an unclear year-round link.
Agree on the audience
Tell members who can open the link and whether selected photographs may be used outside the group.
Test as a contributor
Open the page on another phone, send a sample file and confirm the organiser can download it.
Post the invitation
Use a specific, optional prompt and include the link where members can find it after the activity.
Assign the backup
Choose who will download, check and store the archive before the event collection closes.
Make it a useful part of club life
A club photo collection works best when it supports the activity instead of interrupting it. One named event, a clear link and a modest request let members focus on running and on one another. The organiser gets more than one point of view without trying to build a photo archive from private chats months later. Members can contribute from the finish gathering or after they return home. The club should thank people who send images, ask before sharing them beyond the group and make it easy to raise a concern.
Candid Photos gives a club a browser guest page, a QR code and a single collection to manage for an event. Check the plan for contributors, photos, video, storage, download quality and online time. Name the archive owner and make a second backup before the collection closes. Candid does not provide race registration, timing, route management or results; keep those tasks in the club's established systems. For a group that wants a straightforward way to gather voluntary event pictures, a tested collection can be a useful addition to the day.
Running club photo sharing questions
Can a running club use Candid for a group run?
Yes. The organiser can create an event with a name for the run or club gathering and share the guest page with members.
Do club members need to install an app?
No. Guests open the event page in a browser from a link or QR code. They provide a name and choose files to upload.
Can the collection be used for race results or registration?
No. Candid is for collecting event photos and supported video. Keep registration, timing, safety and official results in the club's existing systems.
How should a club keep the photos?
The host should download the event archive before the plan's online period ends, check the files and save a second copy in an agreed club location.
Give members one place for event photos
Create a named collection, test the guest page and decide which club organiser will save the archive.
Photo collection by event type
Put one link on the tables and let everyone contribute.
Create a collection, print the table stands, and the photographs your guests took are waiting for you the morning after. Guests never install anything and never make an account.