Skip to content
solutionwhere

Who we serve School districts · ISDs, RESAs, IUs, ESCs, AEAs and BOCES · CCR&R agencies and their equivalents · Counties, parishes and community networks · State education and early-childhood agencies · Universities · Adult education · Early childhood networks

Article

Best Pre-K Enrollment Software: What Early Childhood Directors Need to Track

November 3, 2026

What Pre-K Enrollment Software Must Track

Pre-K enrollment software records application intake and family contact information across state-funded pre-K, Head Start, Title I, and blended-funding programs. Each program requires different eligibility criteria, but families often apply to multiple streams for the same child. The system must preserve which program each application targets and whether a family has submitted documentation for more than one funding source.

Age eligibility verification requires storage of birth certificates or passport copies and automated calculation of whether the child meets the program cutoff date. State pre-K programs typically require children to turn four by a specific date, Head Start uses different age ranges, and blended classrooms must track both. The system must flag which children meet which age threshold and which documents are missing.

Income verification and categorical eligibility tracking are required for means-tested programs. Staff upload tax returns, pay stubs, SNAP notices, or TANF letters. The system must flag categorical eligibility automatically when a family provides proof of public assistance.

Immunization records and health screening completion status must be tracked before the first day of attendance. State licensing agencies and Head Start performance standards require proof that each child has received age-appropriate vaccines and completed physical exams, vision screenings, and hearing screenings within a defined window. The system must show which records are on file and which are outstanding.

Lottery assignment preserves priority categories when demand exceeds capacity. Programs define tiers such as sibling preference, resident status, income qualification, and application date. The system must assign each family to the correct tier, run the lottery within each tier, and generate seat offers and waitlist positions in priority order. The lottery result must be auditable and reproducible if a family appeals.

Waitlist position tracking requires a time-stamped application date and movement tracking as seats open. When a family declines an offer, the next family on the waitlist moves up automatically. The system must record every movement, who was offered a seat and when, and whether the family accepted or declined.

Enrollment contract signatures and emergency contact information are required by licensing standards before a child attends. The system must store signed forms, track which families have returned contracts, and confirm that emergency contacts include at least two adults and current phone numbers.

Why Generic Student Information Systems Do Not Fit Pre-K

District student information systems are designed for K-12 grade progression, transcript management, and course scheduling. Pre-K programs do not assign grades, track credits, or schedule courses. They enroll children based on age eligibility, family income, and application date. SIS platforms structure data around students who move from one grade to the next each year. Pre-K programs enroll a new cohort every year based on birth date and program eligibility, not prior enrollment history.

Pre-K enrollment operates across a months-long application cycle, not a single registration event. Families apply in winter or early spring, programs run lotteries in late spring, and enrollment continues through summer as waitlist families accept seats. SIS platforms are built for a registration window that opens a few weeks before school starts, assumes returning students, and focuses on updating addresses and emergency contacts.

Blended funding models require separate eligibility documentation for the same child in the same classroom. A four-year-old may be enrolled in a state pre-K slot because the family meets residency and age requirements, while also qualifying for Head Start because household income falls below the federal poverty guideline, and also receiving Title I services because the school is in a high-poverty area. Each funding stream requires different documentation, different monitoring reports, and different roster formats. SIS platforms do not structure or store multiple eligibility records for a single child.

Licensing agencies require rosters that reflect daily attendance capacity and ratios, not full-time equivalency counts. A pre-K classroom is licensed for 20 children with one teacher and one assistant. If 22 families have signed enrollment contracts but two children attend only on alternating days, the roster must show that the program does not exceed licensed capacity on any given day. SIS platforms calculate enrollment as a count of active students, not as a daily attendance capacity check.

Family applications include sibling data and household income verification that SIS platforms do not protect appropriately. Pre-K enrollment collects sensitive financial information to determine eligibility for means-tested programs. That information must be stored separately from the child's educational record and restricted to enrollment staff. SIS platforms grant access to teachers, counselors, and administrators who need to see academic and behavioral data but should not see family income documents.

How to Run a Pre-K Lottery and Waitlist Without Spreadsheets

Set the application deadline and define priority tiers before opening enrollment. Common tiers include district residents with sibling preference, district residents without siblings, non-residents with siblings, and non-residents without siblings. Some programs add income qualification as a tier, some use application date as a tiebreaker within each tier. Define these rules in writing and communicate them in the application packet.

Assign each application to a tier and time-stamp submission. When a family submits an application, staff verify residency and sibling status, place the application in the correct tier, and record the date and time. If 150 families apply for 60 seats and 40 of those families include siblings, the sibling-preference tier is processed first.

Run the lottery within each tier, generating seat assignments and waitlist positions in priority order. The system assigns seats to all families in the first tier, then moves to the second tier and assigns remaining seats until capacity is reached. Families who do not receive a seat are placed on the waitlist in tier order, with application timestamp determining position within each tier. The result is a numbered list showing seat offers and waitlist rank for every family.

Send offer letters with an enrollment deadline and track family acceptance or declination. Each family receives a letter stating whether they have been offered a seat, their waitlist position, or whether they did not qualify. Families who receive a seat offer must respond by a deadline, typically two to three weeks after the letter is sent. Staff record whether each family accepts or declines.

Move waitlist families into open seats automatically as declinations occur, preserving priority order. When a family declines, the system assigns the open seat to the next family on the waitlist, sends an offer letter, and records the new offer. This continues until all seats are filled or the waitlist is exhausted.

Export the final roster with eligibility documentation attached for state or Head Start monitoring. Monitoring visits require proof that every enrolled child met eligibility criteria at the time of enrollment. The system must generate a roster showing each child's age, residency status, income verification if applicable, and attached copies of birth certificates and income documents.

Eligibility Documentation That Programs Must Collect Before Enrollment

Birth certificates or passports verify age eligibility against the state or district cutoff date. State-funded pre-K programs use cutoff dates that vary by state. Head Start serves three-year-olds and four-year-olds, with separate age requirements. Programs must store a legible copy of the birth certificate and confirm that the child's birth date meets the threshold before enrollment is finalized.

Proof of residency is required when enrollment is limited to district boundaries or a defined service area. Acceptable documents include a signed lease, a utility bill showing the family's name and address, or a notarized residency affidavit from the property owner. Some programs accept a letter from a shelter or a statement from a school liaison if the family is experiencing homelessness.

Income documentation is required for means-tested state pre-K programs and Head Start. Programs accept the most recent federal tax return, four consecutive pay stubs showing gross income, or a SNAP or TANF award notice. Some programs accept a letter from an employer on company letterhead. Categorical eligibility applies when a family receives SNAP, TANF, SSI, or other public assistance, and no further income documentation is required.

Immunization records must show dates and provider signatures, cross-checked against the state schedule for age. State health departments publish immunization schedules specifying which vaccines are required by age four. Programs compare the child's record to the schedule and identify any missing doses. If a child is missing required vaccines, the family must provide documentation of a catch-up plan from a healthcare provider or a signed exemption form if the state allows medical or religious exemptions.

Physical exams and vision or hearing screenings must be completed within a required window before the first day. State requirements for physical exam timing vary. Vision and hearing screenings may be completed by the program or by a healthcare provider. The system must track which screenings are complete and which are pending.

Individualized Education Programs or Individualized Family Service Plans are required if the child is transitioning from Part C early intervention services. Programs coordinate with local education agencies to ensure that IEPs are in place for children with disabilities before the start date. The system must flag which children have an IEP or IFSP on file and which families are waiting for an eligibility determination.

Where Programs Get This Wrong

Accepting applications in paper form or by email forces staff to manually enter each one into a spreadsheet without version control or timestamp. When a family submits an application by email on the last day of the application period, the timestamp in the inbox shows when the email arrived, but staff may not enter it into the spreadsheet for several days. That delay creates disputes when families on the waitlist argue that they applied earlier than families who received seats.

Running the lottery by hand-sorting rows in Excel loses the audit trail of who was selected and when. If a family appeals their waitlist position or claims they should have been in a higher priority tier, staff cannot reproduce the lottery result or show which data were used to assign tiers.

Storing birth certificates and income documents in a director's email inbox or unlocked file cabinet creates privacy and compliance risk. Email accounts are not encrypted, and attachments forwarded to multiple staff members create copies that cannot be tracked or deleted. Unlocked cabinets are accessible to custodial staff, visiting trainers, and substitute teachers who do not have a legitimate need to see family income information.

Failing to track which eligibility documents are missing for each child leads to gaps discovered the day before school starts. Staff assume that a family has submitted all required paperwork because the child's name is on the roster, but when the monitoring visit occurs, birth certificates or immunization records are missing for 15 children. This results in provisional enrollment, delayed start dates, or citations from the licensing agency.

Mixing waitlist management across phone messages, email, and paper notes causes disputes when families claim they applied earlier than recorded. A family leaves a voicemail in February asking to be added to the waitlist, but the message is not returned and the family is not added to the spreadsheet until March. When seats open in April, the family expected to be near the top of the list but finds they are ranked 30th because the March entry date was used.

Duplicating data entry when the same child is enrolled in both state pre-K and Head Start increases error rate and staff time. The child's name, birth date, parent contact information, and address are entered into the state pre-K roster, then entered again into the Head Start database. If the family moves or changes phone numbers, staff must update both systems. If the updates are not synchronized, the family receives conflicting information.

Why Early Childhood Agencies Use Solutionwhere for Pre-K Enrollment

Directors track application status, eligibility document submission, and waitlist position for every family in one system. Office staff and site coordinators see which families have submitted complete applications, which documents are outstanding, and which children are enrolled, waitlisted, or declined. No one searches email or asks another staff member to check a file cabinet.

The lottery module assigns seats by priority tier, preserves time-stamped application order, and generates offer letters and waitlist notifications. Staff define tiers and rules once, then run the lottery with one action. The system produces a numbered list showing every family's seat assignment or waitlist rank, along with a log of which tier and timestamp were used for each decision. If a family appeals, staff retrieve the log and explain the result.

Secure document upload and storage keeps birth certificates, income verification, and immunization records attached to each child's record. Families upload documents through a portal, or staff scan and attach paper documents during application intake. Documents are visible only to staff with enrollment permissions, not to teachers or classroom aides. When a monitoring visit occurs, staff export the roster with all eligibility documents attached as PDFs.

Waitlist automation moves the next eligible family into an open seat when a family declines. The system sends the offer letter by email, records the date and time, and waits for the family's response. If the family accepts, the system removes them from the waitlist and increments the enrollment count for that site. If the family declines, the system moves to the next family on the list.

Reports export rosters by funding stream, eligibility category, or site for state monitoring visits, Head Start PIR, and local board review. State pre-K coordinators generate a roster of all children funded by the state grant, with attached birth certificates and residency documents. Head Start directors generate a roster of income-eligible children, with attached tax returns or SNAP notices. District early-childhood coordinators generate a roster by school site, showing enrollment counts against licensed capacity.

Solutionwhere has been independent since 1996. You buy one module, not a suite. A real person answers the phone.

Responsible for tracking this across your staff? See how districts and agencies manage it in Solutionwhere.

← All posts

Wondering whether we would fit your setup?

Tell us what your year looks like and we will give you a straight answer.