Skip to main content
This is the shortest complete path to taking entries for a race. Nine steps. Each one links to the page with the full detail, so use this as the spine and branch off when you need to.
Budget an hour for your first event. Most of it is Stripe onboarding and writing your waiver — the Time2Bike part is quick.

​
Before you start

Have these ready:
  • A logo (square, under 5 MB).
  • Your waiver text, or the PDF your insurer requires.
  • Your bank details and business info for Stripe.
  • The race schedule — categories, start times, and what you’re charging.

​
1. Create your organization

time2.bike/organizations/create. Name, slug, contact details, brand color, logo. The slug becomes your public URL, so pick something you’ll still want in three years. → Create an organization

​
2. Connect Stripe

Settings → Billing, then work through Stripe’s onboarding.
You cannot publish a paid event until Stripe is connected and onboarding is complete. Do this first — Stripe verification can take a day or two, and it’s the one step you can’t rush on the morning you wanted to open registration.
→ Billing & payouts · Stripe Connect

​
3. Upload a waiver

Settings → Waivers. You need at least one before anyone can register. Waivers are org-level, then assigned to individual races — so write the general one now and add discipline-specific ones later. → Waivers

​
4. Invite your crew

Settings → Team. Registration desk, timing crew, whoever handles the money.
During beta, every org member has full access regardless of the role you assign. Invite accordingly.
→ Team & invites

​
5. Create the event

Create event from the dashboard. A four-step wizard: basic info, location, details, settings. Leave the status as draft. Nothing is public until you say so, which means you can build the rest of this with the page live but invisible. → Create an event

​
6. Add your races

Event → Races → New race, once per category group. For each race: name, format, capacity, categories, gender restriction, and whether it’s a relay.
Get the race structure right before you touch pricing — pricing, waivers, and questions all attach to races, so splitting one race into two afterwards means redoing all three.
→ Races list

​
7. Set pricing

Two levels:
  • Price schedules (org-level) — reusable early-bird / regular / late tiers.
  • Race pricing — apply a schedule to a race, or set a flat price.
Add discount codes now if you’re running any. → Price schedules · Race pricing · Discounts

​
8. Attach waivers and questions

  • Race → Waivers — tick which waivers each race requires.
  • Event → Questions — anything you need to ask (t-shirt size, emergency contact, category self-select, club affiliation).
→ Race waivers · Custom questions

​
9. Build the landing page and publish

Event → Landing page for the banner, description, schedule, sponsors, and photos. Then set the event status to published. Open time2.bike/events/[slug] in a private window and register yourself for the cheapest race. It’s the only way to be sure the whole chain works — waiver, questions, price, receipt. → Landing page builder
!!-IMAGE-NEEDED-!! — A published event landing page as a rider sees it, with the race list and Register button.

​
Then, before race day

1

Assign bib numbers

Event → Bibs. Auto-assign a range or import a list.→ Bibs
2

Recruit volunteers

Event → Volunteers — opportunities, shifts, and race-day check-in.→ Volunteers
3

Set up timing

There’s nothing to create — open the event’s Live Timing tab and the timer is there, covering every race. Issue QR codes to your operators; they don’t need accounts.→ Race-day runbook
4

Print your start lists

Event → Registrations, filtered per race.→ Event registrations

​
And after

1

Finalize and publish results

→ Finalize & publish
2

Handle refunds and no-shows

→ Refunds
3

Check your numbers

→ Event analytics

​
Things people get wrong the first time

Verification isn’t instant. Start it on day one, even if the event is months out.
Register yourself for real, from a private window, before you share the link. Refund yourself afterwards.
Pricing, waivers, and questions all hang off races. Settle the race structure first.
Use timing links instead — they work on one event and nothing else. See Volunteer links.

​
Next

Dashboard tour

Reading your org dashboard.

Create an event

The wizard, field by field.