Community analytics and reporting

The membership dashboard answers how big the organization is and where it is heading:

• New members over a chosen period
• Active and inactive members
• Paying members
• Signups and exits
• Breakdown by fee type and user type
• Age distribution

Revenue is tracked across every income stream in the platform:

• Total revenue
• Recurring revenue
• Donation revenue
• Per-campaign and per-event revenue

Charts run over custom time spans, so a fiscal year that does not match the calendar year still works.

Engagement covers what members actually do on the platform: logins, emails sent, discussions, posts, comments, reactions, newsletter subscribers, and top event attendees, over the period you choose.

Member distribution renders on a map by country, county, and town. Custom map polygons are available where an organization's own districts do not match administrative boundaries.

Leaderboards rank members by activity and can be shown to members, not only admins:

• Most events attended
• Most posts
• Most reactions received
• Most points, where gamification is enabled
• Top referrers, all-time, monthly, or weekly

Membership, financial, geographic, and leaderboard views all carry a chapter filter. National admins switch between the aggregate picture and a single chapter without leaving the dashboard.

Chapter admins see the same dashboards restricted to their own chapter's data: membership growth, fees paid and unpaid, recurring revenue, and donations for their chapter only.

Permissions have an optional middle level, a parent chapter that groups several chapters into a region, district, or state. An admin at that level sees the aggregate for every chapter beneath them.

Because every metric carries a chapter dimension, comparisons come out of the same data: active members by chapter, fee payment status by chapter, signups per chapter over a period. Active members by chapter is one of the standard saved reports.

Describe the report you need once and it is built as a stored query. Opening it re-runs the query against live data, so the figures are current every time, and results export to CSV. Organizations use this for reports their previous system handled through saved searches.

Ask Orgo queries the whole database in plain language across contacts, members, events, and finance, for example the top 100 donors, or members who have not posted in six months. Results can be saved as a reusable report or turned into a newsletter segment.

Ask Orgo runs without sending your data to external LLM providers.

The member list itself is a reporting tool. Filter by fee paid or unpaid, due date, fee type, and chapter, then export the result to Excel or CSV without building a report at all.

A chapter admin running a query or an Ask Orgo question gets results limited to their own chapter's members. The same report definition returns different rows depending on who opens it.

Events and activity across a chosen period aggregate into a single annual report that renders as a PDF. The KPIs it contains are configurable, so the report matches the criteria your funder or supervising body asks for.

Statistical reports covering event types and age groups are configurable per market. Youth organizations that report yearly activity figures to a ministry of education fill the data in on each event and generate the combined report at year end.

Each event carries the fields the report later needs:

• Event type, used for reporting categories
• Group or chapter assignment
• Attendance, recorded by QR check-in or manually
• Custom columns from the registration form
• AI-assigned Sustainable Development Goal tags, for impact reporting

Each analytics module can be made visible to all members rather than admins only. Orgo began as a transparency request from members of an association who wanted equal access to the organization's own numbers.

Each event has its own analytics: total revenue, RSVP statuses, and an attendee table with filters, custom columns drawn from the registration form, and CSV export. A member's profile shows every event they have attended.

Every campaign reports delivery and response:

• Delivered, opened, clicked, including the top-clicked links
• Bounced, unsubscribed, and spam complaints
• Drill-down to individual recipients
• Resend to non-openers

Organizations that currently get these figures back from an external mailing supplier keep them in-house instead.

Donation campaigns report total raised, the recurring against one-time split, and revenue charts by period. The A/B testing engine on suggested donation amounts reports per-variant statistics, including average donation and donation count.

The learning module lists enrolled members with enrollment dates and progress, and exports the list to CSV.

Badge analytics cover usage organization-wide and per chapter, completed against pending awards, and per-badge performance. Manual badge assignment keeps a full audit trail of who awarded what and when.

Export is available module by module rather than only from a central screen:

• Members and contacts, filtered as you like
• Payments and financial transactions for a period
• Event attendance, with registration form columns
• Course enrollments
• Vote collection results
• Saved query results

The REST API covers nearly the whole platform. Create a read-only token scoped for reporting, point your BI or dashboarding tool at it, and keep visualization wherever your organization already does it.

Complete export is available at any time: CSV per module, optional scheduled database dumps, and full API access. Data is never sold to third parties and there is no contractual lock-in.

Invoices, membership certificates, adhesion documents, and the annual report generate as PDFs and attach to the member record, so financial and governance paperwork does not need a separate system.

Every admin role is scoped to one of three levels:

• The whole organization
• A parent chapter, meaning a region, district, or state
• A single chapter

Analytics, queries, and exports all respect that scope automatically.

Access is set separately for each analytics module, so you can give a treasurer the financial dashboard, a communications manager the engagement dashboard, and a membership officer the membership dashboard without opening all three to everyone.

Audit logs record who generated or downloaded which report, when, and from which IP address, whether it came from a saved query or from Ask Orgo. Exports are logged the same way, and large exports of sensitive data trigger a warning prompt.

Admins can view the platform exactly as a given member or permission level sees it, which is the quickest way to confirm a chapter leader sees their own chapter's figures and nothing more.