Appearance
Events
This page is for Club Admin and Events Manager. It describes how to run any event, from a weekly track session to a club-run race. You run events from the admin panel and the volunteer console. Events have four kinds, and each kind behaves differently. Choose the event kind first. The kind decides what a member does and what you can configure. The rest of this page follows from this choice.
Who can do this?
Club Admin or Events Manager can create and edit events. The same two roles answer a member-added race. Clearing the results list is a different job. See Results and club records reviewer playbook. To run check-in on the day, see Check-in. Members register, plan to attend, or add their own race from the member app.
How events work
Every event has an event kind. The kind is the most important choice for an event. It decides how members take part. It also decides which settings exist: registration, payment, capacity and waitlist. Choose the kind first. The form then shows only the settings that are allowed for that kind.
| Event kind | What members do | What you can configure | Examples |
|---|---|---|---|
| Attendance only | Turn up. Optionally add the event to their calendar. Check-in records attendance. | Recurrence, audience. No sign-up, payment, capacity or waitlist. | Weekly training runs, committee meetings |
| Registration required | Register in advance, for free. | Capacity, waitlist, registration open and close windows. | Capped hill sessions, socials with a headcount |
| Ticketed / paid | Register with payment. Bring guests if you allow it. Answer any questions you ask. | Everything that Registration required has, plus member and non-member prices, guest limits and custom questions. | Club races, ticketed talks, dinners |
| External event | Mark that they plan to attend. Then enter on the organiser's own site. | An external registration link and the organiser's name. No club registration, payment or capacity. | Other clubs' races, parkrun, county championships |

Choosing the event kind in the first step of the wizard
TIP
Not sure which kind to choose? Start with Attendance only. Members turn up. You ask nothing of them before the session. This kind is right for most training sessions. Choose another kind only when you need sign-ups or money, or a link to the race of another organiser.
Event kind vs event type
Two different things are often confused:
- Event kind (Attendance only / Registration required / Ticketed / External) is the behaviour. It decides how members take part and which registration and payment settings apply.
- Event type (Training, Race, Social, Competition, Meeting, or a type that your club has added) is the activity. It says what the event is. It drives race configuration, and how the event is tagged and coloured around the site. It does not decide how sign-up behaves.
A club race is a Race (type) that is Ticketed (kind). A parkrun is a Race (type) that is External (kind). Choose the type for what the event is. Choose the kind for how people take part.
Set up event configuration
Before your first event, make a few one-off decisions under Events → Event Configuration. They make day-to-day work quicker:
- Locations: search an address, put a pin on the map, or use the current location of your device. Precise coordinates matter for a start with no street address, such as a park entrance or a trail head. If two locations are the same place, combine them with Merge into….
- Courses: a named, measured route. Point several years of the same race at one course. Members can then compare their times on it from year to year. See Results and club records for how a personal best on a course shows on the Results page of a member.
- Categories: tag events (Road, Trail, Social, and whatever else your club runs). They then filter and colour correctly on the events pages.
- Groups: a series or league that a race counts towards, such as a club handicap or an inter-club road race league. Give every season of a returning league the same Series key. Members then get a season switcher on its page. Give a league a Short name, such as HRRL. Each race in the group then shows the short name on a chip, beside a trophy. Without a short name, the chip shows the full name. A group can have its own season dates, for example a cross-country league from October to March. Without dates, its season is the calendar year.
- Audiences: a tag for who an event is aimed at (Adults, Juniors, U12, Women's). The tag matches by age and gender. It is not a privacy setting. It puts the right sessions in front of the right member. It also helps check-in find the regulars for that slot. It does not hide an event from anyone.
Create an event
There are two ways to start. The way you choose depends on how much the event needs.

The events list in the admin panel
The volunteer console's New event form is the fast path. It is built for a phone. Find it at Events → New event in the volunteer console. Choose Attendance for a turn-up session. Choose Race to add the race of another organiser with an entry link and organiser name. The form saves in seconds. Anything that needs sign-up, payment or a capacity still goes through the wizard below.

Choosing Race on the console's New event form
The Advanced Event wizard is at Events → New event in the admin panel. Use it for anything that needs sign-up, payment, capacity, guests, custom questions or a recurring series. Event kind is step one. Your choice there decides which later steps you see:
- Event Kind: always shown.
- Event Details: name, type, description, date, time, duration and location. For an external event, also the registration link and the name of the organiser.
- Race Configuration: only for the Race type. It holds the competition format (distance), the categories, and the series or league that the race counts towards.
- Registration & Pricing: only for Registration required and Ticketed. It holds registration open and close, capacity and waitlist. Ticketed adds payment, member and non-member prices, and guests. This step is hidden for Attendance only and External, because neither holds club sign-ups.
- Registration Questions: Ticketed only. The question types are short text, long text, dropdown select and yes/no toggle. You can reorder the questions. Each question can be required and can have its own help text.
- Recurring Events: optional. It turns the event into a series.
- Advanced Settings: the confirmation and waitlist email toggles, the automatic move to In Progress, and the early-arrival window for check-in.
After you create an event, choose New from Template on the row of any event. It fills in the wizard from that event, including its kind. The result is a quick, independent copy.
The product clears settings when you change the kind
When you change the kind, the product clears each setting that the new kind does not allow. For example, a change to Attendance only clears the capacity, payment and waitlist settings. The product always tells you which settings it cleared and why.
Group several races in one fixture
A cross-country match or a track meeting can hold several separate races. Mark each race Part of a fixture on its own edit form. Give each race a Running order. Each race stays a real, independent event, with its own entries and its own results. The fixture page groups the races together. It adds up their combined attendance.

A fixture and the races that belong to it
Recurring series
A series is a parent event that owns a set of occurrences. The series generates the occurrences automatically: weekly, every two weeks, monthly, or in a pattern like "first Monday of the month". Every occurrence inherits the event kind of the series. Every occurrence is a real, independent event. You can edit or cancel one occurrence without changing the rest.
WARNING
Regenerate Series deletes every existing occurrence permanently. It then creates new occurrences from the current settings of the series. You lose past occurrences and their registrations. Use it for schedule changes. Do not use it for a one-off edit.
Change an event's kind
Before anyone registers, you can edit the kind freely from the edit form of the event. When someone has registered, or you have added someone, the kind locks. A change would alter the event for people who have already signed up. This would be unfair. The Change Event Kind action lets an admin make the change on purpose anyway. It clears whatever the new kind does not allow. It keeps existing registrations.

The Event Kind selector on the edit form of an event
Registration, capacity and bookings
The product enforces capacity, but only for Registration required and Ticketed events. These are the two kinds where the club controls sign-up.
- No overselling. Two people who book the last place at the same time cannot both get in.
- A booking is one unit. A member and any household members or guests on the same booking count together against capacity. We never split them.
- An unpaid Ticketed booking holds its place until its payment deadline. At the deadline, the hold ends and the place goes back to the waitlist. We set the deadline when someone makes the booking. Every email about the booking states the deadline. The deadline does not change. We send a reminder before the deadline passes. We never release a place without a warning to the member first.
- A full event with a waitlist enabled takes further bookings onto the waitlist instead of turning them away. The waitlist takes whole bookings. It promotes them first-in, first-out when a place frees up. A promoted booking on a paid event gets an invoice with its own deadline. It also gets a link that pays the invoice without signing in. To email promoted members automatically, turn on Send Promotion from Waitlist Email. To tell them yourself, leave it off.
- Each booking gets a reminder a day before the event. We email it to the member who holds the booking, once. It gives the date, time and place, who is booked and their answers. The event's calendar file is attached. An unpaid place is told the payment deadline, with a link to pay. Members on the waiting list do not get it. To stop the reminder for the whole club, turn off Send a Booking Reminder in Settings → Events.
- A place that frees up close to the event is confirmed, not held. Suppose there is not enough time to give the member the minimum window to pay before the event starts. The place is then theirs, and we collect the fee afterwards. If we release a place on the morning of an event, we rarely find anyone else in time. The release also takes the place from a member who would have attended and paid.
Guests and custom questions are Ticketed-only, alongside payment. Guests count against capacity with the member who brings them. Each guest is a named place of its own. You can check in or refund one guest without changing the rest of the booking.
A ticket gives its holder a QR code for check-in. It is the one ticket a member ever reads about.
Change a booking
Each booking has a short reference, for example 7KQ4XM. Members quote it when they contact you. In the console, the reference shows under each person on the event's attendance list, with their choices.
A member changes their own booking with Change booking on the event page, until entries close. Their household manager can do the same. They can change each person's choices, add people and remove people. People they add pay on a new invoice, and a paid invoice is never changed. When a member takes someone off a paid booking, your club's refund policy is applied to that person's own fee. The booking holder gets an email that lists what changed. The event's managers get a notice in the console. If the event has no managers, everyone who can manage events gets it.
When the event is full, people added go onto the waiting list on the same booking. The people already booked keep their places. If the event is full and has no waiting list, nobody can be added.
An organiser can change any booking from the console, after entries close too, until the event starts:
- Open the event in the console.
- Choose the booking reference under a person's name.
- Choose Edit choices, Add a member, Add a guest or the button that takes a person off.
You choose whether a person you add is charged. A charge goes on a new invoice to the person who made the booking. When you remove someone, nothing is refunded. To refund them, open the booking's payment in the admin panel and choose Issue Refund. Enter only that person's fee. Volunteers who run the door see each booking's reference and choices, and cannot change them.
The admin panel shows each registration's choices, and does not change them.
External events
You set the entry fee, entries window and field limit of the organiser on the edit form of the event, after you create it. These are the details of the organiser, not of the club. Entry fee is what an entrant pays. Enter it in pence (2350 for £23.50). Add an England Athletics discount fee only where the organiser publishes a second, cheaper price. The club takes no money and holds no places for an external event. Members mark that they plan to attend. They then enter on the organiser's own site.
When a member adds their own race
A member can add an external race from the member app. The race appears in the Events tab of the console as Awaiting listing. The club answers it. Choose List to put the race on the club calendar and announce it. Choose Decline to leave the race as it was. It stays a genuine plan for the members who already opted into it. The product records a reason against the decision. The member who added the race gets an email with that reason.

The Events tab of the console, with a member-added race that awaits the club's answer
On the day
Check-in records attendance. See Check-in for how to run the door. On the event page in the console, the Manage Check-ins button opens the desk. On the same page, choose Add attendee to add a walk-up who did not register. The product adds the attendee at once and does not change capacity. Check-in works the same way.

An event's page in the console, on the day
If you work from the admin panel instead, the Participations tab of an event holds the same tools. It also holds the tools that correct a mistake after the event. These are Check In, Undo Check-In, Attendance, Results, Add Registration and Refund & Cancel. Use Attendance to set someone to Attended, Absent or Partial by hand.
On a paid event, Add Registration asks what to do about the fee. It offers to raise an invoice at the price of the event. It raises the invoice unless you choose No charge. The product bills a member through whoever pays for their household. A guest has no member record, so you name the member whose invoice carries the fee of the guest. A place that you add is confirmed, not held. If the invoice is not paid, we send reminders. We never release the place for non-payment. A place that goes on the waitlist is not charged. Its invoice comes when the place comes.
Add Registration does not add someone who already holds a place. A place that was cancelled or declined does not count. You can add that person back, if the event still has room. Members follow the same rule when they sign up themselves.
After the event
Record the results of a Race event from its Participations tab. Clearing imported results that the product could not match with confidence is a different job: the results list. That job includes accepting a suggestion, saying who ran, and adding a result by hand. See Results and club records reviewer playbook. Team placings for a league or match go on the Team Results of the event. What you record flows through to the Results page of a member. Where a result beats a club record, it also flows to the club records list. See Results and club records.
To cancel an event, set its status to Cancelled. Members see the event marked as cancelled. The product emails nothing automatically. If members need to know, send a message yourself. Refund and release each registered place individually with Refund & Cancel on the Participations tab. See Payments → Refunds for how this works.
Calendar feeds
An event can reach a calendar app in three ways. The first is the public feed of the whole club. The second is Save to calendar on the page of one event. The third is the personal feed of a member, with the events that the member will attend. A member gets the personal feed as a link from their account. If the member shares the link by mistake, the member can make a new link. Every feed updates itself once subscribed. Nobody needs to download it again.
Save to calendar sits beside Share on the event page, on your club's site and in the member app. It offers Google Calendar, Apple Calendar, Outlook, or an .ics file for any other calendar app. A phone shows its own calendar first. Save to calendar puts a copy in the reader's calendar. It does not tell the club that they are coming. A copy does not change when you change the event, so a member who books often does better with the personal feed. The menu in the member app ends with Keep your calendar up to date, which opens the personal feed. When the member's feed already lists the event, the control says In your calendar instead.
Each calendar entry links back to the event. It gives the venue's name and full address, and the answers each person gave to your booking questions. An event that members book, with or without a fee, has a reminder one day before it starts. An event with no start time is an all-day entry. A cancelled event offers no Save to calendar, and the feeds mark it as cancelled.
What members see
What a member can do on an event depends on its kind. Each event has one main button:
| Event kind | The member's main button | Then |
|---|---|---|
| Attendance only | I'll be there, or I'm racing on a race. Members can also turn up without pressing it. | I can't make it or I'm not racing takes it back. |
| Registration required | Get a place, or Join the waiting list when the event is full | The event shows the member as registered. |
| Ticketed / paid | Get tickets, or Join the waiting list when the event is full. Members pay, add any guests and answer your questions. | Your tickets opens what they booked. |
| External event | I'm racing, or I'll be there when the event is not a race | Enter with {organiser} opens the organiser's entry page. |
In the events list, a card has a button only where it helps. A Registration-required or Ticketed event shows its main button. An External event or a race shows I'm racing as a lighter outline button. A training session or social shows no button, and the card says Turn up.
On a race, the card and the event page also show the faces of the members who are racing, with a count such as "15 racing, including you". After a member presses I'm racing, the button changes to a line that says "You're racing". The line ends with I'm not racing, which takes the reply back. A household sees who is racing, for example "You and Sam are racing", and changes it with Change who's racing. The first member to reply sees "You're the first from the club". After the race, the card shows how many raced.
On a booked Ticketed event, Change booking lets the member change choices, add people and remove people until entries close. After that, the event page tells them to contact the organiser.
A member can also add their own race. It goes onto their own calendar straight away. It goes onto the club's calendar once you list it.
If your club has the weather beta switched on, an event within about a week also shows the expected conditions. It shows them for the time the session runs, and what members might want to bring. It is a forecast shown beside the event. Whether a session goes ahead is still your club's decision. You still tell members yourselves.
Members read about entering, changing a booking, tickets, refunds and the weather on an event in the help library, not on this page.
Settings
| Setting | What it controls | Where |
|---|---|---|
| Trial events limit | How many events a prospect can attend before the product prompts them to join | Settings → Registration |
| Minimum runner age | The youngest age at which a member can be registered to run | Settings → Registration |
| Minimum self-registration age | The youngest age at which a member can register themselves, unassisted | Settings → Registration |
| Confirmation and waitlist emails, auto-transition, early-arrival window | Per event, on the Advanced Settings step of the wizard | The event itself |
| Weather on events | Whether an event shows the forecast conditions for the hours between its start and end time. Beta. Off until we switch it on with you | See Weather on events |
| The event's location | The place that a forecast is for, and what members navigate to. An event with no pinned location shows no conditions | Events → Event Configuration → Locations |
| Cancellation & refund policy | The full-refund and partial-refund cutoffs, the partial percentage, and a flat cancellation fee. We refund automatically when a member cancels their own paid entry. The default is no refund at all. See Payments → Refunds | Settings → Events |
| Booking reminder | Whether each member with a booking gets an email a day before the event. On by default | Settings → Events |
| Unpaid places | How long someone has to pay for a place, how far ahead of the event that window closes, and the minimum window that nobody gets less than. The defaults are seven days, a cutoff a day before the event, and a minimum of 48 hours | Settings → Events |
Troubleshooting
I cannot add capacity or payment to an event
Those settings exist only for Registration required and Ticketed events. Change the event kind first. Change an event's kind explains when you can still do that.
A field I set has disappeared
You probably changed the kind of the event. The product clears whatever the new kind does not allow. A note on the change tells you what it cleared and why.
A member says they cannot see an event
Check the audience of the event. It may be tagged for a group that the member does not match on age or gender. Also check that the event is Open for Registration and not still a Draft.
I cannot change an event's kind
When someone has registered, the kind locks. If you must change it anyway, use Change Event Kind from the header of the event. It clears whatever the new kind does not allow. It keeps existing registrations.