This walkthrough covers the full lifecycle of a club lotto draw — configuring prize tiers, opening entries, drawing numbers, and announcing winners — from the admin side. Members see only the public draw page; admins do everything through Club → Lotto.

Before you begin

• Your club must have Lotto enabled as a feature. Check Settings → Features.
• You need the Lotto admin role.
• Stripe Connect must be onboarded for paid ticket sales.
• Run through your local gambling-compliance checklist (regulator, age gating, responsible-play copy) — the Compliance section in the lotto admin captures these.

Step 1 — Overview

The lotto admin index shows a snapshot of your current draw: ticket sales, sponsor coverage, next-draw date, last-draw status. Each subsection has its own tab in the sidebar.

Step 2 — Settings: prize tiers and ticket price

Under Settings, configure:

• Draw schedule — weekly, fortnightly, or custom. Determines when new draws auto-open.
• Number range — e.g. pick 4 from 1-32. Members pick that many numbers per ticket.
• Ticket price — minor units. EUR/GBP supported depending on your Stripe Connect account currency.
• Prize tiers — match-4 jackpot (rolls over), match-3, match-2, lucky dip. Set fixed amounts or percentages of the pool.
• Compliance — regulator licence number, age gate, responsible-play helpline. Required in most jurisdictions; appears on the public lotto page.

Step 3 — Pricing management

Lotto pricing is separate from course/event pricing because draws often run as subscriptions (weekly auto-debit). Under Pricing, set:

• One-off ticket prices
• Multi-week subscription bundles (e.g. 13 weeks for the price of 12)
• Family / shared-ticket arrangements if your club offers them

Step 4 — Sponsorship

If a local business is sponsoring your draw, add them under Sponsorship. Sponsor logos and copy appear on the public draw page; sponsor sums boost the prize pot or underwrite specific tiers depending on how you set them up.

Step 5 — Open entries

Under Occurrences, you’ll see the upcoming draws. Each draw goes through three phases:

1. Pending — created but not yet open for sale
2. Open — accepting ticket purchases
3. Drawn — numbers drawn, winners notified

Click Open entries to flip the next draw to Open. Members can now buy tickets via the public site.

Step 6 — Monitor entries during the week

The Entries tab shows every ticket sold for the current draw, who bought it, when, and the numbers picked. Use this for reconciliation against Stripe transactions. The Audit Logs tab captures every status change for compliance.

Step 7 — Draw the numbers

On draw night, go to the current occurrence and click Draw numbers. The system picks the winning numbers using a verifiable random source and locks the result. You cannot edit numbers after drawing — this is intentional for regulator audit.

Step 8 — Review results and contact winners

Once drawn, the Results tab lists every winning ticket grouped by prize tier. Winners are automatically emailed (configured in Settings → Notifications); for large prizes your club may want to follow up manually as well.

The public lotto page shows the latest results immediately — you’ve already done the work.

After the draw

• Jackpot rollover — if no one matched the jackpot, the next draw’s jackpot auto-increments per your rollover rule.
• Payouts — payouts happen outside this system (bank transfer, cheque). Log the payout in the entry note for your records.
• Subscriptions — recurring tickets auto-renew for the next open draw. Members can cancel from their tenant portal at any time.

Common questions

Can we run multiple lottos at the same time?

One lotto per tenant in this version. A future release will support concurrent lotto types (e.g. weekly + special draw).

What happens to subscriptions if we change the ticket price?

Existing subscriptions keep the old price until the member renews or updates them. New tickets use the new price.

How do we void a sale (refund mistakenly purchased ticket)?

Use Club → Payments to find the Stripe charge and refund it. The lotto entry is automatically marked void when the Stripe refund webhook fires.