Events in HQ: how the association events rollup works

Events is where association leadership sees a rollup of the events their association runs for its memberships: what's coming up, how registrations and turnout are trending, and how full the next ev…

5 min read·Updated July 14, 2026
On this page

What this section is

Events is where association leadership sees a rollup of the events their association runs for its memberships: what's coming up, how registrations and turnout are trending, and how full the next event is. It's a read-only intelligence view, not a place to build a calendar, send invitations, or manage registrations. Verinode surfaces the picture; running the actual event still happens in whatever tools your team already uses for that.

Events is one of the association-native surfaces in HQ. It's built for organizations that run membership programs (regional associations, industry groups, and similar networks), not for individual franchise systems. If your network doesn't run this kind of program, you won't see Events in your sidebar at all.

Where to find it

Events lives in the HQ sidebar at hq.verinode.ai/events. It only appears for HQ accounts whose network is set up as an association. Franchise systems and other network types don't get an Events entry, the same way associations don't see franchise-only surfaces like FDD financials or Discovery Day. This is a gate on the whole section, not a per-page permission: if your account type doesn't include it, the page isn't reachable at all, including by direct link.

Unknown directive: note

How the page is laid out

The page opens with a hero panel, then two horizontal rows of event tiles below it: Upcoming Events and Recent Events.

The hero panel

At the top, a large number shows how many events are currently scheduled in the future, labeled "Association events" with a pill underneath reading:

  • "No events scheduled" when there are none upcoming
  • "N upcoming" when there's at least one

Underneath the headline number, a line of text tells you what's next: the event's name, its date, and its location if one is set, separated by a middle dot (for example, "Next: Fall Regional Summit on Oct 14, 2026 · Denver, CO"). If nothing is scheduled, this line reads: "Events will appear here as your association schedules them."

Three supporting figures sit beside the headline:

  • Registrations, the total number of registrations across every upcoming event combined (cancelled registrations are never counted). The subtext reads "Across upcoming events."
  • Attendance rate, the average share of registered members who actually attended, calculated across past events. Each past event's own attendance rate (attended divided by registered) is averaged evenly, so one unusually large event doesn't skew the number. Subtext reads "Attended of registered, past events." If there's no past-event data yet, this shows as empty with the subtext "Awaiting past-event turnout."
  • Next event fill, how full the next upcoming event is, as a percentage of its registrations against its stated capacity. Subtext reads "Registrations vs capacity." If the next event has no capacity set, this shows as empty with the subtext "No capacity set."

Upcoming Events row

Below the hero, a horizontally scrolling row titled Upcoming Events shows one tile per future event, up to 12. Each tile shows:

  • The event name as the headline
  • A label showing the registration count (for example, "14 registered")
  • A subline combining the event date and location
  • A meta line showing either "N of C capacity" when the event has a stated capacity, or "N registered" when it doesn't

If nothing is scheduled, the row shows this text instead of tiles: "No upcoming events scheduled. Events will appear here as your association schedules them."

Recent Events row

Below that, a second row titled Recent Events shows one tile per past event, most recent first, up to 12. Each tile shows:

  • The event name as the headline
  • A label showing how many attended (for example, "9 attended")
  • A subline combining the event date and location
  • A meta line reading "N of R attended" (attended against total registrations), or "No registrations" if the event had none

If there's no event history yet, the row shows: "No past events yet. Turnout will appear here once your first event has taken place."

How to use it

Events is meant for a quick read on how your event program is performing, not day-to-day event operations:

  • Check the hero panel for a fast read on what's next and how full it's getting.
  • Watch the attendance rate over time as a signal of member engagement with your event program. A rate that trends down across events is worth a closer look at scheduling, format, or communication.
  • Use the Upcoming row to see everything on the calendar and how registrations are trending relative to capacity, so you can spot an event that's under-filling with enough runway to promote it further.
  • Use the Recent row as a turnout record: it's a running log of who showed up relative to who signed up.

Because this page is read-only, there's nothing to edit here. It reflects what has already been scheduled and recorded elsewhere.

How it fits HQ's role

HQ is the network intelligence layer that sits above the tools your memberships already use day to day, not a calendar, event-management, or registration system. Events follows the same rule every HQ surface follows: it shows an aggregate view assembled for association leadership, refreshed on a regular schedule, never a single member's private business data. What you see here is your association's own event and registration activity, rolled up for the people responsible for running the program, not benchmarked against or shared with other networks.

Verinode surfaces this picture for you to act on. Deciding what to change about the event program, whom to invite, and how to run it stays with your association's leadership.

Tip

The attendance rate and next-event fill figures are most useful once you have a few events of history to compare against. Early on, with only one or two events recorded, treat them as a starting baseline rather than a trend.

Was this helpful?