Workstream note: This is a reporting and consumption workstream under the Data Visibility umbrella initiative. See Data Visibility for the broader foundation, standardization, and consumption strategy.
Why this exists
Operational teams need reports that stay accurate without constant manual pulls. The portal workstream formalizes the reporting lifecycle so data products have clear owners, refresh cadence, validation rules, and visible quality signals.
March 2026 Registry Reconciliation
The enriched BOUSD registry made this workstream more concrete:
- recurring Google-based extract jobs are now documented as one production family instead of a scattered set of repo references;
- report families such as attendance, PADC, enrollment planning, and staff-device readiness are now linked more explicitly to the portal model;
- the biggest remaining gap is still the formal report registry with owner, backup owner, cadence, access rules, and freshness conventions.
Measures of success
- Reports have defined owners, backup owners, refresh cadence, and validation checks.
- Staff access trusted reporting without repeated manual requests.
- Report definitions stay aligned with canonical datasets and standardized metric definitions.
- Data quality issues surface quickly with clear remediation steps.
Active projects
- Perpetual Data Reports Portal
- Aeries-to-Google Sheets Reporting Extract Family
- BOUSD-MonthlyAttendance-Dashboard
- BOUSD-PADC-Extract
- BOUSD-Staff-Technology-Dashboard
- Staff Device Refresh Operations Portal
Key risks
- Stale extract feeds erode trust and lead teams back to manual pulls.
- Report ownership lapses as priorities shift.
- Access controls drift from privacy requirements.
- The formal report registry remains incomplete even though multiple live report families depend on it.