← All features

Governance · Reports & Exports

The board asks in October. You answer in October.

Every check-in, registration, payment, meal, ride, and volunteer hour your team records is already a row in a report. You pick the question and the date range.

What it helps with

What your team can do here.

Funder packets

The AAA quarterly, already assembled.

Four packets ship built: the AAA quarterly bundle, a United Way report, a monthly board summary, and a year-end audit set. Each one is the reports that funder asks for, in the order they ask for them, over the period they ask about. Open it, check it, export it. If yours is close but not quite, save a copy and change what is different.

  • AAA quarterly: Title III meals, rides by purpose, volunteer hours, units of service
  • Save a copy of any packet and edit the reports inside it
  • Build your own packet from any reports in the catalog

Saved views

Build it once in October. Run it in January.

Filters, date range, breakdown, and columns save together as a view with a name on it. Next quarter you open the view rather than remembering which four filters you set at eleven at night. Nothing is emailed on a schedule, so someone still has to press the button, and that person is also the one who looks at the numbers before they leave the building.

  • Save a report's filters and breakdown under a name
  • Group saved views into a package you run as a unit
  • Reports are run on demand, not mailed out automatically

The catalog

Two hundred reports, before you build anything.

Attendance depth, retention, no-show rates, revenue by method, aging, meal counts against Title III eligibility, rides by purpose, room utilization, volunteer hours and their dollar value, data-quality gaps in your own records. Every one takes a date range and a center. Compare this quarter against last and you get the change and the percentage beside it.

  • Filter by date range, center, program, and member audience
  • Period-over-period scorecards with the change spelled out
  • PDF, Excel, or CSV, and every export is logged

Breakdowns

The same report, split by who came.

Take any member-based report and break it out by race, gender, ethnicity, age band, or center. It re-runs once per group and stacks the subtotals underneath, including a Not recorded row, because leaving that row out is how a report quietly flatters itself. Which fields you collect is your decision and your legal ground to stand on. NestPoint aggregates what is there.

  • Break any member report out by demographic field or center
  • A Not recorded bucket, always shown, never folded into the rest
  • Narrow a report to a member audience the same way you build a mailing list

A typical workflow

The number exists before anyone asks for it.

Nothing here is re-entered for the report. It was recorded when it happened, by whoever was standing there.

  1. Pick the report. Start from the catalog or from the packet your funder already asks for.

  2. Set the window. A date range, a center, and if you need it, the group of members the question is about.

  3. Break it out. Split it by program, by center, or by a demographic field you collect.

  4. Read it before you send it. Check the totals and the Not recorded row against what you know about your own year.

  5. Save the view. Name it, and next quarter is opening a saved view instead of rebuilding it.

Common questions

What teams ask before getting started.

The number, and where it came from.

See which records a board or funder figure is built from, and how the export gets made without a weekend attached.

Card required. Cancel anytime.