Skip to Content
HubIRL Help Center is live with mobile-first guides for members and admins.
Events and Tickets

Events and Tickets

This guide covers attendee and organizer workflows, with emphasis on event-day reliability.

Event Lifecycle (Organizer)

1. Draft

  • Create event with name, date/time, location, and visibility.
  • Configure ticket types and capacity.
  • Attach required forms and publish versions.
  • Assign event staff roles and permissions.

2. Publish

  • Publish only when event details and policy are final.
  • Once sales begin, date/time edits should be deliberate and minimal.
  • Visibility and access settings control discoverability and checkout behavior.

3. Operate

  • Use event admin tabs for tickets, staff, scan, attendance, and updates.
  • Scanner and readiness checks are canonical and enforce required-form completion.
  • Use overrides only when policy and permissions allow.

4. Close

  • Post final updates where needed.
  • Review attendance and incident outcomes.
  • Resolve refund/void actions deliberately.
  • Archive operationally complete events.

Ticket Lifecycle (Attendee)

  1. Discover an event.
  2. Select ticket type and quantity.
  3. Complete checkout (or free/comp flow).
  4. Open ticket in My Tickets.
  5. Complete required forms before arrival.
  6. Present QR at check-in.

Transfers

Before event start and when policy allows:

  1. Owner initiates transfer.
  2. Recipient accepts.
  3. Ownership updates and transfer history is retained.
  4. Member-only policy can block transfer if recipient already has an active ticket.

Designated Tickets at Checkout

One payer can assign tickets to other members at checkout:

  • payer remains financial source-of-truth,
  • ticket holder and payer can differ,
  • refunds return to original payer,
  • ledger keeps ownership and refund states explicit.

Critical Event Updates

  • Time-change alerts should only be sent for actual time changes.
  • Time text should be human-readable.
  • Non-time edits should not be labeled as time changes.

Event-Day Quick Checklist

  • Scanner operators are assigned and tested.
  • Required forms readiness is monitored.
  • Staff escalation owner is known.
  • Critical update path is ready.
  • Incident logging path is verified.

Where to Go Next

Last updated on