FIGR / UI TEMPLATE

Event Fundraising

Run fundraising events with registrations, donations, sponsorships, peer fundraisers, auctions, check-in, live totals, and post-event reconciliation.

This analytics reference covers nonprofit & fundraising. Its sample screen includes Ticket revenue and Live auction and the Add fundraiser action. Adapt its workflow to your product and design system.

Event Fundraising

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Analytics

Primary action

Add fundraiser

Pattern

Event Fundraising analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The event fundraising screen supports “Add fundraiser” while keeping overview and attendees in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Add fundraiser
  • Main area: Overview brings the user to the relevant workflow
  • Related area: Attendees keeps nearby context accessible
  • Raised: 3.8M in the sample screen
  • Attendees: 612 in the sample screen
  • Example 1: Ticket revenue
  • Example 2: Live auction
  • Input: Event date

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Keep chart labels and time range visible while metrics refresh
  • Empty: Explain the chosen date range or filter has no data
  • Error: Identify missing or stale metric sources without implying zero activity
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Add fundraiser and say what happens next

Where it fits

Overview → Attendees → Add fundraiser → Review result

Patterns in this screen

Event Fundraising analytics, Overview, Attendees, permission handling, error recovery

UX choices to review

Keep metric definitions, chart periods, and filter context visible together

In this example, Ticket revenue is one of the records worth checking. Keep the sample data clearly separate from a live system.

Show why numbers changed; distinguish delayed data from genuine zero values

Make a useful drill-down available before teams export or share findings

Try a similar screen in Figr

Design a event fundraising screen for an existing nonprofit & fundraising product. Use our actual design system, components, and content rules. Cover Overview and Attendees, include believable records such as Ticket revenue, and make "Add fundraiser" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗