Event Debrief

Three separate forms ran across a 23-day window for this one event: a waiver in late July, a jersey size and medical form in early August, and the full attendee registration form in the days right before the event. Fourteen families completed at least two of these, and a few completed all three — meaning the same medical conditions, the same shirt sizes, and the same emergency contact details were typed in more than once by the same person.

This isn't a one-off — it's the direct result of not having a single system that recognises "we already have this person's information." Every extra form is friction for a parent who's already busy, and every re-entry is a fresh chance for a typo or a missed field, which is exactly what happened (multiple spelling variants of the same person's name across different forms had to be manually reconciled to get an accurate headcount for this report).

The fix isn't complicated: one intake, done once per person, that different registration types (player, sponsor, stallholder, general attendee) route into — collecting whatever's relevant to that role in a single pass rather than staggering it across separate campaigns weeks apart.

The final, trusted team rosters for this event existed as a manually typed list, cross-referenced by hand on the Friday night before the event — not as an automatic output of the registration system. That's a huge amount of manual effort that has to be repeated for every future event unless it's replaced with something that tracks completion automatically.

It also means there were two "truths" running in parallel for a while: what the forms said, and what the manual cross-reference said. They didn't always agree, and reconciling them (which is most of the work behind the data section of this report) took real time after the fact rather than being available in real time on the day.

Right now, "who came" is assumed to be "who registered." There's no wristband, no scan, no door check — so a no-show looks identical to an attendee in the data, and someone who never registered but rocked up on the day (which happens, and needs to be allowed for at a free community event) has no record at all.

The fix already scoped for next event: everyone — players, spectators, sponsors, stallholders, volunteers — gets a wristband on arrival, tied to a QR code scan. That scan becomes the actual attendance record, replacing the current guesswork entirely.

Only a fraction of registered players have a completed medical form on file, and even where the information exists, there's no defined way for the people running the event on the day to actually access it if something happens. If a participant has a medical event, the person attending to them shouldn't have to go looking for a form submission from three weeks ago.

This needs two things, not one: the data itself needs to be reliably attached to each participant's record (captured once, at intake, not optional), and there needs to be an actual written operating procedure for what staff do if a medical emergency happens — who's notified, who has authority to act, and how the participant's medical info gets into the hands of whoever needs it, fast.

The one real sponsorship enquiry (Leisha Hunter, Care Done Differently) sits in the form data as a submission — there's no record of what happened after that, whether she was followed up, or what tier she landed on. Worth closing the loop on this specific enquiry, and worth building a lightweight way to track sponsorship enquiries through to a decision going forward, rather than letting them sit as a form submission and nothing else.

Getting an accurate headcount for this report meant manually removing 3 duplicate resubmissions, untangling one family who tested a form 8 times, and filtering out fake sponsorship test entries from the real data. None of that is a criticism of anyone — it's what happens when there's no single system enforcing "one person, one record." It's also exactly the kind of thing that becomes invisible (and unnecessary) once there's a proper intake system with its own validation built in.

Volunteer applications need to capture compliance documents — blue cards and similar — at intake, and the system needs to flag when any of those are approaching expiry so someone gets a notification and can send a direct message to that volunteer, rather than this being tracked manually or discovered too late. Some of this groundwork already exists inside the Active Heroes app and should be reused here rather than rebuilt from scratch.

A tiered pricing funnel built into registration: people can pre-purchase merch at a discounted rate ahead of the event, pay standard price if they buy on the day, and if something sells out, they can still place an order afterwards for later delivery or pickup. This turns merch from a single-day sales moment into a funnel that starts the moment someone registers.

This needs to be a complete tracked system, not just a payment link: pre-orders need to be recorded against each person's registration so staff can hand merch over at check-in already sorted and ticked off, on-the-day sales need to draw down from the same stock count in real time, and sold-out items need to convert automatically into a post-event order rather than a lost sale.

Done properly, this also gives a live picture all day of exactly how much stock is left, which sizes are running low, and who still hasn't collected what they've already paid for — solving the "who do we chase" problem before it becomes one.

Limitless Cup doesn't have to stay a single outdoor rugby league event. Expanding into indoor sports and other sport types opens the program up to more participants, more of the year, and more venues — turning it from one annual gala day into a broader offering under the same brand.

Alongside sport, workshops that directly support families — the kind of thing parents and carers actually need — add a second, complementary offering. This also creates a new sponsorship product: sponsors can come in not just as a logo on a jersey, but as the host of a workshop stall, putting their name directly against something genuinely useful to families rather than just signage. That's a stronger, more memorable sponsorship placement, and a new revenue line in its own right.

Tiered sponsorship packages, day-specific specials, and on-site signage remain a core revenue line. Selling launch sponsorship for the next event while this one is still fresh in people's minds — rather than starting the sponsorship conversation from zero each time — should become a standard part of the post-event follow-up, not an afterthought.

Licensing this out nationally is a real, reasonable possibility — not a stretch idea. If the intake, ticketing, check-in, and event-day operating procedure all get built properly for Limitless Cup, that whole framework becomes a standard operating system that other communities could license to run their own version of the event, roughly the way a franchise model works.

A placeholder price point of around $1,000/year has been floated, but this needs proper deliberation before it's fixed — what exactly a licensee gets (the app, the templates, the operating procedures, ongoing support), and what it costs to support them, both need to be worked out first.

A family membership, floated at around $10/month, would give families ongoing access to mindset lessons, video training, and parent support content between events — not just something tied to a single gala day. At a modest scale (the example used was 80 families), this becomes a genuine monthly recurring revenue line that helps fund future events rather than each one starting from a blank budget.

This also gives the organisation a reason to stay in touch with families year-round, not just in the lead-up to each event — which directly supports the broader community-building goal behind Limitless Cup in the first place.

A referral points system — earn points for bringing a friend or family member in, spend them on merch discounts — turns word-of-mouth into a built-in growth loop rather than something that happens by chance. This sits in the same points economy as attendance-based rewards, so the two ideas reinforce each other rather than needing separate systems.

Not everyone who shows up on the day will be a registered player — some will just be curious and want to try it. A simple "have-a-go" registration path lets someone sign up on the spot for a taster session rather than the full competition: a coach-led run-through, a bit of a game, something with a small win or moment of achievement at the end of it, without needing to be part of a team or the tournament itself.

This works as a genuine lead-in to the training programs — it gives someone a real taste of what's on offer, on the day, at zero commitment, and gives the organisation a warm, well-timed reason to follow up afterwards about joining properly. It needs coaches rostered specifically to run it, and a lightweight on-the-day sign-up (name, email, quick consent) separate from full player registration, feeding into the same system as a "prospect" rather than a competitor.

An "adventure passport" for the day: attendees carry a passport (physical or in-app) containing questions or challenges supplied by sponsors and stallholders. To answer them, people have to actually go and talk to each sponsor or stallholder — turning a walk past a stall into a real conversation. Completing enough of the passport earns points, and hitting a minimum point threshold enters them into a draw for a prize at the end of the day.

This becomes part of the sponsor intake process itself — when a sponsor or stallholder registers, part of what they provide is their passport question or activity, which means the passport content is generated by the sponsorship pipeline rather than being extra work to create separately.

It's a strong, low-cost engagement mechanic: it drives foot traffic to every sponsor and stallholder rather than just the ones near the entrance, it gives families something structured to do throughout the day, and advertising a genuine prize at the end gives people a reason to complete it rather than wander off halfway through. It also directly supports the community-building goal — the whole point is getting people talking to each other and to the people running stalls, not just watching from the sideline.

Bonus points for opting in with a sponsor. A button in the app lets someone submit their own details directly to a sponsor or volunteer team's email — a genuine opt-in, not just a passport tick. Doing this earns extra points and extra draw entries on top of the base passport activity. This is what turns the passport from an engagement game into an actual lead-generation tool for sponsors: every opt-in is a real contact detail landing directly in a sponsor's inbox, which is a much stronger sponsorship benefit to sell than signage or a logo placement alone.

The bigger vision here goes beyond check-in and ticketing. The app should work as a genuine two-way communication tool on the day: a stallholder with a question can message the event management team directly and the right person gets a ping, rather than someone having to physically track down a staff member. A basic day-of community chat gives everyone attending — players, families, volunteers — a shared space to connect, which supports the community-building goal directly.

Sponsors, stallholders, and workshop hosts would each get their own login with appropriate access — able to promote within their allowed space inside the app. Anyone who registers becomes an account holder in the system, which means the organisation can broadcast messages to everyone (or specific groups) about upcoming events, sponsorship opportunities, or anything else — turning the app into an ongoing channel rather than something people only open once a year.

On top of that: an event comms channel for real-time, day-of operational messages (schedule changes, delays, venue directions), in-app maps so teams can find their area, and merch-specific messaging — tagging anyone who hasn't purchased yet and prompting them, or notifying people when their pre-ordered shirt is ready to collect.

There are a few live options for what Limitless Cup actually is as a business: a formal partnership between Active Heroes and LST, its own standalone entity separate from both, or simply a brand name and vehicle that different organisations use to host their own version of the event under one shared identity. Each option has different implications for who owns the data, who takes the revenue, and who carries the liability.

Tied to this: is Active Heroes a registered not-for-profit, and would Limitless Cup be one too, or something else entirely? This matters for everything from payment processing to how sponsorship and licensing revenue gets treated.

Ticket sales and registration payments need to go to whichever organisation is actually holding a given event — if Active Heroes is running it, payments go to Active Heroes' business; if LST is running it, payments go to LST's. Both already exist as separate businesses inside the Overskill system, so the underlying capability is there — what's needed is a standard landing page structure for an event that's wired to the correct business's payment setup depending on who's hosting.

Two ways this could go: one shared app that manages the event overall, with payments and data routed to whichever business is hosting a particular instance of it — or a duplicated app per organisation, so each one runs its own separate instance with its own payments and data. The first is simpler to maintain long-term; the second gives each organisation cleaner separation and full ownership of their own instance. This needs to be decided before the licensing model (above) can really be finalised, since licensees will need one of these two structures themselves.

Data collected through an event should belong to whoever the actual event organiser is — it's meant to function as their own reusable tournament and event management tool, one they can use to build their own business with, as far as they want to take it. This reinforces why the payment-routing and app-architecture questions above need resolving together, not separately.

A proper web presence for Limitless Cup — one that performs well in Google and AI-assisted search, and is properly connected to social media — is part of the foundation here too, separate from the app itself. This is the discoverability layer that brings people to the registration/landing page structure described above.

Replace the three separate forms with one intake process that branches by registration type. Players, sponsors, and stallholders get a more in-depth, separate registration path appropriate to their role, generating their own QR code. General attendees — people who just want to come and watch — get a much simpler path: name, email, basic info, still generating a QR code, kept deliberately lightweight since this is a free event and walk-ups need to be easy to accommodate.

Medical information and merch sizing get captured once, inside this same process, tied permanently to that person's record — not asked for again on a separate form weeks later.

Everyone checks in on arrival by scanning their QR code — players, spectators, sponsors, stallholders, volunteers, no exceptions. The scan identifies who they are, tells staff what wristband to hand over (role-based), and if they're a player, brings up their player card. No wristband means no entry — this needs to be enforced at the door, not just available as an option.

This scan becomes the actual attendance record for the event, replacing the current situation where attendance is only ever inferred from who registered beforehand.

Designated on-day staff need direct access to each participant's medical information should an emergency occur — not a form buried in an inbox from weeks earlier. Alongside this, a written operating procedure for what happens if a medical emergency takes place: who's notified, who has authority to act, and how the relevant medical details get to whoever needs them, quickly.

Whatever merch someone has pre-ordered gets recorded against their record at intake. When they scan in on the day, staff can see exactly what they're owed and hand it straight over, ticking it off as given. This keeps a running, live tally all day of stock remaining, what's sold, and who still hasn't picked up something they've already paid for.

The 1-week-prior cutoff needs to be a hard system trigger — registrations simply close — rather than something staff have to manually track and chase stragglers on. General on-the-day attendee registration can remain open, since that's meant to stay simple and available for walk-ups, but player, sponsor, and stallholder registration should lock on schedule automatically.

Volunteer applications capture compliance documents at intake, with the system flagging anything approaching its expiry date so a direct message goes out automatically rather than this being discovered too late. Reuse what's already built inside the Active Heroes app for this rather than starting from scratch.