Multi-Location Childcare Enrollment Reports: Define the Counts
- Separate bookings, unique children and scheduled attendance.
- Use one reporting time and shared status definitions across locations.
- Keep unresolved matches visible and restrict identifiable working records.
A multi-location childcare enrollment report is useful only when every location counts the same thing. Start with a shared definition of child, booking, schedule and status before combining totals. Otherwise a part-time booking, a future start and a confirmed current place may all appear in a single misleading number.
Download the editable CSV worksheet.
This guide describes a reporting worksheet. It does not assume that your software combines separate accounts or that one account supports different program types.
Agree on a small data dictionary
Record these definitions at the top of the report and keep them unchanged during the reporting period.
| Field | Definition to agree | Common mismatch to resolve |
|---|---|---|
| Reporting time | Exact snapshot date, time and time zone | One location exports before the deadline and another after it |
| Child reference | Stable identifier used for reviewed matching | The same child has different local references |
| Location | Location attached to the reported booking | A transfer appears at both sites |
| Booking | One enrollment arrangement for a defined period and schedule | One child has several bookings |
| Confirmed | The specific approval event your program uses | An inquiry is counted as an accepted place |
| Active in period | Start and end dates overlap the defined reporting period | Future starts are included in current enrollment |
| Scheduled attendance | Days or sessions attached to the booking | A child count is treated as a daily headcount |
Use a separate label for inquiries, offered places, waitlist requests and confirmed bookings. Payment status can be a separate field; it should not silently redefine an enrollment status.
Show children and bookings separately
Consider this fictional snapshot. Location A has 30 confirmed bookings and Location B has 25. Each child has one booking at each location they attend. Three children attend both locations during the reporting period.
The organization has 55 confirmed bookings and 52 unique children: 30 + 25 − 3. Both numbers are correct, but they answer different questions. Neither establishes how many children will attend on a particular Tuesday or how many places you may legally offer.
If you cannot reliably match children across locations, report “unique children not reconciled” instead of presenting the sum of local child counts as an organization-wide unique count. Keep the bookings total available while the matching issue is resolved.
Reconcile transfers and dates
For a transfer, compare the original booking's end date with the new booking's start date. An overlap may be intentional or may be an unfinished change. Ask the responsible location to confirm it; do not automatically delete a record to make totals agree.
Keep an exceptions sheet with the reference, issue, owner, decision and review date. Useful exceptions include missing start dates, inconsistent statuses, unresolved child matches and canceled bookings still included in an active-period count.
Compare your final aggregate with each location's signed-off subtotal. Explain adjustments explicitly. A total that changes because of a corrected duplicate is different from a total that changes because a family enrolled.
Limit the report to its audience
A director reviewing totals usually does not need the full child record. Keep identifiable matching records restricted to the staff who need them, and share an aggregate version when that answers the question. The FTC's information-protection guidance recommends knowing what information you hold and limiting its collection, retention and access.
Do not use a broadly shared reporting spreadsheet to collect health details, passwords or payment-card information.
Turn definitions into a software requirement
Add the dictionary and fictional transfer example to your software requirements brief. Ask a vendor to demonstrate which counts are available, how locations are separated, what can be exported and who can access each view. Record anything that still requires a manual reconciliation.
The software selection guide provides a way to compare the result with your actual needs. For a preschool program, Bloomily's preschool overview is a starting point for that discussion; confirm your specific reporting arrangement before relying on it.