How PodiumBase works for race directors
The organizer platform at a glance, which parts work together, and which capabilities depend on event activation.
On this page 7
Start with the outcome, not every feature
PodiumBase brings an event page, athlete roster, photography, race-day operations, sponsor inventory, results imports, and reporting into one event workspace. You do not need to adopt every part at once. Most organizers activate one event and choose the workflows they need.
The five organizer outcomes are:
- Bring athletes back: deliver searchable race photos and supported follow-up.
- Run the event: publish the event, maintain the roster, and connect external registration or use native checkout on an enabled event.
- Operate race day: run supported check-in, bib lookup, packet pickup, and live photo coverage.
- Grow event value: coordinate photographers, sell sponsor inventory, import results, and publish configured media products.
- Stay in control: manage the event, team, supported commerce, disputes, payouts, and reporting.
See the capabilities index for the public overview.
What is available on every event?
Availability depends on event setup, location, commerce mode, and rollout. Event pages, rosters, photo galleries, photographer coordination, and core organization controls form the base. Native registration, group checkout, promo codes, clone-from-last-year setup, and custom athlete-email templates are limited-release capabilities and do not appear on every account.
If a tutorial describes a control you cannot see, check its availability note. Do not create a duplicate event to make the control appear; ask about activation.
What PodiumBase does not replace
- Timing: PodiumBase imports supported results; it is not the system that records finish times.
- Website builder: PodiumBase provides event and organization pages and branding, not arbitrary custom-domain sites.
- Standalone store or fundraising: merchandise and donations are registration add-ons on enabled checkout events.
- General email platform: athlete email is built around supported event moments and templates.
- Volunteer management: team access and race-day check-in are not a volunteer scheduling product.
How it works alongside your own photographers
Bring photographers you already trust, publish an opportunity for photographers to apply, or ask whether PodiumBase can help recruit. Coverage is confirmed only after photographers are assigned; a published event does not guarantee a crew.
Use How to get your race photographed to choose a coverage path.
How registration fits
External mode keeps your current provider and uses the PodiumBase event page, roster, gallery, and eligible operational tools around it. Native checkout is a limited-release option for enabled events. Registration-specific refunds, transfers, deferrals, waitlists, add-ons, and financial reports depend on that mode and their individual rollout.
Read How to take race registrations on PodiumBase before configuring ticket types.
How sponsor inventory fits
Organizers can create packages tied to a race or organization, publish eligible inventory to the sponsor marketplace, review orders, place supported sponsor assets, and produce a source-labelled report. Package terms—not a generic promise of “reach”—define what the sponsor receives.
Start with Adding a sponsor to your event and Sponsor orders and partner reports.
Who handles participant questions
Athletes can use the help center for account, photo, registration, and privacy questions. Event-policy decisions—such as entry refunds or deferral approval—remain with the organizer. Photo mismatch and dispute workflows are recorded in the event console.
The full product overview is on the race directors page. For operational steps, browse the **Running your event** section of the help center.