Adult or parent/guardian completes the public join request.
ClubOS admin flow
New Join Request Onboarding
The request stays in Requests while the applicant is being reviewed. Once live member records exist, ongoing lifecycle changes move to Members.
Request handling
Decision or payment
Member records
Closed outcome
The request appears in Admin → Requests with Request status New.
Review applicant details, notes, duplicate warnings, and guardian details for junior requests.
Use Profile incomplete, Profile submitted, and Pending approval to show where review currently stands.
If accepted but fees or setup are still due, select Approved - pending payment.
Waitlisted
Suitable, not ready
Keep open for follow-up.
Rejected
Declined
Close with Rejected when finished.
Withdrawn
Applicant stopped
Close with Applicant withdrew.
Use this only when the club is ready to create or link live member records.
If no linked member IDs exist, confirm Ready to activate and use Create member records.
Adult
One active member
The adult applicant becomes one live member record.
Junior
Guardian + juniors
Create guardian/account holder first, then linked junior records.
Linked member IDs are stored. Ongoing lifecycle changes happen in Members.
Important distinction: Request status is case handling
(New, In progress, Closed). Journey stage is the applicant
onboarding path. Member lifecycle statuses such as Active, Paused,
Suspended, Offboarded, and Archived are managed later from
the Members page.
Admin walkthrough
Open walkthrough video
YouTube
Watch the flow in context
Use this alongside the diagram when explaining how a new join request moves from review to Ready to activate and then into live member records.