Blog/Association Events Guide

Association Event Registration: Member Pricing, Eligibility and Waitlists

A practical guide to the event registration module within association management software, covering member pricing, eligibility, tickets, waitlists, and attendance.

Author: Vivien Yao · Co-founder of Component.app | Ex-Journalist | Ex-Director at F500

· 11 min read

Association event registration helps an association take bookings for conferences, workshops, CPD sessions, AGMs, and other member events. It can recognise a member, show the right ticket and price, check eligibility, manage guests and waitlists, collect payment, and record attendance. In Component.app, event registration is included in the membership management software, so every booking and attendance result can stay connected to the member record. This guide explains the rules an association manager should define before configuring it.

01 · Recognise the registrant

What Makes Association Event Registration Different?

Picture a member registering for a workshop with a personal email address while their membership record uses a work email. A basic ticketing tool may treat them as a stranger and charge the public price. Association event software needs to recognise the person and understand their membership: whether it is current, which grade or company they belong to, and whether that gives them a particular price or access. That is the core of member-aware registration.

Purchaser

Completes the order

May pay for their own ticket, a guest, a company group, or another person's registration.

Registrant

Attends the event

Needs an individual ticket, communication, check-in, and attendance result.

Member

Provides eligibility

The current membership, tier, chapter, committee, or credential may determine access and price.

Organisation

Owns the relationship

A company may receive the invoice, allocate included seats, or connect several representatives to one booking.

One person may use two email addresses

Where possible, connect a booking to an internal member number that stays the same when an email address changes. If the system cannot find a confident match, let staff review it instead of silently creating a second record for the same person.

Download the association event registration checklist

Use the printable PDF to list member tiers, eligibility rules, ticket choices, free or complimentary registrations, group bookings, waitlists, payments, attendance, and member-data updates.

02 · Apply the right rate

Give Each Person the Right Ticket and Price

Associations commonly combine member and non-member, student and professional, early-bird and standard, individual and group, guest, sponsor, exhibitor, speaker, chapter, and committee prices. The system should calculate the eligible ticket from the membership and event rules and explain the result.

Example pricing decisions
ConditionExample result
Active Professional Member before the early-bird deadlineProfessional member early-bird ticket
Lapsed memberNon-member ticket or a renew-first journey
Active Student MemberStudent member ticket
Corporate representative with an available included seatIncluded or corporate ticket
Invited speakerSpeaker ticket with the configured fee and access
Public visitorStandard non-member ticket

Define priority when several rules apply. For example, decide whether the student-member rate overrides the early-bird member rate and whether a sponsor can also use a corporate allocation. A shared code is easy to distribute but can be forwarded to someone who does not qualify.

03 · Check the correct date

Decide When Someone Must Be an Active Member

A person can be active when booking but lapsed when the event takes place. Decide whether membership is checked on registration, on the event date, at check-in, or at more than one point. The policy may allow the current price, require renewal first, hold the price until a deadline, or change access later. Test the chosen rule instead of leaving the answer to whichever system checks first.

  • Restrict tickets by active membership, tier, grade, chapter, committee, credential, or invitation.
  • Explain why a person is not eligible and provide the permitted next action.
  • Do not use a private URL as the only access control; links can be forwarded.
  • Separate renewal and event payment even when both appear in one guided journey.
  • Record the eligibility and pricing rule used for the confirmed registration.

04 · Handle linked bookings

Plan for Guests, Company Bookings, and Limited Places

A member may register a guest, a company may register several representatives, and an administrator may book on behalf of another person. Decide whether all attendee details are required immediately, who may edit the group, how substitutions work, whether corporate seats limit the member price, and which person receives each communication and ticket.

Capacity can exist at several levels
CapacityExample
Event200 people across all ticket types
Ticket type20 guest places and 10 sponsor allocations
Session40 workshop seats inside a larger conference
FormatSeparate in-person and online limits
GroupTables, teams, or corporate allocations

Distinguish reserved, pending, paid, confirmed, and cancelled places. If an unpaid registration holds capacity, define how long the hold lasts and what releases it. Authorised staff overrides should remain visible rather than silently increasing the limit.

05 · Fill released places

Make the Waitlist Fair and Easy to Operate

01

Waitlisted

The eligible person joins an ordered queue using the event's defined priority rule.

02

Invited

A released place is offered and the person receives a clear acceptance and payment deadline.

03

Held

Capacity is reserved during the confirmation window without marking the person attended or fully confirmed.

04

Confirmed or expired

Acceptance completes the registration; expiry releases the place to the next eligible person.

Decisions the waitlist needs

  • Is order first-come, member-priority, tier-based, or manually controlled?
  • How long does an invitation reserve the place?
  • Can a group wait for several seats together?
  • Does a cancellation promote automatically or require staff review?
  • Which overrides can staff make, and how are they recorded?

06 · Preserve the transaction history

Keep Bookings, Payments, Cancellations, and Refunds Clear

Registration

Reserved or confirmed

The attendee has a place under the configured capacity and confirmation rule.

Payment

Pending, paid, failed, or waived

The financial outcome may occur before or after the registration changes state.

Change

Cancelled or transferred

Preserve the original booking and record the cancellation, substitute, capacity release, and communication.

Refund

Requested, processed, or declined

Keep the amount, policy, payment source, accounting result, and registration consequence connected.

For each ticket, define cancellation deadlines, full or partial refund periods, transfer rules, administrative fees, and whether the place returns to capacity. Deleting the original registration removes history needed for finance, member service, and event reporting.

07 · Close the loop

Send Attendance Back to the Member's History

Buying a ticket does not prove that someone attended. The association should decide what counts as attendance, whether individual sessions matter, and who may correct a check-in mistake. If attendance awards CPD points or a certificate, the result should return to the member's history with enough detail for staff and the member to understand where it came from.

Demonstration checklist

  • Apply member, non-member, student, guest, and early-bird pricing without shared codes.
  • Check membership on the event date and guide a lapsed member through the permitted option.
  • Let a corporate administrator register several representatives with individual tickets.
  • Promote a waitlist place, expire the hold, and offer it to the next person.
  • Cancel a ticket with a partial refund and preserve the original history.
  • Transfer a ticket and keep purchaser, attendee, organisation, and payment clear.
  • Write attendance and any configured CPD result back to the correct person.

Bring One Event With Difficult Pricing or Eligibility

Component can be configured around member-aware forms, eligibility rules, ticket types, prices, waitlists, attendance, and their relationship to membership data.

Member and guest pricing
Eligibility and capacity
Waitlist and cancellation states
Attendance and member history
Explore Membership Management Software

08 · FAQ

Frequently Asked Questions

What is association event registration?+

It manages bookings, pricing, capacity, payment, and attendance for association events. In Component.app, the feature is included in the membership management software and can use membership, tier, chapter, committee, or credential data to decide eligibility and price.

How can an event system verify member pricing?+

It can require a member login or check a verified identity against the membership database. The system should use current membership rules rather than rely only on a promotional code.

Can non-members register for association events?+

Yes, when the event allows it. The association can offer public tickets and different prices while keeping the non-member contact distinct from an active membership.

What happens when an event is full?+

The system can close registration or add eligible people to a waitlist. A complete workflow defines how a place is offered, how long it is held, and what happens when the invitation expires.

Should event attendance update CPD records?+

It can when the organisation defines the eligible sessions, attendance conditions, and units. The source and any corrections should remain traceable.

Can one person register a whole company team?+

Yes, if the system distinguishes the purchaser from each attendee and checks corporate seat, membership, or pricing rules. Each attendee should retain an individual registration and attendance record.

Continue reading

Which related guide should you read next?

Share this post