RG · Club OS module

Open the season without rebuilding the intake process.

Registrations is how families join, renew and pay. It connects a person, a product, a fee and a status so the registrar and treasurer work from the same list instead of reconciling two spreadsheets after the rush.

Registrations

New product

Live view

2026 Junior season Open 214 paid
Senior playing fee Closing soon 61 unpaid
Volunteer levy Open 88 paid
The job

What Registrations is for.

Give the club a controlled way to open a season: the right fields, the right fee, a close date, and a live view of who has started, paid, or still needs a nudge.

Product screenshots go here This module will carry real Club OS captures of the working screens. The layout is ready for them.
Who uses it

Built around real club roles.

Registrar

Builds products, watches incomplete intake and follows up missing details.

Treasurer

Sees payment status without waiting for a separate export.

President

Knows whether the season is actually filling, not just “registrations are open”.

Family / member

Completes one intake path instead of a form, an email and a bank transfer with no status.

Inside the module

The functionality committees actually run.

01

Season products

Create a registration product for an age group, senior fee, volunteer levy or trial. Each product has a name, audience, dates and fee so the club is not inventing a new form every year.

02

Intake that matches club work

Capture the fields the club actually needs for teams, medical notes, volunteer interest and payment. Extra fields create extra chasing. Missing fields create extra emails later.

03

Payment status in the same view

Paid, unpaid, partial and overdue sit next to the person. Registrars and treasurers stop arguing about whose list is current.

04

Follow-up without a side list

See who started and did not finish, who has not paid, and who needs a reminder. EquippedAI can draft payment follow-ups from that same list.

05

Connected to People & Teams

A completed registration should update or create the person record. The club should not re-type the same family into the register after they have already enrolled.

06

A close date the committee can defend

When intake closes, the club has a clean picture for grading, teams and fixtures. Late exceptions stay visible instead of disappearing into inboxes.

How it runs

A path volunteers can repeat.

01 · Set the product Name the season offering, fee, close date and who it is for.
02 · Publish the path Open intake when the committee is ready, not when one volunteer has a spare hour.
03 · Watch the list Work incomplete and unpaid records while the season is still forming.
04 · Hand off to operations People, teams and grading pick up from a register that already knows who enrolled.
What it replaces

The hidden systems clubs already have.

  • Google Forms plus a bank rec
  • Unpaid lists in the treasurer’s notebook
  • “Can you resend the form?” emails
  • Manual copy into a member sheet
Connected modules

This work does not sit alone.

See Registrations in a walkthrough.

We will show the working screens, the volunteer path, and how this module connects to the rest of Club OS for your club.

Ready when your committee is

Give the club a system that outlasts the season.

Start with the workflows causing the most pressure, then grow into a full Club Operating System.