Lorixen.
EN

Running Events: Online Entries, Transfers and Race-Day Info

Short answer: A small running event needs two things online: an entry platform that handles payments, caps, transfers and deferrals without email back-and-forth, and an event website that answers every race-week question in one place. Plan them along the event's timeline, because what runners need in the week entries open is very different from what they need the night before the race. Most of your support emails can be designed away before the first entry arrives.

Race organisers usually find out what their systems can't do at the worst moment: the morning the event sells out, or the Thursday before race day when 200 people ask where to collect their numbers. Working through the timeline in advance avoids both.

Stage 1: before entries open (8–12 weeks out, or earlier)

Pick how entries will be taken

You can use an entry platform, build entries into your own site, or combine the two (a branded event site linking to a platform's entry page). For most small organisers the third option is the practical one: platforms already handle payments, confirmation emails and participant lists, while your own site carries the information and the brand.

Entry platforms differ in what organisers can switch on. RunSignup's race registration page, for example, lists participant caps by event or across events, participant-initiated transfers and deferrals, waitlist management, custom questions and early-bird pricing that rises by date or entry count (features as described on its site in November 2026). Let's Do This and SiEntries are other examples used by UK events. Compare them on the features below rather than on the homepage pitch.

Design the entry form

Keep it to what you actually use on the day:

  • Name, date of birth or age category, gender category if your results use one
  • Email and mobile number (for race-week messages)
  • Emergency contact name and number
  • Club name, plus a membership number only if it changes the price or your results
  • T-shirt size, if you offer one, with a clear "order by" date
  • Estimated finish time, if you'll seed start pens or waves
  • Anything else? Ask whether you'd notice if it were missing. If not, drop it.

Set your caps and waves

Decide the total cap, and whether separate distances (10K and 5K, say) have separate caps. If your start area or course can't take everyone at once, set waves at entry stage rather than reshuffling later. A runner who picked "wave 2, 9:15" plans their morning around it.

Stage 2: entries open and the sell-out

  • Show remaining places honestly. A "nearly full" message on your event page, updated from the platform, is more useful than a countdown that never moves.
  • Turn on a waitlist before you sell out, not after. When places free up through cancellations, the waitlist fills them without you running a lottery by email.
  • Pin a short FAQ on the event page: what's included, transfer and deferral rules, age limits, and whether you accept unattached runners.
  • Check confirmation emails by entering yourself. Do they include the date, start time, venue and a link to manage the entry?

Stage 3: the transfer and deferral window

This is where a good platform pays for itself. On Let's Do This, for example, whether a runner can transfer depends on the organiser's settings, and its help centre lists reasons the option may be unavailable: transfers not allowed, the deadline passed, the target race sold out, a payment plan still running, or certain ticket types such as charity, ballot or team entries. Self-serve deferral to a future edition works the same way: available only if the organiser enables it.

Decide your rules before entries open and publish them:

  • Transfers to another runner: allowed or not, deadline, any admin fee
  • Distance switches: allowed both ways, or only to a shorter distance
  • Deferrals: to next year, with a deadline, and whether there's a fee
  • Refunds: only if you offer them, stated plainly

Then set the platform to match. Every rule enforced by the system is one fewer email you answer by hand. Self-serve edits matter too: Let's Do This lets organisers allow participants to edit their own details, such as email address, and buy add-ons like posting the race number. If those options are greyed out for runners, the organiser hasn't enabled them.

Stage 4: race week

Create one page on your site called something obvious like "Race day info" and link to it from every race-week email. It should cover:

  • Number and timing chip collection: dates, times, place, and what to bring (confirmation email, ID if required). If you post numbers, give the posting cut-off date.
  • Getting there: parking, public transport, drop-off point, a map link to the actual entrance.
  • Timetable: bag drop opening, wave start times, course closing time.
  • Course: map, elevation, water stations, toilets, cut-off times.
  • Facilities: bag drop rules, changing, food at the finish.
  • Spectators: best viewing points, where to meet after.
  • Weather and late changes: "We'll post any changes here and text all runners by 7am."

Send one race-week email two to three days before, and one short text or email the evening before. Don't send five. Each extra message makes runners less likely to read the one that matters.

Stage 5: results and after

  • Link results from your site, even if a timing company hosts them. Runners search your event name plus "results".
  • Name the date results will be final, and how to query a time.
  • Add photos if you have a photographer, with a clear link.
  • Open next year's interest list on the same page while enthusiasm is high: a simple email signup is enough.
  • Archive the race-day page, then reuse its structure next year rather than starting again.

A quick comparison of approaches

Approach Works best when Watch out for
Entry platform only One-off events, no website budget Information scattered across platform pages and social posts
Own website + entry platform link Annual events building a brand Keeping both in sync when details change
Entries built into your own site Series organisers with unusual pricing or club rules You now own payments, emails and support

FAQ

Do I need my own website if the entry platform has an event page?

Not strictly, but platform pages are built around buying entries. A simple site gives you a permanent home for race-day info, results and next year's date, which runners will search for.

How do I stop people sharing race numbers instead of transferring?

Make the official transfer easy and cheap, with a clear deadline. If it's simple to do properly, fewer people bother with workarounds.

Should I collect medical information?

Only collect what you'll actually use on the day, and check the rules where you operate on storing health details. Many events ask for an emergency contact and leave medical information to the runner to carry.

When should I close entries?

Leave enough time to assign numbers, print them and post them if you offer posting. Your timing provider may also need a final list by a set date.

Organising an event and want the entry platform and race-day page to work together? Tell us about the race and how entries run today.

Sources

WhatsAppLet’s talk