How to Manage Enrollment, Billing, and Parent Communication for Preschools

A preschool runs on three things: keeping the kids safe, keeping the parents informed, and getting the tuition paid. Software that automates two of those frees the director to actually walk the building — to spot the lead teacher who is burning out, the four-year-old who has not eaten lunch in three days, the bathroom that needs a deep clean before the licensing visit. Software that automates none of those turns the director into a part-time bookkeeper, a part-time enrollment counselor, and a full-time inbox janitor.

Most preschools run hot from January through February. Re-enrollment letters go out, sibling-priority slots get claimed, the waitlist explodes, and somewhere in the middle of all that a state subsidy worker calls about a CCDF child whose paperwork lapsed in November. Tuition is not one number — it is full-pay for some families, sliding-scale for others tied to household income, and partial state-subsidy for a third group that requires monthly reconciliation against the agency's payment file. Parents expect a daily report on their kid by 4 p.m. with naps, meals, diapers, and at least one photo. They expect immunization records to be current and pulled in thirty seconds when the licensing inspector shows up. They expect the app, the email, and the SMS to all say the same thing.

This guide walks through the five operational systems every preschool needs to get right: enrollment with sibling priority, tiered tuition with subsidy reconciliation, daily reports parents will actually read, immunization tracking the state will accept, and a parent-communication strategy that respects the inbox.

Enrollment season is where preschools either build a year of full classrooms or spend nine months scrambling to fill a single Toddler 1 slot. The work breaks into three pieces: the application, the priority order, and the deposit.

The application form. A real intake form — not a PDF. Capture the child's full legal name, date of birth, allergies, current pediatrician, sibling status (with the older child's name and current classroom if applicable), languages spoken at home, and the desired start date. Capture the parents' employer, work hours, and whether they need before-care or after-care. Capture the funding source: full-pay, sliding-scale eligible, or state-subsidy (CCDF, Head Start, or local equivalent). Every one of those fields drives a downstream decision, and re-keying any of them later is where errors creep in.

Lottery vs. first-come. Most preschools use first-come, first-served with sibling priority layered on top. A handful of high-demand programs run a lottery to avoid the appearance of favoritism. Pick one, document it, and put it on your website — parents who feel the process is opaque will leave a one-star Google review six months from now.

Sibling priority. Families with a child already enrolled get first claim on a slot in the next age group. The rule of thumb: re-enrollment for current families opens December 1, sibling priority opens December 15, general enrollment opens January 2. That two-week sibling window keeps families together without locking out the broader community. If you do not enforce sibling priority, you will lose multi-child families to whichever program down the street does.

The deposit. Charge a non-refundable enrollment deposit equal to one month's tuition (or a flat $250-$500 for sliding-scale families to keep it accessible). The deposit holds the slot, applies to the first month, and discourages families from holding two seats at two programs while they decide. Run the deposit through the same recurring-billing system that will handle monthly tuition — do not take it as a separate Venmo or check that you have to manually reconcile later.

Preschool billing is not one rate sheet. A typical full-day program has at least three tuition pathways running side by side, and the director has to keep them straight every month without dropping a payment.

Full-pay families. The cleanest case. Monthly recurring charge on the 1st, autopay on file, late fee after the 5th, hold on transcripts and re-enrollment after 30 days unpaid. The work here is in the setup — once a family is on autopay with a stored card or ACH on file, the system runs itself.

Sliding-scale families. Tuition is set by a published table tied to household adjusted gross income, usually verified annually with a tax return. A family at 200% of the federal poverty line might pay 30% of full tuition; a family at 400% pays 80%. The two operational rules: (1) verify income at enrollment and re-verify every July, and (2) document the table publicly so families understand exactly why their neighbor pays a different amount. Run sliding-scale charges through the same recurring billing system as full-pay — do not invoice them separately, or one will inevitably get missed.

State subsidy (CCDF and equivalents). Federal Child Care and Development Fund dollars flow through state agencies to families who qualify. The agency authorizes a specific number of hours per week at a specific reimbursement rate, and the family is responsible for any "co-pay" portion above the subsidy. Two operational realities: the state pays in arrears (typically 30-60 days after the service month), and the state pays based on attendance — every absence beyond the allowed threshold reduces the reimbursement. The reconciliation work is brutal if you do it manually: each month, take the state's remittance file, match each child's payment to your invoice, write off the gap if the state paid less than expected, and pursue the parent for any unpaid co-pay.

A single connected system — where attendance feeds the invoice, the invoice records the expected subsidy, and the remittance import marks the line item paid — turns a two-day reconciliation job into a forty-minute one.

The cost of getting it wrong. Programs that mis-bill subsidy families end up either eating the loss (which compounds quickly with five or ten subsidy kids) or chasing parents for amounts the parent had no idea they owed. Both paths are bad. Build the system once, test it on three months of data, and run it on rails.

The daily report is the single most-read piece of communication a preschool produces. Every parent looks at it. The good ones get screenshotted and sent to grandma. The bad ones get glanced at and forgotten.

What belongs in the daily report:

- Naps. Start time, end time, total duration. If the child did not nap, say so — parents will plan their evening around it. - Meals. What was served, how much was eaten ("most of the chicken, none of the broccoli"). For infants and toddlers, exact bottle volumes and times. - Diapers and bathroom. Wet vs. soiled, with times. For potty-training kids, accidents and successes both. - Mood and one specific moment. "Maya was a little quiet at drop-off but warmed up during music time and led the line to the playground" beats "had a good day" by a factor of ten. Parents are starved for specifics. - One photo of the actual activity. A picture of the painting, the block tower, or the kid laughing at the sensory bin. Not a posed group shot. The candid photo is what gets sent to relatives.

What does NOT belong in the daily report:

- Chronic compliance noise. The fact that you sanitized the tables, completed the fire drill, and ran the temperature check on the fridge does not need to go to parents — it goes in the licensing logbook. Mixing those two destroys the signal. - Generic checkboxes with no context. "Lunch: ate" tells the parent nothing. - Anything that should be a phone call. If the child was bitten, hit their head, or had a fever — call. Do not bury it in the 4 p.m. report.

Send time. Aim for between 3:30 and 4:30 p.m., before the working parent's commute home. Anything after 5 p.m. competes with dinner and bedtime and gets skipped. Anything before 2 p.m. misses the afternoon.

Every state requires preschools to maintain current immunization records for every enrolled child, plus signed exemption forms for any opt-outs. The licensing inspector who walks in on a random Tuesday morning is going to ask for two things: the staffing ratio log for the past month and the immunization roster. If either one is incomplete, you are looking at a citation, a re-inspection, and potentially a hold on new enrollments.

The required schedule. State requirements vary, but most align with the CDC childhood immunization schedule: DTaP, polio, MMR, varicella, hepatitis B, Hib, pneumococcal, and rotavirus, with specific dose counts at specific ages. Track each child against the schedule and flag any child who is behind by more than 30 days. The grace period is your friend — most states allow a child to attend while a missed dose is being scheduled, but only with documentation that the appointment is on the calendar.

Exemption documentation. Parents who claim a medical, religious, or philosophical exemption (state-dependent) must sign the state's specific exemption form, not a hand-written note. Keep the form in the child's file with the date signed. If your state does not recognize philosophical exemptions, do not accept them — admitting a non-vaccinated child without a valid exemption is the kind of thing that closes programs.

Audit prep. When the licensing inspector visits, you should be able to pull a roster in under sixty seconds showing: every enrolled child, their current immunization status, any pending doses with appointment dates, any exemption with the form on file, and the date each record was last updated. A binder works. A connected system works better, because the system flags the kid whose next DTaP is due next week before the inspector does.

Outbreak protocol. If a vaccine-preventable illness shows up in your program (measles, pertussis, varicella), the state health department may require you to exclude unvaccinated and exemption children for a defined period. Have the contact-and-exclusion list ready before you need it — pulling it together during an active outbreak while parents are calling is not the moment to discover your records are messy.

Parents are not a single audience. The grandparent picking up on Thursdays does not need the curriculum newsletter. The dual-income family with two kids in the program does not want the lead teacher's group text waking them at 6 a.m. about a snow delay they already saw on the news. Sort communication by channel and by urgency.

The parent app — daily and routine. Daily reports, photo updates, monthly tuition statements, calendar of upcoming events, classroom announcements, sign-in/sign-out logs. Every active family has the app installed at enrollment. The app is the default channel for everything that is not urgent and not promotional.

Email — weekly and substantive. A Friday newsletter from the director with the upcoming week's theme, any staffing changes, picture-day reminders, parent-meeting invites, and one paragraph from a teacher about something that happened that week. Keep it under 400 words. Send it at 11 a.m. Friday, not 5 p.m. — the open rate doubles. Do not use email for daily reports; the volume drowns the substantive messages.

SMS — emergency only. Snow days, early closures, lockdowns, building issues, and the occasional same-day reminder for picture day. The rule: every SMS should be something that, if missed, has real consequences for the parent's day. The moment SMS becomes a marketing channel — flu-season tips, new-program promotions, payment reminders — parents start ignoring them, and your one channel for the actual emergency goes dead.

Parent meetings — quarterly. Once a quarter, in person. Twenty minutes, an actual agenda, refreshments, and a written summary emailed within 48 hours so parents who could not attend stay in the loop. Use these for things email cannot do: introducing new staff, walking through curriculum changes, soliciting input on the next school year. The directors who run these well end up with the strongest re-enrollment numbers, because parents who feel heard renew.