Managing Multiple Sites: What Nursery Groups Get Wrong (and How to Fix It)
The economics of running a nursery group look attractive on paper: shared management overhead, bulk purchasing, cross-site staffing flexibility, a stronger brand, and negotiating power with local authorities. In practice, many nursery group managers find that their admin scales faster than their efficiency.
The root cause is almost always the same: systems and processes that work for a single site become unwieldy at two, and unmanageable at five.
The common failure modes
Disconnected data
In a multi-site group where each nursery uses its own spreadsheets, paper registers, and filing cabinets, the group manager has no way to see the overall picture without physically visiting each site or waiting for reports to be compiled manually. You can't spot a staffing problem at Site 3 until it's already critical. You can't compare occupancy across sites in real time. You can't see that a child who also attends Site 2 has an updated medical record.
Duplicated admin work
If each site manager is doing the same admin tasks independently — preparing funding claims, chasing parental declarations, maintaining DBS logs — you're paying for the same work to be done multiple times. In a group of five sites, that's a significant overhead.
Inconsistent practice
Without a shared system, each site develops its own way of recording observations, logging incidents, communicating with parents, and managing registers. This makes group-level reporting almost impossible and creates compliance risk if one site's practice falls below standard.
Visibility without control
Group managers often describe having too little visibility and too little control. Not enough to see problems early; not enough leverage to fix them quickly.
What good multi-site management looks like
A single system with site-level configuration
The most important structural change a nursery group can make is moving to a single management platform across all sites, with appropriate site-level customisation. This means:
- Group managers can see occupancy, attendance, and funding data across all sites in one view
- Each site manager retains control of their day-to-day operations and their site's specific configuration
- Reporting is consistent, because everyone is recording the same things in the same way
- When a child moves between sites, their record moves with them
Centralised admin with distributed delivery
Many admin tasks that are currently duplicated at every site can be centralised: payroll coordination, funding claim review, DBS administration, curriculum documentation. The delivery of care stays local; the overhead stays central.
Consistent parent communication
In a group, parents need to trust the brand, not just their individual site. A consistent parent communication channel — the same app, the same look and feel, the same processes — builds brand confidence even when families have limited interaction with head office.
Cross-site staffing flexibility
A shared staffing pool only works when ratios and availability are visible across sites in real time. If you're coordinating cover by phone call and text message, you're leaving efficiency on the table. A shared rota and attendance system that flags ratio issues at any site — and shows who's available from other sites — makes cross-site flexibility practical.
The conversation about standardisation
Moving a group to a shared system requires some standardisation of process, and that conversation can be hard. Site managers who have run their settings independently for years may resist what feels like the imposition of a central system on their professional practice.
The framing matters. This isn't about removing site manager autonomy — it's about removing the duplication and inconsistency that makes everyone's job harder. The site manager at Site 1 doesn't lose the ability to make judgements about her room; she gains a system that means she's not also doing the group's funding admin every term.
Implementation: managing the transition
For groups moving from disparate systems to a shared platform:
Start with one site: Implement the shared platform at one site first — ideally a site where the manager is enthusiastic and the team is receptive. Use the learnings to refine the rollout approach before scaling.
Run in parallel briefly: For the first half term, keep legacy systems running in parallel at newly onboarded sites. This provides a safety net and builds confidence. After that, retire the legacy systems — running parallel indefinitely removes the incentive to properly adopt the new one.
Define the data standards: Before you onboard multiple sites, agree on how you'll record key information — room names, session types, funded hours categories. Inconsistency at this level makes group-level reporting much harder.
Invest in site manager buy-in: The group's system will only work if site managers use it properly. Their buy-in is worth significant investment in training, in having their concerns heard, and in visible support from group leadership.
Early Tree is designed for single settings and groups alike. Group administrators get a cross-site view of everything that matters; site managers get a system that makes their daily operations faster and cleaner. We're currently expanding to 50+ new settings and groups.