Custom Reports
Feature Detail
Description
Custom Reports allows Org Admins and Coordinators to build ad-hoc reports by selecting dimensions, filters, and groupings from available activity data beyond what Team Reports and Bufdir report templates provide. The report builder exposes configurable parameters including date ranges, activity types, contact categories, and peer mentor groupings. Generated reports can be saved as reusable templates and exported as CSV or XLSX, addressing advanced analytical needs that vary by organization structure and cannot be anticipated in a fixed report schema.
Sources & reasoning
Custom Reports does not appear explicitly in the phase roadmap prose, but blueprint assigns [v1.1], mapping to Phase 3 by ordinal (third phase = v1.1). NHF's 1,400-chapter hierarchy and HLF's Dynamics integration both motivate flexible report shaping that fixed templates cannot satisfy. Placement in v1.1 is correct because standard Team Reports and Bufdir export cover all compliance requirements earlier, and custom reporting adds analytical depth once core operations are proven stable.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Organizations with complex internal structures need analytical flexibility beyond fixed templates. NHF spans 12 national associations, 9 regions, and 1,400 local chapters and must be able to slice activity data by organizational level to verify reporting completeness. HLF's integration with a Dynamics portal means exported data must sometimes match shapes that differ from standard Bufdir output. Custom Reports enables power users to answer organization-specific analytical questions and produce custom-shaped exports without requiring developer involvement. Deferring to v1.1 is appropriate because standard Team Reports and Bufdir export satisfy all grant-compliance obligations at launch; custom reporting adds analytical value once core operations are stable.
The report builder is a Next.js client-side component that constructs parameterized queries against PostgreSQL via the Admin Web Portal REST API. Available dimensions and aggregation metrics are defined server-side in a report schema registry, preventing exposure of internal table structures while still allowing flexible grouping. All queries carry strict tenant-scoped WHERE clauses; the builder never exposes raw SQL to users. Report templates are persisted to the reports table keyed to the generating user's organization. CSV and XLSX export use server-side streaming to handle large result sets. The filter and dimension selection UI must meet WCAG 2.2 AA keyboard navigation and contrast requirements throughout.
Components (47)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.