A preschool can use AI to draft the form's fields, consent wording and four reminder emails, then paste them into its own form tool and track returns in a sheet. Keep real child details out of the AI chat: give it blank templates, placeholders such as [first name], and counts, never completed forms.
Most enrolment problems come from paperwork that arrives late or half-finished, not from the form itself. A form that asks for fifty things gets eleven of them wrong, and the missing immunisation record or collection-password page turns up in week two of term. So the plan below has three parts: a short form that asks only what you must hold, a chase routine with a fixed rhythm, and a tracker that shows at a glance who still owes what.
What to settle before you open any AI tool
AI is good at wording and structure and bad at knowing what your licensing authority requires. Spend twenty minutes first on a single page headed "Records we must hold for every child". Start from your licensing authority's published requirements and your insurer's conditions, then add anything your own policies demand. Typical entries are: the child's full name and date of birth, parent or guardian contacts, emergency contacts who are not the parents, who may collect the child, health and dietary needs, consent for outings and first aid, and any court or family arrangements staff need to know about. Your authority's list may differ, so treat that as a prompt for your own check, not a rule.
That page becomes the brief you give the AI. It also becomes your test at the end: if the finished form does not cover every line, it is not finished, and if it asks for something not on the page, you should be able to say why.
Decide what stays out of the chat
The safe pattern is simple. The AI sees structures, not people. It may see a list of field names, a blank consent paragraph, or an anonymised row such as "Family 07, birth certificate: received, immunisation record: missing". It may not see names, dates of birth, addresses, medical conditions, photographs or anything from a completed form. Placeholders matter on any plan, but the plan changes what happens to the text you do paste: on personal ChatGPT Free, Plus and Pro accounts, chats can be used to improve OpenAI's models unless someone switches off "Improve the model for everyone" in Data controls, while OpenAI says it does not train on ChatGPT Business or Enterprise data by default. If you want a deeper rule set, is it safe to use AI with children's data in a nursery covers the reasoning, and the one-hour staff briefing turns it into something your team will remember.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowBuilding the form fields with a prompt that works
Give the assistant your "records we must hold" page, the form tool you plan to use, and the tone you want. Ask for fields grouped into sections, each marked required or optional, with the reason for asking. The reasons matter: they let you cut anything you cannot justify.
You are helping a small preschool draft an online enrolment form.
Here is the list of records we must hold for every child: [paste your list].
We will build the form in [form tool]. Families fill it in on a phone.
Write the form as sections. For each field give: label, answer type
(short text, date, yes/no, choice, file upload), required or optional, and
one line on why we need it. Keep it under 45 fields in total.
Use plain English at a reading age of about 12. Do not ask for anything
not on my list. Mark any field you think might need extra care under our
data-protection policy.Here is the kind of output you should expect, shortened and illustrative:
| Section | Field | Type | Required? | Why we ask |
|---|---|---|---|---|
| Your child | Full legal name | Short text | Required | Matches the register and the birth record |
| Your child | Name they like to be called | Short text | Optional | Helps staff settle them in |
| Contacts | Second emergency contact | Short text + phone | Required | Needed if parents cannot be reached |
| Collection | Who may collect | Repeating group | Required | Staff check this at every handover |
| Health | Does your child have an allergy? | Yes/no | Required | Opens the allergy detail section |
Two things to fix in a typical first draft. The assistant will often include "parents' employer and job title", which is rarely needed for safety or for your records, so delete it unless a funding scheme you use requires it. It will also tend to put everything on one long page. Split the form into three screens (child, family, health and consents) so that a parent on a phone can save and come back.
The medical and consent sections need a different method
These are the sections where vague wording does real harm, so write them with the AI but let a qualified person sign off the final text. Use yes/no gates so that a family with no health needs answers one question, while a family with a nut allergy is taken to the detail screen.
A health gate with the questions staff can act on
Ask the assistant to turn "allergies" into the questions a room leader needs at 8.30 on a Monday. A good version of the allergy branch asks what the child is allergic to, what happens when exposed, what staff should do first, whether they carry prescribed medication, where it should be kept, and whether a written action plan from a clinician is attached. For other conditions, ask the same pattern: what, how it shows, what to do, who to call.
Before and after, using an illustrative example. The first draft question reads "Please give details of any medical conditions." Parents answer "Asthma, mild." The rewritten branch asks four things: whether the child has an inhaler, how often it is used, what signs staff should watch for, and what the parent wants staff to do if the inhaler does not help within a few minutes. The second version gets an answer a practitioner can use without ringing the parent.
Consent wording in plain English
Separate consents from the enrolment itself. Each consent gets its own tick box and its own sentence, and none is pre-ticked: outings within walking distance, emergency first aid and seeking medical help, sun cream and nappy cream, and photographs used inside the setting. Photographs shared outside the setting (a newsletter, social media) deserve a separate consent with separate choices, and the follow-on tutorial on safe preschool social media posts shows how to keep a register of those.
Rewrite this consent sentence so a parent can understand it at a glance.
Keep the meaning, keep it under 35 words, and do not add any legal claims.
Original: "The undersigned grants permission for the establishment to
photograph the minor for purposes including but not limited to
promotional materials."A usable output reads: "I am happy for the preschool to take photos of my child for use on our noticeboard and in my child's learning record only." Notice what has changed: the purpose is narrowed, so a separate tick box can cover the newsletter and another the website. If the AI keeps phrases like "including but not limited to", ask it to remove them. Then have your owner, manager or a legal adviser read the final text once, because consent wording is a policy decision, not a writing exercise.
Choosing where the form lives and what it may collect
You have three realistic homes for the form: a general form tool such as Google Forms or Jotform, the parent-facing module in your nursery management software, or a PDF that families print and return. A general form tool is the cheapest start. Two practical points to check on the vendor pages before you commit: whether file uploads work for families without an account with that vendor (Google's help page says respondents must sign in to a Google Account to answer a file upload question, which puts off parents who do not have one), what the free plan's limits are, and where submissions are stored. Limits bite sooner than you expect once parents upload phone photos of documents: Jotform's free Starter plan, for example, allows 100 submissions a month but 100 MB of space and 500 stored submissions as of November 2026, and 14 families each uploading three photos of two or three megabytes would use most of that space in one intake. If your management software already has an enrolment module, use that first, since the data lands in the register without retyping.
A quick decision rule: under about 20 new families a year, a free form tool plus a tracking sheet is plenty. Over that, or if you take funded places with extra evidence, check what your management system can do before you build a second system next to it. AI tools for preschool owners looks at what parent-facing software can already do.
A September intake, worked through
An illustrative case. A preschool with 28 places has 14 new families starting in September. Each family owes six items: the completed form, proof of date of birth, immunisation record, a signed copy of the handbook acknowledgement, the signed fees agreement, and the settling-in visit booking. Six items times 14 families is 84 items. The manager sets the form live on 1 June with a deadline of 30 June, and the tracker begins with all 84 as "requested".
By 10 June the tracker shows 51 of 84 received, so 33 are outstanding across 11 families. Reminder one goes only to families with at least one item missing, which spares the three families who finished everything from an irrelevant nudge. By 21 June, 69 of 84 are in and 15 outstanding across 6 families. Reminder three adds a sentence offering a ten-minute phone call, and two families take it. On 30 June, 3 items remain, all immunisation records the parents are waiting on from a clinic. Those get a named exception in the tracker with a new date. None of this needed anyone to scroll through emails looking for who sent what.
The tracker: one row per family, one column per document
Build the tracker in a spreadsheet with no child names. Use a family code (F01 to F14), a start date, and one column per document with three states: requested, received, exception. Add columns for "last reminder sent", "reminder number" and "next action date". Colour the cells with conditional formatting so that red means overdue, amber means due within three days and green means complete.
| Family code | Form | Birth record | Immunisation record | Handbook sign-off | Last reminder | Next action |
|---|---|---|---|---|---|---|
| F03 | Received | Received | Missing | Received | R2 on 14 June | R3 on 21 June |
| F07 | Received | Missing | Missing | Missing | R1 on 10 June | R2 on 14 June |
| F11 | Received | Received | Exception: awaiting clinic | Received | None needed | Check 8 July |
Keep the key linking F03 to a real family inside your management system, not in the same sheet that you might share with a volunteer or paste into a chat. When you want the AI to help, paste only a table like the one above and ask it for something that needs no identity: a list of the families with two or more items outstanding, in order of how overdue they are, with the right reminder number for each.
Here is our enrolment tracker with family codes only, no names.
Today is [date]. Reminder schedule: R1 day 9, R2 day 13, R3 day 20,
R4 day 26 (phone call). For each family, tell me which reminder is due,
which documents to name in it, and flag anyone who is past R4.
Return a table, then do not draft any messages yet.Four reminders that do not nag
The wording changes each time, and each message names the actual missing item rather than saying "some documents". Give the AI the schedule and ask for four versions with merge fields, then test one on a colleague who plays a busy parent. Use merge fields from your email tool or form tool (the [first name] and [missing items] placeholders below) so that no child details have to pass through the chat.
Write four reminder emails for parents who owe us enrolment documents.
Tone: warm, brief, no guilt. Merge fields: [first name], [missing items],
[deadline], [link]. Email 1 is a friendly check; email 2 says exactly what
is missing and how to send it; email 3 explains why we need it before the
first day (safety, not bureaucracy); email 4 says a member of staff will
phone, and gives the reception opening hours. Each under 90 words.An illustrative result for the second email: "Hi [first name], thank you for the form. We still need [missing items] before [deadline]. You can upload a photo of the page from your phone here: [link]. If anything is hard to find, reply and tell us, and we will sort it together." Two edits before it goes out: replace "before [deadline]" with a plain date, and remove any sentence implying that the child's place is at risk, unless that is genuinely your policy and it is written in your handbook.
When a family stops replying
Past the fourth reminder, stop writing and start talking. Ring, or catch the parent at drop-off with the tracker open. Many gaps are practical, not wilful: a record held by a clinic, a parent who does not read English comfortably, a separated couple where only one signed. If you serve families who speak several languages, ask the AI for a plain-language version, then ask a fluent speaker to read it before you send it out.
Five enrolment-form failures and how each shows up
- Over-collection. The AI proposes extra fields and nobody removes them. Check that every field maps to a line on your "records we must hold" page or has a written reason.
- Copied consent wording that does not match your practice. A consent for "promotional use" when you only use photos in learning journals. Check by reading each consent against what staff actually do this term.
- Reminders to the wrong people. A family that finished still gets reminder two. Filter the tracker by "missing" before every send, and send from the tool's segment, not from a pasted list.
- Child details pasted into a chat. It happens in a rush. Make a rule that the tracker has family codes only, and tell the team that a mistake should be reported straight away so that it can be dealt with under your policy.
- A form that cannot be completed on a phone. Test it yourself on a phone on mobile data, and ask one parent to try it before launch.
Checking the form is ready and the routine is working
Before you send the form, run a five-point test: every required record on your page has a field; no pre-ticked boxes; the health gate branches correctly for a "yes" and a "no"; the form submits on a phone; and the confirmation email tells families what happens next. After launch, measure the thing that matters, which is the share of families fully complete at day 14. If it is under half, the form is too long or the first email is too vague, so fix those before adding more reminders.
Time is the other check. Illustratively, hand-chasing 14 families across six documents might take a manager three to four hours spread over the month. With a tracker and templates, the same job is about 20 minutes a week of looking at red cells and sending a segmented email. That is a rough estimate to test against your own intake, not a promise.
Two edge cases that catch out a tidy tracker
The first is the family that enrols twice, usually siblings in different sessions. Do not ask for the same birth record and emergency contacts again. Give the form a "my other child is already enrolled" choice that skips the shared sections, and give each child their own health screen, because an allergy in one child tells you nothing about the other. In the tracker, use one row per family and a separate set of columns per child (F03a, F03b), or one row per child with a shared family code.
The second is the late starter. A place that opens in March needs the same checks as the September cohort, but your reminder calendar is built around a June deadline. Store the reminder schedule as offsets, not dates (day 9, day 13, day 20, day 26 from the date the form was sent, the same rhythm as the June example), and add one column for "form sent on". Then the tracker works for any start date, and the AI prompt that works out who is due simply takes today's date and subtracts. Test it once with a made-up family sent the form 21 days ago: reminder three should show as due, and reminder four should not.
A third check worth five minutes: ask the AI to read your finished form as a nervous first-time parent and list every question that might feel intrusive or confusing. It is a good use of a language tool, because it reads the form cold. Take its list as prompts for a human decision, not as edits to accept. Where it flags "Does your child have any additional needs?" as vague, expand it into specific, optional questions with a line explaining that the answers help you plan support from the first day.
Where this connects to the rest of your paperwork
The handbook acknowledgement is the document families sign as part of enrolment, so keep that text in step with your parent handbook and its yearly review. The same pattern, a short form, a tracker and four reminders, also suits registration for a dance studio or an admission pack in a care agency. If you would rather map your own process with someone, that is what my AI implementation consultation covers, and you can start from the contact page.
Questions preschool owners ask before they switch to an online form
Can I paste a completed enrolment form into ChatGPT or Claude?
Avoid it. A completed form holds names, dates of birth, health details and contact numbers for children and parents. Use AI on blank templates, placeholders and counts, keep the real answers inside your form tool and management system, and follow your own data-protection policy on what may leave them.
Should the medical section be one free-text box?
No. Use separate fields for allergies, conditions, medication, and what staff should do, with a yes/no gate so families without needs can skip the detail. Free text invites vague answers like 'mild allergy' that staff cannot act on in an emergency.
How many reminders are too many?
Three or four over about three weeks is a sensible ceiling for routine documents. Space them out, change the wording each time, and switch to a phone call or a word at drop-off once a family is past the last reminder.
Do I need a paid form tool?
Not necessarily. A free form tool can collect text answers and consents. Check whether it supports file uploads, signatures and the number of submissions you expect, and read where it stores data before you send it to families.
Further reads
- Nursery Data Protection Policy: Draft and Update It With AI — Keep your privacy notice and retention periods in line with the form.
- Preschool Newsletter: A Monthly Issue From Your Notes, With AI — Reuse the same notes habit for the monthly family newsletter.
- AI Chatbots for Nursery Enquiries and Visit Bookings — Handle the enquiries that come before the form is ever sent.
- How to Increase Nursery Occupancy: Open Days, Reviews and AI — Fill the places the enrolment form is waiting for.
- Tapestry vs Famly for a Small Nursery: Where Does AI Fit? — Check which nursery software already includes an enrolment module.
- Martial Arts Summer Camp Ideas: Sign-Ups and Parent Emails With AI — A four-week camp plan for a martial arts school: 20-place pricing, daily timetable, safeguarding and pick-up rules, a sign-up page and six parent emails.
- After School Club Registration Form: Consents Built With AI — A field-by-field club registration workflow with separate permissions, authorised collector details and a chase sequence for missing forms.
- Daycare Late Pickup Policy: Can AI Word the Fees Fairly? — Decide the grace period, fee type and repeat-lateness steps yourself, then let AI draft fair policy wording, a parent notice and reminder texts.
- How to Start a Preschool: First-Year Costs and Where AI Fits — A first-year cost table for a small preschool, the licensing route, enrolment targets, and the forms and parent messages AI can draft from day one.
- Starting a Microschool: Enquiries, Enrolment and Parent Updates With AI — The admin a new microschool needs for enquiries, enrolment and parent communication, with prompts, a worked week and the legal checks AI cannot do for you.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google Forms help on file upload questions (respondents must sign in to a Google Account), Jotform's pricing page (Starter plan limits), OpenAI's data controls help page and its business data page, all checked November 2026, and the licensing requirements your own authority publishes.