Registrations, member linkage, and the HQ privacy boundary

What this article covers

Events (hq.verinode.ai/events) shows association leadership a rollup of upcoming and past events: how many registrations each has, how full they're getting, and what turnout looked like afterward. That page is walked through element by element in Events in HQ: how the association events rollup works.

This article goes one level deeper, into questions that come up once you start relying on those numbers: how a "registration" actually gets counted, what the different registration statuses mean, how a registration connects back to a member when that member exists both on your roster and as a Verinode operator, and, most importantly, why HQ only ever sees counts and rates here, never a list of which specific people registered, attended, canceled, or sat on a waitlist.

How a registration gets counted

Every event on your Events page has a running registration count and, once the event has passed, an attended count. Both are built the same way for every event in your association, with one rule applied consistently: a canceled registration is never counted, anywhere.

Concretely:

• Registration count for an event is the number of registrations currently in any status other than Cancelled. That includes people who are simply Registered, people already marked Attended, and people sitting on a Waitlist. All three represent someone who currently has a live claim on a seat at that event, so all three count toward the total you see on the Upcoming Events and Recent Events tiles and in the hero panel's "Registrations" figure.
• Attended count for a past event is the number of registrations specifically marked Attended. This is a subset of the registration count above, never larger than it.
• Attendance rate, shown in the hero panel, is attended divided by registered, calculated separately for each past event and then averaged evenly across events, so one unusually large event doesn't dominate the network-wide figure.
• Next event fill, also in the hero panel, is the next upcoming event's registration count divided by its stated capacity, capped at 100%. If no capacity is set for that event, this figure is simply blank rather than showing a misleading number.

The registration status vocabulary

Every registration on an event carries exactly one of four statuses at any given time:

| Status shown in Verinode | What it means | |---|---| | Registered | The member has signed up and holds a seat. Counts toward the event's registration total. | | Attended | The member showed up. Counts toward both the registration total and the attended total. | | Waitlist | The member signed up after the event reached capacity (or after some other limit was reached) and is queued behind confirmed registrants. Still counts toward the registration total, since it represents active interest and a live claim, just not yet a confirmed seat. | | Cancelled | The member's registration was withdrawn. Excluded from every count on this page, past or present. |

These four statuses are the complete list. There's no "no-show" status distinct from a registration simply never being updated to Attended, and there's no partial-attendance concept (a multi-day event is either attended or not, at the level Verinode tracks).

How a registration links back to a member

Your association's Member Directory holds every business on your roster, whether or not that business has ever signed up for Verinode itself. Events registrations need to connect back to someone on that roster, but at any given moment a member might exist in one of two states: purely as a roster entry your association manages, or as a roster entry that has also become a full Verinode operator with their own account.

Every registration is linked to whichever of those applies, roster entry, operator account, or both, so a member never has to be a signed-up Verinode operator just to register for an event. If a member later joins Verinode as an operator, their past and future registrations reconcile onto that operator account automatically; nothing about your Events history needs to be re-entered or fixed up when that happens.

Why HQ never sees a member's individual event data

This is the part worth being explicit about: Events never shows you a list of who is registered, who attended, who canceled, or who is on a waitlist for any event. Every number on this page, the event tiles, the hero panel, the attendance rate, is a count or a rate rolled up across registrations. There is no drill-in from an event to a roster of named attendees anywhere in this section.

That's a deliberate boundary, not a missing feature. Verinode HQ is the network intelligence layer for your association, built to show leadership aggregate patterns and compliance status across the membership, never an individual member's own business activity in detail. A member choosing to register, show up, wait-list, or back out of an event is that member's own activity. Your association's role, and Verinode's role on your behalf, is to see the shape of the program as a whole, whether turnout is healthy, whether an event is filling up, whether attendance is trending up or down, not to monitor any one member's individual participation.

This mirrors the same boundary that holds across every other HQ surface: HQ sees your network's own aggregates and rankings, never a single member's private underlying records. Member Directory is the closest comparison: it does show roster-level compliance status per member (dues current, certifications on file, and similar), because compliance status is exactly what association leadership needs to track member-by-member. Events registrations are different: attending an event isn't a compliance obligation, so there's no member-by-member view to show, only the network-wide picture.

Where this shows up on the page

Everything described above feeds the same page walked through in the Events overview:

• The hero panel's "Registrations" figure is the sum of every upcoming event's non-canceled registration count.
• Each tile in Upcoming Events shows that event's own registration count and, if capacity is set, how it compares.
• Each tile in Recent Events shows that event's attended count against its total registrations.
• The hero panel's attendance rate and next event fill are both built from the counting rules above.

None of these figures identify a person. They're all counts and ratios, by design.

Empty states

• If your association has no events recorded at all, both rows read their standard empty-state copy ("No upcoming events scheduled…" and "No past events yet…"), and every hero figure shows as zero or blank rather than an error.
• A newly created event with zero registrations shows "0 registered" on its tile, not an empty tile, since the event itself exists even before anyone has signed up.

Using this correctly

1. 1Treat every number on Events as a program-level signal, not a lookup tool. Use it to judge whether an event is filling up, whether turnout is trending well, and whether your event calendar overall is healthy.
2. 2If a figure looks off, for example an attendance rate that seems too low, check the underlying registration and attendance records in your association's own event-management process. Correcting or canceling a registration there is reflected here on the next refresh.
3. 3Don't expect a per-attendee list here. If a use case genuinely needs one (check-in, badge printing, follow-up outreach to specific registrants), that has to be handled outside Verinode, in whatever system your association uses to run the event itself.

Related help

• Events in HQ: how the association events rollup works
• Member Directory: how HQ separates roster compliance status from private member data
• How Verinode HQ separates network aggregates from private member data