Skip to main content

Registration is now open for this year's LibreFest! Join us virtually the week of July 13.

Register here
Workforce LibreTexts

10.8: Data, Waitlists, and Enrollment Management

  • Page ID
    60118
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \(\newcommand{\longvect}{\overrightarrow}\)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Growing enrollment requires more than general impressions about whether the program is “full” or “slow.” Administrators need reliable data to understand enrollment patterns, anticipate openings, and make informed decisions about staffing, classroom configuration, and outreach. Without clear data, programs may miss important trends or respond too late to enrollment changes. Enrollment management involves tracking where families are in the process, how spaces are being used, and where gaps are likely to occur. It helps administrators move from reactive decision-making to proactive planning.

    Tracking Enrollment Data

    Programs should regularly monitor basic enrollment information, including current enrollment, classroom capacity, inquiries, applications, waitlist numbers, withdrawals, and anticipated transitions. This information helps administrators understand both present enrollment and future enrollment risk. For example, a classroom may appear full in September but have several children aging out or transitioning to kindergarten in the spring. Without tracking those patterns, the program may be surprised by openings later in the year. Similarly, a long waitlist may seem promising, but if many families on the list no longer need care, the program may overestimate actual demand. Enrollment data should be current, organized, and easy to interpret. Programs do not necessarily need complicated software, but they do need a consistent system.

    Understanding the Enrollment Pipeline

    The enrollment pipeline refers to the path families move through from first inquiry to confirmed enrollment. A family may begin by asking about openings, then schedule a tour, submit an application, join a waitlist, complete eligibility paperwork, and eventually enroll. If families drop out of the process at a particular point, that may indicate a problem. For example, if many families inquire but few schedule tours, the program may need to improve its follow-up process. If many families tour but do not apply, the issue may involve cost, schedule, first impressions, or lack of fit. If families apply but do not complete paperwork, the process may be too confusing or burdensome. Tracking the pipeline helps administrators identify where interest is being lost and where changes may be needed.

    Managing Waitlists

    A waitlist can be a useful enrollment tool, but only if it is managed carefully. A long waitlist does not always mean the program has guaranteed future enrollment. Families may join multiple waitlists, find care elsewhere, move, or no longer need the same schedule by the time a space opens. Programs should keep waitlists current by checking in with families periodically and confirming continued interest. Waitlist records should include important details such as the child’s age, desired schedule, preferred start date, eligibility status if applicable, and family contact information. This allows administrators to match openings more accurately. Waitlist procedures should also be transparent. Families should understand whether the list is first-come, first-served; based on eligibility or priority criteria; organized by age group; or influenced by funding requirements. Lack of clarity can create frustration and mistrust.

    Predicting Openings and Transitions

    Enrollment planning requires administrators to look ahead. Programs should anticipate openings caused by children aging into a new classroom, leaving for kindergarten, changing schedules, or withdrawing. These patterns are especially important in programs serving multiple age groups. Transitions can create both opportunities and challenges. When children move from infant to toddler care or from toddler to preschool, the program may retain the family while also creating openings in younger classrooms. However, if the next classroom is full, families may leave even if they would prefer to stay. This is why enrollment management must be connected to classroom capacity and long-term planning. Administrators should regularly review upcoming transitions so they can prepare families, adjust staffing, and communicate about openings before last-minute decisions are necessary.

    Seasonality and Enrollment Patterns

    Many programs experience seasonal enrollment patterns. Enrollment may increase at the start of the school year, shift after winter break, or decline in summer depending on the program model. Programs serving school-year populations may have predictable kindergarten transitions, while full-day or year-round programs may experience more gradual changes.

    Understanding seasonality helps administrators plan staffing, outreach, and budgeting. For example, if a program knows that preschool openings typically occur in August, it can begin outreach earlier. If summer enrollment tends to drop, the program may plan summer programming, adjust staffing, or communicate with families ahead of time. Programs should compare enrollment patterns across multiple years when possible. One year of data may reflect unusual circumstances, but repeated patterns can guide planning.

    Using Data to Guide Decisions

    Enrollment data should inform program decisions, but it should not be interpreted in isolation. Administrators need to consider the reason behind the numbers. A classroom with low enrollment might reflect lack of demand, but it might also reflect limited outreach, a schedule mismatch, high cost, or a difficult enrollment process.

    Useful questions include:

    • Which age groups have the strongest demand?
    • Where are families dropping out of the enrollment process?
    • Are openings predictable or unexpected?
    • Are waitlists current and meaningful?
    • Are withdrawals connected to preventable program issues?

    Data should support decision-making, not replace professional judgment. The strongest decisions combine enrollment numbers with family feedback, staff observations, and community knowledge.

    Vignette \(\PageIndex{1}\)
    "The Waitlist Wasn't Real"

    A program director felt confident about enrollment because the program had a long waitlist for toddler care. When a classroom opening became available, the office began contacting families from the list. Many did not respond. Others had already found care, moved out of the area, or needed a different schedule than the program offered.

    After several weeks, the opening remained unfilled. The director realized that the waitlist had not been updated in months and did not reflect actual demand. The program began contacting waitlisted families regularly, recording desired start dates and schedules, and removing families who were no longer interested. The waitlist became shorter, but it became more useful. This example illustrates that enrollment data must be actively maintained. A long list is less valuable than accurate information.


    This page titled 10.8: Data, Waitlists, and Enrollment Management is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Jennifer Marta and Hannah Knott.