For race directors
Registrations, reports & finance
The Registrations page is your participant reporting system: filter anyone down to exactly who you need, choose the columns you care about, export precisely that, and save the whole setup as a one-click view. Charts and Finance read the same data.
14 min read
Click Registrations under People in your event's sidebar. Every finalized registration is listed, and the toolbar gives you the full reporting kit:
- Search by name, email, bib number, phone, confirmation number, or registration ID.
- Sub-event chips are multi-select, view your 5K alone, or 5K + Kids Run together.
- Filters stack: registration date ranges, checked in or not, gender, age, city/state, bib assigned, amount paid, donated, coupon used, giveaway picked, circle membership, heat (in a heat, not in a heat, or one heat), emergency contact filled out, refunded, and any custom question answer ("Shirt size = Large"). Active filters appear as chips you can dismiss one by one.
- Columns lets you show, hide, and reorder every column, contact details, financials, waiver signers, even one column per custom question. Running heats? Turn on the Heat column. It sorts in your heat order and goes into the CSV like any other column.
- Age follows your race's age setting: race day unless you picked another option under How ages are counted. The Age filter uses the same rule, and a past year's roster counts ages on that year's race day.
- Click any row for the full registration: address, emergency contact, answers, giveaways, signed waivers, payment breakdown, items bought after registering, and the refund tools. In the Giveaways column and the CSV, an item bought later reads “(bought later)”.
- Repeat participant is a built-in column showing how many times each athlete has registered for this event across the years, a quick read on your returning runners. Open a registrant to see the exact editions ("3rd time · 2024, 2025, 2026").
The export IS the table
If a cell starts with =, +, - or @, the file puts an apostrophe in front of it. That way your spreadsheet shows what the person typed instead of treating it as a formula. Numbers stay numbers, negative amounts included. The Finance, volunteer, waiting list and Stopwatch downloads work the same way.
Someone signed up for the wrong distance, or wants to switch? Click their row, choose Manage registration, open Change sub-event, pick the new distance and press Move to. In the Run This app, open the runner on the Registrations page and tap Change sub-event. You only see the option when your race has more than one distance.
- No money moves. Before you press the button you see what they paid and what the new distance costs today. If they owe more, arrange it with them directly. If you owe them, use the refund tools on their registration.
- Their bib number goes back to the old distance's pool, so assign a new one from the new distance. A heat assignment clears too, since heats belong to a distance.
- The move frees a spot in the old distance for its waiting list, if you have one.
Runners can also move themselves, paying any difference at checkout, when you turn on Sub-event transfers.
Two buttons in the toolbar add people who never went through checkout, comped entries, race-day cash and check signups, elites, sponsors' entries, and anyone you took by hand.
- Add registration opens a form with the same required fields a real registrant faces: date of birth, gender, the address and emergency contact your event asks for, your required questions and waivers. Anything you don't have, hit Waive next to it; the registration records exactly what was skipped so your roster stays honest.
- Import CSV does the same thing in bulk, up to 2,000 rows at a time.
In the form, Payment has three choices. Comped is free. Offline is money they already gave you: type the amount, pick How they paid (Cash, Check, Venmo, Cash App or Zelle, or Other) and add a note if you like, such as a check number. That shows on the registration and in the Method column of the Payments list on Finance insights. Charge card takes their card through Run This, explained below. In the Run This app, open your race's Registrations, tap +, and the same three choices are on the Payment step.
Start from Download template. It has a column for every field this event collects (including your required questions, race/ethnicity and giveaways when you use them) plus two filled-in example rows showing the exact format each column wants. Sub-event has to match one of your distance names, and Payment is either comped or offline.
Leave the example rows in if you like
Two money columns, and the difference matters: Amount is the entry fee they paid you offline, and Donation is money they gave for the cause on top. A donation counts toward your public fundraiser total on either payment type, so a comped entry who still handed over $20 gets that $20 on the thermometer. Put it in the wrong column and it lands in the wrong place on your Finance page.
Tick These are comped / charity entries, allow incomplete to import rows even when required fields are blank; each skipped field is recorded as waived. Leave it off and incomplete rows are skipped with a reason so you can fix them.
What an added registration does and doesn't do
When someone can't get through checkout, or signs up at your table, choose Charge card in Add registration. The amount starts at what online checkout would charge them right now: your current price, their age price if you use age pricing, and any paid giveaway they picked. Tap a quick discount (10% off, 25% off, 50% off, $5 off, $10 off) or Other amount to type your own. Under the amount you see exactly what the runner pays: the same Processing fee as online checkout is added on top, so your race gets the entry and any donation, just like an online signup.
Then pick how they pay:
- Type in card opens a card form on your screen. Type their card in while they read it to you. Apple Pay and Google Pay are hidden here so your own phone can't be charged by mistake. They're registered the moment the card goes through.
- Send pay link makes a link the runner opens on their own phone to pay (no Run This account needed). If you entered their email, we email it to them; you can also copy it and text it. They join your roster as soon as they pay.
Unpaid links wait behind the small waiting for payment button in the Registrations toolbar, where you can copy a link again, email it again, or cancel it. Until they pay, a runner with a pay link isn't registered: they don't count toward capacity and don't show on your roster, check-in, or your timer's list. In the Run This app, the same list opens from the waiting for payment line at the top of Registrations.
Once the card goes through, the runner gets the same "You're registered" email online signups get, with their check-in code (when you entered their email). If their email matches a Run This account, the race also shows up in their account, calendar and app, just like a race they signed up for themselves.
Two safety checks: if the same email (or, with no email, the same name) is already registered for that distance, or already has a pay link waiting, you're asked before a second charge is made. And a pay link stops working after race day, so nobody can pay late at an old price; you can still type a card in yourself.
A card you charged works like any other online payment afterwards. It shows on Finance insights (the Payments list there says whether you typed it in or they paid by link), and you can refund it from the registration. A discounted amount is labeled on the registration, for example "50% off (normally $40.00)", so nobody wonders later why one runner paid less. Card charges need your payouts connected, since the money goes to your race's account.
The view menu (top-left of the toolbar) remembers whole report setups, filters, columns, sort, search, sub-events. Built-ins cover the everyday asks (All participants, Checked in, Not checked in, Timing, Donors, Refunded). Save your own ("Large shirts", "VIP list") and it's one click forever after, shared with your co-directors too.
Click Export CSV, then Timing file. You get the columns timing software imports, sorted by bib: Registration ID, First name and Last name in separate columns, Gender (M/F/X), Age, Date of birth, City, State, Sub-event, Bib, Chip, Team, and Heat. Gender (M/F/X) uses X for non-binary and stays blank for anyone who preferred not to say. Under Timing file, pick how birth dates look: 1990-05-31 or 05/31/1990.
The timing file works from any view. It covers the runners on screen, so a sub-event chip or a filter narrows it, and it always leaves out canceled registrations. To see those columns on the page first, or to add a column your timer asks for, pick Timing in the view menu, change it, and use What's on screen.
Because the file starts with Registration ID and has Bib and Chip columns, it also goes straight back into Bib assignments if your timer fills in bibs for you. Timers you add to your event see the same roster on their own dashboard, without the money, your private notes, or race / ethnicity (see Timer companies).
If your timer scores the race in RaceDay Scoring, RACE RESULT or Webscorer, the Export CSV menu has a timing file made for that program, so it imports without fixing anything by hand. Ask your timer which program they use. Each file holds the same runners as the Timing file.
- RaceDay Scoring: RaceDay Scoring's own column names, and birthdays as 05/31/1990. The Run This registration ID goes in its External Reference ID column, so importing a newer file later updates runners instead of adding them twice. It sends the birthday and no age, so the two can't disagree.
- RACE RESULT: RACE RESULT's field names, ages under your race's age setting (RACE RESULT takes an age or a birth date, not both), and m, f, or a (non-binary) for gender. RACE RESULT tells runners apart by bib, so runners without a bib yet are left out, and the menu says how many. Your distance names go in the Contest column: name RACE RESULT's contests the same, or match them when you import.
- Webscorer: Webscorer's exact column names, and F or M for gender (Webscorer has no non-binary option, so that cell stays blank). Webscorer takes a file where every runner has a bib or nobody does, so when only some runners have one, the file leaves all the bibs off and the menu says why. Assign the rest and download again to include bibs.
Late registrations, bib changes and distance switches keep coming until the start. Under Timing files, switch Runners to Changed since and pick a time. Every timing file then holds only the runners added or changed after that time, with a Last changed column. The time starts at your last download of the same list (same distances, filters and search) on that computer, a minute early so nothing slips through. Without one, pick the time of your last import. Checking someone in counts as a change.
Canceled runners are never in a timing file, so the menu tells you how many were canceled since that time. Remove them in your timing program, or check the Cancelled list on this page.
Lists are hand-picked groups of people, Elite Athletes, Media, Previous Winners. Select rows with the checkboxes, hit Add to list, and manage everything under Lists (rename, remove people, export, delete). Someone can be on many lists. Lists pair naturally with the email builder when you're deciding who to write to.
Selecting rows opens the action bar: add to a list, check in (or undo), or export just the selection. The header checkbox selects everyone matching the current filters, not just the visible page.
After you Renew an event, the just-finished edition is filed away as a renew record. A year selector appears on Registrations, Charts, Finance, and Circles, pick a past edition to browse that year's participants, money, and answers exactly as they were. Past editions are read-only: browse, filter, and export freely, but check-in, bibs, and edits are locked, and refunds on past editions are handled by Run This (contact us and we'll take care of it). Changing your event's date never moves anyone between years, only Renew closes out an edition.
The Charts and insights page turns your roster into pictures: a registration count tile, gender and age breakdowns, race/ethnicity when your event collects it, and a registrations-per-day line drawn over your event-page views. Ages follow your race's age setting, the same as the roster's Age column. The same year selector lets you study past editions, and a past year counts ages the way that year did.
If you aren't collecting race / ethnicity, that chart gives way to a message with a Turn on race / ethnicity button that takes you to the setting. In the Run This app, the same button opens the setting right on the page. A past year that has answers keeps its chart.
Next to those sits a Registration questions chart. Pick one question from its dropdown to see how people answered: a pie for single-choice and yes/no questions, including the built-in "How did you hear about this event?", and ranked bars when people could pick more than one answer or when there are many answers. It follows the year and sub-event you have selected and tells you how many registrants answered. Questions with typed-in answers aren't charted; read those on the Registrations page.
Every day on these charts, and on Finance insights, is a day in your event's own time zone, so a signup at 8pm the night before counts on the night before, not the next morning. The newest point is today, still in progress, so it is marked so far and shows no up or down comparison until the day finishes.
The Checkout card counts the people who reached your checkout, how many finished registering, and how many didn't, with what their carts added up to. It also counts the checkout reminder emails Run This sent and how many people came back and finished after one. A chart shows finished and unfinished checkouts by the day each person reached checkout. Pick 7, 30 or 90 days, or the whole year. You see counts only, never who left. Your own visits to your checkout aren't counted. Reminder timing and wording are on your race's Emails page.
In the Run This app, open your race, then Charts & insights: the Checkout numbers for the year sit above Traffic sources.
The Finance insights page answers "how much did we make?", net to your event, donations, fees paid by registrants, revenue by sub-event, coupon impact, and refunds. The year selector shows any past edition's books, read-only.
At the bottom, the Payments list shows every payment for the year: registrations, donations, sponsor payments, volunteer items, and Items runners bought after registering. The buttons above it show one type at a time, such as Donations only. More filters narrows the list by status, amount, or date, or to checkouts with 2 or more registrations or checkouts that included a donation. For example, pick Donations only and set the lowest amount to 250 to see every donation of $250 or more.
Download CSV saves exactly what the Payments list is showing, every page of it, as a spreadsheet file. With no filters on, that is every payment for the year.
For a list of your donors, use Download donor list in the Donations card. It has one row per gift, whether the gift came through your donate page or was added during registration, with names, emails, amounts, notes, and any refunds. The same button is on the Fundraiser page. Donors who chose Anonymous appear with their real name and a mark, on the Payments list and in both downloads: Anonymous hides a name from the public, not from you, so you can still thank them. When you show your supporters, open a donation in the Payments list to hide it from your public supporters list.
Net to your event is what you actually keep. Registrants pay the Run This and processing fees on top of your prices, so a $40 entry banks $40. The one exception is a gift made through your donate link where the donor chooses not to cover the fees: those come out of the gift, so a $100 donation banks about $96. The Donations tile still shows the full $100, because that is what the donor gave and what your fundraising thermometer counts.
A Card disputes tile appears only when a registrant disputed a charge with their bank and the cost was charged to your event. It shows what the dispute cost, and that amount comes off Net to your event. Stripe keeps its dispute fee even when the bank decides in your favor. If the dispute is lost, the payment also goes back to the cardholder.
When the bank decides a dispute on a registration you took through Run This, its cost is charged to your event, as your Organizer Agreement says. It comes out of your event's Stripe balance, and anything the balance can't cover goes on your fee tab, which is paid down out of the fees on your next registrations. The payments manager and the lead director get an email when it happens.
What you see is the registration snapshot

