Dashboards & Reporting Explanation

Introduction#

Altrinum gives tenant teams two complementary ways to understand what is happening across their work:

• a shared dashboard for day-to-day visibility and comparison
• dedicated reporting pages for exact operational, finance, compliance, and email review work

This distinction matters because most nonprofit teams do not all ask the same question at the same time.

A leadership team may want a quick picture of fundraising momentum, event activity, and campaign performance across the organization. A finance or operations team may need a very specific export tied to a reporting period, tax treatment, receipting review, or campaign health issue. Both needs are valid, but they are not the same job.

Altrinum is designed to support both.

Why dashboards and reports are separate#

A dashboard is best when the goal is to understand the shape of activity.

A report is best when the goal is to produce an exact answer.

That may sound simple, but it is one of the most important reporting concepts for staff to understand. Teams often lose time when they try to use a dashboard like an export tool or treat a detailed report like an executive summary.

A dashboard helps people ask questions such as:

• Are donations trending up or down this month?
• Which area of work seems most active right now?
• Is a campaign generating engagement but not conversions?
• Are events, programs, and giving activity telling the same story?

A dedicated reporting page helps answer different questions, such as:

• Which registrations included tax-collected activity for a specific event?
• Which gifts or receipts need compliance review?
• How did a specific group of email campaigns perform over a time window?
• Are there audience health problems that could affect sends?

The dashboard supports awareness and comparison. Reporting pages support exact follow-up.

The dashboard is for shared visibility#

The dashboard is designed as a shared operating view.

Because multiple widgets respond to the same filter set, teams can compare activity across modules without jumping between unrelated screens. This is especially useful when people from different roles need to look at the same period and discuss what happened.

For example, a tenant team might use the dashboard to ask:

• Did event activity and giving move together this quarter?
• Did email performance improve during the same period as donation growth?
• Which tracking sources produced meaningful action?
• Which event, program, or giving form drove the most visible momentum?

This shared filter model is important because it helps teams stay oriented around one reporting window instead of comparing disconnected numbers from different screens.

Reporting pages are for exact follow-up work#

Dedicated reporting pages exist because some work cannot stop at a summary widget.

A finance lead does not usually need a broad KPI overview if the real task is tax review, receipting validation, or reconciliation. An email manager does not always need cross-module comparison if the real task is understanding campaign performance or audience health before the next send.

That is why Altrinum can include dedicated pages such as:

• Email Performance
• Email Audience Health
• Event Tax Report
• Receipting Compliance Report

Each one exists because the follow-up task is narrower and more exact than a dashboard summary.

This reflects real nonprofit work patterns#

In many nonprofits, the same underlying activity is viewed through different lenses by different teams.

For example:

• development may care about campaign momentum and donor response
• events staff may care about registrations, capacity, tax handling, or attendance
• program staff may care about participation patterns
• finance may care about receipting and compliance detail
• leadership may care about the overall picture and whether strategy is working

The dashboard supports the shared conversation across those roles.

Dedicated reporting pages support the precise work that comes after the conversation.

This separation is healthy. It lets teams start together, then move into role-specific follow-up without losing context.

How shared filters change interpretation#

One of the most important things to understand about dashboards is that numbers do not mean much unless staff know the active filter scope.

The dashboard may allow teams to change:

• reporting period
• date range
• source inclusion
• drill-down scope such as event, program, giving form, or designation
• attribution or tracking-related filters

Because of that, the same widget can look very different depending on the selected scope.

A surprising trend does not always mean the business changed. Sometimes it means the team is looking at a different period, a narrower source set, or one filtered entity instead of the full tenant view.

This is why good reporting habits matter just as much as good data.

When to stay in the dashboard#

Stay in the dashboard when you are still trying to understand the shape of activity.

This is usually the best choice when:

• you want a fast overview
• you are comparing multiple modules at once
• you are preparing for a leadership or team check-in
• you are trying to spot patterns before deciding what to investigate
• a chart or KPI is enough to answer the question

A dashboard is often the right first stop because it helps staff discover what deserves a closer look.

When to move into a dedicated report#

Move into a dedicated reporting page when the work requires exactness.

This is usually the best choice when:

• you need an export file
• the task is finance- or compliance-related
• the question is specific rather than exploratory
• staff need record-level review instead of summary widgets
• the output needs to support an operational process outside the dashboard

In other words, use the dashboard to identify and frame the question. Use dedicated reports to finish the job.

A practical reporting mindset for teams#

A healthy reporting rhythm often looks like this:

1. Start broad in the dashboard.
2. Confirm the reporting window and scope.
3. Look for meaningful changes, patterns, or outliers.
4. Narrow to one event, program, giving form, or source if needed.
5. Move into a dedicated report when detail or export becomes necessary.

That approach helps reduce common mistakes, such as exporting too early, comparing mismatched scopes, or skipping the broader context behind a narrow report.

Tips and notes#

Note: Widget visibility may depend on enabled modules and available data within the tenant.

Example: A school advancement office might use the dashboard to compare a spring gala, a scholarship appeal, and recent email performance, then open Receipting Compliance Report for finance-specific follow-up tied to the same reporting window.