---
title: School rollups
category: reporting
order: 3
lastUpdated: 2026-06-08
featureAvailability: GA
planRequirements: [District]
roles: [district-admin]
navigationPath: Reports → School rollups
relatedArticles: [reporting/district-admin-quick-start, reporting/intervention-trends, reporting/exports]
---

## At a glance

- **Who uses it:** District administrators comparing schools within the district.
- **When to use it:** Monthly leadership meetings, end-of-quarter, board reporting.
- **Permissions required:** District administrator. Available on the District plan.
- **Navigation path:** Reports → School rollups.

## Purpose

School rollups aggregate case-load, intervention, and outcome data across every school in the district into a single comparable view. The defining feature is **normalization per 100 students**, so a 2,000-student high school and a 400-student elementary can be compared fairly.

## What you can see

- **Active caseload** per school, raw and per-100-students.
- **Open vs. closed** mix per school.
- **Average days to first intervention** after a referral is accepted.
- **Average days to closure** for cases closed in the window.
- **Intervention category mix** per school.
- **Outcome distribution** per school.

## Step-by-step

1. **Reports → School rollups**.
2. Choose a date range and, optionally, a comparison window (e.g. "this quarter vs. last quarter").
3. Use the **Per 100 students** toggle to normalize for school size.
4. Click any school row to drill into that school's view (the same data scoped to one school).

[SCREENSHOT: reports-school-rollups-table]
_Reports → School rollups table with Per 100 students enabled and three schools sorted by active caseload._

## Tips & best practices

- Always use the **Per 100 students** view for cross-school comparison — raw counts unfairly penalize large schools.
- Compare current window to the same window last year, not to the immediately prior window — case load is highly seasonal in K-12.
- Use the drill-down to validate outliers before raising them in leadership meetings.

## Common mistakes

- Treating "days to first intervention" as latency without context — schools intentionally observe before intervening; very low values can mean poor differentiation.
- Comparing schools that joined AmplifyED at different times in the school year.

## Related articles

- [District Administrator Quick Start](/help/reporting/district-admin-quick-start)
- [Intervention trends](/help/reporting/intervention-trends)
- [Exporting data](/help/reporting/exports)

## FAQ

**Can I add a custom column to this rollup?**
Saved views let you filter and reorder existing columns. Custom-computed columns are scoped during onboarding for districts that need them.

**Why are some schools missing?**
Schools with zero cases in the window are hidden by default; toggle **Show empty** in the toolbar to include them.