Module 3 · Reports
Reports
Five representative reports drawn from the production system's inventory of 125 Crystal Reports. The original Reports landing categorized output by audience and lifecycle stage. The demo surfaces three district-scoped reports (Annual Order detail, summary, and quarterly usage) plus two operational reports added in v0.2.0 (import feed status and exception queue summary).
- Workspace
- Admin (operational reporting) · School district (received reports)
- Primary task
- Generate read-only views of workspace state for board reporting, school district communication, and operational decision-making.
- Complexity hidden
- Real-time aggregation across the canonical workspace state, role-aware visibility, exception highlighting, and lifecycle staging across district reports, operational status, and co-op orders.
- In production
- The reporting layer comprised 125 distinct Crystal Reports across entitlement, allocation, payout, quarterly usage, and food processor / food distributor reporting surfaces.
- Demo simplification
- Five representative reports demonstrate the canonical workspace-to-report flow.
Pick a report to view
Choose a report from the categorized list on the left. Reports render from the canonical workspace; enter orders in Module 1 to see live data flow through these surfaces. Operational reports (import status, exception queue) reflect the multi-channel reporting ecosystem and are admin-facing.
Try this
Pick a report from the list to view how the canonical workspace state flows into a read-only report surface. Operational reports reflect the workspace at a suite-level scope; district reports apply to the active district above.