A childcare management app is three records: who is here, who is watching, who took them home.
Almost every feature anyone asks for in a childcare management app collapses into three questions an inspector can ask without warning. Which children are in the building right now. Which adult is responsible for each of them. Who signed them out, and when. Get those three right and the rest of the software is convenience. Get them wrong and the centre has a finding on its file. This is the operations layer under the wider family of childcare apps.
The same thing is called a daycare management app in one country and a nursery management app in another, and the records underneath are the same four: children, rooms, adults and time. This page covers the ratio rule your rooms have to obey, the sign in and out record and its named fields, what a child record really carries, and where a bought platform stops fitting one centre.
See how a room breaks ratioThe short version
Ratios are set by state rule, and the youngest child in the room sets them.
Staff to child ratios and maximum group sizes are written into state regulation, they differ by state, and they step with the age of the children. New York requires 1:4 with a group of no more than 8 from six weeks to 18 months, and 1:7 with a group of no more than 18 at three years. Texas publishes its own chart. Any tool with one set of numbers baked in is wrong somewhere.
Two things follow for the build. The ratio cannot live on the room, because the youngest child present can change it. And headcount alone never answers the question, because the group size cap applies whatever the staffing is.
The ratio rule your rooms have to obey
Every state regulates how many children one adult may supervise, and the numbers are not close enough to guess at. Check your own licensing rule rather than a blog post. New York is a fair example of the shape. Its rule for child day care centres sets 1:3 with a maximum group of 6 for children under six weeks, and that care is only permitted under section 418-1.15(b)(30) of the same subpart. Then 1:4 with a group of 8 from six weeks to 18 months, 1:5 with a group of 12 from 18 to 36 months, 1:7 with a group of 18 at three years, 1:8 with a group of 21 at four, and 1:9 with a group of 24 at five.
Notice that every line carries two numbers, not one. The ratio says how many adults the room needs. The maximum group size caps the room however it is staffed. Nine infants with three teachers satisfies 1:4 and still breaks a group size of 8. An app that only divides children by adults will paint that room green.
The third trap is the mixed age room. New York provides that where children are grouped across ages, in the circumstances the rule describes, the ratio and maximum group size for the youngest child in the group must be followed. So the app cannot store a ratio on a room record. It has to work the ratio out from the children who are in that room at this minute, which means it needs their dates of birth and not just a count.
Ratio is also a moving number. It changes at every drop off, every collection, every break a teacher takes, every time a room combines at the end of the day. A figure that was right at nine in the morning tells a manager very little about half past four, which is exactly when rooms merge and staff go home.
18 NYCRR 418-1.8, supervision of children in child day care centers
Try it
What one room needs right now
New York numbers, one room. The youngest child present sets the ratio and the group size cap for everyone in it.
Short by 1
12 children in the room. The youngest band present is 18 to 36 months, so 1:5 applies to the whole group and 3 adults are required. Group size is inside the cap of 12 for that band.
Sign in and sign out is a legal record
Texas writes the attendance table straight into the rule. A child care centre must have a tracking system for each child coming and going throughout the day, and the system must include the name of each child, the date, the time of arrival, the time of departure, and the initials or other unique identifier code of the employee or parent. That is a schema, published by a regulator, and it tells you the record is per event and not per day.
The same rule says all caregivers must have access to the tracking system, so they can tell which children are in care during their shift, at changes of caregiver, and during emergency evacuations. That last word is the real design constraint. The roll has to be readable on a phone in a car park, with no signal and no login screen in the way.
This is where the obvious build fails. A tablet at the door with a parent code is easy, and if the roll only exists on that tablet then the roll is still in the building. The record has to reach every staff device and render from local storage. A paper binder that someone carries out beats a well designed app that needs a network, and any honest plan starts by admitting that.
Attendance is also what the money gets counted against. Where a centre holds funded or subsidised places, the hours claimed have to line up with the hours recorded, which is a different report with a different shape and often belongs next to a childcare vouchers app rather than inside the daily roll. Keep the raw events, generate both views from them, and never let a claim edit the attendance record.
26 Tex. Admin. Code 746.631, signing children in and out of care
What a child record actually carries
Ask a manager what the app has to hold about one child and the list runs well past a name and a birthday. Authorised collectors and their relationship. Anyone who must not collect. Allergies and what to do about them. Medication with dose, times and written consent. Immunisation status. A doctor, and two numbers that somebody answers. Sleep and feeding notes for infants. Photo permission. Who holds legal custody.
Two of those behave differently from the rest. Allergy and medication details are read in the room, at the moment food is served, so they belong on the screen a teacher already has open. Custody and do not collect are read at the door, in front of the person asking. Same record, two very different screens, and the design fails if either one is three taps deep.
Incidents deserve their own record and their own shape: what happened, when, where on the body, who saw it, what was done, who was told and when they signed. The temptation is to bolt this onto the daily note home. Resist it. An incident record is the one thing that gets read a year later by somebody who was not there, and it has to still make sense then.
The note home is a separate job with separate rules. It is closer to a parent teacher communication app than to the compliance side, and the two are worth keeping on different rails. A parent should not be able to scroll from this afternoon into an incident log, and a photo of painting should not become an audit artefact.
The two calendars that have to agree
A centre runs two schedules and ratio is where they meet. Children have session patterns: Monday, Wednesday and Friday mornings, alternate weeks, a short day on Thursday, three weeks off in August. Staff have shifts, breaks, training days and leave. Neither calendar is a grid, and the part people mean by a childcare centre admin app is mostly these two plus the money hanging off them.
Booked is not the same as present, and most tools only model one of them. Ratio is measured on the children in the room. Staffing is planned a week out on the children expected. An app that knows only the present tense cannot warn you that next Tuesday afternoon is one adult short. An app that knows only the plan will report compliance for a room that is over.
Birthdays are staffing events, because the bands step at fixed ages. A child turning 18 months can change what the room needs. Model room moves as dated transitions rather than a field on the child, or the first time you look back at a day in March the history will not reconstruct.
Billing rides on the same two calendars: sessions booked, sessions attended, late collections, closure days, sibling discounts. Most centres price by pattern rather than by the hour, which is the main reason generic invoicing tools fit this badly and why the finance screen is usually the one people rebuild first.
What each way of running a centre gives you
| Approach | Ratio by room, live | Sign in and out record | Fits your session patterns | Readable in an evacuation |
|---|---|---|---|---|
| Paper sheet at the door | No | Yes | Yes | if someone grabs it |
| Spreadsheet in the office | No | typed up later | Yes | No |
| Kiosk tablet at the door | headcount, not ratio | Yes | within its settings | No |
| Childcare platform, per child per month | Yes | Yes | within its presets | Yes |
| An app you build for your centre | Yes | Yes | Yes | Yes |
Building one around one centre
Childcare platforms exist, they are priced per child per month, and they are shaped around the average of thousands of centres. That works until yours does something ordinary the average does not: a two day pattern the billing screen cannot express, a room that combines ages after four o'clock, a second site with different opening hours, a sibling rule nobody else has. At that point you are running the centre around the software.
Newly is an AI app builder. You describe the app in plain English and it writes a real React Native and Expo project you own, running it on a cloud iPhone or Android simulator while it builds. It is $25 a month and there is no free plan. It is not childcare software: it does not arrive knowing your state ratios, you tell it what they are, and there are no built-in payments, so billing means an invoice or a payment link rather than a card form inside the app.
Getting it onto staff phones matters more here than in most categories, because the people who need it are not going to install a developer build. The Deploy tab has an Android section: one press builds, signs and uploads to Google Play internal testing, and it also produces a standalone release APK you can install on a phone directly. iOS goes through TestFlight and App Store Connect, which needs your own Apple Developer account. Before any of that, settle where the child and room records live, because attendance is the table you will query from every direction: by child, by room, by day and by member of staff.
Questions people ask about childcare management apps
It is the operational record for a nursery or daycare: who is enrolled, who is present, which room they are in, which adult is responsible, when they were signed out and by whom. Enrolment, billing, allergies, medication, incidents and notes home usually sit on top of that core. The compliance part is the part that has to be right.
Describe the rooms your centre actually runs
Write down the ratio your state sets, the session patterns you sell, and the names that must never appear on a collection list. Build the app around those three.
Start building