← All features

Governance · Reports & Exports

The packet your board wanted — already written.

Save your AAA Q3 packet, your city contract report, your monthly board summary, your year-end giving statement. Run them on a schedule or one click before the meeting.

What it does

The capabilities that earn this module's place.

Report packets

The saved format your funder actually wants.

Each funder, board, or commission has their own format — different sections, different breakdowns, different summary tables. Save the format once; run it every quarter or every month. The AAA Q3 packet, the United Way grant report, the city contract performance review, the monthly board packet — all configured to look exactly like what your reviewers expect.

  • Per-funder packet templates
  • Custom sections and breakdowns
  • Saved layouts and cover pages

Scheduled runs

Friday at 9 AM. PDF in your inbox.

Each packet runs on the schedule you set — quarterly for the AAA report, monthly for the board summary, annually for the audit packet. The PDF generates from the current data, lands in the configured inbox, and posts to your shared drive if you want. No manual reminders, no last-minute scramble.

  • Quarterly, monthly, weekly schedules
  • Multi-recipient delivery
  • Optional shared-drive deposit

Custom report builder

Pull the numbers your specific question needs.

Build ad-hoc reports across any module — "members who attended at least one program in Q3 and live in zip codes starting with 9" or "volunteers who logged more than 50 hours and haven't been to the gala in three years." Save the query if you want to run it again; export to PDF or CSV.

  • Cross-module ad-hoc queries
  • Save queries for reuse
  • PDF and CSV exports

Demographic & equity breakdowns

The numbers your funders are starting to ask for.

Demographic breakdowns — age, race, income tier (for scholarship reporting), residency, mobility, language preference. Equity-focused reports for funders increasingly require this; the same data your team is already collecting at registration generates the breakdown automatically. PII handled per your privacy policy.

  • Per-program demographic breakdowns
  • Scholarship and equity tracking
  • Privacy-aware aggregation

A workflow walkthrough

Building the Q3 packet, once.

The first time a director configures her AAA Q3 packet, then runs it every quarter for the next five years without re-doing the work.

  1. Week 1 — Director maps her requirements. She lists what the AAA Q3 packet needs: total congregate meals served (by demographic), total service hours (by program category), transportation logs (by trip type), program participation (by zip code), scholarship counts.

  2. Week 1 — Packet configured. She builds the packet in the report builder — adds each section, picks the breakdown for each, sets the layout, drops in the cover page. Saves it as "AAA Q3 Packet — [your AAA name]." The packet now runs on demand or on schedule.

  3. Week 1 — Scheduled. She schedules the packet to run on the 15th of October, January, April, and July — five days before each AAA submission deadline. Recipient list: her own email, the deputy director, the auditor on file.

  4. October 15, Year 1 — First scheduled run. 8 AM, the packet runs. PDF lands in three inboxes by 8:01. She reviews on her morning coffee, makes one small note for the cover letter, hits send to the AAA at 9. Done.

  5. Year 3 — Packet still running. Twelve quarters later, the same packet still runs. New funder requirement comes in (now they want a language-preference breakdown); she adds the section in three minutes. Every quarter since: zero compilation work.

Questions, answered

What we hear before customers sign up.

See reports run for your board.

Set up your workspace this morning. Configure your first packet this afternoon. Schedule it to run the day before your next board meeting — and watch the spreadsheet retire.

14 days free · Card required · Cancel anytime