Try-Drivers (Guests)

Try-Drivers are non-member participants who can register for events — ideal for taster days, open events, and race-day drop-ins. They don’t consume a member license seat, have no login, and can be converted to full members at any time.

What makes a Try-Driver different from a Member?

How a Try-Driver registers

1. Share your public event link (/events/[id] or a WordPress embed)
2. The registration form collects:
   • Name, email, phone
   • Address + postcode
   • Date of birth
   • Emergency contact name + phone
   • Marketing opt-in (checkbox)
   • For racing events: an asset selection
3. If the event is paid, Stripe Checkout collects payment
4. On success, the booking is confirmed and a QR code is emailed
5. The guest’s profile is saved for future events

Managing Try-Drivers (Admin)

List view — /dashboard/guests

Visible to CLUB_ADMIN, MEMBERSHIP_ADMIN, EVENT_ADMIN, and SUPER_ADMIN. The list shows:

• Name + email + phone
• Booking count
• Marketing status (Opted in / Opted out / Unsubscribed)
• Conversion status (Guest / Converted)
• Search by name/email/phone
• Filter by converted status

Detail view — /dashboard/guests/[id]

Shows the full guest profile, emergency contact, all event bookings, and two actions:

• Convert to Member — creates a User with the MEMBER role and re-links all prior bookings to the new user account. Requires an available license seat.
• Delete — removes the guest record. Their existing bookings keep the guestName / guestEmail snapshot so check-ins and reports remain intact.

Converting a Try-Driver to a Member

Converting:

1. Creates a new User record (no password — login via OTP)
2. Adds the MEMBER role
3. Re-links every prior booking from the guest to the new user
4. Marks the guest row as converted (for audit / history)

After conversion, you can assign a membership pack from the standard /dashboard/members/[id] view. A license seat is consumed at the moment of conversion.

Marketing & unsubscribe

• Every Try-Driver has a unique unsubscribe link included in their emails: /unsubscribe/[token]
• Clicking the link is idempotent and immediately sets marketingOptIn = false
• Once unsubscribed, re-submitting the registration form does NOT re-opt them in — you must explicitly edit their profile

Participants on race day

Try-Drivers appear in event participant lists alongside members, respecting the tenant’s eventParticipantVisibility setting:

• HIDDEN — no participants shown
• COUNT_ONLY — total + breakdown by class (racing events)
• NAMES_AND_CLASS — “First L.” + class, privacy-formatted

Check-in uses the same QR-code scanner as member bookings.

Privacy & data handling

• Try-Driver data is tenant-scoped and never shared across clubs
• The unsubscribe token is tenant-unique high-entropy and cannot be guessed from the email address
• Deleting a guest preserves the booking snapshot (name + email) but removes the guest profile itself, honouring erasure requests while keeping financial / attendance records intact