Event management software for member organizations

Each event is configured along a few axes:

• Free or paid
• Members-only or public
• Assigned to a group, a chapter, or the whole organization
• Tagged with an event type, used later for reporting
• Given a maximum capacity, with registration closable manually at any point

Physical events pin to Google Maps, so attendees tap through to navigation from the event page. Online events carry a Zoom, Google Meet, or Teams link, revealed only after a person has registered.

Each event stores its own time zone, and every viewer sees the start time converted to their own. This matters for international bodies where a single webinar reaches members across several time zones.

Settings that repeat across events are saved as a template, and new events start from it. Recurring and multi-day events are supported with full agenda handling, so a monthly chapter program is created once rather than rebuilt each time.

Orgo reads an event description and suggests the relevant UN Sustainable Development Goals for one-click tagging. Organizations reporting impact to funders or ministries get the classification without tagging events by hand.

A simple event uses one-click RSVP. A camp, training, or congress uses a full registration form built from standard fields plus any custom fields your organization defines, such as dietary needs, arrival details, or a company name for the badge.

An event can sell several ticket types at once. Member-only tickets and member prices are tied to membership level, so the discount applies from the member record rather than from a code you have to distribute and police.

Pricing changes over the sales period without manual edits:

• Early-bird pricing set through ticket validity windows
• Late fees for registrations after a cut-off
• Voucher and promo codes for partners, speakers, or campaigns

A three-stage price ladder is configured once at the start of the sales period instead of being switched over by hand on each date.

Unlimited add-ons attach to a ticket, covering the extras a real event sells: a plus-one, meals, accommodation, parking, or merchandise. Guest tickets and invitations cover the seats a membership entitles a member to bring.

When an event reaches capacity, further registrants join a waiting list rather than being turned away. Organizers admit people from the list as places open up.

Public events accept registrations from people who are not members and have no login. Those registrants become contacts in your database, matched by email or phone, and their full attendance history is retained.

If a contact later becomes a member, the events they already attended move onto the new member account. External speakers, partner organizations, and guests stay in the same database as members instead of in a separate ticketing tool.

Stripe processes ticket payments in 46+ countries. Payment methods are offered automatically per device and region:

• Cards, debit and credit
• Apple Pay and Google Pay
• Revolut Pay and other digital wallets
• Direct debit where Stripe supports it

Currency is detected automatically, and payments update the member or contact record in real time through Stripe webhooks.

Corporate and institutional ticket buyers need an invoice, not a card receipt. Orgo issues invoices against ticket purchases with billing and tax details and any custom fields your finance team requires. Each invoice is payable by card link or by bank transfer, marked as paid once the money lands.

A chapter with its own legal entity connects its own Stripe account, and ticket revenue from that chapter's events goes straight to its own bank account. The national office does not sit in the middle of local ticket sales, splitting transfers afterwards.

Financial analytics report revenue per event alongside membership and donation revenue, filterable by any period. Everything exports to CSV, and every export is logged.

Every registrant receives a QR code by email. Organizers scan it in the Orgo mobile app to check attendees in, which replaces a printed list and a pen at the door. Offline mode keeps check-in working at large gatherings with poor connectivity.

Orgo tracks two distinct statuses. Attending means a person registered. Attended means they were checked in on the day. Admins override either status manually, so a no-show never counts as participation in a report.

Each event has an attendee table with filters, logs, and CSV export. Columns can be built from any field on the registration form, so dietary needs, troop, or company name appear as sortable columns rather than buried in individual responses. A gallery view shows attendees as profile cards.

Every event a person attends is recorded on their profile and stays there. Years of participation become searchable and reportable, which turns event attendance into an engagement signal for renewals rather than a fact that lives only in last year's spreadsheet.

Events marked as training write a training record to the participant's profile, with trainers tracked separately from participants. Organizations with certification or safeguarding requirements can show who was trained, by whom, and when.

Attendance data feeds statistical reports broken down by event type and age group, configurable per market. Youth organizations reporting yearly to a ministry of education pull those figures from the same records that ran the event.

The agenda spans several days and several stages or rooms running in parallel. Each session carries its own capacity limit, so a workshop with 30 seats stops accepting bookings while the plenary stays open.

Attendees bookmark the sessions they plan to join and carry their own program through the event, instead of working from a printed grid.

Featured speakers appear on the event page with name, photo, and biography, so the program doubles as the promotional page rather than being maintained separately on a website.

Organizers post announcements to an event feed during the congress, and attendees receive them as notifications. In-event voting handles the decisions a general assembly takes in the room.

The congress layer covers what happens between sessions:

• Event badges with QR codes
• Badge scanning to capture a contact
• A participant list, privacy-scoped and restricted to adults where minors attend
• One-on-one meeting booking slots

The event experience runs inside the standard Orgo mobile app, so members are already authenticated and download nothing new. Non-member attendees use the same app. Offline mode covers venues where connectivity fails.

Publishing an event notifies its audience automatically. Reminders then go out on a fixed schedule:

• 24 hours before the start
• 1 hour before the start

Each reminder includes the location and the start time converted to the recipient's own time zone.

Email campaigns target any event's attendee list directly, filtered by attendance status. Practical information goes to confirmed attendees only, and a follow-up goes to the people who were actually checked in.

Every event gets a public landing page that can be shared directly or on social media. The full list of upcoming and past events embeds into any external website through an iframe, with no Orgo branding, and updates as events are published.

Each event has its own media drive and gallery for files, photos, and presentation decks. Video links attach to the event after it ends, so recordings and speaker slides stay on the event record rather than in a newsletter people have to search for.

Surveys are built in the Forms module and sent to an event's attendee list. Responses are stored in the platform and linked to each respondent's member or contact record, including respondents who have no account.

An event created at headquarters propagates to every local chapter in one step. Each chapter gets its own copy to manage, with its own attendees and its own registrations, while the national team keeps the overview.

The event manager role exists at organization, parent-chapter, and local-chapter level, isolated to that level's data. A chapter lead publishes and runs their own program without being given access to any other chapter's attendees.

An event can be scoped to a specific group, chapter, or region, so a regional training reaches only that region and a board meeting reaches only the board. Not every event goes to the full membership.

Event attendance awards points and badges, with a per-event override on the point value. Volunteer hours and participation streaks become part of the same record that tracks membership, rather than a separate tally kept by a chapter lead.