Per-pupil spending by school, explained.

What the field means

Per-pupil spending is a finance context field. In K12 Atlas, it is attached to school profiles from district finance data. That means it helps describe the funding environment around a school, but it should not be read as the exact budget spent inside one campus.

This distinction matters. A district may centralize services, operate specialized programs, or allocate costs in ways that do not map neatly to a single building.

Before you compare schools

• Check the source year. K12 Atlas uses Census F-33 FY 2022 for this finance field.
• Compare within states carefully because finance systems and cost structures vary.
• Remember that district values can appear on multiple school profiles in the same district.
• Use medians and distributions for context instead of reading one number alone.

Reading example

If a district reports $18,000 per pupil, that value can be attached to schools in that district as finance context. It does not mean every campus received exactly $18,000 per student in campus-controlled spending.

The value is still useful. Researchers can use it to compare finance environments. Journalists can use it to add context. Product teams can use it as a sourced field alongside enrollment, staffing, and district metadata.

What the data cannot say

The field cannot prove campus-level spending, classroom-level resources, or program effectiveness. It also should not be used as a standalone explanation for outcomes. It is one finance input in a broader school-data profile.

How K12 Atlas uses it

K12 Atlas exposes the field with source and vintage context so users can decide how to use it. The goal is not to simplify finance into a label. The goal is to make the finance signal available, documented, and joinable.

The source-backed page

The matching data story is /data/school-spending. It includes coverage counts, state context, a CSV slice, methodology notes, and Dataset JSON-LD.

Practical use cases

For journalists, the field can support a narrow reported-fact sentence with a source note. For researchers, it can become a filter, denominator, or join key. For product teams, it can enrich a school profile as long as the interface keeps the vintage and source visible. For real-estate-adjacent workflows, the language should stay neutral: provide cited facts and let the client evaluate them independently.

Refresh and maintenance

This page should be refreshed when K12 Atlas cuts a new release. The number, source year, CSV slice, sitemap date, and schema date should move together. If a source changes definition or coverage, the page should say that plainly instead of preserving an older claim for search traffic.