Preschool Parent Handbook: Draft It With AI and Check State Rules

A preschool can use AI to outline the parent handbook and rewrite each policy in plain English, but it must check the result against its state or local licensing rules, as the licensing authority publishes them, not against what the AI says they are. Build a checklist from the official text, test every section against it, and keep a signed acknowledgement page.

The risk with an AI-drafted handbook is not bad writing. It is confident writing about the wrong rules. An assistant has no idea which jurisdiction you are in unless told, may mix requirements from several, and cannot see which version of your licensing rules is current. It is, however, excellent at the parts that take owners the longest: structure, plain-English wording, consistent tone and spotting gaps against a list you provide. So the method is to use it for those parts and keep the "what is required" decision with a named person and the source documents.

Follow me on Instagram@sagnikteaches

An outline that parents can navigate

Start with the structure, not the wording. A handbook is a reference document, so its outline matters more than its prose. Give the assistant a description of your setting (ages, sessions, staffing pattern, meals, outings) and ask for a numbered outline with a one-line purpose for each section, then trim.

Connect on LinkedInSagnik Bhattacharya

I run a preschool for children aged 2 to 5, mornings and afternoons,
with a garden, a snack and a packed lunch option, and occasional
outings on foot. Propose a numbered outline for a parent handbook.
For each section give a one-line purpose and say whether it is usually
a legal or licensing requirement, a safety matter, or a preference
(use "check" where you are not sure). Do not write any policy text yet.
Keep it to about 18 sections, grouped under 4 to 5 headings.

A typical outline, illustrative: Welcome and who we are; Sessions, fees and payment; Starting with us (settling in, key person); A day at preschool (routines, meals, rest); Keeping children safe (safeguarding, collection, visitors, outings, photographs); Health (illness, medication, allergies, accidents); Behaviour and wellbeing; Working together (communication, complaints, feedback); Data and privacy; Policies you can request in full; Review and changes. The "check" labels tell you where to go to the source. Do not trust the legal or licensing label itself; treat it as a list of places to look.

Subscribe on YouTube@sagnikteaches

Writing each policy in words a parent will read

Policies written for inspectors read like contracts. Handbooks are read by parents at 10pm after a long day. Draft each section in two layers: a plain-English summary of three to six sentences for parents, and a "full policy" reference to the longer document you keep for staff and inspection. Ask the AI to do the first layer from your existing policy text.

Rewrite the policy below as a parent-facing section.
Reading age about 12. Maximum 130 words. Use "we" and "you".
Keep every rule and number exactly as written; do not add or soften any.
End with: "Full policy: available from the office on request."
If anything in the policy is unclear or contradicts itself, list it after
the rewrite under "Needs a decision".

POLICY TEXT:
[paste your existing sickness policy]

An illustrative before and after. Original: "Children displaying symptoms of diarrhoea or vomiting shall be excluded from the setting for a period of 48 hours following the last episode." Rewrite: "If your child has been sick or had diarrhoea, please keep them at home until they have been clear for 48 hours. This protects the other children and our staff." Check that the number came through unchanged, which it did, and that the rewrite did not add a reason you cannot support. The "Needs a decision" line is where the assistant earns its place: it may point out that the policy says 48 hours in one section and 24 in another, a contradiction that will cause a row at the door.

Sections where a human writes the first draft

Some sections should start with a person, not a prompt: safeguarding procedures and who the designated lead is, the arrangements for collection by someone other than the parent, what happens in an emergency, and your complaints route including the external body families may go to. The AI can then tidy the wording afterwards, but the content must come from your actual procedures and your licensing guidance. If the handbook says staff do something that they do not do, the handbook becomes a liability.

The licensing check, built from the source text

This is the step that matters most. Find your licensing authority's published rules, standards or regulations for settings like yours, and the current guidance. Download the official text. Then ask the assistant to extract a checklist from that pasted text, one line per requirement that affects parents or records. Because you gave it the source, it is working from your jurisdiction's wording, not its memory.

Below is the text of my licensing authority's requirements for early
years settings (pasted from the official document, version dated [date]).
Extract every requirement that should be reflected in a parent
handbook or in information given to parents. For each, give:
reference (section number as written), the requirement in one sentence
using the document's own words where possible, and the handbook section
where it should appear. Do not add anything that is not in the text.

TEXT:
[paste the official requirements]

Now do the comparison with your handbook draft. You can paste both the checklist and the draft and ask: "For each checklist line, say whether the handbook covers it, partly covers it or does not, and quote the sentence that covers it." The quote is the point. If the assistant cannot quote a sentence, the handbook does not cover the line. Then a person opens the official document and confirms each "covered" claim at the reference given, because an assistant can quote a sentence that sounds right but does not satisfy the rule.

A handbook audit, with numbers

An illustrative case. A preschool of 30 places has a 24-page handbook that nobody has revised since a move to a new building. The manager pastes the official requirements, and the assistant extracts 31 lines that touch parents. The comparison shows 22 covered, 6 partly covered and 3 not covered. The manager checks the 22 against the source and finds that two were wrongly marked as covered: one quoted a sentence about "fire drills" for a requirement about "procedures for evacuation including meeting points", which is different. So the audit result is 20 covered, 8 partly, 3 missing. Eleven items need work, not the three the AI first suggested.

Two of the three missing items are quick: an uncollected-child procedure and a statement about when information is shared with other agencies. The third, a section on how the setting supports children with additional needs, needs the person who leads on special educational needs to write it, which is a decision about practice, not wording. The whole exercise takes an afternoon, much of it reading the official text, and the manager ends with a dated checklist she can show an inspector. Here is the lesson: the value was in the extraction and the quotes, and the human check was not optional.

Fees, hours and closures: facts that must be exact

The part of a handbook parents argue about is money and time. Paste your fee schedule, session times, late-collection charges, holiday dates and notice periods into the assistant and ask it to write the section, but give it a stricter instruction: every number must appear exactly as given, with currency symbols and dates written in full. Then check every figure against your price list. A typical failure is a rounding, such as "around $30" for a fee that is $29.50, so add "never round or approximate" to the prompt.

Also let the assistant draw out the questions parents will ask that the section does not answer. Prompt: "Read this fees section as a parent. List the five questions it leaves open." Typical gaps: what happens if a child is absent for illness, whether holidays are charged, how much notice is needed to change a session, and what late collection costs. Answer those in the handbook and you cut a stream of emails.

The acknowledgement page that proves families received it

A signed acknowledgement tells you, and your inspector, that parents were given the handbook and key policies. It does not make every policy enforceable in the way a contract might be, so ask a lawyer if your fee and termination wording matters to you. In some places the signature is a licensing requirement rather than good practice: one state's child-care centre standards, for example, require parents to sign an enrolment agreement or similar document that includes the centre's operational policies on or before the day of admission, and the signed copy to be kept in the child's record. Look for the equivalent wording in your own rules and match your page to it. Keep the page short: the handbook version and date; a short list of the essential policies the parent confirms they have read (sickness, collection, photographs, complaints, fees); a line saying they can ask for the full policies at any time; and a signature and date for each parent or carer.

Draft a one-page parent acknowledgement for a preschool handbook.
Include: handbook version and date, 5 tick-box statements (read the
handbook; understand the sickness and collection policies; understand
the fees and notice terms; know how to raise a concern; know how to
request full policies), space for signature and date, and a line about
where it is kept. Plain English, no legal threats, under 180 words.

Practical points: record the version number on every signature, so that when you update the handbook you know who signed which; collect it at enrolment alongside the other documents (the enrolment form and chasing routine shows how to track missing signatures); and re-issue the acknowledgement only when there has been a substantial change, not for every typo. Keep a note of what counted as substantial, such as new fees, new hours or any new safety procedure.

One policy drafted end to end: collection by someone else

Collection is where a plain-English rewrite earns its keep, because the rules are strict and the wording is often fuzzy. Suppose your staff procedure says: "Children may only be released to persons named on the registration form. Any alteration must be notified in advance. Where an unfamiliar adult attends, staff shall verify identity and contact the parent before release." Ask for a parent-facing version with a 120-word limit, and keep every rule.

An illustrative output: "We only hand your child to the people you listed when you enrolled. If someone else will collect, please tell us before the session starts, by phone or in writing. If we do not know the person, we will ask for photo identification and ring you before we let your child go. This may feel strict, and it is how we keep every child safe." What do you fix? "Photo identification" was not in the original procedure, so either add it to the staff procedure, because it is a good idea, or remove it from the handbook. The assistant also dropped "by phone or in writing", which you restored because it is how staff accept changes in practice. This is the pattern for every section: the rewrite is a draft of the parent view, and the staff procedure and the handbook have to say the same thing.

A read-aloud test before anything is printed

Ask two people who did not write the handbook to read three sections aloud: one parent from your parent group if you have one, and one new member of staff. Note where they stumble or ask what a word means. Common culprits are "the setting", "key person", "additional needs", "exclusion period" and "safeguarding". Add a short glossary of five or six terms at the back, or replace the term in the text. You can also ask the assistant to list every term a new parent might not know, which tends to find the jargon you stopped noticing years ago.

Keeping versions straight so the signed page means something

A signature only helps if you can say what was signed. Number versions as a date, such as "Handbook 2026-09", and print that on the cover, the footer of every page and the acknowledgement page. Keep the old versions in an archive folder instead of deleting them, so that if a parent disputes a fee notice you can show which wording applied on the day. When you update mid-year, send the changed section with a one-line summary and mark the new version number, instead of reissuing the whole document.

A short example of how a change travels. Fees rise from September, with eight weeks' notice written into the fees section. In June the manager changes that section, bumps the version to 2026-09, emails families the new page and the summary ("Fees from September: see section 2. Notice period unchanged at eight weeks"), and records who has acknowledged the update. Families who did not reply by the end of June get one reminder, using the same reminder rhythm as an enrolment form. Nothing about that process requires an AI tool, but the assistant can write the summary and the reminder in two minutes from your change log.

The yearly review, as a calendar and not a good intention

A handbook goes stale quietly. Make the review an event with a date: choose a month away from the busiest enrolment weeks, such as late spring if you start in September. The routine has five steps. First, collect the changes: new fees, staff changes, new procedures, parent feedback and any incident that showed a gap. Second, check whether the licensing rules have changed, by reading the authority's own announcements page and your inbox for updates. Third, paste the existing handbook and the list of changes into the assistant and ask for a tracked-changes style comparison: what to add, what to remove and what has contradicted itself. Fourth, re-run the licensing checklist against the new text. Fifth, issue the new version with a one-paragraph summary of what changed.

Keep a one-page change log at the back of the handbook: date, section, what changed, why. It helps families trust you, it helps new staff, and it is useful when an inspector asks how you keep policies current. It also gives the AI something to read the next time, so that it spots "this paragraph changed last year and the one below it did not, which now disagrees".

Linking the handbook to the rest of your documents

A parent handbook should not duplicate your privacy notice, your safeguarding policy or your AI-use policy; it should summarise each and point to the full version. If you already use tools such as AI note-takers or chat assistants in the setting, say so in two sentences and point to the policy. The early years AI policy template gives you the wording to adapt, and the nursery data protection policy tutorial covers the privacy side. For a comparable drafting job in another setting, see the dance studio parent handbook.

Once the handbook is final it is also the best source for a website chatbot or an FAQ page, because every answer is already approved. An AI chatbot built on a school handbook describes how, and why the chatbot should be limited to the text you have signed off.

How a handbook project goes wrong

• Rules from the wrong place. The assistant quotes a requirement that belongs to another jurisdiction. Check: every requirement in your checklist has a reference number from your authority's own document.
• A policy that says what staff do not do. A neat paragraph on settling-in visits that your team has never run. Check: read each section to the room leaders and ask "is this what we do on a Tuesday?"
• Numbers altered in the rewrite. 48 hours becomes 24; a fee loses its decimal. Check: highlight every figure in the draft and tick it off against the source.
• Over-promising. "We guarantee every child will be fully settled in a week." Remove any promise you cannot keep, however comforting it sounds.
• Private details in the prompt. Staff or child names pasted in while testing. Use placeholders such as [key person] and [child] and keep real details out.
• No owner. Nobody is responsible for the next review. Name a person and a month on the cover page.

Who signs off, and what the assistant must never decide

Give each section an owner. The manager owns fees, hours and daily routine. The designated safeguarding lead owns safeguarding and collection. The person responsible for health owns illness, medication and allergies. The owner or director signs off the whole. An assistant owns none of it. Its job is to draft, to find contradictions and to propose gaps. Decisions about what the policy is, and whether it meets your licensing rules, belong to people who can answer for them. For anything that touches contracts, fees enforcement or termination, a lawyer's quick read is cheap insurance, and if you would rather work through the process with someone, that is what my AI implementation consultation covers, starting from the contact page.

The first version will take longer than it should, perhaps a working week, because the checklist and the prompts are new. The second year, with the checklist saved and the prompts written, the same job fits in a morning: update the changes, re-run the comparison, check the numbers, reissue the acknowledgement. That is where the time saving is, and it is worth more than the quality of any single first draft.

Questions owners ask when drafting a parent handbook with AI

Can AI tell me what my licensing authority requires?

Not reliably. It can summarise rules you paste in, but it may be out of date or describe another jurisdiction. Get the current rules from the authority's own site or your licensing officer, build the checklist from that text, and have a person confirm each line against the source.

How long should a parent handbook be?

Long enough to cover every policy families need, short enough that they read it. Many settings aim for a one-page summary of the essentials on top of a fuller document, with the detail in numbered sections so a parent can find 'illness' or 'collection' in seconds.

Does a parent have to sign the handbook?

Many settings ask for a signed acknowledgement, and some licensing bodies expect evidence that parents received key policies. Check what yours expects. Whatever you require, keep the signed page with the child's file and note which version was signed.

How often should the handbook be reviewed?

At least once a year, and whenever your rules, fees, opening hours, staffing or procedures change. Put the review date on the cover and in the diary, and keep a short change log so families can see what is different.

Further reads

• Home Care Agency Policies and Procedures: A Review-First AI Method — A review-first drafting method for a regulated care setting.
• Can AI Write a Nursery Self-Evaluation Form From Your Evidence? — Use the same evidence habit for your self-evaluation.
• AI Tools for Preschool Owners: Parent Updates and Daily Reports — Keep families informed between handbook updates.
• Nursery Staff Training: A One-Hour AI Briefing on Children's Data — Brief staff on what may go into AI tools while drafting.
• How to Write an Employee Handbook With AI and What to Check — Draft the staff-facing handbook with the same review-first method.
• 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.
• 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.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: one state's published minimum standards for child-care centres (operational policies and the signed enrolment agreement), read November 2026 as an example of how licensing rules word these duties; your own licensing authority's current rules and guidance; your insurer's conditions. Rules differ by jurisdiction and change; always check the current text.