A
Add-on A physical or digital item sold alongside an event entry — for example, a t-shirt, medal, finisher pack, or timing chip. You create and manage add-ons under Add-ons → Products in the dashboard. Each add-on has a fulfillment method that determines whether participants collect it on race day or have it shipped. Application ticket A ticket type where a participant submits a request for a place rather than buying one instantly. You review and approve (or decline) each application before a place is confirmed. Application tickets require additional configuration — contact your account manager to enable them. Audience A segment of your customers you can target with an email campaign. You define an audience using filters (for example, everyone who registered for a specific event or all participants who haven’t yet registered for your upcoming event). Audiences are managed under Marketing → Email marketing.B
Basket The in-checkout shopping cart. When a participant selects tickets and add-ons before completing payment, those items are in their basket. Under Reserved Capacities, items in the basket are temporarily held so no one else can buy them while the participant checks out. Bib number The unique race number assigned to a participant for race day. Also called a race number or start number. Assigned after booking and scoped to a specific occurrence and race. Booking The completed record created when a participant finishes registering for an event. A booking contains one or more tickets, any add-ons purchased, and the associated payment. Each booking has a unique Booking ID you can use to look it up or share with LDT support. The booking date is when the transaction was completed. You can view all bookings for an event from its Entries → Startlist. Booker The person who completed the booking — they hold the account and received the confirmation email. The booker may or may not be participating in the event themselves. A single booking can cover multiple participants (for example, a group registration), but there is always one booker. In reports and exports, booker details appear as separate fields: Booker First Name, Booker Last Name, Booker Email, and Booker Address. Booking fee An optional fee charged per booking, separate from the ticket price. When configured, it appears as its own line item in the order summary at checkout and in financial reports. Booking form A custom set of questions attached to a specific ticket and presented at checkout. Use booking forms to collect information beyond the standard fields (name, email, date of birth, gender) — for example, emergency contact, club affiliation, or t-shirt size. You manage forms on the Forms tab of event setup. Bulk Buy Discount An automatic discount offered when a participant buys multiple tickets in a single order. You configure tiers — each tier sets a minimum quantity and the discount that unlocks at that quantity. Configured under Marketing → Bulk buy discount. Bundle A package of tickets from multiple events sold together at a combined price. When a participant adds all the tickets in a bundle to their basket, the bundle discount applies automatically. You create and manage bundles under Marketing → Bundles.C
Capacity The total number of places available for a ticket. When all places have been sold or held, the ticket shows as sold out. You can set capacity when creating or editing a ticket, and manage available places across the event from Waves and capacity. Checkout The multi-step flow a participant moves through to complete a booking — selecting tickets, filling in their details, choosing add-ons, and paying. Participants reach checkout from your event page on the Let’s Do This marketplace. Checkout branding The colors, logo, and fonts applied to your checkout pages and post-booking confirmation screens. You can apply your organization-wide theme or create a custom look for a specific event. Configured under Settings → Branding or from the event setup screen. Conditional fields Form fields that appear or hide based on a participant’s answer to an earlier question in the same booking form. For example, a follow-up question only shown to participants who answered “Yes” to a prior question. Contact your account manager to set up conditional fields. Copy Creating a new, independent event using an existing event as a starting template. A copy has no historical link to the original — it starts fresh with no registrations or reviews. Use Copy when you want to reuse event setup for something unrelated to the original. Compare with Renew. Credit Account credit you issue to a participant, which they can put toward a future booking. Managed under Marketing → Credits.D
Custom question A question you add to a booking form to collect event-specific information from participants at checkout — for example, club affiliation, t-shirt size, or dietary requirements. Custom questions are also called form fields in the event setup screen. In reports and data exports they appear under the label of the question you gave them. See Booking form and Form field. Customer A person who has made at least one booking through your events. Customer records are scoped to your organization — the same person can be a customer of multiple organizers on Let’s Do This. View all customers under Customers → All customers in the dashboard. Data & Insights The reporting section of the dashboard, containing Analytics (charts and trends) and Reports (exportable data tables). Available at both organization level (all events) and per-event level. Deferral Moving a participant’s entry to a future occurrence of the same event — for example, rolling over from this year’s race to next year’s. The original entry is canceled and a new one is created for the future occurrence. Discount code A promo code that participants enter at checkout to receive a price reduction. You set the discount amount or percentage, which tickets it applies to, and any usage limits. Each code has a unique Discount ID used in reports. Managed under Marketing → Discount codes. Discount tier A quantity threshold within a Bulk Buy Discount configuration. For example, a tier might apply a 10% discount when a participant buys 5 or more tickets. You can set multiple tiers with different thresholds and discounts.E
Electronic signature A waiver requirement where participants must type their full name to sign. When enabled on a waiver field, the participant cannot complete checkout without entering their signature. Configured by Let’s Do This — contact your account manager to enable it. Emergency contact The name and phone number of a person to contact in an emergency, collected from participants at checkout via a booking form. In reports and exports these appear as separate fields: Emergency Contact (name) and Emergency Phone (number). Entry A place at an event secured by a completed booking. Used interchangeably with “registration” or “booking” in some parts of the dashboard. Each entry has a unique Entry ID. The Entries section of your event sidebar shows the Startlist, Reserved entries, and Applications. Entry code A type of discount code that unlocks a restricted or hidden ticket — for example, a members-only allocation or a ballot place — rather than reducing the price. Participants without the code cannot see or purchase the ticket. Managed under Marketing → Discount codes alongside other code types. Event The top-level listing on Let’s Do This — for example, “London Marathon”. An event is the parent that groups all races, tickets, and occurrences together. You create and manage events from the Events section of the dashboard.F
Fast checkout A toggle that shortens the checkout form for returning participants who have registered before. When enabled, returning participants skip fields already on file, speeding up re-registration. Configured per ticket in event setup. Form field A single question or input in a booking form. Supported field types include text, phone, dropdown, date, checkboxes, radio buttons, address, email, duration, and waiver. You manage form fields on the Form fields tab of event setup. Fulfillment How an add-on reaches the participant after purchase. The three options are Ship to buyer (mailed to a shipping address collected at checkout), Pick up on race day (collected in person at the event), and Unspecified (you manage delivery separately). Set per add-on product.G
Gender A standard participant field collected at checkout. Appears as a column in registration and startlist exports.I
Installment One of the monthly payments in a Payment Plan. The first installment is charged at checkout; subsequent installments are charged automatically on the same day each month until the plan is complete.L
Line item A single product in an order — a ticket, add-on, booking fee, or discount. Also referred to as an item in some parts of the dashboard and exports. Each line item has its own price and quantity. Line item detail Additional information about a line item — for example, a size or color selection for a merchandise add-on. Also referred to as a detail or variant in exports. Listed An event that is publicly visible on the Let’s Do This marketplace and discoverable via search. Compare with Unlisted.M
Marketplace The Let’s Do This public website where participants discover, browse, and register for events. Your event page on the marketplace is the main place participants find you before checkout. Membership A subscription scheme you can offer participants — for example, a club membership or loyalty plan with tiered benefits. Managed under Memberships in the dashboard sidebar. Minor A participant under 18 years old. When a waiver includes an under-18 restriction, participants registering a minor must indicate they are registering on behalf of a minor and sign as the minor’s guardian.O
Occurrence A specific dated instance of a repeating event. For example, an annual race has one occurrence per year. All bookings, capacity, and startlist entries are scoped to an occurrence, so each year’s edition is managed independently. See Repeat event. Organizer You are the person or company that owns and manages events on Let’s Do This. Your events, tickets, and bookings belong to your organizer account.P
Participant A person who registers for and attends your event. The term used across the dashboard and these docs for the people your event is for. Participant address The postal address collected from a participant at checkout, either as a standard field or via a shipping address prompt when the basket includes an add-on set to Ship to buyer fulfillment. Participant phone The phone number collected from a participant at checkout via a booking form field. Appears as a column in registration exports. Partner An external organization — such as a charity, corporate sponsor, or club — associated with reserved entry allocations. Managed under Partners in the dashboard. Payment Plan A feature that lets participants split the cost of a ticket into interest-free monthly installments rather than paying in full at checkout. You enable Payment Plans at the event level and set the maximum number of monthly payments and a last possible payment date. See Payment Plans for full details. Payout A transfer of funds from Let’s Do This to your connected bank account, representing your earned revenue minus platform fees and any deductions. Payouts are visible in the Financial reporting section.Q
QR code check-in A race-day feature that lets you scan a participant’s ticket QR code to confirm their attendance. Enabled per ticket in event setup. Requires the Let’s Do This race day app.R
Race A distinct distance, wave, or category within your event. Participants choose a race when they select a ticket — for example, “Half Marathon” or “Elite Wave”. The race title is the name shown to participants in the ticket selector and in reports. You set up races on the Races tab of event setup before creating tickets, as each ticket is linked to a specific race. Race day app The mobile and tablet application used at events for checking in participants by scanning their QR codes. Separate from the organizer dashboard. Renew Creating the next edition of an ongoing event — for example, this year’s version of an annual race — while carrying forward historical performance data, reviews, and marketplace presence. A renewed event is linked to the original in the marketplace. Compare with Copy. Repeat event An event with multiple instances at different dates and times, all sharing the same setup. Instead of rebuilding your event from scratch each time, you create a repeating event and manage each occurrence (date/time) independently. Configured using Repeat event from the event card menu. Reserved Capacities A feature that holds a ticket the moment a participant adds it to their basket, preventing anyone else from buying it while they check out. The hold lasts about 10 minutes; participants can extend it once by 5 minutes if they need more time. See Reserved Capacities for full details. Reserved entry A block of places held for a specific partner organization — such as a charity or corporate group — who commits to filling those spots. Participants in that group use a reservation code to claim their reserved places. Managed under Partners and visible in the Reserved entry reporting report. Role The permission level assigned to a team member on your account. Roles control what they can see and do in the dashboard. Available roles include Admin, Editor, Editor (No Financials), Viewer, and Viewer (No Financials), plus event-scoped variants that limit access to a single event.S
Sale dates The window during which a ticket is available for purchase — a sale start date and a sale end date. Outside these dates, the ticket is not shown to participants at checkout. Set per ticket in event setup. Startlist The list of all participants who have completed a booking for your event. Found under Entries → Startlist in the event sidebar. Startlist entry The individual record for one participant in one race. A booking that covers multiple participants produces one startlist entry per participant. Startlist entries are the records used for bib assignment and race day operations.T
Team A group of participants who register together under a shared team name. Teams have a Team ID and Team Name that appear as columns in registration reports, making it easy to identify and manage group entries. Ticket The purchasable entry a participant buys at checkout. Each ticket is linked to a specific race and has its own price, sale window, capacity, and settings. The ticket title is the name shown to participants at checkout; the Ticket ID is the unique identifier used in reports. The two ticket types are Standard (open purchase) and Application (organizer approval required). Theme The visual style — logo, colors, and fonts — applied to your checkout pages and confirmation emails. Your organization has a default theme; you can override it with a custom theme for specific events. Managed under Settings → Branding. Transactional email An automated email sent to a participant in response to an action — for example, a booking confirmation, a waitlist invitation, or a payment reminder. You can customize transactional emails per event under Transactional emails in the event sidebar. Transfer Moving a registration to a different participant, race, or event. There are three types:- Transfer to another race — the participant moves to a different race within the same event (for example, switching from the 10K to the Half Marathon).
- Transfer to another event — the participant moves their entry to a different event entirely.
- Transfer to a friend — the participant passes their entry to someone else to complete checkout in their own name.
U
Unlisted An event that is hidden from the Let’s Do This marketplace and search results. Use this during setup to keep the event invisible until you are ready to go live. Toggle an event listed or unlisted from the event setup screen or the event card menu.V
VAT invoice A monthly invoice from Let’s Do This covering platform fees and applicable taxes for that period. Accessible from Financial reporting.W
Waitlist A queue that lets participants register their interest when a ticket is sold out. When a place opens up (due to a cancellation or capacity increase), the next person in the queue receives an invitation to complete their booking. There are two modes:- Acceptance waitlist — participants receive a time-limited invitation (24 hours, 48 hours, 72 hours, or 1 week) to claim their place. If they don’t complete the booking before the deadline, the invitation passes to the next person in the queue.
- Instant waitlist — available for free tickets only. When a place opens, the participant is booked in automatically without needing to take any action.