What is a school feeder pattern?

What a feeder pattern means

A feeder pattern is a directional relationship between schools. It usually describes how students move from one level to the next, such as an elementary school feeding a middle school, or a middle school feeding a high school.

The important word is directional. A feeder row is not just two schools in the same district. It says one school is upstream and another school is downstream in the student pathway.

How to read it

• Confirm the origin school and destination school. Reversing the direction changes the meaning.
• Check the method. K12 Atlas separates stronger SABS-derived relationships from district-level fallback relationships.
• Use grade span and school type to understand whether the path is plausible.
• Do not use feeder rows as housing guidance. They are education-data relationships, not a location recommendation.

Reading example

A row may show Elementary A to Middle B with a feeder method and district context. That row can help a researcher model pathway coverage or help a newsroom explain district structure. It does not mean every student at Elementary A will attend Middle B.

Boundary changes, open enrollment, magnets, charters, special programs, and family choice can all change the real student path. The feeder field is best used as structured context, not as a guarantee.

What the data cannot say

Feeder data does not prove individual attendance. It does not replace district boundary files or enrollment policy. It also does not explain family decisions or program admissions. It is a structured map of likely school relationships built from available public data.

How K12 Atlas uses it

K12 Atlas treats feeder patterns as a graph layer. Each row is kept with method context so downstream users can decide how strict they need to be. A policy analyst may filter to exact relationships; a product team may use broader fallback coverage for discovery and then display method labels.

The source-backed page

The matching data story is /data/feeder-patterns. It includes counts, methodology, a CSV slice, 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.