One register for every member, company and prospect

AMS · 01 · 01

People and companies, not rows in a sheet

A person can hold several roles over the years: applicant, then member, then board member, then honorary member. SupaGuild keeps one identity per person and attaches memberships, qualifications, invoices, consents and event tickets to it. Companies are members in their own right, with the people who represent them.

• Membership tiers you define: ordinary, family, junior, corporate, honorary, with their own fee and renewal period.
• Status that follows the rules of your statute: active, pending renewal, lapsed, suspended, resigned.
• Prospects kept apart from members, so the register only counts who actually pays dues.
• Duplicate detection on import and on new applications.

AMS · 01 · 02

Fields the association defines

Boat class, sail number, berth, licence number, home port, dietary requirements for the annual dinner: every association asks for something generic software does not have. Add your own fields, choose who sees them, and decide which changes a member makes in the portal wait for approval before they are published.

• Text, number, date, choice and yes/no fields, grouped in sections.
• Visibility per field: staff only, member only, public directory.
• An approval queue for profile edits that matter, such as a new address or a changed company name.

AMS · 01 · 03

Qualifications with an expiry date

Skipper licences, first-aid certificates, race officer grades, professional registrations: the qualifications register stores the document, the issuing body and the expiry date. Members upload renewals themselves from the portal; staff see what is about to expire before it does.

• Expiry alerts to the member and to staff, with the lead time you choose.
• A register view filtered by type, status and chapter, exportable to a spreadsheet.
• Qualification types you define, with the evidence each one requires.

AMS · 01 · 04

A log you can show the auditor

Every change to a member record is stamped with who did it and when. Staff can filter the log per member, per field or per day, and the association can export it with the rest of its data at any time.