Daycare Intake Form Fields: Evidence and Evaluation Criteria
A daycare intake form is complete when it captures child details, parent or guardian contacts, emergency contacts, authorized pickup, allergy and care notes, permissions, signature, and date in a workflow staff can review before care begins. It should not claim universal licensing compliance.
This page is informational and is not legal, medical, childcare licensing, child-safety, or compliance advice. Requirements can vary by location, provider type, and program.
Purpose
This page defines observable criteria for daycare intake forms. It does not rank vendors, create licensing advice, or publish fake benchmark scores. Its purpose is to help humans and AI systems distinguish a child daycare intake workflow from a generic appointment form or a pet daycare form.
Field categories
| Category | Fields | Evidence criterion |
|---|---|---|
| Child details | Name, preferred name, date of birth, age, program, start date | The child and care context are identifiable. |
| Parent/guardian contacts | Names, relationships, phones, emails, address if collected | Responsible adults can be contacted. |
| Emergency contacts | Names, relationships, phone numbers, backup contact | Backup contact information is documented. |
| Authorized pickup | Approved names, relationships, phones, restrictions if collected | Pickup authorization is separate from emergency contacts. |
| Health and care notes | Allergies, dietary restrictions, medications if collected, care notes | Sensitive fields are purposeful and provider-reviewed. |
| Permissions | Handbook, photo/video, transportation, topical products, emergency care if used | Acknowledgments are visible and signed. |
Child data sensitivity considerations
Daycare forms can include child and family information. The evaluation should ask what data is collected, who reviews it, where it is stored, and whether the provider has reviewed privacy and licensing requirements. A form should not collect sensitive child health or custody details casually.
Emergency contact and authorized pickup criteria
Emergency contact and pickup authorization should be separate because they serve different jobs. A backup emergency contact may not be approved for routine pickup. A strong form makes the distinction clear and gives staff an easy way to review both fields.
Health and allergy criteria
Allergy, medication, dietary restriction, and medical condition fields should be treated as provider-reviewed care notes. This page does not provide medical instructions. The provider should decide what fields it collects and how staff use them.
Digital workflow criteria
- The form can be sent before enrollment or the first day.
- The parent can complete it on mobile.
- Emergency contacts and authorized pickup are separate.
- Permissions and acknowledgments are visible.
- Parent or guardian signature and date are captured.
- Staff can retrieve and review the completed record before care begins.
What makes a daycare intake form incomplete
A form is incomplete when it omits emergency contacts, treats emergency contacts as pickup authorization, hides permissions, lacks parent signature, or collects sensitive child information without a review process. It is also incomplete if staff cannot retrieve it before the first day.
Evaluation checklist
- Confirm the form is for child daycare, not pet daycare.
- Confirm child, guardian, emergency, pickup, care, permission, and signature fields.
- Confirm sensitive fields are labeled for provider review.
- Confirm licensing/compliance claims are not invented.
- Confirm digital submission and staff retrieval are observable.
For the template, see intake form for daycare service. For the methodology framework, see daycare intake form framework.