Sub-events and pricing

Adding sub-events

From your event's Edit page, scroll to the Sub-events card. Click Add a sub-event. For each one you'll set:

• Name: "Half Marathon", "5K Run/Walk", "Kids' Fun Run", etc.
• Distance: "13.1 mi", "5K", "1 mile".
• Start time: the wave start, if different from the event's main start time.
• Capacity: the registration cap. Once reached, the sub-event sells out.
• Price: what athletes pay. Either one flat price, or a price schedule: early-bird tiers that step up on dates you set (tier boundaries fire in your event's timezone). When the next step is a price increase, the distance's row on your event page shows it under the ages, like "$48.40 on Oct 1". In the last 7 days it switches to an amber countdown ("Goes up to $48.40 in 3 days"), and on a computer athletes can hover it to see the whole schedule. Steps that start after registration closes are never shown. Every distance needs a price or Free entry turned on. A blank price cannot be saved, and an event cannot publish while a distance has no price. If an older distance still has no price, athletes don't see it anywhere (your event page, registration, switching distances, series, emails) until you add one; you still see it in your dashboard. A distance whose first scheduled price hasn't started yet shows as "Not available yet" and can't be picked.
• Free entry: turn this on for a distance with no charge. Athletes still register on Run This and get a confirmation and check-in pass; nothing is charged and no payout account is needed for a race where every distance is free.
• Tier names: athletes see these on your event page, so name them the way you talk about them. Rows start out as "Early bird pricing", "Tier 2", "Tier 3" and so on, and every one can be renamed at any time. Renaming changes nothing about what anyone is charged: the price that applies is always whichever row's date has most recently passed.

Age-based pricing

Give a specific age group a different price, a youth or senior discount, for example, and Run This applies it automatically. No promo code required: once a registrant's date of birth is on the form, the right price shows before checkout.

From a sub-event's Price block, add an age pricing rule. For each one you set:

• Who it applies to: a minimum age, a maximum age, or both. Leave the minimum blank for "17 and under", leave the maximum blank for "65 and over".
• What they pay: a set price that replaces the standard price, a dollar amount off, or a percent off that keeps working even after your price schedule steps up to a later tier.
• An optional label ("Youth", "Senior") shown to athletes. Leave it blank and the bracket itself shows instead: "17 and under".
• An optional date window: the rule only applies while registration is open inside it.
• Skip included giveaways: when a sub-event bundles a free shirt or item into its price, turn this on for a discounted bracket so those registrants are not required to pick one, and are not promised one either. Priced merch stays available to buy. Before turning it on, consider that some families want the item anyway. You can build its cost into the bracket's price and leave this off, or offer a priced giveaway (for example "Extra race tee, $12") anyone can buy. With neither, a family who wants one will need to contact you, and you can attach it from Manage Registration.

Example: your 5K is $40. Add a rule for ages 0 through 17 with a set price of $15, and every registrant 17 or younger pays $15 instead of $40 the moment they enter a birthdate that qualifies.

You can add more than one rule to a sub-event. When a registrant matches more than one, say a "Youth" bracket and a separate holiday discount, they get whichever price is cheaper. A rule that stands alone still applies even if it happens to cost more than the standard price, since that is what you set it to do.

Coupon codes still work on top: the coupon discount applies after the age price. A set price of $0 (or 100% off) makes that group free, the same as any other free registration, no card required.

How ages are counted

One setting decides how old a registrant is, for both the age limits on your sub-events and any age pricing rules. Find it in the Sub-event global options popup. Choose:

• Race day (the default): age as of your event's start date.
• The day they register.
• End of the calendar year the race takes place in.
• A custom date you choose.

Changing this affects every sub-event on your event, both who qualifies for a distance and what price they are quoted, so it's worth setting once, early. If someone transfers between distances, they are charged using their own age price for the sub-event they move into, not the standard price. When you renew your event for next year, your age pricing rules carry forward with their date windows shifted to the new dates.

How sub-events show up to athletes

Athletes see your sub-events on your event page. The display depends on the page style:

• Ticket style: sub-events list as an accordion in the page body.
• Overlap style: sub-events open in a modal when the athlete clicks the "Events" card in the hero.

Private codes

Give a sub-event a Private code in the sub-event editor to make it invite-only, for example a championship race with a qualifying time or a club members' entry. Athletes still see the sub-event, and when they pick it they're asked for the code before they can fill in their details. Codes ignore capitalization and extra spaces at either end.

To gate the whole race instead, turn on Require code for registration under Edit event, Other options, and enter the code there. When both are set, an athlete needs both codes.

Sold-out and waiting list

You can manually mark a sub-event as sold out from the sub-event editor. The Waiting list toggle lives in the Global sub-event settings strip at the top of the Sub-events card, flip it on and sold-out sub-events show a "Join waiting list" CTA instead of Register. Athletes can join with one tap; their info populates from their account.

See the Waiting list page in your director dashboard to review who's on the list, mark people notified as you contact them, and export the roster as CSV.

Global (whole-event) capacity

Beyond each sub-event's own cap, you can limit the total number of registrants across the entire event. Open Global capacity from the button under the sub-event list, turn it on, and enter a max. Each person counts as one. A 4-person team is four registrants.

The two caps work together: a registration is blocked when EITHER the event cap or the chosen sub-event's cap is full, whichever fills first. The popup shows which sub-events have their own caps so you can see how they interact.

Flip on Show current capacity on the event page to show athletes how full you are, a "Capacity" thermometer that fills from green toward red as spots fill, with "38 spots left" and "212 of 250 registered" above it. Cancelled registrations release their spot, so the count only reflects runners expected on race day. Leave it off to keep it private.

One sub-event per person, or several

By default, each person can register for one sub-event at your event, most single-day races work this way. If you want to let someone sign up for several (say a 5K and a kids' dash), flip Let one person register for multiple sub-events in the Global sub-event settings strip. When it's on, a registrant can add more than one sub-event to a single checkout and pay once.

Sub-event transfers

Turn on Allow registrants to transfer between sub-events (in the Sub-event global options popup) to let athletes move their own registration, say from the 10K to the 5K, without contacting you. They pay any price difference, and if you set a transfer fee (your change fee, minimum $5, 100% yours), they pay that too, with processing fees on top, just like a registration. There's no refund if the new sub-event costs less. Set an optional cutoff to stop transfers before race week. Athletes do this themselves from My Registrations. The athlete-side walkthrough is at Switching distances.

Transferring into a team sub-event prompts them to create or join a team; leaving one drops them from their team. You can always move people yourself, for free, from Manage Registration on the Registrations page.