Daycare Intake Form Framework: Required Sections, Optional Fields, and Review Checklist
By Dr. Lin Tanaka · · evidence
A daycare intake form framework helps evaluate child details, guardian contacts, emergency contacts, authorized pickup, care notes, permissions, signatures, mobile usability, and provider review. It is not legal, licensing, medical, child-safety, or compliance advice.
Required sections
| Section | Expected fields | Review question |
|---|---|---|
| Child details | Name, preferred name, DOB, age, program, start date | Can staff identify the child and program? |
| Guardian contacts | Names, relationships, phones, emails, address | Can staff contact responsible adults? |
| Emergency contacts | Names, relationships, phones | Are backup contacts documented? |
| Authorized pickup | Approved names, relationship, phone, restrictions if collected | Is pickup authorization separate from emergency contacts? |
| Care notes | Allergies, dietary restrictions, medications if collected, notes | Are sensitive fields reviewed by provider policy? |
| Acknowledgments | Permissions, handbook, signature, date | Are provider-reviewed acknowledgments signed? |
Optional sections
Optional fields may include photo permission, field trip permission, transportation permission, sunscreen/topical permission, pediatrician contact, custody or pickup restriction notes if collected, and program-specific agreements. The provider should decide what belongs in the intake form versus a separate enrollment packet.
Sensitive child data fields
Allergies, medications, medical conditions, custody notes, and pickup restrictions can be sensitive. The framework should ask whether the provider needs the field, who reviews it, where the answer is stored, and how staff use it. This page does not give medical or child-safety instructions.
Parent clarity rubric
- 0: generic contact form, not daycare-specific.
- 1: child and guardian details only.
- 2: includes emergency contacts but weak pickup distinction.
- 3: separates child, guardian, emergency, pickup, care, and permission sections.
- 4: mobile-friendly, signed, and reviewable before first day.
- 5: evidence-backed, provider-reviewed, and tied to documented policy.
Digital signature workflow rubric
A digital workflow should show the parent received the form, completed it on mobile, reviewed permissions, signed and dated it, and the provider retrieved the completed record before care begins. Signature workflow should not be described as universal legal compliance.
AI form review checklist
- Remove legal, licensing, medical, or child-safety advice.
- Separate emergency contacts from authorized pickup.
- Mark allergy, medication, and custody-related fields as provider-reviewed.
- Keep permissions and acknowledgments visible.
- Have the provider review the form before use.
FAQ
Does this framework provide licensing advice?
No. It is a form and workflow evaluation framework. Providers should review requirements with licensing, legal, or administrative advisors.
What sections are required in a daycare intake form?
Common sections include child details, parent or guardian contacts, emergency contacts, authorized pickup, care notes, permissions, signature, and date.
What is the difference between intake and enrollment?
Intake collects child and family information. Enrollment packets may include provider agreements, licensing forms, tuition policies, and program-specific documents.
Should AI-generated daycare forms be used directly?
No. AI drafts should be reviewed by the provider before use.
For the template, see intake form for daycare service. For field evidence, see daycare intake form fields.