FlowsBook a callSign inCreate free accountSign up
Population and demographics

Population data for planning school and nursery places

How planners and school groups use children per small area to see where places will be short: which age bands to read, how to set them against seats, and the limits.

Part of the guide Location intelligence automation

By the xMap team · · 4 min read

To plan school and nursery places with population data, count the children who live within a reasonable journey of each school, compare that count with the seats the school has, and look at the younger age band too, because today's under-tens are the next decade's secondary pupils. Small areas where children far outnumber nearby seats are where new classrooms, a new nursery or a bus route are needed first.

This article is for education departments, school groups, nursery chains and the people who advise them. It explains which figures to use, how to set them against your own list of schools, a made-up example in Lyon, the limits of the data, and how an AI employee can redo the count each term.

The figures you need

Two sources meet in this work. The first is where children live. The Demographics block reads xMap's population grid of small hexagons, each about 0.1 km², and gives residents in nine age groups, including 0 to 9 and 10 to 19. The second is where places are, and how many: the schools and nurseries themselves with their capacity, which usually comes from your own records rather than from any map.

Reading the age bands for planning

  • 0 to 9: the pressure on nurseries, kindergartens and primary schools now, and a look ahead at primary demand over the next few years.
  • 10 to 19: the pressure on secondary schools and colleges now. A district heavy in 0 to 9 and light in 10 to 19 will need secondary places as its children grow.
  • Share of children: children as a share of all residents shows family areas, which helps decide where a new school will fill fastest.

Population grids describe where people live at one point in time. They do not forecast births or new housing, so any look ahead is an ageing of today's children, not a projection. Add known housing developments from your own planning team by hand.

Setting children against seats

  1. Make a table of your schools or nurseries with their position and number of places.
  2. For each, count children of the right age within the distance families travel: a walk of about 1 km for primary pupils in a dense city, a longer drive in a suburb or the countryside.
  3. Divide children by places to get children per seat around each school.
  4. Map the hexagons with many children and no school within reach. Those are gaps that a per-school ratio misses, because no school sits there to have a ratio.

A worked example in Lyon

A made-up case; the schools and numbers are invented. A group running four private bilingual primary schools in Lyon wants to know which one to expand and whether to open a fifth.

SchoolPlacesChildren 0 to 9 within 1.5 kmChildren per place
North2202,900about 13
Centre3102,400about 8
East1804,100about 23
South2502,200about 9

Invented figures to show the method.

East is under the most pressure and its waiting list confirms it, so the extension goes there. The hexagon map also shows a cluster of family streets about 3 km west of Centre with no school of the group within reach. That becomes the brief for a fifth site, to be checked against the public and private schools already serving it.

Limits to keep in mind

  • Residents, not pupils. Some children attend schools far from home, or school at home. Enrolment records tell you that, the grid does not.
  • No private or public split. The grid counts children, not which kind of school they go to.
  • A snapshot. New housing estates appear on the grid only after people move in.
  • Ten-year bands. For nursery planning the 0 to 9 band mixes toddlers with older children.

Doing it with an AI employee

An AI employee in xMap Flows can rerun the count every term and send the table and map. One way to build it:

  1. Schedule: on the first Monday of each term, or monthly.
  2. My data: your schools or nurseries with their places.
  3. Demographics: each incoming place, within the distance you choose, with the age groups.
  4. Calculated field: children_per_place = age_0_9 / places (or the 10 to 19 band for secondary schools).
  5. Sort and limit: highest pressure first.
  6. Make a report as a PDF for the board, or Email with a map.

What lands in the inbox is one row per school with its places, the children around it, children per place and the share of children in the area, ranked, with a map. For the gaps between schools, a second flow with an Area of interest over the city and Demographics set to give every hexagon produces a heat map of children. The templates Children per school, block by block, Where to open a nursery and Where families need after-school activities are ready starts.

Questions

Can population data predict how many pupils a school will have next year?

Not on its own. It shows how many children live nearby today, by age band. Enrolment history and planned housing are needed for a forecast.

Why are the figures given for hexagons?

Hexagons of about 0.1 km² are small enough to show one estate or a few streets, and they fit together without gaps, so totals for any area can be added up from them.

Is this available for schools in the United States or United Kingdom?

Not yet: population figures are not available there. In those countries, schools and nurseries can still be counted and mapped against each other.

Can I separate under-fives for nursery planning?

No. The youngest band is 0 to 9. Read it as a sign of young families and check local birth registrations where they are published.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.